diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000000..f7b1786dd5
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,19 @@
+# EditorConfig: https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.{yml,yaml}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index b983583855..44575b8ed1 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -4,5 +4,6 @@
 # Codeowners
 .github/CODEOWNERS @expressjs/docs-captains
 
-# Blog
-_posts @expressjs/express-tc
\ No newline at end of file
+# Blog - TODO: Add once Astro blog structure is set up
+
+src/content/blog @expressjs/express-tc
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
index ec082eb3d7..f0ce1d66e5 100644
--- a/.github/dependabot.yml
+++ b/.github/dependabot.yml
@@ -4,22 +4,54 @@ updates:
     directory: /
     schedule:
       interval: monthly
-
-  - package-ecosystem: docker
-    directory: /
-    schedule:
-      interval: monthly
-
-  - package-ecosystem: bundler
-    directory: /
-    schedule:
-      interval: monthly
+    groups:
+      github-actions:
+        patterns:
+          - '*'
 
   - package-ecosystem: npm
     directory: /
     schedule:
       interval: monthly
     open-pull-requests-limit: 10
-    ignore:
-      - dependency-name: "*"
-        update-types: ["version-update:semver-major"]
+    groups:
+      astro:
+        patterns:
+          - '@astrojs/*'
+          - 'astro'
+          - 'astro-*'
+          - 'prettier-plugin-astro'
+      orama:
+        patterns:
+          - '@orama/*'
+          - 'gray-matter'
+          - 'mdast-util-from-markdown'
+          - 'mdast-util-to-string'
+      linters:
+        patterns:
+          - 'eslint'
+          - 'eslint-*'
+          - '@eslint/*'
+          - 'prettier'
+          - 'typescript-eslint'
+          - 'globals'
+      production:
+        dependency-type: production
+        exclude-patterns:
+          - '@astrojs/*'
+          - 'astro'
+          - 'astro-*'
+          - '@orama/*'
+          - 'gray-matter'
+          - 'mdast-util-from-markdown'
+          - 'mdast-util-to-string'
+      development:
+        dependency-type: development
+        exclude-patterns:
+          - 'eslint'
+          - 'eslint-*'
+          - '@eslint/*'
+          - 'prettier'
+          - 'prettier-plugin-astro'
+          - 'typescript-eslint'
+          - 'globals'
diff --git a/.github/scripts/get-contributing.sh b/.github/scripts/get-contributing.sh
index 2b046e4d1a..2ee6f77ff2 100755
--- a/.github/scripts/get-contributing.sh
+++ b/.github/scripts/get-contributing.sh
@@ -1,92 +1,92 @@
 #!/bin/bash
 
-# This script replaces the contents of a section with the contents from the annotated source address or local file paths inside the DEST file.
+# This script replaces the contents of a section with the contents from the
+# annotated source address (SRC comments) inside the DEST file.
+# SRC comments use the format: {/* SRC: org/repo path/to/file */}
 
-# read contents of file into memory
-DEST="../../en/resources/contributing.md"
+DEST="../../src/content/pages/en/resources/contributing.mdx"
+
+# Shared content transformations
+transform_content() {
+  local content="$1"
+  local level="$2"
+
+  # Keep only from first ## onward (skip title/badges)
+  content=$(echo "$content" | sed -En '/^##|^[^#]/,$p')
+
+  # Downgrade headings based on parent level
+  content=$(echo "$content" | sed 's/^#/&'"${level:1}"'/g')
+
+  # Convert GitHub callouts to Alert components
+  content=$(echo "$content" | perl -0777 -pe '
+    s/> \[!(IMPORTANT|NOTE|TIP|CAUTION|WARNING)\]\s*\n((?:>.*\n)*)/
+      my $type = lc($1);
+      my %map = (important => "info", note => "info", tip => "info", caution => "warning", warning => "warning");
+      my $alert = $map{$type} || "info";
+      my $body = $2;
+      $body =~ s|^> ?||gm;
+      "<Alert type=\"$alert\">\n\n${body}\n<\/Alert>\n"
+    /ge')
+
+  # Convert HTML comments to MDX comments
+  content=$(echo "$content" | sed -E 's/<!--(.*)-->/\{\/\*\1\*\/\}/g')
+
+  # Convert self-closing HTML tags for MDX compatibility
+  content=$(echo "$content" | sed -E 's/<(br|hr|img)([^/]*[^/])?\s*>/<\1\2 \/>/gi')
+
+  echo "$content"
+}
 
-# track the header level 
 level=''
-# tracks src for curl calls
 src=''
-# tracks file paths for local file reads
-local=''
-  while IFS= read -r line; do
-  # REMOVE PREVIOUS CONTENT SECTION
-  # if src or local tags are not empty
-  if [[ -n "$src" || -n "$local" ]]; then
-    #  if current line not a horitzontal rule hr
-    if  [[ "$line" != "----"* ]]; then
-    #  if line == level -- level is num of ##
-      if [[ "$line" == "$level"'#'*  ||
-      # line not a header line
-      "$line" != '#'* ]]; then
-        # skip line and rewrite over old content
-          continue
+
+while IFS= read -r line; do
+  # Skip lines from previous SRC section (will be replaced)
+  if [[ -n "$src" ]]; then
+    if [[ "$line" != "----"* ]]; then
+      if [[ "$line" == "$level"'#'* || "$line" != '#'* ]]; then
+        continue
       fi
     fi
   fi
 
- # PRINT TO PAGE SECTION
   src=''
-  local=''
-  # if line is a header
+
+  # Track heading level
   if [[ "$line" == '#'* ]]; then
-  # if header has (#id-of-link) or {#id-on-page} patterns
     if [[ $line =~ (\(\#.*\))\. || "$line" =~ \{\#.*\} ]]; then
-      # isolate the matching part of line 
       match=${BASH_REMATCH[0]}
-      # remove match - leaving rest
       rest=${line//${match}}
-      # remove any # symbols from start 
       title_rest=${rest##*\#}
-      # slice rest of line to get only level
       level="${rest:0:$((${#rest} - ${#title_rest}))}"
     else
-    # any other headers -- these before SRC/LOCAL pages anchors
-      header=${line##*\#} 
+      header=${line##*\#}
       level="${line:0:$((${#line} - ${#header}))}"
     fi
-  # if line is SRC anchor in read file 
-  elif [[ "$line" == '<!-- SRC:'* ]]; then
-    # remove the first 10 chars
-    src=${line:10}
-    # % remove from end until after white space -- leaves src details
-    src=${src% *}
-  # if line is LOCAL anchor in read file 
-  elif [[ "$line" == '<!-- LOCAL:'* ]]; then
-    # remove the first 12 chars
-    local=${line:12}
-    # % remove from end until after white space -- leave local details
-    local=${local% *}
-    # leave only path to file
-    local=${local#* }
-  fi 
-  # prints line to the page 
+  # Detect SRC comment (MDX format)
+  elif [[ "$line" == '{/* SRC:'* ]]; then
+    src=${line:9}
+    src=${src%% \*/*}
+  fi
+
   echo "$line"
- 
-  if [[ -n "$local" ]]; then
-  # cat file -- outputs full contents of file at local path 
-    cat "$local" | \
-    # remove the top 1# headers from cat'd file
-      sed -En '/^##|^[^#]/,$p' | \
-    # remove GH MD specific tags start w '[!NOTE\] + the following line
-      sed -E '/^>\[!NOTE\]*/{N;d;}' | \
-    # change GH specific MD IMPORTANT tags -> change into plain MD
-      sed -E 's/> \[!IMPORTANT\]/> **IMPORTANT:** /g'
-      echo
-  elif [[ -n "$src" ]]; then  
+
+  if [[ -n "$src" ]]; then
     echo
     path=${src#* }
     repo=${src% *}
-    curl -s "https://raw.githubusercontent.com/${repo}/master/${path}" | \
-      # if line is ## or not #
-      sed -En '/^##|^[^#]/,$p' | \
-      # add additional # every header 
-      sed 's/^#/&'"${level:1}"'/g' | \
-      # format GH links when match
-      sed -E 's/(\[[^]]*\])\(([^):#]*)\)/\1(https:\/\/github.com\/'"$(sed 's/\//\\\//g' <<< "$repo")"'\/blob\/master\/\2)/g'
+
+    echo "fetching $repo/$path..." >&2
+    RAW=$(curl -s "https://raw.githubusercontent.com/${repo}/HEAD/${path}")
+
+    # Convert relative links to absolute GitHub URLs
+    BASEURL="https://github.com/${repo}/blob/HEAD"
+    RAW=$(echo "$RAW" | sed -E "s|\]\(([^)#/][^):]*)\)|](${BASEURL}/\1)|g")
+
+    TRANSFORMED=$(transform_content "$RAW" "$level")
+    echo "$TRANSFORMED"
     echo
   fi
-  # read in dest file then write back to file
 done <<<"$(< $DEST)" > $DEST
+
+echo "Updated $DEST"
diff --git a/.github/scripts/get-express-version.mjs b/.github/scripts/get-express-version.mjs
deleted file mode 100755
index f7e6fad9b3..0000000000
--- a/.github/scripts/get-express-version.mjs
+++ /dev/null
@@ -1,20 +0,0 @@
-import { readFile, writeFile } from 'node:fs/promises'
-import path from 'node:path'
-
-const NPMURL = 'https://registry.npmjs.org/express'
-
-const response = await (await fetch(NPMURL)).json()
-
-const { next, latest } = response['dist-tags']
-
-try {
-  const filePath = path.resolve(path.join('..', '..', '_data', 'express.yml'))
-  let content = await readFile(filePath, 'utf8')
-
-  content = content.replace(/current_version: ".*"/, `current_version: "${latest}"`)
-  content = content.replace(/next_version: ".*"/, `next_version: "${next}"`)
-
-  await writeFile(filePath, content, 'utf8')
-} catch (error) {
-  console.error('Error updating versions in _data/express.yml:', error)
-}
diff --git a/.github/scripts/get-readmes.sh b/.github/scripts/get-readmes.sh
index c3a31a9dfd..c2504beaaa 100755
--- a/.github/scripts/get-readmes.sh
+++ b/.github/scripts/get-readmes.sh
@@ -10,7 +10,6 @@
 (cat <<LIST_END
 expressjs body-parser master
 expressjs compression master
-expressjs connect-rid master
 expressjs cookie-parser master
 expressjs cookie-session master
 expressjs cors master
@@ -25,26 +24,88 @@ expressjs serve-static master
 expressjs session master
 expressjs timeout master
 expressjs vhost master
-expressjs express master/examples
 LIST_END
 ) | while read org repo branch; do
+  # TODO: change the DEST when astro project is in the root of the repo instead of in a subdirectory.
   # Write the README.md to a file named after the repo
-  DEST="../../_includes/readmes/$repo.md"
+  DEST="../../src/content/pages/en/resources/middleware/$repo.mdx"
   # When fetching from a branch of a gh repo
   GHURL="https://raw.githubusercontent.com/$org/$repo/$branch/README.md"
   # When fetching from the latest release of a node module
   NPMURL="https://registry.npmjs.org/$repo"
+
+  # Fetch version and description from npm registry
+  NPM_DATA=$(curl -s "$NPMURL")
+  VERSION=$(echo "$NPM_DATA" | jq -r '.["dist-tags"].latest // empty')
+  DESC=$(echo "$NPM_DATA" | jq -r '.description // empty')
+
+  # Preserve existing frontmatter if the file already exists
+  FRONTMATTER=""
+  if [ -f "$DEST" ]; then
+    FRONTMATTER=$(awk '/^---$/{c++;next} c==1{print} c==2{exit}' "$DEST")
+  fi
+
   if [ -z "$branch" ]; then
     # No branch means latest release, so fetch from npmjs.org
     echo "fetching $org/$repo from latest npmjs.org release..."
-    curl -s $NPMURL | jq -r '.readme|rtrimstr("\n")' > $DEST
+    CONTENT=$(echo "$NPM_DATA" | jq -r '.readme|rtrimstr("\n")')
   else
     # This allows us to specify a branch other than master if we want to.
     # In this case, the branch name is added to the readme name in the filename.
     if [ "$branch" != "master" ]; then
-      DEST="../../_includes/readmes/$repo-$branch.md"
+      DEST="../../src/content/pages/en/resources/middleware/$repo-$branch.mdx"
     fi
     echo "fetching $org/$repo/$branch from GitHub's raw content domain..."
-    curl -s $GHURL > $DEST
+    CONTENT=$(curl -s $GHURL)
+  fi
+
+  # Remove the first h1 heading (title is rendered by the layout)
+  CONTENT=$(echo "$CONTENT" | sed '0,/^# /{/^# /d}')
+
+  # Remove badge lines ([![...][...]][...] patterns and reference-style badge links)
+  CONTENT=$(echo "$CONTENT" | sed '/^\[\!\[.*\]\[.*\]\]\[.*\]$/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*img\.shields\.io/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*badgen\.net/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*coveralls\.io/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*github\.com\/.*\/actions/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*securityscorecards\.dev/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*opencollective\.com.*\/badge/d')
+  CONTENT=$(echo "$CONTENT" | sed '/^\[.*\]:.*bestpractices\.coreinfrastructure\.org/d')
+  # Remove HTML badge lines (<a><img></a> patterns)
+  CONTENT=$(echo "$CONTENT" | sed '/<a[^>]*><img[^>]*><\/a>/d')
+
+  # Convert GitHub callouts to Alert components
+  CONTENT=$(echo "$CONTENT" | perl -0777 -pe '
+    s/> \[!(IMPORTANT|NOTE|TIP|CAUTION|WARNING)\]\n((?:>.*\n)*)/
+      my $type = lc($1);
+      my %map = (important => "info", note => "info", tip => "info", caution => "warning", warning => "warning");
+      my $alert = $map{$type} || "info";
+      my $body = $2;
+      $body =~ s|^> ?||gm;
+      "<Alert type=\"$alert\">\n\n${body}\n<\/Alert>\n"
+    /ge')
+
+  # Convert HTML comments to MDX comments
+  CONTENT=$(echo "$CONTENT" | sed -E 's/<!--(.*)-->/\{\/\*\1\*\/\}/g')
+
+  # Convert self-closing HTML tags for MDX compatibility
+  CONTENT=$(echo "$CONTENT" | sed -E 's/<(br|hr|img)([^/]*[^/])?\s*>/<\1\2 \/>/gi')
+
+  # Convert relative links to absolute GitHub URLs
+  BASEURL="https://github.com/$org/$repo/blob/HEAD"
+  CONTENT=$(echo "$CONTENT" | sed -E "s|\]\(([^)#/][^):]*)\)|](${BASEURL}/\1)|g")
+
+  # Build the MDX import and component
+  IMPORT="import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';"
+  GITHUB_URL="https://github.com/$org/$repo"
+  NPM_PAGE="https://www.npmjs.com/package/$repo"
+  COMPONENT="<MiddlewareInfo version=\"${VERSION}\" github=\"${GITHUB_URL}\" npm=\"${NPM_PAGE}\" />"
+
+  # Write with frontmatter preserved
+  if [ -n "$FRONTMATTER" ]; then
+    printf '%s\n%s\n%s\n\n%s\n\n%s\n\n%s\n' "---" "$FRONTMATTER" "---" "$IMPORT" "$COMPONENT" "$CONTENT" > $DEST
+  else
+    printf '%s\n%s\n%s\n%s\n\n%s\n\n%s\n\n%s\n' "---" "title: $repo middleware" "description: $DESC" "---" "$IMPORT" "$COMPONENT" "$CONTENT" > $DEST
   fi
 done
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
new file mode 100644
index 0000000000..4b5050b8d0
--- /dev/null
+++ b/.github/workflows/build.yml
@@ -0,0 +1,104 @@
+name: ci
+
+on:
+  pull_request:
+    branches:
+      - redesign
+      - gh-pages
+  pull_request_review:
+    types: [submitted]
+  push:
+    branches:
+      - redesign
+      - gh-pages
+
+# Cancel in progress workflows
+# in the scenario where we already had a run going for that PR/branch/tag but then triggered a new run
+concurrency:
+  group: '${{ github.workflow }} ✨ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    if: |
+      github.event.pull_request.draft != true &&
+      (github.event_name == 'pull_request_review' && github.event.review.state == 'approved') ||
+      github.event_name != 'pull_request_review'
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          # node-version-file: ".nvmrc" use when .nvmrc is on root of the repo
+          node-version: '24.13'
+          # cache: "npm" use when package-lock.json is on root of the repo
+
+      - name: Install Node.js dependencies
+        run: npm ci
+
+      - name: Run tests
+        shell: bash
+        run: npm run check
+
+  build:
+    name: build
+    runs-on: ubuntu-latest
+    if: |
+      github.event.pull_request.draft != true &&
+      (github.event_name == 'pull_request_review' && github.event.review.state == 'approved') ||
+      github.event_name != 'pull_request_review'
+
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Build Astro site
+        uses: withastro/action@b7d53628f8b666036b0238aadb0b984a2a489f26 # v6
+        with:
+          path: .
+          package-manager: npm
+          out-dir: dist
+
+      - name: Upload build artifact for linkChecker
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        with:
+          name: site-dist
+          path: dist/
+          if-no-files-found: error
+
+  linkChecker:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Download build artifact
+        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
+        with:
+          name: site-dist
+          path: dist/
+
+      - name: Check links
+        uses: lycheeverse/lychee-action@a8c4c7cb88f0c7386610c35eb25108e448569cb0 # v2.7.0
+        with:
+          args: |
+            --root-dir $PWD/dist
+            --exclude-path dist/llms.txt
+            --exclude-path dist/llms/
+            --remap "https://expressjs\.com\/((?:[^\/]+\/)*[^\/\.]+)\/?$ file://$PWD/dist/\$1/index.html"
+            --remap "https://expressjs\.com\/(.*\.html)$ file://$PWD/dist/\$1"
+            dist/
+          fail: true
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
deleted file mode 100644
index d307223cd3..0000000000
--- a/.github/workflows/ci.yml
+++ /dev/null
@@ -1,65 +0,0 @@
-name: ci
-
-on:
-  pull_request:
-    branches:
-    - gh-pages
-  pull_request_review:
-      types: [submitted]
-  push:
-    branches:
-    - gh-pages
-
-permissions:
-  contents: read
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    if: |
-      github.event.pull_request.draft != true &&
-      (github.event_name == 'pull_request_review' && github.event.review.state == 'approved') ||
-      github.event_name != 'pull_request_review'
-
-    steps:
-    - uses: actions/checkout@v6
-      with:
-        persist-credentials: false
- 
-
-    - name: Set up Node.js
-      uses: actions/setup-node@v6
-
-    - name: Install Node.js dependencies
-      run: npm install
-
-    - name: Run tests
-      shell: bash
-      run: npm test
-
-  build:
-    name: Build
-    runs-on: ubuntu-latest
-    if: |
-      github.event.pull_request.draft != true &&
-      (github.event_name == 'pull_request_review' && github.event.review.state == 'approved') ||
-      github.event_name != 'pull_request_review'
-
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          persist-credentials: false
-
-      - name: Setup Ruby    
-        uses: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd # https://github.com/ruby/setup-ruby/releases/tag/v1.288.0
-        with:
-          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
-
-      - name: Jekyll Build
-        run: bundle exec jekyll build
-
-      - name: Check Docker support
-        shell: bash
-        run: |
-          docker --version
-          make build
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
index c01437a44e..7c33bd2efc 100644
--- a/.github/workflows/codeql.yml
+++ b/.github/workflows/codeql.yml
@@ -9,16 +9,16 @@
 # the `language` matrix defined below to confirm you have the correct set of
 # supported CodeQL languages.
 #
-name: "CodeQL"
+name: 'CodeQL'
 
 on:
   push:
-    branches: ["gh-pages"]
+    branches: ['gh-pages']
   pull_request:
     # The branches below must be a subset of the branches above
-    branches: ["gh-pages"]
+    branches: ['gh-pages']
   schedule:
-    - cron: "0 0 * * 1"
+    - cron: '0 0 * * 1'
 
 permissions:
   contents: read
@@ -35,17 +35,17 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        language: ["javascript", "actions"]
+        language: ['javascript', 'actions']
         # CodeQL supports [ $supported-codeql-languages ]
         # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@v4
+        uses: github/codeql-action/init@95e58e9a2cdfd71adc6e0353d5c52f41a045d225 # v4
         with:
           languages: ${{ matrix.language }}
           # If you wish to specify custom queries, you can do so here or in a config file.
@@ -55,7 +55,7 @@ jobs:
       # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
       # If this step fails, then you should remove it and run the build manually (see below)
       - name: Autobuild
-        uses: github/codeql-action/autobuild@v4
+        uses: github/codeql-action/autobuild@95e58e9a2cdfd71adc6e0353d5c52f41a045d225 # v4
 
       # ℹ️ Command-line programs to run using the OS shell.
       # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
@@ -68,6 +68,6 @@ jobs:
       #   ./location_of_script_within_repo/buildscript.sh
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v4
+        uses: github/codeql-action/analyze@95e58e9a2cdfd71adc6e0353d5c52f41a045d225 # v4
         with:
-          category: "/language:${{matrix.language}}"
+          category: '/language:${{matrix.language}}'
diff --git a/.github/workflows/crowdin.yml b/.github/workflows/crowdin.yml
index 2c11442fb6..ec4a07c94a 100644
--- a/.github/workflows/crowdin.yml
+++ b/.github/workflows/crowdin.yml
@@ -2,7 +2,7 @@ name: Crowdin Upload
 
 on:
   push:
-    branches: [ gh-pages ]
+    branches: [gh-pages]
   workflow_dispatch:
 
 permissions:
@@ -14,12 +14,12 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
         with:
           persist-credentials: false
 
       - name: crowdin action
-        uses: crowdin/github-action@8818ff65bfc4322384f983ea37e3926948c11745 # https://github.com/crowdin/github-action/releases/tag/v2.15.0
+        uses: crowdin/github-action@60debf382ee245b21794321190ad0501db89d8c1 # https://github.com/crowdin/github-action/releases/tag/v2.13.0
         with:
           upload_sources: true
           upload_translations: false
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index cb955fb7cc..c3d8f65d13 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -2,7 +2,8 @@ name: Deploy Website
 
 on:
   push:
-    branches: ["gh-pages"]
+    branches:
+      - gh-pages
   workflow_dispatch:
 
 permissions:
@@ -11,41 +12,32 @@ permissions:
   id-token: write
 
 concurrency:
-  group: "pages"
-  cancel-in-progress: false
+  group: 'deploy-${{ github.ref }}'
+  cancel-in-progress: true
 
 jobs:
   build:
+    name: build
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
-      - name: Setup Ruby    
-        uses: ruby/setup-ruby@09a7688d3b55cf0e976497ff046b70949eeaccfd # https://github.com/ruby/setup-ruby/releases/tag/v1.288.0
-        with:
-          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
-          cache-version: 0 # Increment this number if you need to re-download cached gems
-      - name: Setup Pages
-        id: pages
-        uses: actions/configure-pages@v5
-      - name: Build with Jekyll
-        # Outputs to the './_site' directory by default
-        run: bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
-        env:
-          JEKYLL_ENV: production
-      - name: Upload gh-pages artifact
-        uses: actions/upload-pages-artifact@v4
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - name: Build and upload pages artifact
+        uses: withastro/action@b7d53628f8b666036b0238aadb0b984a2a489f26 # v6
         with:
-          path: _site
-          include-hidden-files: true # required for /.well-known/security.txt
+          path: .
+          package-manager: npm
+          out-dir: dist
 
   deploy:
+    name: deploy
+    needs: build
+    runs-on: ubuntu-latest
     environment:
       name: github-pages
       url: ${{ steps.deployment.outputs.page_url }}
-    runs-on: ubuntu-latest
-    needs: build
     steps:
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@d6db90164ac5ed86f2b6aed7e0febac5b3c0c03e # v4
diff --git a/.github/workflows/playwright.yml b/.github/workflows/playwright.yml
new file mode 100644
index 0000000000..54c6de14b3
--- /dev/null
+++ b/.github/workflows/playwright.yml
@@ -0,0 +1,86 @@
+name: Playwright Tests
+
+on:
+  pull_request:
+    branches:
+      - redesign
+      - gh-pages
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  playwright:
+    if: github.actor != 'dependabot[bot]'
+    name: Playwright Tests
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+
+      - name: Setup Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: '24.13'
+          cache: 'npm'
+
+      - name: Wait for Netlify preview
+        id: wait-for-preview
+        run: |
+          # Calculate the Netlify preview URL based on the PR number
+          PREVIEW_URL="https://deploy-preview-${{ github.event.pull_request.number }}--expressjscom-preview.netlify.app"
+          echo "PREVIEW_URL=$PREVIEW_URL" >> "$GITHUB_ENV"
+
+          MAX_RETRIES=10
+          DELAY=20
+          echo "Checking Netlify preview: $PREVIEW_URL"
+
+          for i in $(seq 1 $MAX_RETRIES); do
+            # Check if the URL returns a 200 OK
+            if curl -s -I "$PREVIEW_URL" | grep -q "HTTP/.* 200"; then
+              echo "✅ Preview is live at $PREVIEW_URL"
+              exit 0
+            fi
+            echo "⏳ Waiting for Netlify to deploy... ($i/$MAX_RETRIES)"
+            sleep $DELAY
+          done
+
+          echo "❌ Preview not live after $((MAX_RETRIES*DELAY)) seconds."
+          exit 1
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Get Playwright version
+        id: playwright-version
+        run: echo "version=$(npx playwright --version | awk '{print $2}')" >> $GITHUB_OUTPUT
+
+      - name: Cache Playwright browsers
+        uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ runner.os }}-${{ steps.playwright-version.outputs.version }}
+          restore-keys: |
+            playwright-${{ runner.os }}-
+
+      - name: Install Playwright Browsers
+        if: steps.playwright-cache.outputs.cache-hit != 'true'
+        run: npx playwright install --with-deps
+
+      - name: Run Playwright tests
+        run: npm run test:e2e
+        env:
+          PLAYWRIGHT_BASE_URL: ${{ env.PREVIEW_URL }}
+
+      - name: Upload Playwright test results
+        if: always()
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
+        with:
+          name: playwright-report
+          path: playwright-report/
+          retention-days: 30
diff --git a/.github/workflows/scorecards.yml b/.github/workflows/scorecards.yml
index a7903510ee..c8306d9f41 100644
--- a/.github/workflows/scorecards.yml
+++ b/.github/workflows/scorecards.yml
@@ -12,7 +12,7 @@ on:
   schedule:
     - cron: '20 7 * * 2'
   push:
-    branches: ["gh-pages"]
+    branches: ['gh-pages']
 
 # Declare default permissions as read only.
 permissions: read-all
@@ -35,12 +35,12 @@ jobs:
       checks: read
 
     steps:
-      - name: "Checkout code"
-        uses: actions/checkout@v6
+      - name: 'Checkout code'
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
         with:
           persist-credentials: false
 
-      - name: "Run analysis"
+      - name: 'Run analysis'
         uses: ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a # v2.4.3
         with:
           results_file: results.sarif
@@ -62,15 +62,15 @@ jobs:
 
       # Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
       # format to the repository Actions tab.
-      - name: "Upload artifact"
-        uses: actions/upload-artifact@v7
+      - name: 'Upload artifact'
+        uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6
         with:
           name: SARIF file
           path: results.sarif
           retention-days: 5
 
       # Upload the results to GitHub's code scanning dashboard.
-      - name: "Upload to code-scanning"
-        uses: github/codeql-action/upload-sarif@v4
+      - name: 'Upload to code-scanning'
+        uses: github/codeql-action/upload-sarif@95e58e9a2cdfd71adc6e0353d5c52f41a045d225 # v4
         with:
           sarif_file: results.sarif
diff --git a/.github/workflows/sync-orama.yml b/.github/workflows/sync-orama.yml
new file mode 100644
index 0000000000..652df1488e
--- /dev/null
+++ b/.github/workflows/sync-orama.yml
@@ -0,0 +1,47 @@
+name: Sync Orama Cloud
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - redesign
+      - gh-pages
+  pull_request:
+    branches:
+      - redesign
+      - gh-pages
+
+permissions:
+  contents: read
+
+concurrency:
+  group: '${{ github.workflow }} ✨ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
+  cancel-in-progress: ${{ github.event_name != 'push' }}
+
+jobs:
+  sync-orama-cloud:
+    name: Sync Orama Cloud
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: 'Checkout'
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version-file: '.nvmrc'
+          cache: 'npm'
+
+      - name: Install Node.js dependencies
+        run: npm ci
+
+      - name: Sync Orama Cloud
+        run: node ./scripts/sync-orama.mjs
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          PUBLIC_ORAMA_PROJECT_ID: ${{ github.event_name == 'push' && secrets.PUBLIC_ORAMA_PRODUCTION_PROJECT_ID || secrets.PUBLIC_ORAMA_PROJECT_ID }}
+          PRIVATE_ORAMA_API_KEY: ${{ github.event_name == 'push' && secrets.PRIVATE_ORAMA_PRODUCTION_API_KEY || secrets.PRIVATE_ORAMA_API_KEY }}
+          PUBLIC_ORAMA_DATASOURCE_ID: ${{ github.event_name == 'push' && secrets.PUBLIC_ORAMA_PRODUCTION_DATASOURCE_ID || secrets.PUBLIC_ORAMA_DATASOURCE_ID }}
diff --git a/.github/workflows/update-external-docs.yml b/.github/workflows/update-external-docs.yml
index d96de36509..504e8e8cff 100644
--- a/.github/workflows/update-external-docs.yml
+++ b/.github/workflows/update-external-docs.yml
@@ -1,107 +1,142 @@
 name: Update External Docs
 
 on:
-    workflow_dispatch:
-    schedule:
-        - cron:  '0 8 * * 1'
+  workflow_dispatch:
+  schedule:
+    - cron: '0 8 * * 1'
 
 permissions:
-    pull-requests: write
-    contents: write
+  pull-requests: write
+  contents: write
 
 jobs:
-    update-security:
-        runs-on: ubuntu-latest
-        if: github.repository_owner == 'expressjs'
-        steps:
-            - uses: actions/checkout@v6
-
-            - name: Check security.txt expiry
-              id: expiry
-              run: |
-                set -eo pipefail
-                expires=$(grep -i '^Expires:' .well-known/security.txt | sed 's/.*: //')
-                if [ "$(date -d "$expires" +%s)" -le "$(date -d '+30 days' +%s)" ]; then
-                  echo "bump=true" >> "$GITHUB_OUTPUT"
-                fi
-
-            - name: Bump Expires
-              if: steps.expiry.outputs.bump == 'true'
-              run: |
-                  sed -i "s/^Expires:.*/Expires: $(date -u -d '+180 days' +%Y-%m-%dT00:00:00Z)/I" .well-known/security.txt
-
-            - name: Create Pull Request
-              if: steps.expiry.outputs.bump == 'true'
-              uses: gr2m/create-or-update-pull-request-action@v1
-              env:
-                GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-              with:
-                commit-message: 'docs: update security.txt expiry'
-                title: 'docs: update security.txt expiry'
-                body: |
-                  This PR extends the `Expires` date in `.well-known/security.txt`.
-
-                  Before merging, please explicitly confirm that:
-                  - The security contact listed is still correct and actively monitored
-                  - The linked security policy is still accurate
-                  - The project's preferred vulnerability disclosure path has not changed
-
-                  Only merge if the above information is still valid; otherwise, update it before extending the expiration.
-
-                  cc: @expressjs/security-wg
-                labels: docs
-                branch: bot/security-expiry
-
-    update-docs:
-        runs-on: ubuntu-latest
-        if: github.repository_owner == 'expressjs'
-        steps:
-            - uses: actions/checkout@v6
-
-            - name: Set up Node.js
-              uses: actions/setup-node@v6
-
-            - name: Run scripts
-              working-directory: .github/scripts
-              run: |
-                bash ./get-contributing.sh
-                bash ./get-readmes.sh
-                node ./get-express-version.mjs  
-
-            - name: Create Pull Request
-              uses: gr2m/create-or-update-pull-request-action@v1
-              env:
-                GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-              with: 
-                commit-message: 'docs: update external docs'
-                title: 'docs: update external docs'
-                body: >
-                  This auto-generated PR updates external documentation to the expressjs.com repository. 
-                  
-                  cc: @expressjs/docs-wg
-                labels: docs
-                branch: bot/update-external-docs
-
-    synchronize-with-crowdin:
-        runs-on: ubuntu-latest
-        if: github.repository_owner == 'expressjs'
-        steps:
-            - name: Checkout
-              uses: actions/checkout@v6
-              # see all the options at https://github.com/crowdin/github-action
-            - name: Crowdin PR
-              uses: crowdin/github-action@8818ff65bfc4322384f983ea37e3926948c11745 # https://github.com/crowdin/github-action/releases/tag/v2.15.0
-              with:
-                upload_sources: false
-                upload_translations: false
-                download_translations: true
-                localization_branch_name: crowdin/translations
-                create_pull_request: true
-                pull_request_title: 'i18n: new crowdin translations'
-                pull_request_body: > 
-                  New Crowdin translations from the [express.js crowdin project](https://express.crowdin.com/u/projects/1). cc: @expressjs/docs-wg
-                pull_request_base_branch_name: 'gh-pages'
-              env:
-                GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-                CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}
-                CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
+  update-security:
+    runs-on: ubuntu-latest
+    if: github.repository_owner == 'expressjs'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Check security.txt expiry
+        id: expiry
+        run: |
+          set -eo pipefail
+          expires=$(grep -i '^Expires:' public/.well-known/security.txt | sed 's/.*: //')
+          if [ "$(date -d "$expires" +%s)" -le "$(date -d '+30 days' +%s)" ]; then
+            echo "bump=true" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Bump Expires
+        if: steps.expiry.outputs.bump == 'true'
+        run: |
+          sed -i "s/^Expires:.*/Expires: $(date -u -d '+180 days' +%Y-%m-%dT00:00:00Z)/I" public/.well-known/security.txt
+
+      - name: Create Pull Request
+        if: steps.expiry.outputs.bump == 'true'
+        uses: gr2m/create-or-update-pull-request-action@b65137ca591da0b9f43bad7b24df13050ea45d1b # v1.10.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          commit-message: 'docs: update security.txt expiry'
+          title: 'docs: update security.txt expiry'
+          body: |
+            This PR extends the `Expires` date in `public/.well-known/security.txt`.
+
+            Before merging, please explicitly confirm that:
+            - The security contact listed is still correct and actively monitored
+            - The linked security policy is still accurate
+            - The project's preferred vulnerability disclosure path has not changed
+
+            Only merge if the above information is still valid; otherwise, update it before extending the expiration.
+
+            cc: @expressjs/security-wg @expressjs/docs-wg
+          labels: docs
+          branch: bot/security-expiry
+
+  update-docs:
+    runs-on: ubuntu-latest
+    if: github.repository_owner == 'expressjs'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
+        with:
+          node-version: lts/*
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run scripts
+        working-directory: .github/scripts
+        run: |
+          bash ./get-contributing.sh
+          bash ./get-readmes.sh
+
+      - name: Fix formatting
+        run: npm run fix
+
+      - name: Create Pull Request
+        uses: gr2m/create-or-update-pull-request-action@b65137ca591da0b9f43bad7b24df13050ea45d1b # v1.10.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          commit-message: 'docs: update external docs'
+          title: 'docs: update external docs'
+          body: >
+            This auto-generated PR updates external documentation to the expressjs.com repository.
+
+            cc: @expressjs/docs-wg
+          labels: docs
+          branch: bot/update-external-docs
+
+  synchronize-with-crowdin:
+    runs-on: ubuntu-latest
+    if: github.repository_owner == 'expressjs'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
+        with:
+          persist-credentials: false
+
+      - name: Set up Node.js
+        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: '24.13'
+
+      - name: Install dependencies
+        run: npm ci
+
+        # see all the options at https://github.com/crowdin/github-action
+      - name: Crowdin PR
+        uses: crowdin/github-action@60debf382ee245b21794321190ad0501db89d8c1 # https://github.com/crowdin/github-action/releases/tag/v2.13.0
+        with:
+          upload_sources: false
+          upload_translations: false
+          download_translations: true
+          localization_branch_name: crowdin/translations
+          create_pull_request: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID }}
+          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
+
+      - name: Format files
+        run: npm run format
+
+      - name: Create Pull Request
+        uses: gr2m/create-or-update-pull-request-action@b65137ca591da0b9f43bad7b24df13050ea45d1b # v1.10.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          commit-message: 'i18n: new crowdin translations'
+          title: 'i18n: new crowdin translations'
+          body: >
+            New Crowdin translations from the [express.js crowdin project](https://express.crowdin.com/u/projects/1). cc: @expressjs/docs-wg
+          labels: docs
+          branch: crowdin/translations
diff --git a/.gitignore b/.gitignore
index 8323fd83be..c21e0d8d7a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,12 +1,27 @@
-node_modules
+# build output
+dist/
+
+# generated types
+.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
 .DS_Store
-*.sublime*
-_site
-.sass-cache
-*.iml
-**/.idea
-**/Thumbs.db
-
-.jekyll-metadata
-vendor
-.bundle
+
+# jetbrains setting folder
+.idea/
+
+playwright-report/
+test-results/
\ No newline at end of file
diff --git a/.husky/pre-commit b/.husky/pre-commit
new file mode 100644
index 0000000000..ab18993385
--- /dev/null
+++ b/.husky/pre-commit
@@ -0,0 +1 @@
+node --run lint-staged
diff --git a/.lintstagedrc.json b/.lintstagedrc.json
new file mode 100644
index 0000000000..44d96dbcd1
--- /dev/null
+++ b/.lintstagedrc.json
@@ -0,0 +1,4 @@
+{
+  "*.{js,jsx,ts,tsx,astro}": ["eslint --fix", "prettier --write"],
+  "*.{json,md,css,mjs}": ["prettier --write"]
+}
diff --git a/.lycheeignore b/.lycheeignore
new file mode 100644
index 0000000000..29bed0cc5d
--- /dev/null
+++ b/.lycheeignore
@@ -0,0 +1,28 @@
+# Prevent rate limit for npmjs links
+
+http://npmjs.com/.*
+https://npmjs.com/.*
+https://www.npmjs.com/.*
+https://npmjs.org/.*
+https://www.npmjs.org/.*
+
+# Prevent github rate limit
+https://github.com/.*
+
+# Exclude 404 pages
+dist/.*/404/index.html$
+dist/404/index.html$
+
+# Exclude Open Collective links
+https://opencollective.com/.*
+
+# Prevent netlify rate limit
+https://www.netlify.com/
+
+## Ignore temporaly sitemap
+https://expressjs.com/sitemap-index.xml
+
+# Ignore Coveralls links
+
+https://coveralls.io/-*
+
diff --git a/.npmrc b/.npmrc
new file mode 100644
index 0000000000..889a7ccb46
--- /dev/null
+++ b/.npmrc
@@ -0,0 +1,3 @@
+min-release-age=2
+ignore-scripts=true
+git=false
diff --git a/.nvmrc b/.nvmrc
new file mode 100644
index 0000000000..12fd1fc277
--- /dev/null
+++ b/.nvmrc
@@ -0,0 +1 @@
+24.13
diff --git a/.prettierignore b/.prettierignore
new file mode 100644
index 0000000000..1d644a224e
--- /dev/null
+++ b/.prettierignore
@@ -0,0 +1,6 @@
+dist/
+.astro/
+node_modules/
+package-lock.json
+pnpm-lock.yaml
+LICENSE.md
diff --git a/.prettierrc b/.prettierrc
new file mode 100644
index 0000000000..167200c363
--- /dev/null
+++ b/.prettierrc
@@ -0,0 +1,9 @@
+{
+  "semi": true,
+  "singleQuote": true,
+  "tabWidth": 2,
+  "useTabs": false,
+  "trailingComma": "es5",
+  "printWidth": 100,
+  "plugins": ["prettier-plugin-astro"]
+}
diff --git a/.ruby-version b/.ruby-version
deleted file mode 100644
index a0891f563f..0000000000
--- a/.ruby-version
+++ /dev/null
@@ -1 +0,0 @@
-3.3.4
diff --git a/.vscode/extensions.json b/.vscode/extensions.json
new file mode 100644
index 0000000000..e7b63ac2c7
--- /dev/null
+++ b/.vscode/extensions.json
@@ -0,0 +1,9 @@
+{
+  "recommendations": [
+    "astro-build.astro-vscode",
+    "esbenp.prettier-vscode",
+    "dbaeumer.vscode-eslint",
+    "unifiedjs.vscode-mdx"
+  ],
+  "unwantedRecommendations": []
+}
diff --git a/.vscode/launch.json b/.vscode/launch.json
new file mode 100644
index 0000000000..d642209762
--- /dev/null
+++ b/.vscode/launch.json
@@ -0,0 +1,11 @@
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "command": "./node_modules/.bin/astro dev",
+      "name": "Development server",
+      "request": "launch",
+      "type": "node-terminal"
+    }
+  ]
+}
diff --git a/.vscode/settings.json b/.vscode/settings.json
new file mode 100644
index 0000000000..c884b6db98
--- /dev/null
+++ b/.vscode/settings.json
@@ -0,0 +1,27 @@
+{
+  "prettier.enable": true,
+  "editor.formatOnSave": true,
+  "editor.defaultFormatter": "esbenp.prettier-vscode",
+  "files.associations": {
+    ".lycheeignore": "ignore"
+  },
+  "[ignore]": {
+    "editor.formatOnSave": false
+  },
+  "[astro]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[typescript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[json]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[css]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  }
+}
diff --git a/2x/applications.md b/2x/applications.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/applications.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/contrib.md b/2x/contrib.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/contrib.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/applications.md b/2x/docs/applications.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/applications.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/contrib.md b/2x/docs/contrib.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/contrib.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/executable.md b/2x/docs/executable.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/executable.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/guide.md b/2x/docs/guide.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/guide.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/index.md b/2x/docs/index.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/index.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/migrate.md b/2x/docs/migrate.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/migrate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/docs/screencasts.md b/2x/docs/screencasts.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/docs/screencasts.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/executable.md b/2x/executable.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/executable.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/guide.md b/2x/guide.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/guide.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/index.md b/2x/index.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/index.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/migrate.md b/2x/migrate.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/migrate.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/2x/screencasts.md b/2x/screencasts.md
deleted file mode 100644
index 8cf4321141..0000000000
--- a/2x/screencasts.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-sitemap: false
-redirect_to:
-  - https://github.com/expressjs/expressjs.com/tree/2x
----
\ No newline at end of file
diff --git a/404.md b/404.md
deleted file mode 100644
index 5bae9ef3f0..0000000000
--- a/404.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-layout: 404
-title: Page not found
-description: We couldn’t find the page you’re looking for.
-lang: en
----
-
-# {{ page.title }}
-
-We couldn’t find the page you’re looking for. Check the address or [head back home](/).
-
-If this is a mistake, [let us know](https://github.com/expressjs/expressjs.com/issues/new/), and we will try to fix it!
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f0b0a9ed9f..66ccf2f188 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,126 +1,141 @@
-# Contributing to Expressjs.com
-
-### The Official Documentation of the Express.js Framework
+# Contributing to the expressjs.com website
 
 This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
 
->[!NOTE]
-> This is not the repo for Express.js framework. To contribute to the _[Express.js framework](https://github.com/expressjs/express)_, check out the [GitHub repo contributing page](https://github.com/expressjs/express?tab=contributing-ov-file) or the website's [Contributing to Express](https://expressjs.com/en/resources/contributing.html) page.
+You can see the current [captains and committers](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md) of this project, and learn how to join through the [governance document](https://github.com/expressjs/discussions/blob/HEAD/docs/GOVERNANCE.md). Also review the [Express Collaborator Guide](https://github.com/expressjs/.github/blob/HEAD/CONTRIBUTING.md) for general contribution guidelines across Express.js projects.
 
+## Common Contributions
 
-#### Need some ideas? These are some typical issues.
+1. **Website Issues**: Improvements to the site's functionality, design, or accessibility.
+2. **Content Issues**: Fix anything related to site content or typos.
+3. **Translation Issues**: Fix translation errors or contribute new content. See the [i18n documentation](docs/i18n.md).
 
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-    - Display or screen sizing problems
-    - Mobile responsiveness issues
-    - Missing or broken accessibility features 
-    - Website outages
-    - Broken links
-    - Page structure or user interface enhancements
+## Working on Issues
 
-2. **Content Issues**: Fix anything related to site content or typos.
-    - Spelling errors
-    - Incorrect/outdated Express.js documentation
-    - Missing content
+We welcome contributions to existing bugs or enhancements. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Look for issues labeled `good first issue` or `help wanted` to get started.
 
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-    - Fix spelling errors 
-    - Fix incorrect/poorly translated words
-    - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
+If you have found a bug, a typo, or have an idea for an enhancement:
 
-#### Want to work on a backlog issue?
+- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) for larger proposals or to get feedback first.
+- Open a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) directly if the work is ready to go.
 
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
+> For significant changes, we encourage opening an issue first to discuss and align before starting work.
 
-#### Have an idea? Found a bug?
+## Getting Started
 
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first. 
+### Prerequisites
 
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
+This project uses:
 
-## Getting Started
+- **Astro** for site generation
+- **TypeScript** for type safety
+- **ESLint** for linting
+- **Prettier** for formatting
 
-The steps below will guide you through the Expressjs.com contribution process.
+Tooling required:
 
-#### Step 1: (OPTIONAL) Open a New Issue
-So you've found a problem that you want to fix, or have a site enhancement you want to make. 
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals. 
-    - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-    - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-    - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
+- **Node.js**: v24.x or higher
+- **npm**: v11.0.0 or higher (comes with Node 24)
 
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback. 
-    - For submissions proposing significant change, we encourage you to follow the review process before starting work. 
+> We recommend using [nvm](https://github.com/nvm-sh/nvm) to manage Node.js versions. This project includes an `.nvmrc` file for automatic version switching.
 
-#### Step 2: Get the Application Code Base
+### Setup
 
-Clone the repo and get the code:
+1. **Clone the repository:**
 
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
+   ```bash
+   git clone https://github.com/expressjs/expressjs.com.git
+   cd expressjs.com
+   ```
+
+2. **Install the correct Node.js version** (if using nvm):
+
+   ```bash
+   nvm install
+   nvm use
+   ```
+
+3. **Install dependencies:**
+
+   ```bash
+   npm install
+   ```
 
-After you've got the code you're ready to start making your changes! 
+4. **Start the development server:**
 
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.  
+   ```bash
+   npm run dev
+   ```
 
-**Markdown Page Files**: 
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup. 
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example. 
+   The site will be available at `http://localhost:4321`
 
-**Includes Partials and Layout Templates**
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages. 
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
+### Available Scripts
 
-**Blog Markdown Files**
-- These files make up the individual blog posts. If you want to contribute a blog post please
-follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory. 
+| Command            | Description                               |
+| ------------------ | ----------------------------------------- |
+| `npm run dev`      | Start development server with hot reload  |
+| `npm run build`    | Build production site to `./dist`         |
+| `npm run preview`  | Preview production build locally          |
+| `npm run lint`     | Run ESLint to check for issues            |
+| `npm run check`    | Run type checking and format verification |
+| `npm run test:e2e` | Run Playwright E2E tests                  |
 
-**CSS or Javascript**
-- All css and js files are kept in `css` and `js` folders on the project root.
+## Submitting a Pull Request
 
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
+1. Create a new branch from `main`.
+2. Make your changes.
+3. Run `npm run check` to verify code style and types.
+4. Run `npm run test:e2e` to ensure your changes don't break existing functionality.
+5. Commit with a clear message.
+6. Push to your fork.
+7. Open a PR against `main`.
 
-#### Step 3: Running the Application
+> Ensure all checks pass and your branch is up to date with `main` before opening a PR.
 
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options. 
+## Testing
 
->[!NOTE]
->If you're only making changes to the content, you most likely won't need to run the site locally.
+We use **Playwright** for End-to-End (E2E) testing. All PRs are automatically tested against a Netlify Preview deployment before they can be merged.
 
-1. __Run Locally__: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.  
-    - This is the recommended option for moderate to complex work. 
+### Prerequisites
 
-2. __Run using Deploy Preview__: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/). 
-    1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a *draft* pull request. 
-    2. After the build steps are complete, you'll have access to a __Deploy Preview__ tab that will run your changes on the web, rebuilding after each commit is pushed. 
-    3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-  
-## Contributing translations
+Before running E2E tests for the first time, you need to install the browser binaries:
 
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
+```bash
+npx playwright install --with-deps
+```
+
+### Running Tests Locally
+
+You can run the full test suite against your local development server:
+
+1. In one terminal, start the site: `npm run dev`
+2. In another terminal, run the tests: `npm run test:e2e`
+
+### Writing Stable Tests
 
-The documentation is translated into these languages:
+When adding new tests or modifying components, please follow these stability guidelines:
+
+1. **Avoid CSS Classes**: Do not use CSS classes (e.g., `.hero__content`) for locators, as they are fragile and change during refactoring.
+2. **Use data-testid**: Add `data-testid` attributes to components for stable targeting (e.g., `<div data-testid="my-component">`).
+3. **User-Visible Locators**: Prefer semantic locators like `getByRole`, `getByText`, or `getByAltText` over IDs when possible.
+
+Example:
+
+```typescript
+// Good: Stable and accessible
+const logo = page.getByAltText('Express.js logo');
+const section = page.getByTestId('features-section');
+
+// Bad: Fragile
+const logo = page.locator('.hero__logo');
+```
 
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
+## Further Documentation
 
-### How to translate
+For more detailed documentation about the project, see the [`docs/`](docs/) folder:
 
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
+- [Project Structure](docs/project-structure.md) — Architecture, folder layout, and framework policy
+- [Content](docs/content.md) — Collections, frontmatter, versioning, and global pages
+- [Configuration](docs/configuration.md) — Navigation menus, announcement bar, and version-specific items
+- [Internationalization](docs/i18n.md) — Translations, Crowdin integration, and adding languages
+- [Design System](docs/design-system.md) — Components, tokens, colors, typography, and breakpoints
diff --git a/Dockerfile b/Dockerfile
deleted file mode 100644
index 30849ade23..0000000000
--- a/Dockerfile
+++ /dev/null
@@ -1,27 +0,0 @@
-# Match GitHub Pages Ruby version (see https://pages.github.com/versions)
-FROM ruby:3.3.4@sha256:d4233f4242ea25346f157709bb8417c615e7478468e2699c8e86a4e1f0156de8
-
-# Install Jekyll and Bundler
-RUN gem install jekyll bundler
-
-# Set the working directory
-WORKDIR /usr/src/app
-
-# Change the permissions of the working directory
-RUN chmod 777 /usr/src/app
-
-# Copy the Gemfile into the image
-COPY Gemfile ./
-COPY Gemfile.lock ./
-
-# Install the gems
-RUN bundle install --no-cache
-
-# Copy the rest of the project into the image
-COPY . .
-
-# Expose the port Jekyll will run on
-EXPOSE 4000
-
-# The default command to run Jekyll
-CMD ["jekyll", "serve", "--host", "0.0.0.0", "--livereload"]
diff --git a/Gemfile b/Gemfile
deleted file mode 100644
index 05b6322344..0000000000
--- a/Gemfile
+++ /dev/null
@@ -1,5 +0,0 @@
-source 'https://rubygems.org'
-
-gem 'github-pages', group: :jekyll_plugins
-gem 'webrick'
-gem 'jekyll-github-metadata'
\ No newline at end of file
diff --git a/Gemfile.lock b/Gemfile.lock
deleted file mode 100644
index fbc4706791..0000000000
--- a/Gemfile.lock
+++ /dev/null
@@ -1,282 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    activesupport (7.2.1)
-      base64
-      bigdecimal
-      concurrent-ruby (~> 1.0, >= 1.3.1)
-      connection_pool (>= 2.2.5)
-      drb
-      i18n (>= 1.6, < 2)
-      logger (>= 1.4.2)
-      minitest (>= 5.1)
-      securerandom (>= 0.3)
-      tzinfo (~> 2.0, >= 2.0.5)
-    addressable (2.8.7)
-      public_suffix (>= 2.0.2, < 7.0)
-    base64 (0.2.0)
-    bigdecimal (3.1.8)
-    coffee-script (2.4.1)
-      coffee-script-source
-      execjs
-    coffee-script-source (1.12.2)
-    colorator (1.1.0)
-    commonmarker (0.23.10)
-    concurrent-ruby (1.3.4)
-    connection_pool (2.4.1)
-    csv (3.3.0)
-    dnsruby (1.72.2)
-      simpleidn (~> 0.2.1)
-    drb (2.2.1)
-    em-websocket (0.5.3)
-      eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0)
-    ethon (0.16.0)
-      ffi (>= 1.15.0)
-    eventmachine (1.2.7)
-    execjs (2.9.1)
-    faraday (2.14.1)
-      faraday-net_http (>= 2.0, < 3.5)
-      json
-      logger
-    faraday-net_http (3.4.2)
-      net-http (~> 0.5)
-    ffi (1.17.0-x64-mingw-ucrt)
-    ffi (1.17.0-x86_64-linux-gnu)
-    forwardable-extended (2.6.0)
-    gemoji (4.1.0)
-    github-pages (232)
-      github-pages-health-check (= 1.18.2)
-      jekyll (= 3.10.0)
-      jekyll-avatar (= 0.8.0)
-      jekyll-coffeescript (= 1.2.2)
-      jekyll-commonmark-ghpages (= 0.5.1)
-      jekyll-default-layout (= 0.1.5)
-      jekyll-feed (= 0.17.0)
-      jekyll-gist (= 1.5.0)
-      jekyll-github-metadata (= 2.16.1)
-      jekyll-include-cache (= 0.2.1)
-      jekyll-mentions (= 1.6.0)
-      jekyll-optional-front-matter (= 0.3.2)
-      jekyll-paginate (= 1.1.0)
-      jekyll-readme-index (= 0.3.0)
-      jekyll-redirect-from (= 0.16.0)
-      jekyll-relative-links (= 0.6.1)
-      jekyll-remote-theme (= 0.4.3)
-      jekyll-sass-converter (= 1.5.2)
-      jekyll-seo-tag (= 2.8.0)
-      jekyll-sitemap (= 1.4.0)
-      jekyll-swiss (= 1.0.0)
-      jekyll-theme-architect (= 0.2.0)
-      jekyll-theme-cayman (= 0.2.0)
-      jekyll-theme-dinky (= 0.2.0)
-      jekyll-theme-hacker (= 0.2.0)
-      jekyll-theme-leap-day (= 0.2.0)
-      jekyll-theme-merlot (= 0.2.0)
-      jekyll-theme-midnight (= 0.2.0)
-      jekyll-theme-minimal (= 0.2.0)
-      jekyll-theme-modernist (= 0.2.0)
-      jekyll-theme-primer (= 0.6.0)
-      jekyll-theme-slate (= 0.2.0)
-      jekyll-theme-tactile (= 0.2.0)
-      jekyll-theme-time-machine (= 0.2.0)
-      jekyll-titles-from-headings (= 0.5.3)
-      jemoji (= 0.13.0)
-      kramdown (= 2.4.0)
-      kramdown-parser-gfm (= 1.1.0)
-      liquid (= 4.0.4)
-      mercenary (~> 0.3)
-      minima (= 2.5.1)
-      nokogiri (>= 1.16.2, < 2.0)
-      rouge (= 3.30.0)
-      terminal-table (~> 1.4)
-      webrick (~> 1.8)
-    github-pages-health-check (1.18.2)
-      addressable (~> 2.3)
-      dnsruby (~> 1.60)
-      octokit (>= 4, < 8)
-      public_suffix (>= 3.0, < 6.0)
-      typhoeus (~> 1.3)
-    html-pipeline (2.14.3)
-      activesupport (>= 2)
-      nokogiri (>= 1.4)
-    http_parser.rb (0.8.0)
-    i18n (1.14.6)
-      concurrent-ruby (~> 1.0)
-    jekyll (3.10.0)
-      addressable (~> 2.4)
-      colorator (~> 1.0)
-      csv (~> 3.0)
-      em-websocket (~> 0.5)
-      i18n (>= 0.7, < 2)
-      jekyll-sass-converter (~> 1.0)
-      jekyll-watch (~> 2.0)
-      kramdown (>= 1.17, < 3)
-      liquid (~> 4.0)
-      mercenary (~> 0.3.3)
-      pathutil (~> 0.9)
-      rouge (>= 1.7, < 4)
-      safe_yaml (~> 1.0)
-      webrick (>= 1.0)
-    jekyll-avatar (0.8.0)
-      jekyll (>= 3.0, < 5.0)
-    jekyll-coffeescript (1.2.2)
-      coffee-script (~> 2.2)
-      coffee-script-source (~> 1.12)
-    jekyll-commonmark (1.4.0)
-      commonmarker (~> 0.22)
-    jekyll-commonmark-ghpages (0.5.1)
-      commonmarker (>= 0.23.7, < 1.1.0)
-      jekyll (>= 3.9, < 4.0)
-      jekyll-commonmark (~> 1.4.0)
-      rouge (>= 2.0, < 5.0)
-    jekyll-default-layout (0.1.5)
-      jekyll (>= 3.0, < 5.0)
-    jekyll-feed (0.17.0)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-gist (1.5.0)
-      octokit (~> 4.2)
-    jekyll-github-metadata (2.16.1)
-      jekyll (>= 3.4, < 5.0)
-      octokit (>= 4, < 7, != 4.4.0)
-    jekyll-include-cache (0.2.1)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-mentions (1.6.0)
-      html-pipeline (~> 2.3)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-optional-front-matter (0.3.2)
-      jekyll (>= 3.0, < 5.0)
-    jekyll-paginate (1.1.0)
-    jekyll-readme-index (0.3.0)
-      jekyll (>= 3.0, < 5.0)
-    jekyll-redirect-from (0.16.0)
-      jekyll (>= 3.3, < 5.0)
-    jekyll-relative-links (0.6.1)
-      jekyll (>= 3.3, < 5.0)
-    jekyll-remote-theme (0.4.3)
-      addressable (~> 2.0)
-      jekyll (>= 3.5, < 5.0)
-      jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0)
-      rubyzip (>= 1.3.0, < 3.0)
-    jekyll-sass-converter (1.5.2)
-      sass (~> 3.4)
-    jekyll-seo-tag (2.8.0)
-      jekyll (>= 3.8, < 5.0)
-    jekyll-sitemap (1.4.0)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-swiss (1.0.0)
-    jekyll-theme-architect (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-cayman (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-dinky (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-hacker (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-leap-day (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-merlot (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-midnight (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-minimal (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-modernist (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-primer (0.6.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-github-metadata (~> 2.9)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-slate (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-tactile (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-theme-time-machine (0.2.0)
-      jekyll (> 3.5, < 5.0)
-      jekyll-seo-tag (~> 2.0)
-    jekyll-titles-from-headings (0.5.3)
-      jekyll (>= 3.3, < 5.0)
-    jekyll-watch (2.2.1)
-      listen (~> 3.0)
-    jemoji (0.13.0)
-      gemoji (>= 3, < 5)
-      html-pipeline (~> 2.2)
-      jekyll (>= 3.0, < 5.0)
-    json (2.19.2)
-    kramdown (2.4.0)
-      rexml
-    kramdown-parser-gfm (1.1.0)
-      kramdown (~> 2.0)
-    liquid (4.0.4)
-    listen (3.9.0)
-      rb-fsevent (~> 0.10, >= 0.10.3)
-      rb-inotify (~> 0.9, >= 0.9.10)
-    logger (1.7.0)
-    mercenary (0.3.6)
-    minima (2.5.1)
-      jekyll (>= 3.5, < 5.0)
-      jekyll-feed (~> 0.9)
-      jekyll-seo-tag (~> 2.1)
-    minitest (5.25.1)
-    net-http (0.9.1)
-      uri (>= 0.11.1)
-    nokogiri (1.19.1-x64-mingw-ucrt)
-      racc (~> 1.4)
-    nokogiri (1.19.1-x86_64-linux-gnu)
-      racc (~> 1.4)
-    octokit (4.25.1)
-      faraday (>= 1, < 3)
-      sawyer (~> 0.9)
-    pathutil (0.16.2)
-      forwardable-extended (~> 2.6)
-    public_suffix (5.1.1)
-    racc (1.8.1)
-    rb-fsevent (0.11.2)
-    rb-inotify (0.11.1)
-      ffi (~> 1.0)
-    rexml (3.4.2)
-    rouge (3.30.0)
-    rubyzip (2.3.2)
-    safe_yaml (1.0.5)
-    sass (3.7.4)
-      sass-listen (~> 4.0.0)
-    sass-listen (4.0.0)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-    sawyer (0.9.2)
-      addressable (>= 2.3.5)
-      faraday (>= 0.17.3, < 3)
-    securerandom (0.3.1)
-    simpleidn (0.2.3)
-    terminal-table (1.8.0)
-      unicode-display_width (~> 1.1, >= 1.1.1)
-    typhoeus (1.4.1)
-      ethon (>= 0.9.0)
-    tzinfo (2.0.6)
-      concurrent-ruby (~> 1.0)
-    unicode-display_width (1.8.0)
-    uri (1.1.1)
-    webrick (1.9.2)
-
-PLATFORMS
-  x64-mingw-ucrt
-  x86_64-linux
-
-DEPENDENCIES
-  github-pages
-  jekyll-github-metadata
-  webrick
-
-BUNDLED WITH
-   2.5.16
\ No newline at end of file
diff --git a/Makefile b/Makefile
deleted file mode 100644
index ff2008ed7e..0000000000
--- a/Makefile
+++ /dev/null
@@ -1,27 +0,0 @@
-GREEN := \033[1;32m
-BLUE := \033[1;34m
-RESET := \033[0m
-
-# The directory of this file
-DIR := $(shell echo $(shell cd "$(shell dirname "${BASH_SOURCE[0]}" )" && pwd ))
-
-# This will output the help for each task
-# thanks to https://marmelab.com/blog/2016/02/29/auto-documented-makefile.html
-.PHONY: help
-
-help: ## This help
-	@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {printf "${GREEN}%-30s${RESET} %s\n", $$1, $$2}' $(MAKEFILE_LIST)
-
-.DEFAULT_GOAL := help
-
-serve: ## Local server
-	@echo "${BLUE}Starting expressjs.com at http://localhost:4000${RESET}"
-	docker run -p 4000:4000 -p 35729:35729 -v $(DIR):/usr/src/app expressjs.com bundle exec jekyll serve --host 0.0.0.0
-
-build: ## Build site
-	@echo "${BLUE}Building site...${RESET}"
-	docker build -t expressjs.com .
-
-clean: ## Clean up
-	@echo "${BLUE}Clean up...${RESET}"
-	docker rmi expressjs.com
diff --git a/README.md b/README.md
index a483423508..73fdf5253b 100644
--- a/README.md
+++ b/README.md
@@ -1,63 +1,42 @@
-# expressjs.com
+<p align="center">
+  <a href="https://expressjs.com">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="public/images/logos/logo-express-white.svg">
+      <img src="public/images/logos/logo-express-black.svg" alt="Express.js" width="280">
+    </picture>
+  </a>
+</p>
 
-This is the repository of the website [expressjs.com](https://expressjs.com). It is hosted directly from the repository as a [GitHub Pages](https://pages.github.com/) website.
+<p align="center">
+  The official website and documentation for <a href="https://expressjs.com">Express.js</a>, the fast, unopinionated, minimalist web framework for Node.js.
+</p>
 
-## Contributing
-
-Any person who wants to contribute to the Website is welcome! Please read [Contributors' Guide](CONTRIBUTING.md) for more information on contributing to the Express.js documentation.
-
-## Translations
-
-If you're interested in contributing to the site's translations, you can find more information [here](https://github.com/expressjs/expressjs.com/blob/gh-pages/CONTRIBUTING.md#contributing-translations).
-
-## Build the website locally
-
->[!NOTE]
->If you're only making changes to the content, you most likely won't need to run the site locally.
-
-To preview the website locally, we have two options: using Docker or using Bundler.
+<p align="center">
+  <a href="https://expressjs.com">Website</a> ·
+  <a href="https://github.com/expressjs/expressjs.com/issues">Report Issue</a> ·
+  <a href="CONTRIBUTING.md">Contributing Guide</a>
+</p>
 
-### Using Docker
+---
 
->[!TIP]
-> You can run `make help` to obtain detailed information on how to use our make commands.
+## Getting started
 
-1. Ensure that you have Docker and Make installed.
-1. Run `make build` to build the project.
-1. Run `make serve` to serve the project, this include live reloading so any change will be reflected (it can take a while, check the logs).
-1. Run `make clean` to remove the docker images and resources generated.
+The site is built with [Astro](https://astro.build), TypeScript, and MDX.
 
-### Using Bundle
+**Prerequisites:** Node.js >= 24.13.0 and npm >= 11.0.0
 
-1. Install [Ruby and Bundler](https://help.github.com/articles/setting-up-your-pages-site-locally-with-jekyll/) if you don't have them already.
+```bash
+npm install
+npm run dev
+```
 
-1. Install the [jekyll-redirect-from](https://github.com/jekyll/jekyll-redirect-from) gem:
+The development server listens at `http://localhost:4321`.
 
-   ```sh
-   $ gem install jekyll-redirect-from
-   ```
-   
-1. Clone this repository by running the following command:
-
-   ```sh
-   $ git clone https://github.com/expressjs/expressjs.com.git
-   ```
-
-1. Navigate to the cloned repository directory and run the following command:
-
-   ```sh
-   $ bundle install
-   ```
-
-   Bundler will look in the Gemfile for which gems to install. The `github-pages` gem includes the same version of Jekyll and other dependencies as used by GitHub Pages, so that your local setup mirrors GitHub Pages as closely as possible.
-
-1. Run Jekyll using the following command:
+## Contributing
 
-   ```sh
-   $ bundle exec jekyll serve
-   ```
+This project welcomes contributors of all experience levels. Whether it's fixing a typo, improving documentation, translating content, or enhancing the website, every contribution matters.
 
-   Then, load <http://localhost:4000> in your browser.
+Please read the [Contributing Guide](CONTRIBUTING.md) and the [Express Collaborator Guide](https://github.com/expressjs/.github/blob/master/CONTRIBUTING.md) before opening a pull request.
 
 ## License
 
diff --git a/_config.yml b/_config.yml
deleted file mode 100644
index 5abcc77f71..0000000000
--- a/_config.yml
+++ /dev/null
@@ -1,110 +0,0 @@
-url: "https://expressjs.com"
-baseurl: "/"
-
-repository: expressjs/expressjs.com
-
-# Site settings
-
-defaults:
-  -
-    scope:
-      path: "_posts" 
-      type: "posts"
-    values:
-      layout: "post"
-      menu: blog
-      lang: en
-  -
-    scope:
-      path: "en"
-    values:
-      lang: en
-  - 
-    scope:
-      path: "index.md"
-    values:
-      lang: en
-  -
-    scope:
-      path: "de"
-    values:
-      lang: de
-  -
-    scope:
-      path: "es"
-    values:
-      lang: es
-  -
-    scope:
-      path: "fr"
-    values:
-      lang: fr
-  -
-    scope:
-      path: "it"
-    values:
-      lang: it
-  -
-    scope:
-      path: "ja"
-    values:
-      lang: ja
-  -
-    scope:
-      path: "ko"
-    values:
-      lang: ko
-  -
-    scope:
-      path: "pt-br"
-    values: 
-      lang: "pt-br"  
-  -
-    scope:
-      path: "zh-cn"
-    values: 
-      lang: "zh-cn"
-  -
-    scope:
-      path: "zh-tw"
-    values:
-      lang: "zh-tw"
-
-announcement: true # Enable or disable the announcements.
-
-collections:
-  starter:
-    output: true
-    sort_by: order
-  guide:
-    output: true
-    sort_by: order
-  advanced:
-    output: true
-    sort_by: order
-  resources:
-    output: true
-    sort_by: order
-
-# Build settings
-
-plugins:
-  - jekyll-redirect-from
-  - jekyll-github-metadata
-
-highlighter: rouge
-# library used for syntax highlighting
-
-markdown: kramdown
-kramdown:
- math_engine: mathjax
- input: GFM
- hard_wrap: false
- syntax_highlighter: rouge
-
-exclude:
-  - [uk/CHANGELOG.md]
-  - vendor/bundle
-  - node_modules/
-
-include: [".well-known"]
\ No newline at end of file
diff --git a/_data/de/footer.yml b/_data/de/footer.yml
deleted file mode 100644
index f4e60d8a38..0000000000
--- a/_data/de/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Nutzungsbedingungen
-privacy_policy: Datenschutzerklärung
-coc: Verhaltenskodex
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: Lizenzvertrag
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/de/general.yml b/_data/de/general.yml
deleted file mode 100644
index 16bd945615..0000000000
--- a/_data/de/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warnung'
-note: 'Hinweis'
-caution: 'Vorsicht'
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
diff --git a/_data/de/menu.yml b/_data/de/menu.yml
deleted file mode 100644
index 8d331e5ea0..0000000000
--- a/_data/de/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: Einführung
-installing: Installation
-hello_world: Hello world
-generator: Express generator
-basic_routing: Basisrouting
-static_files: Statische Dateien
-examples: Weitere Beispiele
-faq: Häufig gestellte Fragen
-# Guide
-guide: Leitfaden
-routing: Weiterleitung (Routing)
-writing_middleware: Middleware schreiben
-using_middleware: Middleware verwenden
-overriding_express_api: Overriding the Express API
-using_template_engines: Template-Engines verwenden
-error_handling: Fehlerbehandlung
-debugging: Debugging
-behind_proxies: Express hinter Proxys
-migrating_4: Wechsel zu Express 4
-migrating_5: Wechsel zu Express 5
-database_integration: Datenbankintegration
-# API reference
-api: API-Referenz
-5x: 5.x
-4x: 4.x
-3x: 3.x (veraltet)
-2x: 2.x (veraltet)
-# Advanced topics
-advanced: Themen für Fortgeschrittene
-developing_template_engines: Template-Engines
-security_updates: Sicherheitsupdates
-best_practice_security: Sicherheitsspezifische Best Practices
-best_practice_performance: Leistungsspezifische Best Practices
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: Ressourcen
-glossary: Glossar
-middleware: Middleware
-community: Community
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/docsearch.yml b/_data/docsearch.yml
deleted file mode 100644
index e60470dcaa..0000000000
--- a/_data/docsearch.yml
+++ /dev/null
@@ -1,3 +0,0 @@
-# config: https://github.com/algolia/docsearch-configs/blob/master/configs/expressjs.json
-apiKey: 7164e33055faa6ecddefd9e08fc59f5d
-indexName: expressjs
diff --git a/_data/en/footer.yml b/_data/en/footer.yml
deleted file mode 100644
index c68d10357e..0000000000
--- a/_data/en/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Terms of Use
-privacy_policy: Privacy Policy
-coc: Code of Conduct
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: License
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/en/general.yml b/_data/en/general.yml
deleted file mode 100644
index aab9e75f2a..0000000000
--- a/_data/en/general.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
-  
\ No newline at end of file
diff --git a/_data/en/menu.yml b/_data/en/menu.yml
deleted file mode 100644
index de6f851575..0000000000
--- a/_data/en/menu.yml
+++ /dev/null
@@ -1,57 +0,0 @@
-# Getting started
-getting_started: Getting started
-installing: Installing
-hello_world: Hello world
-generator: Express generator
-basic_routing: Basic routing
-static_files: Static files
-examples: More examples
-faq: FAQ
-
-# Guide
-guide: Guide
-routing: Routing
-writing_middleware: Writing middleware
-using_middleware: Using middleware
-overriding_express_api: Overriding the Express API
-using_template_engines: Using template engines
-error_handling: Error handling
-debugging: Debugging
-behind_proxies: Express behind proxies
-migrating_4: Moving to Express 4
-migrating_5: Moving to Express 5
-database_integration: Database integration
-
-# API reference
-
-api: API reference
-5x: 5.x
-4x: 4.x
-3x: 3.x (deprecated)
-2x: 2.x (deprecated)
-
-# Advanced topics
-advanced: Advanced topics
-developing_template_engines: Building template engines
-security_updates: Security updates
-best_practice_security: Security best practices
-best_practice_performance: Performance best practices
-healthcheck_graceful_shutdown: Health checks & shutdown
-
-# Resources
-resources: Resources
-glossary: Glossary
-middleware: Middleware
-community: Community
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-
-# Support
-support: Support
-
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/es/footer.yml b/_data/es/footer.yml
deleted file mode 100644
index dd8ecfdd76..0000000000
--- a/_data/es/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Condiciones de uso
-privacy_policy: Política de privacidad
-coc: Código de conducta
-trademark_policy: Política de marcas registradas
-security_policy: Política de seguridad
-license: Licencia
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/es/general.yml b/_data/es/general.yml
deleted file mode 100644
index 73f03efc21..0000000000
--- a/_data/es/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Ahora la versión por defecto en npm con cronograma LTS"
-body_announcement: "Express 5.1.0 es ahora es la versión predeterminada en npm, y estamos introduciendo un cronograma oficial de LTS para las líneas de lanzamiento v4 y v5. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Mira nuestro último blog para más información.</a>"
-community-caveat-alert: "Esta información se refiere a sitios, productos o módulos de terceros que no son mantenidos por el equipo de Expressjs. La lista aquí no constituye un respaldo o una recomendación del equipo del proyecto Expressjs."
-warning: 'Advertencia'
-note: 'Nota'
-caution: 'Precaución'
-i18n_notice: "Este documento puede estar desactualizado en relación con la documentación en inglés. Para las últimas actualizaciones, por favor consulte la"
-i18n_notice_link_text: "documentación en inglés"
diff --git a/_data/es/menu.yml b/_data/es/menu.yml
deleted file mode 100644
index ab87295269..0000000000
--- a/_data/es/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: Cómo empezar
-installing: Instalando
-hello_world: Hola mundo
-generator: Generador express
-basic_routing: Direccionamiento básico
-static_files: Archivos estáticos
-examples: Más ejemplos
-faq: FAQ
-# Guide
-guide: Guía
-routing: Direccionamiento
-writing_middleware: Escritura de middleware
-using_middleware: Utilización del middleware
-overriding_express_api: Overriding the Express API
-using_template_engines: Utilización de motores de plantilla
-error_handling: Manejo de errores
-debugging: Depuración
-behind_proxies: Express detrás de proxies
-migrating_4: Migración a Express 4
-migrating_5: Migración a Express 5
-database_integration: Integración de la base de datos
-# API reference
-api: Referencia de API
-5x: 5.x
-4x: 4.x
-3x: 3.x (obsoleto)
-2x: 2.x (obsoleto)
-# Advanced topics
-advanced: Temas avanzados
-developing_template_engines: Motores de plantilla
-security_updates: Actualizaciones de seguridad
-best_practice_security: Mejores prácticas de seguridad
-best_practice_performance: Mejores prácticas de rendimiento
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: Recursos
-glossary: Glosario
-middleware: Middleware
-community: Comunidad
-utils: Utility modules
-contributing: Contribuir a Express
-changelog: Release Change Log
-# Support
-support: Soporte
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Escribir un post
diff --git a/_data/express.yml b/_data/express.yml
deleted file mode 100644
index 0a6a4d6c0b..0000000000
--- a/_data/express.yml
+++ /dev/null
@@ -1,2 +0,0 @@
-current_version: "5.2.1"
-next_version: "undefined"
\ No newline at end of file
diff --git a/_data/fr/footer.yml b/_data/fr/footer.yml
deleted file mode 100644
index 6b2eb659c0..0000000000
--- a/_data/fr/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Conditions d’utilisation
-privacy_policy: Politique de Confidentialité
-coc: Code de Conduite
-trademark_policy: Politique de Marque
-security_policy: Politique de Sécurité
-license: Licence
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/fr/general.yml b/_data/fr/general.yml
deleted file mode 100644
index e6327e6214..0000000000
--- a/_data/fr/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
diff --git a/_data/fr/menu.yml b/_data/fr/menu.yml
deleted file mode 100644
index 04c8944bcb..0000000000
--- a/_data/fr/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: Mise en route
-installing: Installation
-hello_world: Hello world
-generator: Générateur Express
-basic_routing: Routage de base
-static_files: Fichiers statiques
-examples: More examples
-faq: FAQ
-# Guide
-guide: Guide
-routing: Routage
-writing_middleware: Ecriture de middleware
-using_middleware: Utilisation de middleware
-overriding_express_api: Overriding the Express API
-using_template_engines: Utilisation de moteurs de modèles
-error_handling: Traitement d'erreurs
-debugging: Débogage
-behind_proxies: Express derrière Proxys
-migrating_4: Migration vers Express 4
-migrating_5: Migration vers Express 5
-database_integration: Intégration de bases de données
-# API reference
-api: API reference
-5x: 5.x
-4x: 4.x
-3x: 3.x (obsolète)
-2x: 2.x (obsolète)
-# Advanced topics
-advanced: Rubriques avancées
-developing_template_engines: Moteurs de modèles
-security_updates: Mises à jour de sécurité
-best_practice_security: Meilleures pratiques en termes de sécurité
-best_practice_performance: Meilleures pratiques en termes de performances
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: Ressources
-glossary: Glossaire
-middleware: Middleware
-community: Communauté
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/it/footer.yml b/_data/it/footer.yml
deleted file mode 100644
index c68d10357e..0000000000
--- a/_data/it/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Terms of Use
-privacy_policy: Privacy Policy
-coc: Code of Conduct
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: License
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/it/general.yml b/_data/it/general.yml
deleted file mode 100644
index e6327e6214..0000000000
--- a/_data/it/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
diff --git a/_data/it/menu.yml b/_data/it/menu.yml
deleted file mode 100644
index a8243191f0..0000000000
--- a/_data/it/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: Introduzione
-installing: Installazione
-hello_world: Hello world
-generator: Programma di creazione Express
-basic_routing: Routing di base
-static_files: File statici
-examples: More examples
-faq: FAQ
-# Guide
-guide: Guide
-routing: Routing
-writing_middleware: Scrittura del middleware
-using_middleware: Utilizzo del middleware
-overriding_express_api: Overriding the Express API
-using_template_engines: Utilizzo dei motori di template
-error_handling: Gestione degli errori
-debugging: Debugging
-behind_proxies: Express con i proxy
-migrating_4: Passaggio a Express 4
-migrating_5: Passaggio a Express 5
-database_integration: Integrazione database
-# API reference
-api: Riferimento API
-5x: 5.x
-4x: 4.x
-3x: 3.x (deprecato)
-2x: 2.x (deprecato)
-# Advanced topics
-advanced: Argomenti avanzati
-developing_template_engines: Motori di template
-security_updates: Aggiornamenti sulla sicurezza
-best_practice_security: Best practice sulla sicurezza
-best_practice_performance: Best practice sulle prestazioni
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: Risorse
-glossary: Glossario
-middleware: Middleware
-community: Community
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/ja/footer.yml b/_data/ja/footer.yml
deleted file mode 100644
index c68d10357e..0000000000
--- a/_data/ja/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Terms of Use
-privacy_policy: Privacy Policy
-coc: Code of Conduct
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: License
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/ja/general.yml b/_data/ja/general.yml
deleted file mode 100644
index 41323937a4..0000000000
--- a/_data/ja/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: LTSタイムラインでnpmのデフォルトになりました"
-body_announcement: "Express 5.1.0 が npm のデフォルトとなり、v4 および v5 リリース ラインの公式 LTS スケジュールが導入されます。<a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>詳細については、最新のブログをご覧ください。</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-i18n_notice: "このドキュメントは英語のドキュメントに比べて古くなっている可能性があります。最新情報については、"
-i18n_notice_link_text: "英語のドキュメントを参照してください"
diff --git a/_data/ja/menu.yml b/_data/ja/menu.yml
deleted file mode 100644
index 6fe5206dd6..0000000000
--- a/_data/ja/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: 概説
-installing: インストール
-hello_world: Hello world
-generator: Express ジェネレーター
-basic_routing: 基本的なルーティング
-static_files: 静的ファイル
-examples: More examples
-faq: FAQ
-# Guide
-guide: ガイド
-routing: ルーティング
-writing_middleware: ミドルウェアの作成
-using_middleware: ミドルウェアの使用
-overriding_express_api: Overriding the Express API
-using_template_engines: テンプレート・エンジンの使用
-error_handling: エラー処理
-debugging: デバッグ
-behind_proxies: プロキシーの背後の Express
-migrating_4: Express 4 への移行
-migrating_5: Express 5 への移行
-database_integration: データベースの統合
-# API reference
-api: API リファレンス
-5x: 5.x
-4x: 4.x
-3x: 3.x (非推奨)
-2x: 2.x (非推奨)
-# Advanced topics
-advanced: 高度なトピック
-developing_template_engines: テンプレート・エンジン
-security_updates: セキュリティー更新
-best_practice_security: セキュリティーに関するベスト・プラクティス
-best_practice_performance: パフォーマンスに関するベスト・プラクティス
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: リソース
-glossary: 用語集
-middleware: ミドルウェア
-community: コミュニティー
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/ko/footer.yml b/_data/ko/footer.yml
deleted file mode 100644
index 93c6b42142..0000000000
--- a/_data/ko/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: 이용 약관
-privacy_policy: 개인정보보호정책
-coc: 운영 규정
-trademark_policy: 상표 정책
-security_policy: 보안 정책
-license: 라이선스
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/ko/general.yml b/_data/ko/general.yml
deleted file mode 100644
index a1fd55a3c7..0000000000
--- a/_data/ko/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: npm에서 기본 버전으로 채택, LTS 일정 함께 도입됨"
-body_announcement: "이제 Express 5.1.0이 npm에서 기본 버전이 되었으며, v4와 v5 릴리스 라인에 대해 공식적인 LTS 일정도 도입했습니다.\n<a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>자세한 내용은 최신 블로그를 확인해보세요.</a>"
-community-caveat-alert: "이 정보는 Expressjs 팀에서 관리하지 않는 서드파티 사이트, 제품 또는 모듈에 관한 것입니다. 여기에 나열된다고 해서 Expressjs 프로젝트 팀이 이를 보증하거나 추천한다는 의미는 아닙니다."
-warning: '경고'
-note: '참고'
-caution: '주의'
-i18n_notice: "이 문서는 영어 문서에 비해 최신 정보가 아닐 수 있습니다. 최신 내용을 확인하려면 아래의 영어 문서를 참고해 주시기 바랍니다"
-i18n_notice_link_text: "영어로 된 문서"
diff --git a/_data/ko/menu.yml b/_data/ko/menu.yml
deleted file mode 100644
index c5469f8c10..0000000000
--- a/_data/ko/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: 시작하기
-installing: 설치
-hello_world: Hello world
-generator: Express 생성기
-basic_routing: 기본 라우팅
-static_files: 정적 파일
-examples: 더 많은 예시
-faq: 자주 묻는 질문(FAQ)
-# Guide
-guide: 안내서
-routing: 라우팅
-writing_middleware: 미들웨어 작성
-using_middleware: 미들웨어 사용
-overriding_express_api: Express API 오버라이딩
-using_template_engines: 템플리트 엔진 사용
-error_handling: 오류 처리
-debugging: 디버깅
-behind_proxies: 프록시 환경에서 Express 사용
-migrating_4: Express 4로의 이전
-migrating_5: Express 5로의 이전
-database_integration: 데이터베이스 통합
-# API reference
-api: API 참조
-5x: 5.x
-4x: 4.x
-3x: 3.x(더 이상 사용되지 않음)
-2x: 2.x(더 이상 사용되지 않음)
-# Advanced topics
-advanced: 고급 주제
-developing_template_engines: 템플리트 엔진
-security_updates: 보안 업데이트
-best_practice_security: 보안 우수 사례
-best_practice_performance: 성능 우수 사례
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: 자원
-glossary: 용어집
-middleware: 미들웨어
-community: 커뮤니티
-utils: 유틸리티 모듈
-contributing: Express에 기여하기
-changelog: 릴리즈 변경 로그
-# Support
-support: 지원
-# Blog
-blog: 블로그
-latest_post: 최신 게시물
-all_posts: 모든 게시물
-write_post: 게시물 작성
diff --git a/_data/languages.yml b/_data/languages.yml
deleted file mode 100644
index 8d3055553f..0000000000
--- a/_data/languages.yml
+++ /dev/null
@@ -1,20 +0,0 @@
-- code: en
-  name: English
-- code: fr
-  name: Français
-- code: de
-  name: Deutsch
-- code: es
-  name: Español
-- code: it
-  name: Italiano
-- code: ja
-  name: 日本語
-- code: zh-cn
-  name: 中文 (简体)
-- code: zh-tw
-  name: 繁體中文
-- code: ko
-  name: 한국어
-- code: pt-br
-  name: Português
\ No newline at end of file
diff --git a/_data/pt-br/footer.yml b/_data/pt-br/footer.yml
deleted file mode 100644
index ac75f6f544..0000000000
--- a/_data/pt-br/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Termos de Uso
-privacy_policy: Política de Privacidade
-coc: Código de Conduta
-trademark_policy: Política de Marcas
-security_policy: Política de Segurança
-license: Licença
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> e Express contributors. Todos os direitos reservados. A <a href='https://openjsf.org'>OpenJS Foundation</a> possui marcas registradas e utiliza marcas registradas. Para obter uma lista de marcas registradas da <a href='https://openjsf.org'>Fundação OpenJS</a>, por favor veja nossa <a href='https://trademark-policy.openjsf.org'>Politica de Marca</a> e <a href='https://trademark-list.openjsf.org'>Lista de Marcas</a>. Marcas e logotipos não indicados na lista <a href='https://trademark-list.openjsf.org'>de marcas registradas da OpenJS Foundation</a> são marcas registradas ou registradas de seus respectivos titulares. O uso deles não implica em nenhuma afiliação ou endosso por eles.
diff --git a/_data/pt-br/general.yml b/_data/pt-br/general.yml
deleted file mode 100644
index 3544c6811b..0000000000
--- a/_data/pt-br/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Agora o Padrão no npm com LTS Timeline"
-body_announcement: "Expresse 5.1.0 agora é o padrão do npm, e estamos introduzindo um cronograma oficial de LTS para as linhas de lançamento v4 e v5. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Confira nosso último blog para obter mais informações.</a>"
-community-caveat-alert: "Esta informação refere-se a sites de terceiros, produtos ou módulos que não são mantidos pela equipe do Expressjs. A listagem aqui não constitui um endosso ou recomendação da equipe de projeto Expressjs."
-warning: 'Atenção'
-note: 'Observação'
-caution: 'Atenção'
-i18n_notice: "Este documento pode estar desatualizado em relação à documentação em inglês. Para as últimas atualizações, por favor consulte o"
-i18n_notice_link_text: "documentação em inglês"
diff --git a/_data/pt-br/menu.yml b/_data/pt-br/menu.yml
deleted file mode 100644
index 4b533b9206..0000000000
--- a/_data/pt-br/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: Primeiros passos
-installing: Instalação
-hello_world: Olá mundo
-generator: Gerador do Express
-basic_routing: Roteamento Básico
-static_files: Arquivos Estáticos
-examples: Mais exemplos
-faq: Perguntas mais frequentes
-# Guide
-guide: Guia
-routing: Roteamento
-writing_middleware: Escrevendo o middleware
-using_middleware: Usando o middleware
-overriding_express_api: Sobrescrevendo a API Express
-using_template_engines: Usando template engines
-error_handling: Manipulação de erros
-debugging: Depuração
-behind_proxies: Express por trás dos proxies
-migrating_4: Migrando para o Express 4
-migrating_5: Migrando para o Express 5
-database_integration: Integração com base de dados
-# API reference
-api: Referência da API
-5x: 5.x
-4x: 4.x
-3x: 3.x (descontinuada)
-2x: 2.x (descontinuada)
-# Advanced topics
-advanced: Tópicos Avançados
-developing_template_engines: Criando template engines
-security_updates: Atualizações de segurança
-best_practice_security: Melhores práticas de segurança
-best_practice_performance: Melhores práticas de desempenho
-healthcheck_graceful_shutdown: Verificações de saúde e desligamento
-# Resources
-resources: Recursos
-glossary: Glossário
-middleware: Middleware
-community: Comunidade
-utils: Módulos utilitários
-contributing: Contribuindo para o Express
-changelog: Registros de alterações
-# Support
-support: Suporte
-# Blog
-blog: Blog
-latest_post: Ultimos post
-all_posts: Todos posts
-write_post: Escreva um Post
diff --git a/_data/zh-cn/footer.yml b/_data/zh-cn/footer.yml
deleted file mode 100644
index c68d10357e..0000000000
--- a/_data/zh-cn/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Terms of Use
-privacy_policy: Privacy Policy
-coc: Code of Conduct
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: License
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/zh-cn/general.yml b/_data/zh-cn/general.yml
deleted file mode 100644
index e6327e6214..0000000000
--- a/_data/zh-cn/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
diff --git a/_data/zh-cn/menu.yml b/_data/zh-cn/menu.yml
deleted file mode 100644
index 2f93d3585c..0000000000
--- a/_data/zh-cn/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: 入门
-installing: 安装
-hello_world: Hello world
-generator: Express 生成器
-basic_routing: 基本路由
-static_files: 静态文件
-examples: More examples
-faq: 常见问题及解答
-# Guide
-guide: 指南
-routing: 路由
-writing_middleware: 编写中间件
-using_middleware: 使用中间件
-overriding_express_api: Overriding the Express API
-using_template_engines: 使用模板引擎
-error_handling: 错误处理
-debugging: 调试
-behind_proxies: 代理背后的 Express
-migrating_4: 迁移到 Express 4
-migrating_5: 迁移到 Express 5
-database_integration: 数据库集成
-# API reference
-api: API 参考
-5x: 5.x
-4x: 4.x
-3x: 3.x (不推荐）
-2x: 2.x (不推荐）
-# Advanced topics
-advanced: 高级主题
-developing_template_engines: 模板引擎
-security_updates: 安全更新
-best_practice_security: 安全最佳实践
-best_practice_performance: 性能最佳实践
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: 资源
-glossary: 词汇表
-middleware: 中间件
-community: 社区
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_data/zh-tw/footer.yml b/_data/zh-tw/footer.yml
deleted file mode 100644
index c68d10357e..0000000000
--- a/_data/zh-tw/footer.yml
+++ /dev/null
@@ -1,7 +0,0 @@
-terms_of_use: Terms of Use
-privacy_policy: Privacy Policy
-coc: Code of Conduct
-trademark_policy: Trademark Policy
-security_policy: Security Policy
-license: License
-trademark_legal: Copyright <a href='https://openjsf.org'>OpenJS Foundation</a> and Express contributors. All rights reserved. The <a href='https://openjsf.org'>OpenJS Foundation</a> has registered trademarks and uses trademarks. For a list of trademarks of the <a href='https://openjsf.org'>OpenJS Foundation</a>, please see our <a href='https://trademark-policy.openjsf.org'>Trademark Policy</a> and <a href='https://trademark-list.openjsf.org'>Trademark List</a>. Trademarks and logos not indicated on the <a href='https://trademark-list.openjsf.org'>list of OpenJS Foundation trademarks</a> are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
diff --git a/_data/zh-tw/general.yml b/_data/zh-tw/general.yml
deleted file mode 100644
index e6327e6214..0000000000
--- a/_data/zh-tw/general.yml
+++ /dev/null
@@ -1,8 +0,0 @@
-title_announcement: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-body_announcement: "Express 5.1.0 is now the default on npm, and we're introducing an official LTS schedule for the v4 and v5 release lines. <a href='https://expressjs.com/2025/03/31/v5-1-latest-release.html'>Check out our latest blog for more information.</a>"
-community-caveat-alert: "This information refers to third-party sites, products, or modules that are not maintained by the Expressjs team. Listing here does not constitute an endorsement or recommendation from the Expressjs project team."
-warning: 'Warning'
-note: 'Note'
-caution: 'Caution'
-i18n_notice: "This document might be outdated relative to the documentation in English. For the latest updates, please refer to the"
-i18n_notice_link_text: "documentation in english"
diff --git a/_data/zh-tw/menu.yml b/_data/zh-tw/menu.yml
deleted file mode 100644
index f8dccefefb..0000000000
--- a/_data/zh-tw/menu.yml
+++ /dev/null
@@ -1,50 +0,0 @@
-# Getting started
-getting_started: 入門
-installing: 安裝
-hello_world: Hello world
-generator: Express 產生器
-basic_routing: 基本路由
-static_files: 靜態檔案
-examples: More examples
-faq: 常見問題 (FAQ)
-# Guide
-guide: 手冊
-routing: 路由
-writing_middleware: 撰寫中介軟體
-using_middleware: 使用中介軟體
-overriding_express_api: Overriding the Express API
-using_template_engines: 使用範本引擎
-error_handling: 錯誤處理
-debugging: 除錯
-behind_proxies: 位於 Proxy 背後的 Express
-migrating_4: 移至 Express 4
-migrating_5: 移至 Express 5
-database_integration: 資料庫整合
-# API reference
-api: API 參照
-5x: 5.x
-4x: 4.x
-3x: 3.x 已淘汰
-2x: 2.x (已淘汰）
-# Advanced topics
-advanced: 進階主題
-developing_template_engines: 範本引擎
-security_updates: 安全更新
-best_practice_security: 安全最佳作法
-best_practice_performance: 效能最佳作法
-healthcheck_graceful_shutdown: Health checks & shutdown
-# Resources
-resources: 資源
-glossary: 名詞解釋
-middleware: 中介軟體
-community: 社群
-utils: Utility modules
-contributing: Contributing to Express
-changelog: Release Change Log
-# Support
-support: Support
-# Blog
-blog: Blog
-latest_post: Latest post
-all_posts: All posts
-write_post: Write a Post
diff --git a/_includes/admonitions/caution.html b/_includes/admonitions/caution.html
deleted file mode 100644
index 0cb2624f19..0000000000
--- a/_includes/admonitions/caution.html
+++ /dev/null
@@ -1,4 +0,0 @@
-<div class="doc-box doc-notice" markdown="1"><p class="doc-title">{% include icons/caution.svg %} {{ site.data[page.lang].general.caution }}</p>
-{{include.content}}
-</div>
-    
\ No newline at end of file
diff --git a/_includes/admonitions/note.html b/_includes/admonitions/note.html
deleted file mode 100644
index afed80d26b..0000000000
--- a/_includes/admonitions/note.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<div class="doc-box doc-info" markdown="1">
-  <p class="doc-title" markdown="1">
-    {% include icons/note.svg %} {{ site.data[page.lang].general.note }}
-  </p>
-  {{include.content}}
-</div>
diff --git a/_includes/admonitions/warning.html b/_includes/admonitions/warning.html
deleted file mode 100644
index 27672663b7..0000000000
--- a/_includes/admonitions/warning.html
+++ /dev/null
@@ -1,3 +0,0 @@
-<div class="doc-box doc-warn" markdown="1"><p class="doc-title">{% include icons/warning.svg %} {{ site.data[page.lang].general.warning }}</p>
-{{include.content}}
-</div>
\ No newline at end of file
diff --git a/_includes/announcement.html b/_includes/announcement.html
deleted file mode 100644
index d0c213340e..0000000000
--- a/_includes/announcement.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<ul>
-    <li>
-      <p class="announcement-title">{% include icons/announcement.svg %} {{ site.data[page.lang].general.title_announcement }}</p>
-      <p markdown="1">
-        {{ site.data[page.lang].general.body_announcement }}
-      </p>
-    </li>
-</ul>
-  
\ No newline at end of file
diff --git a/_includes/api/en/3x/app-VERB.md b/_includes/api/en/3x/app-VERB.md
deleted file mode 100644
index 6e9b0d2759..0000000000
--- a/_includes/api/en/3x/app-VERB.md
+++ /dev/null
@@ -1,57 +0,0 @@
-<h3 id='app.VERB'>app.VERB(path, [callback...], callback)</h3>
-
-The `app.VERB()` methods provide the routing functionality
-in Express, where <strong>VERB</strong> is one of the HTTP verbs, such
-as `app.post()`. Multiple callbacks may be given, all are treated
-equally, and behave just like middleware, with the one exception that
-these callbacks may invoke `next('route')` to bypass the
-remaining route callback(s). This mechanism can be used to perform pre-conditions
-on a route then pass control to subsequent routes when there is no reason to proceed
-with the route matched.
-
-The following snippet illustrates the most simple route definition possible. Express
-translates the path strings to regular expressions, used internally to match incoming requests.
-Query strings are <em>not</em> considered when peforming these matches, for example "GET /"
-would match the following route, as would "GET /?name=tobi".
-
-```js
-app.get('/', function (req, res) {
-  res.send('hello world')
-})
-```
-
-Regular expressions may also be used, and can be useful
-if you have very specific restraints, for example the following
-would match "GET /commits/71dbb9c" as well as "GET /commits/71dbb9c..4c084f9".
-
-```js
-app.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, function (req, res) {
-  var from = req.params[0]
-  var to = req.params[1] || 'HEAD'
-  res.send('commit range ' + from + '..' + to)
-})
-```
-
-Several callbacks may also be passed, useful for re-using middleware
-that load resources, perform validations, etc.
-
-```js
-app.get('/user/:id', user.load, function () {
-  // ...
-})
-```
-
-These callbacks may be passed within arrays as well, these arrays are
-simply flattened when passed:
-
-```js
-var middleware = [loadForum, loadThread]
-
-app.get('/forum/:fid/thread/:tid', middleware, function () {
-  // ...
-})
-
-app.post('/forum/:fid/thread/:tid', middleware, function () {
-  // ...
-})
-```
diff --git a/_includes/api/en/3x/app-all.md b/_includes/api/en/3x/app-all.md
deleted file mode 100644
index 6b3a1e99f5..0000000000
--- a/_includes/api/en/3x/app-all.md
+++ /dev/null
@@ -1,32 +0,0 @@
-<h3 id='app.all'>app.all(path, [callback...], callback)</h3>
-
-This method functions just like the `app.VERB()` methods,
-however it matches all HTTP verbs.
-
-This method is extremely useful for
-mapping "global" logic for specific path prefixes or arbitrary matches.
-For example if you placed the following route at the top of all other
-route definitions, it would require that all routes from that point on
-would require authentication, and automatically load a user. Keep in mind
-that these callbacks do not have to act as end points, `loadUser`
-can perform a task, then `next()` to continue matching subsequent
-routes.
-
-```js
-app.all('*', requireAuthentication, loadUser)
-```
-
-Or the equivalent:
-
-```js
-app.all('*', requireAuthentication)
-app.all('*', loadUser)
-```
-
-Another great example of this is white-listed "global" functionality. Here
-the example is much like before, however only restricting paths prefixed with
-"/api":
-
-```js
-app.all('/api/*', requireAuthentication)
-```
diff --git a/_includes/api/en/3x/app-configure.md b/_includes/api/en/3x/app-configure.md
deleted file mode 100644
index 19029170e0..0000000000
--- a/_includes/api/en/3x/app-configure.md
+++ /dev/null
@@ -1,40 +0,0 @@
-<h3 id='app.configure'>app.configure([env], callback)</h3>
-
-Conditionally invoke `callback` when `env` matches `app.get('env')`,
-aka `process.env.NODE_ENV`. This method remains for legacy reasons, and is effectively
-an `if` statement as illustrated in the following snippets. These functions are <em>not</em>
-required in order to use `app.set()` and other configuration methods.
-
-```js
-// all environments
-app.configure(function () {
-  app.set('title', 'My Application')
-})
-
-// development only
-app.configure('development', function () {
-  app.set('db uri', 'localhost/dev')
-})
-
-// production only
-app.configure('production', function () {
-  app.set('db uri', 'n.n.n.n/prod')
-})
-```
-
-Is effectively sugar for:
-
-```js
-// all environments
-app.set('title', 'My Application')
-
-// development only
-if (app.get('env') === 'development') {
-  app.set('db uri', 'localhost/dev')
-}
-
-// production only
-if (app.get('env') === 'production') {
-  app.set('db uri', 'n.n.n.n/prod')
-}
-```
diff --git a/_includes/api/en/3x/app-disable.md b/_includes/api/en/3x/app-disable.md
deleted file mode 100644
index a3525d8543..0000000000
--- a/_includes/api/en/3x/app-disable.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='app.disable'>app.disable(name)</h3>
-
-Set setting `name` to `false`.
-
-```js
-app.disable('trust proxy')
-app.get('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/3x/app-disabled.md b/_includes/api/en/3x/app-disabled.md
deleted file mode 100644
index f2438f1c66..0000000000
--- a/_includes/api/en/3x/app-disabled.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='app.disabled'>app.disabled(name)</h3>
-
-Check if setting `name` is disabled.
-
-```js
-app.disabled('trust proxy')
-// => true
-
-app.enable('trust proxy')
-app.disabled('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/3x/app-enable.md b/_includes/api/en/3x/app-enable.md
deleted file mode 100644
index 926806ec1f..0000000000
--- a/_includes/api/en/3x/app-enable.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='app.enable'>app.enable(name)</h3>
-
-Set setting `name` to `true`.
-
-```js
-app.enable('trust proxy')
-app.get('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/3x/app-enabled.md b/_includes/api/en/3x/app-enabled.md
deleted file mode 100644
index b485780286..0000000000
--- a/_includes/api/en/3x/app-enabled.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='app.enabled'>app.enabled(name)</h3>
-
-Check if setting `name` is enabled.
-
-```js
-app.enabled('trust proxy')
-// => false
-
-app.enable('trust proxy')
-app.enabled('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/3x/app-engine.md b/_includes/api/en/3x/app-engine.md
deleted file mode 100644
index fcdfd7c9d9..0000000000
--- a/_includes/api/en/3x/app-engine.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='app.engine'>app.engine(ext, callback)</h3>
-
-Register the given template engine `callback` as `ext`
-
-By default will `require()` the engine based on the
-file extension. For example if you try to render
-a "foo.jade" file Express will invoke the following internally,
-and cache the `require()` on subsequent calls to increase
-performance.
-
-```js
-app.engine('jade', require('jade').__express)
-```
-
-For engines that do not provide `.__express` out of the box -
-or if you wish to "map" a different extension to the template engine
-you may use this method. For example mapping the EJS template engine to
-".html" files:
-
-```js
-app.engine('html', require('ejs').renderFile)
-```
-
-In this case EJS provides a `.renderFile()` method with
-the same signature that Express expects: `(path, options, callback)`,
-though note that it aliases this method as `ejs.__express` internally
-so if you're using ".ejs" extensions you dont need to do anything.
-
-Some template engines do not follow this convention, the
-<a href="https://github.com/visionmedia/consolidate.js">consolidate.js</a>
-library was created to map all of node's popular template
-engines to follow this convention, thus allowing them to
-work seemlessly within Express.
-
-```js
-var engines = require('consolidate')
-app.engine('haml', engines.haml)
-app.engine('html', engines.hogan)
-```
diff --git a/_includes/api/en/3x/app-get.md b/_includes/api/en/3x/app-get.md
deleted file mode 100644
index 15b908a1cc..0000000000
--- a/_includes/api/en/3x/app-get.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='app.get'>app.get(name)</h3>
-
-Get setting `name` value.
-
-```js
-app.get('title')
-// => undefined
-
-app.set('title', 'My Site')
-app.get('title')
-// => "My Site"
-```
diff --git a/_includes/api/en/3x/app-listen.md b/_includes/api/en/3x/app-listen.md
deleted file mode 100644
index f2349f0b54..0000000000
--- a/_includes/api/en/3x/app-listen.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='app.listen'>app.listen()</h3>
-
-Bind and listen for connections on the given host and port,
-this method is identical to node's <a href="http://nodejs.org/api/http.html#http_server_listen_port_hostname_backlog_callback">http.Server#listen()</a>.
-
-```js
-var express = require('express')
-var app = express()
-app.listen(3000)
-```
-
-The `app` returned by `express()` is in fact a JavaScript
-`Function`, designed to be passed to node's http servers as a callback
-to handle requests. This allows you to provide both HTTP and HTTPS versions of
-your app with the same codebase easily, as the app does not inherit from these,
-it is simply a callback:
-
-```js
-var express = require('express')
-var https = require('https')
-var http = require('http')
-var app = express()
-
-http.createServer(app).listen(80)
-https.createServer(options, app).listen(443)
-```
-
-The `app.listen()` method is simply a convenience method defined as,
-if you wish to use HTTPS or provide both, use the technique above.
-
-```js
-app.listen = function () {
-  var server = http.createServer(this)
-  return server.listen.apply(server, arguments)
-}
-```
diff --git a/_includes/api/en/3x/app-locals.md b/_includes/api/en/3x/app-locals.md
deleted file mode 100644
index d35421160e..0000000000
--- a/_includes/api/en/3x/app-locals.md
+++ /dev/null
@@ -1,47 +0,0 @@
-<h3 id='app.locals'>app.locals</h3>
-
-Application local variables are provided to all templates
-rendered within the application. This is useful for providing
-helper functions to templates, as well as app-level data.
-
-```js
-app.locals.title = 'My App'
-app.locals.strftime = require('strftime')
-```
-
-The `app.locals` object is a JavaScript `Function`,
-which when invoked with an object will merge properties into itself, providing
-a simple way to expose existing objects as local variables.
-
-```js
-app.locals({
-  title: 'My App',
-  phone: '1-250-858-9990',
-  email: 'me@myapp.com'
-})
-
-console.log(app.locals.title)
-// => 'My App'
-
-console.log(app.locals.email)
-// => 'me@myapp.com'
-```
-
-A consequence of the `app.locals` Object being ultimately a Javascript Function Object is that you must not reuse existing (native) named properties for your own variable names, such as `name, apply, bind, call, arguments, length, constructor`.
-
-```js
-app.locals({ name: 'My App' })
-
-console.log(app.locals.name)
-// => return 'app.locals' in place of 'My App' (app.locals is a Function !)
-// => if name's variable is used in a template, a ReferenceError will be returned.
-```
-
-The full list of native named properties can be found in many specifications. The <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference">JavaScript specification</a> introduced original properties, some of which still recognized by modern engines, and the <a href="http://www.ecma-international.org/ecma-262/5.1/">EcmaScript specification</a> then built on it and normalized the set of properties, adding new ones and removing deprecated ones. Check out properties for Functions and Objects if interested.
-
-By default Express exposes only a single app-level local variable, `settings`.
-
-```js
-app.set('title', 'My App')
-// use settings.title in a view
-```
diff --git a/_includes/api/en/3x/app-param.md b/_includes/api/en/3x/app-param.md
deleted file mode 100644
index 72d9fd507b..0000000000
--- a/_includes/api/en/3x/app-param.md
+++ /dev/null
@@ -1,70 +0,0 @@
-<h3 id='app.param'>app.param([name], callback)</h3>
-
-Map logic to route parameters. For example when `:user`
-is present in a route path you may map user loading logic to automatically
-provide `req.user` to the route, or perform validations
-on the parameter input.
-
-The following snippet illustrates how the `callback`
-is much like middleware, thus supporting async operations, however
-providing the additional value of the parameter, here named as `id`.
-An attempt to load the user is then performed, assigning `req.user`,
-otherwise passing an error to `next(err)`.
-
-```js
-app.param('user', function (req, res, next, id) {
-  User.find(id, function (err, user) {
-    if (err) {
-      next(err)
-    } else if (user) {
-      req.user = user
-      next()
-    } else {
-      next(new Error('failed to load user'))
-    }
-  })
-})
-```
-
-Alternatively you may pass only a `callback`, in which
-case you have the opportunity to alter the `app.param()` API.
-For example the <a href="http://github.com/expressjs/express-params">express-params</a>
-defines the following callback which allows you to restrict parameters to a given
-regular expression.
-
-This example is a bit more advanced, checking if the second argument is a regular
-expression, returning the callback which acts much like the "user" param example.
-
-```js
-app.param(function (name, fn) {
-  if (fn instanceof RegExp) {
-    return function (req, res, next, val) {
-      var captures
-      if ((captures = fn.exec(String(val)))) {
-        req.params[name] = captures
-        next()
-      } else {
-        next('route')
-      }
-    }
-  }
-})
-```
-
-The method could now be used to effectively validate parameters, or also
-parse them to provide capture groups:
-
-```js
-app.param('id', /^\d+$/)
-
-app.get('/user/:id', function (req, res) {
-  res.send('user ' + req.params.id)
-})
-
-app.param('range', /^(\w+)\.\.(\w+)?$/)
-
-app.get('/range/:range', function (req, res) {
-  var range = req.params.range
-  res.send('from ' + range[1] + ' to ' + range[2])
-})
-```
diff --git a/_includes/api/en/3x/app-render.md b/_includes/api/en/3x/app-render.md
deleted file mode 100644
index 0b1ced84c8..0000000000
--- a/_includes/api/en/3x/app-render.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='app.render'>app.render(view, [options], callback)</h3>
-
-Render a `view` with a callback responding with
-the rendered string. This is the app-level variant of `res.render()`,
-and otherwise behaves the same way.
-
-```js
-app.render('email', function (err, html) {
-  // ...
-})
-
-app.render('email', { name: 'Tobi' }, function (err, html) {
-  // ...
-})
-```
diff --git a/_includes/api/en/3x/app-routes.md b/_includes/api/en/3x/app-routes.md
deleted file mode 100644
index aff28f6967..0000000000
--- a/_includes/api/en/3x/app-routes.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<h3 id='app.routes'>app.routes</h3>
-
-The `app.routes` object houses all of the routes defined mapped
-by the associated HTTP verb. This object may be used for introspection capabilities,
-for example Express uses this internally not only for routing but to provide default
-<string>OPTIONS</string> behaviour unless `app.options()` is used. Your application
-or framework may also remove routes by simply by removing them from this object.
-
-The output of `console.log(app.routes)`:
-
-```
-{ get:
-   [ { path: '/',
-       method: 'get',
-       callbacks: [Object],
-       keys: [],
-       regexp: /^\/\/?$/i },
-     { path: '/user/:id',
-       method: 'get',
-       callbacks: [Object],
-       keys: [{ name: 'id', optional: false }],
-       regexp: /^\/user\/(?:([^\/]+?))\/?$/i } ],
-  delete:
-   [ { path: '/user/:id',
-       method: 'delete',
-       callbacks: [Object],
-       keys: [Object],
-       regexp: /^\/user\/(?:([^\/]+?))\/?$/i } ] }
-```
diff --git a/_includes/api/en/3x/app-set.md b/_includes/api/en/3x/app-set.md
deleted file mode 100644
index 8991774208..0000000000
--- a/_includes/api/en/3x/app-set.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='app.set'>app.set(name, value)</h3>
-
-Assigns setting `name` to `value`.
-
-```js
-app.set('title', 'My Site')
-app.get('title')
-// => "My Site"
-```
diff --git a/_includes/api/en/3x/app-settings.md b/_includes/api/en/3x/app-settings.md
deleted file mode 100644
index 71c7848d1e..0000000000
--- a/_includes/api/en/3x/app-settings.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='app-settings'>settings</h3>
-
-The following settings are provided to alter how Express will behave:
-
-* `env` Environment mode, defaults to process.env.NODE_ENV or "development"
-* `trust proxy` Enables reverse proxy support, disabled by default
-* `jsonp callback name` Changes the default callback name of ?callback=
-* `json replacer` JSON replacer callback, null by default
-* `json spaces` JSON response spaces for formatting, defaults to 2 in development, 0 in production
-* `case sensitive routing` Enable case sensitivity, disabled by default, treating "/Foo" and "/foo" as the same
-* `strict routing` Enable strict routing, by default "/foo" and "/foo/" are treated the same by the router
-* `view cache` Enables view template compilation caching, enabled in production by default
-* `view engine` The default engine extension to use when omitted
-* `views` The view directory path, defaulting to "process.cwd() + '/views'"
-  
diff --git a/_includes/api/en/3x/app-use.md b/_includes/api/en/3x/app-use.md
deleted file mode 100644
index ceba45f66c..0000000000
--- a/_includes/api/en/3x/app-use.md
+++ /dev/null
@@ -1,89 +0,0 @@
-<h3 id='app.use'>app.use([path], function)</h3>
-
-Use the given middleware `function`, with optional mount `path`,
-defaulting to "/".
-
-```js
-var express = require('express')
-var app = express()
-
-// simple logger
-app.use(function (req, res, next) {
-  console.log('%s %s', req.method, req.url)
-  next()
-})
-
-// respond
-app.use(function (req, res, next) {
-  res.send('Hello World')
-})
-
-app.listen(3000)
-```
-
-The "mount" path is stripped and is <strong>not</strong> visible
-to the middleware `function`. The main effect of this feature is that
-mounted middleware may operate without code changes regardless of its "prefix"
-pathname.
-
-<div class="doc-box doc-notice" markdown="1">
-A route will match any path that follows its path immediately with either a "`/`" or a "`.`". For example: `app.use('/apple', ...)` will match _/apple_, _/apple/images_, _/apple/images/news_, _/apple.html_, _/apple.html.txt_, and so on.
-</div>
-
-Here's a concrete example, take the typical use-case of serving files in ./public
-using the `express.static()` middleware:
-
-```js
-// GET /javascripts/jquery.js
-// GET /style.css
-// GET /favicon.ico
-app.use(express.static(path.join(__dirname, 'public')))
-```
-
-Say for example you wanted to prefix all static files with "/static", you could
-use the "mounting" feature to support this. Mounted middleware functions are _not_
-invoked unless the `req.url` contains this prefix, at which point
-it is stripped when the function is invoked. This affects this function only,
-subsequent middleware will see `req.url` with "/static" included
-unless they are mounted as well.
-
-```js
-// GET /static/javascripts/jquery.js
-// GET /static/style.css
-// GET /static/favicon.ico
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-The order of which middleware are "defined" using `app.use()` is
-very important, they are invoked sequentially, thus this defines middleware
-precedence. For example usually `express.logger()` is the very
-first middleware you would use, logging every request:
-
-```js
-app.use(express.logger())
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(function (req, res) {
-  res.send('Hello')
-})
-```
-
-Now suppose you wanted to ignore logging requests for static files, but to
-continue logging routes and middleware defined after `logger()`,
-you would simply move `static()` above:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(express.logger())
-app.use(function (req, res) {
-  res.send('Hello')
-})
-```
-
-Another concrete example would be serving files from multiple directories,
-giving precedence to "./public" over the others:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(express.static(path.join(__dirname, 'files')))
-app.use(express.static(path.join(__dirname, 'uploads')))
-```
diff --git a/_includes/api/en/3x/app.md b/_includes/api/en/3x/app.md
deleted file mode 100644
index 0d15c491a8..0000000000
--- a/_includes/api/en/3x/app.md
+++ /dev/null
@@ -1,69 +0,0 @@
-<h2 id="application">Application</h2>
-
-<section markdown="1">
-  {% include api/en/3x/app-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-enable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-disable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-enabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-disabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-configure.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-use.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-settings.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-engine.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-VERB.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-all.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-locals.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-render.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-routes.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/app-listen.md %}
-</section>
diff --git a/_includes/api/en/3x/express.md b/_includes/api/en/3x/express.md
deleted file mode 100644
index 195683b30d..0000000000
--- a/_includes/api/en/3x/express.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h2 id="express">express()</h2>
-
-Creates an Express application. The `express()` function is a top-level function exported by the _express_ module.
-
-```js
-var express = require('express')
-var app = express()
-
-app.get('/', function (req, res) {
-  res.send('hello world')
-})
-
-app.listen(3000)
-```
diff --git a/_includes/api/en/3x/menu.md b/_includes/api/en/3x/menu.md
deleted file mode 100644
index c09dbbe6f2..0000000000
--- a/_includes/api/en/3x/menu.md
+++ /dev/null
@@ -1,163 +0,0 @@
-<button id="menu-toggle" title="show table of content">On this page</button>
-<ul id="menu">
-    <li><a href="#express">express()</a></li>
-    <li id="app-api"> <a href="#application">Application</a>
-        <ul id="app-menu">
-            <li><a href="#app.set">app.set()</a>
-            </li>
-            <li><a href="#app.get">app.get()</a>
-            </li>
-            <li><a href="#app.enable">app.enable()</a>
-            </li>
-            <li><a href="#app.disable">app.disable()</a>
-            </li>
-            <li><a href="#app.enabled">app.enabled()</a>
-            </li>
-            <li><a href="#app.disabled">app.disabled()</a>
-            </li>
-            <li><a href="#app.configure">app.configure()</a>
-            </li>
-            <li><a href="#app.use">app.use()</a>
-            </li>
-            <li><a href="#app-settings">application settings</a>
-            </li>
-            <li><a href="#app.engine">app.engine()</a>
-            </li>
-            <li><a href="#app.param">app.param()</a>
-            </li>
-            <li><a href="#app.VERB">application routing</a>
-            </li>
-            <li><a href="#app.all">app.all()</a>
-            </li>
-            <li><a href="#app.locals">app.locals</a>
-            </li>
-            <li><a href="#app.render">app.render()</a>
-            </li>
-            <li><a href="#app.routes">app.routes</a>
-            </li>
-            <li><a href="#app.listen">app.listen()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="req-api"> <a href="#request">Request</a>
-        <ul id="req-menu">
-            <li><a href="#req.params">req.params</a>
-            </li>
-            <li><a href="#req.query">req.query</a>
-            </li>
-            <li><a href="#req.body">req.body</a>
-            </li>
-            <li><a href="#req.files">req.files</a>
-            </li>
-            <li><a href="#req.param">req.param()</a>
-            </li>
-            <li><a href="#req.route">req.route</a>
-            </li>
-            <li><a href="#req.cookies">req.cookies</a>
-            </li>
-            <li><a href="#req.signedCookies">req.signedCookies</a>
-            </li>
-            <li><a href="#req.get">req.get()</a>
-            </li>
-            <li><a href="#req.accepts">req.accepts()</a>
-            </li>
-            <li><a href="#req.accepted">req.accepted</a>
-            </li>
-            <li><a href="#req.is">req.is()</a>
-            </li>
-            <li><a href="#req.ip">req.ip</a>
-            </li>
-            <li><a href="#req.ips">req.ips</a>
-            </li>
-            <li><a href="#req.path">req.path</a>
-            </li>
-            <li><a href="#req.host">req.host</a>
-            </li>
-            <li><a href="#req.fresh">req.fresh</a>
-            </li>
-            <li><a href="#req.stale">req.stale</a>
-            </li>
-            <li><a href="#req.xhr">req.xhr</a>
-            </li>
-            <li><a href="#req.protocol">req.protocol</a>
-            </li>
-            <li><a href="#req.secure">req.secure</a>
-            </li>
-            <li><a href="#req.subdomains">req.subdomains</a>
-            </li>
-            <li><a href="#req.originalUrl">req.originalUrl</a>
-            </li>
-            <li><a href="#req.acceptedLanguages">req.acceptedLanguages</a>
-            </li>
-            <li><a href="#req.acceptedCharsets">req.acceptedCharsets</a>
-            </li>
-            <li><a href="#req.acceptsCharset">req.acceptsCharset()</a>
-            </li>
-            <li><a href="#req.acceptsLanguage">req.acceptsLanguage()</a>
-            </li>
-            <li><a href="#req.res">req.res</a>
-            </li>
-        </ul>
-    </li>
-    <li id="res-api"> <a href="#response">Response</a>
-        <ul id="res-menu">
-            <li><a href="#res.status">res.status()</a>
-            </li>
-            <li><a href="#res.set">res.set()</a>
-            </li>
-            <li><a href="#res.get">res.get()</a>
-            </li>
-            <li><a href="#res.cookie">res.cookie()</a>
-            </li>
-            <li><a href="#res.clearCookie">res.clearCookie()</a>
-            </li>
-            <li><a href="#res.redirect">res.redirect()</a>
-            </li>
-            <li><a href="#res.location">res.location()</a>
-            </li>
-            <li><a href="#res.charset">res.charset</a>
-            </li>
-            <li><a href="#res.send">res.send()</a>
-            </li>
-            <li><a href="#res.json">res.json()</a>
-            </li>
-            <li><a href="#res.jsonp">res.jsonp()</a>
-            </li>
-            <li><a href="#res.type">res.type()</a>
-            </li>
-            <li><a href="#res.format">res.format()</a>
-            </li>
-            <li><a href="#res.attachment">res.attachment()</a>
-            </li>
-            <li><a href="#res.sendfile">res.sendfile()</a>
-            </li>
-            <li><a href="#res.download">res.download()</a>
-            </li>
-            <li><a href="#res.links">res.links()</a>
-            </li>
-            <li><a href="#res.locals">res.locals</a>
-            </li>
-            <li><a href="#res.render">res.render()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="middleware-api"><a href="#middleware">Middleware</a>
-        <ul id="middleware-menu">
-            <li><a href="#basicAuth">basicAuth()</a>
-            </li>
-            <li><a href="#bodyParser">bodyParser()</a>
-            </li>
-            <li><a href="#compress">compress()</a>
-            </li>
-            <li><a href="#cookieParser">cookieParser()</a>
-            </li>
-            <li><a href="#cookieSession">cookieSession()</a>
-            </li>
-            <li><a href="#csrf">csrf()</a>
-            </li>
-            <li><a href="#directory">directory()</a>
-            </li>
-        </ul>
-    </li>
-</ul>
-
diff --git a/_includes/api/en/3x/middleware.md b/_includes/api/en/3x/middleware.md
deleted file mode 100644
index 001790acc9..0000000000
--- a/_includes/api/en/3x/middleware.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<h2 id="middleware">Middleware</h2>
-
-<section markdown="1">
-  {% include api/en/3x/mw-basicAuth.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-bodyParser.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-compress.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-cookieParser.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-cookieSession.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-csrf.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/mw-directory.md %}
-</section>
diff --git a/_includes/api/en/3x/mw-basicAuth.md b/_includes/api/en/3x/mw-basicAuth.md
deleted file mode 100644
index b5c2879c6a..0000000000
--- a/_includes/api/en/3x/mw-basicAuth.md
+++ /dev/null
@@ -1,27 +0,0 @@
-<h3 id='basicAuth'>basicAuth()</h3>
-
-Basic Authentication middleware, populating `req.user`
-with the username.
-
-Simple username and password:
-
-```js
-app.use(express.basicAuth('username', 'password'))
-```
-
-Callback verification:
-
-```js
-app.use(express.basicAuth(function (user, pass) {
-  return user === 'tj' && pass === 'wahoo'
-}))
-```
-
-Async callback verification, accepting `fn(err, user)`,
-in this case `req.user` will be the user object passed.
-
-```js
-app.use(express.basicAuth(function (user, pass, fn) {
-  User.authenticate({ user: user, pass: pass }, fn)
-}))
-```
diff --git a/_includes/api/en/3x/mw-bodyParser.md b/_includes/api/en/3x/mw-bodyParser.md
deleted file mode 100644
index 0052443b17..0000000000
--- a/_includes/api/en/3x/mw-bodyParser.md
+++ /dev/null
@@ -1,27 +0,0 @@
-<h3 id='bodyParser'>bodyParser()</h3>
-
-Request body parsing middleware supporting JSON, urlencoded,
-and multipart requests. This middleware is simply a wrapper
-for the `json()`, `urlencoded()`, and
-`multipart()` middleware.
-
-```js
-app.use(express.bodyParser())
-
-// is equivalent to:
-app.use(express.json())
-app.use(express.urlencoded())
-app.use(express.multipart())
-```
-
-For security sake, it's better to disable file upload if your application
-doesn't need it. To do this, use only the needed middleware, i.e. don't use
-the `bodyParser` and `multipart()` middleware:
-
-```js
-app.use(express.json())
-app.use(express.urlencoded())
-```
-
-If your application needs file upload you should set up
-<a href='https://groups.google.com/d/msg/express-js/iP2VyhkypHo/5AXQiYN3RPcJ'>a strategy for dealing with those files</a>.
diff --git a/_includes/api/en/3x/mw-compress.md b/_includes/api/en/3x/mw-compress.md
deleted file mode 100644
index 3221859c02..0000000000
--- a/_includes/api/en/3x/mw-compress.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='compress'>compress()</h3>
-
-Compress response data with gzip / deflate. This middleware
-should be placed "high" within the stack to ensure all
-responses may be compressed.
-
-```js
-app.use(express.logger())
-app.use(express.compress())
-app.use(express.methodOverride())
-app.use(express.bodyParser())
-```
diff --git a/_includes/api/en/3x/mw-cookieParser.md b/_includes/api/en/3x/mw-cookieParser.md
deleted file mode 100644
index 32b5c28e2e..0000000000
--- a/_includes/api/en/3x/mw-cookieParser.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='cookieParser'>cookieParser()</h3>
-
-Parses the Cookie header field and populates `req.cookies`
-with an object keyed by the cookie names. Optionally you may enabled
-signed cookie support by passing a `secret` string.
-
-```js
-app.use(express.cookieParser())
-app.use(express.cookieParser('some secret'))
-```
diff --git a/_includes/api/en/3x/mw-cookieSession.md b/_includes/api/en/3x/mw-cookieSession.md
deleted file mode 100644
index 5daecf0bfe..0000000000
--- a/_includes/api/en/3x/mw-cookieSession.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='cookieSession'>cookieSession()</h3>
-
-Provides cookie-based sessions, and populates `req.session`.
-This middleware takes the following options:
-
-* `key` cookie name defaulting to `connect.sess`
-* `secret` prevents cookie tampering
-* `cookie` session cookie settings, defaulting to `{ path: '/', httpOnly: true, maxAge: null }`
-* `proxy` trust the reverse proxy when setting secure cookies (via "x-forwarded-proto")
-
-```js
-app.use(express.cookieSession())
-```
-
-To clear a cookie simply assign the session to null before responding:
-
-```js
-req.session = null
-```
diff --git a/_includes/api/en/3x/mw-csrf.md b/_includes/api/en/3x/mw-csrf.md
deleted file mode 100644
index beacfe56b2..0000000000
--- a/_includes/api/en/3x/mw-csrf.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='csrf'>csrf()</h3>
-
-CSRF protection middleware.
-
-By default this middleware generates a token named "_csrf"
-which should be added to requests which mutate
-state, within a hidden form field, query-string etc. This
-token is validated against `req.csrfToken()`.
-
-The default `value` function checks `req.body` generated
-by the `bodyParser()` middleware, `req.query` generated
-by `query()`, and the "X-CSRF-Token" header field.
-
-This middleware requires session support, thus should be added
-somewhere below `session()`.
diff --git a/_includes/api/en/3x/mw-directory.md b/_includes/api/en/3x/mw-directory.md
deleted file mode 100644
index b2e785489d..0000000000
--- a/_includes/api/en/3x/mw-directory.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='directory'>directory()</h3>
-
-Directory serving middleware, serves the given `path`.
-This middleware may be paired with `static()` to serve
-files, providing a full-featured file browser.
-
-```js
-app.use(express.directory('public'))
-app.use(express.static('public'))
-```
-
-This middleware accepts the following options:
-
-* `hidden` display hidden (dot) files. Defaults to false.
-* `icons`  display icons. Defaults to false.
-* `filter` Apply this filter function to files. Defaults to false.
diff --git a/_includes/api/en/3x/req-accepted.md b/_includes/api/en/3x/req-accepted.md
deleted file mode 100644
index 04d664dafd..0000000000
--- a/_includes/api/en/3x/req-accepted.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='req.accepted'>req.accepted</h3>
-
-Return an array of Accepted media types ordered from highest quality to lowest.
-
-```
-[ { value: 'application/json',
-    quality: 1,
-    type: 'application',
-    subtype: 'json' },
-   { value: 'text/html',
-     quality: 0.5,
-     type: 'text',
-     subtype: 'html' } ]
-```
diff --git a/_includes/api/en/3x/req-acceptedCharsets.md b/_includes/api/en/3x/req-acceptedCharsets.md
deleted file mode 100644
index fb4cca0c74..0000000000
--- a/_includes/api/en/3x/req-acceptedCharsets.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='req.acceptedCharsets'>req.acceptedCharsets</h3>
-
-Return an array of Accepted charsets ordered from highest quality to lowest.
-
-```
-Accept-Charset: iso-8859-5;q=.2, unicode-1-1;q=0.8
-// => ['unicode-1-1', 'iso-8859-5']
-```
diff --git a/_includes/api/en/3x/req-acceptedLanguages.md b/_includes/api/en/3x/req-acceptedLanguages.md
deleted file mode 100644
index 42c5494e89..0000000000
--- a/_includes/api/en/3x/req-acceptedLanguages.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='req.acceptedLanguages'>req.acceptedLanguages</h3>
-
-Return an array of Accepted languages ordered from highest quality to lowest.
-
-```
-Accept-Language: en;q=.5, en-us
-// => ['en-us', 'en']
-```
diff --git a/_includes/api/en/3x/req-accepts.md b/_includes/api/en/3x/req-accepts.md
deleted file mode 100644
index aac9440ad6..0000000000
--- a/_includes/api/en/3x/req-accepts.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='req.accepts'>req.accepts(types)</h3>
-
-Check if the given `types` are acceptable, returning
-the best match when true, otherwise `undefined` - in which
-case you should respond with 406 "Not Acceptable".
-
-The `type` value may be a single mime type string
-such as "application/json", the extension name
-such as "json", a comma-delimited list or an array. When a list
-or array is given the best match, if any is returned.
-
-```js
-// Accept: text/html
-req.accepts('html')
-// => "html"
-
-// Accept: text/*, application/json
-req.accepts('html')
-// => "html"
-req.accepts('text/html')
-// => "text/html"
-req.accepts('json, text')
-// => "json"
-req.accepts('application/json')
-// => "application/json"
-
-// Accept: text/*, application/json
-req.accepts('image/png')
-req.accepts('png')
-// => undefined
-
-// Accept: text/*;q=.5, application/json
-req.accepts(['html', 'json'])
-req.accepts('html, json')
-// => "json"
-```
diff --git a/_includes/api/en/3x/req-acceptsCharset.md b/_includes/api/en/3x/req-acceptsCharset.md
deleted file mode 100644
index 99e8e16a43..0000000000
--- a/_includes/api/en/3x/req-acceptsCharset.md
+++ /dev/null
@@ -1,3 +0,0 @@
-<h3 id='req.acceptsCharset'>req.acceptsCharset(charset)</h3>
-
-Check if the given `charset` are acceptable.
diff --git a/_includes/api/en/3x/req-acceptsLanguage.md b/_includes/api/en/3x/req-acceptsLanguage.md
deleted file mode 100644
index a640dd308e..0000000000
--- a/_includes/api/en/3x/req-acceptsLanguage.md
+++ /dev/null
@@ -1,3 +0,0 @@
-<h3 id='req.acceptsLanguage'>req.acceptsLanguage(lang)</h3>
-
-Check if the given `lang` are acceptable.
diff --git a/_includes/api/en/3x/req-body.md b/_includes/api/en/3x/req-body.md
deleted file mode 100644
index dfed5c3eff..0000000000
--- a/_includes/api/en/3x/req-body.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='req.body'>req.body</h3>
-
-This property is an object containing the parsed request body. This feature
-is provided by the `bodyParser()` middleware, though other body
-parsing middleware may follow this convention as well. This property
-defaults to `{}` when `bodyParser()` is used.
-
-```js
-// POST user[name]=tobi&user[email]=tobi@learnboost.com
-console.log(req.body.user.name)
-// => "tobi"
-
-console.log(req.body.user.email)
-// => "tobi@learnboost.com"
-
-// POST { "name": "tobi" }
-console.log(req.body.name)
-// => "tobi"
-```
diff --git a/_includes/api/en/3x/req-cookies.md b/_includes/api/en/3x/req-cookies.md
deleted file mode 100644
index 66ad363ace..0000000000
--- a/_includes/api/en/3x/req-cookies.md
+++ /dev/null
@@ -1,11 +0,0 @@
-<h3 id='req.cookies'>req.cookies</h3>
-
-This object requires the `cookieParser()` middleware for use.
-It contains cookies sent by the user-agent. If no cookies are sent, it
-defaults to `{}`.
-
-```js
-// Cookie: name=tj
-console.log(req.cookies.name)
-// => "tj"
-```
diff --git a/_includes/api/en/3x/req-files.md b/_includes/api/en/3x/req-files.md
deleted file mode 100644
index 98331fbd48..0000000000
--- a/_includes/api/en/3x/req-files.md
+++ /dev/null
@@ -1,45 +0,0 @@
-<h3 id='req.files'>req.files</h3>
-
-This property is an object of the files uploaded. This feature
-is provided by the `bodyParser()` middleware, though other body
-parsing middleware may follow this convention as well. This property
-defaults to `{}` when `bodyParser()` is used.
-
-For example if a <strong>file</strong> field was named "image",
-and a file was uploaded, `req.files.image` would contain
-the following `File` object:
-
-```
-{ size: 74643,
-  path: '/tmp/8ef9c52abe857867fd0a4e9a819d1876',
-  name: 'edge.png',
-  type: 'image/png',
-  hash: false,
-  lastModifiedDate: Thu Aug 09 2012 20:07:51 GMT-0700 (PDT),
-  _writeStream:
-   { path: '/tmp/8ef9c52abe857867fd0a4e9a819d1876',
-     fd: 13,
-     writable: false,
-     flags: 'w',
-     encoding: 'binary',
-     mode: 438,
-     bytesWritten: 74643,
-     busy: false,
-     _queue: [],
-     _open: [Function],
-     drainable: true },
-  length: [Getter],
-  filename: [Getter],
-  mime: [Getter] }
-```
-
-The `bodyParser()` middleware utilizes the
-<a href="https://github.com/felixge/node-formidable">node-formidable</a>
-module internally, and accepts the same options. An example of this
-is the `keepExtensions` formidable option, defaulting to <strong>false</strong>
-which in this case gives you the filename "/tmp/8ef9c52abe857867fd0a4e9a819d1876" void of
-the ".png" extension. To enable this, and others you may pass them to `bodyParser()`:
-
-```js
-app.use(express.bodyParser({ keepExtensions: true, uploadDir: '/my/files' }))
-```
diff --git a/_includes/api/en/3x/req-fresh.md b/_includes/api/en/3x/req-fresh.md
deleted file mode 100644
index 6b4e6e5832..0000000000
--- a/_includes/api/en/3x/req-fresh.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.fresh'>req.fresh</h3>
-
-Check if the request is fresh - aka Last-Modified and/or the ETag still match,
-indicating that the resource is "fresh".
-
-```js
-console.dir(req.fresh)
-// => true
-```
diff --git a/_includes/api/en/3x/req-header.md b/_includes/api/en/3x/req-header.md
deleted file mode 100644
index e186dbdcd9..0000000000
--- a/_includes/api/en/3x/req-header.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='req.get'>req.get(field)</h3>
-
-Get the case-insensitive request header `field`. The "Referrer" and "Referer" fields are interchangeable.
-
-```js
-req.get('Content-Type')
-// => "text/plain"
-
-req.get('content-type')
-// => "text/plain"
-
-req.get('Something')
-// => undefined
-```
-
-p Aliased as `req.header(field)`.
diff --git a/_includes/api/en/3x/req-host.md b/_includes/api/en/3x/req-host.md
deleted file mode 100644
index d24fdfe1c4..0000000000
--- a/_includes/api/en/3x/req-host.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.host'>req.host</h3>
-
-Returns the hostname from the "Host" header field (void of portno).
-
-```js
-// Host: "example.com:3000"
-console.dir(req.host)
-// => 'example.com'
-```
diff --git a/_includes/api/en/3x/req-ip.md b/_includes/api/en/3x/req-ip.md
deleted file mode 100644
index 1de60fabf3..0000000000
--- a/_includes/api/en/3x/req-ip.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.ip'>req.ip</h3>
-
-Return the remote address, or when "trust proxy"
-is enabled - the upstream address.
-
-```js
-console.dir(req.ip)
-// => '127.0.0.1'
-```
diff --git a/_includes/api/en/3x/req-ips.md b/_includes/api/en/3x/req-ips.md
deleted file mode 100644
index 7b139a29a6..0000000000
--- a/_includes/api/en/3x/req-ips.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='req.ips'>req.ips</h3>
-
-When "trust proxy" is `true`, parse
-the "X-Forwarded-For" ip address list
-and return an array, otherwise an empty
-array is returned.
-
-For example if the value were "client, proxy1, proxy2"
-you would receive the array `["client", "proxy1", "proxy2"]`
-where "proxy2" is the furthest down-stream.
diff --git a/_includes/api/en/3x/req-is.md b/_includes/api/en/3x/req-is.md
deleted file mode 100644
index aa93c425cb..0000000000
--- a/_includes/api/en/3x/req-is.md
+++ /dev/null
@@ -1,21 +0,0 @@
-<h3 id='req.is'>req.is(type)</h3>
-
-Check if the incoming request contains the "Content-Type"
-header field, and it matches the give mime `type`.
-
-```js
-// With Content-Type: text/html; charset=utf-8
-req.is('html')
-req.is('text/html')
-req.is('text/*')
-// => true
-
-// When Content-Type is application/json
-req.is('json')
-req.is('application/json')
-req.is('application/*')
-// => true
-
-req.is('html')
-// => false
-```
diff --git a/_includes/api/en/3x/req-originalUrl.md b/_includes/api/en/3x/req-originalUrl.md
deleted file mode 100644
index d209148d87..0000000000
--- a/_includes/api/en/3x/req-originalUrl.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.originalUrl'>req.originalUrl</h3>
-
-This property is much like `req.url`, however it retains
-the original request url, allowing you to rewrite `req.url`
-freely for internal routing purposes. For example the "mounting" feature
-of <a href="#app.use">app.use()</a> will rewrite `req.url` to
-strip the mount point.
-
-```js
-// GET /search?q=something
-console.log(req.originalUrl)
-// => "/search?q=something"
-```
diff --git a/_includes/api/en/3x/req-param.md b/_includes/api/en/3x/req-param.md
deleted file mode 100644
index 5aaa22f80a..0000000000
--- a/_includes/api/en/3x/req-param.md
+++ /dev/null
@@ -1,27 +0,0 @@
-<h3 id='req.param'>req.param(name)</h3>
-
-Return the value of param `name` when present.
-
-```js
-// ?name=tobi
-req.param('name')
-// => "tobi"
-
-// POST name=tobi
-req.param('name')
-// => "tobi"
-
-// /user/tobi for /user/:name
-req.param('name')
-// => "tobi"
-```
-
-Lookup is performed in the following order:
-
-* `req.params`
-* `req.body`
-* `req.query`
-
-Direct access to `req.body`, `req.params`,
-and `req.query` should be favoured for clarity - unless
-you truly accept input from each object.
diff --git a/_includes/api/en/3x/req-params.md b/_includes/api/en/3x/req-params.md
deleted file mode 100644
index 408f8ef8b6..0000000000
--- a/_includes/api/en/3x/req-params.md
+++ /dev/null
@@ -1,22 +0,0 @@
-<h3 id='req.params'>req.params</h3>
-
-This property is an array containing properties mapped to the named route "parameters".
-For example if you have the route `/user/:name`, then the "name" property
-is available to you as `req.params.name`. This object defaults to `{}`.
-
-```js
-// GET /user/tj
-console.dir(req.params.name)
-// => 'tj'
-```
-
-When a regular expression is used for the route definition, capture groups
-are provided in the array using `req.params[N]`, where `N`
-is the nth capture group. This rule is applied to unnamed wild-card matches
-with string routes such as `/file/*`:
-
-```js
-// GET /file/javascripts/jquery.js
-console.dir(req.params[0])
-// => 'javascripts/jquery.js'
-```
diff --git a/_includes/api/en/3x/req-path.md b/_includes/api/en/3x/req-path.md
deleted file mode 100644
index 52f7ace8e4..0000000000
--- a/_includes/api/en/3x/req-path.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.path'>req.path</h3>
-
-Returns the request URL pathname.
-
-```js
-// example.com/users?sort=desc
-console.dir(req.path)
-// => '/users'
-```
diff --git a/_includes/api/en/3x/req-protocol.md b/_includes/api/en/3x/req-protocol.md
deleted file mode 100644
index 1090ab51cc..0000000000
--- a/_includes/api/en/3x/req-protocol.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.protocol'>req.protocol</h3>
-
-Return the protocol string "http" or "https"
-when requested with TLS. When the "trust proxy"
-setting is enabled the "X-Forwarded-Proto" header
-field will be trusted. If you're running behind
-a reverse proxy that supplies https for you this
-may be enabled.
-
-```js
-console.dir(req.protocol)
-// => 'http'
-```
diff --git a/_includes/api/en/3x/req-query.md b/_includes/api/en/3x/req-query.md
deleted file mode 100644
index 17c8a1dda8..0000000000
--- a/_includes/api/en/3x/req-query.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='req.query'>req.query</h3>
-
-This property is an object containing the parsed query-string,
-defaulting to `{}`.
-
-```js
-// GET /search?q=tobi+ferret
-console.dir(req.query.q)
-// => 'tobi ferret'
-
-// GET /shoes?order=desc&shoe[color]=blue&shoe[type]=converse
-console.dir(req.query.order)
-// => 'desc'
-
-console.dir(req.query.shoe.color)
-// => 'blue'
-
-console.dir(req.query.shoe.type)
-// => 'converse'
-```
diff --git a/_includes/api/en/3x/req-res.md b/_includes/api/en/3x/req-res.md
deleted file mode 100644
index b6f30a3aa0..0000000000
--- a/_includes/api/en/3x/req-res.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='req.res'>req.res</h3>
-
-This property holds a reference to the <a href="#response">response object</a>
-that relates to this request object.
diff --git a/_includes/api/en/3x/req-route.md b/_includes/api/en/3x/req-route.md
deleted file mode 100644
index bbb59f2de8..0000000000
--- a/_includes/api/en/3x/req-route.md
+++ /dev/null
@@ -1,22 +0,0 @@
-<h3 id='req.route'>req.route</h3>
-
-The currently matched `Route` containing
-several properties such as the route's original path
-string, the regexp generated, and so on.
-
-```js
-app.get('/user/:id?', function (req, res) {
-  console.dir(req.route)
-})
-```
-
-Example output from the previous snippet:
-
-```
-{ path: '/user/:id?',
-  method: 'get',
-  callbacks: [ [Function] ],
-  keys: [ { name: 'id', optional: true } ],
-  regexp: /^\/user(?:\/([^\/]+?))?\/?$/i,
-  params: [ id: '12' ] }
-```
diff --git a/_includes/api/en/3x/req-secure.md b/_includes/api/en/3x/req-secure.md
deleted file mode 100644
index d78bc954a0..0000000000
--- a/_includes/api/en/3x/req-secure.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='req.secure'>req.secure</h3>
-
-Check if a TLS connection is established. This is a short-hand for:
-
-```js
-console.dir(req.protocol === 'https')
-// => true
-```
diff --git a/_includes/api/en/3x/req-signedCookies.md b/_includes/api/en/3x/req-signedCookies.md
deleted file mode 100644
index a60f16061a..0000000000
--- a/_includes/api/en/3x/req-signedCookies.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='req.signedCookies'>req.signedCookies</h3>
-
-This object requires the `cookieParser(secret)` middleware for use.
-It contains signed cookies sent by the user-agent, unsigned and ready for use.
-Signed cookies reside in a different object to show developer intent; otherwise,
-a malicious attack could be placed on `req.cookie` values (which are easy to spoof).
-Note that signing a cookie does not make it "hidden" or encrypted; this simply
-prevents tampering (because the secret used to sign is private). If no signed
-cookies are sent, it defaults to `{}`.
-
-```js
-// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
-console.dir(req.signedCookies.user)
-// => 'tobi'
-```
diff --git a/_includes/api/en/3x/req-stale.md b/_includes/api/en/3x/req-stale.md
deleted file mode 100644
index c41d3df8c7..0000000000
--- a/_includes/api/en/3x/req-stale.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.stale'>req.stale</h3>
-
-Check if the request is stale - aka Last-Modified and/or the ETag do not match,
-indicating that the resource is "stale".
-
-```js
-console.dir(req.stale)
-// => true
-```
diff --git a/_includes/api/en/3x/req-subdomains.md b/_includes/api/en/3x/req-subdomains.md
deleted file mode 100644
index 5b405ac6e2..0000000000
--- a/_includes/api/en/3x/req-subdomains.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.subdomains'>req.subdomains</h3>
-
-Return subdomains as an array.
-
-```js
-// Host: "tobi.ferrets.example.com"
-console.dir(req.subdomains)
-// => ['ferrets', 'tobi']
-```
diff --git a/_includes/api/en/3x/req-xhr.md b/_includes/api/en/3x/req-xhr.md
deleted file mode 100644
index 05c8a4b30f..0000000000
--- a/_includes/api/en/3x/req-xhr.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.xhr'>req.xhr</h3>
-
-Check if the request was issued with the "X-Requested-With"
-header field set to "XMLHttpRequest" (jQuery etc).
-
-```js
-console.dir(req.xhr)
-// => true
-```
diff --git a/_includes/api/en/3x/req.md b/_includes/api/en/3x/req.md
deleted file mode 100644
index 115d5dd721..0000000000
--- a/_includes/api/en/3x/req.md
+++ /dev/null
@@ -1,116 +0,0 @@
-<h2 id="request">Request</h2>
-
-The `req` object is an enhanced version of Node's own request object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).
-
-<section markdown="1">
-  {% include api/en/3x/req-params.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-query.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-body.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-files.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-cookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-signedCookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-header.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-accepts.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-accepted.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-is.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-ip.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-ips.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-path.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-host.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-fresh.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-stale.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-xhr.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-protocol.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-secure.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-subdomains.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-originalUrl.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-acceptedLanguages.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-acceptedCharsets.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-acceptsCharset.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-acceptsLanguage.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/req-res.md %}
-</section>
diff --git a/_includes/api/en/3x/res-attachment.md b/_includes/api/en/3x/res-attachment.md
deleted file mode 100644
index d52e3bba6f..0000000000
--- a/_includes/api/en/3x/res-attachment.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='res.attachment'>res.attachment([filename])</h3>
-
-Sets the Content-Disposition header field to "attachment". If
-a `filename` is given then the Content-Type will be
-automatically set based on the extname via `res.type()`,
-and the Content-Disposition's "filename=" parameter will be set.
-
-```js
-res.attachment()
-// Content-Disposition: attachment
-
-res.attachment('path/to/logo.png')
-// Content-Disposition: attachment; filename="logo.png"
-// Content-Type: image/png
-```
diff --git a/_includes/api/en/3x/res-charset.md b/_includes/api/en/3x/res-charset.md
deleted file mode 100644
index 07d0a35e95..0000000000
--- a/_includes/api/en/3x/res-charset.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='res.charset'>res.charset</h3>
-
-Assign the charset. Defaults to "utf-8".
-
-```js
-res.charset = 'value'
-res.send('<p>some html</p>')
-// => Content-Type: text/html; charset=value
-```
diff --git a/_includes/api/en/3x/res-clearCookie.md b/_includes/api/en/3x/res-clearCookie.md
deleted file mode 100644
index afb139628d..0000000000
--- a/_includes/api/en/3x/res-clearCookie.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='res.clearCookie'>res.clearCookie(name, [options])</h3>
-
-Clear cookie `name`. The `path` option defaults to "/".
-
-```js
-res.cookie('name', 'tobi', { path: '/admin' })
-res.clearCookie('name', { path: '/admin' })
-```
diff --git a/_includes/api/en/3x/res-cookie.md b/_includes/api/en/3x/res-cookie.md
deleted file mode 100644
index 5f6eb0186c..0000000000
--- a/_includes/api/en/3x/res-cookie.md
+++ /dev/null
@@ -1,37 +0,0 @@
-<h3 id='res.cookie'>res.cookie(name, value, [options])</h3>
-
-Set cookie `name` to `value`, which may be a string or object converted to JSON. The `path`
-option defaults to "/".
-
-```js
-res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true })
-res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true })
-```
-
-The `maxAge` option is a convenience option for setting "expires"
-relative to the current time in milliseconds. The following is equivalent to
-the previous example.
-
-```js
-res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true })
-```
-
-An object may be passed which is then serialized as JSON, which is
-automatically parsed by the `bodyParser()` middleware.
-
-```js
-res.cookie('cart', { items: [1, 2, 3] })
-res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 })
-```
-
-Signed cookies are also supported through this method. Simply
-pass the `signed` option. When given `res.cookie()`
-will use the secret passed to `express.cookieParser(secret)`
-to sign the value.
-
-```js
-res.cookie('name', 'tobi', { signed: true })
-```
-
-Later you may access this value through the <a href="#req.signedCookies">req.signedCookie</a>
-object.
diff --git a/_includes/api/en/3x/res-download.md b/_includes/api/en/3x/res-download.md
deleted file mode 100644
index 43d48f769d..0000000000
--- a/_includes/api/en/3x/res-download.md
+++ /dev/null
@@ -1,26 +0,0 @@
-<h3 id='res.download'>res.download(path, [filename], [fn])</h3>
-
-Transfer the file at `path` as an "attachment",
-typically browsers will prompt the user for download. The
-Content-Disposition "filename=" parameter, aka the one
-that will appear in the brower dialog is set to `path`
-by default, however you may provide an override `filename`.
-
-When an error has ocurred or transfer is complete the optional
-callback `fn` is invoked. This method uses <a href="#res.sendfile">res.sendfile()</a>
-to transfer the file.
-
-```js
-res.download('/report-12345.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf', function (err) {
-  if (err) {
-    // handle error, keep in mind the response may be partially-sent
-    // so check res.headerSent
-  } else {
-    // decrement a download credit etc
-  }
-})
-```
diff --git a/_includes/api/en/3x/res-format.md b/_includes/api/en/3x/res-format.md
deleted file mode 100644
index 5092c626a1..0000000000
--- a/_includes/api/en/3x/res-format.md
+++ /dev/null
@@ -1,52 +0,0 @@
-<h3 id='res.format'>res.format(object)</h3>
-
-Performs content-negotiation on the request Accept header
-field when present. This method uses `req.accepted`, an array of
-acceptable types ordered by their quality values, otherwise the
-first callback is invoked. When no match is performed the server
-responds with 406 "Not Acceptable", or invokes the `default`
-callback.
-
-The Content-Type is set for you when a callback is selected,
-however you may alter this within the callback using `res.set()`
-or `res.type()` etcetera.
-
-The following example would respond with `{ "message": "hey" }`
-when the Accept header field is set to "application/json" or "*/json",
-however if "*/*" is given then "hey" will be the response.
-
-```js
-res.format({
-  'text/plain': function () {
-    res.send('hey')
-  },
-
-  'text/html': function () {
-    res.send('<p>hey</p>')
-  },
-
-  'application/json': function () {
-    res.send({ message: 'hey' })
-  }
-})
-```
-
-In addition to canonicalized MIME types you may also
-use extnames mapped to these types, providing a slightly
-less verbose implementation:
-
-```js
-res.format({
-  text: function () {
-    res.send('hey')
-  },
-
-  html: function () {
-    res.send('<p>hey</p>')
-  },
-
-  json: function () {
-    res.send({ message: 'hey' })
-  }
-})
-```
diff --git a/_includes/api/en/3x/res-get.md b/_includes/api/en/3x/res-get.md
deleted file mode 100644
index 2dbf992020..0000000000
--- a/_includes/api/en/3x/res-get.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='res.get'>res.get(field)</h3>
-
-Get the case-insensitive response header `field`.
-
-```js
-res.get('Content-Type')
-// => "text/plain"
-```
diff --git a/_includes/api/en/3x/res-json.md b/_includes/api/en/3x/res-json.md
deleted file mode 100644
index d13bb2ab0b..0000000000
--- a/_includes/api/en/3x/res-json.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='res.json'>res.json([status|body], [body])</h3>
-
-Send a JSON response. This method is identical
-to `res.send()` when an object or
-array is passed, however it may be used for
-explicit JSON conversion of non-objects (null, undefined, etc),
-though these are technically not valid JSON.
-
-```js
-res.json(null)
-res.json({ user: 'tobi' })
-res.json(500, { error: 'message' })
-```
diff --git a/_includes/api/en/3x/res-jsonp.md b/_includes/api/en/3x/res-jsonp.md
deleted file mode 100644
index 5340c4487d..0000000000
--- a/_includes/api/en/3x/res-jsonp.md
+++ /dev/null
@@ -1,33 +0,0 @@
-<h3 id='res.jsonp'>res.jsonp([status|body], [body])</h3>
-
-Send a JSON response with JSONP support. This method is identical
-to `res.json()` however opts-in to JSONP callback
-support.
-
-```js
-res.jsonp(null)
-// => null
-
-res.jsonp({ user: 'tobi' })
-// => { "user": "tobi" }
-
-res.jsonp(500, { error: 'message' })
-// => { "error": "message" }
-```
-
-By default the JSONP callback name is simply `callback`,
-however you may alter this with the <a href="#app-settings">jsonp callback name</a>
-setting. The following are some examples of JSONP responses using the same
-code:
-
-```js
-// ?callback=foo
-res.jsonp({ user: 'tobi' })
-// => foo({ "user": "tobi" })
-
-app.set('jsonp callback name', 'cb')
-
-// ?cb=foo
-res.jsonp(500, { error: 'message' })
-// => foo({ "error": "message" })
-```
diff --git a/_includes/api/en/3x/res-links.md b/_includes/api/en/3x/res-links.md
deleted file mode 100644
index 2b8c734b24..0000000000
--- a/_includes/api/en/3x/res-links.md
+++ /dev/null
@@ -1,17 +0,0 @@
-<h3 id='res.links'>res.links(links)</h3>
-
-Join the given `links` to populate the "Link" response header field.
-
-```js
-res.links({
-  next: 'http://api.example.com/users?page=2',
-  last: 'http://api.example.com/users?page=5'
-})
-```
-
-p yields:
-
-```
-Link: <http://api.example.com/users?page=2> rel="next",
-      <http://api.example.com/users?page=5> rel="last"
-```
diff --git a/_includes/api/en/3x/res-locals.md b/_includes/api/en/3x/res-locals.md
deleted file mode 100644
index 5c6dbfbf95..0000000000
--- a/_includes/api/en/3x/res-locals.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.locals'>res.locals</h3>
-
-Response local variables are scoped to the request, thus only
-available to the view(s) rendered during that request / response
-cycle, if any. Otherwise this API is identical to <a href="#app.locals">app.locals</a>.
-
-This object is useful for exposing request-level information such as the
-request pathname, authenticated user, user settings etcetera.
-
-```js
-app.use(function (req, res, next) {
-  res.locals.user = req.user
-  res.locals.authenticated = !req.user.anonymous
-  next()
-})
-```
diff --git a/_includes/api/en/3x/res-location.md b/_includes/api/en/3x/res-location.md
deleted file mode 100644
index 60b59db930..0000000000
--- a/_includes/api/en/3x/res-location.md
+++ /dev/null
@@ -1,21 +0,0 @@
-<h3 id='res.location'>res.location</h3>
-
-Set the location header.
-
-```js
-res.location('/foo/bar')
-res.location('foo/bar')
-res.location('http://example.com')
-res.location('../login')
-res.location('back')
-```
-
-You can use the same kind of `urls` as in `res.redirect()`.
-
-For example, if your application is mounted at `/blog`,
-the following would set the `location` header to
-`/blog/admin`:
-
-```js
-res.location('admin')
-```
diff --git a/_includes/api/en/3x/res-redirect.md b/_includes/api/en/3x/res-redirect.md
deleted file mode 100644
index dc87d689c2..0000000000
--- a/_includes/api/en/3x/res-redirect.md
+++ /dev/null
@@ -1,51 +0,0 @@
-<h3 id='res.redirect'>res.redirect([status], url)</h3>
-
-Redirect to the given `url` with optional `status` code
-defaulting to 302 "Found".
-
-```js
-res.redirect('/foo/bar')
-res.redirect('http://example.com')
-res.redirect(301, 'http://example.com')
-res.redirect('../login')
-```
-
-Express supports a few forms of redirection, first being
-a fully qualified URI for redirecting to a different site:
-
-```js
-res.redirect('http://google.com')
-```
-
-The second form is the pathname-relative redirect, for example
-if you were on `http://example.com/admin/post/new`, the
-following redirect to `/admin` would land you at `http://example.com/admin`:
-
-```js
-res.redirect('/admin')
-```
-
-This next redirect is relative to the `mount` point of the application. For example
-if you have a blog application mounted at `/blog`, ideally it has no knowledge of
-where it was mounted, so where a redirect of `/admin/post/new` would simply give you
-`http://example.com/admin/post/new`, the following mount-relative redirect would give
-you `http://example.com/blog/admin/post/new`:
-
-```js
-res.redirect('admin/post/new')
-```
-
-Pathname relative redirects are also possible. If you were
-on `http://example.com/admin/post/new`, the following redirect
-would land you at `http//example.com/admin/post`:
-
-```js
-res.redirect('..')
-```
-
-The final special-case is a `back` redirect, redirecting back to
-the Referer (or Referrer), defaulting to `/` when missing.
-
-```js
-res.redirect('back')
-```
diff --git a/_includes/api/en/3x/res-render.md b/_includes/api/en/3x/res-render.md
deleted file mode 100644
index e87cba9f3e..0000000000
--- a/_includes/api/en/3x/res-render.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.render'>res.render(view, [locals], callback)</h3>
-
-Render a `view` with a callback responding with
-the rendered string. When an error occurs `next(err)`
-is invoked internally. When a callback is provided both the possible error
-and rendered string are passed, and no automated response is performed.
-
-```js
-res.render('index', function (err, html) {
-  // ...
-})
-
-res.render('user', { name: 'Tobi' }, function (err, html) {
-  // ...
-})
-```
diff --git a/_includes/api/en/3x/res-req.md b/_includes/api/en/3x/res-req.md
deleted file mode 100644
index 6c0236cdc1..0000000000
--- a/_includes/api/en/3x/res-req.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='res.req'>res.req</h3>
-
-This property holds a reference to the <a href="#request">request object</a>
-that relates to this response object.
diff --git a/_includes/api/en/3x/res-send.md b/_includes/api/en/3x/res-send.md
deleted file mode 100644
index 75903b13cb..0000000000
--- a/_includes/api/en/3x/res-send.md
+++ /dev/null
@@ -1,53 +0,0 @@
-<h3 id='res.send'>res.send([body|status], [body])</h3>
-
-Send a response.
-
-```js
-res.send(Buffer.from('whoop'))
-res.send({ some: 'json' })
-res.send('<p>some html</p>')
-res.send(404, 'Sorry, we cannot find that!')
-res.send(500, { error: 'something blew up' })
-res.send(200)
-```
-
-This method performs a myriad of
-useful tasks for simple non-streaming responses such
-as automatically assigning the Content-Length unless
-previously defined and providing automatic <em>HEAD</em> and
-HTTP cache freshness support.
-
-When a `Buffer` is given
-the Content-Type is set to "application/octet-stream"
-unless previously defined as shown below:
-
-```js
-res.set('Content-Type', 'text/html')
-res.send(Buffer.from('<p>some html</p>'))
-```
-
-When a `String` is given the
-Content-Type is set defaulted to "text/html":
-
-```js
-res.send('<p>some html</p>')
-```
-
-When an `Array` or `Object` is
-given Express will respond with the JSON representation:
-
-```js
-res.send({ user: 'tobi' })
-res.send([1, 2, 3])
-```
-
-Finally when a `Number` is given without
-any of the previously mentioned bodies, then a response
-body string is assigned for you. For example 200 will
-respond will the text "OK", and 404 "Not Found" and so on.
-
-```js
-res.send(200)
-res.send(404)
-res.send(500)
-```
diff --git a/_includes/api/en/3x/res-sendfile.md b/_includes/api/en/3x/res-sendfile.md
deleted file mode 100644
index 0580a98b48..0000000000
--- a/_includes/api/en/3x/res-sendfile.md
+++ /dev/null
@@ -1,30 +0,0 @@
-<h3 id='res.sendfile'>res.sendfile(path, [options], [fn]])</h3>
-
-Transfer the file at the given `path`.
-
-Automatically defaults the Content-Type response header field based
-on the filename's extension. The callback `fn(err)` is
-invoked when the transfer is complete or when an error occurs.
-
-Options:
-
-* `maxAge` in milliseconds defaulting to 0
-* `root` root directory for relative filenames
-
-This method provides fine-grained support for file serving
-as illustrated in the following example:
-
-```js
-app.get('/user/:uid/photos/:file', function (req, res) {
-  var uid = req.params.uid
-  var file = req.params.file
-
-  req.user.mayViewFilesFrom(uid, function (yes) {
-    if (yes) {
-      res.sendfile('/uploads/' + uid + '/' + file)
-    } else {
-      res.send(403, 'Sorry! you cant see that.')
-    }
-  })
-})
-```
diff --git a/_includes/api/en/3x/res-set.md b/_includes/api/en/3x/res-set.md
deleted file mode 100644
index 76ca5086b1..0000000000
--- a/_includes/api/en/3x/res-set.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='res.set'>res.set(field, [value])</h3>
-
-Set header `field` to `value`, or pass an object to set multiple fields at once.
-
-```js
-res.set('Content-Type', 'text/plain')
-
-res.set({
-  'Content-Type': 'text/plain',
-  'Content-Length': '123',
-  ETag: '12345'
-})
-```
-
-Aliased as `res.header(field, [value])`.
diff --git a/_includes/api/en/3x/res-status.md b/_includes/api/en/3x/res-status.md
deleted file mode 100644
index 3be23e5138..0000000000
--- a/_includes/api/en/3x/res-status.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='res.status'>res.status(code)</h3>
-
-Chainable alias of node's `res.statusCode=`.
-
-```js
-res.status(404).sendfile('path/to/404.png')
-```
diff --git a/_includes/api/en/3x/res-type.md b/_includes/api/en/3x/res-type.md
deleted file mode 100644
index d686d65105..0000000000
--- a/_includes/api/en/3x/res-type.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='res.type'>res.type(type)</h3>
-
-Sets the Content-Type to the mime lookup of `type`,
-or when "/" is present the Content-Type is simply set to this
-literal value.
-
-```js
-res.type('.html')
-res.type('html')
-res.type('json')
-res.type('application/json')
-res.type('png')
-```
-
-p Aliased as `res.contentType(type)`.
diff --git a/_includes/api/en/3x/res.md b/_includes/api/en/3x/res.md
deleted file mode 100644
index b56f9fb7d6..0000000000
--- a/_includes/api/en/3x/res.md
+++ /dev/null
@@ -1,84 +0,0 @@
-<h2 id="response">Response</h2>
-
-The `res` object is an enhanced version of Node's own response object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
-
-<section markdown="1">
-  {% include api/en/3x/res-status.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-cookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-clearCookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-redirect.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-location.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-charset.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-send.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-json.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-jsonp.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-type.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-format.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-attachment.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-sendfile.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-download.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-links.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-locals.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-render.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/3x/res-req.md %}
-</section>
diff --git a/_includes/api/en/4x/app-METHOD.md b/_includes/api/en/4x/app-METHOD.md
deleted file mode 100644
index c526a04d11..0000000000
--- a/_includes/api/en/4x/app-METHOD.md
+++ /dev/null
@@ -1,60 +0,0 @@
-<h3 id='app.METHOD'>app.METHOD(path, callback [, callback ...])</h3>
-
-Routes an HTTP request, where METHOD is the HTTP method of the request, such as GET,
-PUT, POST, and so on, in lowercase. Thus, the actual methods are `app.get()`,
-`app.post()`, `app.put()`, and so on.  See [Routing methods](#routing-methods) below for the complete list.
-
-{% include api/en/4x/routing-args.html %}
-
-#### Routing methods
-
-Express supports the following routing methods corresponding to the HTTP methods of the same names:
-
-<div class="methods-columns">
-  <ul>
-    <li><code>checkout</code></li>
-    <li><code>copy</code></li>
-    <li><code>delete</code></li>
-    <li><code>get</code></li>
-    <li><code>head</code></li>
-    <li><code>lock</code></li>
-    <li><code>merge</code></li>
-    <li><code>mkactivity</code></li>
-  </ul>
-  <ul>
-    <li><code>mkcol</code></li>
-    <li><code>move</code></li>
-    <li><code>m-search</code></li>
-    <li><code>notify</code></li>
-    <li><code>options</code></li>
-    <li><code>patch</code></li>
-    <li><code>post</code></li>
-  </ul>
-  <ul>
-    <li><code>purge</code></li>
-    <li><code>put</code></li>
-    <li><code>report</code></li>
-    <li><code>search</code></li>
-    <li><code>subscribe</code></li>
-    <li><code>trace</code></li>
-    <li><code>unlock</code></li>
-    <li><code>unsubscribe</code></li>
-  </ul>
-</div>
-
-The API documentation has explicit entries only for the most popular HTTP methods `app.get()`,
-`app.post()`, `app.put()`, and `app.delete()`.
-However, the other methods listed above work in exactly the same way.
-
-To route methods that translate to invalid JavaScript variable names, use the bracket notation. For example, `app['m-search']('/', function ...`.
-
-<div class="doc-box doc-info" markdown="1">
-  The `app.get()` function is automatically called for the HTTP `HEAD` method in addition to the `GET`
-  method if `app.head()` was not called for the path before `app.get()`.
-</div>
-
-The method, `app.all()`, is not derived from any HTTP method and loads middleware at
-the specified path for _all_ HTTP request methods.
-For more information, see [app.all](#app.all).
-
-For more information on routing, see the [routing guide](/{{page.lang}}/guide/routing.html).
diff --git a/_includes/api/en/4x/app-all.md b/_includes/api/en/4x/app-all.md
deleted file mode 100644
index 2939bd6f07..0000000000
--- a/_includes/api/en/4x/app-all.md
+++ /dev/null
@@ -1,44 +0,0 @@
-<h3 id='app.all'>app.all(path, callback [, callback ...])</h3>
-
-This method is like the standard [app.METHOD()](#app.METHOD) methods,
-except it matches all HTTP verbs.
-
-{% include api/en/4x/routing-args.html %}
-
-#### Examples
-
-The following callback is executed for requests to `/secret` whether using
-GET, POST, PUT, DELETE, or any other HTTP request method:
-
-```js
-app.all('/secret', function (req, res, next) {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-The `app.all()` method is useful for mapping "global" logic for specific path prefixes or arbitrary matches.  For example, if you put the following at the top of all other
-route definitions, it requires that all routes from that point on
-require authentication, and automatically load a user. Keep in mind
-that these callbacks do not have to act as end-points: `loadUser`
-can perform a task, then call `next()` to continue matching subsequent
-routes.
-
-```js
-app.all('*', requireAuthentication, loadUser)
-```
-
-Or the equivalent:
-
-```js
-app.all('*', requireAuthentication)
-app.all('*', loadUser)
-```
-
-Another example is white-listed "global" functionality.
-The example is similar to the ones above, but it only restricts paths that start with
-"/api":
-
-```js
-app.all('/api/*', requireAuthentication)
-```
diff --git a/_includes/api/en/4x/app-delete-method.md b/_includes/api/en/4x/app-delete-method.md
deleted file mode 100644
index 0d9e5cbcc0..0000000000
--- a/_includes/api/en/4x/app-delete-method.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='app.delete.method'>app.delete(path, callback [, callback ...])</h3>
-
-Routes HTTP DELETE requests to the specified path with the specified callback functions.
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-{% include api/en/4x/routing-args.html %}
-
-#### Example
-
-```js
-app.delete('/', function (req, res) {
-  res.send('DELETE request to homepage')
-})
-```
diff --git a/_includes/api/en/4x/app-disable.md b/_includes/api/en/4x/app-disable.md
deleted file mode 100644
index 08bbcf11ba..0000000000
--- a/_includes/api/en/4x/app-disable.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='app.disable'>app.disable(name)</h3>
-
-Sets the Boolean setting `name` to `false`, where `name` is one of the properties from the [app settings table](#app.settings.table).
-Calling `app.set('foo', false)` for a Boolean property is the same as calling `app.disable('foo')`.
-
-For example:
-
-```js
-app.disable('trust proxy')
-app.get('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/4x/app-disabled.md b/_includes/api/en/4x/app-disabled.md
deleted file mode 100644
index 370048fde6..0000000000
--- a/_includes/api/en/4x/app-disabled.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.disabled'>app.disabled(name)</h3>
-
-Returns `true` if the Boolean setting `name` is disabled (`false`), where `name` is one of the properties from
-the [app settings table](#app.settings.table).
-
-```js
-app.disabled('trust proxy')
-// => true
-
-app.enable('trust proxy')
-app.disabled('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/4x/app-enable.md b/_includes/api/en/4x/app-enable.md
deleted file mode 100644
index 1152335a4c..0000000000
--- a/_includes/api/en/4x/app-enable.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='app.enable'>app.enable(name)</h3>
-
-Sets the Boolean setting `name` to `true`, where `name` is one of the properties from the [app settings table](#app.settings.table).
-Calling `app.set('foo', true)` for a Boolean property is the same as calling `app.enable('foo')`.
-
-```js
-app.enable('trust proxy')
-app.get('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/4x/app-enabled.md b/_includes/api/en/4x/app-enabled.md
deleted file mode 100644
index ad9b17aa89..0000000000
--- a/_includes/api/en/4x/app-enabled.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.enabled'>app.enabled(name)</h3>
-
-Returns `true` if the setting `name` is enabled (`true`), where `name` is one of the
-properties from the [app settings table](#app.settings.table).
-
-```js
-app.enabled('trust proxy')
-// => false
-
-app.enable('trust proxy')
-app.enabled('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/4x/app-engine.md b/_includes/api/en/4x/app-engine.md
deleted file mode 100644
index 4906a254f1..0000000000
--- a/_includes/api/en/4x/app-engine.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='app.engine'>app.engine(ext, callback)</h3>
-
-Registers the given template engine `callback` as `ext`.
-
-By default, Express will `require()` the engine based on the file extension.
-For example, if you try to render a "foo.pug" file, Express invokes the
-following internally, and caches the `require()` on subsequent calls to increase
-performance.
-
-```js
-app.engine('pug', require('pug').__express)
-```
-
-Use this method for engines that do not provide `.__express` out of the box,
-or if you wish to "map" a different extension to the template engine.
-
-For example, to map the EJS template engine to ".html" files:
-
-```js
-app.engine('html', require('ejs').renderFile)
-```
-
-In this case, EJS provides a `.renderFile()` method with
-the same signature that Express expects: `(path, options, callback)`,
-though note that it aliases this method as `ejs.__express` internally
-so if you're using ".ejs" extensions you don't need to do anything.
-
-Some template engines do not follow this convention.  The
-[consolidate.js](https://github.com/tj/consolidate.js) library maps Node template engines to follow this convention,
-so they work seamlessly with Express.
-
-```js
-var engines = require('consolidate')
-app.engine('haml', engines.haml)
-app.engine('html', engines.hogan)
-```
diff --git a/_includes/api/en/4x/app-get-method.md b/_includes/api/en/4x/app-get-method.md
deleted file mode 100644
index 37c61c342c..0000000000
--- a/_includes/api/en/4x/app-get-method.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='app.get.method'>app.get(path, callback [, callback ...])</h3>
-
-Routes HTTP GET requests to the specified path with the specified callback functions.
-
-{% include api/en/4x/routing-args.html %}
-
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-#### Example
-
-```js
-app.get('/', function (req, res) {
-  res.send('GET request to homepage')
-})
-```
diff --git a/_includes/api/en/4x/app-get.md b/_includes/api/en/4x/app-get.md
deleted file mode 100644
index c93ef34d70..0000000000
--- a/_includes/api/en/4x/app-get.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.get'>app.get(name)</h3>
-
-Returns the value of `name` app setting, where `name` is one of the strings in the
-[app settings table](#app.settings.table). For example:
-
-```js
-app.get('title')
-// => undefined
-
-app.set('title', 'My Site')
-app.get('title')
-// => "My Site"
-```
diff --git a/_includes/api/en/4x/app-listen.md b/_includes/api/en/4x/app-listen.md
deleted file mode 100644
index 26bde4121b..0000000000
--- a/_includes/api/en/4x/app-listen.md
+++ /dev/null
@@ -1,53 +0,0 @@
-<h3 id='app.listen_path_callback'>app.listen(path, [callback])</h3>
-
-Starts a UNIX socket and listens for connections on the given path.
-This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
-
-```js
-var express = require('express')
-var app = express()
-app.listen('/tmp/sock')
-```
-
-<h3 id='app.listen'>app.listen([port[, host[, backlog]]][, callback])</h3>
-
-Binds and listens for connections on the specified host and port.
-This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
-
-If port is omitted or is 0, the operating system will assign an arbitrary unused
-port, which is useful for cases like automated tasks (tests, etc.).
-
-```js
-var express = require('express')
-var app = express()
-app.listen(3000)
-```
-
-The `app` returned by `express()` is in fact a JavaScript
-`Function`, designed to be passed to Node's HTTP servers as a callback
-to handle requests. This makes it easy to provide both HTTP and HTTPS versions of
-your app with the same code base, as the app does not inherit from these
-(it is simply a callback):
-
-```js
-var express = require('express')
-var https = require('https')
-var http = require('http')
-var app = express()
-
-http.createServer(app).listen(80)
-https.createServer(options, app).listen(443)
-```
-
-The `app.listen()` method returns an [http.Server](https://nodejs.org/api/http.html#http_class_http_server) object and (for HTTP) is a convenience method for the following:
-
-```js
-app.listen = function () {
-  var server = http.createServer(this)
-  return server.listen.apply(server, arguments)
-}
-```
-
-{% include admonitions/note.html content="All the forms of Node's
-[http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen)
-method are in fact actually supported." %}
diff --git a/_includes/api/en/4x/app-locals.md b/_includes/api/en/4x/app-locals.md
deleted file mode 100644
index 178d640054..0000000000
--- a/_includes/api/en/4x/app-locals.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<h3 id='app.locals'>app.locals</h3>
-
-The `app.locals` object has properties that are local variables within the application,
-and will be available in templates rendered with [res.render](#res.render).
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-```js
-console.dir(app.locals.title)
-// => 'My App'
-
-console.dir(app.locals.email)
-// => 'me@myapp.com'
-```
-
-Once set, the value of `app.locals` properties persist throughout the life of the application,
-in contrast with [res.locals](#res.locals) properties that
-are valid only for the lifetime of the request.
-
-You can access local variables in templates rendered within the application.
-This is useful for providing helper functions to templates, as well as application-level data.
-Local variables are available in middleware via `req.app.locals` (see [req.app](#req.app))
-
-```js
-app.locals.title = 'My App'
-app.locals.strftime = require('strftime')
-app.locals.email = 'me@myapp.com'
-```
diff --git a/_includes/api/en/4x/app-mountpath.md b/_includes/api/en/4x/app-mountpath.md
deleted file mode 100644
index 2ccdd57202..0000000000
--- a/_includes/api/en/4x/app-mountpath.md
+++ /dev/null
@@ -1,45 +0,0 @@
-<h3 id='app.mountpath'>app.mountpath</h3>
-
-The `app.mountpath` property contains one or more path patterns on which a sub-app was mounted.
-
-<div class="doc-box doc-info" markdown="1">
-  A sub-app is an instance of `express` that may be used for handling the request to a route.
-</div>
-
-```js
-var express = require('express')
-
-var app = express() // the main app
-var admin = express() // the sub app
-
-admin.get('/', function (req, res) {
-  console.log(admin.mountpath) // /admin
-  res.send('Admin Homepage')
-})
-
-app.use('/admin', admin) // mount the sub app
-```
-
-It is similar to the [baseUrl](#req.baseUrl) property of the `req` object, except `req.baseUrl`
-returns the matched URL path, instead of the matched patterns.
-
-If a sub-app is mounted on multiple path patterns, `app.mountpath` returns the list of
-patterns it is mounted on, as shown in the following example.
-
-```js
-var admin = express()
-
-admin.get('/', function (req, res) {
-  console.dir(admin.mountpath) // [ '/adm*n', '/manager' ]
-  res.send('Admin Homepage')
-})
-
-var secret = express()
-secret.get('/', function (req, res) {
-  console.log(secret.mountpath) // /secr*t
-  res.send('Admin Secret')
-})
-
-admin.use('/secr*t', secret) // load the 'secret' router on '/secr*t', on the 'admin' sub app
-app.use(['/adm*n', '/manager'], admin) // load the 'admin' router on '/adm*n' and '/manager', on the parent app
-```
diff --git a/_includes/api/en/4x/app-onmount.md b/_includes/api/en/4x/app-onmount.md
deleted file mode 100644
index 8275cf19b3..0000000000
--- a/_includes/api/en/4x/app-onmount.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<h3 id='app.onmount'>app.on('mount', callback(parent))</h3>
-
-The `mount` event is fired on a sub-app, when it is mounted on a parent app. The parent app is passed to the callback function.
-
-<div class="doc-box doc-info" markdown="1">
-**NOTE**
-
-Sub-apps will:
-
-* Not inherit the value of settings that have a default value.  You must set the value in the sub-app.
-* Inherit the value of settings with no default value.
-
-For details, see [Application settings](/en/4x/api.html#app.settings.table).
-</div>
-
-```js
-var admin = express()
-
-admin.on('mount', function (parent) {
-  console.log('Admin Mounted')
-  console.log(parent) // refers to the parent app
-})
-
-admin.get('/', function (req, res) {
-  res.send('Admin Homepage')
-})
-
-app.use('/admin', admin)
-```
diff --git a/_includes/api/en/4x/app-param.md b/_includes/api/en/4x/app-param.md
deleted file mode 100644
index 2b0d8bf2aa..0000000000
--- a/_includes/api/en/4x/app-param.md
+++ /dev/null
@@ -1,154 +0,0 @@
-<h3 id='app.param'>app.param([name], callback)</h3>
-
-Add callback triggers to [route parameters](/{{ page.lang }}/guide/routing.html#route-parameters), where `name` is the name of the parameter or an array of them, and `callback` is the callback function. The parameters of the callback function are the request object, the response object, the next middleware, the value of the parameter and the name of the parameter, in that order.
-
-If `name` is an array, the `callback` trigger is registered for each parameter declared in it, in the order in which they are declared. Furthermore, for each declared parameter except the last one, a call to `next` inside the callback will call the callback for the next declared parameter. For the last parameter, a call to `next` will call the next middleware in place for the route currently being processed, just like it would if `name` were just a string.
-
-For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
-
-```js
-app.param('user', function (req, res, next, id) {
-  // try to get the user details from the User model and attach it to the request object
-  User.find(id, function (err, user) {
-    if (err) {
-      next(err)
-    } else if (user) {
-      req.user = user
-      next()
-    } else {
-      next(new Error('failed to load user'))
-    }
-  })
-})
-```
-
-Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `app` will be triggered only by route parameters defined on `app` routes.
-
-All param callbacks will be called before any handler of any route in which the param occurs, and they will each be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
-
-```js
-app.param('id', function (req, res, next, id) {
-  console.log('CALLED ONLY ONCE')
-  next()
-})
-
-app.get('/user/:id', function (req, res, next) {
-  console.log('although this matches')
-  next()
-})
-
-app.get('/user/:id', function (req, res) {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42`, the following is printed:
-
-```
-CALLED ONLY ONCE
-although this matches
-and this matches too
-```
-
-```js
-app.param(['id', 'page'], function (req, res, next, value) {
-  console.log('CALLED ONLY ONCE with', value)
-  next()
-})
-
-app.get('/user/:id/:page', function (req, res, next) {
-  console.log('although this matches')
-  next()
-})
-
-app.get('/user/:id/:page', function (req, res) {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42/3`, the following is printed:
-
-```
-CALLED ONLY ONCE with 42
-CALLED ONLY ONCE with 3
-although this matches
-and this matches too
-```
-
-<div class="doc-box doc-warn" markdown="1">
-The following section describes `app.param(callback)`, which is deprecated as of v4.11.0.
-</div>
-
-The behavior of the `app.param(name, callback)` method can be altered entirely by passing only a function to `app.param()`. This function is a custom implementation of how `app.param(name, callback)` should behave - it accepts two parameters and must return a middleware.
-
-The first parameter of this function is the name of the URL parameter that should be captured, the second parameter can be any JavaScript object which might be used for returning the middleware implementation.
-
-The middleware returned by the function decides the behavior of what happens when a URL parameter is captured.
-
-In this example, the `app.param(name, callback)` signature is modified to `app.param(name, accessId)`. Instead of accepting a name and a callback, `app.param()` will now accept a name and a number.
-
-```js
-var express = require('express')
-var app = express()
-
-// customizing the behavior of app.param()
-app.param(function (param, option) {
-  return function (req, res, next, val) {
-    if (val === option) {
-      next()
-    } else {
-      next('route')
-    }
-  }
-})
-
-// using the customized app.param()
-app.param('id', 1337)
-
-// route to trigger the capture
-app.get('/user/:id', function (req, res) {
-  res.send('OK')
-})
-
-app.listen(3000, function () {
-  console.log('Ready')
-})
-```
-
-In this example, the `app.param(name, callback)` signature remains the same, but instead of a middleware callback, a custom data type checking function has been defined to validate the data type of the user id.
-
-```js
-app.param(function (param, validator) {
-  return function (req, res, next, val) {
-    if (validator(val)) {
-      next()
-    } else {
-      next('route')
-    }
-  }
-})
-
-app.param('id', function (candidate) {
-  return !isNaN(parseFloat(candidate)) && isFinite(candidate)
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-The '`.`' character can't be used to capture a character in your capturing regexp. For example you can't use `'/user-.+/'` to capture `'users-gami'`, use `[\\s\\S]` or `[\\w\\W]` instead (as in `'/user-[\\s\\S]+/'`.
-
-Examples:
-
-```js
-// captures '1-a_6' but not '543-azser-sder'
-router.get('/[0-9]+-[[\\w]]*', function (req, res, next) { next() })
-
-// captures '1-a_6' and '543-az(ser"-sder' but not '5-a s'
-router.get('/[0-9]+-[[\\S]]*', function (req, res, next) { next() })
-
-// captures all (equivalent to '.*')
-router.get('[[\\s\\S]]*', function (req, res, next) { next() })
-```
-
-</div>
diff --git a/_includes/api/en/4x/app-path.md b/_includes/api/en/4x/app-path.md
deleted file mode 100644
index 6dd12d3d2d..0000000000
--- a/_includes/api/en/4x/app-path.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='app.path'>app.path()</h3>
-
-Returns the canonical path of the app, a string.
-
-```js
-var app = express()
-var blog = express()
-var blogAdmin = express()
-
-app.use('/blog', blog)
-blog.use('/admin', blogAdmin)
-
-console.dir(app.path()) // ''
-console.dir(blog.path()) // '/blog'
-console.dir(blogAdmin.path()) // '/blog/admin'
-```
-
-The behavior of this method can become very complicated in complex cases of mounted apps:
-it is usually better to use [req.baseUrl](#req.baseUrl) to get the canonical path of the app.
diff --git a/_includes/api/en/4x/app-post-method.md b/_includes/api/en/4x/app-post-method.md
deleted file mode 100644
index 2ccb9ce81a..0000000000
--- a/_includes/api/en/4x/app-post-method.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='app.post.method'>app.post(path, callback [, callback ...])</h3>
-
-Routes HTTP POST requests to the specified path with the specified callback functions.
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-{% include api/en/4x/routing-args.html %}
-
-#### Example
-
-```js
-app.post('/', function (req, res) {
-  res.send('POST request to homepage')
-})
-```
diff --git a/_includes/api/en/4x/app-put-method.md b/_includes/api/en/4x/app-put-method.md
deleted file mode 100644
index 3d4d62c9fc..0000000000
--- a/_includes/api/en/4x/app-put-method.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.put.method'>app.put(path, callback [, callback ...])</h3>
-
-Routes HTTP PUT requests to the specified path with the specified callback functions.
-
-{% include api/en/4x/routing-args.html %}
-
-#### Example
-
-```js
-app.put('/', function (req, res) {
-  res.send('PUT request to homepage')
-})
-```
diff --git a/_includes/api/en/4x/app-render.md b/_includes/api/en/4x/app-render.md
deleted file mode 100644
index 8e35207ebd..0000000000
--- a/_includes/api/en/4x/app-render.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='app.render'>app.render(view, [locals], callback)</h3>
-
-Returns the rendered HTML of a view via the `callback` function. It accepts an optional parameter
-that is an object containing local variables for the view. It is like [res.render()](#res.render),
-except it cannot send the rendered view to the client on its own.
-
-<div class="doc-box doc-info" markdown="1">
-Think of `app.render()` as a utility function for generating rendered view strings.
-Internally `res.render()` uses `app.render()` to render views.
-</div>
-
-<div class="doc-box doc-warn" markdown="1">
-The `view` argument performs file system operations like reading a file from
-disk and evaluating Node.js modules, and as so for security reasons should not
-contain input from the end-user.
-</div>
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-The local variable `cache` is reserved for enabling view cache. Set it to `true`, if you want to
-cache view during development; view caching is enabled in production by default.
-</div>
-
-```js
-app.render('email', function (err, html) {
-  // ...
-})
-
-app.render('email', { name: 'Tobi' }, function (err, html) {
-  // ...
-})
-```
diff --git a/_includes/api/en/4x/app-route.md b/_includes/api/en/4x/app-route.md
deleted file mode 100644
index 60a339b2e9..0000000000
--- a/_includes/api/en/4x/app-route.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='app.route'>app.route(path)</h3>
-
-Returns an instance of a single route, which you can then use to handle HTTP verbs with optional middleware.
-Use `app.route()` to avoid duplicate route names (and thus typo errors).
-
-```js
-var app = express()
-
-app.route('/events')
-  .all(function (req, res, next) {
-    // runs for all HTTP verbs first
-    // think of it as route specific middleware!
-  })
-  .get(function (req, res, next) {
-    res.json({})
-  })
-  .post(function (req, res, next) {
-    // maybe add a new event...
-  })
-```
diff --git a/_includes/api/en/4x/app-set.md b/_includes/api/en/4x/app-set.md
deleted file mode 100644
index 4215749fe8..0000000000
--- a/_includes/api/en/4x/app-set.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='app.set'>app.set(name, value)</h3>
-
-Assigns setting `name` to `value`. You may store any value that you want,
-but certain names can be used to configure the behavior of the server. These
-special names are listed in the [app settings table](#app.settings.table).
-
-Calling `app.set('foo', true)` for a Boolean property is the same as calling
-`app.enable('foo')`. Similarly, calling `app.set('foo', false)` for a Boolean
-property is the same as calling `app.disable('foo')`.
-
-Retrieve the value of a setting with [`app.get()`](#app.get).
-
-```js
-app.set('title', 'My Site')
-app.get('title') // "My Site"
-```
-
-<h4 id='app.settings.table'>Application Settings</h4>
-
-{% include api/en/4x/app-settings.md %}
diff --git a/_includes/api/en/4x/app-settings.md b/_includes/api/en/4x/app-settings.md
deleted file mode 100644
index 1b5a2610fe..0000000000
--- a/_includes/api/en/4x/app-settings.md
+++ /dev/null
@@ -1,329 +0,0 @@
-The following table lists application settings.
-
-Note that sub-apps will:
-
-* Not inherit the value of settings that have a default value.  You must set the value in the sub-app.
-* Inherit the value of settings with no default value; these are explicitly noted in the table below.
-
-Exceptions: Sub-apps will inherit the value of `trust proxy` even though it has a default value (for backward-compatibility);
-Sub-apps will not inherit the value of `view cache` in production (when `NODE_ENV` is "production").
-
-<div class="table-scroller">
-  <table>
-    <thead>
-      <tr>
-        <th id="app-settings-property">Property</th>
-        <th>Type</th>
-        <th>Description</th>
-        <th>Default</th>
-      </tr>
-    </thead>
-    <tbody>
-    <tr>
-  <td markdown="1">
-  `case sensitive routing`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enable case sensitivity.
-      When enabled, "/Foo" and "/foo" are different routes.
-      When disabled, "/Foo" and "/foo" are treated the same.</p>
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)
-      </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `env`
-  </td>
-  <td>String</td>
-  <td markdown="1">
-  Environment mode. Be sure to set to "production" in a production environment; see [Production best practices: performance and reliability](/{{page.lang}}/advanced/best-practice-performance.html#env).
-  </td>
-  <td markdown="1">
-  `process.env.NODE_ENV` (`NODE_ENV` environment variable) or "development" if `NODE_ENV` is not set.
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `etag`
-  </td>
-  <td>Varied</td>
-  <td markdown="1">
-  Set the ETag response header. For possible values, see the [`etag` options table](#etag.options.table).
-
-  [More about the HTTP ETag header](http://en.wikipedia.org/wiki/HTTP_ETag).
-  </td>
-  <td markdown="1">
-  `weak`
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `jsonp callback name`
-  </td>
-      <td>String</td>
-      <td>Specifies the default JSONP callback name.</td>
-  <td markdown="1">
-  "callback"
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json escape`
-  </td>
-  <td>Boolean</td>
-  <td markdown="1">
-  Enable escaping JSON responses from the `res.json`, `res.jsonp`, and `res.send` APIs. This will escape the characters `<`, `>`, and `&` as Unicode escape sequences in JSON. The purpose of this it to assist with [mitigating certain types of persistent XSS attacks](https://blog.mozilla.org/security/2017/07/18/web-service-audits-firefox-accounts/) when clients sniff responses for HTML.
-  <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-  </td>
-  <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json replacer`
-  </td>
-      <td>Varied</td>
-      <td>The <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_replacer_parameter">'replacer' argument used by `JSON.stringify`</a>.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-  <td>N/A (undefined)
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json spaces`
-  </td>
-      <td>Varied</td>
-      <td>The <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_space_argument">'space' argument used by `JSON.stringify`</a>.
-This is typically set to the number of spaces to use to indent prettified JSON.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `query parser`
-  </td>
-      <td>Varied</td>
-  <td markdown="1">
-Disable query parsing by setting the value to `false`, or set the query parser to use either "simple" or "extended" or a custom query string parsing function.
-
-The simple query parser is based on Node's native query parser, [querystring](http://nodejs.org/api/querystring.html).
-
-The extended query parser is based on [qs](https://www.npmjs.org/package/qs).
-
-A custom query string parsing function will receive the complete query string, and must return an object of query keys and their values.
-  </td>
-      <td>"extended"</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `strict routing`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enable strict routing.
-      When enabled, the router treats "/foo" and "/foo/" as different.
-      Otherwise, the router treats "/foo" and "/foo/" as the same.</p>
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined) </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `subdomain offset`
-  </td>
-      <td>Number</td>
-      <td>The number of dot-separated parts of the host to remove to access subdomain.</td>
-      <td>2</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `trust proxy`
-  </td>
-      <td>Varied</td>
-  <td markdown="1">
-  Indicates the app is behind a front-facing proxy, and to use the `X-Forwarded-*` headers to determine the connection and the IP address of the client. NOTE: `X-Forwarded-*` headers are easily spoofed and the detected IP addresses are unreliable.
-<p>
-  When enabled, Express attempts to determine the IP address of the client connected through the front-facing proxy, or series of proxies. The `req.ips` property, then contains an array of IP addresses the client is connected through. To enable it, use the values described in the <a href="#trust.proxy.options.table">trust proxy options table</a>.
-</p><p>
-  The `trust proxy` setting is implemented using the <a href="https://www.npmjs.org/package/proxy-addr">proxy-addr</a> package.  For more information, see its documentation.
-</p><p>
-<b>NOTE</b>: Sub-apps <i>will</i> inherit the value of this setting, even though it has a default value.
-</p>
-  </td>
-  <td markdown="1">
-  `false` (disabled)
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `views`
-  </td>
-      <td>String or Array</td>
-      <td>A directory or an array of directories for the application's views. If an array, the views are looked up in the order they occur in the array.</td>
-  <td markdown="1">
-  `process.cwd() + '/views'`
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `view cache`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enables view template compilation caching.</p>
-      <p><b>NOTE</b>: Sub-apps will not inherit the value of this setting in production (when `NODE_ENV` is "production").</p>
-      </td>
-  <td markdown="1">
-  `true` in production, otherwise undefined.
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `view engine`
-  </td>
-      <td>String</td>
-      <td>The default engine extension to use when omitted.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `x-powered-by`
-  </td>
-      <td>Boolean</td>
-      <td>Enables the "X-Powered-By: Express" HTTP header.</td>
-  <td markdown="1">
-  `true`
-  </td>
-    </tr>
-    </tbody>
-  </table>
-  </div>
-
-  <h5 id="trust.proxy.options.table">Options for `trust proxy` setting</h5>
-
-  <p markdown="1">
-  Read [Express behind proxies](/{{page.lang}}/guide/behind-proxies.html) for more
-  information.
-  </p>
-
-<div class="table-scroller">
-  <table>
-    <thead><tr><th>Type</th><th>Value</th></tr></thead>
-    <tbody>
-      <tr>
-        <td>Boolean</td>
-  <td markdown="1">
-  If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-*` header.
-
-  If `false`, the app is understood as directly facing the Internet and the client's IP address is derived from `req.connection.remoteAddress`. This is the default setting.
-  </td>
-      </tr>
-      <tr>
-        <td>String<br/>String containing comma-separated values<br/>Array of strings </td>
-  <td markdown="1">
-  An IP address, subnet, or an array of IP addresses, and subnets to trust. Pre-configured subnet names are:
-
-  * loopback - `127.0.0.1/8`, `::1/128`
-  * linklocal - `169.254.0.0/16`, `fe80::/10`
-  * uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-  Set IP addresses in any of the following ways:
-
-Specify a single subnet:
-
-```js
-app.set('trust proxy', 'loopback')
-```
-
-Specify a subnet and an address:
-
-```js
-app.set('trust proxy', 'loopback, 123.123.123.123')
-```
-
-Specify multiple subnets as CSV:
-
-```js
-app.set('trust proxy', 'loopback, linklocal, uniquelocal')
-```
-
-Specify multiple subnets as an array:
-
-```js
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal'])
-```
-
-  When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address.
-  </td>
-      </tr>
-      <tr>
-        <td>Number</td>
-  <td markdown="1">
-  Trust the <i>n</i><sup>th</sup> hop from the front-facing proxy server as the client.
-  </td>
-      </tr>
-      <tr>
-        <td>Function</td>
-  <td markdown="1">
-  Custom trust implementation. Use this only if you know what you are doing.
-
-```js
-app.set('trust proxy', function (ip) {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-  </td>
-      </tr>
-    </tbody>
-  </table>
-</div>
-
-  <h5 id="etag.options.table">Options for `etag` setting</h5>
-
-<p markdown="1">
-**NOTE**:  These settings apply only to dynamic files, not static files.
-The [express.static](#express.static) middleware ignores these settings.
-</p>
-
-  <p markdown="1">
-  The ETag functionality is implemented using the
-  [etag](https://www.npmjs.org/package/etag) package.
-  For more information, see its documentation.
-  </p>
-
-<div class="table-scroller">
-  <table>
-    <thead><tr><th>Type</th><th>Value</th></tr></thead>
-    <tbody>
-      <tr>
-        <td>Boolean</td>
-  <td markdown="1">
-  `true` enables weak ETag. This is the default setting.<br>
-  `false` disables ETag altogether.
-  </td>
-      </tr>
-      <tr>
-        <td>String</td>
-        <td>
-            If "strong", enables strong ETag.<br>
-            If "weak", enables weak ETag.
-        </td>
-      </tr>
-      <tr>
-        <td>Function</td>
-  <td markdown="1">Custom ETag function implementation. Use this only if you know what you are doing.
-
-```js
-app.set('etag', function (body, encoding) {
-  return generateHash(body, encoding) // consider the function is defined
-})
-```
-  </td>
-      </tr>
-    </tbody>
-  </table>
-</div>
diff --git a/_includes/api/en/4x/app-use.md b/_includes/api/en/4x/app-use.md
deleted file mode 100644
index c5e9dbf90c..0000000000
--- a/_includes/api/en/4x/app-use.md
+++ /dev/null
@@ -1,318 +0,0 @@
-<h3 id='app.use'>app.use([path,] callback [, callback...])</h3>
-
-Mounts the specified [middleware](/{{page.lang}}/guide/using-middleware.html) function or functions
-at the specified path:
-the middleware function is executed when the base of the requested path matches `path`.
-
-{% include api/en/4x/routing-args.html %}
-
-#### Description
-
-A route will match any path that follows its path immediately with a "`/`".
-For example: `app.use('/apple', ...)` will match "/apple", "/apple/images",
-"/apple/images/news", and so on.
-
-Since `path` defaults to "/", middleware mounted without a path will be executed for every request to the app.
-For example, this middleware function will be executed for _every_ request to the app:
-
-```js
-app.use(function (req, res, next) {
-  console.log('Time: %d', Date.now())
-  next()
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-**NOTE**
-
-Sub-apps will:
-
-* Not inherit the value of settings that have a default value.  You must set the value in the sub-app.
-* Inherit the value of settings with no default value.
-
-For details, see [Application settings](/en/4x/api.html#app.settings.table).
-</div>
-
-Middleware functions are executed sequentially, therefore the order of middleware inclusion is important.
-
-```js
-// this middleware will not allow the request to go beyond it
-app.use(function (req, res, next) {
-  res.send('Hello World')
-})
-
-// requests will never reach this route
-app.get('/', function (req, res) {
-  res.send('Welcome')
-})
-```
-
-**Error-handling middleware**
-
-Error-handling middleware always takes _four_ arguments.  You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors. For details about error-handling middleware, see: [Error handling](/{{ page.lang }}/guide/error-handling.html).
-
-Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`):
-
-```js
-app.use(function (err, req, res, next) {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-#### Path examples
-
-The following table provides some simple examples of valid `path` values for
-mounting middleware.
-
-<div class="table-scroller">
-<table>
-
-<thead>
-<tr>
-<th>Type</th>
-<th>Example</th>
-</tr>
-</thead>
-<tbody>
-
-<tr>
-<td>Path</td>
-<td markdown="1">
-Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
-
-
-```js
-app.use('/abcd', function (req, res, next) {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Path Pattern</td>
-<td markdown="1">
-This will match paths starting with `/abcd` and `/abd`:
-
-```js
-app.use('/abc?d', function (req, res, next) {
-  next()
-})
-```
-
-This will match paths starting with `/abcd`, `/abbcd`, `/abbbbbcd`, and so on:
-
-```js
-app.use('/ab+cd', function (req, res, next) {
-  next()
-})
-```
-
-This will match paths starting with `/abcd`, `/abxcd`, `/abFOOcd`, `/abbArcd`, and so on:
-
-```js
-app.use('/ab*cd', function (req, res, next) {
-  next()
-})
-```
-
-This will match paths starting with `/ad` and `/abcd`:
-
-```js
-app.use('/a(bc)?d', function (req, res, next) {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Regular Expression</td>
-<td markdown="1">
-This will match paths starting with `/abc` and `/xyz`:
-
-```js
-app.use(/\/abc|\/xyz/, function (req, res, next) {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Array</td>
-<td markdown="1">
-This will match paths starting with `/abcd`, `/xyza`, `/lmn`, and `/pqr`:
-
-```js
-app.use(['/abcd', '/xyza', /\/lmn|\/pqr/], function (req, res, next) {
-  next()
-})
-```
-
-</td>
-</tr>
-
-</tbody>
-
-</table>
-</div>
-
-#### Middleware callback function examples
-
-The following table provides some simple examples of middleware functions that
-can be used as the `callback` argument to `app.use()`, `app.METHOD()`, and `app.all()`.
-
-<table>
-
-<thead>
-<tr>
-<th>Usage</th>
-<th>Example</th>
-</tr>
-</thead>
-
-<tbody>
-
-<tr>
-<td>Single Middleware</td>
-<td markdown="1">
-You can define and mount a middleware function locally.
-
-```js
-app.use(function (req, res, next) {
-  next()
-})
-```
-
-A router is valid middleware.
-
-```js
-var router = express.Router()
-router.get('/', function (req, res, next) {
-  next()
-})
-app.use(router)
-```
-
-An Express app is valid middleware.
-
-```js
-var subApp = express()
-subApp.get('/', function (req, res, next) {
-  next()
-})
-app.use(subApp)
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Series of Middleware</td>
-<td markdown="1">
-You can specify more than one middleware function at the same mount path.
-
-```js
-var r1 = express.Router()
-r1.get('/', function (req, res, next) {
-  next()
-})
-
-var r2 = express.Router()
-r2.get('/', function (req, res, next) {
-  next()
-})
-
-app.use(r1, r2)
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Array</td>
-<td markdown="1">
-Use an array to group middleware logically.
-
-```js
-var r1 = express.Router()
-r1.get('/', function (req, res, next) {
-  next()
-})
-
-var r2 = express.Router()
-r2.get('/', function (req, res, next) {
-  next()
-})
-
-app.use([r1, r2])
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Combination</td>
-<td markdown="1">
-You can combine all the above ways of mounting middleware.
-
-```js
-function mw1 (req, res, next) { next() }
-function mw2 (req, res, next) { next() }
-
-var r1 = express.Router()
-r1.get('/', function (req, res, next) { next() })
-
-var r2 = express.Router()
-r2.get('/', function (req, res, next) { next() })
-
-var subApp = express()
-subApp.get('/', function (req, res, next) { next() })
-
-app.use(mw1, [mw2, r1, r2], subApp)
-```
-
-</td>
-</tr>
-
-</tbody>
-
-</table>
-</div>
-
-Following are some examples of using the [express.static](/{{page.lang}}/guide/using-middleware.html#middleware.built-in)
-middleware in an Express app.
-
-Serve static content for the app from the "public" directory in the application directory:
-
-```js
-// GET /style.css etc
-app.use(express.static(path.join(__dirname, 'public')))
-```
-
-Mount the middleware at "/static" to serve static content only when their request path is prefixed with "/static":
-
-```js
-// GET /static/style.css etc.
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-Disable logging for static content requests by loading the logger middleware after the static middleware:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(logger())
-```
-
-Serve static files from multiple directories, but give precedence to "./public" over the others:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(express.static(path.join(__dirname, 'files')))
-app.use(express.static(path.join(__dirname, 'uploads')))
-```
diff --git a/_includes/api/en/4x/app.md b/_includes/api/en/4x/app.md
deleted file mode 100644
index 518ec66efd..0000000000
--- a/_includes/api/en/4x/app.md
+++ /dev/null
@@ -1,123 +0,0 @@
-<h2 id="app">Application</h2>
-
-The `app` object conventionally denotes the Express application.
-Create it by calling the top-level `express()` function exported by the Express module:
-
-```js
-var express = require('express')
-var app = express()
-
-app.get('/', function (req, res) {
-  res.send('hello world')
-})
-
-app.listen(3000)
-```
-
-The `app` object has methods for
-
-* Routing HTTP requests; see for example, [app.METHOD](#app.METHOD) and [app.param](#app.param).
-* Configuring middleware; see [app.route](#app.route).
-* Rendering HTML views; see [app.render](#app.render).
-* Registering a template engine; see [app.engine](#app.engine).
-
-It also has settings (properties) that affect how the application behaves;
-for more information, see [Application settings](#app.settings.table).
-
-<div class="doc-box doc-info" markdown="1">
-The Express application object can be referred from the [request object](#req) and the [response object](#res) as `req.app`, and `res.app`, respectively.
-</div>
-
-<h3 id='app.properties'>Properties</h3>
-
-<section markdown="1">
-  {% include api/en/4x/app-locals.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-mountpath.md %}
-</section>
-
-<h3 id='app.events'>Events</h3>
-
-<section markdown="1">
-  {% include api/en/4x/app-onmount.md %}
-</section>
-
-<h3 id='app.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/4x/app-all.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-delete-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-disable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-disabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-enable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-enabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-engine.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-get-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-listen.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-METHOD.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-path.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-post-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-put-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-render.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/app-use.md %}
-</section>
diff --git a/_includes/api/en/4x/express.json.md b/_includes/api/en/4x/express.json.md
deleted file mode 100644
index ffc460193d..0000000000
--- a/_includes/api/en/4x/express.json.md
+++ /dev/null
@@ -1,42 +0,0 @@
-<h3 id='express.json' class='h2'>express.json([options])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-This middleware is available in Express v4.16.0 onwards.
-</div>
-
-This is a built-in middleware function in Express. It parses incoming requests
-with JSON payloads and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that only parses JSON and only looks at requests where
-the `Content-Type` header matches the `type` option. This parser accepts any
-Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.foo.toString()` may fail in multiple ways, for example
-`foo` may not be there or may not be a string, and `toString` may not be a
-function and instead a string or other user-input.
-</div>
-
-<div class="table-scroller" markdown="1">
-
-The following table describes the properties of the optional `options` object.
-
-| Property      | Description                                                           |   Type      | Default         |
-|---------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `inflate`     | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`       | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `reviver`     | The `reviver` option is passed directly to `JSON.parse` as the second argument. You can find more information on this argument [in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter). | Function | `null` |
-| `strict`      | Enables or disables only accepting arrays and objects; when disabled will accept anything `JSON.parse` accepts. | Boolean | `true` |
-| `type`        | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `json`), a mime type (like `application/json`), or a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/json"` |
-| `verify`      | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/4x/express.md b/_includes/api/en/4x/express.md
deleted file mode 100644
index 6ba0094cc7..0000000000
--- a/_includes/api/en/4x/express.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<h2 id="express">express()</h2>
-
-Creates an Express application. The `express()` function is a top-level function exported by the `express` module.
-
-```js
-var express = require('express')
-var app = express()
-```
-
-<h3 id='express.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/4x/express.json.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/express.raw.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/express.router.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/express.static.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/express.text.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/express.urlencoded.md %}
-</section>
diff --git a/_includes/api/en/4x/express.raw.md b/_includes/api/en/4x/express.raw.md
deleted file mode 100644
index cac172fb95..0000000000
--- a/_includes/api/en/4x/express.raw.md
+++ /dev/null
@@ -1,40 +0,0 @@
-<h3 id='express.raw' class='h2'>express.raw([options])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-This middleware is available in Express v4.17.0 onwards.
-</div>
-
-This is a built-in middleware function in Express. It parses incoming request
-payloads into a `Buffer` and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that parses all bodies as a `Buffer` and only looks at requests
-where the `Content-Type` header matches the `type` option. This parser accepts
-any Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` `Buffer` containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.toString()` may fail in multiple ways, for example
-stacking multiple parsers `req.body` may be from a different parser. Testing
-that `req.body` is a `Buffer` before calling buffer methods is recommended.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property  | Description                                                           |   Type      | Default         |
-|-----------|-----------------------------------------------------------------------|-------------|-----------------|
-| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `bin`), a mime type (like `application/octet-stream`), or a mime type with a wildcard (like `*/*` or `application/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/octet-stream"` |
-| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/4x/express.router.md b/_includes/api/en/4x/express.router.md
deleted file mode 100644
index 10dc92c94a..0000000000
--- a/_includes/api/en/4x/express.router.md
+++ /dev/null
@@ -1,24 +0,0 @@
-<h3 id='express.router' class='h2'>express.Router([options])</h3>
-
-Creates a new [router](#router) object.
-
-```js
-var router = express.Router([options])
-```
-
-The optional `options` parameter specifies the behavior of the router.
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability  |
-|-----------------|-------------------------------------------------|-------------|---------------|
-| `caseSensitive` | Enable case sensitivity. | Disabled by default, treating "/Foo" and "/foo" as the same.|  |
-| `mergeParams`   | Preserve the `req.params` values from the parent router. If the parent and the child have conflicting param names, the child's value take precedence.| `false` | 4.5.0+ |
-| `strict`        | Enable strict routing. | Disabled by default, "/foo" and "/foo/" are treated the same by the router.| &nbsp; |
-
-</div>
-
-You can add middleware and HTTP method routes (such as `get`, `put`, `post`, and
-so on) to `router` just like an application.
-
-For more information, see [Router](#router).
diff --git a/_includes/api/en/4x/express.static.md b/_includes/api/en/4x/express.static.md
deleted file mode 100644
index d7e899cd58..0000000000
--- a/_includes/api/en/4x/express.static.md
+++ /dev/null
@@ -1,97 +0,0 @@
-<h3 id='express.static' class='h2'>express.static(root, [options])</h3>
-
-This is a built-in middleware function in Express.
-It serves static files and is based on  [serve-static](/resources/middleware/serve-static.html).
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-The `root` argument specifies the root directory from which to serve static assets.
-The function determines the file to serve by combining `req.url` with the provided `root` directory.
-When a file is not found, instead of sending a 404 response, it calls `next()`
-to move on to the next middleware, allowing for stacking and fall-backs.
-
-The following table describes the properties of the `options` object.
-See also the [example below](#example.of.express.static).
-
-<div class="table-scroller" markdown="1">
-
-| Property      | Description                                                           |   Type      | Default         |
-|---------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `dotfiles`    | Determines how dotfiles (files or directories that begin with a dot ".") are treated.  <br/><br/>See [dotfiles](#dotfiles) below. | String | `undefined` |
-| `etag`        | Enable or disable etag generation <br/><br/>NOTE: `express.static` always sends weak ETags. | Boolean | `true` |
-| `extensions`  | Sets file extension fallbacks: If a file is not found, search for files with the specified extensions and serve the first one found. Example: `['html', 'htm']`.| Mixed | `false` |
-| `fallthrough`  | Let client errors fall-through as unhandled requests, otherwise forward a client error. <br/><br/>See [fallthrough](#fallthrough) below.| Boolean | `true` |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | Boolean | `false` |
-| `index`       | Sends the specified directory index file. Set to `false` to disable directory indexing. | Mixed | "index.html" |
-| `lastModified` | Set the `Last-Modified` header to the last modified date of the file on the OS. | Boolean | `true` |
-| `maxAge`      | Set the max-age property of the Cache-Control header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms). | Number | 0 |
-| `redirect`    | Redirect to trailing "/" when the pathname is a directory. | Boolean | `true` |
-| `setHeaders`  | Function for setting HTTP headers to serve with the file. <br/><br/>See [setHeaders](#setHeaders) below. | Function |  |
-| `acceptRanges`    | Enable or disable accepting ranged requests. Disabling this will not send the `Accept-Ranges` header and will ignore the contents of the Range request header.| Boolean | true |
-| `cacheControl`    | Enable or disable setting the `Cache-Control` response header. Disabling this will ignore the immutable and maxAge options. | Boolean | true |
-
-</div>
-
-For more information, see [Serving static files in Express](/starter/static-files.html).
-and [Using middleware - Built-in middleware](/{{page.lang}}/guide/using-middleware.html#middleware.built-in).
-
-<h5 id='dotfiles'>dotfiles</h5>
-
-Possible values for this option are:
-
-- "allow" - No special treatment for dotfiles.
-- "deny" - Deny a request for a dotfile, respond with `403`, then call `next()`.
-- "ignore" - Act as if the dotfile does not exist, respond with `404`, then call `next()`.
-- `undefined` - Act as ignore, except that files in a directory that begins with a dot are **NOT** ignored.
-
-<h5 id='fallthrough'>fallthrough</h5>
-
-When this option is `true`, client errors such as a bad request or a request to a non-existent
-file will cause this middleware to simply call `next()` to invoke the next middleware in the stack.
-When false, these errors (even 404s), will invoke `next(err)`.
-
-Set this option to `true` so you can map multiple physical directories
-to the same web address or for routes to fill in non-existent files.
-
-Use `false` if you have mounted this middleware at a path designed
-to be strictly a single file system directory, which allows for short-circuiting 404s
-for less overhead. This middleware will also reply to all methods.
-
-<h5 id='setHeaders'>setHeaders</h5>
-
-For this option, specify a function to set custom response headers. Alterations to the headers must occur synchronously.
-
-The signature of the function is:
-
-```js
-fn(res, path, stat)
-```
-
-Arguments:
-
-- `res`, the [response object](#res).
-- `path`, the file path that is being sent.
-- `stat`, the `stat` object of the file that is being sent.
-
-<h4 id='example.of.express.static'>Example of express.static</h4>
-
-Here is an example of using the `express.static` middleware function with an elaborate options object:
-
-```js
-var options = {
-  dotfiles: 'ignore',
-  etag: false,
-  extensions: ['htm', 'html'],
-  index: false,
-  maxAge: '1d',
-  redirect: false,
-  setHeaders: function (res, path, stat) {
-    res.set('x-timestamp', Date.now())
-  }
-}
-
-app.use(express.static('public', options))
-```
diff --git a/_includes/api/en/4x/express.text.md b/_includes/api/en/4x/express.text.md
deleted file mode 100644
index 4d762427e5..0000000000
--- a/_includes/api/en/4x/express.text.md
+++ /dev/null
@@ -1,41 +0,0 @@
-<h3 id='express.text' class='h2'>express.text([options])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-This middleware is available in Express v4.17.0 onwards.
-</div>
-
-This is a built-in middleware function in Express. It parses incoming request
-payloads into a string and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that parses all bodies as a string and only looks at requests
-where the `Content-Type` header matches the `type` option. This parser accepts
-any Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` string containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.trim()` may fail in multiple ways, for example
-stacking multiple parsers `req.body` may be from a different parser. Testing
-that `req.body` is a string before calling string methods is recommended.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property         | Description                                                           |   Type      | Default         |
-|------------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `defaultCharset` | Specify the default character set for the text content if the charset is not specified in the `Content-Type` header of the request. | String | `"utf-8"` |
-| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `txt`), a mime type (like `text/plain`), or a mime type with a wildcard (like `*/*` or `text/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"text/plain"` |
-| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/4x/express.urlencoded.md b/_includes/api/en/4x/express.urlencoded.md
deleted file mode 100644
index f6bcc46325..0000000000
--- a/_includes/api/en/4x/express.urlencoded.md
+++ /dev/null
@@ -1,48 +0,0 @@
-<h3 id='express.urlencoded' class='h2'>express.urlencoded([options])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-This middleware is available in Express v4.16.0 onwards.
-</div>
-
-This is a built-in middleware function in Express. It parses incoming requests
-with urlencoded payloads and is based on [body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that only parses urlencoded bodies and only looks at
-requests where the `Content-Type` header matches the `type` option. This
-parser accepts only UTF-8 encoding of the body and supports automatic
-inflation of `gzip` and `deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred. This object will contain key-value pairs, where the value can be
-a string or array (when `extended` is `false`), or any type (when `extended`
-is `true`).
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.foo.toString()` may fail in multiple ways, for example
-`foo` may not be there or may not be a string, and `toString` may not be a
-function and instead a string or other user-input.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property         | Description                                                           |   Type      | Default         |
-|------------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `extended`       | This option allows to choose between parsing the URL-encoded data with the `querystring` library (when `false`) or the `qs` library (when `true`). The "extended" syntax allows for rich objects and arrays to be encoded into the URL-encoded format, allowing for a JSON-like experience with URL-encoded. For more information, please [see the qs library](https://www.npmjs.org/package/qs#readme). | Boolean | `true` |
-| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `parameterLimit` | This option controls the maximum number of parameters that are allowed in the URL-encoded data. If a request contains more parameters than this value, an error will be raised. | Number | `1000` |
-| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `urlencoded`), a mime type (like `application/x-www-form-urlencoded`), or a mime type with a wildcard (like `*/x-www-form-urlencoded`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/x-www-form-urlencoded"` |
-| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-| `depth`          | Configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible. | Number | `32` |
-
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-The `depth` option was added in Express v4.20.0. If you are using an earlier version, this option will not be available.
-</div>  
diff --git a/_includes/api/en/4x/menu.md b/_includes/api/en/4x/menu.md
deleted file mode 100644
index 81584103c3..0000000000
--- a/_includes/api/en/4x/menu.md
+++ /dev/null
@@ -1,208 +0,0 @@
-<button id="menu-toggle" title="show table of content">On this page</button>
-<ul id="menu">
-    <li id="express-api"><a href="#express">express()</a>
-    <ul id="express-menu">
-        <li><em>Methods</em></li>
-        <li id="express-json-middleware"><a href="#express.json">express.json()</a></li>
-        <li id="express-raw"><a href="#express.raw">express.raw()</a></li>
-        <li id="express-router"><a href="#express.router">express.Router()</a></li>
-        <li id="express-static-middleware"><a href="#express.static">express.static()</a></li>
-        <li id="express-text"><a href="#express.text">express.text()</a></li>
-        <li id="express-urlencoded-middleware"><a href="#express.urlencoded">express.urlencoded()</a></li>
-    </ul>
-    </li>
-
-    <li id="app-api"><a href="#app">Application</a>
-        <ul id="app-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#app.locals">app.locals</a>
-            </li>
-            <li><a href="#app.mountpath">app.mountpath</a>
-            </li>
-            <li><em>Events</em>
-            </li>
-            <li><a href="#app.onmount">mount</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#app.all">app.all()</a>
-            </li>
-            <li><a href="#app.delete.method">app.delete()</a>
-            </li>
-            <li><a href="#app.disable">app.disable()</a>
-            </li>
-            <li><a href="#app.disabled">app.disabled()</a>
-            </li>
-            <li><a href="#app.enable">app.enable()</a>
-            </li>
-            <li><a href="#app.enabled">app.enabled()</a>
-            </li>
-            <li><a href="#app.engine">app.engine()</a>
-            </li>
-            <li><a href="#app.get">app.get()</a>
-            </li>
-            <li><a href="#app.get.method">app.get()</a>
-            </li>
-            <li><a href="#app.listen">app.listen()</a>
-            </li>
-            <li><a href="#app.METHOD">app.METHOD()</a>
-            </li>
-            <li><a href="#app.param">app.param()</a>
-            </li>
-            <li><a href="#app.path">app.path()</a>
-            </li>
-            <li><a href="#app.post.method">app.post()</a>
-            </li>
-            <li><a href="#app.put.method">app.put()</a>
-            </li>
-            <li><a href="#app.render">app.render()</a>
-            </li>
-            <li><a href="#app.route">app.route()</a>
-            </li>
-            <li><a href="#app.set">app.set()</a>
-            </li>
-            <li><a href="#app.use">app.use()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="req-api"><a href="#req">Request</a>
-        <ul id="req-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#req.app">req.app</a>
-            </li>
-            <li><a href="#req.baseUrl">req.baseUrl</a>
-            </li>
-            <li><a href="#req.body">req.body</a>
-            </li>
-            <li><a href="#req.cookies">req.cookies</a>
-            </li>
-            <li><a href="#req.fresh">req.fresh</a>
-            </li>
-            <li><a href="#req.hostname">req.hostname</a>
-            </li>
-            <li><a href="#req.ip">req.ip</a>
-            </li>
-            <li><a href="#req.ips">req.ips</a>
-            </li>
-            <li><a href="#req.method">req.method</a>
-            </li>
-            <li><a href="#req.originalUrl">req.originalUrl</a>
-            </li>
-            <li><a href="#req.params">req.params</a>
-            </li>
-            <li><a href="#req.path">req.path</a>
-            </li>
-            <li><a href="#req.protocol">req.protocol</a>
-            </li>
-            <li><a href="#req.query">req.query</a>
-            </li>
-            <li><a href="#req.res">req.res</a>
-            </li>
-            <li><a href="#req.route">req.route</a>
-            </li>
-            <li><a href="#req.secure">req.secure</a>
-            </li>
-            <li><a href="#req.signedCookies">req.signedCookies</a>
-            </li>
-            <li><a href="#req.stale">req.stale</a>
-            </li>
-            <li><a href="#req.subdomains">req.subdomains</a>
-            </li>
-            <li><a href="#req.xhr">req.xhr</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#req.accepts">req.accepts()</a>
-            </li>
-            <li><a href="#req.acceptsCharsets">req.acceptsCharsets()</a>
-            </li>
-            <li><a href="#req.acceptsEncodings">req.acceptsEncodings()</a>
-            </li>
-            <li><a href="#req.acceptsLanguages">req.acceptsLanguages()</a>
-            </li>
-            <li><a href="#req.get">req.get()</a>
-            </li>
-            <li><a href="#req.is">req.is()</a>
-            </li>
-            <li><a href="#req.param">req.param()</a>
-            </li>
-            <li><a href="#req.range">req.range()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="res-api"><a href="#res">Response</a>
-        <ul id="res-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#res.app">res.app</a>
-            </li>
-            <li><a href="#res.headersSent">res.headersSent</a>
-            </li>
-            <li><a href="#res.locals">res.locals</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#res.append">res.append()</a>
-            </li>
-            <li><a href="#res.attachment">res.attachment()</a>
-            </li>
-            <li><a href="#res.cookie">res.cookie()</a>
-            </li>
-            <li><a href="#res.clearCookie">res.clearCookie()</a>
-            </li>
-            <li><a href="#res.download">res.download()</a>
-            </li>
-            <li><a href="#res.end">res.end()</a>
-            </li>
-            <li><a href="#res.format">res.format()</a>
-            </li>
-            <li><a href="#res.get">res.get()</a>
-            </li>
-            <li><a href="#res.json">res.json()</a>
-            </li>
-            <li><a href="#res.jsonp">res.jsonp()</a>
-            </li>
-            <li><a href="#res.links">res.links()</a>
-            </li>
-            <li><a href="#res.location">res.location()</a>
-            </li>
-            <li><a href="#res.redirect">res.redirect()</a>
-            </li>
-            <li><a href="#res.render">res.render()</a>
-            </li>
-            <li><a href="#res.send">res.send()</a>
-            </li>
-            <li><a href="#res.sendFile">res.sendFile()</a>
-            </li>
-            <li><a href="#res.sendStatus">res.sendStatus()</a>
-            </li>
-            <li><a href="#res.set">res.set()</a>
-            </li>
-            <li><a href="#res.status">res.status()</a>
-            </li>
-            <li><a href="#res.type">res.type()</a>
-            </li>
-            <li><a href="#res.vary">res.vary()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="router-api"><a href="#router">Router</a>
-        <ul id="router-menu">
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#router.all">router.all()</a>
-            </li>
-            <li><a href="#router.METHOD">router.METHOD()</a>
-            </li>
-            <li><a href="#router.param">router.param()</a>
-            </li>
-            <li><a href="#router.route">router.route()</a>
-            </li>
-            <li><a href="#router.use">router.use()</a>
-            </li>
-        </ul>
-    </li>
-</ul>
-
diff --git a/_includes/api/en/4x/req-accepts.md b/_includes/api/en/4x/req-accepts.md
deleted file mode 100644
index 7258c71b4c..0000000000
--- a/_includes/api/en/4x/req-accepts.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='req.accepts'>req.accepts(types)</h3>
-
-Checks if the specified content types are acceptable, based on the request's `Accept` HTTP header field.
-The method returns the best match, or if none of the specified content types is acceptable, returns
-`false` (in which case, the application should respond with `406 "Not Acceptable"`).
-
-The `type` value may be a single MIME type string (such as "application/json"),
-an extension name such as "json", a comma-delimited list, or an array. For a
-list or array, the method returns the *best* match (if any).
-
-```js
-// Accept: text/html
-req.accepts('html')
-// => "html"
-
-// Accept: text/*, application/json
-req.accepts('html')
-// => "html"
-req.accepts('text/html')
-// => "text/html"
-req.accepts(['json', 'text'])
-// => "json"
-req.accepts('application/json')
-// => "application/json"
-
-// Accept: text/*, application/json
-req.accepts('image/png')
-req.accepts('png')
-// => false
-
-// Accept: text/*;q=.5, application/json
-req.accepts(['html', 'json'])
-// => "json"
-```
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/4x/req-acceptsCharsets.md b/_includes/api/en/4x/req-acceptsCharsets.md
deleted file mode 100644
index d47d0480d3..0000000000
--- a/_includes/api/en/4x/req-acceptsCharsets.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='req.acceptsCharsets'>req.acceptsCharsets(charset [, ...])</h3>
-
-Returns the first accepted charset of the specified character sets,
-based on the request's `Accept-Charset` HTTP header field.
-If none of the specified charsets is accepted, returns `false`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/4x/req-acceptsEncodings.md b/_includes/api/en/4x/req-acceptsEncodings.md
deleted file mode 100644
index 2c6a3f236f..0000000000
--- a/_includes/api/en/4x/req-acceptsEncodings.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='req.acceptsEncodings'>req.acceptsEncodings(encoding [, ...])</h3>
-
-Returns the first accepted encoding of the specified encodings,
-based on the request's `Accept-Encoding` HTTP header field.
-If none of the specified encodings is accepted, returns `false`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/4x/req-acceptsLanguages.md b/_includes/api/en/4x/req-acceptsLanguages.md
deleted file mode 100644
index 0ea278b1da..0000000000
--- a/_includes/api/en/4x/req-acceptsLanguages.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='req.acceptsLanguages'>req.acceptsLanguages([lang, ...])</h3>
-
-Returns the first accepted language of the specified languages,
-based on the request's `Accept-Language` HTTP header field.
-If none of the specified languages is accepted, returns `false`.
-
-If no `lang` argument is given, then `req.acceptsLanguages()`
-returns all languages from the HTTP `Accept-Language` header
-as an `Array`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
-
-Express (4.x) source: [request.js line 179](https://github.com/expressjs/express/blob/4.x/lib/request.js#L179)
-
-Accepts (1.3) source: [index.js line 195](https://github.com/jshttp/accepts/blob/f69c19e459bd501e59fb0b1a40b7471bb578113a/index.js#L195)
diff --git a/_includes/api/en/4x/req-app.md b/_includes/api/en/4x/req-app.md
deleted file mode 100644
index 8fde7da97e..0000000000
--- a/_includes/api/en/4x/req-app.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='req.app'>req.app</h3>
-
-This property holds a reference to the instance of the Express application that is using the middleware.
-
-If you follow the pattern in which you create a module that just exports a middleware function
-and `require()` it in your main file, then the middleware can access the Express instance via `req.app`
-
-For example:
-
-```js
-// index.js
-app.get('/viewdirectory', require('./mymiddleware.js'))
-```
-
-```js
-// mymiddleware.js
-module.exports = function (req, res) {
-  res.send('The views directory is ' + req.app.get('views'))
-}
-```
diff --git a/_includes/api/en/4x/req-baseUrl.md b/_includes/api/en/4x/req-baseUrl.md
deleted file mode 100644
index 039c636f93..0000000000
--- a/_includes/api/en/4x/req-baseUrl.md
+++ /dev/null
@@ -1,30 +0,0 @@
-<h3 id='req.baseUrl'>req.baseUrl</h3>
-
-The URL path on which a router instance was mounted.
-
-The `req.baseUrl` property is similar to the [mountpath](#app.mountpath) property of the `app` object,
-except `app.mountpath` returns the matched path pattern(s).
-
-For example:
-
-```js
-var greet = express.Router()
-
-greet.get('/jp', function (req, res) {
-  console.log(req.baseUrl) // /greet
-  res.send('Konnichiwa!')
-})
-
-app.use('/greet', greet) // load the router on '/greet'
-```
-
-Even if you use a path pattern or a set of path patterns to load the router,
-the `baseUrl` property returns the matched string, not the pattern(s). In the
-following example, the `greet` router is loaded on two path patterns.
-
-```js
-app.use(['/gre+t', '/hel{2}o'], greet) // load the router on '/gre+t' and '/hel{2}o'
-```
-
-When a request is made to `/greet/jp`, `req.baseUrl` is "/greet".  When a request is
-made to `/hello/jp`, `req.baseUrl` is "/hello".
diff --git a/_includes/api/en/4x/req-body.md b/_includes/api/en/4x/req-body.md
deleted file mode 100644
index a0caa50067..0000000000
--- a/_includes/api/en/4x/req-body.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<h3 id='req.body'>req.body</h3>
-
-Contains key-value pairs of data submitted in the request body.
-By default, it is `undefined`, and is populated when you use body-parsing middleware such
-as [`express.json()`](#express.json) or [`express.urlencoded()`](#express.urlencoded).
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and values in this object are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString` may not be a function and instead a string or other user-input.
-</div>
-
-The following example shows how to use body-parsing middleware to populate `req.body`.
-
-```js
-var express = require('express')
-
-var app = express()
-
-app.use(express.json()) // for parsing application/json
-app.use(express.urlencoded({ extended: true })) // for parsing application/x-www-form-urlencoded
-
-app.post('/profile', function (req, res, next) {
-  console.log(req.body)
-  res.json(req.body)
-})
-```
diff --git a/_includes/api/en/4x/req-cookies.md b/_includes/api/en/4x/req-cookies.md
deleted file mode 100644
index 244276fffe..0000000000
--- a/_includes/api/en/4x/req-cookies.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='req.cookies'>req.cookies</h3>
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property is an object that
-contains cookies sent by the request.  If the request contains no cookies, it defaults to `{}`.
-
-```js
-// Cookie: name=tj
-console.dir(req.cookies.name)
-// => 'tj'
-```
-
-If the cookie has been signed, you have to use [req.signedCookies](#req.signedCookies).
-
-For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
diff --git a/_includes/api/en/4x/req-fresh.md b/_includes/api/en/4x/req-fresh.md
deleted file mode 100644
index 1b6ec61c59..0000000000
--- a/_includes/api/en/4x/req-fresh.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.fresh'>req.fresh</h3>
-
-When the response is still "fresh" in the client's cache `true` is returned, otherwise `false` is returned to indicate that the client cache is now stale and the full response should be sent.
-
-When a client sends the `Cache-Control: no-cache` request header to indicate an end-to-end reload request, this module will return `false` to make handling these requests transparent.
-
-Further details for how cache validation works can be found in the
-[HTTP/1.1 Caching Specification](https://tools.ietf.org/html/rfc7234).
-
-```js
-console.dir(req.fresh)
-// => true
-```
diff --git a/_includes/api/en/4x/req-get.md b/_includes/api/en/4x/req-get.md
deleted file mode 100644
index 7cd4250b22..0000000000
--- a/_includes/api/en/4x/req-get.md
+++ /dev/null
@@ -1,17 +0,0 @@
-<h3 id='req.get'>req.get(field)</h3>
-
-Returns the specified HTTP request header field (case-insensitive match).
-The `Referrer` and `Referer` fields are interchangeable.
-
-```js
-req.get('Content-Type')
-// => "text/plain"
-
-req.get('content-type')
-// => "text/plain"
-
-req.get('Something')
-// => undefined
-```
-
-Aliased as `req.header(field)`.
diff --git a/_includes/api/en/4x/req-hostname.md b/_includes/api/en/4x/req-hostname.md
deleted file mode 100644
index fbb4731440..0000000000
--- a/_includes/api/en/4x/req-hostname.md
+++ /dev/null
@@ -1,23 +0,0 @@
-<h3 id='req.hostname'>req.hostname</h3>
-
-Contains the hostname derived from the `Host` HTTP header.
-
-When the [`trust proxy` setting](/4x/api.html#trust.proxy.options.table)
-does not evaluate to `false`, this property will instead get the value
-from the `X-Forwarded-Host` header field. This header can be set by
-the client or by the proxy.
-
-If there is more than one `X-Forwarded-Host` header in the request, the
-value of the first header is used. This includes a single header with
-comma-separated values, in which the first value is used.
-
-<div class="doc-box doc-info" markdown="1">
-Prior to Express v4.17.0, the `X-Forwarded-Host` could not contain multiple
-values or be present more than once.
-</div>
-
-```js
-// Host: "example.com:3000"
-console.dir(req.hostname)
-// => 'example.com'
-```
diff --git a/_includes/api/en/4x/req-ip.md b/_includes/api/en/4x/req-ip.md
deleted file mode 100644
index fea8639d52..0000000000
--- a/_includes/api/en/4x/req-ip.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='req.ip'>req.ip</h3>
-
-Contains the remote IP address of the request.
-
-When the [`trust proxy` setting](/4x/api.html#trust.proxy.options.table) does not evaluate to `false`,
-the value of this property is derived from the left-most entry in the
-`X-Forwarded-For` header. This header can be set by the client or by the proxy.
-
-```js
-console.dir(req.ip)
-// => '127.0.0.1'
-```
diff --git a/_includes/api/en/4x/req-ips.md b/_includes/api/en/4x/req-ips.md
deleted file mode 100644
index 7fa7b2653e..0000000000
--- a/_includes/api/en/4x/req-ips.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.ips'>req.ips</h3>
-
-When the [`trust proxy` setting](/4x/api.html#trust.proxy.options.table) does not evaluate to `false`,
-this property contains an array of IP addresses
-specified in the `X-Forwarded-For` request header. Otherwise, it contains an
-empty array. This header can be set by the client or by the proxy.
-
-For example, if `X-Forwarded-For` is `client, proxy1, proxy2`, `req.ips` would be
-`["client", "proxy1", "proxy2"]`, where `proxy2` is the furthest downstream.
diff --git a/_includes/api/en/4x/req-is.md b/_includes/api/en/4x/req-is.md
deleted file mode 100644
index 93d8fd40f4..0000000000
--- a/_includes/api/en/4x/req-is.md
+++ /dev/null
@@ -1,42 +0,0 @@
-<h3 id='req.is'>req.is(type)</h3>
-
-Returns the matching content type if the incoming request's "Content-Type" HTTP header field
-matches the MIME type specified by the `type` parameter. If the request has no body, returns `null`.
-Returns `false` otherwise.
-
-```js
-// With Content-Type: text/html; charset=utf-8
-req.is('html')
-// => 'html'
-req.is('text/html')
-// => 'text/html'
-req.is('text/*')
-// => 'text/*'
-
-// When Content-Type is application/json
-req.is('json')
-// => 'json'
-req.is('application/json')
-// => 'application/json'
-req.is('application/*')
-// => 'application/*'
-
-// Using arrays
-// When Content-Type is application/json
-req.is(['json', 'html'])
-// => 'json'
-
-// Using multiple arguments
-// When Content-Type is application/json
-req.is('json', 'html')
-// => 'json'
-
-req.is('html')
-// => false
-req.is(['xml', 'yaml'])
-// => false
-req.is('xml', 'yaml')
-// => false
-```
-
-For more information, or if you have issues or concerns, see [type-is](https://github.com/expressjs/type-is).
\ No newline at end of file
diff --git a/_includes/api/en/4x/req-method.md b/_includes/api/en/4x/req-method.md
deleted file mode 100644
index 3d2b886d7d..0000000000
--- a/_includes/api/en/4x/req-method.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='req.method'>req.method</h3>
-
-Contains a string corresponding to the HTTP method of the request:
-`GET`, `POST`, `PUT`, and so on.
diff --git a/_includes/api/en/4x/req-originalUrl.md b/_includes/api/en/4x/req-originalUrl.md
deleted file mode 100644
index 4babd80d04..0000000000
--- a/_includes/api/en/4x/req-originalUrl.md
+++ /dev/null
@@ -1,27 +0,0 @@
-<h3 id='req.originalUrl'>req.originalUrl</h3>
-
-<div class="doc-box doc-notice" markdown="1">
-`req.url` is not a native Express property, it is inherited from Node's [http module](https://nodejs.org/api/http.html#http_message_url).
-</div>
-
-This property is much like `req.url`; however, it retains the original request URL,
-allowing you to rewrite `req.url` freely for internal routing purposes. For example,
-the "mounting" feature of [app.use()](#app.use) will rewrite `req.url` to strip the mount point.
-
-```js
-// GET /search?q=something
-console.dir(req.originalUrl)
-// => '/search?q=something'
-```
-
-`req.originalUrl` is available both in middleware and router objects, and is a
-combination of `req.baseUrl` and `req.url`. Consider following example:
-
-```js
-app.use('/admin', function (req, res, next) { // GET 'http://www.example.com/admin/new?sort=desc'
-  console.dir(req.originalUrl) // '/admin/new?sort=desc'
-  console.dir(req.baseUrl) // '/admin'
-  console.dir(req.path) // '/new'
-  next()
-})
-```
diff --git a/_includes/api/en/4x/req-param.md b/_includes/api/en/4x/req-param.md
deleted file mode 100644
index c0a31602be..0000000000
--- a/_includes/api/en/4x/req-param.md
+++ /dev/null
@@ -1,35 +0,0 @@
-<h3 id='req.param'>req.param(name [, defaultValue])</h3>
-
-<div class="doc-box doc-warn" markdown="1">
-Deprecated. Use either `req.params`, `req.body` or `req.query`, as applicable.
-</div>
-
-Returns the value of param `name` when present.
-
-```js
-// ?name=tobi
-req.param('name')
-// => "tobi"
-
-// POST name=tobi
-req.param('name')
-// => "tobi"
-
-// /user/tobi for /user/:name
-req.param('name')
-// => "tobi"
-```
-
-Lookup is performed in the following order:
-
-* `req.params`
-* `req.body`
-* `req.query`
-
-Optionally, you can specify `defaultValue` to set a default value if the parameter is not found in any of the request objects.
-
-<div class="doc-box doc-warn" markdown="1">
-Direct access to `req.body`, `req.params`, and `req.query` should be favoured for clarity - unless you truly accept input from each object.
-
-Body-parsing middleware must be loaded for `req.param()` to work predictably. Refer [req.body](#req.body) for details.
-</div>
diff --git a/_includes/api/en/4x/req-params.md b/_includes/api/en/4x/req-params.md
deleted file mode 100644
index a92d640508..0000000000
--- a/_includes/api/en/4x/req-params.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<h3 id='req.params'>req.params</h3>
-
-This property is an object containing properties mapped to the [named route "parameters"](/{{ page.lang }}/guide/routing.html#route-parameters). For example, if you have the route `/user/:name`, then the "name" property is available as `req.params.name`. This object defaults to `{}`.
-
-```js
-// GET /user/tj
-console.dir(req.params.name)
-// => 'tj'
-```
-
-When you use a regular expression for the route definition, capture groups are provided as integer keys using `req.params[n]`, where `n` is the n<sup>th</sup> capture group. This rule is applied to unnamed wild card matches with string routes such as `/file/*`:
-
-```js
-// GET /file/javascripts/jquery.js
-console.dir(req.params[0])
-// => 'javascripts/jquery.js'
-```
-
-Named capturing groups in regular expressions behave like named route parameters. For example the group from `/^\/file\/(?<path>.*)$/` expression is available as `req.params.path`.
-
-If you need to make changes to a key in `req.params`, use the [app.param](/{{ page.lang }}/4x/api.html#app.param) handler. Changes are applicable only to [parameters](/{{ page.lang }}/guide/routing.html#route-parameters) already defined in the route path.
-
-Any changes made to the `req.params` object in a middleware or route handler will be reset.
-
-{% include admonitions/note.html content="Express automatically decodes the values in `req.params` (using `decodeURIComponent`)." %}
diff --git a/_includes/api/en/4x/req-path.md b/_includes/api/en/4x/req-path.md
deleted file mode 100644
index 0b71c71bf7..0000000000
--- a/_includes/api/en/4x/req-path.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.path'>req.path</h3>
-
-Contains the path part of the request URL.
-
-```js
-// example.com/users?sort=desc
-console.dir(req.path)
-// => '/users'
-```
-
-<div class="doc-box doc-info" markdown="1">
-When called from a middleware, the mount point is not included in `req.path`. See [app.use()](/4x/api.html#app.use) for more details.
-</div>
diff --git a/_includes/api/en/4x/req-protocol.md b/_includes/api/en/4x/req-protocol.md
deleted file mode 100644
index 6d38cc1f19..0000000000
--- a/_includes/api/en/4x/req-protocol.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='req.protocol'>req.protocol</h3>
-
-Contains the request protocol string: either `http` or (for TLS requests) `https`.
-
-When the [`trust proxy` setting](#trust.proxy.options.table) does not evaluate to `false`,
-this property will use the value of the `X-Forwarded-Proto` header field if present.
-This header can be set by the client or by the proxy.
-
-```js
-console.dir(req.protocol)
-// => 'http'
-```
diff --git a/_includes/api/en/4x/req-query.md b/_includes/api/en/4x/req-query.md
deleted file mode 100644
index 019779b8f3..0000000000
--- a/_includes/api/en/4x/req-query.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='req.query'>req.query</h3>
-
-This property is an object containing a property for each query string parameter in the route.
-When [query parser](#app.settings.table) is set to disabled, it is an empty object `{}`, otherwise it is the result of the configured query parser.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.query`'s shape is based on user-controlled input, all properties and values in this object are untrusted and should be validated before trusting. For example, `req.query.foo.toString()` may fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString` may not be a function and instead a string or other user-input.
-</div>
-
-The value of this property can be configured with the [query parser application setting](#app.settings.table) to work how your application needs it. A very popular query string parser is the [`qs` module](https://www.npmjs.org/package/qs), and this is used by default. The `qs` module is very configurable with many settings, and it may be desirable to use different settings than the default to populate `req.query`:
-
-```js
-var qs = require('qs')
-app.set('query parser', function (str) {
-  return qs.parse(str, { /* custom options */ })
-})
-```
-
-Check out the [query parser application setting](#app.settings.table) documentation for other customization options.
diff --git a/_includes/api/en/4x/req-range.md b/_includes/api/en/4x/req-range.md
deleted file mode 100644
index dbf2afeb5e..0000000000
--- a/_includes/api/en/4x/req-range.md
+++ /dev/null
@@ -1,33 +0,0 @@
-<h3 id='req.range'>req.range(size[, options])</h3>
-
-`Range` header parser.
-
-The `size` parameter is the maximum size of the resource.
-
-The `options` parameter is an object that can have the following properties.
-
-<div class="table-scroller" markdown="1">
-
-| Property    | Type |  Description                                                     |
-|-------------|-------------------------------------------------------------------------|
-| `combine`   | Boolean | Specify if overlapping & adjacent ranges should be combined, defaults to `false`. When `true`, ranges will be combined and returned as if they were specified that way in the header.|
-
-</div>
-
-An array of ranges will be returned or negative numbers indicating an error parsing.
-
-* `-2` signals a malformed header string
-* `-1` signals an unsatisfiable range
-
-```js
-// parse header from request
-var range = req.range(1000)
-
-// the type of the range
-if (range.type === 'bytes') {
-  // the ranges
-  range.forEach(function (r) {
-    // do something with r.start and r.end
-  })
-}
-```
diff --git a/_includes/api/en/4x/req-res.md b/_includes/api/en/4x/req-res.md
deleted file mode 100644
index 772ddb43b4..0000000000
--- a/_includes/api/en/4x/req-res.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='req.res'>req.res</h3>
-
-This property holds a reference to the <a href="#res">response object</a>
-that relates to this request object.
diff --git a/_includes/api/en/4x/req-route.md b/_includes/api/en/4x/req-route.md
deleted file mode 100644
index bc5bc31a0b..0000000000
--- a/_includes/api/en/4x/req-route.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<h3 id='req.route'>req.route</h3>
-
-Contains the currently-matched route, a string.  For example:
-
-```js
-app.get('/user/:id?', function userIdHandler (req, res) {
-  console.log(req.route)
-  res.send('GET')
-})
-```
-
-Example output from the previous snippet:
-
-```
-{ path: '/user/:id?',
-  stack:
-   [ { handle: [Function: userIdHandler],
-       name: 'userIdHandler',
-       params: undefined,
-       path: undefined,
-       keys: [],
-       regexp: /^\/?$/i,
-       method: 'get' } ],
-  methods: { get: true } }
-```
diff --git a/_includes/api/en/4x/req-secure.md b/_includes/api/en/4x/req-secure.md
deleted file mode 100644
index 5519638a47..0000000000
--- a/_includes/api/en/4x/req-secure.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='req.secure'>req.secure</h3>
-
-A Boolean property that is true if a TLS connection is established. Equivalent to:
-
-```js
-console.dir(req.protocol === 'https')
-// => true
-```
diff --git a/_includes/api/en/4x/req-signedCookies.md b/_includes/api/en/4x/req-signedCookies.md
deleted file mode 100644
index eb2cba8343..0000000000
--- a/_includes/api/en/4x/req-signedCookies.md
+++ /dev/null
@@ -1,17 +0,0 @@
-<h3 id='req.signedCookies'>req.signedCookies</h3>
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property
-contains signed cookies sent by the request, unsigned and ready for use. Signed cookies reside
-in a different object to show developer intent; otherwise, a malicious attack could be placed on
-`req.cookie` values (which are easy to spoof). Note that signing a cookie does not make it "hidden"
-or encrypted; but simply prevents tampering (because the secret used to sign is private).
-
-If no signed cookies are sent, the property defaults to `{}`.
-
-```js
-// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
-console.dir(req.signedCookies.user)
-// => 'tobi'
-```
-
-For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
diff --git a/_includes/api/en/4x/req-stale.md b/_includes/api/en/4x/req-stale.md
deleted file mode 100644
index ca8b479f4c..0000000000
--- a/_includes/api/en/4x/req-stale.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.stale'>req.stale</h3>
-
-Indicates whether the request is "stale," and is the opposite of `req.fresh`.
-For more information, see [req.fresh](#req.fresh).
-
-```js
-console.dir(req.stale)
-// => true
-```
diff --git a/_includes/api/en/4x/req-subdomains.md b/_includes/api/en/4x/req-subdomains.md
deleted file mode 100644
index 0f8e27a840..0000000000
--- a/_includes/api/en/4x/req-subdomains.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.subdomains'>req.subdomains</h3>
-
-An array of subdomains in the domain name of the request.
-
-```js
-// Host: "tobi.ferrets.example.com"
-console.dir(req.subdomains)
-// => ['ferrets', 'tobi']
-```
-
-The application property `subdomain offset`, which defaults to 2, is used for determining the
-beginning of the subdomain segments. To change this behavior, change its value
-using [app.set](/{{ page.lang }}/4x/api.html#app.set).
diff --git a/_includes/api/en/4x/req-xhr.md b/_includes/api/en/4x/req-xhr.md
deleted file mode 100644
index 5c1da1c704..0000000000
--- a/_includes/api/en/4x/req-xhr.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.xhr'>req.xhr</h3>
-
-A Boolean property that is `true` if the request's `X-Requested-With` header field is
-"XMLHttpRequest", indicating that the request was issued by a client library such as jQuery.
-
-```js
-console.dir(req.xhr)
-// => true
-```
diff --git a/_includes/api/en/4x/req.md b/_includes/api/en/4x/req.md
deleted file mode 100644
index 8e217a6f5b..0000000000
--- a/_includes/api/en/4x/req.md
+++ /dev/null
@@ -1,156 +0,0 @@
-<h2 id="req">Request</h2>
-
-The `req` object represents the HTTP request and has properties for the
-request query string, parameters, body, HTTP headers, and so on.  In this documentation and by convention,
-the object is always referred to as `req` (and the HTTP response is `res`) but its actual name is determined
-by the parameters to the callback function in which you're working.
-
-For example:
-
-```js
-app.get('/user/:id', function (req, res) {
-  res.send('user ' + req.params.id)
-})
-```
-
-But you could just as well have:
-
-```js
-app.get('/user/:id', function (request, response) {
-  response.send('user ' + request.params.id)
-})
-```
-
-The `req` object is an enhanced version of Node's own request object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).
-
-<h3 id='req.properties'>Properties</h3>
-
-<div class="doc-box doc-notice" markdown="1">
-In Express 4, `req.files` is no longer available on the `req` object by default. To access uploaded files
-on the `req.files` object, use multipart-handling middleware like [busboy](https://www.npmjs.
-com/package/busboy), [multer](https://www.npmjs.com/package/multer),
-[formidable](https://www.npmjs.com/package/formidable),
-[multiparty](https://www.npmjs.com/package/multiparty),
-[connect-multiparty](https://www.npmjs.com/package/connect-multiparty),
-or [pez](https://www.npmjs.com/package/pez).
-</div>
-
-<section markdown="1">
-  {% include api/en/4x/req-app.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-baseUrl.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-body.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-cookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-fresh.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-hostname.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-ip.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-ips.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-originalUrl.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-params.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-path.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-protocol.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-query.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-res.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-secure.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-signedCookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-stale.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-subdomains.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-xhr.md %}
-</section>
-
-<h3 id='req.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/4x/req-accepts.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-acceptsCharsets.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-acceptsEncodings.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-acceptsLanguages.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-is.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/req-range.md %}
-</section>
-
diff --git a/_includes/api/en/4x/res-app.md b/_includes/api/en/4x/res-app.md
deleted file mode 100644
index 19d8681d23..0000000000
--- a/_includes/api/en/4x/res-app.md
+++ /dev/null
@@ -1,5 +0,0 @@
-<h3 id='res.app'>res.app</h3>
-
-This property holds a reference to the instance of the Express application that is using the middleware.
-
-`res.app` is identical to the [req.app](#req.app) property in the request object.
diff --git a/_includes/api/en/4x/res-append.md b/_includes/api/en/4x/res-append.md
deleted file mode 100644
index c74e2fd3ef..0000000000
--- a/_includes/api/en/4x/res-append.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='res.append'>res.append(field [, value])</h3>
-
-{% include admonitions/note.html content="`res.append()` is supported by Express v4.11.0+" %}
-Appends the specified `value` to the HTTP response header `field`.  If the header is not already set,
-it creates the header with the specified value.  The `value` parameter can be a string or an array.
-
-{% include admonitions/note.html content="calling `res.set()` after `res.append()` will reset the previously-set header value." %}
-
-```js
-res.append('Link', ['<http://localhost/>', '<http://localhost:3000/>'])
-res.append('Set-Cookie', 'foo=bar; Path=/; HttpOnly')
-res.append('Warning', '199 Miscellaneous warning')
-```
diff --git a/_includes/api/en/4x/res-attachment.md b/_includes/api/en/4x/res-attachment.md
deleted file mode 100644
index 73932d14fc..0000000000
--- a/_includes/api/en/4x/res-attachment.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='res.attachment'>res.attachment([filename])</h3>
-
-Sets the HTTP response `Content-Disposition` header field to "attachment". If a `filename` is given,
-then it sets the Content-Type based on the extension name via `res.type()`,
-and sets the `Content-Disposition` "filename=" parameter.
-
-```js
-res.attachment()
-// Content-Disposition: attachment
-
-res.attachment('path/to/logo.png')
-// Content-Disposition: attachment; filename="logo.png"
-// Content-Type: image/png
-```
diff --git a/_includes/api/en/4x/res-clearCookie.md b/_includes/api/en/4x/res-clearCookie.md
deleted file mode 100644
index 5b6ea8517a..0000000000
--- a/_includes/api/en/4x/res-clearCookie.md
+++ /dev/null
@@ -1,22 +0,0 @@
-<h3 id='res.clearCookie'>res.clearCookie(name [, options])</h3>
-
-Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
-This instructs the client that the cookie has expired and is no longer valid. For more information
-about available `options`, see [res.cookie()](#res.cookie).
-
-<div class="doc-box doc-warn" markdown="1">
-If the `maxAge` or `expires` options are set, the cookie may not be cleared depending on the time values provided,
-as Express does not ignore these options. It is therefore recommended to omit these options when calling this
-method. Passing these two options has been deprecated since Express v4.20.0.
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-Web browsers and other compliant clients will only clear the cookie if the given
-`options` is identical to those given to [res.cookie()](#res.cookie), excluding
-`expires` and `maxAge`.
-</div>
-
-```js
-res.cookie('name', 'tobi', { path: '/admin' })
-res.clearCookie('name', { path: '/admin' })
-```
diff --git a/_includes/api/en/4x/res-cookie.md b/_includes/api/en/4x/res-cookie.md
deleted file mode 100644
index 814779340c..0000000000
--- a/_includes/api/en/4x/res-cookie.md
+++ /dev/null
@@ -1,87 +0,0 @@
-<h3 id='res.cookie'>res.cookie(name, value [, options])</h3>
-
-Sets cookie `name` to `value`.  The `value` parameter may be a string or object converted to JSON.
-
-The `options` parameter is an object that can have the following properties.
-
-<div class="table-scroller" markdown="1">
-
-| Property      | Type |  Description                                                             |
-|---------------|-------------------------------------------------------------------------|
-| `domain`      | String | Domain name for the cookie. Defaults to the domain name of the app.|
-| `encode`      | Function | A synchronous function used for cookie value encoding. Defaults to `encodeURIComponent`.|
-| `expires`     | Date | Expiry date of the cookie in GMT. If not specified or set to 0, creates a session cookie.|
-| `httpOnly`    | Boolean | Flags the cookie to be accessible only by the web server.|
-| `maxAge`      | Number | Convenient option for setting the expiry time relative to the current time in milliseconds.|
-| `path`        | String | Path for the cookie. Defaults to "/".|
-| `partitioned` | Boolean | Indicates that the cookie should be stored using partitioned storage. See [Cookies Having Independent Partitioned State (CHIPS)](https://developer.mozilla.org/en-US/docs/Web/Privacy/Partitioned_cookies) for more details.|
-| `priority`    | String | Value of the "Priority" **Set-Cookie** attribute.|
-| `secure`      | Boolean | Marks the cookie to be used with HTTPS only.|
-| `signed`      | Boolean | Indicates if the cookie should be signed.|
-| `sameSite`    | Boolean or String | Value of the "SameSite" **Set-Cookie** attribute. More information at [https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1](https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1).|
-
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-All `res.cookie()` does is set the HTTP `Set-Cookie` header with the options provided.
-Any option not specified defaults to the value stated in [RFC 6265](http://tools.ietf.org/html/rfc6265).
-</div>
-
-For example:
-
-```js
-res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true })
-res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true })
-```
-
-You can set multiple cookies in a single response by calling `res.cookie` multiple times, for example:
-
-```js
-res
-  .status(201)
-  .cookie('access_token', 'Bearer ' + token, {
-    expires: new Date(Date.now() + 8 * 3600000) // cookie will be removed after 8 hours
-  })
-  .cookie('test', 'test')
-  .redirect(301, '/admin')
-```
-
-The `encode` option allows you to choose the function used for cookie value encoding.
-Does not support asynchronous functions.
-
-Example use case: You need to set a domain-wide cookie for another site in your organization.
-This other site (not under your administrative control) does not use URI-encoded cookie values.
-
-```js
-// Default encoding
-res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com' })
-// Result: 'some_cross_domain_cookie=http%3A%2F%2Fmysubdomain.example.com; Domain=example.com; Path=/'
-
-// Custom encoding
-res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com', encode: String })
-// Result: 'some_cross_domain_cookie=http://mysubdomain.example.com; Domain=example.com; Path=/;'
-```
-
-The `maxAge` option is a convenience option for setting "expires" relative to the current time in milliseconds.
-The following is equivalent to the second example above.
-
-```js
-res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true })
-```
-
-You can pass an object as the `value` parameter; it is then serialized as JSON and parsed by `bodyParser()` middleware.
-
-```js
-res.cookie('cart', { items: [1, 2, 3] })
-res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 })
-```
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this method also
-supports signed cookies. Simply include the `signed` option set to `true`.
-Then `res.cookie()` will use the secret passed to `cookieParser(secret)` to sign the value.
-
-```js
-res.cookie('name', 'tobi', { signed: true })
-```
-
-Later you may access this value through the [req.signedCookie](#req.signedCookies) object.
diff --git a/_includes/api/en/4x/res-download.md b/_includes/api/en/4x/res-download.md
deleted file mode 100644
index 6851716f16..0000000000
--- a/_includes/api/en/4x/res-download.md
+++ /dev/null
@@ -1,56 +0,0 @@
-<h3 id='res.download'>res.download(path [, filename] [, options] [, fn])</h3>
-
-Transfers the file at `path` as an "attachment". Typically, browsers will prompt the user for download.
-By default, the `Content-Disposition` header "filename=" parameter is derived from the `path` argument, but can be overridden with the `filename` parameter.
-If `path` is relative, then it will be based on the current working directory of the process or
-the `root` option, if provided.
-
-<div class="doc-box doc-warn" markdown="1">
-This API provides access to data on the running file system. Ensure that either (a) the way in
-which the `path` argument was constructed is secure if it contains user input or (b) set the `root`
-option to the absolute path of a directory to contain access within.
-
-When the `root` option is provided, Express will validate that the relative path provided as
-`path` will resolve within the given `root` option.
-</div>
-
-The following table provides details on the `options` parameter.
-
-<div class="doc-box doc-info" markdown="1">
-The optional `options` argument is supported by Express v4.16.0 onwards.
-</div>
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability |
-|-----------------|-------------------------------------------------|-------------|--------------|
-| `maxAge`        | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)| 0 | 4.16+ |
-| `root`          | Root directory for relative filenames.|  | 4.18+ |
-| `lastModified`  | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.| Enabled | 4.16+ |
-| `headers`       | Object containing HTTP headers to serve with the file. The header `Content-Disposition` will be overridden by the `filename` argument.|  | 4.16+ |
-| `dotfiles`      | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".| "ignore" | 4.16+ |
-| `acceptRanges`  | Enable or disable accepting ranged requests. | `true` | 4.16+ |
-| `cacheControl`  | Enable or disable setting `Cache-Control` response header.| `true` | 4.16+ |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false` | 4.16+ |
-
-</div>
-
-The method invokes the callback function `fn(err)` when the transfer is complete
-or when an error occurs. If the callback function is specified and an error occurs,
-the callback function must explicitly handle the response process either by
-ending the request-response cycle, or by passing control to the next route.
-
-```js
-res.download('/report-12345.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf', function (err) {
-  if (err) {
-    // Handle error, but keep in mind the response may be partially-sent
-    // so check res.headersSent
-  } else {
-    // decrement a download credit, etc.
-  }
-})
-```
diff --git a/_includes/api/en/4x/res-end.md b/_includes/api/en/4x/res-end.md
deleted file mode 100644
index 2906805fea..0000000000
--- a/_includes/api/en/4x/res-end.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='res.end'>res.end([data[, encoding]][, callback])</h3>
-
-Ends the response process. This method actually comes from Node core, specifically the [response.end() method of http.ServerResponse](https://nodejs.org/api/http.html#responseenddata-encoding-callback).
-
-Use to quickly end the response without any data. If you need to respond with data, instead use methods such as [res.send()](#res.send) and [res.json()](#res.json).
-
-```js
-res.end()
-res.status(404).end()
-```
diff --git a/_includes/api/en/4x/res-format.md b/_includes/api/en/4x/res-format.md
deleted file mode 100644
index 476a2caea7..0000000000
--- a/_includes/api/en/4x/res-format.md
+++ /dev/null
@@ -1,52 +0,0 @@
-<h3 id='res.format'>res.format(object)</h3>
-
-Performs content-negotiation on the `Accept` HTTP header on the request object, when present.
-It uses [req.accepts()](#req.accepts) to select a handler for the request, based on the acceptable
-types ordered by their quality values. If the header is not specified, the first callback is invoked.
-When no match is found, the server responds with 406 "Not Acceptable", or invokes the `default` callback.
-
-The `Content-Type` response header is set when a callback is selected. However, you may alter
-this within the callback using methods such as `res.set()` or `res.type()`.
-
-The following example would respond with `{ "message": "hey" }` when the `Accept` header field is set
-to "application/json" or "\*/json" (however if it is "\*/\*", then the response will be "hey").
-
-```js
-res.format({
-  'text/plain': function () {
-    res.send('hey')
-  },
-
-  'text/html': function () {
-    res.send('<p>hey</p>')
-  },
-
-  'application/json': function () {
-    res.send({ message: 'hey' })
-  },
-
-  default: function () {
-    // log the request and respond with 406
-    res.status(406).send('Not Acceptable')
-  }
-})
-```
-
-In addition to canonicalized MIME types, you may also use extension names mapped
-to these types for a slightly less verbose implementation:
-
-```js
-res.format({
-  text: function () {
-    res.send('hey')
-  },
-
-  html: function () {
-    res.send('<p>hey</p>')
-  },
-
-  json: function () {
-    res.send({ message: 'hey' })
-  }
-})
-```
diff --git a/_includes/api/en/4x/res-get.md b/_includes/api/en/4x/res-get.md
deleted file mode 100644
index 8aefb205ef..0000000000
--- a/_includes/api/en/4x/res-get.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='res.get'>res.get(field)</h3>
-
-Returns the HTTP response header specified by `field`.
-The match is case-insensitive.
-
-```js
-res.get('Content-Type')
-// => "text/plain"
-```
diff --git a/_includes/api/en/4x/res-headersSent.md b/_includes/api/en/4x/res-headersSent.md
deleted file mode 100644
index 3f7923ee7d..0000000000
--- a/_includes/api/en/4x/res-headersSent.md
+++ /dev/null
@@ -1,11 +0,0 @@
-<h3 id='res.headersSent'>res.headersSent</h3>
-
-Boolean property that indicates if the app sent HTTP headers for the response.
-
-```js
-app.get('/', function (req, res) {
-  console.dir(res.headersSent) // false
-  res.send('OK')
-  console.dir(res.headersSent) // true
-})
-```
diff --git a/_includes/api/en/4x/res-json.md b/_includes/api/en/4x/res-json.md
deleted file mode 100644
index 8e699a7ed5..0000000000
--- a/_includes/api/en/4x/res-json.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='res.json'>res.json([body])</h3>
-
-Sends a JSON response. This method sends a response (with the correct content-type) that is the parameter converted to a 
-JSON string using [JSON.stringify()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify).
-
-The parameter can be any JSON type, including object, array, string, Boolean, number, or null,
-and you can also use it to convert other values to JSON.
-
-```js
-res.json(null)
-res.json({ user: 'tobi' })
-res.status(500).json({ error: 'message' })
-```
diff --git a/_includes/api/en/4x/res-jsonp.md b/_includes/api/en/4x/res-jsonp.md
deleted file mode 100644
index edb7e45466..0000000000
--- a/_includes/api/en/4x/res-jsonp.md
+++ /dev/null
@@ -1,32 +0,0 @@
-<h3 id='res.jsonp'>res.jsonp([body])</h3>
-
-Sends a JSON response with JSONP support. This method is identical to `res.json()`,
-except that it opts-in to JSONP callback support.
-
-```js
-res.jsonp(null)
-// => callback(null)
-
-res.jsonp({ user: 'tobi' })
-// => callback({ "user": "tobi" })
-
-res.status(500).jsonp({ error: 'message' })
-// => callback({ "error": "message" })
-```
-
-By default, the JSONP callback name is simply `callback`. Override this with the
-<a href="#app.settings.table">jsonp callback name</a> setting.
-
-The following are some examples of JSONP responses using the same code:
-
-```js
-// ?callback=foo
-res.jsonp({ user: 'tobi' })
-// => foo({ "user": "tobi" })
-
-app.set('jsonp callback name', 'cb')
-
-// ?cb=foo
-res.status(500).jsonp({ error: 'message' })
-// => foo({ "error": "message" })
-```
diff --git a/_includes/api/en/4x/res-links.md b/_includes/api/en/4x/res-links.md
deleted file mode 100644
index 17164155d4..0000000000
--- a/_includes/api/en/4x/res-links.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='res.links'>res.links(links)</h3>
-
-Joins the `links` provided as properties of the parameter to populate the response's
-`Link` HTTP header field.
-
-For example, the following call:
-
-```js
-res.links({
-  next: 'http://api.example.com/users?page=2',
-  last: 'http://api.example.com/users?page=5'
-})
-```
-
-Yields the following results:
-
-```
-Link: <http://api.example.com/users?page=2>; rel="next",
-      <http://api.example.com/users?page=5>; rel="last"
-```
diff --git a/_includes/api/en/4x/res-locals.md b/_includes/api/en/4x/res-locals.md
deleted file mode 100644
index 38949ea971..0000000000
--- a/_includes/api/en/4x/res-locals.md
+++ /dev/null
@@ -1,28 +0,0 @@
-<h3 id='res.locals'>res.locals</h3>
-
-Use this property to set variables accessible in templates rendered with [res.render](#res.render).
-The variables set on `res.locals` are available within a single request-response cycle, and will not
-be shared between requests.
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-In order to keep local variables for use in template rendering between requests, use
-[app.locals](#app.locals) instead.
-
-This property is useful for exposing request-level information such as the request path name,
-authenticated user, user settings, and so on to templates rendered within the application.
-
-```js
-app.use(function (req, res, next) {
-  // Make `user` and `authenticated` available in templates
-  res.locals.user = req.user
-  res.locals.authenticated = !req.user.anonymous
-  next()
-})
-```
diff --git a/_includes/api/en/4x/res-location.md b/_includes/api/en/4x/res-location.md
deleted file mode 100644
index c093ef3966..0000000000
--- a/_includes/api/en/4x/res-location.md
+++ /dev/null
@@ -1,24 +0,0 @@
-<h3 id='res.location'>res.location(path)</h3>
-
-Sets the response `Location` HTTP header to the specified `path` parameter.
-
-```js
-res.location('/foo/bar')
-res.location('http://example.com')
-res.location('back')
-```
-
-{% include admonitions/note.html content="`'back'` was deprecated in 4.21.0, use `req.get('Referrer') || '/'` as an argument instead." %}
-
-A `path` value of "back" has a special meaning, it refers to the URL specified in the `Referer` header of the request. If the `Referer` header was not specified, it refers to "/".
-
-See also [Security best practices: Prevent open redirect 
-vulnerabilities](http://expressjs.com/en/advanced/best-practice-security.html#prevent-open-redirects). 
-
-<div class='doc-box doc-warn' markdown="1">
-After encoding the URL, if not encoded already, Express passes the specified URL to the browser in the `Location` header,
-without any validation.
-
-Browsers take the responsibility of deriving the intended URL from the current URL
-or the referring URL, and the URL specified in the `Location` header; and redirect the user accordingly.
-</div>
diff --git a/_includes/api/en/4x/res-redirect.md b/_includes/api/en/4x/res-redirect.md
deleted file mode 100644
index 0ff536ef32..0000000000
--- a/_includes/api/en/4x/res-redirect.md
+++ /dev/null
@@ -1,58 +0,0 @@
-<h3 id='res.redirect'>res.redirect([status,] path)</h3>
-
-Redirects to the URL derived from the specified `path`, with specified `status`, a positive integer
-that corresponds to an [HTTP status code](https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes) .
-If not specified, `status` defaults to "302 "Found".
-
-```js
-res.redirect('/foo/bar')
-res.redirect('http://example.com')
-res.redirect(301, 'http://example.com')
-res.redirect('../login')
-```
-Redirects can be a fully-qualified URL for redirecting to a different site:
-
-```js
-res.redirect('http://google.com')
-```
-Redirects can be relative to the root of the host name. For example, if the
-application is on `http://example.com/admin/post/new`, the following
-would redirect to the URL `http://example.com/admin`:
-
-```js
-res.redirect('/admin')
-```
-
-Redirects can be relative to the current URL. For example,
-from `http://example.com/blog/admin/` (notice the trailing slash), the following
-would redirect to the URL `http://example.com/blog/admin/post/new`.
-
-```js
-res.redirect('post/new')
-```
-
-Redirecting to `post/new` from `http://example.com/blog/admin` (no trailing slash),
-will redirect to `http://example.com/blog/post/new`.
-
-If you found the above behavior confusing, think of path segments as directories
-(with trailing slashes) and files, it will start to make sense.
-
-Path-relative redirects are also possible. If you were on
-`http://example.com/admin/post/new`, the following would redirect to
-`http://example.com/admin/post`:
-
-```js
-res.redirect('..')
-```
-
-A `back` redirection redirects the request back to the [referer](http://en.wikipedia.org/wiki/HTTP_referer),
-defaulting to `/` when the referer is missing.
-
-```js
-res.redirect('back')
-```
-
-{% include admonitions/note.html content="`back` redirect was deprecated in 4.21.0, use `req.get('Referrer') || '/'` as an argument instead." %}
-
-See also [Security best practices: Prevent open redirect 
-vulnerabilities](http://expressjs.com/en/advanced/best-practice-security.html#prevent-open-redirects). 
diff --git a/_includes/api/en/4x/res-render.md b/_includes/api/en/4x/res-render.md
deleted file mode 100644
index 2bcb4e60cb..0000000000
--- a/_includes/api/en/4x/res-render.md
+++ /dev/null
@@ -1,45 +0,0 @@
-<h3 id='res.render'>res.render(view [, locals] [, callback])</h3>
-
-Renders a `view` and sends the rendered HTML string to the client.
-Optional parameters:
-
-- `locals`, an object whose properties define local variables for the view.
-- `callback`, a callback function. If provided, the method returns both the possible error and rendered string, but does not perform an automated response. When an error occurs, the method invokes `next(err)` internally.
-
-The `view` argument is a string that is the file path of the view file to render. This can be an absolute path, or a path relative to the `views` setting. If the path does not contain a file extension, then the `view engine` setting determines the file extension. If the path does contain a file extension, then Express will load the module for the specified template engine (via `require()`) and render it using the loaded module's `__express` function.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-<div class="doc-box doc-warn" markdown="1">
-The `view` argument performs file system operations like reading a file from
-disk and evaluating Node.js modules, and as so for security reasons should not
-contain input from the end-user.
-</div>
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-The local variable `cache` enables view caching. Set it to `true`,
-to cache the view during development; view caching is enabled in production by default.
-</div>
-
-```js
-// send the rendered view to the client
-res.render('index')
-
-// if a callback is specified, the rendered HTML string has to be sent explicitly
-res.render('index', function (err, html) {
-  res.send(html)
-})
-
-// pass a local variable to the view
-res.render('user', { name: 'Tobi' }, function (err, html) {
-  // ...
-})
-```
diff --git a/_includes/api/en/4x/res-req.md b/_includes/api/en/4x/res-req.md
deleted file mode 100644
index 8763653d9f..0000000000
--- a/_includes/api/en/4x/res-req.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='res.req'>res.req</h3>
-
-This property holds a reference to the <a href="#req">request object</a>
-that relates to this response object.
diff --git a/_includes/api/en/4x/res-send.md b/_includes/api/en/4x/res-send.md
deleted file mode 100644
index 8c902e568a..0000000000
--- a/_includes/api/en/4x/res-send.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='res.send'>res.send([body])</h3>
-
-Sends the HTTP response.
-
-The `body` parameter can be a `Buffer` object, a `String`, an object, `Boolean`, or an `Array`.
-For example:
-
-```js
-res.send(Buffer.from('whoop'))
-res.send({ some: 'json' })
-res.send('<p>some html</p>')
-res.status(404).send('Sorry, we cannot find that!')
-res.status(500).send({ error: 'something blew up' })
-```
-
-This method performs many useful tasks for simple non-streaming responses:
-For example, it automatically assigns the `Content-Length` HTTP response header field
-(unless previously defined) and provides automatic HEAD and HTTP cache freshness support.
-
-When the parameter is a `Buffer` object, the method sets the `Content-Type`
-response header field  to "application/octet-stream", unless previously defined as shown below:
-
-```js
-res.set('Content-Type', 'text/html')
-res.send(Buffer.from('<p>some html</p>'))
-```
-
-When the parameter is a `String`, the method sets the `Content-Type` to "text/html":
-
-```js
-res.send('<p>some html</p>')
-```
-
-When the parameter is an `Array` or `Object`, Express responds with the JSON representation:
-
-```js
-res.send({ user: 'tobi' })
-res.send([1, 2, 3])
-```
diff --git a/_includes/api/en/4x/res-sendFile.md b/_includes/api/en/4x/res-sendFile.md
deleted file mode 100644
index 7c72613c29..0000000000
--- a/_includes/api/en/4x/res-sendFile.md
+++ /dev/null
@@ -1,84 +0,0 @@
-<h3 id='res.sendFile'>res.sendFile(path [, options] [, fn])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-`res.sendFile()` is supported by Express v4.8.0 onwards.
-</div>
-
-Transfers the file at the given `path`. Sets the `Content-Type` response HTTP header field
-based on the filename's extension. Unless the `root` option is set in
-the options object, `path` must be an absolute path to the file.
-
-<div class="doc-box doc-warn" markdown="1">
-This API provides access to data on the running file system. Ensure that either (a) the way in
-which the `path` argument was constructed into an absolute path is secure if it contains user
-input or (b) set the `root` option to the absolute path of a directory to contain access within.
-
-When the `root` option is provided, the `path` argument is allowed to be a relative path,
-including containing `..`. Express will validate that the relative path provided as `path` will
-resolve within the given `root` option.
-</div>
-
-The following table provides details on the `options` parameter.
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability |
-|-----------------|-------------------------------------------------|-------------|--------------|
-|`maxAge`         | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)| 0 |  |
-| `root`          | Root directory for relative filenames.|  |  |
-| `lastModified`  | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.| Enabled | 4.9.0+ |
-| `headers`       | Object containing HTTP headers to serve with the file.|  |  |
-| `dotfiles`      | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".| "ignore" | &nbsp; |
-| `acceptRanges`  | Enable or disable accepting ranged requests. | `true` | 4.14+ |
-| `cacheControl`  | Enable or disable setting `Cache-Control` response header.| `true` | 4.14+ |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false` | 4.16+ |
-
-</div>
-
-The method invokes the callback function `fn(err)` when the transfer is complete
-or when an error occurs. If the callback function is specified and an error occurs,
-the callback function must explicitly handle the response process either by
-ending the request-response cycle, or by passing control to the next route.
-
-Here is an example of using `res.sendFile` with all its arguments.
-
-```js
-app.get('/file/:name', function (req, res, next) {
-  var options = {
-    root: path.join(__dirname, 'public'),
-    dotfiles: 'deny',
-    headers: {
-      'x-timestamp': Date.now(),
-      'x-sent': true
-    }
-  }
-
-  var fileName = req.params.name
-  res.sendFile(fileName, options, function (err) {
-    if (err) {
-      next(err)
-    } else {
-      console.log('Sent:', fileName)
-    }
-  })
-})
-```
-
-The following example illustrates using
-`res.sendFile` to provide fine-grained support for serving files:
-
-```js
-app.get('/user/:uid/photos/:file', function (req, res) {
-  var uid = req.params.uid
-  var file = req.params.file
-
-  req.user.mayViewFilesFrom(uid, function (yes) {
-    if (yes) {
-      res.sendFile('/uploads/' + uid + '/' + file)
-    } else {
-      res.status(403).send("Sorry! You can't see that.")
-    }
-  })
-})
-```
-For more information, or if you have issues or concerns, see [send](https://github.com/pillarjs/send).
diff --git a/_includes/api/en/4x/res-sendStatus.md b/_includes/api/en/4x/res-sendStatus.md
deleted file mode 100644
index 4439f0216d..0000000000
--- a/_includes/api/en/4x/res-sendStatus.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='res.sendStatus'>res.sendStatus(statusCode)</h3>
-
-Sets the response HTTP status code to `statusCode` and sends the registered status message as the text response body. If an unknown status code is specified, the response body will just be the code number.
-
-```js
-res.sendStatus(404)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Some versions of Node.js will throw when `res.statusCode` is set to an
-invalid HTTP status code (outside of the range `100` to `599`). Consult
-the HTTP server documentation for the Node.js version being used.
-</div>
-
-[More about HTTP Status Codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
diff --git a/_includes/api/en/4x/res-set.md b/_includes/api/en/4x/res-set.md
deleted file mode 100644
index b91698d4b1..0000000000
--- a/_includes/api/en/4x/res-set.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.set'>res.set(field [, value])</h3>
-
-Sets the response's HTTP header `field` to `value`.
-To set multiple fields at once, pass an object as the parameter.
-
-```js
-res.set('Content-Type', 'text/plain')
-
-res.set({
-  'Content-Type': 'text/plain',
-  'Content-Length': '123',
-  ETag: '12345'
-})
-```
-
-Aliased as `res.header(field [, value])`.
diff --git a/_includes/api/en/4x/res-status.md b/_includes/api/en/4x/res-status.md
deleted file mode 100644
index 9cb9d44e94..0000000000
--- a/_includes/api/en/4x/res-status.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='res.status'>res.status(code)</h3>
-
-Sets the HTTP status for the response.
-It is a chainable alias of Node's [response.statusCode](http://nodejs.org/api/http.html#http_response_statuscode).
-
-```js
-res.status(403).end()
-res.status(400).send('Bad Request')
-res.status(404).sendFile('/absolute/path/to/404.png')
-```
diff --git a/_includes/api/en/4x/res-type.md b/_includes/api/en/4x/res-type.md
deleted file mode 100644
index 2d224ede79..0000000000
--- a/_includes/api/en/4x/res-type.md
+++ /dev/null
@@ -1,18 +0,0 @@
-<h3 id='res.type'>res.type(type)</h3>
-
-Sets the `Content-Type` HTTP header to the MIME type as determined by the specified `type`. If `type` contains the "/" character, then it sets the `Content-Type` to the exact value of `type`, otherwise it is assumed to be a file extension and the MIME type is looked up in a mapping using the `express.static.mime.lookup()` method.
-
-```js
-res.type('.html')
-// => 'text/html'
-res.type('html')
-// => 'text/html'
-res.type('json')
-// => 'application/json'
-res.type('application/json')
-// => 'application/json'
-res.type('png')
-// => 'image/png'
-```
-
-Aliased as `res.contentType(type)`.
diff --git a/_includes/api/en/4x/res-vary.md b/_includes/api/en/4x/res-vary.md
deleted file mode 100644
index 956aab25ae..0000000000
--- a/_includes/api/en/4x/res-vary.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='res.vary'>res.vary(field)</h3>
-
-Adds the field to the `Vary` response header, if it is not there already.
-
-```js
-res.vary('User-Agent').render('docs')
-```
diff --git a/_includes/api/en/4x/res.md b/_includes/api/en/4x/res.md
deleted file mode 100644
index 3af14b5ee5..0000000000
--- a/_includes/api/en/4x/res.md
+++ /dev/null
@@ -1,130 +0,0 @@
-<h2 id="res">Response</h2>
-
-The `res` object represents the HTTP response that an Express app sends when it gets an HTTP request.
-
-In this documentation and by convention,
-the object is always referred to as `res` (and the HTTP request is `req`) but its actual name is determined
-by the parameters to the callback function in which you're working.
-
-For example:
-
-```js
-app.get('/user/:id', function (req, res) {
-  res.send('user ' + req.params.id)
-})
-```
-
-But you could just as well have:
-
-```js
-app.get('/user/:id', function (request, response) {
-  response.send('user ' + request.params.id)
-})
-```
-
-The `res` object is an enhanced version of Node's own response object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
-
-<h3 id='res.properties'>Properties</h3>
-
-<section markdown="1">
-  {% include api/en/4x/res-app.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-headersSent.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-locals.md %}
-</section>
-
-<h3 id='res.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/4x/res-append.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-attachment.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-cookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-clearCookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-download.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-end.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-format.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-json.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-jsonp.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-links.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-location.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-redirect.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-render.md %}
-</section>
-
-<section>
-  {% include api/en/4x/res-req.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-send.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-sendFile.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-sendStatus.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-status.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-type.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/res-vary.md %}
-</section>
diff --git a/_includes/api/en/4x/router-METHOD.md b/_includes/api/en/4x/router-METHOD.md
deleted file mode 100644
index 82dd5fc866..0000000000
--- a/_includes/api/en/4x/router-METHOD.md
+++ /dev/null
@@ -1,42 +0,0 @@
-<h3 id='router.METHOD'>router.METHOD(path, [callback, ...] callback)</h3>
-
-The `router.METHOD()` methods provide the routing functionality in Express,
-where METHOD is one of the HTTP methods, such as GET, PUT, POST, and so on,
-in lowercase.  Thus, the actual methods are `router.get()`, `router.post()`,
-`router.put()`, and so on.
-
-<div class="doc-box doc-info" markdown="1">
-  The `router.get()` function is automatically called for the HTTP `HEAD` method in
-  addition to the `GET` method if `router.head()` was not called for the
-  path before `router.get()`.
-</div>
-
-You can provide multiple callbacks, and all are treated equally, and behave just
-like middleware, except that these callbacks may invoke `next('route')`
-to bypass the remaining route callback(s).  You can use this mechanism to perform
-pre-conditions on a route then pass control to subsequent routes when there is no
-reason to proceed with the route matched.
-
-The following snippet illustrates the most simple route definition possible.
-Express translates the path strings to regular expressions, used internally
-to match incoming requests. Query strings are _not_ considered when performing
-these matches, for example "GET /" would match the following route, as would
-"GET /?name=tobi".
-
-```js
-router.get('/', function (req, res) {
-  res.send('hello world')
-})
-```
-
-You can also use regular expressions&mdash;useful if you have very specific
-constraints, for example the following would match "GET /commits/71dbb9c" as well
-as "GET /commits/71dbb9c..4c084f9".
-
-```js
-router.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, function (req, res) {
-  var from = req.params[0]
-  var to = req.params[1] || 'HEAD'
-  res.send('commit range ' + from + '..' + to)
-})
-```
diff --git a/_includes/api/en/4x/router-Router.md b/_includes/api/en/4x/router-Router.md
deleted file mode 100644
index 664ffb34c2..0000000000
--- a/_includes/api/en/4x/router-Router.md
+++ /dev/null
@@ -1,2 +0,0 @@
-<h3 id='router'>Router([options])</h3>
-
diff --git a/_includes/api/en/4x/router-all.md b/_includes/api/en/4x/router-all.md
deleted file mode 100644
index 7fe32b156b..0000000000
--- a/_includes/api/en/4x/router-all.md
+++ /dev/null
@@ -1,31 +0,0 @@
-<h3 id='router.all'>router.all(path, [callback, ...] callback)</h3>
-
-This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs).
-
-This method is extremely useful for
-mapping "global" logic for specific path prefixes or arbitrary matches.
-For example, if you placed the following route at the top of all other
-route definitions, it would require that all routes from that point on
-would require authentication, and automatically load a user. Keep in mind
-that these callbacks do not have to act as end points; `loadUser`
-can perform a task, then call `next()` to continue matching subsequent
-routes.
-
-```js
-router.all('*', requireAuthentication, loadUser)
-```
-
-Or the equivalent:
-
-```js
-router.all('*', requireAuthentication)
-router.all('*', loadUser)
-```
-
-Another example of this is white-listed "global" functionality. Here
-the example is much like before, but it only restricts paths prefixed with
-"/api":
-
-```js
-router.all('/api/*', requireAuthentication)
-```
diff --git a/_includes/api/en/4x/router-param.md b/_includes/api/en/4x/router-param.md
deleted file mode 100644
index 20b35d1afe..0000000000
--- a/_includes/api/en/4x/router-param.md
+++ /dev/null
@@ -1,123 +0,0 @@
-<h3 id='router.param'>router.param(name, callback)</h3>
-
-Adds callback triggers to route parameters, where `name` is the name of the parameter and `callback` is the callback function. Although `name` is technically optional, using this method without it is deprecated starting with Express v4.11.0 (see below).
-
-The parameters of the callback function are:
-
-- `req`, the request object.
-- `res`, the response object.
-- `next`, indicating the next middleware function.
-- The value of the `name` parameter.
-- The name of the parameter.
-
-<div class="doc-box doc-info" markdown="1">
-Unlike `app.param()`, `router.param()` does not accept an array of route parameters.
-</div>
-
-For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
-
-```js
-router.param('user', function (req, res, next, id) {
-  // try to get the user details from the User model and attach it to the request object
-  User.find(id, function (err, user) {
-    if (err) {
-      next(err)
-    } else if (user) {
-      req.user = user
-      next()
-    } else {
-      next(new Error('failed to load user'))
-    }
-  })
-})
-```
-
-Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `router` will be triggered only by route parameters defined on `router` routes.
-
-A param callback will be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
-
-```js
-router.param('id', function (req, res, next, id) {
-  console.log('CALLED ONLY ONCE')
-  next()
-})
-
-router.get('/user/:id', function (req, res, next) {
-  console.log('although this matches')
-  next()
-})
-
-router.get('/user/:id', function (req, res) {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42`, the following is printed:
-
-```
-CALLED ONLY ONCE
-although this matches
-and this matches too
-```
-
-<div class="doc-box doc-warn" markdown="1">
-The following section describes `router.param(callback)`, which is deprecated as of v4.11.0.
-</div>
-
-The behavior of the `router.param(name, callback)` method can be altered entirely by passing only a function to `router.param()`. This function is a custom implementation of how `router.param(name, callback)` should behave - it accepts two parameters and must return a middleware.
-
-The first parameter of this function is the name of the URL parameter that should be captured, the second parameter can be any JavaScript object which might be used for returning the middleware implementation.
-
-The middleware returned by the function decides the behavior of what happens when a URL parameter is captured.
-
-In this example, the `router.param(name, callback)` signature is modified to `router.param(name, accessId)`. Instead of accepting a name and a callback, `router.param()` will now accept a name and a number.
-
-```js
-var express = require('express')
-var app = express()
-var router = express.Router()
-
-// customizing the behavior of router.param()
-router.param(function (param, option) {
-  return function (req, res, next, val) {
-    if (val === option) {
-      next()
-    } else {
-      res.sendStatus(403)
-    }
-  }
-})
-
-// using the customized router.param()
-router.param('id', '1337')
-
-// route to trigger the capture
-router.get('/user/:id', function (req, res) {
-  res.send('OK')
-})
-
-app.use(router)
-
-app.listen(3000, function () {
-  console.log('Ready')
-})
-```
-
-In this example, the `router.param(name, callback)` signature remains the same, but instead of a middleware callback, a custom data type checking function has been defined to validate the data type of the user id.
-
-```js
-router.param(function (param, validator) {
-  return function (req, res, next, val) {
-    if (validator(val)) {
-      next()
-    } else {
-      res.sendStatus(403)
-    }
-  }
-})
-
-router.param('id', function (candidate) {
-  return !isNaN(parseFloat(candidate)) && isFinite(candidate)
-})
-```
diff --git a/_includes/api/en/4x/router-route.md b/_includes/api/en/4x/router-route.md
deleted file mode 100644
index 0f03d39adc..0000000000
--- a/_includes/api/en/4x/router-route.md
+++ /dev/null
@@ -1,48 +0,0 @@
-<h3 id='router.route'>router.route(path)</h3>
-
-Returns an instance of a single route which you can then use to handle HTTP verbs
-with optional middleware. Use `router.route()` to avoid duplicate route naming and
-thus typing errors.
-
-Building on the `router.param()` example above, the following code shows how to use
-`router.route()` to specify various HTTP method handlers.
-
-```js
-var router = express.Router()
-
-router.param('user_id', function (req, res, next, id) {
-  // sample user, would actually fetch from DB, etc...
-  req.user = {
-    id: id,
-    name: 'TJ'
-  }
-  next()
-})
-
-router.route('/users/:user_id')
-  .all(function (req, res, next) {
-    // runs for all HTTP verbs first
-    // think of it as route specific middleware!
-    next()
-  })
-  .get(function (req, res, next) {
-    res.json(req.user)
-  })
-  .put(function (req, res, next) {
-    // just an example of maybe updating the user
-    req.user.name = req.params.name
-    // save user ... etc
-    res.json(req.user)
-  })
-  .post(function (req, res, next) {
-    next(new Error('not implemented'))
-  })
-  .delete(function (req, res, next) {
-    next(new Error('not implemented'))
-  })
-```
-
-This approach re-uses the single `/users/:user_id` path and adds handlers for
-various HTTP methods.
-
-{% include admonitions/note.html content="When you use `router.route()`, middleware ordering is based on when the _route_ is created, not when method handlers are added to the route.  For this purpose, you can consider method handlers to belong to the route to which they were added." %}
diff --git a/_includes/api/en/4x/router-use.md b/_includes/api/en/4x/router-use.md
deleted file mode 100644
index 776a112fa0..0000000000
--- a/_includes/api/en/4x/router-use.md
+++ /dev/null
@@ -1,107 +0,0 @@
-<h3 id='router.use'>router.use([path], [function, ...] function)</h3>
-
-Uses the specified middleware function or functions, with optional mount path `path`, that defaults to "/".
-
-This method is similar to [app.use()](#app.use). A simple example and use case is described below.
-See [app.use()](#app.use) for more information.
-
-Middleware is like a plumbing pipe: requests start at the first middleware function defined
-and work their way "down" the middleware stack processing for each path they match.
-
-```js
-var express = require('express')
-var app = express()
-var router = express.Router()
-
-// simple logger for this router's requests
-// all requests to this router will first hit this middleware
-router.use(function (req, res, next) {
-  console.log('%s %s %s', req.method, req.url, req.path)
-  next()
-})
-
-// this will only be invoked if the path starts with /bar from the mount point
-router.use('/bar', function (req, res, next) {
-  // ... maybe some additional /bar logging ...
-  next()
-})
-
-// always invoked
-router.use(function (req, res, next) {
-  res.send('Hello World')
-})
-
-app.use('/foo', router)
-
-app.listen(3000)
-```
-
-The "mount" path is stripped and is _not_ visible to the middleware function.
-The main effect of this feature is that a mounted middleware function may operate without
-code changes regardless of its "prefix" pathname.
-
-The order in which you define middleware with `router.use()` is very important.
-They are invoked sequentially, thus the order defines middleware precedence. For example,
-usually a logger is the very first middleware you would use, so that every request gets logged.
-
-```js
-var logger = require('morgan')
-var path = require('path')
-
-router.use(logger())
-router.use(express.static(path.join(__dirname, 'public')))
-router.use(function (req, res) {
-  res.send('Hello')
-})
-```
-
-Now suppose you wanted to ignore logging requests for static files, but to continue
-logging routes and middleware defined after `logger()`.  You would simply move the call to `express.static()` to the top,
-before adding the logger middleware:
-
-```js
-router.use(express.static(path.join(__dirname, 'public')))
-router.use(logger())
-router.use(function (req, res) {
-  res.send('Hello')
-})
-```
-
-Another example is serving files from multiple directories,
-giving precedence to "./public" over the others:
-
-```js
-router.use(express.static(path.join(__dirname, 'public')))
-router.use(express.static(path.join(__dirname, 'files')))
-router.use(express.static(path.join(__dirname, 'uploads')))
-```
-
-The `router.use()` method also supports named parameters so that your mount points
-for other routers can benefit from preloading using named parameters.
-
-__NOTE__: Although these middleware functions are added via a particular router, _when_
-they run is defined by the path they are attached to (not the router). Therefore,
-middleware added via one router may run for other routers if its routes
-match. For example, this code shows two different routers mounted on the same path:
-
-```js
-var authRouter = express.Router()
-var openRouter = express.Router()
-
-authRouter.use(require('./authenticate').basic(usersdb))
-
-authRouter.get('/:user_id/edit', function (req, res, next) {
-  // ... Edit user UI ...
-})
-openRouter.get('/', function (req, res, next) {
-  // ... List users ...
-})
-openRouter.get('/:user_id', function (req, res, next) {
-  // ... View user ...
-})
-
-app.use('/users', authRouter)
-app.use('/users', openRouter)
-```
-
-Even though the authentication middleware was added via the `authRouter` it will run on the routes defined by the `openRouter` as well since both routers were mounted on `/users`.  To avoid this behavior, use different paths for each router.
diff --git a/_includes/api/en/4x/router.md b/_includes/api/en/4x/router.md
deleted file mode 100644
index 4198420a59..0000000000
--- a/_includes/api/en/4x/router.md
+++ /dev/null
@@ -1,62 +0,0 @@
-<h2 id="router">Router</h2>
-
-<section markdown="1">
-A `router` object is an instance of middleware and routes. You can think of it
-as a "mini-application," capable only of performing middleware and routing
-functions. Every Express application has a built-in app router.
-
-A router behaves like middleware itself, so you can use it as an argument to
-[app.use()](#app.use) or as the argument to another router's  [use()](#router.use) method.
-
-The top-level `express` object has a [Router()](#express.router) method that creates a new `router` object.
-
-Once you've created a router object, you can add middleware and HTTP method routes (such as `get`, `put`, `post`,
-and so on) to it just like an application.  For example:
-
-```js
-// invoked for any requests passed to this router
-router.use(function (req, res, next) {
-  // .. some logic here .. like any other middleware
-  next()
-})
-
-// will handle any request that ends in /events
-// depends on where the router is "use()'d"
-router.get('/events', function (req, res, next) {
-  // ..
-})
-```
-
-You can then use a router for a particular root URL in this way separating your routes into files or even mini-apps.
-
-```js
-// only requests to /calendar/* will be sent to our "router"
-app.use('/calendar', router)
-```
-
-Keep in mind that any middleware applied to a router will run for all requests on that router's path, even those that aren't part of the router.
-
-
-</section>
-
-<h3 id='router.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/4x/router-all.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/router-METHOD.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/router-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/router-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/4x/router-use.md %}
-</section>
diff --git a/_includes/api/en/4x/routing-args.html b/_includes/api/en/4x/routing-args.html
deleted file mode 100644
index 6dd9fe8712..0000000000
--- a/_includes/api/en/4x/routing-args.html
+++ /dev/null
@@ -1,55 +0,0 @@
-<h4>Arguments</h4>
-
-<div class="table-scroller">
-  <table>
-    <thead>
-      <tr>
-        <th scope="col">Argument</th>
-        <th scope="col">Description</th>
-        <th scope="col">Default</th>
-      </tr>
-    </thead>
-    <tbody>
-      <tr>
-        <th scope="row"><code>path</code></th>
-        <td>
-          The path for which the middleware function is invoked; can be any of:
-          <ul>
-            <li>A string representing a path.</li>
-            <li>A path pattern.</li>
-            <li>A regular expression pattern to match paths.</li>
-            <li>An array of combinations of any of the above.</li>
-          </ul>
-          For examples, see <a href="#path-examples">Path examples</a>.
-        </td>
-        <td>'/' (root path)</td>
-      </tr>
-      <tr>
-        <th scope="row"><code>callback</code></th>
-        <td>
-          Callback functions; can be:
-          <ul>
-            <li>A middleware function.</li>
-            <li>A series of middleware functions (separated by commas).</li>
-            <li>An array of middleware functions.</li>
-            <li>A combination of all of the above.</li>
-          </ul>
-          <p>
-            You can provide multiple callback functions that behave just like middleware, except
-            that these callbacks can invoke <code>next('route')</code> to bypass
-            the remaining route callback(s). You can use this mechanism to impose pre-conditions
-            on a route, then pass control to subsequent routes if there is no reason to proceed with the current route.
-          </p>
-          <p>
-            Since <a href="#router">router</a> and <a href="#application">app</a> implement the middleware interface,
-            you can use them as you would any other middleware function.
-          </p>
-          <p>
-            For examples, see <a href="#middleware-callback-function-examples">Middleware callback function examples</a>.
-          </p>
-        </td>
-        <td>None</td>
-      </tr>
-    </tbody>
-  </table>
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/5x/app-METHOD.md b/_includes/api/en/5x/app-METHOD.md
deleted file mode 100644
index c2a1c0586b..0000000000
--- a/_includes/api/en/5x/app-METHOD.md
+++ /dev/null
@@ -1,60 +0,0 @@
-<h3 id='app.METHOD'>app.METHOD(path, callback [, callback ...])</h3>
-
-Routes an HTTP request, where METHOD is the HTTP method of the request, such as GET,
-PUT, POST, and so on, in lowercase. Thus, the actual methods are `app.get()`,
-`app.post()`, `app.put()`, and so on. See [Routing methods](#routing-methods) below for the complete list.
-
-{% include api/en/5x/routing-args.html %}
-
-#### Routing methods
-
-Express supports the following routing methods corresponding to the HTTP methods of the same names:
-
-<div class="methods-columns">
-  <ul>
-    <li><code>checkout</code></li>
-    <li><code>copy</code></li>
-    <li><code>delete</code></li>
-    <li><code>get</code></li>
-    <li><code>head</code></li>
-    <li><code>lock</code></li>
-    <li><code>merge</code></li>
-    <li><code>mkactivity</code></li>
-  </ul>
-  <ul>
-    <li><code>mkcol</code></li>
-    <li><code>move</code></li>
-    <li><code>m-search</code></li>
-    <li><code>notify</code></li>
-    <li><code>options</code></li>
-    <li><code>patch</code></li>
-    <li><code>post</code></li>
-  </ul>
-  <ul>
-    <li><code>purge</code></li>
-    <li><code>put</code></li>
-    <li><code>report</code></li>
-    <li><code>search</code></li>
-    <li><code>subscribe</code></li>
-    <li><code>trace</code></li>
-    <li><code>unlock</code></li>
-    <li><code>unsubscribe</code></li>
-  </ul>
-</div>
-
-The API documentation has explicit entries only for the most popular HTTP methods `app.get()`,
-`app.post()`, `app.put()`, and `app.delete()`.
-However, the other methods listed above work in exactly the same way.
-
-To route methods that translate to invalid JavaScript variable names, use the bracket notation. For example, `app['m-search']('/', function ...`.
-
-<div class="doc-box doc-info" markdown="1">
-  The `app.get()` function is automatically called for the HTTP `HEAD` method in addition to the `GET`
-  method if `app.head()` was not called for the path before `app.get()`.
-</div>
-
-The method, `app.all()`, is not derived from any HTTP method and loads middleware at
-the specified path for _all_ HTTP request methods.
-For more information, see [app.all](#app.all).
-
-For more information on routing, see the [routing guide](/{{page.lang}}/guide/routing.html).
diff --git a/_includes/api/en/5x/app-all.md b/_includes/api/en/5x/app-all.md
deleted file mode 100644
index 5098300dc1..0000000000
--- a/_includes/api/en/5x/app-all.md
+++ /dev/null
@@ -1,44 +0,0 @@
-<h3 id='app.all'>app.all(path, callback [, callback ...])</h3>
-
-This method is like the standard [app.METHOD()](#app.METHOD) methods,
-except it matches all HTTP verbs.
-
-{% include api/en/5x/routing-args.html %}
-
-#### Examples
-
-The following callback is executed for requests to `/secret` whether using
-GET, POST, PUT, DELETE, or any other HTTP request method:
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-The `app.all()` method is useful for mapping "global" logic for specific path prefixes or arbitrary matches. For example, if you put the following at the top of all other
-route definitions, it requires that all routes from that point on
-require authentication, and automatically load a user. Keep in mind
-that these callbacks do not have to act as end-points: `loadUser`
-can perform a task, then call `next()` to continue matching subsequent
-routes.
-
-```js
-app.all('{*splat}', requireAuthentication, loadUser)
-```
-
-Or the equivalent:
-
-```js
-app.all('{*splat}', requireAuthentication)
-app.all('{*splat}', loadUser)
-```
-
-Another example is white-listed "global" functionality.
-The example is similar to the ones above, but it only restricts paths that start with
-"/api":
-
-```js
-app.all('/api/{*splat}', requireAuthentication)
-```
diff --git a/_includes/api/en/5x/app-delete-method.md b/_includes/api/en/5x/app-delete-method.md
deleted file mode 100644
index 3a08590fd0..0000000000
--- a/_includes/api/en/5x/app-delete-method.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='app.delete.method'>app.delete(path, callback [, callback ...])</h3>
-
-Routes HTTP DELETE requests to the specified path with the specified callback functions.
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-{% include api/en/5x/routing-args.html %}
-
-#### Example
-
-```js
-app.delete('/', (req, res) => {
-  res.send('DELETE request to homepage')
-})
-```
diff --git a/_includes/api/en/5x/app-disable.md b/_includes/api/en/5x/app-disable.md
deleted file mode 100644
index 08bbcf11ba..0000000000
--- a/_includes/api/en/5x/app-disable.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='app.disable'>app.disable(name)</h3>
-
-Sets the Boolean setting `name` to `false`, where `name` is one of the properties from the [app settings table](#app.settings.table).
-Calling `app.set('foo', false)` for a Boolean property is the same as calling `app.disable('foo')`.
-
-For example:
-
-```js
-app.disable('trust proxy')
-app.get('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/5x/app-disabled.md b/_includes/api/en/5x/app-disabled.md
deleted file mode 100644
index 370048fde6..0000000000
--- a/_includes/api/en/5x/app-disabled.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.disabled'>app.disabled(name)</h3>
-
-Returns `true` if the Boolean setting `name` is disabled (`false`), where `name` is one of the properties from
-the [app settings table](#app.settings.table).
-
-```js
-app.disabled('trust proxy')
-// => true
-
-app.enable('trust proxy')
-app.disabled('trust proxy')
-// => false
-```
diff --git a/_includes/api/en/5x/app-enable.md b/_includes/api/en/5x/app-enable.md
deleted file mode 100644
index 1152335a4c..0000000000
--- a/_includes/api/en/5x/app-enable.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='app.enable'>app.enable(name)</h3>
-
-Sets the Boolean setting `name` to `true`, where `name` is one of the properties from the [app settings table](#app.settings.table).
-Calling `app.set('foo', true)` for a Boolean property is the same as calling `app.enable('foo')`.
-
-```js
-app.enable('trust proxy')
-app.get('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/5x/app-enabled.md b/_includes/api/en/5x/app-enabled.md
deleted file mode 100644
index ad9b17aa89..0000000000
--- a/_includes/api/en/5x/app-enabled.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.enabled'>app.enabled(name)</h3>
-
-Returns `true` if the setting `name` is enabled (`true`), where `name` is one of the
-properties from the [app settings table](#app.settings.table).
-
-```js
-app.enabled('trust proxy')
-// => false
-
-app.enable('trust proxy')
-app.enabled('trust proxy')
-// => true
-```
diff --git a/_includes/api/en/5x/app-engine.md b/_includes/api/en/5x/app-engine.md
deleted file mode 100644
index 1314b0586e..0000000000
--- a/_includes/api/en/5x/app-engine.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='app.engine'>app.engine(ext, callback)</h3>
-
-Registers the given template engine `callback` as `ext`.
-
-By default, Express will `require()` the engine based on the file extension.
-For example, if you try to render a "foo.pug" file, Express invokes the
-following internally, and caches the `require()` on subsequent calls to increase
-performance.
-
-```js
-app.engine('pug', require('pug').__express)
-```
-
-Use this method for engines that do not provide `.__express` out of the box,
-or if you wish to "map" a different extension to the template engine.
-
-For example, to map the EJS template engine to ".html" files:
-
-```js
-app.engine('html', require('ejs').renderFile)
-```
-
-In this case, EJS provides a `.renderFile()` method with
-the same signature that Express expects: `(path, options, callback)`,
-though note that it aliases this method as `ejs.__express` internally
-so if you're using ".ejs" extensions you don't need to do anything.
-
-Some template engines do not follow this convention.  The
-[consolidate.js](https://github.com/tj/consolidate.js) library maps Node template engines to follow this convention,
-so they work seamlessly with Express.
-
-```js
-const engines = require('consolidate')
-app.engine('haml', engines.haml)
-app.engine('html', engines.hogan)
-```
diff --git a/_includes/api/en/5x/app-get-method.md b/_includes/api/en/5x/app-get-method.md
deleted file mode 100644
index 99b91354d6..0000000000
--- a/_includes/api/en/5x/app-get-method.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='app.get.method'>app.get(path, callback [, callback ...])</h3>
-
-Routes HTTP GET requests to the specified path with the specified callback functions.
-
-{% include api/en/5x/routing-args.html %}
-
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-#### Example
-
-```js
-app.get('/', (req, res) => {
-  res.send('GET request to homepage')
-})
-```
diff --git a/_includes/api/en/5x/app-get.md b/_includes/api/en/5x/app-get.md
deleted file mode 100644
index c93ef34d70..0000000000
--- a/_includes/api/en/5x/app-get.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.get'>app.get(name)</h3>
-
-Returns the value of `name` app setting, where `name` is one of the strings in the
-[app settings table](#app.settings.table). For example:
-
-```js
-app.get('title')
-// => undefined
-
-app.set('title', 'My Site')
-app.get('title')
-// => "My Site"
-```
diff --git a/_includes/api/en/5x/app-listen.md b/_includes/api/en/5x/app-listen.md
deleted file mode 100644
index 7135d69074..0000000000
--- a/_includes/api/en/5x/app-listen.md
+++ /dev/null
@@ -1,51 +0,0 @@
-<h3 id='app.listen_path_callback'>app.listen(path, [callback])</h3>
-
-Starts a UNIX socket and listens for connections on the given path.
-This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
-
-```js
-const express = require('express')
-const app = express()
-app.listen('/tmp/sock')
-```
-
-<h3 id='app.listen'>app.listen([port[, host[, backlog]]][, callback])</h3>
-
-Binds and listens for connections on the specified host and port.
-This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
-
-If port is omitted or is 0, the operating system will assign an arbitrary unused
-port, which is useful for cases like automated tasks (tests, etc.).
-
-```js
-const express = require('express')
-const app = express()
-app.listen(3000)
-```
-
-The `app` returned by `express()` is in fact a JavaScript
-`Function`, designed to be passed to Node's HTTP servers as a callback
-to handle requests. This makes it easy to provide both HTTP and HTTPS versions of
-your app with the same code base, as the app does not inherit from these
-(it is simply a callback):
-
-```js
-const express = require('express')
-const https = require('https')
-const http = require('http')
-const app = express()
-
-http.createServer(app).listen(80)
-https.createServer(options, app).listen(443)
-```
-
-The `app.listen()` method returns an [http.Server](https://nodejs.org/api/http.html#http_class_http_server) object and (for HTTP) is a convenience method for the following:
-
-```js
-app.listen = function () {
-  const server = http.createServer(this)
-  return server.listen.apply(server, arguments)
-}
-```
-
-{% include admonitions/note.html content="All the forms of Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen) method are in fact actually supported." %}
diff --git a/_includes/api/en/5x/app-locals.md b/_includes/api/en/5x/app-locals.md
deleted file mode 100644
index 178d640054..0000000000
--- a/_includes/api/en/5x/app-locals.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<h3 id='app.locals'>app.locals</h3>
-
-The `app.locals` object has properties that are local variables within the application,
-and will be available in templates rendered with [res.render](#res.render).
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-```js
-console.dir(app.locals.title)
-// => 'My App'
-
-console.dir(app.locals.email)
-// => 'me@myapp.com'
-```
-
-Once set, the value of `app.locals` properties persist throughout the life of the application,
-in contrast with [res.locals](#res.locals) properties that
-are valid only for the lifetime of the request.
-
-You can access local variables in templates rendered within the application.
-This is useful for providing helper functions to templates, as well as application-level data.
-Local variables are available in middleware via `req.app.locals` (see [req.app](#req.app))
-
-```js
-app.locals.title = 'My App'
-app.locals.strftime = require('strftime')
-app.locals.email = 'me@myapp.com'
-```
diff --git a/_includes/api/en/5x/app-mountpath.md b/_includes/api/en/5x/app-mountpath.md
deleted file mode 100644
index c18e0f8eb7..0000000000
--- a/_includes/api/en/5x/app-mountpath.md
+++ /dev/null
@@ -1,45 +0,0 @@
-<h3 id='app.mountpath'>app.mountpath</h3>
-
-The `app.mountpath` property contains one or more path patterns on which a sub-app was mounted.
-
-<div class="doc-box doc-info" markdown="1">
-  A sub-app is an instance of `express` that may be used for handling the request to a route.
-</div>
-
-```js
-const express = require('express')
-
-const app = express() // the main app
-const admin = express() // the sub app
-
-admin.get('/', (req, res) => {
-  console.log(admin.mountpath) // /admin
-  res.send('Admin Homepage')
-})
-
-app.use('/admin', admin) // mount the sub app
-```
-
-It is similar to the [baseUrl](#req.baseUrl) property of the `req` object, except `req.baseUrl`
-returns the matched URL path, instead of the matched patterns.
-
-If a sub-app is mounted on multiple path patterns, `app.mountpath` returns the list of
-patterns it is mounted on, as shown in the following example.
-
-```js
-const admin = express()
-
-admin.get('/', (req, res) => {
-  console.log(admin.mountpath) // [ '/adm{*splat}n', '/manager' ]
-  res.send('Admin Homepage')
-})
-
-const secret = express()
-secret.get('/', (req, res) => {
-  console.log(secret.mountpath) // /secr{*splat}t
-  res.send('Admin Secret')
-})
-
-admin.use('/secr{*splat}t', secret) // load the 'secret' router on '/secr{*splat}t', on the 'admin' sub app
-app.use(['/adm{*splat}n', '/manager'], admin) // load the 'admin' router on '/adm{*splat}n' and '/manager', on the parent app
-```
diff --git a/_includes/api/en/5x/app-onmount.md b/_includes/api/en/5x/app-onmount.md
deleted file mode 100644
index 80e38520eb..0000000000
--- a/_includes/api/en/5x/app-onmount.md
+++ /dev/null
@@ -1,29 +0,0 @@
-<h3 id='app.onmount'>app.on('mount', callback(parent))</h3>
-
-The `mount` event is fired on a sub-app, when it is mounted on a parent app. The parent app is passed to the callback function.
-
-<div class="doc-box doc-info" markdown="1">
-**NOTE**
-
-Sub-apps will:
-
-* Not inherit the value of settings that have a default value. You must set the value in the sub-app.
-* Inherit the value of settings with no default value.
-
-For details, see [Application settings](/en/5x/api.html#app.settings.table).
-</div>
-
-```js
-const admin = express()
-
-admin.on('mount', (parent) => {
-  console.log('Admin Mounted')
-  console.log(parent) // refers to the parent app
-})
-
-admin.get('/', (req, res) => {
-  res.send('Admin Homepage')
-})
-
-app.use('/admin', admin)
-```
diff --git a/_includes/api/en/5x/app-param.md b/_includes/api/en/5x/app-param.md
deleted file mode 100644
index a1e064add2..0000000000
--- a/_includes/api/en/5x/app-param.md
+++ /dev/null
@@ -1,78 +0,0 @@
-<h3 id='app.param'>app.param(name, callback)</h3>
-
-Add callback triggers to [route parameters](/{{ page.lang }}/guide/routing.html#route-parameters), where `name` is the name of the parameter or an array of them, and `callback` is the callback function. The parameters of the callback function are the request object, the response object, the next middleware, the value of the parameter and the name of the parameter, in that order.
-
-If `name` is an array, the `callback` trigger is registered for each parameter declared in it, in the order in which they are declared. Furthermore, for each declared parameter except the last one, a call to `next` inside the callback will call the callback for the next declared parameter. For the last parameter, a call to `next` will call the next middleware in place for the route currently being processed, just like it would if `name` were just a string.
-
-For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
-
-```js
-app.param('user', (req, res, next, id) => {
-  // try to get the user details from the User model and attach it to the request object
-  User.find(id, (err, user) => {
-    if (err) {
-      next(err)
-    } else if (user) {
-      req.user = user
-      next()
-    } else {
-      next(new Error('failed to load user'))
-    }
-  })
-})
-```
-
-Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `app` will be triggered only by route parameters defined on `app` routes.
-
-All param callbacks will be called before any handler of any route in which the param occurs, and they will each be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
-
-```js
-app.param('id', (req, res, next, id) => {
-  console.log('CALLED ONLY ONCE')
-  next()
-})
-
-app.get('/user/:id', (req, res, next) => {
-  console.log('although this matches')
-  next()
-})
-
-app.get('/user/:id', (req, res) => {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42`, the following is printed:
-
-```
-CALLED ONLY ONCE
-although this matches
-and this matches too
-```
-
-```js
-app.param(['id', 'page'], (req, res, next, value) => {
-  console.log('CALLED ONLY ONCE with', value)
-  next()
-})
-
-app.get('/user/:id/:page', (req, res, next) => {
-  console.log('although this matches')
-  next()
-})
-
-app.get('/user/:id/:page', (req, res) => {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42/3`, the following is printed:
-
-```
-CALLED ONLY ONCE with 42
-CALLED ONLY ONCE with 3
-although this matches
-and this matches too
-```
diff --git a/_includes/api/en/5x/app-path.md b/_includes/api/en/5x/app-path.md
deleted file mode 100644
index e1fabc0c10..0000000000
--- a/_includes/api/en/5x/app-path.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='app.path'>app.path()</h3>
-
-Returns the canonical path of the app, a string.
-
-```js
-const app = express()
-const blog = express()
-const blogAdmin = express()
-
-app.use('/blog', blog)
-blog.use('/admin', blogAdmin)
-
-console.log(app.path()) // ''
-console.log(blog.path()) // '/blog'
-console.log(blogAdmin.path()) // '/blog/admin'
-```
-
-The behavior of this method can become very complicated in complex cases of mounted apps:
-it is usually better to use [req.baseUrl](#req.baseUrl) to get the canonical path of the app.
diff --git a/_includes/api/en/5x/app-post-method.md b/_includes/api/en/5x/app-post-method.md
deleted file mode 100644
index 9bde32e02a..0000000000
--- a/_includes/api/en/5x/app-post-method.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='app.post.method'>app.post(path, callback [, callback ...])</h3>
-
-Routes HTTP POST requests to the specified path with the specified callback functions.
-For more information, see the [routing guide](/{{page.lang}}/guide/routing.html).
-
-{% include api/en/5x/routing-args.html %}
-
-#### Example
-
-```js
-app.post('/', (req, res) => {
-  res.send('POST request to homepage')
-})
-```
diff --git a/_includes/api/en/5x/app-put-method.md b/_includes/api/en/5x/app-put-method.md
deleted file mode 100644
index 0575714854..0000000000
--- a/_includes/api/en/5x/app-put-method.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='app.put.method'>app.put(path, callback [, callback ...])</h3>
-
-Routes HTTP PUT requests to the specified path with the specified callback functions.
-
-{% include api/en/5x/routing-args.html %}
-
-#### Example
-
-```js
-app.put('/', (req, res) => {
-  res.send('PUT request to homepage')
-})
-```
diff --git a/_includes/api/en/5x/app-render.md b/_includes/api/en/5x/app-render.md
deleted file mode 100644
index c526f099ad..0000000000
--- a/_includes/api/en/5x/app-render.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='app.render'>app.render(view, [locals], callback)</h3>
-
-Returns the rendered HTML of a view via the `callback` function. It accepts an optional parameter
-that is an object containing local variables for the view. It is like [res.render()](#res.render),
-except it cannot send the rendered view to the client on its own.
-
-<div class="doc-box doc-info" markdown="1">
-Think of `app.render()` as a utility function for generating rendered view strings.
-Internally `res.render()` uses `app.render()` to render views.
-</div>
-
-<div class="doc-box doc-warn" markdown="1">
-The `view` argument performs file system operations like reading a file from
-disk and evaluating Node.js modules, and as so for security reasons should not
-contain input from the end-user.
-</div>
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-The local variable `cache` is reserved for enabling view cache. Set it to `true`, if you want to
-cache view during development; view caching is enabled in production by default.
-</div>
-
-```js
-app.render('email', (err, html) => {
-  // ...
-})
-
-app.render('email', { name: 'Tobi' }, (err, html) => {
-  // ...
-})
-```
diff --git a/_includes/api/en/5x/app-route.md b/_includes/api/en/5x/app-route.md
deleted file mode 100644
index 2a0db757dd..0000000000
--- a/_includes/api/en/5x/app-route.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='app.route'>app.route(path)</h3>
-
-Returns an instance of a single route, which you can then use to handle HTTP verbs with optional middleware.
-Use `app.route()` to avoid duplicate route names (and thus typo errors).
-
-```js
-const app = express()
-
-app.route('/events')
-  .all((req, res, next) => {
-    // runs for all HTTP verbs first
-    // think of it as route specific middleware!
-  })
-  .get((req, res, next) => {
-    res.json({})
-  })
-  .post((req, res, next) => {
-    // maybe add a new event...
-  })
-```
diff --git a/_includes/api/en/5x/app-router.md b/_includes/api/en/5x/app-router.md
deleted file mode 100644
index b821faa75d..0000000000
--- a/_includes/api/en/5x/app-router.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='app.router'>app.router</h3>
-
-The application's in-built instance of router. This is created lazily, on first access.
-
-```js
-const express = require('express')
-const app = express()
-const router = app.router
-
-router.get('/', (req, res) => {
-  res.send('hello world')
-})
-
-app.listen(3000)
-```
-
-You can add middleware and HTTP method routes to the `router` just like an application.
-
-For more information, see [Router](#router).
diff --git a/_includes/api/en/5x/app-set.md b/_includes/api/en/5x/app-set.md
deleted file mode 100644
index e85bd9be19..0000000000
--- a/_includes/api/en/5x/app-set.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='app.set'>app.set(name, value)</h3>
-
-Assigns setting `name` to `value`. You may store any value that you want,
-but certain names can be used to configure the behavior of the server. These
-special names are listed in the [app settings table](#app.settings.table).
-
-Calling `app.set('foo', true)` for a Boolean property is the same as calling
-`app.enable('foo')`. Similarly, calling `app.set('foo', false)` for a Boolean
-property is the same as calling `app.disable('foo')`.
-
-Retrieve the value of a setting with [`app.get()`](#app.get).
-
-```js
-app.set('title', 'My Site')
-app.get('title') // "My Site"
-```
-
-<h4 id='app.settings.table'>Application Settings</h4>
-
-{% include api/en/5x/app-settings.md %}
diff --git a/_includes/api/en/5x/app-settings.md b/_includes/api/en/5x/app-settings.md
deleted file mode 100644
index 3b8b8369db..0000000000
--- a/_includes/api/en/5x/app-settings.md
+++ /dev/null
@@ -1,323 +0,0 @@
-The following table lists application settings.
-
-Note that sub-apps will:
-
-* Not inherit the value of settings that have a default value. You must set the value in the sub-app.
-* Inherit the value of settings with no default value; these are explicitly noted in the table below.
-
-Exceptions: Sub-apps will inherit the value of `trust proxy` even though it has a default value (for backward-compatibility);
-Sub-apps will not inherit the value of `view cache` in production (when `NODE_ENV` is "production").
-
-<div class="table-scroller">
-  <table>
-    <thead><tr><th id="app-settings-property">Property</th><th>Type</th><th>Description</th><th>Default</th></tr></thead>
-    <tbody>
-    <tr>
-  <td markdown="1">
-  `case sensitive routing`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enable case sensitivity.
-      When enabled, "/Foo" and "/foo" are different routes.
-      When disabled, "/Foo" and "/foo" are treated the same.</p>
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)
-      </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `env`
-  </td>
-      <td>String</td>
-      <td>Environment mode.
-      Be sure to set to "production" in a production environment;
-      see <a href="/advanced/best-practice-performance.html#env">Production best practices: performance and reliability</a>.
-    </td>
-  <td markdown="1">
-  `process.env.NODE_ENV` (`NODE_ENV` environment variable) or "development" if `NODE_ENV` is not set.
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `etag`
-  </td>
-  <td>Varied</td>
-  <td markdown="1">
-  Set the ETag response header. For possible values, see the [`etag` options table](#etag.options.table).
-
-  [More about the HTTP ETag header](http://en.wikipedia.org/wiki/HTTP_ETag).
-  </td>
-  <td markdown="1">
-  `weak`
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `jsonp callback name`
-  </td>
-      <td>String</td>
-      <td>Specifies the default JSONP callback name.</td>
-  <td markdown="1">
-  "callback"
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json escape`
-  </td>
-  <td>Boolean</td>
-  <td markdown="1">
-  Enable escaping JSON responses from the `res.json`, `res.jsonp`, and `res.send` APIs. This will escape the characters `<`, `>`, and `&` as Unicode escape sequences in JSON. The purpose of this is to assist with [mitigating certain types of persistent XSS attacks](https://blog.mozilla.org/security/2017/07/18/web-service-audits-firefox-accounts/) when clients sniff responses for HTML.
-  <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-  </td>
-  <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json replacer`
-  </td>
-      <td>Varied</td>
-      <td>The <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_replacer_parameter">'replacer' argument used by `JSON.stringify`</a>.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-  <td>N/A (undefined)
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `json spaces`
-  </td>
-      <td>Varied</td>
-      <td>The <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_space_argument">'space' argument used by `JSON.stringify`</a>.
-This is typically set to the number of spaces to use to indent prettified JSON.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `query parser`
-  </td>
-      <td>Varied</td>
-  <td markdown="1">
-Disable query parsing by setting the value to `false`, or set the query parser to use either "simple" or "extended" or a custom query string parsing function.
-
-The simple query parser is based on Node's native query parser, [querystring](http://nodejs.org/api/querystring.html).
-
-The extended query parser is based on [qs](https://www.npmjs.org/package/qs).
-
-A custom query string parsing function will receive the complete query string, and must return an object of query keys and their values.
-  </td>
-      <td>"simple"</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `strict routing`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enable strict routing.
-      When enabled, the router treats "/foo" and "/foo/" as different.
-      Otherwise, the router treats "/foo" and "/foo/" as the same.</p>
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined) </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `subdomain offset`
-  </td>
-      <td>Number</td>
-      <td>The number of dot-separated parts of the host to remove to access subdomain.</td>
-      <td>2</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `trust proxy`
-  </td>
-      <td>Varied</td>
-  <td markdown="1">
-  Indicates the app is behind a front-facing proxy, and to use the `X-Forwarded-*` headers to determine the connection and the IP address of the client. NOTE: `X-Forwarded-*` headers are easily spoofed and the detected IP addresses are unreliable.
-<p>
-  When enabled, Express attempts to determine the IP address of the client connected through the front-facing proxy, or series of proxies. The `req.ips` property, then contains an array of IP addresses the client is connected through. To enable it, use the values described in the <a href="#trust.proxy.options.table">trust proxy options table</a>.
-</p><p>
-  The `trust proxy` setting is implemented using the <a href="https://www.npmjs.org/package/proxy-addr">proxy-addr</a> package. For more information, see its documentation.
-</p><p>
-<b>NOTE</b>: Sub-apps <i>will</i> inherit the value of this setting, even though it has a default value.
-</p>
-  </td>
-  <td markdown="1">
-  `false` (disabled)
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `views`
-  </td>
-      <td>String or Array</td>
-      <td>A directory or an array of directories for the application's views. If an array, the views are looked up in the order they occur in the array.</td>
-  <td markdown="1">
-  `process.cwd() + '/views'`
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `view cache`
-  </td>
-      <td>Boolean</td>
-      <td><p>Enables view template compilation caching.</p>
-      <p><b>NOTE</b>: Sub-apps will not inherit the value of this setting in production (when `NODE_ENV` is "production").</p>
-      </td>
-  <td markdown="1">
-  `true` in production, otherwise undefined.
-  </td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `view engine`
-  </td>
-      <td>String</td>
-      <td>The default engine extension to use when omitted.
-        <p><b>NOTE</b>: Sub-apps will inherit the value of this setting.</p>
-      </td>
-      <td>N/A (undefined)</td>
-    </tr>
-    <tr>
-  <td markdown="1">
-  `x-powered-by`
-  </td>
-      <td>Boolean</td>
-      <td>Enables the "X-Powered-By: Express" HTTP header.</td>
-  <td markdown="1">
-  `true`
-  </td>
-    </tr>
-    </tbody>
-  </table>
-  </div>
-
-  <h5 id="trust.proxy.options.table">Options for `trust proxy` setting</h5>
-
-  <p markdown="1">
-  Read [Express behind proxies](/{{page.lang}}/guide/behind-proxies.html) for more
-  information.
-  </p>
-
-<div class="table-scroller">
-  <table>
-    <thead><tr><th>Type</th><th>Value</th></tr></thead>
-    <tbody>
-      <tr>
-        <td>Boolean</td>
-  <td markdown="1">
-  If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-*` header.
-
-  If `false`, the app is understood as directly facing the Internet and the client's IP address is derived from `req.connection.remoteAddress`. This is the default setting.
-  </td>
-      </tr>
-      <tr>
-        <td>String<br/>String containing comma-separated values<br/>Array of strings </td>
-  <td markdown="1">
-  An IP address, subnet, or an array of IP addresses, and subnets to trust. Pre-configured subnet names are:
-
-  * loopback - `127.0.0.1/8`, `::1/128`
-  * linklocal - `169.254.0.0/16`, `fe80::/10`
-  * uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-  Set IP addresses in any of the following ways:
-
-Specify a single subnet:
-
-```js
-app.set('trust proxy', 'loopback')
-```
-
-Specify a subnet and an address:
-
-```js
-app.set('trust proxy', 'loopback, 123.123.123.123')
-```
-
-Specify multiple subnets as CSV:
-
-```js
-app.set('trust proxy', 'loopback, linklocal, uniquelocal')
-```
-
-Specify multiple subnets as an array:
-
-```js
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal'])
-```
-
-  When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address.
-  </td>
-      </tr>
-      <tr>
-        <td>Number</td>
-  <td markdown="1">
-  Trust the <i>n</i><sup>th</sup> hop from the front-facing proxy server as the client.
-  </td>
-      </tr>
-      <tr>
-        <td>Function</td>
-  <td markdown="1">
-  Custom trust implementation. Use this only if you know what you are doing.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-  </td>
-      </tr>
-    </tbody>
-  </table>
-</div>
-
-  <h5 id="etag.options.table">Options for `etag` setting</h5>
-
-<p markdown="1">
-**NOTE**:  These settings apply only to dynamic files, not static files.
-The [express.static](#express.static) middleware ignores these settings.
-</p>
-
-  <p markdown="1">
-  The ETag functionality is implemented using the
-  [etag](https://www.npmjs.org/package/etag) package.
-  For more information, see its documentation.
-  </p>
-
-<div class="table-scroller">
-  <table>
-    <thead><tr><th>Type</th><th>Value</th></tr></thead>
-    <tbody>
-      <tr>
-        <td>Boolean</td>
-  <td markdown="1">
-  `true` enables weak ETag. This is the default setting.<br>
-  `false` disables ETag altogether.
-  </td>
-      </tr>
-      <tr>
-        <td>String</td>
-        <td>
-            If "strong", enables strong ETag.<br>
-            If "weak", enables weak ETag.
-        </td>
-      </tr>
-      <tr>
-        <td>Function</td>
-  <td markdown="1">Custom ETag function implementation. Use this only if you know what you are doing.
-
-```js
-app.set('etag', (body, encoding) => {
-  return generateHash(body, encoding) // consider the function is defined
-})
-```
-  </td>
-      </tr>
-    </tbody>
-  </table>
-</div>
diff --git a/_includes/api/en/5x/app-use.md b/_includes/api/en/5x/app-use.md
deleted file mode 100644
index 8b5a2b13cc..0000000000
--- a/_includes/api/en/5x/app-use.md
+++ /dev/null
@@ -1,295 +0,0 @@
-<h3 id='app.use'>app.use([path,] callback [, callback...])</h3>
-
-Mounts the specified [middleware](/{{page.lang}}/guide/using-middleware.html) function or functions
-at the specified path:
-the middleware function is executed when the base of the requested path matches `path`.
-
-{% include api/en/5x/routing-args.html %}
-
-#### Description
-
-A route will match any path that follows its path immediately with a "`/`".
-For example: `app.use('/apple', ...)` will match "/apple", "/apple/images",
-"/apple/images/news", and so on.
-
-Since `path` defaults to "/", middleware mounted without a path will be executed for every request to the app.
-For example, this middleware function will be executed for _every_ request to the app:
-
-```js
-app.use((req, res, next) => {
-  console.log('Time: %d', Date.now())
-  next()
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-**NOTE**
-
-Sub-apps will:
-
-* Not inherit the value of settings that have a default value. You must set the value in the sub-app.
-* Inherit the value of settings with no default value.
-
-For details, see [Application settings](/en/5x/api.html#app.settings.table).
-</div>
-
-Middleware functions are executed sequentially, therefore the order of middleware inclusion is important.
-
-```js
-// this middleware will not allow the request to go beyond it
-app.use((req, res, next) => {
-  res.send('Hello World')
-})
-
-// requests will never reach this route
-app.get('/', (req, res) => {
-  res.send('Welcome')
-})
-```
-
-**Error-handling middleware**
-
-Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors. For details about error-handling middleware, see: [Error handling](/{{ page.lang }}/guide/error-handling.html).
-
-Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`):
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-#### Path examples
-
-The following table provides some simple examples of valid `path` values for
-mounting middleware.
-
-<div class="table-scroller">
-<table>
-
-<thead>
-<tr>
-<th>Type</th>
-<th>Example</th>
-</tr>
-</thead>
-
-<tbody>
-
-<tr>
-<td>Path</td>
-<td markdown="1">
-Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
-
-
-```js
-app.use('/abcd', (req, res, next) => {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Path Pattern</td>
-<td markdown="1">
-This will match paths starting with `/abcd` and `/abd`:
-
-```js
-app.use('/ab{c}d', (req, res, next) => {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Regular Expression</td>
-<td markdown="1">
-This will match paths starting with `/abc` and `/xyz`:
-
-```js
-app.use(/\/abc|\/xyz/, (req, res, next) => {
-  next()
-})
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Array</td>
-<td markdown="1">
-This will match paths starting with `/abcd`, `/xyza`, `/lmn`, and `/pqr`:
-
-```js
-app.use(['/abcd', '/xyza', /\/lmn|\/pqr/], (req, res, next) => {
-  next()
-})
-```
-
-</td>
-</tr>
-
-</tbody>
-
-</table>
-</div>
-
-#### Middleware callback function examples
-
-The following table provides some simple examples of middleware functions that
-can be used as the `callback` argument to `app.use()`, `app.METHOD()`, and `app.all()`.
-
-<div class="table-scroller">
-<table>
-
-<thead>
-<tr>
-<th>Usage</th>
-<th>Example</th>
-</tr>
-</thead>
-<tbody>
-
-<tr>
-<td>Single Middleware</td>
-<td markdown="1">
-You can define and mount a middleware function locally.
-
-```js
-app.use((req, res, next) => {
-  next()
-})
-```
-
-A router is valid middleware.
-
-```js
-const router = express.Router()
-router.get('/', (req, res, next) => {
-  next()
-})
-app.use(router)
-```
-
-An Express app is valid middleware.
-
-```js
-const subApp = express()
-subApp.get('/', (req, res, next) => {
-  next()
-})
-app.use(subApp)
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Series of Middleware</td>
-<td markdown="1">
-You can specify more than one middleware function at the same mount path.
-
-```js
-const r1 = express.Router()
-r1.get('/', (req, res, next) => {
-  next()
-})
-
-const r2 = express.Router()
-r2.get('/', (req, res, next) => {
-  next()
-})
-
-app.use(r1, r2)
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Array</td>
-<td markdown="1">
-Use an array to group middleware logically.
-
-```js
-const r1 = express.Router()
-r1.get('/', (req, res, next) => {
-  next()
-})
-
-const r2 = express.Router()
-r2.get('/', (req, res, next) => {
-  next()
-})
-
-app.use([r1, r2])
-```
-
-</td>
-</tr>
-
-<tr>
-<td>Combination</td>
-<td markdown="1">
-You can combine all the above ways of mounting middleware.
-
-```js
-function mw1 (req, res, next) { next() }
-function mw2 (req, res, next) { next() }
-
-const r1 = express.Router()
-r1.get('/', (req, res, next) => { next() })
-
-const r2 = express.Router()
-r2.get('/', (req, res, next) => { next() })
-
-const subApp = express()
-subApp.get('/', (req, res, next) => { next() })
-
-app.use(mw1, [mw2, r1, r2], subApp)
-```
-
-</td>
-</tr>
-
-</tbody>
-
-</table>
-</div>
-
-Following are some examples of using the [express.static](/{{page.lang}}/guide/using-middleware.html#middleware.built-in)
-middleware in an Express app.
-
-Serve static content for the app from the "public" directory in the application directory:
-
-```js
-// GET /style.css etc
-app.use(express.static(path.join(__dirname, 'public')))
-```
-
-Mount the middleware at "/static" to serve static content only when their request path is prefixed with "/static":
-
-```js
-// GET /static/style.css etc.
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-Disable logging for static content requests by loading the logger middleware after the static middleware:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(logger())
-```
-
-Serve static files from multiple directories, but give precedence to "./public" over the others:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(express.static(path.join(__dirname, 'files')))
-app.use(express.static(path.join(__dirname, 'uploads')))
-```
diff --git a/_includes/api/en/5x/app.md b/_includes/api/en/5x/app.md
deleted file mode 100644
index 458ba8a447..0000000000
--- a/_includes/api/en/5x/app.md
+++ /dev/null
@@ -1,127 +0,0 @@
-<h2 id="app">Application</h2>
-
-The `app` object conventionally denotes the Express application.
-Create it by calling the top-level `express()` function exported by the Express module:
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-
-app.listen(3000)
-```
-
-The `app` object has methods for
-
-* Routing HTTP requests; see for example, [app.METHOD](#app.METHOD) and [app.param](#app.param).
-* Configuring middleware; see [app.route](#app.route).
-* Rendering HTML views; see [app.render](#app.render).
-* Registering a template engine; see [app.engine](#app.engine).
-
-It also has settings (properties) that affect how the application behaves;
-for more information, see [Application settings](#app.settings.table).
-
-<div class="doc-box doc-info" markdown="1">
-The Express application object can be referred from the [request object](#req) and the [response object](#res) as `req.app`, and `res.app`, respectively.
-</div>
-
-<h3 id='app.properties'>Properties</h3>
-
-<section markdown="1">
-  {% include api/en/5x/app-locals.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-mountpath.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-router.md %}
-</section>
-
-<h3 id='app.events'>Events</h3>
-
-<section markdown="1">
-  {% include api/en/5x/app-onmount.md %}
-</section>
-
-<h3 id='app.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/5x/app-all.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-delete-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-disable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-disabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-enable.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-enabled.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-engine.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-get-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-listen.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-METHOD.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-path.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-post-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-put-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-render.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/app-use.md %}
-</section>
diff --git a/_includes/api/en/5x/express.json.md b/_includes/api/en/5x/express.json.md
deleted file mode 100644
index bc12042d8d..0000000000
--- a/_includes/api/en/5x/express.json.md
+++ /dev/null
@@ -1,38 +0,0 @@
-<h3 id='express.json' class='h2'>express.json([options])</h3>
-
-This is a built-in middleware function in Express. It parses incoming requests
-with JSON payloads and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that only parses JSON and only looks at requests where
-the `Content-Type` header matches the `type` option. This parser accepts any
-Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or `undefined` if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.foo.toString()` may fail in multiple ways, for example
-`foo` may not be there or may not be a string, and `toString` may not be a
-function and instead a string or other user-input.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property      | Description                                                           |   Type      | Default         |
-|---------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `inflate`     | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`       | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `reviver`     | The `reviver` option is passed directly to `JSON.parse` as the second argument. You can find more information on this argument [in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter). | Function | `null` |
-| `strict`      | Enables or disables only accepting arrays and objects; when disabled will accept anything `JSON.parse` accepts. | Boolean | `true` |
-| `type`        | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `json`), a mime type (like `application/json`), or a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/json"` |
-| `verify`      | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/5x/express.md b/_includes/api/en/5x/express.md
deleted file mode 100644
index acfae62a5a..0000000000
--- a/_includes/api/en/5x/express.md
+++ /dev/null
@@ -1,34 +0,0 @@
-<h2 id="express">express()</h2>
-
-Creates an Express application. The `express()` function is a top-level function exported by the `express` module.
-
-```js
-const express = require('express')
-const app = express()
-```
-
-<h3 id='express.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/5x/express.json.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/express.raw.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/express.router.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/express.static.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/express.text.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/express.urlencoded.md %}
-</section>
diff --git a/_includes/api/en/5x/express.raw.md b/_includes/api/en/5x/express.raw.md
deleted file mode 100644
index b20ff13ed6..0000000000
--- a/_includes/api/en/5x/express.raw.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='express.raw' class='h2'>express.raw([options])</h3>
-
-This is a built-in middleware function in Express. It parses incoming request
-payloads into a `Buffer` and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that parses all bodies as a `Buffer` and only looks at requests
-where the `Content-Type` header matches the `type` option. This parser accepts
-any Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` `Buffer` containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or `undefined` if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.toString()` may fail in multiple ways, for example
-stacking multiple parsers `req.body` may be from a different parser. Testing
-that `req.body` is a `Buffer` before calling buffer methods is recommended.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property  | Description                                                           |   Type      | Default         |
-|-----------|-----------------------------------------------------------------------|-------------|-----------------|
-| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `bin`), a mime type (like `application/octet-stream`), or a mime type with a wildcard (like `*/*` or `application/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/octet-stream"` |
-| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/5x/express.router.md b/_includes/api/en/5x/express.router.md
deleted file mode 100644
index babd0b0279..0000000000
--- a/_includes/api/en/5x/express.router.md
+++ /dev/null
@@ -1,24 +0,0 @@
-<h3 id='express.router' class='h2'>express.Router([options])</h3>
-
-Creates a new [router](#router) object.
-
-```js
-const router = express.Router([options])
-```
-
-The optional `options` parameter specifies the behavior of the router.
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability  |
-|-----------------|-------------------------------------------------|-------------|---------------|
-| `caseSensitive` | Enable case sensitivity. | Disabled by default, treating "/Foo" and "/foo" as the same.|  |
-| `mergeParams`   | Preserve the `req.params` values from the parent router. If the parent and the child have conflicting param names, the child's value take precedence.| `false` | 4.5.0+ |
-| `strict`        | Enable strict routing. | Disabled by default, "/foo" and "/foo/" are treated the same by the router.| &nbsp; |
-
-</div>
-
-You can add middleware and HTTP method routes (such as `get`, `put`, `post`, and
-so on) to `router` just like an application.
-
-For more information, see [Router](#router).
diff --git a/_includes/api/en/5x/express.static.md b/_includes/api/en/5x/express.static.md
deleted file mode 100644
index 72094c40f9..0000000000
--- a/_includes/api/en/5x/express.static.md
+++ /dev/null
@@ -1,94 +0,0 @@
-<h3 id='express.static' class='h2'>express.static(root, [options])</h3>
-
-This is a built-in middleware function in Express.
-It serves static files and is based on  [serve-static](/resources/middleware/serve-static.html).
-
-<div class="doc-box doc-info" markdown="1">NOTE: For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-</div>
-
-The `root` argument specifies the root directory from which to serve static assets.
-The function determines the file to serve by combining `req.url` with the provided `root` directory.
-When a file is not found, instead of sending a 404 response, it instead calls `next()`
-to move on to the next middleware, allowing for stacking and fall-backs.
-
-The following table describes the properties of the `options` object.
-See also the [example below](#example.of.express.static).
-
-<div class="table-scroller" markdown="1">
-
-| Property      | Description                                                           |   Type      | Default         |
-|---------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `dotfiles`    | Determines how dotfiles (files or directories that begin with a dot ".") are treated.  <br/><br/>See [dotfiles](#dotfiles) below. | String | "ignore"|
-| `etag`        | Enable or disable etag generation <br/><br/>NOTE: `express.static` always sends weak ETags. | Boolean | `true` |
-| `extensions`  | Sets file extension fallbacks: If a file is not found, search for files with the specified extensions and serve the first one found. Example: `['html', 'htm']`.| Mixed | `false` |
-| `fallthrough`  | Let client errors fall-through as unhandled requests, otherwise forward a client error. <br/><br/>See [fallthrough](#fallthrough) below.| Boolean | `true` |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | Boolean | `false` |
-| `index`       | Sends the specified directory index file. Set to `false` to disable directory indexing. | Mixed | "index.html" |
-| `lastModified` | Set the `Last-Modified` header to the last modified date of the file on the OS. | Boolean | `true` |
-| `maxAge`      | Set the max-age property of the Cache-Control header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms). | Number | 0 |
-| `redirect`    | Redirect to trailing "/" when the pathname is a directory. | Boolean | `true` |
-| `setHeaders`  | Function for setting HTTP headers to serve with the file. <br/><br/>See [setHeaders](#setHeaders) below. | Function |  |
-| `acceptRanges`    | Enable or disable accepting ranged requests. Disabling this will not send the Accept-Ranges header and will ignore the contents of the Range request header.| Boolean | true |
-| `cacheControl`    | Enable or disable setting the Cache-Control response header. Disabling this will ignore the immutable and maxAge options. | Boolean | true |
-
-</div>
-
-For more information, see [Serving static files in Express](/starter/static-files.html).
-and [Using middleware - Built-in middleware](/{{page.lang}}/guide/using-middleware.html#middleware.built-in).
-
-<h5 id='dotfiles'> dotfiles</h5>
-
-Possible values for this option are:
-
-- "allow" - No special treatment for dotfiles.
-- "deny" - Deny a request for a dotfile, respond with `403`, then call `next()`.
-- "ignore" - Act as if the dotfile does not exist, respond with `404`, then call `next()`.
-
-<h5 id='fallthrough'>fallthrough</h5>
-
-When this option is `true`, client errors such as a bad request or a request to a non-existent
-file will cause this middleware to simply call `next()` to invoke the next middleware in the stack.
-When false, these errors (even 404s), will invoke `next(err)`.
-
-Set this option to `true` so you can map multiple physical directories
-to the same web address or for routes to fill in non-existent files.
-
-Use `false` if you have mounted this middleware at a path designed
-to be strictly a single file system directory, which allows for short-circuiting 404s
-for less overhead. This middleware will also reply to all methods.
-
-<h5 id='setHeaders'>setHeaders</h5>
-
-For this option, specify a function to set custom response headers. Alterations to the headers must occur synchronously.
-
-The signature of the function is:
-
-```js
-fn(res, path, stat)
-```
-
-Arguments:
-
-- `res`, the [response object](#res).
-- `path`, the file path that is being sent.
-- `stat`, the `stat` object of the file that is being sent.
-
-<h4 id='example.of.express.static'>Example of express.static</h4>
-
-Here is an example of using the `express.static` middleware function with an elaborate options object:
-
-```js
-const options = {
-  dotfiles: 'ignore',
-  etag: false,
-  extensions: ['htm', 'html'],
-  index: false,
-  maxAge: '1d',
-  redirect: false,
-  setHeaders (res, path, stat) {
-    res.set('x-timestamp', Date.now())
-  }
-}
-
-app.use(express.static('public', options))
-```
diff --git a/_includes/api/en/5x/express.text.md b/_includes/api/en/5x/express.text.md
deleted file mode 100644
index 18223455b4..0000000000
--- a/_includes/api/en/5x/express.text.md
+++ /dev/null
@@ -1,37 +0,0 @@
-<h3 id='express.text' class='h2'>express.text([options])</h3>
-
-This is a built-in middleware function in Express. It parses incoming request
-payloads into a string and is based on
-[body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that parses all bodies as a string and only looks at requests
-where the `Content-Type` header matches the `type` option. This parser accepts
-any Unicode encoding of the body and supports automatic inflation of `gzip` and
-`deflate` encodings.
-
-A new `body` string containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or `undefined` if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.trim()` may fail in multiple ways, for example
-stacking multiple parsers `req.body` may be from a different parser. Testing
-that `req.body` is a string before calling string methods is recommended.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property         | Description                                                           |   Type      | Default         |
-|------------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `defaultCharset` | Specify the default character set for the text content if the charset is not specified in the `Content-Type` header of the request. | String | `"utf-8"` |
-| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `txt`), a mime type (like `text/plain`), or a mime type with a wildcard (like `*/*` or `text/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"text/plain"` |
-| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-
-</div>
\ No newline at end of file
diff --git a/_includes/api/en/5x/express.urlencoded.md b/_includes/api/en/5x/express.urlencoded.md
deleted file mode 100644
index 58885486c3..0000000000
--- a/_includes/api/en/5x/express.urlencoded.md
+++ /dev/null
@@ -1,40 +0,0 @@
-<h3 id='express.urlencoded' class='h2'>express.urlencoded([options])</h3>
-
-This is a built-in middleware function in Express. It parses incoming requests
-with urlencoded payloads and is based on [body-parser](/resources/middleware/body-parser.html).
-
-Returns middleware that only parses urlencoded bodies and only looks at
-requests where the `Content-Type` header matches the `type` option. This
-parser accepts only UTF-8 encoding of the body and supports automatic
-inflation of `gzip` and `deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`), or `undefined` if
-there was no body to parse, the `Content-Type` was not matched, or an error
-occurred. This object will contain key-value pairs, where the value can be
-a string or array (when `extended` is `false`), or any type (when `extended`
-is `true`).
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and
-values in this object are untrusted and should be validated before trusting.
-For example, `req.body.foo.toString()` may fail in multiple ways, for example
-`foo` may not be there or may not be a string, and `toString` may not be a
-function and instead a string or other user-input.
-</div>
-
-The following table describes the properties of the optional `options` object.
-
-<div class="table-scroller" markdown="1">
-
-| Property         | Description                                                           |   Type      | Default         |
-|------------------|-----------------------------------------------------------------------|-------------|-----------------|
-| `extended`       | This option allows to choose between parsing the URL-encoded data with the `querystring` library (when `false`) or the `qs` library (when `true`). The "extended" syntax allows for rich objects and arrays to be encoded into the URL-encoded format, allowing for a JSON-like experience with URL-encoded. For more information, please [see the qs library](https://www.npmjs.org/package/qs#readme). | Boolean | `false` |
-| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected. | Boolean | `true` |
-| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing. | Mixed | `"100kb"` |
-| `parameterLimit` | This option controls the maximum number of parameters that are allowed in the URL-encoded data. If a request contains more parameters than this value, an error will be raised. | Number | `1000` |
-| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `urlencoded`), a mime type (like `application/x-www-form-urlencoded`), or a mime type with a wildcard (like `*/x-www-form-urlencoded`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed | `"application/x-www-form-urlencoded"` |
-| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error. | Function | `undefined` |
-| `depth`          | Configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible. | Number | `32` |
-
-</div>
diff --git a/_includes/api/en/5x/menu.md b/_includes/api/en/5x/menu.md
deleted file mode 100644
index 278555d110..0000000000
--- a/_includes/api/en/5x/menu.md
+++ /dev/null
@@ -1,209 +0,0 @@
-<button id="menu-toggle" title="show table of content">On this page</button>
-<ul id="menu">
-    <li id="express-api"><a href="#express">express()</a>
-    <ul id="express-menu">
-        <li><em>Methods</em></li>
-        <li id="express-json-middleware"><a href="#express.json">express.json()</a></li>
-        <li id="express-raw-middleware"><a href="#express.raw">express.raw()</a></li>
-        <li id="express-router"><a href="#express.router">express.Router()</a></li>
-        <li id="express-static-middleware"><a href="#express.static">express.static()</a></li>
-        <li id="express-text-middleware"><a href="#express.text">express.text()</a></li>
-        <li id="express-urlencoded-middleware"><a href="#express.urlencoded">express.urlencoded()</a></li>
-    </ul>
-    </li>
-
-    <li id="app-api"><a href="#app">Application</a>
-        <ul id="app-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#app.locals">app.locals</a>
-            </li>
-            <li><a href="#app.mountpath">app.mountpath</a>
-            </li>
-            <li><a href="#app.router">app.router</a>
-            </li>
-            <li><em>Events</em>
-            </li>
-            <li><a href="#app.onmount">mount</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#app.all">app.all()</a>
-            </li>
-            <li><a href="#app.delete.method">app.delete()</a>
-            </li>
-            <li><a href="#app.disable">app.disable()</a>
-            </li>
-            <li><a href="#app.disabled">app.disabled()</a>
-            </li>
-            <li><a href="#app.enable">app.enable()</a>
-            </li>
-            <li><a href="#app.enabled">app.enabled()</a>
-            </li>
-            <li><a href="#app.engine">app.engine()</a>
-            </li>
-            <li><a href="#app.get">app.get()</a>
-            </li>
-            <li><a href="#app.get.method">app.get()</a>
-            </li>
-            <li><a href="#app.listen">app.listen()</a>
-            </li>
-            <li><a href="#app.METHOD">app.METHOD()</a>
-            </li>
-            <li><a href="#app.param">app.param()</a>
-            </li>
-            <li><a href="#app.path">app.path()</a>
-            </li>
-            <li><a href="#app.post.method">app.post()</a>
-            </li>
-            <li><a href="#app.put.method">app.put()</a>
-            </li>
-            <li><a href="#app.render">app.render()</a>
-            </li>
-            <li><a href="#app.route">app.route()</a>
-            </li>
-            <li><a href="#app.set">app.set()</a>
-            </li>
-            <li><a href="#app.use">app.use()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="req-api"><a href="#req">Request</a>
-        <ul id="req-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#req.app">req.app</a>
-            </li>
-            <li><a href="#req.baseUrl">req.baseUrl</a>
-            </li>
-            <li><a href="#req.body">req.body</a>
-            </li>
-            <li><a href="#req.cookies">req.cookies</a>
-            </li>
-            <li><a href="#req.fresh">req.fresh</a>
-            </li>
-            <li><a href="#req.host">req.host</a>
-            </li>
-            <li><a href="#req.hostname">req.hostname</a>
-            </li>
-            <li><a href="#req.ip">req.ip</a>
-            </li>
-            <li><a href="#req.ips">req.ips</a>
-            </li>
-            <li><a href="#req.method">req.method</a>
-            </li>
-            <li><a href="#req.originalUrl">req.originalUrl</a>
-            </li>
-            <li><a href="#req.params">req.params</a>
-            </li>
-            <li><a href="#req.path">req.path</a>
-            </li>
-            <li><a href="#req.protocol">req.protocol</a>
-            </li>
-            <li><a href="#req.query">req.query</a>
-            </li>
-            <li><a href="#req.res">req.res</a>
-            </li>
-            <li><a href="#req.route">req.route</a>
-            </li>
-            <li><a href="#req.secure">req.secure</a>
-            </li>
-            <li><a href="#req.signedCookies">req.signedCookies</a>
-            </li>
-            <li><a href="#req.stale">req.stale</a>
-            </li>
-            <li><a href="#req.subdomains">req.subdomains</a>
-            </li>
-            <li><a href="#req.xhr">req.xhr</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#req.accepts">req.accepts()</a>
-            </li>
-            <li><a href="#req.acceptsCharsets">req.acceptsCharsets()</a>
-            </li>
-            <li><a href="#req.acceptsEncodings">req.acceptsEncodings()</a>
-            </li>
-            <li><a href="#req.acceptsLanguages">req.acceptsLanguages()</a>
-            </li>
-            <li><a href="#req.get">req.get()</a>
-            </li>
-            <li><a href="#req.is">req.is()</a>
-            </li>
-            <li><a href="#req.range">req.range()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="res-api"><a href="#res">Response</a>
-        <ul id="res-menu">
-            <li><em>Properties</em>
-            </li>
-            <li><a href="#res.app">res.app      </a>
-            </li>
-            <li><a href="#res.headersSent">res.headersSent</a>
-            </li>
-            <li><a href="#res.locals">res.locals</a>
-            </li>
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#res.append">res.append()</a>
-            </li>
-            <li><a href="#res.attachment">res.attachment()</a>
-            </li>
-            <li><a href="#res.cookie">res.cookie()</a>
-            </li>
-            <li><a href="#res.clearCookie">res.clearCookie()</a>
-            </li>
-            <li><a href="#res.download">res.download()</a>
-            </li>
-            <li><a href="#res.end">res.end()</a>
-            </li>
-            <li><a href="#res.format">res.format()</a>
-            </li>
-            <li><a href="#res.get">res.get()</a>
-            </li>
-            <li><a href="#res.json">res.json()</a>
-            </li>
-            <li><a href="#res.jsonp">res.jsonp()</a>
-            </li>
-            <li><a href="#res.links">res.links()</a>
-            </li>
-            <li><a href="#res.location">res.location()</a>
-            </li>
-            <li><a href="#res.redirect">res.redirect()</a>
-            </li>
-            <li><a href="#res.render">res.render()</a>
-            </li>
-            <li><a href="#res.send">res.send()</a>
-            </li>
-            <li><a href="#res.sendFile">res.sendFile()</a>
-            </li>
-            <li><a href="#res.sendStatus">res.sendStatus()</a>
-            </li>
-            <li><a href="#res.set">res.set()</a>
-            </li>
-            <li><a href="#res.status">res.status()</a>
-            </li>
-            <li><a href="#res.type">res.type()</a>
-            </li>
-            <li><a href="#res.vary">res.vary()</a>
-            </li>
-        </ul>
-    </li>
-    <li id="router-api"><a href="#router">Router</a>
-        <ul id="router-menu">
-            <li><em>Methods</em>
-            </li>
-            <li><a href="#router.all">router.all()</a>
-            </li>
-            <li><a href="#router.METHOD">router.METHOD()</a>
-            </li>
-            <li><a href="#router.param">router.param()</a>
-            </li>
-            <li><a href="#router.route">router.route()</a>
-            </li>
-            <li><a href="#router.use">router.use()</a>
-            </li>
-        </ul>
-    </li>
-</ul>
diff --git a/_includes/api/en/5x/req-accepts.md b/_includes/api/en/5x/req-accepts.md
deleted file mode 100644
index 7258c71b4c..0000000000
--- a/_includes/api/en/5x/req-accepts.md
+++ /dev/null
@@ -1,36 +0,0 @@
-<h3 id='req.accepts'>req.accepts(types)</h3>
-
-Checks if the specified content types are acceptable, based on the request's `Accept` HTTP header field.
-The method returns the best match, or if none of the specified content types is acceptable, returns
-`false` (in which case, the application should respond with `406 "Not Acceptable"`).
-
-The `type` value may be a single MIME type string (such as "application/json"),
-an extension name such as "json", a comma-delimited list, or an array. For a
-list or array, the method returns the *best* match (if any).
-
-```js
-// Accept: text/html
-req.accepts('html')
-// => "html"
-
-// Accept: text/*, application/json
-req.accepts('html')
-// => "html"
-req.accepts('text/html')
-// => "text/html"
-req.accepts(['json', 'text'])
-// => "json"
-req.accepts('application/json')
-// => "application/json"
-
-// Accept: text/*, application/json
-req.accepts('image/png')
-req.accepts('png')
-// => false
-
-// Accept: text/*;q=.5, application/json
-req.accepts(['html', 'json'])
-// => "json"
-```
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/5x/req-acceptsCharsets.md b/_includes/api/en/5x/req-acceptsCharsets.md
deleted file mode 100644
index d47d0480d3..0000000000
--- a/_includes/api/en/5x/req-acceptsCharsets.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='req.acceptsCharsets'>req.acceptsCharsets(charset [, ...])</h3>
-
-Returns the first accepted charset of the specified character sets,
-based on the request's `Accept-Charset` HTTP header field.
-If none of the specified charsets is accepted, returns `false`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/5x/req-acceptsEncodings.md b/_includes/api/en/5x/req-acceptsEncodings.md
deleted file mode 100644
index 2c6a3f236f..0000000000
--- a/_includes/api/en/5x/req-acceptsEncodings.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='req.acceptsEncodings'>req.acceptsEncodings(encoding [, ...])</h3>
-
-Returns the first accepted encoding of the specified encodings,
-based on the request's `Accept-Encoding` HTTP header field.
-If none of the specified encodings is accepted, returns `false`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
diff --git a/_includes/api/en/5x/req-acceptsLanguages.md b/_includes/api/en/5x/req-acceptsLanguages.md
deleted file mode 100644
index 7aefa5477d..0000000000
--- a/_includes/api/en/5x/req-acceptsLanguages.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='req.acceptsLanguages'>req.acceptsLanguages([lang, ...])</h3>
-
-Returns the first accepted language of the specified languages,
-based on the request's `Accept-Language` HTTP header field.
-If none of the specified languages is accepted, returns `false`.
-
-If no `lang` argument is given, then `req.acceptsLanguages()`
-returns all languages from the HTTP `Accept-Language` header
-as an `Array`.
-
-For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
-
-Express (5.x) source: [request.js line 172](https://github.com/expressjs/express/blob/v5.1.0/lib/request.js#L172)
-
-Accepts (2.0) source: [index.js line 195](https://github.com/jshttp/accepts/blob/2.0.0/index.js#L195)
diff --git a/_includes/api/en/5x/req-app.md b/_includes/api/en/5x/req-app.md
deleted file mode 100644
index 30873d7ab7..0000000000
--- a/_includes/api/en/5x/req-app.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='req.app'>req.app</h3>
-
-This property holds a reference to the instance of the Express application that is using the middleware.
-
-If you follow the pattern in which you create a module that just exports a middleware function
-and `require()` it in your main file, then the middleware can access the Express instance via `req.app`
-
-For example:
-
-```js
-// index.js
-app.get('/viewdirectory', require('./mymiddleware.js'))
-```
-
-```js
-// mymiddleware.js
-module.exports = (req, res) => {
-  res.send(`The views directory is ${req.app.get('views')}`)
-}
-```
diff --git a/_includes/api/en/5x/req-baseUrl.md b/_includes/api/en/5x/req-baseUrl.md
deleted file mode 100644
index 3daa0ee5b6..0000000000
--- a/_includes/api/en/5x/req-baseUrl.md
+++ /dev/null
@@ -1,30 +0,0 @@
-<h3 id='req.baseUrl'>req.baseUrl</h3>
-
-The URL path on which a router instance was mounted.
-
-The `req.baseUrl` property is similar to the [mountpath](#app.mountpath) property of the `app` object,
-except `app.mountpath` returns the matched path pattern(s).
-
-For example:
-
-```js
-const greet = express.Router()
-
-greet.get('/jp', (req, res) => {
-  console.log(req.baseUrl) // /greet
-  res.send('Konichiwa!')
-})
-
-app.use('/greet', greet) // load the router on '/greet'
-```
-
-Even if you use a path pattern or a set of path patterns to load the router,
-the `baseUrl` property returns the matched string, not the pattern(s). In the
-following example, the `greet` router is loaded on two path patterns.
-
-```js
-app.use(['/gre:"param"t', '/hel{l}o'], greet) // load the router on '/gre:"param"t' and '/hel{l}o'
-```
-
-When a request is made to `/greet/jp`, `req.baseUrl` is "/greet". When a request is
-made to `/hello/jp`, `req.baseUrl` is "/hello".
diff --git a/_includes/api/en/5x/req-body.md b/_includes/api/en/5x/req-body.md
deleted file mode 100644
index ea3610b04b..0000000000
--- a/_includes/api/en/5x/req-body.md
+++ /dev/null
@@ -1,25 +0,0 @@
-<h3 id='req.body'>req.body</h3>
-
-Contains key-value pairs of data submitted in the request body.
-By default, it is `undefined`, and is populated when you use body-parsing middleware such
-as [`express.json()`](#express.json) or [`express.urlencoded()`](#express.urlencoded).
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.body`'s shape is based on user-controlled input, all properties and values in this object are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString` may not be a function and instead a string or other user-input.
-</div>
-
-The following example shows how to use body-parsing middleware to populate `req.body`.
-
-```js
-const express = require('express')
-
-const app = express()
-
-app.use(express.json()) // for parsing application/json
-app.use(express.urlencoded({ extended: true })) // for parsing application/x-www-form-urlencoded
-
-app.post('/profile', (req, res, next) => {
-  console.log(req.body)
-  res.json(req.body)
-})
-```
diff --git a/_includes/api/en/5x/req-cookies.md b/_includes/api/en/5x/req-cookies.md
deleted file mode 100644
index 00821e722f..0000000000
--- a/_includes/api/en/5x/req-cookies.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='req.cookies'>req.cookies</h3>
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property is an object that
-contains cookies sent by the request. If the request contains no cookies, it defaults to `{}`.
-
-```js
-// Cookie: name=tj
-console.dir(req.cookies.name)
-// => "tj"
-```
-
-If the cookie has been signed, you have to use [req.signedCookies](#req.signedCookies).
-
-For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
diff --git a/_includes/api/en/5x/req-fresh.md b/_includes/api/en/5x/req-fresh.md
deleted file mode 100644
index 1b6ec61c59..0000000000
--- a/_includes/api/en/5x/req-fresh.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.fresh'>req.fresh</h3>
-
-When the response is still "fresh" in the client's cache `true` is returned, otherwise `false` is returned to indicate that the client cache is now stale and the full response should be sent.
-
-When a client sends the `Cache-Control: no-cache` request header to indicate an end-to-end reload request, this module will return `false` to make handling these requests transparent.
-
-Further details for how cache validation works can be found in the
-[HTTP/1.1 Caching Specification](https://tools.ietf.org/html/rfc7234).
-
-```js
-console.dir(req.fresh)
-// => true
-```
diff --git a/_includes/api/en/5x/req-get.md b/_includes/api/en/5x/req-get.md
deleted file mode 100644
index 7cd4250b22..0000000000
--- a/_includes/api/en/5x/req-get.md
+++ /dev/null
@@ -1,17 +0,0 @@
-<h3 id='req.get'>req.get(field)</h3>
-
-Returns the specified HTTP request header field (case-insensitive match).
-The `Referrer` and `Referer` fields are interchangeable.
-
-```js
-req.get('Content-Type')
-// => "text/plain"
-
-req.get('content-type')
-// => "text/plain"
-
-req.get('Something')
-// => undefined
-```
-
-Aliased as `req.header(field)`.
diff --git a/_includes/api/en/5x/req-host.md b/_includes/api/en/5x/req-host.md
deleted file mode 100644
index dfcf63be9e..0000000000
--- a/_includes/api/en/5x/req-host.md
+++ /dev/null
@@ -1,22 +0,0 @@
-<h3 id='req.host'>req.host</h3>
-
-Contains the host derived from the `Host` HTTP header.
-
-When the [`trust proxy` setting](api.html#app.settings.table)
-does not evaluate to `false`, this property will instead get the value
-from the `X-Forwarded-Host` header field. This header can be set by
-the client or by the proxy.
-
-If there is more than one `X-Forwarded-Host` header in the request, the
-value of the first header is used. This includes a single header with
-comma-separated values, in which the first value is used.
-
-```js
-// Host: "example.com:3000"
-console.dir(req.host)
-// => 'example.com:3000'
-
-// Host: "[::1]:3000"
-console.dir(req.host)
-// => '[::1]:3000'
-```
diff --git a/_includes/api/en/5x/req-hostname.md b/_includes/api/en/5x/req-hostname.md
deleted file mode 100644
index 327a22426d..0000000000
--- a/_includes/api/en/5x/req-hostname.md
+++ /dev/null
@@ -1,23 +0,0 @@
-<h3 id='req.hostname'>req.hostname</h3>
-
-Contains the hostname derived from the `Host` HTTP header.
-
-When the [`trust proxy` setting](/5x/api.html#trust.proxy.options.table)
-does not evaluate to `false`, this property will instead get the value
-from the `X-Forwarded-Host` header field. This header can be set by
-the client or by the proxy.
-
-If there is more than one `X-Forwarded-Host` header in the request, the
-value of the first header is used. This includes a single header with
-comma-separated values, in which the first value is used.
-
-<div class="doc-box doc-info" markdown="1">
-Prior to Express v4.17.0, the `X-Forwarded-Host` could not contain multiple
-values or be present more than once.
-</div>
-
-```js
-// Host: "example.com:3000"
-console.dir(req.hostname)
-// => 'example.com'
-```
diff --git a/_includes/api/en/5x/req-ip.md b/_includes/api/en/5x/req-ip.md
deleted file mode 100644
index 0bbc7f0318..0000000000
--- a/_includes/api/en/5x/req-ip.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='req.ip'>req.ip</h3>
-
-Contains the remote IP address of the request.
-
-When the [`trust proxy` setting](/5x/api.html#trust.proxy.options.table) does not evaluate to `false`,
-the value of this property is derived from the left-most entry in the
-`X-Forwarded-For` header. This header can be set by the client or by the proxy.
-
-```js
-console.dir(req.ip)
-// => "127.0.0.1"
-```
diff --git a/_includes/api/en/5x/req-ips.md b/_includes/api/en/5x/req-ips.md
deleted file mode 100644
index 312238b346..0000000000
--- a/_includes/api/en/5x/req-ips.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.ips'>req.ips</h3>
-
-When the [`trust proxy` setting](/5x/api.html#trust.proxy.options.table) does not evaluate to `false`,
-this property contains an array of IP addresses
-specified in the `X-Forwarded-For` request header. Otherwise, it contains an
-empty array. This header can be set by the client or by the proxy.
-
-For example, if `X-Forwarded-For` is `client, proxy1, proxy2`, `req.ips` would be
-`["client", "proxy1", "proxy2"]`, where `proxy2` is the furthest downstream.
diff --git a/_includes/api/en/5x/req-is.md b/_includes/api/en/5x/req-is.md
deleted file mode 100644
index 7ee29a9cf2..0000000000
--- a/_includes/api/en/5x/req-is.md
+++ /dev/null
@@ -1,31 +0,0 @@
-<h3 id='req.is'>req.is(type)</h3>
-
-Returns the matching content type if the incoming request's "Content-Type" HTTP header field
-matches the MIME type specified by the `type` parameter. If the request has no body, returns `null`.
-Returns `false` otherwise.
-
-```js
-// With Content-Type: text/html; charset=utf-8
-req.is('html') // => 'html'
-req.is('text/html') // => 'text/html'
-req.is('text/*') // => 'text/*'
-
-// When Content-Type is application/json
-req.is('json') // => 'json'
-req.is('application/json') // => 'application/json'
-req.is('application/*') // => 'application/*'
-
-// Using arrays
-// When Content-Type is application/json
-req.is(['json', 'html']) // => 'json'
-
-// Using multiple arguments
-// When Content-Type is application/json
-req.is('json', 'html') // => 'json'
-
-req.is('html') // => false
-req.is(['xml', 'yaml']) // => false
-req.is('xml', 'yaml') // => false
-```
-
-For more information, or if you have issues or concerns, see [type-is](https://github.com/expressjs/type-is).
diff --git a/_includes/api/en/5x/req-method.md b/_includes/api/en/5x/req-method.md
deleted file mode 100644
index 3d2b886d7d..0000000000
--- a/_includes/api/en/5x/req-method.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='req.method'>req.method</h3>
-
-Contains a string corresponding to the HTTP method of the request:
-`GET`, `POST`, `PUT`, and so on.
diff --git a/_includes/api/en/5x/req-originalUrl.md b/_includes/api/en/5x/req-originalUrl.md
deleted file mode 100644
index 660f46d7b1..0000000000
--- a/_includes/api/en/5x/req-originalUrl.md
+++ /dev/null
@@ -1,28 +0,0 @@
-<h3 id='req.originalUrl'>req.originalUrl</h3>
-
-<div class="doc-box doc-notice" markdown="1">
-`req.url` is not a native Express property, it is inherited from Node's [http module](https://nodejs.org/api/http.html#http_message_url).
-</div>
-
-This property is much like `req.url`; however, it retains the original request URL,
-allowing you to rewrite `req.url` freely for internal routing purposes. For example,
-the "mounting" feature of [app.use()](#app.use) will rewrite `req.url` to strip the mount point.
-
-```js
-// GET /search?q=something
-console.dir(req.originalUrl)
-// => "/search?q=something"
-```
-
-`req.originalUrl` is available both in middleware and router objects, and is a
-combination of `req.baseUrl` and `req.url`. Consider following example:
-
-```js
-// GET 'http://www.example.com/admin/new?sort=desc'
-app.use('/admin', (req, res, next) => {
-  console.dir(req.originalUrl) // '/admin/new?sort=desc'
-  console.dir(req.baseUrl) // '/admin'
-  console.dir(req.path) // '/new'
-  next()
-})
-```
diff --git a/_includes/api/en/5x/req-params.md b/_includes/api/en/5x/req-params.md
deleted file mode 100644
index 4037832cb4..0000000000
--- a/_includes/api/en/5x/req-params.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='req.params'>req.params</h3>
-
-This property is an object containing properties mapped to the [named route "parameters"](/{{ page.lang }}/guide/routing.html#route-parameters). For example, if you have the route `/user/:name`, then the "name" property is available as `req.params.name`. This object defaults to `Object.create(null)` when using string paths, but remains a standard object with a normal prototype when the path is defined with a regular expression.
-
-```js
-// GET /user/tj
-console.dir(req.params.name)
-// => "tj"
-```
-
-Properties corresponding to wildcard parameters are arrays containing separate path segments split on `/`:
-
-```js
-app.get('/files/*file', (req, res) => {
-  console.dir(req.params.file)
-  // GET /files/note.txt
-  // => [ 'note.txt' ]
-  // GET /files/images/image.png
-  // => [ 'images', 'image.png' ]
-})
-```
-
-When you use a regular expression for the route definition, capture groups are provided as integer keys using `req.params[n]`, where `n` is the n<sup>th</sup> capture group.
-
-```js
-app.use(/^\/file\/(.*)$/, (req, res) => {
-  // GET /file/javascripts/jquery.js
-  console.dir(req.params[0])
-  // => "javascripts/jquery.js"
-})
-```
-
-Named capturing groups in regular expressions behave like named route parameters. For example the group from `/^\/file\/(?<path>.*)$/` expression is available as `req.params.path`.
-
-If you need to make changes to a key in `req.params`, use the [app.param](/{{ page.lang }}/5x/api.html#app.param) handler. Changes are applicable only to [parameters](/{{ page.lang }}/guide/routing.html#route-parameters) already defined in the route path.
-
-Any changes made to the `req.params` object in a middleware or route handler will be reset.
-
-{% include admonitions/note.html content="Express automatically decodes the values in `req.params` (using `decodeURIComponent`)." %}
\ No newline at end of file
diff --git a/_includes/api/en/5x/req-path.md b/_includes/api/en/5x/req-path.md
deleted file mode 100644
index 70eb680c50..0000000000
--- a/_includes/api/en/5x/req-path.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.path'>req.path</h3>
-
-Contains the path part of the request URL.
-
-```js
-// example.com/users?sort=desc
-console.dir(req.path)
-// => "/users"
-```
-
-<div class="doc-box doc-info" markdown="1">
-When called from a middleware, the mount point is not included in `req.path`. See [app.use()](/5x/api.html#app.use) for more details.
-</div>
diff --git a/_includes/api/en/5x/req-protocol.md b/_includes/api/en/5x/req-protocol.md
deleted file mode 100644
index 32e1ba8a75..0000000000
--- a/_includes/api/en/5x/req-protocol.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<h3 id='req.protocol'>req.protocol</h3>
-
-Contains the request protocol string: either `http` or (for TLS requests) `https`.
-
-When the [`trust proxy` setting](#trust.proxy.options.table) does not evaluate to `false`,
-this property will use the value of the `X-Forwarded-Proto` header field if present.
-This header can be set by the client or by the proxy.
-
-```js
-console.dir(req.protocol)
-// => "http"
-```
diff --git a/_includes/api/en/5x/req-query.md b/_includes/api/en/5x/req-query.md
deleted file mode 100644
index ca114cf2ca..0000000000
--- a/_includes/api/en/5x/req-query.md
+++ /dev/null
@@ -1,18 +0,0 @@
-<h3 id='req.query'>req.query</h3>
-
-This property is an object containing a property for each query string parameter in the route.
-When [query parser](#app.settings.table) is set to disabled, it is an empty object `{}`, otherwise it is the result of the configured query parser.
-
-<div class="doc-box doc-warn" markdown="1">
-As `req.query`'s shape is based on user-controlled input, all properties and values in this object are untrusted and should be validated before trusting. For example, `req.query.foo.toString()` may fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString` may not be a function and instead a string or other user-input.
-</div>
-
-The value of this property can be configured with the [query parser application setting](#app.settings.table) to work how your application needs it. A very popular query string parser is the [`qs` module](https://www.npmjs.org/package/qs), and this is used by default. The `qs` module is very configurable with many settings, and it may be desirable to use different settings than the default to populate `req.query`:
-
-```js
-const qs = require('qs')
-app.set('query parser',
-  (str) => qs.parse(str, { /* custom options */ }))
-```
-
-Check out the [query parser application setting](#app.settings.table) documentation for other customization options.
diff --git a/_includes/api/en/5x/req-range.md b/_includes/api/en/5x/req-range.md
deleted file mode 100644
index 1444f8f816..0000000000
--- a/_includes/api/en/5x/req-range.md
+++ /dev/null
@@ -1,33 +0,0 @@
-<h3 id='req.range'>req.range(size[, options])</h3>
-
-`Range` header parser.
-
-The `size` parameter is the maximum size of the resource.
-
-The `options` parameter is an object that can have the following properties.
-
-<div class="table-scroller" markdown="1">
-
-| Property    | Type |  Description                                                     |
-|-------------|-------------------------------------------------------------------------|
-| `combine`   | Boolean | Specify if overlapping & adjacent ranges should be combined, defaults to `false`. When `true`, ranges will be combined and returned as if they were specified that way in the header.|
-
-</div>
-
-An array of ranges will be returned or negative numbers indicating an error parsing.
-
-* `-2` signals a malformed header string
-* `-1` signals an unsatisfiable range
-
-```js
-// parse header from request
-const range = req.range(1000)
-
-// the type of the range
-if (range.type === 'bytes') {
-  // the ranges
-  range.forEach((r) => {
-    // do something with r.start and r.end
-  })
-}
-```
diff --git a/_includes/api/en/5x/req-res.md b/_includes/api/en/5x/req-res.md
deleted file mode 100644
index 772ddb43b4..0000000000
--- a/_includes/api/en/5x/req-res.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='req.res'>req.res</h3>
-
-This property holds a reference to the <a href="#res">response object</a>
-that relates to this request object.
diff --git a/_includes/api/en/5x/req-route.md b/_includes/api/en/5x/req-route.md
deleted file mode 100644
index fb8084b0ae..0000000000
--- a/_includes/api/en/5x/req-route.md
+++ /dev/null
@@ -1,31 +0,0 @@
-<h3 id='req.route'>req.route</h3>
-
-Contains the currently-matched route, a string. For example:
-
-```js
-app.get('/user/{:id}', (req, res) => {
-  console.dir(req.route, { depth: null })
-  res.send('GET')
-})
-```
-
-Example output from the previous snippet:
-
-```
-Route {
-  path: '/user/{:id}',
-  stack: [
-    Layer {
-      handle: [Function (anonymous)],
-      keys: [],
-      name: '<anonymous>',
-      params: undefined,
-      path: undefined,
-      slash: false,
-      matchers: [ [Function: match] ],
-      method: 'get'
-    }
-  ],
-  methods: [Object: null prototype] { get: true }
-}
-```
diff --git a/_includes/api/en/5x/req-secure.md b/_includes/api/en/5x/req-secure.md
deleted file mode 100644
index 4d8ab831ce..0000000000
--- a/_includes/api/en/5x/req-secure.md
+++ /dev/null
@@ -1,8 +0,0 @@
-<h3 id='req.secure'>req.secure</h3>
- 
-A Boolean property that is true if a TLS connection is established. Equivalent to the following:
-
-<!-- eslint-disable no-unused-expressions -->
-```js
-req.protocol === 'https'
-```
diff --git a/_includes/api/en/5x/req-signedCookies.md b/_includes/api/en/5x/req-signedCookies.md
deleted file mode 100644
index 2fd5b3c29c..0000000000
--- a/_includes/api/en/5x/req-signedCookies.md
+++ /dev/null
@@ -1,17 +0,0 @@
-<h3 id='req.signedCookies'>req.signedCookies</h3>
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property
-contains signed cookies sent by the request, unsigned and ready for use. Signed cookies reside
-in a different object to show developer intent; otherwise, a malicious attack could be placed on
-`req.cookie` values (which are easy to spoof). Note that signing a cookie does not make it "hidden"
-or encrypted; but simply prevents tampering (because the secret used to sign is private).
-
-If no signed cookies are sent, the property defaults to `{}`.
-
-```js
-// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
-console.dir(req.signedCookies.user)
-// => "tobi"
-```
-
-For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
diff --git a/_includes/api/en/5x/req-stale.md b/_includes/api/en/5x/req-stale.md
deleted file mode 100644
index ca8b479f4c..0000000000
--- a/_includes/api/en/5x/req-stale.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.stale'>req.stale</h3>
-
-Indicates whether the request is "stale," and is the opposite of `req.fresh`.
-For more information, see [req.fresh](#req.fresh).
-
-```js
-console.dir(req.stale)
-// => true
-```
diff --git a/_includes/api/en/5x/req-subdomains.md b/_includes/api/en/5x/req-subdomains.md
deleted file mode 100644
index 714e6e8c07..0000000000
--- a/_includes/api/en/5x/req-subdomains.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='req.subdomains'>req.subdomains</h3>
-
-An array of subdomains in the domain name of the request.
-
-```js
-// Host: "tobi.ferrets.example.com"
-console.dir(req.subdomains)
-// => ["ferrets", "tobi"]
-```
-
-The application property `subdomain offset`, which defaults to 2, is used for determining the
-beginning of the subdomain segments. To change this behavior, change its value
-using [app.set](/{{ page.lang }}/5x/api.html#app.set).
diff --git a/_includes/api/en/5x/req-xhr.md b/_includes/api/en/5x/req-xhr.md
deleted file mode 100644
index 5c1da1c704..0000000000
--- a/_includes/api/en/5x/req-xhr.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='req.xhr'>req.xhr</h3>
-
-A Boolean property that is `true` if the request's `X-Requested-With` header field is
-"XMLHttpRequest", indicating that the request was issued by a client library such as jQuery.
-
-```js
-console.dir(req.xhr)
-// => true
-```
diff --git a/_includes/api/en/5x/req.md b/_includes/api/en/5x/req.md
deleted file mode 100644
index 7b330b88f8..0000000000
--- a/_includes/api/en/5x/req.md
+++ /dev/null
@@ -1,156 +0,0 @@
-<h2 id="req">Request</h2>
-
-The `req` object represents the HTTP request and has properties for the
-request query string, parameters, body, HTTP headers, and so on. In this documentation and by convention,
-the object is always referred to as `req` (and the HTTP response is `res`) but its actual name is determined
-by the parameters to the callback function in which you're working.
-
-For example:
-
-```js
-app.get('/user/:id', (req, res) => {
-  res.send(`user ${req.params.id}`)
-})
-```
-
-But you could just as well have:
-
-```js
-app.get('/user/:id', (request, response) => {
-  response.send(`user ${request.params.id}`)
-})
-```
-
-The `req` object is an enhanced version of Node's own request object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).
-
-<h3 id='req.properties'>Properties</h3>
-
-<div class="doc-box doc-notice" markdown="1">
-In Express 4, `req.files` is no longer available on the `req` object by default. To access uploaded files
-on the `req.files` object, use multipart-handling middleware like [busboy](https://www.npmjs.
-com/package/busboy), [multer](https://www.npmjs.com/package/multer),
-[formidable](https://www.npmjs.com/package/formidable),
-[multiparty](https://www.npmjs.com/package/multiparty),
-[connect-multiparty](https://www.npmjs.com/package/connect-multiparty),
-or [pez](https://www.npmjs.com/package/pez).
-</div>
-
-<section markdown="1">
-  {% include api/en/5x/req-app.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-baseUrl.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-body.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-cookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-fresh.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-host.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-hostname.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-ip.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-ips.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-method.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-originalUrl.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-params.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-path.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-protocol.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-query.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-res.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-secure.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-signedCookies.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-stale.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-subdomains.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-xhr.md %}
-</section>
-
-<h3 id='req.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/5x/req-accepts.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-acceptsCharsets.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-acceptsEncodings.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-acceptsLanguages.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-is.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/req-range.md %}
-</section>
-
diff --git a/_includes/api/en/5x/res-app.md b/_includes/api/en/5x/res-app.md
deleted file mode 100644
index 19d8681d23..0000000000
--- a/_includes/api/en/5x/res-app.md
+++ /dev/null
@@ -1,5 +0,0 @@
-<h3 id='res.app'>res.app</h3>
-
-This property holds a reference to the instance of the Express application that is using the middleware.
-
-`res.app` is identical to the [req.app](#req.app) property in the request object.
diff --git a/_includes/api/en/5x/res-append.md b/_includes/api/en/5x/res-append.md
deleted file mode 100644
index 2522d827ba..0000000000
--- a/_includes/api/en/5x/res-append.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.append'>res.append(field [, value])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-`res.append()` is supported by Express v4.11.0+
-</div>
-
-Appends the specified `value` to the HTTP response header `field`.  If the header is not already set,
-it creates the header with the specified value. The `value` parameter can be a string or an array.
-
-{% include admonitions/note.html content="calling `res.set()` after `res.append()` will reset the previously-set header value." %}
-
-```js
-res.append('Link', ['<http://localhost/>', '<http://localhost:3000/>'])
-res.append('Set-Cookie', 'foo=bar; Path=/; HttpOnly')
-res.append('Warning', '199 Miscellaneous warning')
-```
diff --git a/_includes/api/en/5x/res-attachment.md b/_includes/api/en/5x/res-attachment.md
deleted file mode 100644
index 73556bece4..0000000000
--- a/_includes/api/en/5x/res-attachment.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<h3 id='res.attachment'>res.attachment([filename])</h3>
-
-Sets the HTTP response `Content-Disposition` header field to "attachment". If a `filename` is given,
-then it sets the `Content-Type` based on the extension name via `res.type()`,
-and sets the `Content-Disposition` "filename=" parameter.
-
-```js
-res.attachment()
-// Content-Disposition: attachment
-
-res.attachment('path/to/logo.png')
-// Content-Disposition: attachment; filename="logo.png"
-// Content-Type: image/png
-```
diff --git a/_includes/api/en/5x/res-clearCookie.md b/_includes/api/en/5x/res-clearCookie.md
deleted file mode 100644
index 543fe2e2a1..0000000000
--- a/_includes/api/en/5x/res-clearCookie.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<h3 id='res.clearCookie'>res.clearCookie(name [, options])</h3>
-
-Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
-This instructs the client that the cookie has expired and is no longer valid. For more information
-about available `options`, see [res.cookie()](#res.cookie).
-
-<div class="doc-box doc-notice" markdown="1">
-The `expires` and `max-age` options are being ignored completely.
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-Web browsers and other compliant clients will only clear the cookie if the given
-`options` is identical to those given to [res.cookie()](#res.cookie)
-</div>
-
-```js
-res.cookie('name', 'tobi', { path: '/admin' })
-res.clearCookie('name', { path: '/admin' })
-```
diff --git a/_includes/api/en/5x/res-cookie.md b/_includes/api/en/5x/res-cookie.md
deleted file mode 100644
index c8ee380e5e..0000000000
--- a/_includes/api/en/5x/res-cookie.md
+++ /dev/null
@@ -1,87 +0,0 @@
-<h3 id='res.cookie'>res.cookie(name, value [, options])</h3>
-
-Sets cookie `name` to `value`.  The `value` parameter may be a string or object converted to JSON.
-
-The `options` parameter is an object that can have the following properties.
-
-<div class="table-scroller" markdown="1">
-
-| Property      | Type |  Description                                                             |
-|---------------|-------------------------------------------------------------------------|
-| `domain`      | String | Domain name for the cookie. Defaults to the domain name of the app.|
-| `encode`      | Function | A synchronous function used for cookie value encoding. Defaults to `encodeURIComponent`.|
-| `expires`     | Date | Expiry date of the cookie in GMT. If not specified or set to 0, creates a session cookie.|
-| `httpOnly`    | Boolean | Flags the cookie to be accessible only by the web server.|
-| `maxAge`      | Number | Convenient option for setting the expiry time relative to the current time in milliseconds.|
-| `path`        | String | Path for the cookie. Defaults to "/".|
-| `partitioned` | Boolean | Indicates that the cookie should be stored using partitioned storage. See [Cookies Having Independent Partitioned State (CHIPS)](https://developer.mozilla.org/en-US/docs/Web/Privacy/Partitioned_cookies) for more details.|
-| `priority`    | String | Value of the "Priority" **Set-Cookie** attribute.|
-| `secure`      | Boolean | Marks the cookie to be used with HTTPS only.|
-| `signed`      | Boolean | Indicates if the cookie should be signed.|
-| `sameSite`    | Boolean or String | Value of the "SameSite" **Set-Cookie** attribute. More information at [https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1](https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1).|
-
-</div>
-
-<div class="doc-box doc-notice" markdown="1">
-All `res.cookie()` does is set the HTTP `Set-Cookie` header with the options provided.
-Any option not specified defaults to the value stated in [RFC 6265](http://tools.ietf.org/html/rfc6265).
-</div>
-
-For example:
-
-```js
-res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true })
-res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true })
-```
-
-You can set multiple cookies in a single response by calling `res.cookie` multiple times, for example:
-
-```js
-res
-  .status(201)
-  .cookie('access_token', `Bearer ${token}`, {
-    expires: new Date(Date.now() + 8 * 3600000) // cookie will be removed after 8 hours
-  })
-  .cookie('test', 'test')
-  .redirect(301, '/admin')
-```
-
-The `encode` option allows you to choose the function used for cookie value encoding.
-Does not support asynchronous functions.
-
-Example use case: You need to set a domain-wide cookie for another site in your organization.
-This other site (not under your administrative control) does not use URI-encoded cookie values.
-
-```js
-// Default encoding
-res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com' })
-// Result: 'some_cross_domain_cookie=http%3A%2F%2Fmysubdomain.example.com; Domain=example.com; Path=/'
-
-// Custom encoding
-res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com', encode: String })
-// Result: 'some_cross_domain_cookie=http://mysubdomain.example.com; Domain=example.com; Path=/;'
-```
-
-The `maxAge` option is a convenience option for setting "expires" relative to the current time in milliseconds.
-The following is equivalent to the second example above.
-
-```js
-res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true })
-```
-
-You can pass an object as the `value` parameter; it is then serialized as JSON and parsed by `bodyParser()` middleware.
-
-```js
-res.cookie('cart', { items: [1, 2, 3] })
-res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 })
-```
-
-When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this method also
-supports signed cookies. Simply include the `signed` option set to `true`.
-Then, `res.cookie()` will use the secret passed to `cookieParser(secret)` to sign the value.
-
-```js
-res.cookie('name', 'tobi', { signed: true })
-```
-
-Later, you may access this value through the [req.signedCookies](#req.signedCookies) object.
diff --git a/_includes/api/en/5x/res-download.md b/_includes/api/en/5x/res-download.md
deleted file mode 100644
index b95c89a50c..0000000000
--- a/_includes/api/en/5x/res-download.md
+++ /dev/null
@@ -1,60 +0,0 @@
-<h3 id='res.download'>res.download(path [, filename] [, options] [, fn])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-The optional `options` argument is supported by Express v4.16.0 onwards.
-</div>
-
-Transfers the file at `path` as an "attachment". Typically, browsers will prompt the user for download.
-By default, the `Content-Disposition` header "filename=" parameter is derived from the `path` argument, but can be overridden with the `filename` parameter.
-If `path` is relative, then it will be based on the current working directory of the process or
-the `root` option, if provided.
-
-<div class="doc-box doc-warn" markdown="1">
-This API provides access to data on the running file system. Ensure that either (a) the way in
-which the `path` argument was constructed is secure if it contains user input or (b) set the `root`
-option to the absolute path of a directory to contain access within.
-
-When the `root` option is provided, Express will validate that the relative path provided as
-`path` will resolve within the given `root` option.
-</div>
-
-The following table provides details on the `options` parameter.
-
-<div class="doc-box doc-info" markdown="1">
-The optional `options` argument is supported by Express v4.16.0 onwards.
-</div>
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability |
-|-----------------|-------------------------------------------------|-------------|--------------|
-| `maxAge`        | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)| 0 | 4.16+ |
-| `root`          | Root directory for relative filenames.|  | 4.18+ |
-| `lastModified`  | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.| Enabled | 4.16+ |
-| `headers`       | Object containing HTTP headers to serve with the file. The header `Content-Disposition` will be overridden by the `filename` argument.|  | 4.16+ |
-| `dotfiles`      | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".| "ignore" | 4.16+ |
-| `acceptRanges`  | Enable or disable accepting ranged requests. | `true` | 4.16+ |
-| `cacheControl`  | Enable or disable setting `Cache-Control` response header.| `true` | 4.16+ |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false` | 4.16+ |
-
-</div>
-
-The method invokes the callback function `fn(err)` when the transfer is complete
-or when an error occurs. If the callback function is specified and an error occurs,
-the callback function must explicitly handle the response process either by
-ending the request-response cycle, or by passing control to the next route.
-
-```js
-res.download('/report-12345.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf')
-
-res.download('/report-12345.pdf', 'report.pdf', (err) => {
-  if (err) {
-    // Handle error, but keep in mind the response may be partially-sent
-    // so check res.headersSent
-  } else {
-    // decrement a download credit, etc.
-  }
-})
-```
diff --git a/_includes/api/en/5x/res-end.md b/_includes/api/en/5x/res-end.md
deleted file mode 100644
index 2906805fea..0000000000
--- a/_includes/api/en/5x/res-end.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='res.end'>res.end([data[, encoding]][, callback])</h3>
-
-Ends the response process. This method actually comes from Node core, specifically the [response.end() method of http.ServerResponse](https://nodejs.org/api/http.html#responseenddata-encoding-callback).
-
-Use to quickly end the response without any data. If you need to respond with data, instead use methods such as [res.send()](#res.send) and [res.json()](#res.json).
-
-```js
-res.end()
-res.status(404).end()
-```
diff --git a/_includes/api/en/5x/res-format.md b/_includes/api/en/5x/res-format.md
deleted file mode 100644
index 1a5a3d7a5a..0000000000
--- a/_includes/api/en/5x/res-format.md
+++ /dev/null
@@ -1,52 +0,0 @@
-<h3 id='res.format'>res.format(object)</h3>
-
-Performs content-negotiation on the `Accept` HTTP header on the request object, when present.
-It uses [req.accepts()](#req.accepts) to select a handler for the request, based on the acceptable
-types ordered by their quality values. If the header is not specified, the first callback is invoked.
-When no match is found, the server responds with 406 "Not Acceptable", or invokes the `default` callback.
-
-The `Content-Type` response header is set when a callback is selected. However, you may alter
-this within the callback using methods such as `res.set()` or `res.type()`.
-
-The following example would respond with `{ "message": "hey" }` when the `Accept` header field is set
-to "application/json" or "\*/json" (however, if it is "\*/\*", then the response will be "hey").
-
-```js
-res.format({
-  'text/plain' () {
-    res.send('hey')
-  },
-
-  'text/html' () {
-    res.send('<p>hey</p>')
-  },
-
-  'application/json' () {
-    res.send({ message: 'hey' })
-  },
-
-  default () {
-    // log the request and respond with 406
-    res.status(406).send('Not Acceptable')
-  }
-})
-```
-
-In addition to canonicalized MIME types, you may also use extension names mapped
-to these types for a slightly less verbose implementation:
-
-```js
-res.format({
-  text () {
-    res.send('hey')
-  },
-
-  html () {
-    res.send('<p>hey</p>')
-  },
-
-  json () {
-    res.send({ message: 'hey' })
-  }
-})
-```
diff --git a/_includes/api/en/5x/res-get.md b/_includes/api/en/5x/res-get.md
deleted file mode 100644
index 8aefb205ef..0000000000
--- a/_includes/api/en/5x/res-get.md
+++ /dev/null
@@ -1,9 +0,0 @@
-<h3 id='res.get'>res.get(field)</h3>
-
-Returns the HTTP response header specified by `field`.
-The match is case-insensitive.
-
-```js
-res.get('Content-Type')
-// => "text/plain"
-```
diff --git a/_includes/api/en/5x/res-headersSent.md b/_includes/api/en/5x/res-headersSent.md
deleted file mode 100644
index 1bbe06d1b3..0000000000
--- a/_includes/api/en/5x/res-headersSent.md
+++ /dev/null
@@ -1,11 +0,0 @@
-<h3 id='res.headersSent'>res.headersSent</h3>
-
-Boolean property that indicates if the app sent HTTP headers for the response.
-
-```js
-app.get('/', (req, res) => {
-  console.log(res.headersSent) // false
-  res.send('OK')
-  console.log(res.headersSent) // true
-})
-```
diff --git a/_includes/api/en/5x/res-json.md b/_includes/api/en/5x/res-json.md
deleted file mode 100644
index 8e699a7ed5..0000000000
--- a/_includes/api/en/5x/res-json.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='res.json'>res.json([body])</h3>
-
-Sends a JSON response. This method sends a response (with the correct content-type) that is the parameter converted to a 
-JSON string using [JSON.stringify()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify).
-
-The parameter can be any JSON type, including object, array, string, Boolean, number, or null,
-and you can also use it to convert other values to JSON.
-
-```js
-res.json(null)
-res.json({ user: 'tobi' })
-res.status(500).json({ error: 'message' })
-```
diff --git a/_includes/api/en/5x/res-jsonp.md b/_includes/api/en/5x/res-jsonp.md
deleted file mode 100644
index edb7e45466..0000000000
--- a/_includes/api/en/5x/res-jsonp.md
+++ /dev/null
@@ -1,32 +0,0 @@
-<h3 id='res.jsonp'>res.jsonp([body])</h3>
-
-Sends a JSON response with JSONP support. This method is identical to `res.json()`,
-except that it opts-in to JSONP callback support.
-
-```js
-res.jsonp(null)
-// => callback(null)
-
-res.jsonp({ user: 'tobi' })
-// => callback({ "user": "tobi" })
-
-res.status(500).jsonp({ error: 'message' })
-// => callback({ "error": "message" })
-```
-
-By default, the JSONP callback name is simply `callback`. Override this with the
-<a href="#app.settings.table">jsonp callback name</a> setting.
-
-The following are some examples of JSONP responses using the same code:
-
-```js
-// ?callback=foo
-res.jsonp({ user: 'tobi' })
-// => foo({ "user": "tobi" })
-
-app.set('jsonp callback name', 'cb')
-
-// ?cb=foo
-res.status(500).jsonp({ error: 'message' })
-// => foo({ "error": "message" })
-```
diff --git a/_includes/api/en/5x/res-links.md b/_includes/api/en/5x/res-links.md
deleted file mode 100644
index 17164155d4..0000000000
--- a/_includes/api/en/5x/res-links.md
+++ /dev/null
@@ -1,20 +0,0 @@
-<h3 id='res.links'>res.links(links)</h3>
-
-Joins the `links` provided as properties of the parameter to populate the response's
-`Link` HTTP header field.
-
-For example, the following call:
-
-```js
-res.links({
-  next: 'http://api.example.com/users?page=2',
-  last: 'http://api.example.com/users?page=5'
-})
-```
-
-Yields the following results:
-
-```
-Link: <http://api.example.com/users?page=2>; rel="next",
-      <http://api.example.com/users?page=5>; rel="last"
-```
diff --git a/_includes/api/en/5x/res-locals.md b/_includes/api/en/5x/res-locals.md
deleted file mode 100644
index 304900033d..0000000000
--- a/_includes/api/en/5x/res-locals.md
+++ /dev/null
@@ -1,28 +0,0 @@
-<h3 id='res.locals'>res.locals</h3>
-
-Use this property to set variables accessible in templates rendered with [res.render](#res.render).
-The variables set on `res.locals` are available within a single request-response cycle, and will not
-be shared between requests.
-
-<div class="doc-box doc-warn" markdown="1">
-The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations.
-</div>
-
-In order to keep local variables for use in template rendering between requests, use
-[app.locals](#app.locals) instead.
-
-This property is useful for exposing request-level information such as the request path name,
-authenticated user, user settings, and so on to templates rendered within the application.
-
-```js
-app.use((req, res, next) => {
-  // Make `user` and `authenticated` available in templates
-  res.locals.user = req.user
-  res.locals.authenticated = !req.user.anonymous
-  next()
-})
-```
diff --git a/_includes/api/en/5x/res-location.md b/_includes/api/en/5x/res-location.md
deleted file mode 100644
index 637404bd4f..0000000000
--- a/_includes/api/en/5x/res-location.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.location'>res.location(path)</h3>
-
-Sets the response `Location` HTTP header to the specified `path` parameter.
-
-```js
-res.location('/foo/bar')
-res.location('http://example.com')
-```
-
-<div class='doc-box doc-warn' markdown="1">
-After encoding the URL, if not encoded already, Express passes the specified URL to the browser in the `Location` header,
-without any validation.
-
-Browsers take the responsibility of deriving the intended URL from the current URL
-or the referring URL, and the URL specified in the `Location` header; and redirect the user accordingly.
-</div>
diff --git a/_includes/api/en/5x/res-redirect.md b/_includes/api/en/5x/res-redirect.md
deleted file mode 100644
index 8fbf9a88df..0000000000
--- a/_includes/api/en/5x/res-redirect.md
+++ /dev/null
@@ -1,49 +0,0 @@
-<h3 id='res.redirect'>res.redirect([status,] path)</h3>
-
-Redirects to the URL derived from the specified `path`, with specified `status`, a positive integer
-that corresponds to an [HTTP status code](https://www.rfc-editor.org/rfc/rfc9110.html#name-status-codes).
-If not specified, `status` defaults to `302 "Found"`.
-
-```js
-res.redirect('/foo/bar')
-res.redirect('http://example.com')
-res.redirect(301, 'http://example.com')
-res.redirect('../login')
-```
-Redirects can be a fully-qualified URL for redirecting to a different site:
-
-```js
-res.redirect('http://google.com')
-```
-Redirects can be relative to the root of the host name. For example, if the
-application is on `http://example.com/admin/post/new`, the following
-would redirect to the URL `http://example.com/admin`:
-
-```js
-res.redirect('/admin')
-```
-
-Redirects can be relative to the current URL. For example,
-from `http://example.com/blog/admin/` (notice the trailing slash), the following
-would redirect to the URL `http://example.com/blog/admin/post/new`.
-
-```js
-res.redirect('post/new')
-```
-
-Redirecting to `post/new` from `http://example.com/blog/admin` (no trailing slash),
-will redirect to `http://example.com/blog/post/new`.
-
-If you found the above behavior confusing, think of path segments as directories
-(with trailing slashes) and files, it will start to make sense.
-
-Path-relative redirects are also possible. If you were on
-`http://example.com/admin/post/new`, the following would redirect to
-`http://example.com/admin/post`:
-
-```js
-res.redirect('..')
-```
-
-See also [Security best practices: Prevent open redirect 
-vulnerabilities](http://expressjs.com/en/advanced/best-practice-security.html#prevent-open-redirects). 
\ No newline at end of file
diff --git a/_includes/api/en/5x/res-render.md b/_includes/api/en/5x/res-render.md
deleted file mode 100644
index 8fa563fe71..0000000000
--- a/_includes/api/en/5x/res-render.md
+++ /dev/null
@@ -1,37 +0,0 @@
-<h3 id='res.render'>res.render(view [, locals] [, callback])</h3>
-
-Renders a `view` and sends the rendered HTML string to the client.
-Optional parameters:
-
-- `locals`, an object whose properties define local variables for the view.
-- `callback`, a callback function. If provided, the method returns both the possible error and rendered string, but does not perform an automated response. When an error occurs, the method invokes `next(err)` internally.
-
-The `view` argument is a string that is the file path of the view file to render. This can be an absolute path, or a path relative to the `views` setting. If the path does not contain a file extension, then the `view engine` setting determines the file extension. If the path does contain a file extension, then Express will load the module for the specified template engine (via `require()`) and render it using the loaded module's `__express` function.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-{% include admonitions/warning.html content="The `view` argument performs file system operations like reading a file from disk and evaluating Node.js modules, and as so for security reasons should not contain input from the end-user." %}
-
-{% include admonitions/warning.html content="The `locals` object is used by view engines to render a response. The object
-keys may be particularly sensitive and should not contain user-controlled
-input, as it may affect the operation of the view engine or provide a path to
-cross-site scripting. Consult the documentation for the used view engine for
-additional considerations." %}
-
-{% include admonitions/caution.html content="The local variable `cache` enables view caching. Set it to `true`,
-to cache the view during development; view caching is enabled in production by default." %}
-
-```js
-// send the rendered view to the client
-res.render('index')
-
-// if a callback is specified, the rendered HTML string has to be sent explicitly
-res.render('index', (err, html) => {
-  res.send(html)
-})
-
-// pass a local variable to the view
-res.render('user', { name: 'Tobi' }, (err, html) => {
-  // ...
-})
-```
diff --git a/_includes/api/en/5x/res-req.md b/_includes/api/en/5x/res-req.md
deleted file mode 100644
index 8763653d9f..0000000000
--- a/_includes/api/en/5x/res-req.md
+++ /dev/null
@@ -1,4 +0,0 @@
-<h3 id='res.req'>res.req</h3>
-
-This property holds a reference to the <a href="#req">request object</a>
-that relates to this response object.
diff --git a/_includes/api/en/5x/res-send.md b/_includes/api/en/5x/res-send.md
deleted file mode 100644
index ba46abd399..0000000000
--- a/_includes/api/en/5x/res-send.md
+++ /dev/null
@@ -1,39 +0,0 @@
-<h3 id='res.send'>res.send([body])</h3>
-
-Sends the HTTP response.
-
-The `body` parameter can be a `Buffer` object, a `String`, an object, `Boolean`, or an `Array`.
-For example:
-
-```js
-res.send(Buffer.from('whoop'))
-res.send({ some: 'json' })
-res.send('<p>some html</p>')
-res.status(404).send('Sorry, we cannot find that!')
-res.status(500).send({ error: 'something blew up' })
-```
-
-This method performs many useful tasks for simple non-streaming responses:
-For example, it automatically assigns the `Content-Length` HTTP response header field 
-and provides automatic HEAD and HTTP cache freshness support.
-
-When the parameter is a `Buffer` object, the method sets the `Content-Type`
-response header field to "application/octet-stream", unless previously defined as shown below:
-
-```js
-res.set('Content-Type', 'text/html')
-res.send(Buffer.from('<p>some html</p>'))
-```
-
-When the parameter is a `String`, the method sets the `Content-Type` to "text/html":
-
-```js
-res.send('<p>some html</p>')
-```
-
-When the parameter is an `Array` or `Object`, Express responds with the JSON representation:
-
-```js
-res.send({ user: 'tobi' })
-res.send([1, 2, 3])
-```
diff --git a/_includes/api/en/5x/res-sendFile.md b/_includes/api/en/5x/res-sendFile.md
deleted file mode 100644
index e415a21dc6..0000000000
--- a/_includes/api/en/5x/res-sendFile.md
+++ /dev/null
@@ -1,84 +0,0 @@
-<h3 id='res.sendFile'>res.sendFile(path [, options] [, fn])</h3>
-
-<div class="doc-box doc-info" markdown="1">
-`res.sendFile()` is supported by Express v4.8.0 onwards.
-</div>
-
-Transfers the file at the given `path`. Sets the `Content-Type` response HTTP header field
-based on the filename's extension. Unless the `root` option is set in
-the options object, `path` must be an absolute path to the file.
-
-<div class="doc-box doc-warn" markdown="1">
-This API provides access to data on the running file system. Ensure that either (a) the way in
-which the `path` argument was constructed into an absolute path is secure if it contains user
-input or (b) set the `root` option to the absolute path of a directory to contain access within.
-
-When the `root` option is provided, the `path` argument is allowed to be a relative path,
-including containing `..`. Express will validate that the relative path provided as `path` will
-resolve within the given `root` option.
-</div>
-
-The following table provides details on the `options` parameter.
-
-<div class="table-scroller" markdown="1">
-
-| Property        | Description                                     | Default     | Availability |
-|-----------------|-------------------------------------------------|-------------|--------------|
-|`maxAge`         | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)| 0 |  |
-| `root`          | Root directory for relative filenames.|  |  |
-| `lastModified`  | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.| Enabled | 4.9.0+ |
-| `headers`       | Object containing HTTP headers to serve with the file.|  |  |
-| `dotfiles`      | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".| "ignore" | &nbsp; |
-| `acceptRanges`  | Enable or disable accepting ranged requests. | `true` | 4.14+ |
-| `cacheControl`  | Enable or disable setting `Cache-Control` response header.| `true` | 4.14+ |
-| `immutable`   | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false` | 4.16+ |
-
-</div>
-
-The method invokes the callback function `fn(err)` when the transfer is complete
-or when an error occurs. If the callback function is specified and an error occurs,
-the callback function must explicitly handle the response process either by
-ending the request-response cycle, or by passing control to the next route.
-
-Here is an example of using `res.sendFile` with all its arguments.
-
-```js
-app.get('/file/:name', (req, res, next) => {
-  const options = {
-    root: path.join(__dirname, 'public'),
-    dotfiles: 'deny',
-    headers: {
-      'x-timestamp': Date.now(),
-      'x-sent': true
-    }
-  }
-
-  const fileName = req.params.name
-  res.sendFile(fileName, options, (err) => {
-    if (err) {
-      next(err)
-    } else {
-      console.log('Sent:', fileName)
-    }
-  })
-})
-```
-
-The following example illustrates using
-`res.sendFile` to provide fine-grained support for serving files:
-
-```js
-app.get('/user/:uid/photos/:file', (req, res) => {
-  const uid = req.params.uid
-  const file = req.params.file
-
-  req.user.mayViewFilesFrom(uid, (yes) => {
-    if (yes) {
-      res.sendFile(`/uploads/${uid}/${file}`)
-    } else {
-      res.status(403).send("Sorry! You can't see that.")
-    }
-  })
-})
-```
-For more information, or if you have issues or concerns, see [send](https://github.com/pillarjs/send).
diff --git a/_includes/api/en/5x/res-sendStatus.md b/_includes/api/en/5x/res-sendStatus.md
deleted file mode 100644
index fe819bdfcf..0000000000
--- a/_includes/api/en/5x/res-sendStatus.md
+++ /dev/null
@@ -1,15 +0,0 @@
-<h3 id='res.sendStatus'>res.sendStatus(statusCode)</h3>
-
-Sets the response HTTP status code to `statusCode` and sends the registered status message as the text response body. If an unknown status code is specified, the response body will just be the code number.
-
-```js
-res.sendStatus(404)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Some versions of Node.js will throw when `res.statusCode` is set to an
-invalid HTTP status code (outside of the range `100` to `599`). Consult
-the HTTP server documentation for the Node.js version being used.
-</div>
-
-[More about HTTP Status Codes](http://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
diff --git a/_includes/api/en/5x/res-set.md b/_includes/api/en/5x/res-set.md
deleted file mode 100644
index b91698d4b1..0000000000
--- a/_includes/api/en/5x/res-set.md
+++ /dev/null
@@ -1,16 +0,0 @@
-<h3 id='res.set'>res.set(field [, value])</h3>
-
-Sets the response's HTTP header `field` to `value`.
-To set multiple fields at once, pass an object as the parameter.
-
-```js
-res.set('Content-Type', 'text/plain')
-
-res.set({
-  'Content-Type': 'text/plain',
-  'Content-Length': '123',
-  ETag: '12345'
-})
-```
-
-Aliased as `res.header(field [, value])`.
diff --git a/_includes/api/en/5x/res-status.md b/_includes/api/en/5x/res-status.md
deleted file mode 100644
index 9cb9d44e94..0000000000
--- a/_includes/api/en/5x/res-status.md
+++ /dev/null
@@ -1,10 +0,0 @@
-<h3 id='res.status'>res.status(code)</h3>
-
-Sets the HTTP status for the response.
-It is a chainable alias of Node's [response.statusCode](http://nodejs.org/api/http.html#http_response_statuscode).
-
-```js
-res.status(403).end()
-res.status(400).send('Bad Request')
-res.status(404).sendFile('/absolute/path/to/404.png')
-```
diff --git a/_includes/api/en/5x/res-type.md b/_includes/api/en/5x/res-type.md
deleted file mode 100644
index f1aa7de27c..0000000000
--- a/_includes/api/en/5x/res-type.md
+++ /dev/null
@@ -1,13 +0,0 @@
-<h3 id='res.type'>res.type(type)</h3>
-
-Sets the `Content-Type` HTTP header to the MIME type as determined by the specified `type`. If `type` contains the "/" character, then it sets the `Content-Type` to the exact value of `type`, otherwise it is assumed to be a file extension and the MIME type is looked up using the `contentType()` method of the `mime-types` package.
-
-```js
-res.type('.html') // => 'text/html'
-res.type('html') // => 'text/html'
-res.type('json') // => 'application/json'
-res.type('application/json') // => 'application/json'
-res.type('png') // => image/png:
-```
-
-Aliased as `res.contentType(type)`.
diff --git a/_includes/api/en/5x/res-vary.md b/_includes/api/en/5x/res-vary.md
deleted file mode 100644
index 956aab25ae..0000000000
--- a/_includes/api/en/5x/res-vary.md
+++ /dev/null
@@ -1,7 +0,0 @@
-<h3 id='res.vary'>res.vary(field)</h3>
-
-Adds the field to the `Vary` response header, if it is not there already.
-
-```js
-res.vary('User-Agent').render('docs')
-```
diff --git a/_includes/api/en/5x/res.md b/_includes/api/en/5x/res.md
deleted file mode 100644
index a26c2c7d14..0000000000
--- a/_includes/api/en/5x/res.md
+++ /dev/null
@@ -1,130 +0,0 @@
-<h2 id="res">Response</h2>
-
-The `res` object represents the HTTP response that an Express app sends when it gets an HTTP request.
-
-In this documentation and by convention,
-the object is always referred to as `res` (and the HTTP request is `req`) but its actual name is determined
-by the parameters to the callback function in which you're working.
-
-For example:
-
-```js
-app.get('/user/:id', (req, res) => {
-  res.send(`user ${req.params.id}`)
-})
-```
-
-But you could just as well have:
-
-```js
-app.get('/user/:id', (request, response) => {
-  response.send(`user ${request.params.id}`)
-})
-```
-
-The `res` object is an enhanced version of Node's own response object
-and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
-
-<h3 id='res.properties'>Properties</h3>
-
-<section markdown="1">
-  {% include api/en/5x/res-app.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-headersSent.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-locals.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-req.md %}
-</section>
-
-<h3 id='res.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/5x/res-append.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-attachment.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-cookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-clearCookie.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-download.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-end.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-format.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-get.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-json.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-jsonp.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-links.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-location.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-redirect.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-render.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-send.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-sendFile.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-sendStatus.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-set.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-status.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-type.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/res-vary.md %}
-</section>
diff --git a/_includes/api/en/5x/router-METHOD.md b/_includes/api/en/5x/router-METHOD.md
deleted file mode 100644
index 8f42424566..0000000000
--- a/_includes/api/en/5x/router-METHOD.md
+++ /dev/null
@@ -1,66 +0,0 @@
-<h3 id='router.METHOD'>router.METHOD(path, [callback, ...] callback)</h3>
-
-The `router.METHOD()` methods provide the routing functionality in Express,
-where METHOD is one of the HTTP methods, such as GET, PUT, POST, and so on,
-in lowercase. Thus, the actual methods are `router.get()`, `router.post()`,
-`router.put()`, and so on.
-
-<div class="doc-box doc-info" markdown="1">
-  The `router.get()` function is automatically called for the HTTP `HEAD` method in
-  addition to the `GET` method if `router.head()` was not called for the
-  path before `router.get()`.
-</div>
-
-You can provide multiple callbacks, and all are treated equally, and behave just
-like middleware, except that these callbacks may invoke `next('route')`
-to bypass the remaining route callback(s). You can use this mechanism to perform
-pre-conditions on a route then pass control to subsequent routes when there is no
-reason to proceed with the route matched.
-
-The following snippet illustrates the most simple route definition possible.
-Express translates the path strings to regular expressions, used internally
-to match incoming requests. Query strings are _not_ considered when performing
-these matches, for example "GET /" would match the following route, as would
-"GET /?name=tobi".
-
-```js
-router.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-You can also use regular expressions&mdash;useful if you have very specific
-constraints, for example the following would match "GET /commits/71dbb9c" as well
-as "GET /commits/71dbb9c..4c084f9".
-
-```js
-router.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, (req, res) => {
-  const from = req.params[0]
-  const to = req.params[1] || 'HEAD'
-  res.send(`commit range ${from}..${to}`)
-})
-```
-
-You can use `next` primitive to implement a flow control between different
-middleware functions, based on a specific program state. Invoking `next` with
-the string `'router'` will cause all the remaining route callbacks on that router
-to be bypassed.
-
-The following example illustrates `next('router')` usage.
-
-```js
-function fn (req, res, next) {
-  console.log('I come here')
-  next('router')
-}
-router.get('/foo', fn, (req, res, next) => {
-  console.log('I dont come here')
-})
-router.get('/foo', (req, res, next) => {
-  console.log('I dont come here')
-})
-app.get('/foo', (req, res) => {
-  console.log(' I come here too')
-  res.end('good')
-})
-```
diff --git a/_includes/api/en/5x/router-Router.md b/_includes/api/en/5x/router-Router.md
deleted file mode 100644
index 664ffb34c2..0000000000
--- a/_includes/api/en/5x/router-Router.md
+++ /dev/null
@@ -1,2 +0,0 @@
-<h3 id='router'>Router([options])</h3>
-
diff --git a/_includes/api/en/5x/router-all.md b/_includes/api/en/5x/router-all.md
deleted file mode 100644
index 91b2d2ec19..0000000000
--- a/_includes/api/en/5x/router-all.md
+++ /dev/null
@@ -1,31 +0,0 @@
-<h3 id='router.all'>router.all(path, [callback, ...] callback)</h3>
-
-This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs).
-
-This method is extremely useful for
-mapping "global" logic for specific path prefixes or arbitrary matches.
-For example, if you placed the following route at the top of all other
-route definitions, it would require that all routes from that point on
-would require authentication, and automatically load a user. Keep in mind
-that these callbacks do not have to act as end points; `loadUser`
-can perform a task, then call `next()` to continue matching subsequent
-routes.
-
-```js
-router.all('{*splat}', requireAuthentication, loadUser)
-```
-
-Or the equivalent:
-
-```js
-router.all('{*splat}', requireAuthentication)
-router.all('{*splat}', loadUser)
-```
-
-Another example of this is white-listed "global" functionality. Here,
-the example is much like before, but it only restricts paths prefixed with
-"/api":
-
-```js
-router.all('/api/{*splat}', requireAuthentication)
-```
diff --git a/_includes/api/en/5x/router-param.md b/_includes/api/en/5x/router-param.md
deleted file mode 100644
index 9ef80f6abf..0000000000
--- a/_includes/api/en/5x/router-param.md
+++ /dev/null
@@ -1,62 +0,0 @@
-<h3 id='router.param'>router.param(name, callback)</h3>
-
-Adds callback triggers to route parameters, where `name` is the name of the parameter and `callback` is the callback function. Although `name` is technically optional, using this method without it is deprecated starting with Express v4.11.0 (see below).
-
-The parameters of the callback function are:
-
-- `req`, the request object.
-- `res`, the response object.
-- `next`, indicating the next middleware function.
-- The value of the `name` parameter.
-- The name of the parameter.
-
-<div class="doc-box doc-info" markdown="1">
-Unlike `app.param()`, `router.param()` does not accept an array of route parameters.
-</div>
-
-For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
-
-```js
-router.param('user', (req, res, next, id) => {
-  // try to get the user details from the User model and attach it to the request object
-  User.find(id, (err, user) => {
-    if (err) {
-      next(err)
-    } else if (user) {
-      req.user = user
-      next()
-    } else {
-      next(new Error('failed to load user'))
-    }
-  })
-})
-```
-
-Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `router` will be triggered only by route parameters defined on `router` routes.
-
-A param callback will be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
-
-```js
-router.param('id', (req, res, next, id) => {
-  console.log('CALLED ONLY ONCE')
-  next()
-})
-
-router.get('/user/:id', (req, res, next) => {
-  console.log('although this matches')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  console.log('and this matches too')
-  res.end()
-})
-```
-
-On `GET /user/42`, the following is printed:
-
-```
-CALLED ONLY ONCE
-although this matches
-and this matches too
-```
diff --git a/_includes/api/en/5x/router-route.md b/_includes/api/en/5x/router-route.md
deleted file mode 100644
index 30b5603ed9..0000000000
--- a/_includes/api/en/5x/router-route.md
+++ /dev/null
@@ -1,48 +0,0 @@
-<h3 id='router.route'>router.route(path)</h3>
-
-Returns an instance of a single route which you can then use to handle HTTP verbs
-with optional middleware. Use `router.route()` to avoid duplicate route naming and
-thus typing errors.
-
-Building on the `router.param()` example above, the following code shows how to use
-`router.route()` to specify various HTTP method handlers.
-
-```js
-const router = express.Router()
-
-router.param('user_id', (req, res, next, id) => {
-  // sample user, would actually fetch from DB, etc...
-  req.user = {
-    id,
-    name: 'TJ'
-  }
-  next()
-})
-
-router.route('/users/:user_id')
-  .all((req, res, next) => {
-  // runs for all HTTP verbs first
-  // think of it as route specific middleware!
-    next()
-  })
-  .get((req, res, next) => {
-    res.json(req.user)
-  })
-  .put((req, res, next) => {
-  // just an example of maybe updating the user
-    req.user.name = req.params.name
-    // save user ... etc
-    res.json(req.user)
-  })
-  .post((req, res, next) => {
-    next(new Error('not implemented'))
-  })
-  .delete((req, res, next) => {
-    next(new Error('not implemented'))
-  })
-```
-
-This approach re-uses the single `/users/:user_id` path and adds handlers for
-various HTTP methods.
-
-{% include admonitions/note.html content="When you use `router.route()`, middleware ordering is based on when the _route_ is created, not when method handlers are added to the route. For this purpose, you can consider method handlers to belong to the route to which they were added." %}
diff --git a/_includes/api/en/5x/router-use.md b/_includes/api/en/5x/router-use.md
deleted file mode 100644
index 1a0799af7f..0000000000
--- a/_includes/api/en/5x/router-use.md
+++ /dev/null
@@ -1,106 +0,0 @@
-<h3 id='router.use'>router.use([path], [function, ...] function)</h3>
-
-Uses the specified middleware function or functions, with optional mount path `path`, that defaults to "/".
-
-This method is similar to [app.use()](#app.use). A simple example and use case is described below.
-See [app.use()](#app.use) for more information.
-
-Middleware is like a plumbing pipe: requests start at the first middleware function defined
-and work their way "down" the middleware stack processing for each path they match.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// simple logger for this router's requests
-// all requests to this router will first hit this middleware
-router.use((req, res, next) => {
-  console.log('%s %s %s', req.method, req.url, req.path)
-  next()
-})
-
-// this will only be invoked if the path starts with /bar from the mount point
-router.use('/bar', (req, res, next) => {
-  // ... maybe some additional /bar logging ...
-  next()
-})
-
-// always invoked
-router.use((req, res, next) => {
-  res.send('Hello World')
-})
-
-app.use('/foo', router)
-
-app.listen(3000)
-```
-
-The "mount" path is stripped and is _not_ visible to the middleware function.
-The main effect of this feature is that a mounted middleware function may operate without
-code changes regardless of its "prefix" pathname.
-
-The order in which you define middleware with `router.use()` is very important.
-They are invoked sequentially, thus the order defines middleware precedence. For example,
-usually a logger is the very first middleware you would use, so that every request gets logged.
-
-```js
-const logger = require('morgan')
-
-router.use(logger())
-router.use(express.static(path.join(__dirname, 'public')))
-router.use((req, res) => {
-  res.send('Hello')
-})
-```
-
-Now suppose you wanted to ignore logging requests for static files, but to continue
-logging routes and middleware defined after `logger()`.  You would simply move the call to `express.static()` to the top,
-before adding the logger middleware:
-
-```js
-router.use(express.static(path.join(__dirname, 'public')))
-router.use(logger())
-router.use((req, res) => {
-  res.send('Hello')
-})
-```
-
-Another example is serving files from multiple directories,
-giving precedence to "./public" over the others:
-
-```js
-app.use(express.static(path.join(__dirname, 'public')))
-app.use(express.static(path.join(__dirname, 'files')))
-app.use(express.static(path.join(__dirname, 'uploads')))
-```
-
-The `router.use()` method also supports named parameters so that your mount points
-for other routers can benefit from preloading using named parameters.
-
-__NOTE__: Although these middleware functions are added via a particular router, _when_
-they run is defined by the path they are attached to (not the router). Therefore,
-middleware added via one router may run for other routers if its routes
-match. For example, this code shows two different routers mounted on the same path:
-
-```js
-const authRouter = express.Router()
-const openRouter = express.Router()
-
-authRouter.use(require('./authenticate').basic(usersdb))
-
-authRouter.get('/:user_id/edit', (req, res, next) => {
-  // ... Edit user UI ...
-})
-openRouter.get('/', (req, res, next) => {
-  // ... List users ...
-})
-openRouter.get('/:user_id', (req, res, next) => {
-  // ... View user ...
-})
-
-app.use('/users', authRouter)
-app.use('/users', openRouter)
-```
-
-Even though the authentication middleware was added via the `authRouter` it will run on the routes defined by the `openRouter` as well since both routers were mounted on `/users`. To avoid this behavior, use different paths for each router.
diff --git a/_includes/api/en/5x/router.md b/_includes/api/en/5x/router.md
deleted file mode 100644
index 26eb778ca9..0000000000
--- a/_includes/api/en/5x/router.md
+++ /dev/null
@@ -1,62 +0,0 @@
-<h2 id="router">Router</h2>
-
-<section markdown="1">
-A `router` object is an instance of middleware and routes. You can think of it
-as a "mini-application," capable only of performing middleware and routing
-functions. Every Express application has a built-in app router.
-
-A router behaves like middleware itself, so you can use it as an argument to
-[app.use()](#app.use) or as the argument to another router's [use()](#router.use) method.
-
-The top-level `express` object has a [Router()](#express.router) method that creates a new `router` object.
-
-Once you've created a router object, you can add middleware and HTTP method routes (such as `get`, `put`, `post`,
-and so on) to it just like an application. For example:
-
-```js
-// invoked for any requests passed to this router
-router.use((req, res, next) => {
-  // .. some logic here .. like any other middleware
-  next()
-})
-
-// will handle any request that ends in /events
-// depends on where the router is "use()'d"
-router.get('/events', (req, res, next) => {
-  // ..
-})
-```
-
-You can then use a router for a particular root URL in this way separating your routes into files or even mini-apps.
-
-```js
-// only requests to /calendar/* will be sent to our "router"
-app.use('/calendar', router)
-```
-
-Keep in mind that any middleware applied to a router will run for all requests on that router's path, even those that aren't part of the router.
-
-
-</section>
-
-<h3 id='router.methods'>Methods</h3>
-
-<section markdown="1">
-  {% include api/en/5x/router-all.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/router-METHOD.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/router-param.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/router-route.md %}
-</section>
-
-<section markdown="1">
-  {% include api/en/5x/router-use.md %}
-</section>
diff --git a/_includes/api/en/5x/routing-args.html b/_includes/api/en/5x/routing-args.html
deleted file mode 100644
index bd7e504d40..0000000000
--- a/_includes/api/en/5x/routing-args.html
+++ /dev/null
@@ -1,58 +0,0 @@
-<h4>Arguments</h4>
-
-<div class="table-scroller">
-    <table>
-        <thead>
-            <tr>
-            <th>Argument</th>
-            <th>Description</th>
-            <th>Default</th>
-            </tr>
-        </thead>
-        <tbody>
-            <tr>
-            <td><code>path</code></td>
-            <td>
-                The path for which the middleware function is invoked. It can be any of the following:
-                <ul>
-                <li>A string representing a path.</li>
-                <li>A path pattern.</li>
-                <li>A regular expression pattern to match paths.</li>
-                <li>An array containing any combination of the above.</li>
-                </ul>
-                For examples, see <a href="#path-examples">Path examples</a>.
-            </td>
-            <td><code>'/'</code> (root path)</td>
-            </tr>
-
-            <tr>
-            <td><code>callback</code></td>
-            <td>
-                One or more callback functions. Accepted formats:
-                <ul>
-                <li>A single middleware function.</li>
-                <li>Multiple middleware functions separated by commas.</li>
-                <li>An array of middleware functions.</li>
-                <li>A combination of the above.</li>
-                </ul>
-                <p>
-                You may provide multiple callbacks that behave like middleware. These can call
-                <code>next('route')</code> to skip remaining callbacks for the current route.
-                This is useful for conditional routing logic.
-                </p>
-                <p>
-                If a callback throws an error or returns a rejected promise, <code>next(err)</code> is invoked automatically.
-                </p>
-                <p>
-                Since both <a href="#router">router</a> and <a href="#application">app</a> implement the middleware interface,
-                they can also be used as callback middleware.
-                </p>
-                <p>
-                For examples, see <a href="#middleware-callback-function-examples">Middleware callback function examples</a>.
-                </p>
-            </td>
-            <td><em>None</em></td>
-            </tr>
-        </tbody>
-    </table>
-</div>
\ No newline at end of file
diff --git a/_includes/blog/authors.html b/_includes/blog/authors.html
deleted file mode 100644
index 5efdfd23a1..0000000000
--- a/_includes/blog/authors.html
+++ /dev/null
@@ -1,21 +0,0 @@
-{%- assign authors = include.authors -%}
-{% if authors %}
-  <div class="blog-authors">
-    By
-    {% for author in authors %}
-
-      {%- assign label = author.github | prepend: '@' -%}
-      {%- if author.name -%}
-        {%- assign label = author.name -%}
-      {%- endif -%}
-
-      {% if label and author.github %}
-        <a href="https://github.com/{{author.github}}" rel="author" class="blog-author-link">
-          <img src="https://github.com/{{author.github}}.png?size=64" alt="" class="blog-author-avatar" />
-          <span class="blog-author-link-label">{{label}}</span></a>{% unless forloop.last %}, {% endunless %}
-      {% elsif label %}
-        {{label}}{% unless forloop.last %}, {% endunless %}
-      {% endif %}
-    {% endfor %}
-  </div>
-{% endif %}
diff --git a/_includes/blog/posts-menu.md b/_includes/blog/posts-menu.md
deleted file mode 100644
index b10a50d84b..0000000000
--- a/_includes/blog/posts-menu.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<button id="menu-toggle" title="show blogs list">All Blogs</button>
-<ul id="menu" class="blog-side-menu">
-  <li>
-    <ul id="side-menu" class="active">
-      {% for post in site.posts %}
-    <li>
-      <a href="{{post.url}}">{{ post.title }}</a>
-    </li>
-      {% endfor %}
-  </ul>
-  </li>
-</ul> 
diff --git a/_includes/bottom-navigation.html b/_includes/bottom-navigation.html
deleted file mode 100644
index 10ce134c1f..0000000000
--- a/_includes/bottom-navigation.html
+++ /dev/null
@@ -1,46 +0,0 @@
-{% assign current_menu = page.menu %}
-{% assign current_lang = page.lang %}
-
-{% if current_menu and current_lang %}
-
-  {% assign all_pages_in_menu = site.pages | where: "menu", current_menu %}
-  {% assign lang_specific_pages = all_pages_in_menu | where: "lang", current_lang %}
-  
-  {% assign sorted_pages = lang_specific_pages | sort: "order" %}
-
-  {% for doc in sorted_pages %}
-    {% if doc.path == page.path %}
-      {% assign current_index = forloop.index0 %}
-      {% break %}
-    {% endif %}
-  {% endfor %}
-
-  {% if current_index != nil %}
-    {% assign prev_index = current_index | minus: 1 %}
-    {% if prev_index >= 0 %}
-      {% assign prev_page = sorted_pages[prev_index] %}
-    {% endif %}
-
-    {% assign next_index = current_index | plus: 1 %}
-    {% if next_index < sorted_pages.size %}
-      {% assign next_page = sorted_pages[next_index] %}
-    {% endif %}
-  {% endif %}
-
-  {% if prev_page or next_page %}
-    <nav class="bottom-navigation" aria-label="Pagination">
-      {% if prev_page %}
-        <a href="{{ prev_page.url | relative_url }}" class="bottom-nav-prev">
-          Previous: {{ prev_page.title }}
-        </a>
-      {% endif %}
-
-      {% if next_page %}
-        <a href="{{ next_page.url | relative_url }}" class="bottom-nav-next">
-          Next: {{ next_page.title }}
-        </a>
-      {% endif %}
-    </nav>
-  {% endif %}
-
-{% endif %}
\ No newline at end of file
diff --git a/_includes/changelog/menu.md b/_includes/changelog/menu.md
deleted file mode 100644
index b3bdb5d17b..0000000000
--- a/_includes/changelog/menu.md
+++ /dev/null
@@ -1,3 +0,0 @@
-- [5.x](#5.x)
-- [4.x](#4.x)
-{: #side-menu .active}
\ No newline at end of file
diff --git a/_includes/community-caveat.html b/_includes/community-caveat.html
deleted file mode 100644
index 92770e3bd1..0000000000
--- a/_includes/community-caveat.html
+++ /dev/null
@@ -1,5 +0,0 @@
-{% capture alert_content %}
-{{ site.data[page.lang].general.community-caveat-alert }}
-{% endcapture %}
-
-{% include admonitions/warning.html content=alert_content %}
diff --git a/_includes/feed-entry.xml b/_includes/feed-entry.xml
deleted file mode 100644
index 00af8b9350..0000000000
--- a/_includes/feed-entry.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-{%- assign entry = include.entry -%}
-<entry>
-  <id>{{ site.url }}{{ entry.url }}</id>
-  <link href="{{ site.url }}{{ entry.url }}" rel="alternate" type="text/html" />
-  <title type="text">{{ entry.title }}</title>
-  {%- for author in entry.authors %}
-    <author>
-        {% if author.name %}
-          <name>{{ author.name }}</name>
-        {% elsif author.github %}
-          <name>@{{ author.github }}</name>
-        {% endif %}
-        {% if author.github %}
-          <uri>https://github.com/{{ author.github }}</uri>
-        {% endif %}
-    </author>
-  {%- endfor %}
-  <published>{{ entry.date | date_to_xmlschema }}</published>
-  <updated>{{ entry.last_modified_at | default: post.date | date_to_xmlschema }}</updated>
-  {%- for tag in post.tags %}
-  <category term="{{ tag | xml_escape }}" />
-  {%- endfor %}
-  <content type="html"><![CDATA[ <a href="{{ site.url }}{{ entry.url }}">Read {{ entry.title }}</a> ]]></content>
-</entry>
diff --git a/_includes/footer.html b/_includes/footer.html
deleted file mode 100644
index 2c9aff8dd4..0000000000
--- a/_includes/footer.html
+++ /dev/null
@@ -1,74 +0,0 @@
-<a id="top" href="#" role="button" aria-label="go to top">{% include icons/arrow.svg %}</a>
-
-<footer>
-  <section id="footer-content">
-    <div id="footer-copyright">
-      <a href="https://openjsf.org/" class="openjs-logo" title="OpenJS Foundation">
-         {% include icons/openjs_foundation-logo-horizontal-white.svg %}
-      </a>
-      <p id="footer-trademark-legal">
-        {{ site.data[page.lang].footer.trademark_legal | default: site.data.en.footer.trademark_legal }}
-      </p>
-      <div id="footer-policy">
-        <a href="https://terms-of-use.openjsf.org">
-          {{ site.data[page.lang].footer.terms_of_use }}
-        </a>
-        <a href="https://privacy-policy.openjsf.org">
-          {{ site.data[page.lang].footer.privacy_policy }}
-        </a>
-        <a id="coc" href="https://github.com/expressjs/.github/blob/HEAD/CODE_OF_CONDUCT.md">
-          {{ site.data[page.lang].footer.coc }}
-        </a>
-        <a href="https://trademark-policy.openjsf.org">
-          {{ site.data[page.lang].footer.trademark_policy }}
-        </a>
-        <a id="security" href="https://github.com/expressjs/express/security/policy">
-          {{ site.data[page.lang].footer.security_policy }}
-        </a>
-      </div>
-    </div>
-    <div id="footer-links">
-      <div class="footer-social">
-        <div>
-          <a href="https://github.com/expressjs/express" aria-label="Go to the repository on GitHub">
-            {% include icons/github.svg %}
-          </a>
-        </div>
-        <div>
-          <a href="https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g"
-            aria-label="Go to the repository on Youtube">
-            {% include icons/youtube.svg %}</a>
-        </div>
-        <div>
-          <a href="https://x.com/UseExpressJS" aria-label="Go to the X account">
-              {% include icons/X.svg %}
-          </a>
-        </div>
-        <div>
-          <a href="https://openjs-foundation.slack.com/archives/C02QB1731FH"
-            aria-label="Join Slack group">
-            {% include icons/slack.svg %}</a>
-        </div>
-        <div>
-          <a href="https://opencollective.com/express" aria-label="Go to Open Collective">{% include
-            icons/opencollective.svg %}</a>
-        </div>
-        <div>
-          <a href="https://bsky.app/profile/expressjs.bsky.social" aria-label="Go to the Bluesky">{%
-            include icons/bluesky.svg %}</a>
-        </div>
-      </div>
-      <a href="https://www.netlify.com">
-          <img src="https://www.netlify.com/v3/img/components/netlify-color-accent.svg" alt="Preview Deploys by Netlify"
-            width="80" />
-      </a>
-    </div>
-  </section>
-</footer>
-
-<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js" onload="docsearch({
-  apiKey: '{{ site.data.docsearch.apiKey }}',
-  indexName: '{{ site.data.docsearch.indexName }}',
-  inputSelector: '#q',
-  algoliaOptions: { 'facetFilters': ['lang:{{ page.lang }}'] }
-})" async></script>
diff --git a/_includes/github-edit-btn.html b/_includes/github-edit-btn.html
deleted file mode 100644
index 3c90f515b8..0000000000
--- a/_includes/github-edit-btn.html
+++ /dev/null
@@ -1,9 +0,0 @@
-<a role="button" class="edit-github-btn" 
-    href="{% if page.layout == 'api' %} 
-            {{ site.github.repository_url }}/tree/gh-pages/_includes/api/en/{{page.version}}
-          {% else %}
-            {{ site.github.repository_url }}/edit/gh-pages/{{ page.path }}
-          {% endif %}">      
-    {% include icons/github.svg %}
-    Edit this page
-</a>
\ No newline at end of file
diff --git a/_includes/head.html b/_includes/head.html
deleted file mode 100644
index d94b9f0f10..0000000000
--- a/_includes/head.html
+++ /dev/null
@@ -1,73 +0,0 @@
-<head>
-    <title>{{ page.title }}</title>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <link 
-        rel="preload" 
-        href="/fonts/open-sans/woff2/open-sans-latin-wght-normal.woff2"
-        as="font" 
-        type="font/woff2" 
-        crossorigin 
-    />
-    <link 
-        rel="preload" 
-        href="/fonts/open-sans/woff2/open-sans-latin-wght-italic.woff2" 
-        as="font" 
-        type="font/woff2" 
-        crossorigin 
-    />
-    <link
-        href="/fonts/open-sans/woff/OpenSans.woff"
-        as="font"
-        type="font/woff"
-        crossorigin
-    />
-    <link
-        href="/fonts/open-sans/woff/OpenSans-Italic.woff"
-        as="font"
-        type="font/woff"
-        crossorigin
-    />
-    <link rel="stylesheet" href="/fonts/open-sans/fonts.css" />
-    <link rel="icon" type="image/png" href="/images/favicon.png" />
-    <script data-cfasync="false" src="/js/theme.js"></script>
-    <link rel="stylesheet" href="/css/variables.css?_={{ site.time | date: '%s' }}">
-    <link rel="stylesheet" href="/css/themes/dark-theme.css?_={{ site.time | date: '%s' }}">
-    <link rel="stylesheet" href="/css/style.css?_={{ site.time | date: '%s' }}">
-    <link rel="stylesheet" href="/css/sintax.css?_={{ site.time | date: '%s' }}">
-    <link rel="stylesheet" href="/css/langs/{{ page.lang }}.css">
-    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-    <meta name="description" content="{{page.description}}">
-    <meta property="og:url" content="https://expressjs.com{{page.url}}">
-    {% if page.authors %}
-        <meta property="og:type" content="article">
-        {%- for author in page.authors %}
-            <meta property="og:article:author" content="{{author.name}}">
-        {%- endfor %}
-    {% else %}
-    <meta property="og:type" content="website">
-    {% endif %}
-    <meta name="title" property="og:title" content="{{page.title}}">
-    <meta property="og:description" content="{{page.description}}">
-    {% if page.image %}
-    <meta property="og:image" content="{{page.image}}">
-    {% else %}
-    <meta property="og:image" content="https://expressjs.com/images/og.png">
-    {% endif %}
-    <meta name="twitter:card" content="summary_large_image">
-    <meta property="twitter:domain" content="expressjs.com">
-    <meta property="twitter:url" content="https://expressjs.com{{page.url}}">
-    <meta name="twitter:title" content="{{page.title}}">
-    <meta name="twitter:description" content="{{page.description}}">
-    {% if page contains "image" %}
-    <meta property="twitter:image" content="{{ page.image }}">
-    {% else %}
-    <meta property="twitter:image" content="https://expressjs.com/images/og.png">
-    {% endif %}
-    <script data-cfasync="false" defer src="/js/app.js"></script>
-    <script data-cfasync="false" defer src="/js/menu.js"></script>
-    <script data-cfasync="false" defer src="/js/copycode.js"></script>
-    <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
-    <link rel="alternate" type="application/atom+xml" href="/feed.xml" title="Express Blog" />
-    <link rel="alternate" type="application/atom+xml" href="/vulnerabilities.xml" title="Express Vulnerabilities" />
-</head>
\ No newline at end of file
diff --git a/_includes/header.html b/_includes/header.html
deleted file mode 100644
index 9c6adc9987..0000000000
--- a/_includes/header.html
+++ /dev/null
@@ -1,251 +0,0 @@
-<header>
-  <div id="mobile-menu">
-    <div id="nav-button" class="header-btn">
-      {% include icons/hamburger.svg %}
-    </div>
-  </div>
-  <div class="logo-container">
-    <a href="/" title="Go to homepage" aria-label="Go to homepage">
-      {% include icons/express-logo.svg %}
-    </a>
-  </div>
-  <nav id="navbar" aria-label="primary">
-    <input id="q" placeholder="🔎 search">
-    <ul id="navmenu">
-      <li id="getting-started-menu" class="submenu">
-        <a href="/{{ page.lang }}/starter/installing.html" {% if page.menu=='starter' %} class="active" {% endif%}>
-          {{ site.data[page.lang].menu.getting_started }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="/{{ page.lang }}/starter/installing.html">
-              {{ site.data[page.lang].menu.installing }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/hello-world.html">
-              {{ site.data[page.lang].menu.hello_world }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/generator.html">
-              {{ site.data[page.lang].menu.generator }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/basic-routing.html">
-              {{ site.data[page.lang].menu.basic_routing }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/static-files.html">
-              {{ site.data[page.lang].menu.static_files }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/examples.html">
-              {{ site.data[page.lang].menu.examples }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/starter/faq.html">
-              {{ site.data[page.lang].menu.faq }}
-            </a>
-          </li>
-        </ul>
-      </li>
-      <li id="guide-menu" class="submenu">
-        <a href="/{{ page.lang }}/guide/routing.html" {% if page.menu=='guide' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.guide }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="/{{ page.lang }}/guide/routing.html">
-              {{ site.data[page.lang].menu.routing }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/writing-middleware.html">
-              {{ site.data[page.lang].menu.writing_middleware }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/using-middleware.html">
-              {{ site.data[page.lang].menu.using_middleware }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/overriding-express-api.html">
-              {{ site.data[page.lang].menu.overriding_express_api }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/using-template-engines.html">
-              {{ site.data[page.lang].menu.using_template_engines }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/error-handling.html">
-              {{ site.data[page.lang].menu.error_handling }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/debugging.html">
-              {{ site.data[page.lang].menu.debugging }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/behind-proxies.html">
-              {{ site.data[page.lang].menu.behind_proxies }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/migrating-4.html">
-              {{ site.data[page.lang].menu.migrating_4 }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/migrating-5.html">
-              {{ site.data[page.lang].menu.migrating_5 }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/guide/database-integration.html">
-              {{ site.data[page.lang].menu.database_integration }}
-            </a>
-          </li>
-        </ul>
-      </li>
-      <li id="application-menu" class="submenu">
-        <a href="/{{ page.lang }}/5x/api.html" {% if page.menu=='api' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.api }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="/{{ page.lang }}/5x/api.html">
-              {{ site.data[page.lang].menu.5x }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/4x/api.html">
-              {{ site.data[page.lang].menu.4x }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/3x/api.html">
-              {{ site.data[page.lang].menu.3x }}
-            </a>
-          </li>
-          <li>
-            <a href="/2x/">
-              {{ site.data[page.lang].menu.2x }}
-            </a>
-          </li>
-        </ul>
-      </li>
-      <li id="advanced-topics-menu" class="submenu">
-        <a href="/{{ page.lang }}/advanced/developing-template-engines.html" {% if page.menu=='advanced' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.advanced }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="/{{ page.lang }}/advanced/developing-template-engines.html">
-              {{ site.data[page.lang].menu.developing_template_engines }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/advanced/security-updates.html">
-              {{ site.data[page.lang].menu.security_updates }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/advanced/best-practice-security.html">
-              {{ site.data[page.lang].menu.best_practice_security }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/advanced/best-practice-performance.html">
-              {{ site.data[page.lang].menu.best_practice_performance }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/advanced/healthcheck-graceful-shutdown.html">
-              {{ site.data[page.lang].menu.healthcheck_graceful_shutdown }}
-            </a>
-          </li>
-        </ul>
-      </li>
-      <li id="resources-menu" class="submenu">
-        <a href="/{{ page.lang }}/resources/community.html" {% if page.menu=='resources' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.resources }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="/{{ page.lang }}/resources/community.html">
-              {{ site.data[page.lang].menu.community }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/resources/glossary.html">
-              {{ site.data[page.lang].menu.glossary }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/resources/middleware.html">
-              {{ site.data[page.lang].menu.middleware }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/resources/utils.html">
-              {{ site.data[page.lang].menu.utils }}
-            </a>
-          </li>
-          <li>
-            <a href="/{{ page.lang }}/resources/contributing.html">
-              {{ site.data[page.lang].menu.contributing }}
-            </a>
-          </li>
-          <li>
-            <a href="https://github.com/expressjs/express/releases">
-              {{ site.data[page.lang].menu.changelog }}
-            </a>
-          </li>
-        </ul>
-      </li>
-      <li>
-        <a href="/{{ page.lang }}/support" id="support-menu" {% if page.menu=='support' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.support }}
-        </a>
-      </li>
-      <li id="blog-menu" class="submenu">
-        <a href="{{site.posts.first.url}}" {% if page.menu=='blog' %} class="active" {% endif %}>
-          {{ site.data[page.lang].menu.blog }}
-        </a>
-        <ul class="submenu-content">
-          <li>
-            <a href="{{site.posts.first.url}}">
-              {{ site.data[page.lang].menu.latest_post }}
-            </a>
-          </li>
-          <li>
-            <a href="/en/blog/posts.html">
-              {{ site.data[page.lang].menu.all_posts }}
-            </a>
-          </li>
-          <li>
-            <a href="/en/blog/write-post.html">
-              {{ site.data[page.lang].menu.write_post }}
-            </a>
-          </li>
-        </ul>
-      </li>
-    </ul>
-  </nav>
-  <div class="header-right">
-    <button id="theme-toggle" type="button" class="theme-btn" title="change theme" aria-label="Switch to dark mode">
-      <span id="icon-moon">{% include icons/moon.svg %}</span>
-      <span id="icon-sun">{% include icons/sun.svg %}</span>
-    </button>
-    {% include language-picker.html %}
-  </div>
-</header>
diff --git a/_includes/i18n-notice.html b/_includes/i18n-notice.html
deleted file mode 100644
index 6c5adf9e0b..0000000000
--- a/_includes/i18n-notice.html
+++ /dev/null
@@ -1,10 +0,0 @@
-{% assign notice = site.data[page.lang].general.i18n_notice %}
-{% assign lang_path = '/' | append: page.lang | append: '/' %}
-{% if notice %}
-  {% assign notice_link_text = site.data[page.lang].general.i18n_notice_link_text %}
-{% else %}
-  {% assign notice = site.data.en.general.i18n_notice %}
-  {% assign notice_link_text = site.data.en.general.i18n_notice_link_text %}
-{% endif %}
-<p>{{ notice }} <a href="{{ page.url | replace: lang_path, '/en/' }}">{{ notice_link_text}}</a>.</p>
-<div id="close-i18n-notice-box" title="Close" role="button" aria-label="Close notice" tabindex="0">✖</div>
\ No newline at end of file
diff --git a/_includes/icons/X.svg b/_includes/icons/X.svg
deleted file mode 100644
index cc93734c32..0000000000
--- a/_includes/icons/X.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" fill="currentColor" width="20" height="20" viewBox="0 0 1200 1227"><path d="M714.163 519.284 1160.89 0h-105.86L667.137 450.887 357.328 0H0l468.492 681.821L0 1226.37h105.866l409.625-476.152 327.181 476.152H1200L714.137 519.284h.026ZM569.165 687.828l-47.468-67.894-377.686-540.24h162.604l304.797 435.991 47.468 67.894 396.2 566.721H892.476L569.165 687.854v-.026Z"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/announcement.svg b/_includes/icons/announcement.svg
deleted file mode 100644
index 460c9522f8..0000000000
--- a/_includes/icons/announcement.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="none" stroke="currentColor" stroke-width="1.5" viewBox="0 0 24 24"><path stroke-linecap="round" stroke-linejoin="round" d="M10.34 15.84a24.07 24.07 0 0 0-2.09-.09H7.5a4.5 4.5 0 1 1 0-9h.75c.704 0 1.402-.03 2.09-.09m0 9.18c.253.962.584 1.892.985 2.783.247.55.06 1.21-.463 1.511l-.657.38c-.551.318-1.26.117-1.527-.461a20.845 20.845 0 0 1-1.44-4.282m3.102.069a18.03 18.03 0 0 1-.59-4.59c0-1.586.205-3.124.59-4.59m0 9.18a23.848 23.848 0 0 1 8.835 2.535M10.34 6.66a23.847 23.847 0 0 0 8.835-2.535m0 0A23.74 23.74 0 0 0 18.795 3m.38 1.125a23.91 23.91 0 0 1 1.014 5.395m-1.014 8.855c-.118.38-.245.754-.38 1.125m.38-1.125a23.91 23.91 0 0 0 1.014-5.395m0-3.46a2.249 2.249 0 0 1 0 3.46m0-3.46a24.347 24.347 0 0 1 0 3.46"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/arrow.svg b/_includes/icons/arrow.svg
deleted file mode 100644
index 3b44d7b7bb..0000000000
--- a/_includes/icons/arrow.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="10" height="6" fill="none" viewBox="0 0 1155 1000"><path fill="currentColor" d="m577.344 0 577.346 1000H0L577.344 0Z"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/bluesky.svg b/_includes/icons/bluesky.svg
deleted file mode 100644
index ac3613791d..0000000000
--- a/_includes/icons/bluesky.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 -3.268 64 68.414" height="20" width="20"><path fill="#0085ff" d="M13.873 3.805C21.21 9.332 29.103 20.537 32 26.55v15.882c0-.338-.13.044-.41.867-1.512 4.456-7.418 21.847-20.923 7.944-7.111-7.32-3.819-14.64 9.125-16.85-7.405 1.264-15.73-.825-18.014-9.015C1.12 23.022 0 8.51 0 6.55 0-3.268 8.579-.182 13.873 3.805zm36.254 0C42.79 9.332 34.897 20.537 32 26.55v15.882c0-.338.13.044.41.867 1.512 4.456 7.418 21.847 20.923 7.944 7.111-7.32 3.819-14.64-9.125-16.85 7.405 1.264 15.73-.825 18.014-9.015C62.88 23.022 64 8.51 64 6.55c0-9.818-8.578-6.732-13.873-2.745z"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/caution.svg b/_includes/icons/caution.svg
deleted file mode 100644
index c62c756faf..0000000000
--- a/_includes/icons/caution.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" fill="none" stroke="currentColor" stroke-width="1.5" height="24" width="24" viewBox="0 0 24 24"><path stroke-linecap="round" stroke-linejoin="round" d="M12 9v3.75m-9.303 3.376c-.866 1.5.217 3.374 1.948 3.374h14.71c1.73 0 2.813-1.874 1.948-3.374L13.949 3.378c-.866-1.5-3.032-1.5-3.898 0L2.697 16.126ZM12 15.75h.007v.008H12v-.008Z"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/express-logo.svg b/_includes/icons/express-logo.svg
deleted file mode 100644
index 16bcc7070a..0000000000
--- a/_includes/icons/express-logo.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" class="express-logo" viewBox="0 0 1120.322 250" width="90" height="30">
-  <path d="M347.47162 250V4.890464h13.29516v38.55596a50.415241 50.415241 0 0 0 4.33954-5.43506c11.10412-23.03785 34.52487-37.57744 60.09412-37.29026 30.31296-.90408 54.94623 10.31704 69.422 37.29026a119.86915 119.86915 0 0 1 2.89302 109.881816c-13.4866 30.22788-46.79895 45.25672-82.46189 39.73657a66.688515 66.688515 0 0 1-53.22317-35.12049v97.4801zm13.29516-158.403836 2.97812 28.781356c5.25425 32.75927 24.62263 52.11702 55.03132 55.75458a62.540425 62.540425 0 0 0 68.69874-39.73657c11.82737-28.18574 10.95521-60.094116-2.33995-87.620406a61.26409 61.26409 0 0 0-64.54001-35.66294 59.668671 59.668671 0 0 0-53.30827 44.07611 304.40595 304.40595 0 0 0-6.51995 34.39724zm420.10574 33.312346a71.687494 71.687494 0 0 1-70.06017 63.35941c-55.75458 2.80794-81.91945-34.21642-86.07817-76.94174a123.27271 123.27271 0 0 1 10.85948-67.890396 75.729222 75.729222 0 0 1 78.83497-42.26797 72.432023 72.432023 0 0 1 64.26348 55.12705 371.94535 371.94535 0 0 1 6.24341 40.73636H638.50796c-2.71221 38.736776 18.10269 69.879356 47.6073 77.388456 36.74782 9.04071 68.1563-6.88157 79.55823-41.82125 2.5314-8.96625 7.14748-10.23195 15.29475-7.68992zM638.4016 84.629504h130.97326c-.81898-41.26817-26.51586-71.26205-61.37045-71.60241-39.35367-.63816-67.89039 28.15383-69.60281 71.60241zm169.53986 41.183076h12.83781a51.478853 51.478853 0 0 0 30.22787 44.35265 79.026422 79.026422 0 0 0 68.61365-1.80814 30.844768 30.844768 0 0 0 18.10269-30.3236 27.973013 27.973013 0 0 0-18.82595-27.97301c-14.12477-5.25425-29.14298-8.14727-43.53366-12.763346a319.0838 319.0838 0 0 1-43.81021-16.01801c-23.18675-11.31684-24.62263-55.39295 1.62733-69.34755a92.427941 92.427941 0 0 1 88.34367-1.36142c16.95398 9.35979 26.32441 28.26019 23.53775 47.43712h-11.00839c0-.5318-.9998-.99979-.9998-1.54223-1.36142-35.09922-30.86604-46.07571-62.54043-42.99123-9.57251 1.06361-18.64513 3.95664-27.15403 8.23236a27.122123 27.122123 0 0 0-15.74147 27.15404 27.122123 27.122123 0 0 0 18.10269 25.5267c13.82697 5.07343 28.50482 8.32809 42.81041 12.306l34.56741 9.04071a40.842727 40.842727 0 0 1 28.05811 36.843536c2.76539 18.56004-6.70076 36.801-23.44203 45.25672-30.22787 17.10289-80.01558 12.58254-102.1919-9.04071-11.34875-11.41256-17.67724-26.9094-17.54961-42.99123zm306.10774-67.794666h-12.0401c0-1.62733-.6382-3.19084-.819-4.43526a39.353669 39.353669 0 0 0-32.0466-37.83271 79.026422 79.026422 0 0 0-50.7769 2.44631 30.844768 30.844768 0 0 0-22.35715 29.41953 28.398458 28.398458 0 0 0 21.71895 28.60054l55.0313 14.12478a153.05386 153.05386 0 0 1 17.5497 5.33934c17.5496 6.381666 29.462 22.676216 29.9938 41.300076a45.203539 45.203539 0 0 1-27.6539 42.96995 100.72412 100.72412 0 0 1-81.4621.81898 56.477833 56.477833 0 0 1-34.0356-54.85051h11.76356c4.42463 21.32544 19.07054 39.08777 39.16224 47.49031 20.0916 8.40254 43.0337 6.33913 61.3066-5.48824a32.333825 32.333825 0 0 0 17.3794-30.22787 27.973013 27.973013 0 0 0-19.1024-27.7922c-14.1248-5.25425-29.143-8.05155-43.5337-12.763356a320.67922 320.67922 0 0 1-44.0761-15.83719c-22.6337-11.13602-24.44184-54.8505 1.3614-68.79447a91.151606 91.151606 0 0 1 89.7902-.99979 47.330764 47.330764 0 0 1 22.7188 46.43733zM325.59311 183.84329a20.740447 20.740447 0 0 1-25.70752-9.7746l-46.79895-64.72083-6.78585-9.04071-54.30807 73.85727a19.889557 19.889557 0 0 1-24.44182 9.59378l69.96445-93.863816-65.0931-84.81247c9.6576-3.48865 20.42136.29781 25.79261 9.04071l48.50074 65.51854 48.78791-65.26328a19.464112 19.464112 0 0 1 24.261-9.05134l-25.2608 33.51443-34.21642 44.53347a9.040708 9.040708 0 0 0 0 13.48661l65.16755 86.982236zM622.66013 4.177844v12.76335a65.624902 65.624902 0 0 0-69.87935 67.79467v99.564786h-12.94417V4.975554h12.76336v36.74781c15.65637-26.80304 39.82165-36.74781 70.14525-37.47107ZM.021272 88.724414l5.700964-28.15383c15.656379-55.66949 79.473139-78.83497 123.379074-44.35265 25.70751 20.18737 32.1211 48.78792 30.86604 81.01538H15.135208C12.79526 154.79603 54.329335 189.55489 107.45679 171.81383c17.50706-6.38167 30.68522-20.93189 35.02476-39.01331 2.80794-9.04071 7.44529-10.59359 15.93292-7.9771a73.495636 73.495636 0 0 1-35.12049 53.68054 85.089014 85.089014 0 0 1-99.118064-12.66763c-12.93353-14.53959-20.740447-32.91881-22.261413-52.32975 0-3.19084-1.063613-6.16895-1.808142-9.0407Q0 96.414334 0 88.724414Zm15.294751-3.89282H146.28929c-.81898-41.72553-27.15403-71.32587-62.274525-71.60241-39.098402-.53181-67.071415 28.41973-68.794468 71.42159Z"/>
-</svg>
diff --git a/_includes/icons/github.svg b/_includes/icons/github.svg
deleted file mode 100644
index b2b41dbd47..0000000000
--- a/_includes/icons/github.svg
+++ /dev/null
@@ -1,10 +0,0 @@
-<svg
-    viewBox="0 0 256 250"
-    width="20"
-    height="20"
-    xmlns="http://www.w3.org/2000/svg"
-    fill="currentColor"
->
-    <path
-        d="M128.001 0C57.317 0 0 57.307 0 128.001c0 56.554 36.676 104.535 87.535 121.46 6.397 1.185 8.746-2.777 8.746-6.158 0-3.052-.12-13.135-.174-23.83-35.61 7.742-43.124-15.103-43.124-15.103-5.823-14.795-14.213-18.73-14.213-18.73-11.613-7.944.876-7.78.876-7.78 12.853.902 19.621 13.19 19.621 13.19 11.417 19.568 29.945 13.911 37.249 10.64 1.149-8.272 4.466-13.92 8.127-17.116-28.431-3.236-58.318-14.212-58.318-63.258 0-13.975 5-25.394 13.188-34.358-1.329-3.224-5.71-16.242 1.24-33.874 0 0 10.749-3.44 35.21 13.121 10.21-2.836 21.16-4.258 32.038-4.307 10.878.049 21.837 1.47 32.066 4.307 24.431-16.56 35.165-13.12 35.165-13.12 6.967 17.63 2.584 30.65 1.255 33.873 8.207 8.964 13.173 20.383 13.173 34.358 0 49.163-29.944 59.988-58.447 63.157 4.591 3.972 8.682 11.762 8.682 23.704 0 17.126-.148 30.91-.148 35.126 0 3.407 2.304 7.398 8.792 6.14C219.37 232.5 256 184.537 256 128.002 256 57.307 198.691 0 128.001 0Zm-80.06 182.34c-.282.636-1.283.827-2.194.39-.929-.417-1.45-1.284-1.15-1.922.276-.655 1.279-.838 2.205-.399.93.418 1.46 1.293 1.139 1.931Zm6.296 5.618c-.61.566-1.804.303-2.614-.591-.837-.892-.994-2.086-.375-2.66.63-.566 1.787-.301 2.626.591.838.903 1 2.088.363 2.66Zm4.32 7.188c-.785.545-2.067.034-2.86-1.104-.784-1.138-.784-2.503.017-3.05.795-.547 2.058-.055 2.861 1.075.782 1.157.782 2.522-.019 3.08Zm7.304 8.325c-.701.774-2.196.566-3.29-.49-1.119-1.032-1.43-2.496-.726-3.27.71-.776 2.213-.558 3.315.49 1.11 1.03 1.45 2.505.701 3.27Zm9.442 2.81c-.31 1.003-1.75 1.459-3.199 1.033-1.448-.439-2.395-1.613-2.103-2.626.301-1.01 1.747-1.484 3.207-1.028 1.446.436 2.396 1.602 2.095 2.622Zm10.744 1.193c.036 1.055-1.193 1.93-2.715 1.95-1.53.034-2.769-.82-2.786-1.86 0-1.065 1.202-1.932 2.733-1.958 1.522-.03 2.768.818 2.768 1.868Zm10.555-.405c.182 1.03-.875 2.088-2.387 2.37-1.485.271-2.861-.365-3.05-1.386-.184-1.056.893-2.114 2.376-2.387 1.514-.263 2.868.356 3.061 1.403Z" />
-</svg>
\ No newline at end of file
diff --git a/_includes/icons/hamburger.svg b/_includes/icons/hamburger.svg
deleted file mode 100644
index 9a681768f3..0000000000
--- a/_includes/icons/hamburger.svg
+++ /dev/null
@@ -1,5 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
-  <line x1="3" y1="6" x2="21" y2="6"/>
-  <line x1="3" y1="12" x2="21" y2="12"/>
-  <line x1="3" y1="18" x2="21" y2="18"/>
-</svg>
\ No newline at end of file
diff --git a/_includes/icons/i18n.svg b/_includes/icons/i18n.svg
deleted file mode 100644
index e0b2a0b2bc..0000000000
--- a/_includes/icons/i18n.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="1.5" stroke="currentColor" class="size-6" width="24" height="24">
-  <path stroke-linecap="round" stroke-linejoin="round" d="m10.5 21 5.25-11.25L21 21m-9-3h7.5M3 5.621a49 49 0 0 1 6-.371m0 0q1.681 0 3.334.114M9 5.25V3m3.334 2.364C11.176 10.658 7.69 15.08 3 17.502m9.334-12.138A48 48 0 0 1 15 5.621m-4.589 8.495a18 18 0 0 1-3.827-5.802"/>
-</svg>
diff --git a/_includes/icons/moon.svg b/_includes/icons/moon.svg
deleted file mode 100644
index 0b224e4910..0000000000
--- a/_includes/icons/moon.svg
+++ /dev/null
@@ -1,5 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 32 32" fill="currentColor">
-  <g transform="translate(1, 4) scale(0.7)">
-    <path d="M16.2 5c-9.3 5.7-9.5 19.7-.3 24.5 6.3 3.2 16.2.9 19.1-4.5 1.5-2.9.7-3.4-4.4-3.1-6.3.4-10.1-3.1-10.1-9.2 0-2.9.6-5.2 1.8-6.4 3.2-3.6-.8-4.5-6.1-1.3m2 6.3c-.4 4.9-.1 5.7 2.8 9 2 2.4 4.4 3.9 6.7 4.3 3.2.6 3.3.8 1.9 2.3-2.7 2.6-10.9 2.2-13.9-.7-4-3.8-5.2-7.6-3.8-12.2.9-3 5-8 6.6-8 .1 0 0 2.4-.3 5.3"/>
-  </g>
-</svg>
diff --git a/_includes/icons/note.svg b/_includes/icons/note.svg
deleted file mode 100644
index b08a648992..0000000000
--- a/_includes/icons/note.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" fill="none" stroke="currentColor" stroke-width="1.5" height="24" width="24" viewBox="0 0 24 24"><path stroke-linecap="round" stroke-linejoin="round" d="m11.25 11.25.041-.02a.75.75 0 0 1 1.063.852l-.708 2.836a.75.75 0 0 0 1.063.853l.041-.021M21 12a9 9 0 1 1-18 0 9 9 0 0 1 18 0Zm-9-3.75h.008v.008H12V8.25Z"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/opencollective.svg b/_includes/icons/opencollective.svg
deleted file mode 100644
index e4c1b67a75..0000000000
--- a/_includes/icons/opencollective.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 64 64" fill-rule="evenodd"><path d="M52.402 31.916c0 4.03-1.17 7.895-3.178 11.087l8.196 8.23c4.014-5.375 6.523-12.094 6.523-19.318s-2.51-13.942-6.523-19.318l-8.196 8.23c2.007 3.192 3.178 6.887 3.178 11.087z" fill="#b8d3f4"/><path d="M32.004 52.41c-11.207 0-20.406-9.24-20.406-20.493s9.2-20.493 20.406-20.493c4.182 0 7.86 1.176 11.04 3.36l8.196-8.23C45.887 2.52 39.197 0 32.004 0 14.44 0 .057 14.278.057 32.084S14.44 64 32.004 64c7.36 0 14.05-2.52 19.403-6.55l-8.196-8.23c-3.178 2.016-7.025 3.192-11.207 3.192z" fill="#3385ff"/></svg>
\ No newline at end of file
diff --git a/_includes/icons/openjs_foundation-logo-horizontal-white.svg b/_includes/icons/openjs_foundation-logo-horizontal-white.svg
deleted file mode 100644
index e87bedfa01..0000000000
--- a/_includes/icons/openjs_foundation-logo-horizontal-white.svg
+++ /dev/null
@@ -1,61 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- Generator: Adobe Illustrator 23.0.2, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
-<svg version="1.1" id="ARTWORK" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
-	 viewBox="0 0 1000 314.4" style="enable-background:new 0 0 1000 314.4;" xml:space="preserve">
-<style type="text/css">
-	.st0{fill:var(--fg);}
-</style>
-<g>
-	<path class="st0" d="M271.4,78.1L137,0.5L136.1,0l-0.9,0.5L1.6,77.7l-0.7,0.4L0,78.6v157.2l0.9,0.5l134.4,77.6l0.9,0.5l0.9-0.5
-		l132.6-76.5l1.8-1l0.9-0.5V78.6L271.4,78.1z M122.7,20.1L89.8,77H24.1L122.7,20.1z M84.4,86.4L69,113.1L22.8,86.4H84.4z
-		 M72.4,125.8l54.3,31.4l-54.3,31.4l-18.1-31.4L72.4,125.8z M64.4,121.2l-15.4,26.7L18.1,94.5L64.4,121.2z M10.7,100.3l32.9,56.9
-		l-32.9,56.9V100.3z M48.9,166.6l15.4,26.7l-46.2,26.7L48.9,166.6z M69,201.3L84.4,228H22.8L69,201.3z M24.1,237.4h65.7l32.9,56.9
-		L24.1,237.4z M131.5,290.8l-30.8-53.4h30.8V290.8z M131.5,228H95.2l-18.1-31.4l54.3-31.4V228z M131.5,149.1l-54.3-31.4l18.1-31.4
-		h36.2V149.1z M131.5,77h-30.8l30.8-53.4V77z M207.9,121.2l46.2-26.7l-30.8,53.4L207.9,121.2z M217.9,157.2l-18.1,31.4l-54.3-31.4
-		l54.3-31.4L217.9,157.2z M203.2,113.1l-15.4-26.7h61.6L203.2,113.1z M248.1,77h-65.7l-32.8-56.9L248.1,77z M140.8,23.6L171.6,77
-		h-30.8V23.6z M140.8,86.4H177l18.1,31.4l-54.3,31.4V86.4z M140.8,165.3l54.3,31.4L177,228h-36.2V165.3z M140.8,237.4h30.8
-		l-30.8,53.4V237.4z M149.6,294.3l32.8-56.9h65.7L149.6,294.3z M187.8,228l15.4-26.7l46.2,26.7H187.8z M207.9,193.2l15.4-26.7
-		l30.8,53.4L207.9,193.2z M261.6,214.1l-32.9-56.9l32.9-56.9V214.1z"/>
-	<polygon class="st0" points="308.4,202.7 372.6,202.7 372.6,208.5 315,208.5 315,257 367.2,257 367.2,263 315,263 315,312.9 
-		308.4,312.9 	"/>
-	<path class="st0" d="M383.8,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
-		C399,314.2,383.8,298.7,383.8,279.7 M446,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
-		C434.8,308.6,446,296.1,446,279.7"/>
-	<path class="st0" d="M469.9,288.5v-41.7h6.3v40.7c0,13.5,6.3,21.1,19,21.1c14.3,0,24.3-9.6,24.3-24.8v-37h6.3v66.2h-6.3l0.2-14.6
-		c-4.4,9.9-13.5,16-25.1,16C479.8,314.4,469.9,304.7,469.9,288.5"/>
-	<path class="st0" d="M543,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
-		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37H543V246.8z"/>
-	<path class="st0" d="M616.3,279.7c0-19.5,13.8-34.4,32.8-34.4c13.5,0,23.2,7.3,28,17.2v-66.6h6.3v117.1h-6.3l0.3-16.5
-		c-4.7,10.2-15.6,17.8-28.4,17.8C630.1,314.2,616.3,299.2,616.3,279.7 M677.6,279.7c0-16.4-11-28.7-27.7-28.7
-		c-16.4,0-26.9,12.3-26.9,28.7c0,16.4,10.5,28.9,26.9,28.9C666.6,308.6,677.6,296.1,677.6,279.7"/>
-	<path class="st0" d="M748,271.4c0-14.9-6.8-20.6-17.7-20.6c-10.1,0-16.9,4.2-21.6,11.4l-4.5-3.2c5.5-8.6,14.9-13.6,26.3-13.6
-		c13.6,0,23.8,8.3,23.8,25.5v42.2H748l0.3-10.2c-4.2,6.3-11.5,11.5-22.9,11.5c-15.1,0-25-7-25-20.3c0-13.1,11.5-19.3,24.2-19.3H748
-		V271.4z M725.4,279.9c-10.1,0-18.6,3.9-18.6,13.9c0,10.1,6.6,14.8,19.3,14.8c11,0,21.9-6.5,21.9-16.7v-12H725.4z"/>
-	<path class="st0" d="M782.5,295.4v-43.3h-10.4v-5.4h10.4v-23.2h6.3v23.2h19.1v5.4h-19.1v43.1c0,9.7,3.4,13.3,8.9,13.3
-		c5.8,0,8.1-2.3,10.5-4.9l4.1,3.9c-3.2,3.7-7.1,6.6-14.6,6.6C789.3,314.2,782.5,308.9,782.5,295.4"/>
-	<path class="st0" d="M829.5,218.2c0-3.1,2.6-5.4,5.4-5.4c2.8,0,5.4,2.3,5.4,5.4c0,3.2-2.6,5.3-5.4,5.3
-		C832.1,223.6,829.5,221.5,829.5,218.2 M831.8,246.8h6.3v66.2h-6.3V246.8z"/>
-	<path class="st0" d="M857.1,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
-		C872.4,314.2,857.1,298.7,857.1,279.7 M919.4,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
-		C908.2,308.6,919.4,296.1,919.4,279.7"/>
-	<path class="st0" d="M943.9,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
-		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37h-6.3V246.8z"/>
-	<path class="st0" d="M308.4,73.1c0-41.4,31.8-71.3,71.7-71.3c39.6,0,71.5,29.8,71.5,71.3c0,41.4-31.9,71.3-71.5,71.3
-		C340.2,144.3,308.4,114.5,308.4,73.1 M429.4,73.1c0-29.6-20.4-51.9-49.4-51.9c-29,0-49.6,22.3-49.6,51.9
-		c0,29.6,20.6,51.9,49.6,51.9C409,124.9,429.4,102.7,429.4,73.1"/>
-	<path class="st0" d="M473.9,56.8h20.8l-0.6,15.9c5.5-10.6,15.7-17.8,30.4-17.8c22,0,39.8,18.6,39.8,44.5c0,25.9-18,44.9-40.2,44.9
-		c-14.3,0-24.5-6.9-29.4-16.5v58h-20.8V56.8z M543.1,99.4c0-15.5-9.4-26.1-24.3-26.1c-15.1,0-24.9,10.6-24.9,26.1
-		c0,16.1,9.8,26.7,24.9,26.7C533.8,126.2,543.1,115.6,543.1,99.4"/>
-	<path class="st0" d="M635,127c11.2,0,19.4-4.5,24.3-9.2l12,12.7c-8,8-19,13.9-36.1,13.9c-29.4,0-48.4-19-48.4-44.7
-		c0-25.5,20-44.7,45.7-44.7c29.2,0,45.7,21.6,44.3,51.7h-69C610.3,119,619.3,127,635,127 M656.1,92.3c-1.8-11.6-9-20.2-23.3-20.2
-		c-13.3,0-22.5,7.3-24.9,20.2H656.1z"/>
-	<path class="st0" d="M699.7,56.8h20.6l-0.4,15.9c5.3-11.2,16.1-17.8,29-17.8c19,0,32.1,13.5,32.1,36.7v50.8h-20.6V93.3
-		c0-12.3-5.7-19.4-17.8-19.4c-13.5,0-22.3,8.2-22.3,22v46.5h-20.6V56.8z"/>
-	<path class="st0" d="M803.5,120.9l17.6-10.8c4.9,8.8,10.6,14.9,20.8,14.9c11.6,0,19.2-5.5,19.2-21.6V3.7h21.6v100
-		c0,27.6-16.5,40.6-39.8,40.6C822.3,144.3,810.1,133.7,803.5,120.9"/>
-	<path class="st0" d="M904.9,115.6l17.8-9.8c6.5,10.8,14.9,19.4,31.8,19.4c14.1,0,24.1-7.6,24.1-19c0-12-8.2-17.4-23.3-24.1
-		l-9.2-4.1c-20.2-9-32.5-19.2-32.5-40.6c0-20.6,15.9-35.3,39-35.3C971,2,983.5,9,991.8,23.9l-16.9,10.4
-		c-5.3-9.2-11.4-13.5-22.3-13.5c-11,0-18,6.7-18,16.1c0,10.4,5.9,15.1,20,21.2l9,4.1c23.7,10.4,36.3,21.4,36.3,43.7
-		c0,24.3-19,38.4-45.1,38.4C928.5,144.3,912.6,131.3,904.9,115.6"/>
-</g>
-</svg>
diff --git a/_includes/icons/slack.svg b/_includes/icons/slack.svg
deleted file mode 100644
index e6bb3f152c..0000000000
--- a/_includes/icons/slack.svg
+++ /dev/null
@@ -1,25 +0,0 @@
-<svg
-  viewBox="0 0 2447.6 2452.5"
-  xmlns="http://www.w3.org/2000/svg"
-  width="20"
-  height="20"
->
-  <g clip-rule="evenodd" fill-rule="evenodd">
-    <path
-      d="m897.4 0c-135.3.1-244.8 109.9-244.7 245.2-.1 135.3 109.5 245.1 244.8 245.2h244.8v-245.1c.1-135.3-109.5-245.1-244.9-245.3.1 0 .1 0 0 0m0 654h-652.6c-135.3.1-244.9 109.9-244.8 245.2-.2 135.3 109.4 245.1 244.7 245.3h652.7c135.3-.1 244.9-109.9 244.8-245.2.1-135.4-109.5-245.2-244.8-245.3z"
-      fill="#36c5f0"
-    />
-    <path
-      d="m2447.6 899.2c.1-135.3-109.5-245.1-244.8-245.2-135.3.1-244.9 109.9-244.8 245.2v245.3h244.8c135.3-.1 244.9-109.9 244.8-245.3zm-652.7 0v-654c.1-135.2-109.4-245-244.7-245.2-135.3.1-244.9 109.9-244.8 245.2v654c-.2 135.3 109.4 245.1 244.7 245.3 135.3-.1 244.9-109.9 244.8-245.3z"
-      fill="#2eb67d"
-    />
-    <path
-      d="m1550.1 2452.5c135.3-.1 244.9-109.9 244.8-245.2.1-135.3-109.5-245.1-244.8-245.2h-244.8v245.2c-.1 135.2 109.5 245 244.8 245.2zm0-654.1h652.7c135.3-.1 244.9-109.9 244.8-245.2.2-135.3-109.4-245.1-244.7-245.3h-652.7c-135.3.1-244.9 109.9-244.8 245.2-.1 135.4 109.4 245.2 244.7 245.3z"
-      fill="#ecb22e"
-    />
-    <path
-      d="m0 1553.2c-.1 135.3 109.5 245.1 244.8 245.2 135.3-.1 244.9-109.9 244.8-245.2v-245.2h-244.8c-135.3.1-244.9 109.9-244.8 245.2zm652.7 0v654c-.2 135.3 109.4 245.1 244.7 245.3 135.3-.1 244.9-109.9 244.8-245.2v-653.9c.2-135.3-109.4-245.1-244.7-245.3-135.4 0-244.9 109.8-244.8 245.1 0 0 0 .1 0 0"
-      fill="#e01e5a"
-    />
-  </g>
-</svg>
diff --git a/_includes/icons/sun.svg b/_includes/icons/sun.svg
deleted file mode 100644
index 0701fffd93..0000000000
--- a/_includes/icons/sun.svg
+++ /dev/null
@@ -1,17 +0,0 @@
-<svg width="24" height="24" viewBox="0 0 32 32" fill="none" xmlns="http://www.w3.org/2000/svg">
-  <g transform="translate(4 4)" stroke="currentColor" stroke-width="2" stroke-linecap="round">
-    <circle cx="12" cy="12" r="7.5"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(0 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(30 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(60 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(90 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(120 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(150 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(180 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(210 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(240 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(270 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(300 12 12)"/>
-    <line x1="12" y1="-2" x2="12" y2="1" transform="rotate(330 12 12)"/>
-  </g>
-</svg>
diff --git a/_includes/icons/warning.svg b/_includes/icons/warning.svg
deleted file mode 100644
index fa4907c793..0000000000
--- a/_includes/icons/warning.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg viewBox="0 0 24 24" width="24" height="24" fill="currentColor"><path d="M12 7C11.7348 7 11.4804 7.10536 11.2929 7.29289C11.1054 7.48043 11 7.73478 11 8V12C11 12.2652 11.1054 12.5196 11.2929 12.7071C11.4804 12.8946 11.7348 13 12 13C12.2652 13 12.5196 12.8946 12.7071 12.7071C12.8946 12.5196 13 12.2652 13 12V8C13 7.73478 12.8946 7.48043 12.7071 7.29289C12.5196 7.10536 12.2652 7 12 7ZM12 15C11.8022 15 11.6089 15.0586 11.4444 15.1685C11.28 15.2784 11.1518 15.4346 11.0761 15.6173C11.0004 15.8 10.9806 16.0011 11.0192 16.1951C11.0578 16.3891 11.153 16.5673 11.2929 16.7071C11.4327 16.847 11.6109 16.9422 11.8049 16.9808C11.9989 17.0194 12.2 16.9996 12.3827 16.9239C12.5654 16.8482 12.7216 16.72 12.8315 16.5556C12.9414 16.3911 13 16.1978 13 16C13 15.7348 12.8946 15.4804 12.7071 15.2929C12.5196 15.1054 12.2652 15 12 15ZM21.71 7.56L16.44 2.29C16.2484 2.10727 15.9948 2.00368 15.73 2H8.27C8.00523 2.00368 7.75163 2.10727 7.56 2.29L2.29 7.56C2.10727 7.75163 2.00368 8.00523 2 8.27V15.73C2.00368 15.9948 2.10727 16.2484 2.29 16.44L7.56 21.71C7.75163 21.8927 8.00523 21.9963 8.27 22H15.73C15.9948 21.9963 16.2484 21.8927 16.44 21.71L21.71 16.44C21.8927 16.2484 21.9963 15.9948 22 15.73V8.27C21.9963 8.00523 21.8927 7.75163 21.71 7.56ZM20 15.31L15.31 20H8.69L4 15.31V8.69L8.69 4H15.31L20 8.69V15.31Z"></path></svg>
\ No newline at end of file
diff --git a/_includes/icons/youtube.svg b/_includes/icons/youtube.svg
deleted file mode 100644
index 5968f9b040..0000000000
--- a/_includes/icons/youtube.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg viewBox="0 0 256 180" height="20" xmlns="http://www.w3.org/2000/svg" preserveAspectRatio="xMidYMid"><path d="M250.346 28.075A32.18 32.18 0 0 0 227.69 5.418C207.824 0 127.87 0 127.87 0S47.912.164 28.046 5.582A32.18 32.18 0 0 0 5.39 28.24c-6.009 35.298-8.34 89.084.165 122.97a32.18 32.18 0 0 0 22.656 22.657c19.866 5.418 99.822 5.418 99.822 5.418s79.955 0 99.82-5.418a32.18 32.18 0 0 0 22.657-22.657c6.338-35.348 8.291-89.1-.164-123.134Z" fill="red"/><path fill="#FFF" d="m102.421 128.06 66.328-38.418-66.328-38.418z"/></svg>
\ No newline at end of file
diff --git a/_includes/language-picker.html b/_includes/language-picker.html
deleted file mode 100644
index 0a344ed9a3..0000000000
--- a/_includes/language-picker.html
+++ /dev/null
@@ -1,21 +0,0 @@
-{% assign url_parts = page.url | split: '/' %}
-{% assign url_remainder = url_parts | slice: 2, url_parts.size | join: '/' %}
-{% assign current_lang = page.lang %}
-<div class="desktop-lang-switcher">
-  <button id="langBtn" class="lang-btn" type="button" aria-expanded="false" aria-haspopup="listbox" aria-label="Change language">
-    {% include icons/i18n.svg %}
-  </button>
-  <ul id="langList" class="lang-list" role="listbox">
-    {% for lang in site.data.languages %}
-    <li>
-      <a href="/{{ lang.code }}/{{ url_remainder }}">
-        {% if lang.code == current_lang %}
-        <strong>{{ lang.name }}</strong>
-        {% else %}
-        {{ lang.name }}
-        {% endif %}
-      </a>
-    </li>
-    {% endfor %}
-  </ul>
-</div>
\ No newline at end of file
diff --git a/_includes/mw-list.md b/_includes/mw-list.md
deleted file mode 100644
index 7eae8705cc..0000000000
--- a/_includes/mw-list.md
+++ /dev/null
@@ -1,18 +0,0 @@
-- [body-parser](/resources/middleware/body-parser.html)
-- [compression](/resources/middleware/compression.html)
-- [connect-rid](/resources/middleware/connect-rid.html)
-- [cookie-parser](/resources/middleware/cookie-parser.html)
-- [cookie-session](/resources/middleware/cookie-session.html)
-- [cors](/resources/middleware/cors.html)
-- [errorhandler](/resources/middleware/errorhandler.html)
-- [method-override](/resources/middleware/method-override.html)
-- [morgan](/resources/middleware/morgan.html)
-- [multer](/resources/middleware/multer.html)
-- [response-time](/resources/middleware/response-time.html)
-- [serve-favicon](/resources/middleware/serve-favicon.html)
-- [serve-index](/resources/middleware/serve-index.html)
-- [serve-static](/resources/middleware/serve-static.html)
-- [session](/resources/middleware/session.html)
-- [timeout](/resources/middleware/timeout.html)
-- [vhost](/resources/middleware/vhost.html)
-{: #side-menu .active}
\ No newline at end of file
diff --git a/_includes/readmes/body-parser.md b/_includes/readmes/body-parser.md
deleted file mode 100644
index d7149004fe..0000000000
--- a/_includes/readmes/body-parser.md
+++ /dev/null
@@ -1,509 +0,0 @@
-# body-parser
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Build Status][ci-image]][ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-[![OpenSSF Scorecard Badge][ossf-scorecard-badge]][ossf-scorecard-visualizer]
-
-Node.js body parsing middleware.
-
-Parse incoming request bodies in a middleware before your handlers, available
-under the `req.body` property.
-
-**Note** As `req.body`'s shape is based on user-controlled input, all
-properties and values in this object are untrusted and should be validated
-before trusting. For example, `req.body.foo.toString()` may fail in multiple
-ways, for example the `foo` property may not be there or may not be a string,
-and `toString` may not be a function and instead a string or other user input.
-
-[Learn about the anatomy of an HTTP transaction in Node.js](https://nodejs.org/en/learn/http/anatomy-of-an-http-transaction).
-
-_This does not handle multipart bodies_, due to their complex and typically
-large nature. For multipart bodies, you may be interested in the following
-modules:
-
-  * [busboy](https://www.npmjs.com/package/busboy#readme) and
-    [connect-busboy](https://www.npmjs.com/package/connect-busboy#readme)
-  * [multiparty](https://www.npmjs.com/package/multiparty#readme) and
-    [connect-multiparty](https://www.npmjs.com/package/connect-multiparty#readme)
-  * [formidable](https://www.npmjs.com/package/formidable#readme)
-  * [multer](https://www.npmjs.com/package/multer#readme)
-
-This module provides the following parsers:
-
-  * [JSON body parser](#bodyparserjsonoptions)
-  * [Raw body parser](#bodyparserrawoptions)
-  * [Text body parser](#bodyparsertextoptions)
-  * [URL-encoded form body parser](#bodyparserurlencodedoptions)
-
-Other body parsers you might be interested in:
-
-- [body](https://www.npmjs.com/package/body#readme)
-- [co-body](https://www.npmjs.com/package/co-body#readme)
-
-## Installation
-
-```sh
-$ npm install body-parser
-```
-
-## API
-
-```js
-// Import all parsers
-const bodyParser = require('body-parser')
-
-// Or import individual parsers directly
-const json = require('body-parser/json')
-const urlencoded = require('body-parser/urlencoded')
-const raw = require('body-parser/raw')
-const text = require('body-parser/text')
-```
-
-The `bodyParser` object exposes various factories to create middlewares. All
-middlewares will populate the `req.body` property with the parsed body when
-the `Content-Type` request header matches the `type` option.
-
-The various errors returned by this module are described in the
-[errors section](#errors).
-
-### bodyParser.json([options])
-
-Returns middleware that only parses `json` and only looks at requests where
-the `Content-Type` header matches the `type` option. This parser accepts any
-Unicode encoding of the body and supports automatic inflation of `gzip`,
-`br` (brotli) and `deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`).
-
-#### Options
-
-The `json` function takes an optional `options` object that may contain any of
-the following keys:
-
-##### defaultCharset
-
-Specify the default character set for the json content if the charset is not
-specified in the `Content-Type` header of the request. Defaults to `utf-8`.
-
-##### inflate
-
-When set to `true`, then deflated (compressed) bodies will be inflated; when
-`false`, deflated bodies are rejected. Defaults to `true`.
-
-##### limit
-
-Controls the maximum request body size. If this is a number, then the value
-specifies the number of bytes; if it is a string, the value is passed to the
-[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
-to `'100kb'`.
-
-> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
-
-##### reviver
-
-The `reviver` option is passed directly to `JSON.parse` as the second
-argument. You can find more information on this argument
-[in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter).
-
-##### strict
-
-When set to `true`, will only accept arrays and objects; when `false` will
-accept anything `JSON.parse` accepts. Defaults to `true`.
-
-##### type
-
-The `type` option is used to determine what media type the middleware will
-parse. This option can be a string, array of strings, or a function. If not a
-function, `type` option is passed directly to the
-[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
-be an extension name (like `json`), a mime type (like `application/json`), or
-a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type`
-option is called as `fn(req)` and the request is parsed if it returns a truthy
-value. Defaults to `application/json`.
-
-##### verify
-
-The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
-where `buf` is a `Buffer` of the raw request body and `encoding` is the
-encoding of the request. The parsing can be aborted by throwing an error.
-
-### bodyParser.raw([options])
-
-Returns middleware that parses all bodies as a `Buffer` and only looks at
-requests where the `Content-Type` header matches the `type` option. This
-parser supports automatic inflation of `gzip`, `br` (brotli) and `deflate`
-encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`). This will be a `Buffer` object
-of the body.
-
-#### Options
-
-The `raw` function takes an optional `options` object that may contain any of
-the following keys:
-
-##### inflate
-
-When set to `true`, then deflated (compressed) bodies will be inflated; when
-`false`, deflated bodies are rejected. Defaults to `true`.
-
-##### limit
-
-Controls the maximum request body size. If this is a number, then the value
-specifies the number of bytes; if it is a string, the value is passed to the
-[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
-to `'100kb'`.
-
-> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
-
-##### type
-
-The `type` option is used to determine what media type the middleware will
-parse. This option can be a string, array of strings, or a function.
-If not a function, `type` option is passed directly to the
-[type-is](https://www.npmjs.com/package/type-is#readme) library and this
-can be an extension name (like `bin`), a mime type (like
-`application/octet-stream`), or a mime type with a wildcard (like `*/*` or
-`application/*`). If a function, the `type` option is called as `fn(req)`
-and the request is parsed if it returns a truthy value. Defaults to
-`application/octet-stream`.
-
-##### verify
-
-The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
-where `buf` is a `Buffer` of the raw request body and `encoding` is the
-encoding of the request. The parsing can be aborted by throwing an error.
-
-### bodyParser.text([options])
-
-Returns middleware that parses all bodies as a string and only looks at
-requests where the `Content-Type` header matches the `type` option. This
-parser supports automatic inflation of `gzip`, `br` (brotli) and `deflate`
-encodings.
-
-A new `body` string containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`). This will be a string of the
-body.
-
-#### Options
-
-The `text` function takes an optional `options` object that may contain any of
-the following keys:
-
-##### defaultCharset
-
-Specify the default character set for the text content if the charset is not
-specified in the `Content-Type` header of the request. Defaults to `utf-8`.
-
-##### inflate
-
-When set to `true`, then deflated (compressed) bodies will be inflated; when
-`false`, deflated bodies are rejected. Defaults to `true`.
-
-##### limit
-
-Controls the maximum request body size. If this is a number, then the value
-specifies the number of bytes; if it is a string, the value is passed to the
-[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
-to `'100kb'`.
-
-> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
-
-##### type
-
-The `type` option is used to determine what media type the middleware will
-parse. This option can be a string, array of strings, or a function. If not
-a function, `type` option is passed directly to the
-[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
-be an extension name (like `txt`), a mime type (like `text/plain`), or a mime
-type with a wildcard (like `*/*` or `text/*`). If a function, the `type`
-option is called as `fn(req)` and the request is parsed if it returns a
-truthy value. Defaults to `text/plain`.
-
-##### verify
-
-The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
-where `buf` is a `Buffer` of the raw request body and `encoding` is the
-encoding of the request. The parsing can be aborted by throwing an error.
-
-### bodyParser.urlencoded([options])
-
-Returns middleware that only parses `urlencoded` bodies and only looks at
-requests where the `Content-Type` header matches the `type` option. This
-parser accepts only UTF-8 and ISO-8859-1 encodings of the body and supports 
-automatic inflation of `gzip`, `br` (brotli) and `deflate` encodings.
-
-A new `body` object containing the parsed data is populated on the `request`
-object after the middleware (i.e. `req.body`). This object will contain
-key-value pairs, where the value can be a string or array (when `extended` is
-`false`), or any type (when `extended` is `true`).
-
-#### Options
-
-The `urlencoded` function takes an optional `options` object that may contain
-any of the following keys:
-
-##### extended
-
-The "extended" syntax allows for rich objects and arrays to be encoded into the
-URL-encoded format, allowing for a JSON-like experience with URL-encoded. For
-more information, please [see the qs
-library](https://www.npmjs.com/package/qs#readme).
-
-Defaults to `false`.
-
-##### inflate
-
-When set to `true`, then deflated (compressed) bodies will be inflated; when
-`false`, deflated bodies are rejected. Defaults to `true`.
-
-##### limit
-
-Controls the maximum request body size. If this is a number, then the value
-specifies the number of bytes; if it is a string, the value is passed to the
-[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
-to `'100kb'`.
-
-> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
-
-##### parameterLimit
-
-The `parameterLimit` option controls the maximum number of parameters that
-are allowed in the URL-encoded data. If a request contains more parameters
-than this value, a 413 will be returned to the client. Defaults to `1000`.
-
-##### type
-
-The `type` option is used to determine what media type the middleware will
-parse. This option can be a string, array of strings, or a function. If not
-a function, `type` option is passed directly to the
-[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
-be an extension name (like `urlencoded`), a mime type (like
-`application/x-www-form-urlencoded`), or a mime type with a wildcard (like
-`*/x-www-form-urlencoded`). If a function, the `type` option is called as
-`fn(req)` and the request is parsed if it returns a truthy value. Defaults
-to `application/x-www-form-urlencoded`.
-
-##### verify
-
-The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
-where `buf` is a `Buffer` of the raw request body and `encoding` is the
-encoding of the request. The parsing can be aborted by throwing an error.
-
-##### defaultCharset
-
-The default charset to parse as, if not specified in content-type. Must be
-either `utf-8` or `iso-8859-1`. Defaults to `utf-8`.
-
-##### charsetSentinel
-
-Whether to let the value of the `utf8` parameter take precedence as the charset
-selector. It requires the form to contain a parameter named `utf8` with a value
-of `✓`. Defaults to `false`.
-
-##### interpretNumericEntities
-
-Whether to decode numeric entities such as `&#9786;` when parsing an iso-8859-1
-form. Defaults to `false`.
-
-
-##### depth
-
-The `depth` option is used to configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible.
-
-## Errors
-
-The middlewares provided by this module create errors using the
-[`http-errors` module](https://www.npmjs.com/package/http-errors). The errors
-will typically have a `status`/`statusCode` property that contains the suggested
-HTTP response code, an `expose` property to determine if the `message` property
-should be displayed to the client, a `type` property to determine the type of
-error without matching against the `message`, and a `body` property containing
-the read body, if available.
-
-The following are the common errors created, though any error can come through
-for various reasons.
-
-### content encoding unsupported
-
-This error will occur when the request had a `Content-Encoding` header that
-contained an encoding but the "inflation" option was set to `false`. The
-`status` property is set to `415`, the `type` property is set to
-`'encoding.unsupported'`, and the `charset` property will be set to the
-encoding that is unsupported.
-
-### entity parse failed
-
-This error will occur when the request contained an entity that could not be
-parsed by the middleware. The `status` property is set to `400`, the `type`
-property is set to `'entity.parse.failed'`, and the `body` property is set to
-the entity value that failed parsing.
-
-### entity verify failed
-
-This error will occur when the request contained an entity that could not be
-failed verification by the defined `verify` option. The `status` property is
-set to `403`, the `type` property is set to `'entity.verify.failed'`, and the
-`body` property is set to the entity value that failed verification.
-
-### request aborted
-
-This error will occur when the request is aborted by the client before reading
-the body has finished. The `received` property will be set to the number of
-bytes received before the request was aborted and the `expected` property is
-set to the number of expected bytes. The `status` property is set to `400`
-and `type` property is set to `'request.aborted'`.
-
-### request entity too large
-
-This error will occur when the request body's size is larger than the "limit"
-option. The `limit` property will be set to the byte limit and the `length`
-property will be set to the request body's length. The `status` property is
-set to `413` and the `type` property is set to `'entity.too.large'`.
-
-### request size did not match content length
-
-This error will occur when the request's length did not match the length from
-the `Content-Length` header. This typically occurs when the request is malformed,
-typically when the `Content-Length` header was calculated based on characters
-instead of bytes. The `status` property is set to `400` and the `type` property
-is set to `'request.size.invalid'`.
-
-### stream encoding should not be set
-
-This error will occur when something called the `req.setEncoding` method prior
-to this middleware. This module operates directly on bytes only and you cannot
-call `req.setEncoding` when using this module. The `status` property is set to
-`500` and the `type` property is set to `'stream.encoding.set'`.
-
-### stream is not readable
-
-This error will occur when the request is no longer readable when this middleware
-attempts to read it. This typically means something other than a middleware from
-this module read the request body already and the middleware was also configured to
-read the same request. The `status` property is set to `500` and the `type`
-property is set to `'stream.not.readable'`.
-
-### too many parameters
-
-This error will occur when the content of the request exceeds the configured
-`parameterLimit` for the `urlencoded` parser. The `status` property is set to
-`413` and the `type` property is set to `'parameters.too.many'`.
-
-### unsupported charset "BOGUS"
-
-This error will occur when the request had a charset parameter in the
-`Content-Type` header, but the `iconv-lite` module does not support it OR the
-parser does not support it. The charset is contained in the message as well
-as in the `charset` property. The `status` property is set to `415`, the
-`type` property is set to `'charset.unsupported'`, and the `charset` property
-is set to the charset that is unsupported.
-
-### unsupported content encoding "bogus"
-
-This error will occur when the request had a `Content-Encoding` header that
-contained an unsupported encoding. The encoding is contained in the message
-as well as in the `encoding` property. The `status` property is set to `415`,
-the `type` property is set to `'encoding.unsupported'`, and the `encoding`
-property is set to the encoding that is unsupported.
-
-### The input exceeded the depth
-
-This error occurs when using `bodyParser.urlencoded` with the `extended` property set to `true` and the input exceeds the configured `depth` option. The `status` property is set to `400`. It is recommended to review the `depth` option and evaluate if it requires a higher value. When the `depth` option is set to `32` (default value), the error will not be thrown.
-
-## Examples
-
-### Express/Connect top-level generic
-
-This example demonstrates adding a generic JSON and URL-encoded parser as a
-top-level middleware, which will parse the bodies of all incoming requests.
-This is the simplest setup.
-
-```js
-const express = require('express')
-const bodyParser = require('body-parser')
-
-const app = express()
-
-// parse application/x-www-form-urlencoded
-app.use(bodyParser.urlencoded())
-
-// parse application/json
-app.use(bodyParser.json())
-
-app.use(function (req, res) {
-  res.setHeader('Content-Type', 'text/plain')
-  res.write('you posted:\n')
-  res.end(String(JSON.stringify(req.body, null, 2)))
-})
-```
-
-### Express route-specific
-
-This example demonstrates adding body parsers specifically to the routes that
-need them. In general, this is the most recommended way to use body-parser with
-Express.
-
-```js
-const express = require('express')
-const bodyParser = require('body-parser')
-
-const app = express()
-
-// create application/json parser
-const jsonParser = bodyParser.json()
-
-// create application/x-www-form-urlencoded parser
-const urlencodedParser = bodyParser.urlencoded()
-
-// POST /login gets urlencoded bodies
-app.post('/login', urlencodedParser, function (req, res) {
-  if (!req.body || !req.body.username) res.sendStatus(400)
-  res.send('welcome, ' + req.body.username)
-})
-
-// POST /api/users gets JSON bodies
-app.post('/api/users', jsonParser, function (req, res) {
-  if (!req.body) res.sendStatus(400)
-  // create user in req.body
-})
-```
-
-### Change accepted type for parsers
-
-All the parsers accept a `type` option which allows you to change the
-`Content-Type` that the middleware will parse.
-
-```js
-const express = require('express')
-const bodyParser = require('body-parser')
-
-const app = express()
-
-// parse various different custom JSON types as JSON
-app.use(bodyParser.json({ type: 'application/*+json' }))
-
-// parse some custom thing into a Buffer
-app.use(bodyParser.raw({ type: 'application/vnd.custom-type' }))
-
-// parse an HTML body into a string
-app.use(bodyParser.text({ type: 'text/html' }))
-```
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://img.shields.io/github/actions/workflow/status/expressjs/body-parser/ci.yml?branch=master&label=ci
-[ci-url]: https://github.com/expressjs/body-parser/actions/workflows/ci.yml
-[coveralls-image]: https://img.shields.io/coverallsCoverage/github/expressjs/body-parser?branch=master
-[coveralls-url]: https://coveralls.io/r/expressjs/body-parser?branch=master
-[npm-downloads-image]: https://img.shields.io/npm/dm/body-parser
-[npm-url]: https://npmjs.com/package/body-parser
-[npm-version-image]: https://img.shields.io/npm/v/body-parser
-[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/body-parser/badge
-[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/body-parser
diff --git a/_includes/readmes/compression.md b/_includes/readmes/compression.md
deleted file mode 100644
index df1bd78947..0000000000
--- a/_includes/readmes/compression.md
+++ /dev/null
@@ -1,311 +0,0 @@
-# compression
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Build Status][github-actions-ci-image]][github-actions-ci-url]
-[![OpenSSF Scorecard Badge][ossf-scorecard-badge]][ossf-scorecard-visualizer]
-[![Funding][funding-image]][funding-url]
-
-
-Node.js compression middleware.
-
-The following compression codings are supported:
-
-  - deflate
-  - gzip
-  - br (brotli)
-
-**Note** Brotli is supported only since Node.js versions v11.7.0 and v10.16.0.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```bash
-$ npm install compression
-```
-
-## API
-
-```js
-var compression = require('compression')
-```
-
-### compression([options])
-
-Returns the compression middleware using the given `options`. The middleware
-will attempt to compress response bodies for all requests that traverse through
-the middleware, based on the given `options`.
-
-This middleware will never compress responses that include a `Cache-Control`
-header with the [`no-transform` directive](https://tools.ietf.org/html/rfc7234#section-5.2.2.4),
-as compressing will transform the body.
-
-#### Options
-
-`compression()` accepts these properties in the options object. In addition to
-those listed below, [zlib](https://nodejs.org/api/zlib.html) options may be
-passed in to the options object or
-[brotli](https://nodejs.org/api/zlib.html#zlib_class_brotlioptions) options.
-
-##### chunkSize
-
-Type: `Number`<br>
-Default: `zlib.constants.Z_DEFAULT_CHUNK`, or `16384`.
-
-See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
-regarding the usage.
-
-##### filter
-
-Type: `Function`
-
-A function to decide if the response should be considered for compression.
-This function is called as `filter(req, res)` and is expected to return
-`true` to consider the response for compression, or `false` to not compress
-the response.
-
-The default filter function uses the [compressible](https://www.npmjs.com/package/compressible)
-module to determine if `res.getHeader('Content-Type')` is compressible.
-
-##### level
-
-Type: `Number`<br>
-Default: `zlib.constants.Z_DEFAULT_COMPRESSION`, or `-1`
-
-The level of zlib compression to apply to responses. A higher level will result
-in better compression, but will take longer to complete. A lower level will
-result in less compression, but will be much faster.
-
-This is an integer in the range of `0` (no compression) to `9` (maximum
-compression). The special value `-1` can be used to mean the "default
-compression level", which is a default compromise between speed and
-compression (currently equivalent to level 6).
-
-  - `-1` Default compression level (also `zlib.constants.Z_DEFAULT_COMPRESSION`).
-  - `0` No compression (also `zlib.constants.Z_NO_COMPRESSION`).
-  - `1` Fastest compression (also `zlib.constants.Z_BEST_SPEED`).
-  - `2`
-  - `3`
-  - `4`
-  - `5`
-  - `6` (currently what `zlib.constants.Z_DEFAULT_COMPRESSION` points to).
-  - `7`
-  - `8`
-  - `9` Best compression (also `zlib.constants.Z_BEST_COMPRESSION`).
-
-**Note** in the list above, `zlib` is from `zlib = require('zlib')`.
-
-##### memLevel
-
-Type: `Number`<br>
-Default: `zlib.constants.Z_DEFAULT_MEMLEVEL`, or `8`
-
-This specifies how much memory should be allocated for the internal compression
-state and is an integer in the range of `1` (minimum level) and `9` (maximum
-level).
-
-See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
-regarding the usage.
-
-##### brotli
-
-Type: `Object`
-
-This specifies the options for configuring Brotli. See [Node.js documentation](https://nodejs.org/api/zlib.html#class-brotlioptions) for a complete list of available options.
-
-
-##### strategy
-
-Type: `Number`<br>
-Default: `zlib.constants.Z_DEFAULT_STRATEGY`
-
-This is used to tune the compression algorithm. This value only affects the
-compression ratio, not the correctness of the compressed output, even if it
-is not set appropriately.
-
-  - `zlib.constants.Z_DEFAULT_STRATEGY` Use for normal data.
-  - `zlib.constants.Z_FILTERED` Use for data produced by a filter (or predictor).
-    Filtered data consists mostly of small values with a somewhat random
-    distribution. In this case, the compression algorithm is tuned to
-    compress them better. The effect is to force more Huffman coding and less
-    string matching; it is somewhat intermediate between `zlib.constants.Z_DEFAULT_STRATEGY`
-    and `zlib.constants.Z_HUFFMAN_ONLY`.
-  - `zlib.constants.Z_FIXED` Use to prevent the use of dynamic Huffman codes, allowing
-    for a simpler decoder for special applications.
-  - `zlib.constants.Z_HUFFMAN_ONLY` Use to force Huffman encoding only (no string match).
-  - `zlib.constants.Z_RLE` Use to limit match distances to one (run-length encoding).
-    This is designed to be almost as fast as `zlib.constants.Z_HUFFMAN_ONLY`, but give
-    better compression for PNG image data.
-
-**Note** in the list above, `zlib` is from `zlib = require('zlib')`.
-
-##### threshold
-
-Type: `Number` or `String`<br>
-Default: `1kb`
-
-The byte threshold for the response body size before compression is considered
-for the response. This is a number of bytes or any string
-accepted by the [bytes](https://www.npmjs.com/package/bytes) module.
-
-**Note** this is only an advisory setting; if the response size cannot be determined
-at the time the response headers are written, then it is assumed the response is
-_over_ the threshold. To guarantee the response size can be determined, be sure
-set a `Content-Length` response header.
-
-##### windowBits
-
-Type: `Number`<br>
-Default: `zlib.constants.Z_DEFAULT_WINDOWBITS`, or `15`
-
-See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
-regarding the usage.
-
-##### enforceEncoding
-
-Type: `String`<br>
-Default: `identity`
-
-This is the default encoding to use when the client does not specify an encoding in the request's [Accept-Encoding](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding) header.
-
-#### .filter
-
-The default `filter` function. This is used to construct a custom filter
-function that is an extension of the default function.
-
-```js
-var compression = require('compression')
-var express = require('express')
-
-var app = express()
-
-app.use(compression({ filter: shouldCompress }))
-
-function shouldCompress (req, res) {
-  if (req.headers['x-no-compression']) {
-    // don't compress responses with this request header
-    return false
-  }
-
-  // fallback to standard filter function
-  return compression.filter(req, res)
-}
-```
-
-### res.flush
-
-This module adds a `res.flush()` method to force the partially-compressed
-response to be flushed to the client.
-
-## Examples
-
-### express
-
-When using this module with express, simply `app.use` the module as
-high as you like. Requests that pass through the middleware will be compressed.
-
-```js
-var compression = require('compression')
-var express = require('express')
-
-var app = express()
-
-// compress all responses
-app.use(compression())
-
-// add all routes
-```
-
-### Node.js HTTP server
-
-```js
-var compression = require('compression')({ threshold: 0 })
-var http = require('http')
-
-function createServer (fn) {
-  return http.createServer(function (req, res) {
-    compression(req, res, function (err) {
-      if (err) {
-        res.statusCode = err.status || 500
-        res.end(err.message)
-        return
-      }
-
-      fn(req, res)
-    })
-  })
-}
-
-var server = createServer(function (req, res) {
-  res.setHeader('Content-Type', 'text/plain')
-  res.end('hello world!')
-})
-
-server.listen(3000, () => {
-  console.log('> Listening at http://localhost:3000')
-})
-```
-
-### Server-Sent Events
-
-Because of the nature of compression this module does not work out of the box
-with server-sent events. To compress content, a window of the output needs to
-be buffered up in order to get good compression. Typically when using server-sent
-events, there are certain block of data that need to reach the client.
-
-You can achieve this by calling `res.flush()` when you need the data written to
-actually make it to the client.
-
-```js
-var compression = require('compression')
-var express = require('express')
-
-var app = express()
-
-// compress responses
-app.use(compression())
-
-// server-sent event stream
-app.get('/events', function (req, res) {
-  res.setHeader('Content-Type', 'text/event-stream')
-  res.setHeader('Cache-Control', 'no-cache')
-
-  // send a ping approx every 2 seconds
-  var timer = setInterval(function () {
-    res.write('data: ping\n\n')
-
-    // !!! this is the important part
-    res.flush()
-  }, 2000)
-
-  res.on('close', function () {
-    clearInterval(timer)
-  })
-})
-```
-
-##  Contributing
-
-The Express.js project welcomes all constructive contributions. Contributions take many forms,
-from code for bug fixes and enhancements, to additions and fixes to documentation, additional
-tests, triaging incoming pull requests and issues, and more!
-
-See the [Contributing Guide](https://github.com/expressjs/express/blob/master/Contributing.md) for more technical details on contributing.
-
-## License
-
-[MIT](LICENSE)
-
-[npm-image]: https://badgen.net/npm/v/compression
-[npm-url]: https://npmjs.org/package/compression
-[downloads-image]: https://badgen.net/npm/dm/compression
-[downloads-url]: https://npmcharts.com/compare/compression?minimal=true
-[github-actions-ci-image]: https://badgen.net/github/checks/expressjs/compression/master?label=CI
-[github-actions-ci-url]: https://github.com/expressjs/compression/actions?query=workflow%3Aci
-[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/compression/badge
-[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/compression
-[funding-url]: https://opencollective.com/express
-[funding-image]: https://badgen.net/badge/icon/sponsor/pink?icon=github&label=Open%20Collective
\ No newline at end of file
diff --git a/_includes/readmes/connect-rid.md b/_includes/readmes/connect-rid.md
deleted file mode 100644
index 62c34d3788..0000000000
--- a/_includes/readmes/connect-rid.md
+++ /dev/null
@@ -1,59 +0,0 @@
-> [!CAUTION]
-> **This repository is archived and no longer actively maintained.**
->
-> We are no longer accepting issues, feature requests, or pull requests.
-> For additional support or questions, please visit the [Express.js Discussions page](https://github.com/expressjs/express/discussions).
-
-
-
-connect-rid
-=======
-
-[![Build Status](https://secure.travis-ci.org/fengmk2/connect-rid.png)](http://travis-ci.org/fengmk2/connect-rid) [![Coverage Status](https://coveralls.io/repos/fengmk2/connect-rid/badge.png)](https://coveralls.io/r/fengmk2/connect-rid) [![Dependency Status](https://gemnasium.com/fengmk2/connect-rid.png)](https://gemnasium.com/fengmk2/connect-rid)
-
-[![NPM](https://nodei.co/npm/connect-rid.png?downloads=true&stars=true)](https://nodei.co/npm/connect-rid/)
-
-![logo](https://raw.github.com/fengmk2/connect-rid/master/logo.png)
-
-connect request id middleware, base on [rid](https://github.com/fengmk2/rid).
-
-## Install
-
-```bash
-$ npm install connect-rid
-```
-
-## Usage
-
-```js
-var rid = require('connect-rid');
-
-app.use(rid({
-  // headerName: 'X-RID'
-}));
-```
-
-## License
-
-(The MIT License)
-
-Copyright (c) 2014 fengmk2 &lt;fengmk2@gmail.com&gt; and other contributors
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-'Software'), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/_includes/readmes/cookie-parser.md b/_includes/readmes/cookie-parser.md
deleted file mode 100644
index b8ecd7b24e..0000000000
--- a/_includes/readmes/cookie-parser.md
+++ /dev/null
@@ -1,119 +0,0 @@
-# cookie-parser
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Build Status][ci-image]][ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Parse `Cookie` header and populate `req.cookies` with an object keyed by the
-cookie names. Optionally you may enable signed cookie support by passing a
-`secret` string, which assigns `req.secret` so it may be used by other
-middleware.
-
-## Installation
-
-```sh
-$ npm install cookie-parser
-```
-
-## API
-
-```js
-var cookieParser = require('cookie-parser')
-```
-
-### cookieParser(secret, options)
-
-Create a new cookie parser middleware function using the given `secret` and
-`options`.
-
-- `secret` a string or array used for signing cookies. This is optional and if
-  not specified, will not parse signed cookies. If a string is provided, this
-  is used as the secret. If an array is provided, an attempt will be made to
-  unsign the cookie with each secret in order.
-- `options` an object that is passed to `cookie.parse` as the second option. See
-  [cookie](https://www.npmjs.org/package/cookie) for more information.
-  - `decode` a function to decode the value of the cookie
-
-The middleware will parse the `Cookie` header on the request and expose the
-cookie data as the property `req.cookies` and, if a `secret` was provided, as
-the property `req.signedCookies`. These properties are name value pairs of the
-cookie name to cookie value.
-
-When `secret` is provided, this module will unsign and validate any signed cookie
-values and move those name value pairs from `req.cookies` into `req.signedCookies`.
-A signed cookie is a cookie that has a value prefixed with `s:`. Signed cookies
-that fail signature validation will have the value `false` instead of the tampered
-value.
-
-In addition, this module supports special "JSON cookies". These are cookie where
-the value is prefixed with `j:`. When these values are encountered, the value will
-be exposed as the result of `JSON.parse`. If parsing fails, the original value will
-remain.
-
-### cookieParser.JSONCookie(str)
-
-Parse a cookie value as a JSON cookie. This will return the parsed JSON value
-if it was a JSON cookie, otherwise, it will return the passed value.
-
-### cookieParser.JSONCookies(cookies)
-
-Given an object, this will iterate over the keys and call `JSONCookie` on each
-value, replacing the original value with the parsed value. This returns the
-same object that was passed in.
-
-### cookieParser.signedCookie(str, secret)
-
-Parse a cookie value as a signed cookie. This will return the parsed unsigned
-value if it was a signed cookie and the signature was valid. If the value was
-not signed, the original value is returned. If the value was signed but the
-signature could not be validated, `false` is returned.
-
-The `secret` argument can be an array or string. If a string is provided, this
-is used as the secret. If an array is provided, an attempt will be made to
-unsign the cookie with each secret in order.
-
-### cookieParser.signedCookies(cookies, secret)
-
-Given an object, this will iterate over the keys and check if any value is a
-signed cookie. If it is a signed cookie and the signature is valid, the key
-will be deleted from the object and added to the new object that is returned.
-
-The `secret` argument can be an array or string. If a string is provided, this
-is used as the secret. If an array is provided, an attempt will be made to
-unsign the cookie with each secret in order.
-
-## Example
-
-```js
-var express = require('express')
-var cookieParser = require('cookie-parser')
-
-var app = express()
-app.use(cookieParser())
-
-app.get('/', function (req, res) {
-  // Cookies that have not been signed
-  console.log('Cookies: ', req.cookies)
-
-  // Cookies that have been signed
-  console.log('Signed Cookies: ', req.signedCookies)
-})
-
-app.listen(8080)
-
-// curl command that sends an HTTP request with two cookies
-// curl http://127.0.0.1:8080 --cookie "Cho=Kim;Greet=Hello"
-```
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://badgen.net/github/checks/expressjs/cookie-parser/master?label=ci
-[ci-url]: https://github.com/expressjs/cookie-parser/actions?query=workflow%3Aci
-[coveralls-image]: https://badgen.net/coveralls/c/github/expressjs/cookie-parser/master
-[coveralls-url]: https://coveralls.io/r/expressjs/cookie-parser?branch=master
-[npm-downloads-image]: https://badgen.net/npm/dm/cookie-parser
-[npm-url]: https://npmjs.org/package/cookie-parser
-[npm-version-image]: https://badgen.net/npm/v/cookie-parser
diff --git a/_includes/readmes/cookie-session.md b/_includes/readmes/cookie-session.md
deleted file mode 100644
index 13a9d88714..0000000000
--- a/_includes/readmes/cookie-session.md
+++ /dev/null
@@ -1,290 +0,0 @@
-# cookie-session
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Build Status][ci-image]][ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Simple cookie-based session middleware.
-
-A user session can be stored in two main ways with cookies: on the server or on
-the client. This module stores the session data on the client within a cookie,
-while a module like [express-session](https://www.npmjs.com/package/express-session)
-stores only a session identifier on the client within a cookie and stores the
-session data on the server, typically in a database.
-
-The following points can help you choose which to use:
-
-  * `cookie-session` does not require any database / resources on the server side,
-    though the total session data cannot exceed the browser's max cookie size.
-  * `cookie-session` can simplify certain load-balanced scenarios.
-  * `cookie-session` can be used to store a "light" session and include an identifier
-    to look up a database-backed secondary store to reduce database lookups.
-
-**NOTE** This module does not encrypt the session contents in the cookie, only provides
-signing to prevent tampering. The client will be able to read the session data by
-examining the cookie's value. Secret data should not be set in `req.session` without
-encrypting it, or use a server-side session instead.
-
-**NOTE** This module does not prevent session replay, as the expiration set is that
-of the cookie only; if that is a concern of your application, you can store an expiration
-date in `req.session` object and validate it on the server, and implement any other logic
-to extend the session as your application needs.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install cookie-session
-```
-
-## API
-
-```js
-var cookieSession = require('cookie-session')
-var express = require('express')
-
-var app = express()
-
-app.use(cookieSession({
-  name: 'session',
-  keys: [/* secret keys */],
-
-  // Cookie Options
-  maxAge: 24 * 60 * 60 * 1000 // 24 hours
-}))
-```
-
-### cookieSession(options)
-
-Create a new cookie session middleware with the provided options. This middleware
-will attach the property `session` to `req`, which provides an object representing
-the loaded session. This session is either a new session if no valid session was
-provided in the request, or a loaded session from the request.
-
-The middleware will automatically add a `Set-Cookie` header to the response if the
-contents of `req.session` were altered. _Note_ that no `Set-Cookie` header will be
-in the response (and thus no session created for a specific user) unless there are
-contents in the session, so be sure to add something to `req.session` as soon as
-you have identifying information to store for the session.
-
-#### Options
-
-Cookie session accepts these properties in the options object.
-
-##### name
-
-The name of the cookie to set, defaults to `session`.
-
-##### keys
-
-The list of keys to use to sign & verify cookie values, or a configured
-[`Keygrip`](https://www.npmjs.com/package/keygrip) instance. Set cookies are always
-signed with `keys[0]`, while the other keys are valid for verification, allowing
-for key rotation. If a `Keygrip` instance is provided, it can be used to
-change signature parameters like the algorithm of the signature.
-
-##### secret
-
-A string which will be used as single key if `keys` is not provided.
-
-##### Cookie Options
-
-Other options are passed to `cookies.get()` and `cookies.set()` allowing you
-to control security, domain, path, and signing among other settings.
-
-The options can also contain any of the following (for the full list, see
-[cookies module documentation](https://www.npmjs.org/package/cookies#readme):
-
-  - `maxAge`: a number representing the milliseconds from `Date.now()` for expiry
-  - `expires`: a `Date` object indicating the cookie's expiration date (expires at the end of session by default).
-  - `path`: a string indicating the path of the cookie (`/` by default).
-  - `domain`: a string indicating the domain of the cookie (no default).
-  - `partitioned`: a boolean indicating whether to partition the cookie in Chrome for the [CHIPS Update](https://developers.google.com/privacy-sandbox/3pcd/chips) (`false` by default). If this is true, Cookies from embedded sites will be partitioned and only readable from the same top level site from which it was created.
-  - `priority`: a string indicating the cookie priority. This can be set to `'low'`, `'medium'`, or `'high'`.
-  - `sameSite`: a boolean or string indicating whether the cookie is a "same site" cookie (`false` by default). This can be set to `'strict'`, `'lax'`, `'none'`, or `true` (which maps to `'strict'`).
-  - `secure`: a boolean indicating whether the cookie is only to be sent over HTTPS (`false` by default for HTTP, `true` by default for HTTPS). If this is set to `true` and Node.js is not directly over a TLS connection, be sure to read how to [setup Express behind proxies](https://expressjs.com/en/guide/behind-proxies.html) or the cookie may not ever set correctly.
-  - `httpOnly`: a boolean indicating whether the cookie is only to be sent over HTTP(S), and not made available to client JavaScript (`true` by default).
-  - `signed`: a boolean indicating whether the cookie is to be signed (`true` by default).
-  - `overwrite`: a boolean indicating whether to overwrite previously set cookies of the same name (`true` by default).
-
-### req.session
-
-Represents the session for the given request.
-
-#### .isChanged
-
-Is `true` if the session has been changed during the request.
-
-#### .isNew
-
-Is `true` if the session is new.
-
-#### .isPopulated
-
-Determine if the session has been populated with data or is empty.
-
-### req.sessionOptions
-
-Represents the session options for the current request. These options are a
-shallow clone of what was provided at middleware construction and can be
-altered to change cookie setting behavior on a per-request basis.
-
-### Destroying a session
-
-To destroy a session simply set it to `null`:
-
-```js
-req.session = null
-```
-
-### Saving a session
-
-Since the entire contents of the session is kept in a client-side cookie, the
-session is "saved" by writing a cookie out in a `Set-Cookie` response header.
-This is done automatically if there has been a change made to the session when
-the Node.js response headers are being written to the client and the session
-was not destroyed.
-
-## Examples
-
-### Simple view counter example
-
-```js
-var cookieSession = require('cookie-session')
-var express = require('express')
-
-var app = express()
-
-app.set('trust proxy', 1) // trust first proxy
-
-app.use(cookieSession({
-  name: 'session',
-  keys: ['key1', 'key2']
-}))
-
-app.get('/', function (req, res, next) {
-  // Update views
-  req.session.views = (req.session.views || 0) + 1
-
-  // Write response
-  res.end(req.session.views + ' views')
-})
-
-app.listen(3000)
-```
-
-### Per-user sticky max age
-
-```js
-var cookieSession = require('cookie-session')
-var express = require('express')
-
-var app = express()
-
-app.set('trust proxy', 1) // trust first proxy
-
-app.use(cookieSession({
-  name: 'session',
-  keys: ['key1', 'key2']
-}))
-
-// This allows you to set req.session.maxAge to let certain sessions
-// have a different value than the default.
-app.use(function (req, res, next) {
-  req.sessionOptions.maxAge = req.session.maxAge || req.sessionOptions.maxAge
-  next()
-})
-
-// ... your logic here ...
-```
-
-### Extending the session expiration
-
-This module does not send a `Set-Cookie` header if the contents of the session
-have not changed. This means that to extend the expiration of a session in the
-user's browser (in response to user activity, for example) some kind of
-modification to the session needs be made.
-
-```js
-var cookieSession = require('cookie-session')
-var express = require('express')
-
-var app = express()
-
-app.use(cookieSession({
-  name: 'session',
-  keys: ['key1', 'key2']
-}))
-
-// Update a value in the cookie so that the set-cookie will be sent.
-// Only changes every minute so that it's not sent with every request.
-app.use(function (req, res, next) {
-  req.session.nowInMinutes = Math.floor(Date.now() / 60e3)
-  next()
-})
-
-// ... your logic here ...
-```
-
-### Using a custom signature algorithm
-
-This example shows creating a custom `Keygrip` instance as the `keys` option
-to provide keys and additional signature configuration.
-
-```js
-var cookieSession = require('cookie-session')
-var express = require('express')
-var Keygrip = require('keygrip')
-
-var app = express()
-
-app.use(cookieSession({
-  name: 'session',
-  keys: new Keygrip(['key1', 'key2'], 'SHA384', 'base64')
-}))
-
-// ... your logic here ...
-```
-
-## Usage Limitations
-
-### Max Cookie Size
-
-Because the entire session object is encoded and stored in a cookie, it is
-possible to exceed the maximum cookie size limits on different browsers. The
-[RFC6265 specification](https://tools.ietf.org/html/rfc6265#section-6.1)
-recommends that a browser **SHOULD** allow
-
-> At least 4096 bytes per cookie (as measured by the sum of the length of
-> the cookie's name, value, and attributes)
-
-In practice this limit differs slightly across browsers. See a list of
-[browser limits here](http://browsercookielimits.iain.guru). As a rule
-of thumb **don't exceed 4093 bytes per domain**.
-
-If your session object is large enough to exceed a browser limit when encoded,
-in most cases the browser will refuse to store the cookie. This will cause the
-following requests from the browser to either a) not have any session
-information or b) use old session information that was small enough to not
-exceed the cookie limit.
-
-If you find your session object is hitting these limits, it is best to
-consider if  data in your session should be loaded from a database on the
-server instead of transmitted to/from the browser with every request. Or
-move to an [alternative session strategy](https://github.com/expressjs/session#compatible-session-stores)
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://img.shields.io/github/actions/workflow/status/expressjs/cookie-session/ci.yml
-[ci-url]: https://github.com/expressjs/cookie-session/actions?query=workflow%3Aci
-[coveralls-image]: https://img.shields.io/coverallsCoverage/github/expressjs/cookie-session?branch=master
-[coveralls-url]: https://coveralls.io/r/expressjs/cookie-session?branch=master
-[npm-downloads-image]: https://img.shields.io/npm/dw/cookie-session
-[npm-url]: https://npmjs.org/package/cookie-session
-[npm-version-image]:https://img.shields.io/npm/v/cookie-session
\ No newline at end of file
diff --git a/_includes/readmes/cors.md b/_includes/readmes/cors.md
deleted file mode 100644
index 3d206e5b6f..0000000000
--- a/_includes/readmes/cors.md
+++ /dev/null
@@ -1,277 +0,0 @@
-# cors
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Build Status][github-actions-ci-image]][github-actions-ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-CORS is a [Node.js](https://nodejs.org/en/) middleware for [Express](https://expressjs.com/)/[Connect](https://github.com/senchalabs/connect) that sets [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS) response headers. These headers tell browsers which origins can read responses from your server.
-
-> [!IMPORTANT]
-> **How CORS Works:** This package sets response headers—it doesn't block requests. CORS is enforced by browsers: they check the headers and decide if JavaScript can read the response. Non-browser clients (curl, Postman, other servers) ignore CORS entirely. See the [MDN CORS guide](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS) for details.
-
-* [Installation](#installation)
-* [Usage](#usage)
-  * [Simple Usage](#simple-usage-enable-all-cors-requests)
-  * [Enable CORS for a Single Route](#enable-cors-for-a-single-route)
-  * [Configuring CORS](#configuring-cors)
-  * [Configuring CORS w/ Dynamic Origin](#configuring-cors-w-dynamic-origin)
-  * [Enabling CORS Pre-Flight](#enabling-cors-pre-flight)
-  * [Customizing CORS Settings Dynamically per Request](#customizing-cors-settings-dynamically-per-request)
-* [Configuration Options](#configuration-options)
-* [Common Misconceptions](#common-misconceptions)
-* [License](#license)
-* [Original Author](#original-author)
-
-## Installation
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/downloading-and-installing-packages-locally):
-
-```sh
-$ npm install cors
-```
-
-## Usage
-
-### Simple Usage (Enable *All* CORS Requests)
-
-```javascript
-var express = require('express')
-var cors = require('cors')
-var app = express()
-
-// Adds headers: Access-Control-Allow-Origin: *
-app.use(cors())
-
-app.get('/products/:id', function (req, res, next) {
-  res.json({msg: 'Hello'})
-})
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-### Enable CORS for a Single Route
-
-```javascript
-var express = require('express')
-var cors = require('cors')
-var app = express()
-
-// Adds headers: Access-Control-Allow-Origin: *
-app.get('/products/:id', cors(), function (req, res, next) {
-  res.json({msg: 'Hello'})
-})
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-### Configuring CORS
-
-See the [configuration options](#configuration-options) for details.
-
-```javascript
-var express = require('express')
-var cors = require('cors')
-var app = express()
-
-var corsOptions = {
-  origin: 'http://example.com',
-  optionsSuccessStatus: 200 // some legacy browsers (IE11, various SmartTVs) choke on 204
-}
-
-// Adds headers: Access-Control-Allow-Origin: http://example.com, Vary: Origin
-app.get('/products/:id', cors(corsOptions), function (req, res, next) {
-  res.json({msg: 'Hello'})
-})
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-### Configuring CORS w/ Dynamic Origin
-
-This module supports validating the origin dynamically using a function provided
-to the `origin` option. This function will be passed a string that is the origin
-(or `undefined` if the request has no origin), and a `callback` with the signature
-`callback(error, origin)`.
-
-The `origin` argument to the callback can be any value allowed for the `origin`
-option of the middleware, except a function. See the
-[configuration options](#configuration-options) section for more information on all
-the possible value types.
-
-This function is designed to allow the dynamic loading of allowed origin(s) from
-a backing datasource, like a database.
-
-```javascript
-var express = require('express')
-var cors = require('cors')
-var app = express()
-
-var corsOptions = {
-  origin: function (origin, callback) {
-    // db.loadOrigins is an example call to load
-    // a list of origins from a backing database
-    db.loadOrigins(function (error, origins) {
-      callback(error, origins)
-    })
-  }
-}
-
-// Adds headers: Access-Control-Allow-Origin: <matched origin>, Vary: Origin
-app.get('/products/:id', cors(corsOptions), function (req, res, next) {
-  res.json({msg: 'Hello'})
-})
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-### Enabling CORS Pre-Flight
-
-Certain CORS requests are considered 'complex' and require an initial
-`OPTIONS` request (called the "pre-flight request"). An example of a
-'complex' CORS request is one that uses an HTTP verb other than
-GET/HEAD/POST (such as DELETE) or that uses custom headers. To enable
-pre-flighting, you must add a new OPTIONS handler for the route you want
-to support:
-
-```javascript
-var express = require('express')
-var cors = require('cors')
-var app = express()
-
-app.options('/products/:id', cors()) // preflight for DELETE
-app.del('/products/:id', cors(), function (req, res, next) {
-  res.json({msg: 'Hello'})
-})
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-You can also enable pre-flight across-the-board like so:
-
-```javascript
-app.options('*', cors()) // include before other routes
-```
-
-NOTE: When using this middleware as an application level middleware (for
-example, `app.use(cors())`), pre-flight requests are already handled for all
-routes.
-
-### Customizing CORS Settings Dynamically per Request
-
-For APIs that require different CORS configurations for specific routes or requests, you can dynamically generate CORS options based on the incoming request. The `cors` middleware allows you to achieve this by passing a function instead of static options. This function is called for each incoming request and must use the callback pattern to return the appropriate CORS options.
-
-The function accepts:
-1. **`req`**: 
-   - The incoming request object.
-
-2. **`callback(error, corsOptions)`**: 
-   - A function used to return the computed CORS options.
-   - **Arguments**:
-     - **`error`**: Pass `null` if there’s no error, or an error object to indicate a failure.
-     - **`corsOptions`**: An object specifying the CORS policy for the current request.
-
-Here’s an example that handles both public routes and restricted, credential-sensitive routes:
-
-```javascript
-var dynamicCorsOptions = function(req, callback) {
-  var corsOptions;
-  if (req.path.startsWith('/auth/connect/')) {
-    // Access-Control-Allow-Origin: http://mydomain.com, Access-Control-Allow-Credentials: true, Vary: Origin
-    corsOptions = {
-      origin: 'http://mydomain.com',
-      credentials: true
-    };
-  } else {
-    // Access-Control-Allow-Origin: *
-    corsOptions = { origin: '*' };
-  }
-  callback(null, corsOptions);
-};
-
-app.use(cors(dynamicCorsOptions));
-
-app.get('/auth/connect/twitter', function (req, res) {
-  res.send('Hello');
-});
-
-app.get('/public', function (req, res) {
-  res.send('Hello');
-});
-
-app.listen(80, function () {
-  console.log('web server listening on port 80')
-})
-```
-
-## Configuration Options
-
-* `origin`: Configures the **Access-Control-Allow-Origin** CORS header. Possible values:
-  - `Boolean` - set `origin` to `true` to reflect the [request origin](https://datatracker.ietf.org/doc/html/draft-abarth-origin-09), as defined by `req.header('Origin')`, or set it to `false` to disable CORS.
-  - `String` - set `origin` to a specific origin. For example, if you set it to
-    - `"http://example.com"` only requests from "http://example.com" will be allowed.
-    - `"*"` for all domains to be allowed. 
-  - `RegExp` - set `origin` to a regular expression pattern which will be used to test the request origin. If it's a match, the request origin will be reflected. For example the pattern `/example\.com$/` will reflect any request that is coming from an origin ending with "example.com".
-  - `Array` - set `origin` to an array of valid origins. Each origin can be a `String` or a `RegExp`. For example `["http://example1.com", /\.example2\.com$/]` will accept any request from "http://example1.com" or from a subdomain of "example2.com".
-  - `Function` - set `origin` to a function implementing some custom logic. The function takes the request origin as the first parameter and a callback (called as `callback(err, origin)`, where `origin` is a non-function value of the `origin` option) as the second.
-* `methods`: Configures the **Access-Control-Allow-Methods** CORS header. Expects a comma-delimited string (ex: 'GET,PUT,POST') or an array (ex: `['GET', 'PUT', 'POST']`).
-* `allowedHeaders`: Configures the **Access-Control-Allow-Headers** CORS header. Expects a comma-delimited string (ex: 'Content-Type,Authorization') or an array (ex: `['Content-Type', 'Authorization']`). If not specified, defaults to reflecting the headers specified in the request's **Access-Control-Request-Headers** header.
-* `exposedHeaders`: Configures the **Access-Control-Expose-Headers** CORS header. Expects a comma-delimited string (ex: 'Content-Range,X-Content-Range') or an array (ex: `['Content-Range', 'X-Content-Range']`). If not specified, no custom headers are exposed.
-* `credentials`: Configures the **Access-Control-Allow-Credentials** CORS header. Set to `true` to pass the header, otherwise it is omitted.
-* `maxAge`: Configures the **Access-Control-Max-Age** CORS header. Set to an integer to pass the header, otherwise it is omitted.
-* `preflightContinue`: Pass the CORS preflight response to the next handler.
-* `optionsSuccessStatus`: Provides a status code to use for successful `OPTIONS` requests, since some legacy browsers (IE11, various SmartTVs) choke on `204`.
-
-The default configuration is the equivalent of:
-
-```json
-{
-  "origin": "*",
-  "methods": "GET,HEAD,PUT,PATCH,POST,DELETE",
-  "preflightContinue": false,
-  "optionsSuccessStatus": 204
-}
-```
-
-## Common Misconceptions
-
-### "CORS blocks requests from disallowed origins"
-
-**No.** Your server receives and processes every request. CORS headers tell the browser whether JavaScript can read the response—not whether the request is allowed.
-
-### "CORS protects my API from unauthorized access"
-
-**No.** CORS is not access control. Any HTTP client (curl, Postman, another server) can call your API regardless of CORS settings. Use authentication and authorization to protect your API.
-
-### "Setting `origin: 'http://example.com'` means only that domain can access my server"
-
-**No.** It means browsers will only let JavaScript from that origin read responses. The server still responds to all requests.
-
-## License
-
-[MIT License](http://www.opensource.org/licenses/mit-license.php)
-
-## Original Author
-
-[Troy Goode](https://github.com/TroyGoode) ([troygoode@gmail.com](mailto:troygoode@gmail.com))
-
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/cors/master.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/cors?branch=master
-[downloads-image]: https://img.shields.io/npm/dm/cors.svg
-[downloads-url]: https://npmjs.com/package/cors
-[github-actions-ci-image]: https://img.shields.io/github/actions/workflow/status/expressjs/cors/ci.yml?branch=master&label=ci
-[github-actions-ci-url]: https://github.com/expressjs/cors?query=workflow%3Aci
-[npm-image]: https://img.shields.io/npm/v/cors.svg
-[npm-url]: https://npmjs.com/package/cors
diff --git a/_includes/readmes/errorhandler.md b/_includes/readmes/errorhandler.md
deleted file mode 100644
index 31942ee9eb..0000000000
--- a/_includes/readmes/errorhandler.md
+++ /dev/null
@@ -1,128 +0,0 @@
-# errorhandler
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-<a href="https://github.com/expressjs/errorhandler/actions/workflows/ci.yml"><img src="https://github.com/expressjs/errorhandler/actions/workflows/ci.yml/badge.svg"></a>
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Development-only error handler middleware.
-
-This middleware is only intended to be used in a development environment, as
-the _full error stack traces and internal details of any object passed to this
-module_ will be sent back to the client when an error occurs.
-
-When an object is provided to Express as an error, this module will display
-as much about this object as possible, and will do so by using content negotiation
-for the response between HTML, JSON, and plain text.
-
-  * When the object is a standard `Error` object, the string provided by the
-    `stack` property will be returned in HTML/text responses.
-  * When the object is a non-`Error` object, the result of
-    [util.inspect](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-    will be returned in HTML/text responses.
-  * For JSON responses, the result will be an object with all enumerable properties
-    from the object in the response.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install errorhandler
-```
-
-## API
-
-<!-- eslint-disable no-unused-vars -->
-
-```js
-var errorhandler = require('errorhandler')
-```
-
-### errorhandler(options)
-
-Create new middleware to handle errors and respond with content negotiation.
-
-#### Options
-
-Error handler accepts these properties in the options object.
-
-##### log
-
-Provide a function to be called with the error and a string representation of
-the error. Can be used to write the error to any desired location, or set to
-`false` to only send the error back in the response. Called as
-`log(err, str, req, res)` where `err` is the `Error` object, `str` is a string
-representation of the error, `req` is the request object and `res` is the
-response object (note, this function is invoked _after_ the response has been
-written).
-
-The default value for this option is `true` unless `process.env.NODE_ENV === 'test'`.
-
-Possible values:
-
-  * `true`: Log errors using `console.error(str)`.
-  * `false`: Only send the error back in the response.
-  * A function: pass the error to a function for handling.
-
-## Examples
-
-### Simple example
-
-Basic example of adding this middleware as the error handler only in development
-with `connect` (`express` also can be used in this example).
-
-```js
-var connect = require('connect')
-var errorhandler = require('errorhandler')
-
-var app = connect()
-
-// assumes NODE_ENV is set by the user
-if (process.env.NODE_ENV === 'development') {
-  // only use in development
-  app.use(errorhandler())
-}
-```
-
-### Custom output location
-
-Sometimes you may want to output the errors to a different location than STDERR
-during development, like a system notification, for example.
-
-<!-- eslint-disable handle-callback-err -->
-
-```js
-var connect = require('connect')
-var errorhandler = require('errorhandler')
-var notifier = require('node-notifier')
-
-var app = connect()
-
-// assumes NODE_ENV is set by the user
-if (process.env.NODE_ENV === 'development') {
-  // only use in development
-  app.use(errorhandler({ log: errorNotification }))
-}
-
-function errorNotification (err, str, req) {
-  var title = 'Error in ' + req.method + ' ' + req.url
-
-  notifier.notify({
-    title: title,
-    message: str
-  })
-}
-```
-
-## License
-
-[MIT](LICENSE)
-
-[coveralls-image]: https://badgen.net/coveralls/c/github/expressjs/errorhandler/master
-[coveralls-url]: https://coveralls.io/r/expressjs/errorhandler?branch=master
-[npm-downloads-image]: https://badgen.net/npm/dm/errorhandler
-[npm-url]: https://npmjs.org/package/errorhandler
-[npm-version-image]: https://badgen.net/npm/v/errorhandler
diff --git a/_includes/readmes/express-master/examples.md b/_includes/readmes/express-master/examples.md
deleted file mode 100644
index bd1f1f6310..0000000000
--- a/_includes/readmes/express-master/examples.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Express examples
-
-This page contains list of examples using Express.
-
-- [auth](./auth) - Authentication with login and password
-- [content-negotiation](./content-negotiation) - HTTP content negotiation
-- [cookie-sessions](./cookie-sessions) - Working with cookie-based sessions
-- [cookies](./cookies) - Working with cookies
-- [downloads](./downloads) - Transferring files to client
-- [ejs](./ejs) - Working with Embedded JavaScript templating (ejs)
-- [error-pages](./error-pages) - Creating error pages
-- [error](./error) - Working with error middleware
-- [hello-world](./hello-world) - Simple request handler
-- [markdown](./markdown) - Markdown as template engine
-- [multi-router](./multi-router) - Working with multiple Express routers
-- [mvc](./mvc) - MVC-style controllers
-- [online](./online) - Tracking online user activity with `online` and `redis` packages
-- [params](./params) - Working with route parameters
-- [resource](./resource) - Multiple HTTP operations on the same resource
-- [route-map](./route-map) - Organizing routes using a map
-- [route-middleware](./route-middleware) - Working with route middleware
-- [route-separation](./route-separation) - Organizing routes per each resource
-- [search](./search) - Search API
-- [session](./session) - User sessions
-- [static-files](./static-files) - Serving static files
-- [vhost](./vhost) - Working with virtual hosts
-- [view-constructor](./view-constructor) - Rendering views dynamically
-- [view-locals](./view-locals) - Saving data in request object between middleware calls
-- [web-service](./web-service) - Simple API service
diff --git a/_includes/readmes/method-override.md b/_includes/readmes/method-override.md
deleted file mode 100644
index ce96a96c9e..0000000000
--- a/_includes/readmes/method-override.md
+++ /dev/null
@@ -1,180 +0,0 @@
-# method-override
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Build Status][travis-image]][travis-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Lets you use HTTP verbs such as PUT or DELETE in places where the client doesn't support it.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install method-override
-```
-
-## API
-
-**NOTE** It is very important that this module is used **before** any module that
-needs to know the method of the request (for example, it _must_ be used prior to
-the `csurf` module).
-
-### methodOverride(getter, options)
-
-Create a new middleware function to override the `req.method` property with a new
-value. This value will be pulled from the provided `getter`.
-
-- `getter` - The getter to use to look up the overridden request method for the request. (default: `X-HTTP-Method-Override`)
-- `options.methods` - The allowed methods the original request must be in to check for a method override value. (default: `['POST']`)
-
-If the found method is supported by node.js core, then `req.method` will be set to
-this value, as if it has originally been that value. The previous `req.method`
-value will be stored in `req.originalMethod`.
-
-#### getter
-
-This is the method of getting the override value from the request. If a function is provided,
-the `req` is passed as the first argument, the `res` as the second argument and the method is
-expected to be returned. If a string is provided, the string is used to look up the method
-with the following rules:
-
-- If the string starts with `X-`, then it is treated as the name of a header and that header
-  is used for the method override. If the request contains the same header multiple times, the
-  first occurrence is used.
-- All other strings are treated as a key in the URL query string.
-
-#### options.methods
-
-This allows the specification of what methods(s) the request *MUST* be in in order to check for
-the method override value. This defaults to only `POST` methods, which is the only method the
-override should arrive in. More methods may be specified here, but it may introduce security
-issues and cause weird behavior when requests travel through caches. This value is an array
-of methods in upper-case. `null` can be specified to allow all methods.
-
-## Examples
-
-### override using a header
-
-To use a header to override the method, specify the header name
-as a string argument to the `methodOverride` function. To then make
-the call, send  a `POST` request to a URL with the overridden method
-as the value of that header. This method of using a header would
-typically be used in conjunction with `XMLHttpRequest` on implementations
-that do not support the method you are trying to use.
-
-```js
-const express = require('express')
-const methodOverride = require('method-override')
-const app = express()
-
-// override with the X-HTTP-Method-Override header in the request
-app.use(methodOverride('X-HTTP-Method-Override'))
-```
-
-Example call with header override using `XMLHttpRequest`:
-
-<!-- eslint-env browser -->
-
-```js
-const xhr = new XMLHttpRequest()
-xhr.onload = onload
-xhr.open('post', '/resource', true)
-xhr.setRequestHeader('X-HTTP-Method-Override', 'DELETE')
-xhr.send()
-
-function onload () {
-  alert('got response: ' + this.responseText)
-}
-```
-
-### override using a query value
-
-To use a query string value to override the method, specify the query
-string key as a string argument to the `methodOverride` function. To
-then make the call, send  a `POST` request to a URL with the overridden
-method as the value of that query string key. This method of using a
-query value would typically be used in conjunction with plain HTML
-`<form>` elements when trying to support legacy browsers but still use
-newer methods.
-
-```js
-const express = require('express')
-const methodOverride = require('method-override')
-const app = express()
-
-// override with POST having ?_method=DELETE
-app.use(methodOverride('_method'))
-```
-
-Example call with query override using HTML `<form>`:
-
-```html
-<form method="POST" action="/resource?_method=DELETE">
-  <button type="submit">Delete resource</button>
-</form>
-```
-
-### multiple format support
-
-```js
-const express = require('express')
-const methodOverride = require('method-override')
-const app = express()
-
-// override with different headers; last one takes precedence
-app.use(methodOverride('X-HTTP-Method')) //          Microsoft
-app.use(methodOverride('X-HTTP-Method-Override')) // Google/GData
-app.use(methodOverride('X-Method-Override')) //      IBM
-```
-
-### custom logic
-
-You can implement any kind of custom logic with a function for the `getter`. The following
-implements the logic for looking in `req.body` that was in `method-override@1`:
-
-```js
-const bodyParser = require('body-parser')
-const express = require('express')
-const methodOverride = require('method-override')
-const app = express()
-
-// NOTE: when using req.body, you must fully parse the request body
-//       before you call methodOverride() in your middleware stack,
-//       otherwise req.body will not be populated.
-app.use(bodyParser.urlencoded())
-app.use(methodOverride(function (req, res) {
-  if (req.body && typeof req.body === 'object' && '_method' in req.body) {
-    // look in urlencoded POST bodies and delete it
-    const method = req.body._method
-    delete req.body._method
-    return method
-  }
-}))
-```
-
-Example call with query override using HTML `<form>`:
-
-```html
-<!-- enctype must be set to the type you will parse before methodOverride() -->
-<form method="POST" action="/resource" enctype="application/x-www-form-urlencoded">
-  <input type="hidden" name="_method" value="DELETE">
-  <button type="submit">Delete resource</button>
-</form>
-```
-
-## License
-
-[MIT](LICENSE)
-
-[npm-image]: https://img.shields.io/npm/v/method-override.svg
-[npm-url]: https://npmjs.org/package/method-override
-[travis-image]: https://img.shields.io/travis/expressjs/method-override/master.svg
-[travis-url]: https://travis-ci.org/expressjs/method-override
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/method-override/master.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/method-override?branch=master
-[downloads-image]: https://img.shields.io/npm/dm/method-override.svg
-[downloads-url]: https://npmjs.org/package/method-override
diff --git a/_includes/readmes/morgan.md b/_includes/readmes/morgan.md
deleted file mode 100644
index e384080406..0000000000
--- a/_includes/readmes/morgan.md
+++ /dev/null
@@ -1,440 +0,0 @@
-# morgan
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Build Status][ci-image]][ci-url]
-[![Coverage Status][coveralls-image]][coveralls-url]
-
-HTTP request logger middleware for node.js
-
-> Named after [Dexter](http://en.wikipedia.org/wiki/Dexter_Morgan), a show you should not watch until completion.
-
-## Installation
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install morgan
-```
-
-## API
-
-<!-- eslint-disable no-unused-vars -->
-
-```js
-var morgan = require('morgan')
-```
-
-### morgan(format, options)
-
-Create a new morgan logger middleware function using the given `format` and `options`.
-The `format` argument may be a string of a predefined name (see below for the names),
-a string of a format string, or a function that will produce a log entry.
-
-The `format` function will be called with three arguments `tokens`, `req`, and `res`,
-where `tokens` is an object with all defined tokens, `req` is the HTTP request and `res`
-is the HTTP response. The function is expected to return a string that will be the log
-line, or `undefined` / `null` to skip logging.
-
-#### Using a predefined format string
-
-<!-- eslint-disable no-undef -->
-
-```js
-morgan('tiny')
-```
-
-#### Using format string of predefined tokens
-
-<!-- eslint-disable no-undef -->
-
-```js
-morgan(':method :url :status :res[content-length] - :response-time ms')
-```
-
-#### Using a custom format function
-
-<!-- eslint-disable no-undef -->
-
-``` js
-morgan(function (tokens, req, res) {
-  return [
-    tokens.method(req, res),
-    tokens.url(req, res),
-    tokens.status(req, res),
-    tokens.res(req, res, 'content-length'), '-',
-    tokens['response-time'](req, res), 'ms'
-  ].join(' ')
-})
-```
-
-#### Options
-
-Morgan accepts these properties in the options object.
-
-##### immediate
-
-Write log line on request instead of response. This means that a requests will
-be logged even if the server crashes, _but data from the response (like the
-response code, content length, etc.) cannot be logged_.
-
-##### skip
-
-Function to determine if logging is skipped, defaults to `false`. This function
-will be called as `skip(req, res)`.
-
-<!-- eslint-disable no-undef -->
-
-```js
-// EXAMPLE: only log error responses
-morgan('combined', {
-  skip: function (req, res) { return res.statusCode < 400 }
-})
-```
-
-##### stream
-
-Output stream for writing log lines, defaults to `process.stdout`.
-
-#### Predefined Formats
-
-There are various pre-defined formats provided:
-
-##### combined
-
-Standard Apache combined log output.
-```
-:remote-addr - :remote-user [:date[clf]] ":method :url HTTP/:http-version" :status :res[content-length] ":referrer" ":user-agent"
-# will output
-::1 - - [27/Nov/2024:06:21:42 +0000] "GET /combined HTTP/1.1" 200 2 "-" "curl/8.7.1"
-```
-
-##### common
-
-Standard Apache common log output.
-
-```
-:remote-addr - :remote-user [:date[clf]] ":method :url HTTP/:http-version" :status :res[content-length]
-# will output
-::1 - - [27/Nov/2024:06:21:46 +0000] "GET /common HTTP/1.1" 200 2
-```
-
-##### dev
-
-Concise output colored by response status for development use. The `:status`
-token will be colored green for success codes, red for server error codes,
-yellow for client error codes, cyan for redirection codes, and uncolored
-for information codes.
-
-```
-:method :url :status :response-time ms - :res[content-length]
-# will output
-GET /dev 200 0.224 ms - 2
-```
-
-##### short
-
-Shorter than default, also including response time.
-
-```
-:remote-addr :remote-user :method :url HTTP/:http-version :status :res[content-length] - :response-time ms
-# will output
-::1 - GET /short HTTP/1.1 200 2 - 0.283 ms
-```
-
-##### tiny
-
-The minimal output.
-
-```
-:method :url :status :res[content-length] - :response-time ms
-# will output
-GET /tiny 200 2 - 0.188 ms
-```
-
-#### Tokens
-
-##### Creating new tokens
-
-To define a token, simply invoke `morgan.token()` with the name and a callback function.
-This callback function is expected to return a string value. The value returned is then
-available as ":type" in this case:
-
-<!-- eslint-disable no-undef -->
-
-```js
-morgan.token('type', function (req, res) { return req.headers['content-type'] })
-```
-
-Calling `morgan.token()` using the same name as an existing token will overwrite that
-token definition.
-
-The token function is expected to be called with the arguments `req` and `res`, representing
-the HTTP request and HTTP response. Additionally, the token can accept further arguments of
-it's choosing to customize behavior.
-
-##### :date[format]
-
-The current date and time in UTC. The available formats are:
-
-  - `clf` for the common log format (`"10/Oct/2000:13:55:36 +0000"`)
-  - `iso` for the common ISO 8601 date time format (`2000-10-10T13:55:36.000Z`)
-  - `web` for the common RFC 1123 date time format (`Tue, 10 Oct 2000 13:55:36 GMT`)
-
-If no format is given, then the default is `web`.
-
-##### :http-version
-
-The HTTP version of the request.
-
-##### :method
-
-The HTTP method of the request.
-
-##### :pid
-
-The process ID of the Node.js process handling the request.
-
-##### :referrer
-
-The Referrer header of the request. This will use the standard mis-spelled Referer header if exists, otherwise Referrer.
-
-##### :remote-addr
-
-The remote address of the request. This will use `req.ip`, otherwise the standard `req.connection.remoteAddress` value (socket address).
-
-##### :remote-user
-
-The user authenticated as part of Basic auth for the request.
-
-##### :req[header]
-
-The given `header` of the request. If the header is not present, the
-value will be displayed as `"-"` in the log.
-
-##### :res[header]
-
-The given `header` of the response. If the header is not present, the
-value will be displayed as `"-"` in the log.
-
-##### :response-time[digits]
-
-The time between the request coming into `morgan` and when the response
-headers are written, in milliseconds.
-
-The `digits` argument is a number that specifies the number of digits to
-include on the number, defaulting to `3`, which provides microsecond precision.
-
-##### :status
-
-The status code of the response.
-
-If the request/response cycle completes before a response was sent to the
-client (for example, the TCP socket closed prematurely by a client aborting
-the request), then the status will be empty (displayed as `"-"` in the log).
-
-##### :total-time[digits]
-
-The time between the request coming into `morgan` and when the response
-has finished being written out to the connection, in milliseconds.
-
-The `digits` argument is a number that specifies the number of digits to
-include on the number, defaulting to `3`, which provides microsecond precision.
-
-##### :url
-
-The URL of the request. This will use `req.originalUrl` if exists, otherwise `req.url`.
-
-##### :user-agent
-
-The contents of the User-Agent header of the request.
-
-### morgan.compile(format)
-
-Compile a format string into a `format` function for use by `morgan`. A format string
-is a string that represents a single log line and can utilize token syntax.
-Tokens are references by `:token-name`. If tokens accept arguments, they can
-be passed using `[]`, for example: `:token-name[pretty]` would pass the string
-`'pretty'` as an argument to the token `token-name`.
-
-The function returned from `morgan.compile` takes three arguments `tokens`, `req`, and
-`res`, where `tokens` is object with all defined tokens, `req` is the HTTP request and
-`res` is the HTTP response. The function will return a string that will be the log line,
-or `undefined` / `null` to skip logging.
-
-Normally formats are defined using `morgan.format(name, format)`, but for certain
-advanced uses, this compile function is directly available.
-
-## Examples
-
-### express/connect
-
-Sample app that will log all request in the Apache combined format to STDOUT
-
-```js
-var express = require('express')
-var morgan = require('morgan')
-
-var app = express()
-
-app.use(morgan('combined'))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-### vanilla http server
-
-Sample app that will log all request in the Apache combined format to STDOUT
-
-```js
-var finalhandler = require('finalhandler')
-var http = require('http')
-var morgan = require('morgan')
-
-// create "middleware"
-var logger = morgan('combined')
-
-http.createServer(function (req, res) {
-  var done = finalhandler(req, res)
-  logger(req, res, function (err) {
-    if (err) return done(err)
-
-    // respond to request
-    res.setHeader('content-type', 'text/plain')
-    res.end('hello, world!')
-  })
-})
-```
-
-### write logs to a file
-
-#### single file
-
-Sample app that will log all requests in the Apache combined format to the file
-`access.log`.
-
-```js
-var express = require('express')
-var fs = require('fs')
-var morgan = require('morgan')
-var path = require('path')
-
-var app = express()
-
-// create a write stream (in append mode)
-var accessLogStream = fs.createWriteStream(path.join(__dirname, 'access.log'), { flags: 'a' })
-
-// setup the logger
-app.use(morgan('combined', { stream: accessLogStream }))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-#### log file rotation
-
-Sample app that will log all requests in the Apache combined format to one log
-file per day in the `log/` directory using the
-[rotating-file-stream module](https://www.npmjs.com/package/rotating-file-stream).
-
-```js
-var express = require('express')
-var morgan = require('morgan')
-var path = require('path')
-var rfs = require('rotating-file-stream') // version 2.x
-
-var app = express()
-
-// create a rotating write stream
-var accessLogStream = rfs.createStream('access.log', {
-  interval: '1d', // rotate daily
-  path: path.join(__dirname, 'log')
-})
-
-// setup the logger
-app.use(morgan('combined', { stream: accessLogStream }))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-### split / dual logging
-
-The `morgan` middleware can be used as many times as needed, enabling
-combinations like:
-
-  * Log entry on request and one on response
-  * Log all requests to file, but errors to console
-  * ... and more!
-
-Sample app that will log all requests to a file using Apache format, but
-error responses are logged to the console:
-
-```js
-var express = require('express')
-var fs = require('fs')
-var morgan = require('morgan')
-var path = require('path')
-
-var app = express()
-
-// log only 4xx and 5xx responses to console
-app.use(morgan('dev', {
-  skip: function (req, res) { return res.statusCode < 400 }
-}))
-
-// log all requests to access.log
-app.use(morgan('common', {
-  stream: fs.createWriteStream(path.join(__dirname, 'access.log'), { flags: 'a' })
-}))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-### use custom token formats
-
-Sample app that will use custom token formats. This adds an ID to all requests and displays it using the `:id` token.
-
-```js
-var express = require('express')
-var morgan = require('morgan')
-var uuid = require('node-uuid')
-
-morgan.token('id', function getId (req) {
-  return req.id
-})
-
-var app = express()
-
-app.use(assignId)
-app.use(morgan(':id :method :url :response-time'))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-
-function assignId (req, res, next) {
-  req.id = uuid.v4()
-  next()
-}
-```
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://badgen.net/github/checks/expressjs/morgan/master?label=ci
-[ci-url]: https://github.com/expressjs/morgan/actions/workflows/ci.yml
-[coveralls-image]: https://badgen.net/coveralls/c/github/expressjs/morgan/master
-[coveralls-url]: https://coveralls.io/r/expressjs/morgan?branch=master
-[npm-downloads-image]: https://badgen.net/npm/dm/morgan
-[npm-url]: https://npmjs.org/package/morgan
-[npm-version-image]: https://badgen.net/npm/v/morgan
diff --git a/_includes/readmes/multer.md b/_includes/readmes/multer.md
deleted file mode 100644
index 630a495a1b..0000000000
--- a/_includes/readmes/multer.md
+++ /dev/null
@@ -1,351 +0,0 @@
-# Multer [![NPM Version][npm-version-image]][npm-url] [![NPM Downloads][npm-downloads-image]][npm-url] [![Build Status][ci-image]][ci-url] [![Test Coverage][test-image]][test-url] [![OpenSSF Scorecard Badge][ossf-scorecard-badge]][ossf-scorecard-visualizer]
-
-Multer is a node.js middleware for handling `multipart/form-data`, which is primarily used for uploading files. It is written
-on top of [busboy](https://github.com/mscdex/busboy) for maximum efficiency.
-
-**NOTE**: Multer will not process any form which is not multipart (`multipart/form-data`).
-
-## Translations
-
-This README is also available in other languages:
-
-|                                                                                |                 |
-| ------------------------------------------------------------------------------ | --------------- |
-| [العربية](https://github.com/expressjs/multer/blob/main/doc/README-ar.md)      | Arabic          |
-| [简体中文](https://github.com/expressjs/multer/blob/main/doc/README-zh-cn.md)  | Chinese         |
-| [Français](https://github.com/expressjs/multer/blob/main/doc/README-fr.md)     | French          |
-| [한국어](https://github.com/expressjs/multer/blob/main/doc/README-ko.md)       | Korean          |
-| [Português](https://github.com/expressjs/multer/blob/main/doc/README-pt-br.md) | Portuguese (BR) |
-| [Русский язык](https://github.com/expressjs/multer/blob/main/doc/README-ru.md) | Russian         |
-| [Español](https://github.com/expressjs/multer/blob/main/doc/README-es.md)      | Spanish         |
-| [O'zbek tili](https://github.com/expressjs/multer/blob/main/doc/README-uz.md)  | Uzbek           |
-| [Việt Nam](https://github.com/expressjs/multer/blob/main/doc/README-vi.md)     | Vietnamese      |
-| [Türkçe](https://github.com/expressjs/multer/blob/main/doc/README-tr.md)       | Turkish         |
-
-
-## Installation
-
-```sh
-$ npm install multer
-```
-
-## Usage
-
-Multer adds a `body` object and a `file` or `files` object to the `request` object. The `body` object contains the values of the text fields of the form, the `file` or `files` object contains the files uploaded via the form.
-
-Basic usage example:
-
-Don't forget the `enctype="multipart/form-data"` in your form.
-
-```html
-<form action="/profile" method="post" enctype="multipart/form-data">
-  <input type="file" name="avatar" />
-</form>
-```
-
-```javascript
-const express = require('express')
-const multer  = require('multer')
-const upload = multer({ dest: 'uploads/' })
-
-const app = express()
-
-app.post('/profile', upload.single('avatar'), function (req, res, next) {
-  // req.file is the `avatar` file
-  // req.body will hold the text fields, if there were any
-})
-
-app.post('/photos/upload', upload.array('photos', 12), function (req, res, next) {
-  // req.files is array of `photos` files
-  // req.body will contain the text fields, if there were any
-})
-
-const uploadMiddleware = upload.fields([{ name: 'avatar', maxCount: 1 }, { name: 'gallery', maxCount: 8 }])
-app.post('/cool-profile', uploadMiddleware, function (req, res, next) {
-  // req.files is an object (String -> Array) where fieldname is the key, and the value is array of files
-  //
-  // e.g.
-  //  req.files['avatar'][0] -> File
-  //  req.files['gallery'] -> Array
-  //
-  // req.body will contain the text fields, if there were any
-})
-```
-
-In case you need to handle a text-only multipart form, you should use the `.none()` method:
-
-```javascript
-const express = require('express')
-const app = express()
-const multer  = require('multer')
-const upload = multer()
-
-app.post('/profile', upload.none(), function (req, res, next) {
-  // req.body contains the text fields
-})
-```
-
-Here's an example on how multer is used in a HTML form. Take special note of the `enctype="multipart/form-data"` and `name="uploaded_file"` fields:
-
-```html
-<form action="/stats" enctype="multipart/form-data" method="post">
-  <div class="form-group">
-    <input type="file" class="form-control-file" name="uploaded_file">
-    <input type="text" class="form-control" placeholder="Number of speakers" name="nspeakers">
-    <input type="submit" value="Get me the stats!" class="btn btn-default">
-  </div>
-</form>
-```
-
-Then in your javascript file you would add these lines to access both the file and the body. It is important that you use the `name` field value from the form in your upload function. This tells multer which field on the request it should look for the files in. If these fields aren't the same in the HTML form and on your server, your upload will fail:
-
-```javascript
-const multer  = require('multer')
-const upload = multer({ dest: './public/data/uploads/' })
-app.post('/stats', upload.single('uploaded_file'), function (req, res) {
-  // req.file is the name of your file in the form above, here 'uploaded_file'
-  // req.body will hold the text fields, if there were any
-  console.log(req.file, req.body)
-});
-```
-
-
-
-## API
-
-### File information
-
-Each file contains the following information:
-
-Key | Description | Note
---- | --- | ---
-`fieldname` | Field name specified in the form |
-`originalname` | Name of the file on the user's computer |
-`encoding` | Encoding type of the file |
-`mimetype` | Mime type of the file |
-`size` | Size of the file in bytes |
-`destination` | The folder to which the file has been saved | `DiskStorage`
-`filename` | The name of the file within the `destination` | `DiskStorage`
-`path` | The full path to the uploaded file | `DiskStorage`
-`buffer` | A `Buffer` of the entire file | `MemoryStorage`
-
-### `multer(opts)`
-
-Multer accepts an options object, the most basic of which is the `dest`
-property, which tells Multer where to upload the files. In case you omit the
-options object, the files will be kept in memory and never written to disk.
-
-By default, Multer will rename the files so as to avoid naming conflicts. The
-renaming function can be customized according to your needs.
-
-The following are the options that can be passed to Multer.
-
-Key | Description
---- | ---
-`dest` or `storage` | Where to store the files
-`fileFilter` | Function to control which files are accepted
-`limits` | Limits of the uploaded data
-`preservePath` | Keep the full path of files instead of just the base name
-`defParamCharset` | Default character set to use for values of part header parameters (e.g. filename) that are not extended parameters (that contain an explicit charset). Default: `'latin1'`
-
-In an average web app, only `dest` might be required, and configured as shown in
-the following example.
-
-```javascript
-const upload = multer({ dest: 'uploads/' })
-```
-
-If you want more control over your uploads, you'll want to use the `storage`
-option instead of `dest`. Multer ships with storage engines `DiskStorage`
-and `MemoryStorage`; More engines are available from third parties.
-
-#### `.single(fieldname)`
-
-Accept a single file with the name `fieldname`. The single file will be stored
-in `req.file`.
-
-#### `.array(fieldname[, maxCount])`
-
-Accept an array of files, all with the name `fieldname`. Optionally error out if
-more than `maxCount` files are uploaded. The array of files will be stored in
-`req.files`.
-
-#### `.fields(fields)`
-
-Accept a mix of files, specified by `fields`. An object with arrays of files
-will be stored in `req.files`.
-
-`fields` should be an array of objects with `name` and optionally a `maxCount`.
-Example:
-
-```javascript
-[
-  { name: 'avatar', maxCount: 1 },
-  { name: 'gallery', maxCount: 8 }
-]
-```
-
-#### `.none()`
-
-Accept only text fields. If any file upload is made, error with code
-"LIMIT\_UNEXPECTED\_FILE" will be issued.
-
-#### `.any()`
-
-Accepts all files that comes over the wire. An array of files will be stored in
-`req.files`.
-
-**WARNING:** Make sure that you always handle the files that a user uploads.
-Never add multer as a global middleware since a malicious user could upload
-files to a route that you didn't anticipate. Only use this function on routes
-where you are handling the uploaded files.
-
-### `storage`
-
-#### `DiskStorage`
-
-The disk storage engine gives you full control on storing files to disk.
-
-```javascript
-const storage = multer.diskStorage({
-  destination: function (req, file, cb) {
-    cb(null, '/tmp/my-uploads')
-  },
-  filename: function (req, file, cb) {
-    const uniqueSuffix = Date.now() + '-' + Math.round(Math.random() * 1E9)
-    cb(null, file.fieldname + '-' + uniqueSuffix)
-  }
-})
-
-const upload = multer({ storage: storage })
-```
-
-There are two options available, `destination` and `filename`. They are both
-functions that determine where the file should be stored.
-
-`destination` is used to determine within which folder the uploaded files should
-be stored. This can also be given as a `string` (e.g. `'/tmp/uploads'`). If no
-`destination` is given, the operating system's default directory for temporary
-files is used.
-
-**Note:** You are responsible for creating the directory when providing
-`destination` as a function. When passing a string, multer will make sure that
-the directory is created for you.
-
-`filename` is used to determine what the file should be named inside the folder.
-If no `filename` is given, each file will be given a random name that doesn't
-include any file extension.
-
-**Note:** Multer will not append any file extension for you, your function
-should return a filename complete with a file extension.
-
-Each function gets passed both the request (`req`) and some information about
-the file (`file`) to aid with the decision.
-
-Note that `req.body` might not have been fully populated yet. It depends on the
-order that the client transmits fields and files to the server.
-
-For understanding the calling convention used in the callback (needing to pass
-null as the first param), refer to
-[Node.js error handling](https://web.archive.org/web/20220417042018/https://www.joyent.com/node-js/production/design/errors)
-
-#### `MemoryStorage`
-
-The memory storage engine stores the files in memory as `Buffer` objects. It
-doesn't have any options.
-
-```javascript
-const storage = multer.memoryStorage()
-const upload = multer({ storage: storage })
-```
-
-When using memory storage, the file info will contain a field called
-`buffer` that contains the entire file.
-
-**WARNING**: Uploading very large files, or relatively small files in large
-numbers very quickly, can cause your application to run out of memory when
-memory storage is used.
-
-### `limits`
-
-An object specifying the size limits of the following optional properties. Multer passes this object into busboy directly, and the details of the properties can be found on [busboy's page](https://github.com/mscdex/busboy#busboy-methods).
-
-The following integer values are available:
-
-Key | Description | Default
---- | --- | ---
-`fieldNameSize` | Max field name size | 100 bytes
-`fieldSize` | Max field value size (in bytes) | 1MB
-`fields` | Max number of non-file fields | Infinity
-`fileSize` | For multipart forms, the max file size (in bytes) | Infinity
-`files` | For multipart forms, the max number of file fields | Infinity
-`parts` | For multipart forms, the max number of parts (fields + files) | Infinity
-`headerPairs` | For multipart forms, the max number of header key=>value pairs to parse | 2000
-
-Specifying the limits can help protect your site against denial of service (DoS) attacks.
-
-### `fileFilter`
-
-Set this to a function to control which files should be uploaded and which
-should be skipped. The function should look like this:
-
-```javascript
-function fileFilter (req, file, cb) {
-
-  // The function should call `cb` with a boolean
-  // to indicate if the file should be accepted
-
-  // To reject this file pass `false`, like so:
-  cb(null, false)
-
-  // To accept the file pass `true`, like so:
-  cb(null, true)
-
-  // You can always pass an error if something goes wrong:
-  cb(new Error('I don\'t have a clue!'))
-
-}
-```
-
-## Error handling
-
-When encountering an error, Multer will delegate the error to Express. You can
-display a nice error page using [the standard express way](http://expressjs.com/guide/error-handling.html).
-
-If you want to catch errors specifically from Multer, you can call the
-middleware function by yourself. Also, if you want to catch only [the Multer errors](https://github.com/expressjs/multer/blob/main/lib/multer-error.js), you can use the `MulterError` class that is attached to the `multer` object itself (e.g. `err instanceof multer.MulterError`).
-
-```javascript
-const multer = require('multer')
-const upload = multer().single('avatar')
-
-app.post('/profile', function (req, res) {
-  upload(req, res, function (err) {
-    if (err instanceof multer.MulterError) {
-      // A Multer error occurred when uploading.
-    } else if (err) {
-      // An unknown error occurred when uploading.
-    }
-
-    // Everything went fine.
-  })
-})
-```
-
-## Custom storage engine
-
-For information on how to build your own storage engine, see [Multer Storage Engine](https://github.com/expressjs/multer/blob/main/StorageEngine.md).
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://github.com/expressjs/multer/actions/workflows/ci.yml/badge.svg
-[ci-url]: https://github.com/expressjs/multer/actions/workflows/ci.yml
-[test-url]: https://coveralls.io/r/expressjs/multer?branch=main
-[test-image]: https://badgen.net/coveralls/c/github/expressjs/multer/main
-[npm-downloads-image]: https://badgen.net/npm/dm/multer
-[npm-url]: https://npmjs.org/package/multer
-[npm-version-image]: https://badgen.net/npm/v/multer
-[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/multer/badge
-[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/multer
diff --git a/_includes/readmes/response-time.md b/_includes/readmes/response-time.md
deleted file mode 100644
index 4e26aee0fe..0000000000
--- a/_includes/readmes/response-time.md
+++ /dev/null
@@ -1,142 +0,0 @@
-# response-time
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![Node.js Version][node-image]][node-url]
-[![Build Status][ci-image]][ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Response time for Node.js servers.
-
-This module creates a middleware that records the response time for
-requests in HTTP servers. The "response time" is defined here as the
-elapsed time from when a request enters this middleware to when the
-headers are written out to the client.
-
-## Installation
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install response-time
-```
-
-## API
-
-<!-- eslint-disable no-unused-vars -->
-
-```js
-var responseTime = require('response-time')
-```
-
-### responseTime([options])
-
-Create a middleware that adds a `X-Response-Time` header to responses. If
-you don't want to use this module to automatically set a header, please
-see the section about [`responseTime(fn)`](#responsetimefn).
-
-#### Options
-
-The `responseTime` function accepts an optional `options` object that may
-contain any of the following keys:
-
-##### digits
-
-The fixed number of digits to include in the output, which is always in
-milliseconds, defaults to `3` (ex: `2.300ms`).
-
-##### header
-
-The name of the header to set, defaults to `X-Response-Time`.
-
-##### suffix
-
-Boolean to indicate if units of measurement suffix should be added to
-the output, defaults to `true` (ex: `2.300ms` vs `2.300`).
-
-### responseTime(fn)
-
-Create a new middleware that records the response time of a request and
-makes this available to your own function `fn`. The `fn` argument will be
-invoked as `fn(req, res, time)`, where `time` is a number in milliseconds.
-
-## Examples
-
-### express/connect
-
-```js
-var express = require('express')
-var responseTime = require('response-time')
-
-var app = express()
-
-app.use(responseTime())
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-### vanilla http server
-
-```js
-var finalhandler = require('finalhandler')
-var http = require('http')
-var responseTime = require('response-time')
-
-// create "middleware"
-var _responseTime = responseTime()
-
-http.createServer(function (req, res) {
-  var done = finalhandler(req, res)
-  _responseTime(req, res, function (err) {
-    if (err) return done(err)
-
-    // respond to request
-    res.setHeader('content-type', 'text/plain')
-    res.end('hello, world!')
-  })
-})
-```
-
-### response time metrics
-
-```js
-var express = require('express')
-var responseTime = require('response-time')
-var StatsD = require('node-statsd')
-
-var app = express()
-var stats = new StatsD()
-
-stats.socket.on('error', function (error) {
-  console.error(error.stack)
-})
-
-app.use(responseTime(function (req, res, time) {
-  var stat = (req.method + req.url).toLowerCase()
-    .replace(/[:.]/g, '')
-    .replace(/\//g, '_')
-  stats.timing(stat, time)
-}))
-
-app.get('/', function (req, res) {
-  res.send('hello, world!')
-})
-```
-
-## License
-
-[MIT](LICENSE)
-
-[npm-version-image]: https://badgen.net/npm/v/response-time
-[npm-url]: https://npmjs.org/package/response-time
-[npm-downloads-image]: https://badgen.net/npm/dm/response-time
-[node-image]: https://badgen.net/npm/node/response-time
-[node-url]: https://nodejs.org/en/download
-[ci-image]: https://badgen.net/github/checks/express/response-time/master?label=ci
-[ci-url]: https://github.com/express/response-time/actions/workflows/ci.yml
-[coveralls-image]: https://badgen.net/coveralls/c/github/express/response-time/master
-[coveralls-url]: https://coveralls.io/r/express/response-time?branch=master
diff --git a/_includes/readmes/serve-favicon.md b/_includes/readmes/serve-favicon.md
deleted file mode 100644
index a7f94b4520..0000000000
--- a/_includes/readmes/serve-favicon.md
+++ /dev/null
@@ -1,136 +0,0 @@
-# serve-favicon
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Linux Build Status][ci-image]][ci-url]
-[![Coverage Status][coveralls-image]][coveralls-url]
-[![OpenSSF Scorecard Badge][ossf-scorecard-badge]][ossf-scorecard-visualizer]
-
-Node.js middleware for serving a favicon.
-
-A favicon is a visual cue that client software, like browsers, use to identify
-a site. For an example and more information, please visit
-[the Wikipedia article on favicons](https://en.wikipedia.org/wiki/Favicon).
-
-Why use this module?
-
-  - User agents request `favicon.ico` frequently and indiscriminately, so you
-    may wish to exclude these requests from your logs by using this middleware
-    before your logger middleware.
-  - This module caches the icon in memory to improve performance by skipping
-    disk access.
-  - This module provides an `ETag` based on the contents of the icon, rather
-    than file system properties.
-  - This module will serve with the most compatible `Content-Type`.
-
-**Note** This module is exclusively for serving the "default, implicit favicon",
-which is `GET /favicon.ico`. For additional vendor-specific icons that require
-HTML markup, additional middleware is required to serve the relevant files, for
-example [serve-static](https://npmjs.org/package/serve-static).
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install serve-favicon
-```
-
-## API
-
-### favicon(path, options)
-
-Create new middleware to serve a favicon from the given `path` to a favicon file.
-`path` may also be a `Buffer` of the icon to serve.
-
-#### Options
-
-Serve favicon accepts these properties in the options object.
-
-##### maxAge
-
-The `cache-control` `max-age` directive in `ms`, defaulting to 1 year. This can
-also be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
-module.
-
-## Examples
-
-Typically this middleware will come very early in your stack (maybe even first)
-to avoid processing any other middleware if we already know the request is for
-`/favicon.ico`.
-
-### express
-
-```javascript
-var express = require('express')
-var favicon = require('serve-favicon')
-var path = require('path')
-
-var app = express()
-app.use(favicon(path.join(__dirname, 'public', 'favicon.ico')))
-
-// Add your routes here, etc.
-
-app.listen(3000)
-```
-
-### connect
-
-```javascript
-var connect = require('connect')
-var favicon = require('serve-favicon')
-var path = require('path')
-
-var app = connect()
-app.use(favicon(path.join(__dirname, 'public', 'favicon.ico')))
-
-// Add your middleware here, etc.
-
-app.listen(3000)
-```
-
-### vanilla http server
-
-This middleware can be used anywhere, even outside express/connect. It takes
-`req`, `res`, and `callback`.
-
-```javascript
-var http = require('http')
-var favicon = require('serve-favicon')
-var finalhandler = require('finalhandler')
-var path = require('path')
-
-var _favicon = favicon(path.join(__dirname, 'public', 'favicon.ico'))
-
-var server = http.createServer(function onRequest (req, res) {
-  var done = finalhandler(req, res)
-
-  _favicon(req, res, function onNext (err) {
-    if (err) return done(err)
-
-    // continue to process the request here, etc.
-
-    res.statusCode = 404
-    res.end('oops')
-  })
-})
-
-server.listen(3000)
-```
-
-## License
-
-[MIT](LICENSE)
-
-[ci-image]: https://badgen.net/github/checks/expressjs/serve-favicon/master?label=ci
-[ci-url]: https://github.com/expressjs/serve-favicon/actions/workflows/ci.yml
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/serve-favicon.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/serve-favicon?branch=master
-[downloads-image]: https://img.shields.io/npm/dm/serve-favicon.svg
-[downloads-url]: https://npmjs.org/package/serve-favicon
-[npm-image]: https://img.shields.io/npm/v/serve-favicon.svg
-[npm-url]: https://npmjs.org/package/serve-favicon
-[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/serve-favicon/badge
-[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/serve-favicon
diff --git a/_includes/readmes/serve-index.md b/_includes/readmes/serve-index.md
deleted file mode 100644
index f720b0d950..0000000000
--- a/_includes/readmes/serve-index.md
+++ /dev/null
@@ -1,151 +0,0 @@
-# serve-index
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Linux Build Status][ci-image]][ci-url]
-[![Windows Build][appveyor-image]][appveyor-url]
-[![Coverage Status][coveralls-image]][coveralls-url]
-
-  Serves pages that contain directory listings for a given path.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install serve-index
-```
-
-## API
-
-```js
-var serveIndex = require('serve-index')
-```
-
-### serveIndex(path, options)
-
-Returns middlware that serves an index of the directory in the given `path`.
-
-The `path` is based off the `req.url` value, so a `req.url` of `'/some/dir`
-with a `path` of `'public'` will look at `'public/some/dir'`. If you are using
-something like `express`, you can change the URL "base" with `app.use` (see
-the express example).
-
-#### Options
-
-Serve index accepts these properties in the options object.
-
-##### filter
-
-Apply this filter function to files. Defaults to `false`. The `filter` function
-is called for each file, with the signature `filter(filename, index, files, dir)`
-where `filename` is the name of the file, `index` is the array index, `files` is
-the array of files and `dir` is the absolute path the file is located (and thus,
-the directory the listing is for).
-
-##### hidden
-
-Display hidden (dot) files. Defaults to `false`.
-
-##### icons
-
-Display icons. Defaults to `false`.
-
-##### stylesheet
-
-Optional path to a CSS stylesheet. Defaults to a built-in stylesheet.
-
-##### template
-
-Optional path to an HTML template or a function that will render a HTML
-string. Defaults to a built-in template.
-
-When given a string, the string is used as a file path to load and then the
-following tokens are replaced in templates:
-
-  * `{directory}` with the name of the directory.
-  * `{files}` with the HTML of an unordered list of file links.
-  * `{linked-path}` with the HTML of a link to the directory.
-  * `{style}` with the specified stylesheet and embedded images.
-
-When given as a function, the function is called as `template(locals, callback)`
-and it needs to invoke `callback(error, htmlString)`. The following are the
-provided locals:
-
-  * `directory` is the directory being displayed (where `/` is the root).
-  * `displayIcons` is a Boolean for if icons should be rendered or not.
-  * `fileList` is a sorted array of files in the directory. The array contains
-    objects with the following properties:
-    - `name` is the relative name for the file.
-    - `stat` is a `fs.Stats` object for the file.
-  * `path` is the full filesystem path to `directory`.
-  * `style` is the default stylesheet or the contents of the `stylesheet` option.
-  * `viewName` is the view name provided by the `view` option.
-
-##### view
-
-Display mode. `tiles` and `details` are available. Defaults to `tiles`.
-
-## Examples
-
-### Serve directory indexes with vanilla node.js http server
-
-```js
-var finalhandler = require('finalhandler')
-var http = require('http')
-var serveIndex = require('serve-index')
-var serveStatic = require('serve-static')
-
-// Serve directory indexes for public/ftp folder (with icons)
-var index = serveIndex('public/ftp', {'icons': true})
-
-// Serve up public/ftp folder files
-var serve = serveStatic('public/ftp')
-
-// Create server
-var server = http.createServer(function onRequest(req, res){
-  var done = finalhandler(req, res)
-  serve(req, res, function onNext(err) {
-    if (err) return done(err)
-    index(req, res, done)
-  })
-})
-
-// Listen
-server.listen(3000)
-```
-
-### Serve directory indexes with express
-
-```js
-var express    = require('express')
-var serveIndex = require('serve-index')
-
-var app = express()
-
-// Serve URLs like /ftp/thing as public/ftp/thing
-// The express.static serves the file contents
-// The serveIndex is this module serving the directory
-app.use('/ftp', express.static('public/ftp'), serveIndex('public/ftp', {'icons': true}))
-
-// Listen
-app.listen(3000)
-```
-
-## License
-
-[MIT](LICENSE). The [Silk](http://www.famfamfam.com/lab/icons/silk/) icons
-are created by/copyright of [FAMFAMFAM](http://www.famfamfam.com/).
-
-[appveyor-image]: https://img.shields.io/appveyor/ci/dougwilson/serve-index/master.svg?label=windows
-[appveyor-url]: https://ci.appveyor.com/project/dougwilson/serve-index
-[ci-image]: https://badgen.net/github/checks/expressjs/serve-index/master?label=ci
-[ci-url]: https://github.com/expressjs/serve-index/actions/workflows/ci.yml
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/serve-index/master.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/serve-index?branch=master
-[downloads-image]: https://img.shields.io/npm/dm/serve-index.svg
-[downloads-url]: https://npmjs.org/package/serve-index
-[npm-image]: https://img.shields.io/npm/v/serve-index.svg
-[npm-url]: https://npmjs.org/package/serve-index
\ No newline at end of file
diff --git a/_includes/readmes/serve-static.md b/_includes/readmes/serve-static.md
deleted file mode 100644
index 3ff1f1fa39..0000000000
--- a/_includes/readmes/serve-static.md
+++ /dev/null
@@ -1,253 +0,0 @@
-# serve-static
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][npm-url]
-[![CI][github-actions-ci-image]][github-actions-ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install serve-static
-```
-
-## API
-
-```js
-const serveStatic = require('serve-static')
-```
-
-### serveStatic(root, options)
-
-Create a new middleware function to serve files from within a given root
-directory. The file to serve will be determined by combining `req.url`
-with the provided root directory. When a file is not found, instead of
-sending a 404 response, this module will instead call `next()` to move on
-to the next middleware, allowing for stacking and fall-backs.
-
-#### Options
-
-##### acceptRanges
-
-Enable or disable accepting ranged requests, defaults to true.
-Disabling this will not send `Accept-Ranges` and ignore the contents
-of the `Range` request header.
-
-##### cacheControl
-
-Enable or disable setting `Cache-Control` response header, defaults to
-true. Disabling this will ignore the `immutable` and `maxAge` options.
-
-##### dotfiles
-
-Set how "dotfiles" are treated when encountered. A dotfile is a file
-or directory that begins with a dot ("."). Note this check is done on
-the path itself without checking if the path actually exists on the
-disk. If `root` is specified, only the dotfiles above the root are
-checked (i.e. the root itself can be within a dotfile when set
-to "deny").
-
-  - `'allow'` No special treatment for dotfiles.
-  - `'deny'` Deny a request for a dotfile and 403/`next()`.
-  - `'ignore'` Pretend like the dotfile does not exist and 404/`next()`.
-
-The default value is `'ignore'`.
-
-##### etag
-
-Enable or disable etag generation, defaults to true.
-
-##### extensions
-
-Set file extension fallbacks. When set, if a file is not found, the given
-extensions will be added to the file name and search for. The first that
-exists will be served. Example: `['html', 'htm']`.
-
-The default value is `false`.
-
-##### fallthrough
-
-Set the middleware to have client errors fall-through as just unhandled
-requests, otherwise forward a client error. The difference is that client
-errors like a bad request or a request to a non-existent file will cause
-this middleware to simply `next()` to your next middleware when this value
-is `true`. When this value is `false`, these errors (even 404s), will invoke
-`next(err)`.
-
-Typically `true` is desired such that multiple physical directories can be
-mapped to the same web address or for routes to fill in non-existent files.
-
-The value `false` can be used if this middleware is mounted at a path that
-is designed to be strictly a single file system directory, which allows for
-short-circuiting 404s for less overhead. This middleware will also reply to
-all methods.
-
-The default value is `true`.
-
-##### immutable
-
-Enable or disable the `immutable` directive in the `Cache-Control` response
-header, defaults to `false`. If set to `true`, the `maxAge` option should
-also be specified to enable caching. The `immutable` directive will prevent
-supported clients from making conditional requests during the life of the
-`maxAge` option to check if the file has changed.
-
-##### index
-
-By default this module will send "index.html" files in response to a request
-on a directory. To disable this set `false` or to supply a new index pass a
-string or an array in preferred order.
-
-##### lastModified
-
-Enable or disable `Last-Modified` header, defaults to true. Uses the file
-system's last modified value.
-
-##### maxAge
-
-Provide a max-age in milliseconds for http caching, defaults to 0. This
-can also be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
-module.
-
-##### redirect
-
-Redirect to trailing "/" when the pathname is a dir. Defaults to `true`.
-
-##### setHeaders
-
-Function to set custom headers on response. Alterations to the headers need to
-occur synchronously. The function is called as `fn(res, path, stat)`, where
-the arguments are:
-
-  - `res` the response object
-  - `path` the file path that is being sent
-  - `stat` the stat object of the file that is being sent
-
-## Examples
-
-### Serve files with vanilla node.js http server
-
-```js
-const finalhandler = require('finalhandler')
-const http = require('http')
-const serveStatic = require('serve-static')
-
-// Serve up public/ftp folder
-const serve = serveStatic('public/ftp', { index: ['index.html', 'index.htm'] })
-
-// Create server
-const server = http.createServer((req, res) => {
-  serve(req, res, finalhandler(req, res))
-})
-
-// Listen
-server.listen(3000)
-```
-
-### Serve all files as downloads
-
-```js
-const contentDisposition = require('content-disposition')
-const finalhandler = require('finalhandler')
-const http = require('http')
-const serveStatic = require('serve-static')
-
-// Serve up public/ftp folder
-const serve = serveStatic('public/ftp', {
-  index: false,
-  setHeaders: setHeaders
-})
-
-// Set header to force download
-function setHeaders (res, path) {
-  res.setHeader('Content-Disposition', contentDisposition(path))
-}
-
-// Create server
-const server = http.createServer((req, res) => {
-  serve(req, res, finalhandler(req, res))
-})
-
-// Listen
-server.listen(3000)
-```
-
-### Serving using express
-
-#### Simple
-
-This is a simple example of using Express.
-
-```js
-const express = require('express')
-const serveStatic = require('serve-static')
-
-const app = express()
-
-app.use(serveStatic('public/ftp', { index: ['default.html', 'default.htm'] }))
-app.listen(3000)
-```
-
-#### Multiple roots
-
-This example shows a simple way to search through multiple directories.
-Files are searched for in `public-optimized/` first, then `public/` second
-as a fallback.
-
-```js
-const express = require('express')
-const path = require('path')
-const serveStatic = require('serve-static')
-
-const app = express()
-
-app.use(serveStatic(path.join(__dirname, 'public-optimized')))
-app.use(serveStatic(path.join(__dirname, 'public')))
-app.listen(3000)
-```
-
-#### Different settings for paths
-
-This example shows how to set a different max age depending on the served
-file. In this example, HTML files are not cached, while everything else
-is for 1 day.
-
-```js
-const express = require('express')
-const path = require('path')
-const serveStatic = require('serve-static')
-
-const app = express()
-
-app.use(serveStatic(path.join(__dirname, 'public'), {
-  maxAge: '1d',
-  setHeaders: setCustomCacheControl
-}))
-
-app.listen(3000)
-
-function setCustomCacheControl (res, file) {
-  if (path.extname(file) === '.html') {
-    // Custom Cache-Control for HTML files
-    res.setHeader('Cache-Control', 'public, max-age=0')
-  }
-}
-```
-
-## License
-
-[MIT](LICENSE)
-
-[coveralls-image]: https://badgen.net/coveralls/c/github/expressjs/serve-static/master
-[coveralls-url]: https://coveralls.io/r/expressjs/serve-static?branch=master
-[github-actions-ci-image]: https://badgen.net/github/checks/expressjs/serve-static/master?label=linux
-[github-actions-ci-url]: https://github.com/expressjs/serve-static/actions/workflows/ci.yml
-[node-image]: https://badgen.net/npm/node/serve-static
-[node-url]: https://nodejs.org/en/download/
-[npm-downloads-image]: https://badgen.net/npm/dm/serve-static
-[npm-url]: https://npmjs.org/package/serve-static
-[npm-version-image]: https://badgen.net/npm/v/serve-static
diff --git a/_includes/readmes/session.md b/_includes/readmes/session.md
deleted file mode 100644
index 292b20240e..0000000000
--- a/_includes/readmes/session.md
+++ /dev/null
@@ -1,1061 +0,0 @@
-# express-session
-
-[![NPM Version][npm-version-image]][npm-url]
-[![NPM Downloads][npm-downloads-image]][node-url]
-[![Build Status][ci-image]][ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-## Installation
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install express-session
-```
-
-## API
-
-```js
-var session = require('express-session')
-```
-
-### session(options)
-
-Create a session middleware with the given `options`.
-
-**Note** Session data is _not_ saved in the cookie itself, just the session ID.
-Session data is stored server-side.
-
-**Note** Since version 1.5.0, the [`cookie-parser` middleware](https://www.npmjs.com/package/cookie-parser)
-no longer needs to be used for this module to work. This module now directly reads
-and writes cookies on `req`/`res`. Using `cookie-parser` may result in issues
-if the `secret` is not the same between this module and `cookie-parser`.
-
-**Warning** The default server-side session storage, `MemoryStore`, is _purposely_
-not designed for a production environment. It will leak memory under most
-conditions, does not scale past a single process, and is meant for debugging and
-developing.
-
-For a list of stores, see [compatible session stores](#compatible-session-stores).
-
-#### Options
-
-`express-session` accepts these properties in the options object.
-
-##### cookie
-
-Settings object for the session ID cookie. The default value is
-`{ path: '/', httpOnly: true, secure: false, maxAge: null }`.
-
-In addition to providing a static object, you can also pass a callback function to dynamically generate the cookie options for each request. The callback receives the `req` object as its argument and should return an object containing the cookie settings.
-
-```js
-var app = express()
-app.use(session({
-  secret: 'keyboard cat',
-  resave: false,
-  saveUninitialized: true,
-  cookie: function(req) {
-    var match = req.url.match(/^\/([^/]+)/);
-    return {
-      path: match ? '/' + match[1] : '/',
-      httpOnly: true,
-      secure: req.secure || false,
-      maxAge: 60000
-    }
-  }
-}))
-```
-
-The following are options that can be set in this object.
-
-##### cookie.domain
-
-Specifies the value for the `Domain` `Set-Cookie` attribute. By default, no domain
-is set, and most clients will consider the cookie to apply to only the current
-domain.
-
-##### cookie.expires
-
-Specifies the `Date` object to be the value for the `Expires` `Set-Cookie` attribute.
-By default, no expiration is set, and most clients will consider this a
-"non-persistent cookie" and will delete it on a condition like exiting a web browser
-application.
-
-**Note** If both `expires` and `maxAge` are set in the options, then the last one
-defined in the object is what is used.
-
-**Note** The `expires` option should not be set directly; instead only use the `maxAge`
-option.
-
-##### cookie.httpOnly
-
-Specifies the `boolean` value for the `HttpOnly` `Set-Cookie` attribute. When truthy,
-the `HttpOnly` attribute is set, otherwise it is not. By default, the `HttpOnly`
-attribute is set.
-
-**Note** be careful when setting this to `true`, as compliant clients will not allow
-client-side JavaScript to see the cookie in `document.cookie`.
-
-##### cookie.maxAge
-
-Specifies the `number` (in milliseconds) to use when calculating the `Expires`
-`Set-Cookie` attribute. This is done by taking the current server time and adding
-`maxAge` milliseconds to the value to calculate an `Expires` datetime. By default,
-no maximum age is set.
-
-**Note** If both `expires` and `maxAge` are set in the options, then the last one
-defined in the object is what is used.
-
-##### cookie.partitioned
-
-Specifies the `boolean` value for the [`Partitioned` `Set-Cookie`](rfc-cutler-httpbis-partitioned-cookies)
-attribute. When truthy, the `Partitioned` attribute is set, otherwise it is not.
-By default, the `Partitioned` attribute is not set.
-
-**Note** This is an attribute that has not yet been fully standardized, and may
-change in the future. This also means many clients may ignore this attribute until
-they understand it.
-
-More information about can be found in [the proposal](https://github.com/privacycg/CHIPS).
-
-##### cookie.path
-
-Specifies the value for the `Path` `Set-Cookie`. By default, this is set to `'/'`, which
-is the root path of the domain.
-
-##### cookie.priority
-
-Specifies the `string` to be the value for the [`Priority` `Set-Cookie` attribute][rfc-west-cookie-priority-00-4.1].
-
-  - `'low'` will set the `Priority` attribute to `Low`.
-  - `'medium'` will set the `Priority` attribute to `Medium`, the default priority when not set.
-  - `'high'` will set the `Priority` attribute to `High`.
-
-More information about the different priority levels can be found in
-[the specification][rfc-west-cookie-priority-00-4.1].
-
-**Note** This is an attribute that has not yet been fully standardized, and may change in the future.
-This also means many clients may ignore this attribute until they understand it.
-
-##### cookie.sameSite
-
-Specifies the `boolean` or `string` to be the value for the `SameSite` `Set-Cookie` attribute.
-By default, this is `false`.
-
-  - `true` will set the `SameSite` attribute to `Strict` for strict same site enforcement.
-  - `false` will not set the `SameSite` attribute.
-  - `'lax'` will set the `SameSite` attribute to `Lax` for lax same site enforcement.
-  - `'none'` will set the `SameSite` attribute to `None` for an explicit cross-site cookie.
-  - `'strict'` will set the `SameSite` attribute to `Strict` for strict same site enforcement.
-  - `'auto'` will set the `SameSite` attribute to `None` for secure connections and `Lax` for non-secure connections.
-
-More information about the different enforcement levels can be found in
-[the specification][rfc-6265bis-03-4.1.2.7].
-
-**Note** This is an attribute that has not yet been fully standardized, and may change in
-the future. This also means many clients may ignore this attribute until they understand it.
-
-**Note** There is a [draft spec](https://tools.ietf.org/html/draft-west-cookie-incrementalism-01)
-that requires that the `Secure` attribute be set to `true` when the `SameSite` attribute has been
-set to `'none'`. Some web browsers or other clients may be adopting this specification.
-
-The `cookie.sameSite` option can also be set to the special value `'auto'` to have
-this setting automatically match the determined security of the connection. When the connection
-is secure (HTTPS), the `SameSite` attribute will be set to `None` to enable cross-site usage.
-When the connection is not secure (HTTP), the `SameSite` attribute will be set to `Lax` for
-better security while maintaining functionality. This is useful when the Express `"trust proxy"`
-setting is properly setup to simplify development vs production configuration, particularly
-for SAML authentication scenarios.
-
-##### cookie.secure
-
-Specifies the `boolean` value for the `Secure` `Set-Cookie` attribute. When truthy,
-the `Secure` attribute is set, otherwise it is not. By default, the `Secure`
-attribute is not set.
-
-**Note** be careful when setting this to `true`, as compliant clients will not send
-the cookie back to the server in the future if the browser does not have an HTTPS
-connection.
-
-Please note that `secure: true` is a **recommended** option. However, it requires
-an https-enabled website, i.e., HTTPS is necessary for secure cookies. If `secure`
-is set, and you access your site over HTTP, the cookie will not be set. If you
-have your node.js behind a proxy and are using `secure: true`, you need to set
-"trust proxy" in express:
-
-```js
-var app = express()
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 'keyboard cat',
-  resave: false,
-  saveUninitialized: true,
-  cookie: { secure: true }
-}))
-```
-
-For using secure cookies in production, but allowing for testing in development,
-the following is an example of enabling this setup based on `NODE_ENV` in express:
-
-```js
-var app = express()
-var sess = {
-  secret: 'keyboard cat',
-  cookie: {}
-}
-
-if (app.get('env') === 'production') {
-  app.set('trust proxy', 1) // trust first proxy
-  sess.cookie.secure = true // serve secure cookies
-}
-
-app.use(session(sess))
-```
-
-The `cookie.secure` option can also be set to the special value `'auto'` to have
-this setting automatically match the determined security of the connection. Be
-careful when using this setting if the site is available both as HTTP and HTTPS,
-as once the cookie is set on HTTPS, it will no longer be visible over HTTP. This
-is useful when the Express `"trust proxy"` setting is properly setup to simplify
-development vs production configuration.
-
-##### genid
-
-Function to call to generate a new session ID. Provide a function that returns
-a string that will be used as a session ID. The function is given `req` as the
-first argument if you want to use some value attached to `req` when generating
-the ID.
-
-The default value is a function which uses the `uid-safe` library to generate IDs.
-
-**NOTE** be careful to generate unique IDs so your sessions do not conflict.
-
-```js
-app.use(session({
-  genid: function(req) {
-    return genuuid() // use UUIDs for session IDs
-  },
-  secret: 'keyboard cat'
-}))
-```
-
-##### name
-
-The name of the session ID cookie to set in the response (and read from in the
-request).
-
-The default value is `'connect.sid'`.
-
-**Note** if you have multiple apps running on the same hostname (this is just
-the name, i.e. `localhost` or `127.0.0.1`; different schemes and ports do not
-name a different hostname), then you need to separate the session cookies from
-each other. The simplest method is to simply set different `name`s per app.
-
-##### proxy
-
-Trust the reverse proxy when setting secure cookies (via the "X-Forwarded-Proto"
-header).
-
-The default value is `undefined`.
-
-  - `true` The "X-Forwarded-Proto" header will be used.
-  - `false` All headers are ignored and the connection is considered secure only
-    if there is a direct TLS/SSL connection.
-  - `undefined` Uses the "trust proxy" setting from express
-
-##### resave
-
-Forces the session to be saved back to the session store, even if the session
-was never modified during the request. Depending on your store this may be
-necessary, but it can also create race conditions where a client makes two
-parallel requests to your server and changes made to the session in one
-request may get overwritten when the other request ends, even if it made no
-changes (this behavior also depends on what store you're using).
-
-The default value is `true`, but using the default has been deprecated,
-as the default will change in the future. Please research into this setting
-and choose what is appropriate to your use-case. Typically, you'll want
-`false`.
-
-How do I know if this is necessary for my store? The best way to know is to
-check with your store if it implements the `touch` method. If it does, then
-you can safely set `resave: false`. If it does not implement the `touch`
-method and your store sets an expiration date on stored sessions, then you
-likely need `resave: true`.
-
-##### rolling
-
-Force the session identifier cookie to be set on every response. The expiration
-is reset to the original [`maxAge`](#cookiemaxage), resetting the expiration
-countdown.
-
-The default value is `false`.
-
-With this enabled, the session identifier cookie will expire in
-[`maxAge`](#cookiemaxage) since the last response was sent instead of in
-[`maxAge`](#cookiemaxage) since the session was last modified by the server.
-
-This is typically used in conjunction with short, non-session-length
-[`maxAge`](#cookiemaxage) values to provide a quick timeout of the session data
-with reduced potential of it occurring during on going server interactions.
-
-**Note** When this option is set to `true` but the `saveUninitialized` option is
-set to `false`, the cookie will not be set on a response with an uninitialized
-session. This option only modifies the behavior when an existing session was
-loaded for the request.
-
-##### saveUninitialized
-
-Forces a session that is "uninitialized" to be saved to the store. A session is
-uninitialized when it is new but not modified. Choosing `false` is useful for
-implementing login sessions, reducing server storage usage, or complying with
-laws that require permission before setting a cookie. Choosing `false` will also
-help with race conditions where a client makes multiple parallel requests
-without a session.
-
-The default value is `true`, but using the default has been deprecated, as the
-default will change in the future. Please research into this setting and
-choose what is appropriate to your use-case.
-
-**Note** if you are using Session in conjunction with PassportJS, Passport
-will add an empty Passport object to the session for use after a user is
-authenticated, which will be treated as a modification to the session, causing
-it to be saved. *This has been fixed in PassportJS 0.3.0*
-
-##### secret
-
-**Required option**
-
-This is the secret used to sign the session ID cookie. The secret can be any type
-of value that is supported by Node.js `crypto.createHmac` (like a string or a
-`Buffer`). This can be either a single secret, or an array of multiple secrets. If
-an array of secrets is provided, only the first element will be used to sign the
-session ID cookie, while all the elements will be considered when verifying the
-signature in requests. The secret itself should be not easily parsed by a human and
-would best be a random set of characters. A best practice may include:
-
-  - The use of environment variables to store the secret, ensuring the secret itself
-    does not exist in your repository.
-  - Periodic updates of the secret, while ensuring the previous secret is in the
-    array.
-
-Using a secret that cannot be guessed will reduce the ability to hijack a session to
-only guessing the session ID (as determined by the `genid` option).
-
-Changing the secret value will invalidate all existing sessions. In order to rotate
-the secret without invalidating sessions, provide an array of secrets, with the new
-secret as first element of the array, and including previous secrets as the later
-elements.
-
-**Note** HMAC-256 is used to sign the session ID. For this reason, the secret should
-contain at least 32 bytes of entropy.
-
-##### store
-
-The session store instance, defaults to a new `MemoryStore` instance.
-
-##### unset
-
-Control the result of unsetting `req.session` (through `delete`, setting to `null`,
-etc.).
-
-The default value is `'keep'`.
-
-  - `'destroy'` The session will be destroyed (deleted) when the response ends.
-  - `'keep'` The session in the store will be kept, but modifications made during
-    the request are ignored and not saved.
-
-### req.session
-
-To store or access session data, simply use the request property `req.session`,
-which is (generally) serialized as JSON by the store, so nested objects
-are typically fine. For example below is a user-specific view counter:
-
-```js
-// Use the session middleware
-app.use(session({ secret: 'keyboard cat', cookie: { maxAge: 60000 }}))
-
-// Access the session as req.session
-app.get('/', function(req, res, next) {
-  if (req.session.views) {
-    req.session.views++
-    res.setHeader('Content-Type', 'text/html')
-    res.write('<p>views: ' + req.session.views + '</p>')
-    res.write('<p>expires in: ' + (req.session.cookie.maxAge / 1000) + 's</p>')
-    res.end()
-  } else {
-    req.session.views = 1
-    res.end('welcome to the session demo. refresh!')
-  }
-})
-```
-
-#### Session.regenerate(callback)
-
-To regenerate the session simply invoke the method. Once complete,
-a new SID and `Session` instance will be initialized at `req.session`
-and the `callback` will be invoked.
-
-```js
-req.session.regenerate(function(err) {
-  // will have a new session here
-})
-```
-
-#### Session.destroy(callback)
-
-Destroys the session and will unset the `req.session` property.
-Once complete, the `callback` will be invoked.
-
-```js
-req.session.destroy(function(err) {
-  // cannot access session here
-})
-```
-
-#### Session.reload(callback)
-
-Reloads the session data from the store and re-populates the
-`req.session` object. Once complete, the `callback` will be invoked.
-
-```js
-req.session.reload(function(err) {
-  // session updated
-})
-```
-
-#### Session.save(callback)
-
-Save the session back to the store, replacing the contents on the store with the
-contents in memory (though a store may do something else--consult the store's
-documentation for exact behavior).
-
-This method is automatically called at the end of the HTTP response if the
-session data has been altered (though this behavior can be altered with various
-options in the middleware constructor). Because of this, typically this method
-does not need to be called.
-
-There are some cases where it is useful to call this method, for example,
-redirects, long-lived requests or in WebSockets.
-
-```js
-req.session.save(function(err) {
-  // session saved
-})
-```
-
-#### Session.touch()
-
-Updates the `.maxAge` property. Typically this is
-not necessary to call, as the session middleware does this for you.
-
-### req.session.id
-
-Each session has a unique ID associated with it. This property is an
-alias of [`req.sessionID`](#reqsessionid-1) and cannot be modified.
-It has been added to make the session ID accessible from the `session`
-object.
-
-### req.session.cookie
-
-Each session has a unique cookie object accompany it. This allows
-you to alter the session cookie per visitor. For example we can
-set `req.session.cookie.expires` to `false` to enable the cookie
-to remain for only the duration of the user-agent.
-
-#### Cookie.maxAge
-
-Alternatively `req.session.cookie.maxAge` will return the time
-remaining in milliseconds, which we may also re-assign a new value
-to adjust the `.expires` property appropriately. The following
-are essentially equivalent
-
-```js
-var hour = 3600000
-req.session.cookie.expires = new Date(Date.now() + hour)
-req.session.cookie.maxAge = hour
-```
-
-For example when `maxAge` is set to `60000` (one minute), and 30 seconds
-has elapsed it will return `30000` until the current request has completed,
-at which time `req.session.touch()` is called to reset
-`req.session.cookie.maxAge` to its original value.
-
-```js
-req.session.cookie.maxAge // => 30000
-```
-
-#### Cookie.originalMaxAge
-
-The `req.session.cookie.originalMaxAge` property returns the original
-`maxAge` (time-to-live), in milliseconds, of the session cookie.
-
-### req.sessionID
-
-To get the ID of the loaded session, access the request property
-`req.sessionID`. This is simply a read-only value set when a session
-is loaded/created.
-
-## Session Store Implementation
-
-Every session store _must_ be an `EventEmitter` and implement specific
-methods. The following methods are the list of **required**, **recommended**,
-and **optional**.
-
-  * Required methods are ones that this module will always call on the store.
-  * Recommended methods are ones that this module will call on the store if
-    available.
-  * Optional methods are ones this module does not call at all, but helps
-    present uniform stores to users.
-
-For an example implementation view the [connect-redis](http://github.com/visionmedia/connect-redis) repo.
-
-### store.all(callback)
-
-**Optional**
-
-This optional method is used to get all sessions in the store as an array. The
-`callback` should be called as `callback(error, sessions)`.
-
-### store.destroy(sid, callback)
-
-**Required**
-
-This required method is used to destroy/delete a session from the store given
-a session ID (`sid`). The `callback` should be called as `callback(error)` once
-the session is destroyed.
-
-### store.clear(callback)
-
-**Optional**
-
-This optional method is used to delete all sessions from the store. The
-`callback` should be called as `callback(error)` once the store is cleared.
-
-### store.length(callback)
-
-**Optional**
-
-This optional method is used to get the count of all sessions in the store.
-The `callback` should be called as `callback(error, len)`.
-
-### store.get(sid, callback)
-
-**Required**
-
-This required method is used to get a session from the store given a session
-ID (`sid`). The `callback` should be called as `callback(error, session)`.
-
-The `session` argument should be a session if found, otherwise `null` or
-`undefined` if the session was not found (and there was no error). A special
-case is made when `error.code === 'ENOENT'` to act like `callback(null, null)`.
-
-### store.set(sid, session, callback)
-
-**Required**
-
-This required method is used to upsert a session into the store given a
-session ID (`sid`) and session (`session`) object. The callback should be
-called as `callback(error)` once the session has been set in the store.
-
-### store.touch(sid, session, callback)
-
-**Recommended**
-
-This recommended method is used to "touch" a given session given a
-session ID (`sid`) and session (`session`) object. The `callback` should be
-called as `callback(error)` once the session has been touched.
-
-This is primarily used when the store will automatically delete idle sessions
-and this method is used to signal to the store the given session is active,
-potentially resetting the idle timer.
-
-## Compatible Session Stores
-
-The following modules implement a session store that is compatible with this
-module. Please make a PR to add additional modules :)
-
-[![★][aerospike-session-store-image] aerospike-session-store][aerospike-session-store-url] A session store using [Aerospike](http://www.aerospike.com/).
-
-[aerospike-session-store-url]: https://www.npmjs.com/package/aerospike-session-store
-[aerospike-session-store-image]: https://badgen.net/github/stars/aerospike/aerospike-session-store-expressjs?label=%E2%98%85
-
-[![★][better-sqlite3-session-store-image] better-sqlite3-session-store][better-sqlite3-session-store-url] A session store based on [better-sqlite3](https://github.com/JoshuaWise/better-sqlite3).
-
-[better-sqlite3-session-store-url]: https://www.npmjs.com/package/better-sqlite3-session-store
-[better-sqlite3-session-store-image]: https://badgen.net/github/stars/timdaub/better-sqlite3-session-store?label=%E2%98%85
-
-[![★][cassandra-store-image] cassandra-store][cassandra-store-url] An Apache Cassandra-based session store.
-
-[cassandra-store-url]: https://www.npmjs.com/package/cassandra-store
-[cassandra-store-image]: https://badgen.net/github/stars/webcc/cassandra-store?label=%E2%98%85
-
-[![★][cluster-store-image] cluster-store][cluster-store-url] A wrapper for using in-process / embedded
-stores - such as SQLite (via knex), leveldb, files, or memory - with node cluster (desirable for Raspberry Pi 2
-and other multi-core embedded devices).
-
-[cluster-store-url]: https://www.npmjs.com/package/cluster-store
-[cluster-store-image]: https://badgen.net/github/stars/coolaj86/cluster-store?label=%E2%98%85
-
-[![★][connect-arango-image] connect-arango][connect-arango-url] An ArangoDB-based session store.
-
-[connect-arango-url]: https://www.npmjs.com/package/connect-arango
-[connect-arango-image]: https://badgen.net/github/stars/AlexanderArvidsson/connect-arango?label=%E2%98%85
-
-[![★][connect-azuretables-image] connect-azuretables][connect-azuretables-url] An [Azure Table Storage](https://azure.microsoft.com/en-gb/services/storage/tables/)-based session store.
-
-[connect-azuretables-url]: https://www.npmjs.com/package/connect-azuretables
-[connect-azuretables-image]: https://badgen.net/github/stars/mike-goodwin/connect-azuretables?label=%E2%98%85
-
-[![★][connect-cloudant-store-image] connect-cloudant-store][connect-cloudant-store-url] An [IBM Cloudant](https://cloudant.com/)-based session store.
-
-[connect-cloudant-store-url]: https://www.npmjs.com/package/connect-cloudant-store
-[connect-cloudant-store-image]: https://badgen.net/github/stars/adriantanasa/connect-cloudant-store?label=%E2%98%85
-
-[![★][connect-cosmosdb-image] connect-cosmosdb][connect-cosmosdb-url] An Azure [Cosmos DB](https://azure.microsoft.com/en-us/products/cosmos-db/)-based session store.
-
-[connect-cosmosdb-url]: https://www.npmjs.com/package/connect-cosmosdb
-[connect-cosmosdb-image]: https://badgen.net/github/stars/thekillingspree/connect-cosmosdb?label=%E2%98%85
-
-[![★][connect-couchbase-image] connect-couchbase][connect-couchbase-url] A [couchbase](http://www.couchbase.com/)-based session store.
-
-[connect-couchbase-url]: https://www.npmjs.com/package/connect-couchbase
-[connect-couchbase-image]: https://badgen.net/github/stars/christophermina/connect-couchbase?label=%E2%98%85
-
-[![★][connect-datacache-image] connect-datacache][connect-datacache-url] An [IBM Bluemix Data Cache](http://www.ibm.com/cloud-computing/bluemix/)-based session store.
-
-[connect-datacache-url]: https://www.npmjs.com/package/connect-datacache
-[connect-datacache-image]: https://badgen.net/github/stars/adriantanasa/connect-datacache?label=%E2%98%85
-
-[![★][@google-cloud/connect-datastore-image] @google-cloud/connect-datastore][@google-cloud/connect-datastore-url] A [Google Cloud Datastore](https://cloud.google.com/datastore/docs/concepts/overview)-based session store.
-
-[@google-cloud/connect-datastore-url]: https://www.npmjs.com/package/@google-cloud/connect-datastore
-[@google-cloud/connect-datastore-image]: https://badgen.net/github/stars/GoogleCloudPlatform/cloud-datastore-session-node?label=%E2%98%85
-
-[![★][connect-db2-image] connect-db2][connect-db2-url] An IBM DB2-based session store built using [ibm_db](https://www.npmjs.com/package/ibm_db) module.
-
-[connect-db2-url]: https://www.npmjs.com/package/connect-db2
-[connect-db2-image]: https://badgen.net/github/stars/wallali/connect-db2?label=%E2%98%85
-
-[![★][connect-dynamodb-image] connect-dynamodb][connect-dynamodb-url] A DynamoDB-based session store.
-
-[connect-dynamodb-url]: https://www.npmjs.com/package/connect-dynamodb
-[connect-dynamodb-image]: https://badgen.net/github/stars/ca98am79/connect-dynamodb?label=%E2%98%85
-
-[![★][@google-cloud/connect-firestore-image] @google-cloud/connect-firestore][@google-cloud/connect-firestore-url] A [Google Cloud Firestore](https://cloud.google.com/firestore/docs/overview)-based session store.
-
-[@google-cloud/connect-firestore-url]: https://www.npmjs.com/package/@google-cloud/connect-firestore
-[@google-cloud/connect-firestore-image]: https://badgen.net/github/stars/googleapis/nodejs-firestore-session?label=%E2%98%85
-
-[![★][connect-hazelcast-image] connect-hazelcast][connect-hazelcast-url] Hazelcast session store for Connect and Express.
-
-[connect-hazelcast-url]: https://www.npmjs.com/package/connect-hazelcast
-[connect-hazelcast-image]: https://badgen.net/github/stars/huseyinbabal/connect-hazelcast?label=%E2%98%85
-
-[![★][connect-loki-image] connect-loki][connect-loki-url] A Loki.js-based session store.
-
-[connect-loki-url]: https://www.npmjs.com/package/connect-loki
-[connect-loki-image]: https://badgen.net/github/stars/Requarks/connect-loki?label=%E2%98%85
-
-[![★][connect-lowdb-image] connect-lowdb][connect-lowdb-url] A lowdb-based session store.
-
-[connect-lowdb-url]: https://www.npmjs.com/package/connect-lowdb
-[connect-lowdb-image]: https://badgen.net/github/stars/travishorn/connect-lowdb?label=%E2%98%85
-
-[![★][connect-memcached-image] connect-memcached][connect-memcached-url] A memcached-based session store.
-
-[connect-memcached-url]: https://www.npmjs.com/package/connect-memcached
-[connect-memcached-image]: https://badgen.net/github/stars/balor/connect-memcached?label=%E2%98%85
-
-[![★][connect-memjs-image] connect-memjs][connect-memjs-url] A memcached-based session store using
-[memjs](https://www.npmjs.com/package/memjs) as the memcached client.
-
-[connect-memjs-url]: https://www.npmjs.com/package/connect-memjs
-[connect-memjs-image]: https://badgen.net/github/stars/liamdon/connect-memjs?label=%E2%98%85
-
-[![★][connect-ml-image] connect-ml][connect-ml-url] A MarkLogic Server-based session store.
-
-[connect-ml-url]: https://www.npmjs.com/package/connect-ml
-[connect-ml-image]: https://badgen.net/github/stars/bluetorch/connect-ml?label=%E2%98%85
-
-[![★][connect-monetdb-image] connect-monetdb][connect-monetdb-url] A MonetDB-based session store.
-
-[connect-monetdb-url]: https://www.npmjs.com/package/connect-monetdb
-[connect-monetdb-image]: https://badgen.net/github/stars/MonetDB/npm-connect-monetdb?label=%E2%98%85
-
-[![★][connect-mongo-image] connect-mongo][connect-mongo-url] A MongoDB-based session store.
-
-[connect-mongo-url]: https://www.npmjs.com/package/connect-mongo
-[connect-mongo-image]: https://badgen.net/github/stars/kcbanner/connect-mongo?label=%E2%98%85
-
-[![★][connect-mongodb-session-image] connect-mongodb-session][connect-mongodb-session-url] Lightweight MongoDB-based session store built and maintained by MongoDB.
-
-[connect-mongodb-session-url]: https://www.npmjs.com/package/connect-mongodb-session
-[connect-mongodb-session-image]: https://badgen.net/github/stars/mongodb-js/connect-mongodb-session?label=%E2%98%85
-
-[![★][connect-mssql-v2-image] connect-mssql-v2][connect-mssql-v2-url] A Microsoft SQL Server-based session store based on [connect-mssql](https://www.npmjs.com/package/connect-mssql).
-
-[connect-mssql-v2-url]: https://www.npmjs.com/package/connect-mssql-v2
-[connect-mssql-v2-image]: https://badgen.net/github/stars/jluboff/connect-mssql-v2?label=%E2%98%85
-
-[![★][connect-neo4j-image] connect-neo4j][connect-neo4j-url] A [Neo4j](https://neo4j.com)-based session store.
-
-[connect-neo4j-url]: https://www.npmjs.com/package/connect-neo4j
-[connect-neo4j-image]: https://badgen.net/github/stars/MaxAndersson/connect-neo4j?label=%E2%98%85
-
-[![★][connect-ottoman-image] connect-ottoman][connect-ottoman-url] A [couchbase ottoman](http://www.couchbase.com/)-based session store.
-
-[connect-ottoman-url]: https://www.npmjs.com/package/connect-ottoman
-[connect-ottoman-image]: https://badgen.net/github/stars/noiissyboy/connect-ottoman?label=%E2%98%85
-
-[![★][connect-pg-simple-image] connect-pg-simple][connect-pg-simple-url] A PostgreSQL-based session store.
-
-[connect-pg-simple-url]: https://www.npmjs.com/package/connect-pg-simple
-[connect-pg-simple-image]: https://badgen.net/github/stars/voxpelli/node-connect-pg-simple?label=%E2%98%85
-
-[![★][connect-redis-image] connect-redis][connect-redis-url] A Redis-based session store.
-
-[connect-redis-url]: https://www.npmjs.com/package/connect-redis
-[connect-redis-image]: https://badgen.net/github/stars/tj/connect-redis?label=%E2%98%85
-
-[![★][connect-session-firebase-image] connect-session-firebase][connect-session-firebase-url] A session store based on the [Firebase Realtime Database](https://firebase.google.com/docs/database/)
-
-[connect-session-firebase-url]: https://www.npmjs.com/package/connect-session-firebase
-[connect-session-firebase-image]: https://badgen.net/github/stars/benweier/connect-session-firebase?label=%E2%98%85
-
-[![★][connect-session-knex-image] connect-session-knex][connect-session-knex-url] A session store using
-[Knex.js](http://knexjs.org/), which is a SQL query builder for PostgreSQL, MySQL, MariaDB, SQLite3, and Oracle.
-
-[connect-session-knex-url]: https://www.npmjs.com/package/connect-session-knex
-[connect-session-knex-image]: https://badgen.net/github/stars/llambda/connect-session-knex?label=%E2%98%85
-
-[![★][connect-session-sequelize-image] connect-session-sequelize][connect-session-sequelize-url] A session store using
-[Sequelize.js](http://sequelizejs.com/), which is a Node.js / io.js ORM for PostgreSQL, MySQL, SQLite and MSSQL.
-
-[connect-session-sequelize-url]: https://www.npmjs.com/package/connect-session-sequelize
-[connect-session-sequelize-image]: https://badgen.net/github/stars/mweibel/connect-session-sequelize?label=%E2%98%85
-
-[![★][connect-sqlite3-image] connect-sqlite3][connect-sqlite3-url] A [SQLite3](https://github.com/mapbox/node-sqlite3) session store modeled after the TJ's `connect-redis` store.
-
-[connect-sqlite3-url]: https://www.npmjs.com/package/connect-sqlite3
-[connect-sqlite3-image]: https://badgen.net/github/stars/rawberg/connect-sqlite3?label=%E2%98%85
-
-[![★][connect-typeorm-image] connect-typeorm][connect-typeorm-url] A [TypeORM](https://github.com/typeorm/typeorm)-based session store.
-
-[connect-typeorm-url]: https://www.npmjs.com/package/connect-typeorm
-[connect-typeorm-image]: https://badgen.net/github/stars/makepost/connect-typeorm?label=%E2%98%85
-
-[![★][couchdb-expression-image] couchdb-expression][couchdb-expression-url] A [CouchDB](https://couchdb.apache.org/)-based session store.
-
-[couchdb-expression-url]: https://www.npmjs.com/package/couchdb-expression
-[couchdb-expression-image]: https://badgen.net/github/stars/tkshnwesper/couchdb-expression?label=%E2%98%85
-
-[![★][dynamodb-store-image] dynamodb-store][dynamodb-store-url] A DynamoDB-based session store.
-
-[dynamodb-store-url]: https://www.npmjs.com/package/dynamodb-store
-[dynamodb-store-image]: https://badgen.net/github/stars/rafaelrpinto/dynamodb-store?label=%E2%98%85
-
-[![★][dynamodb-store-v3-image] dynamodb-store-v3][dynamodb-store-v3-url] Implementation of a session store using DynamoDB backed by the [AWS SDK for JavaScript v3](https://github.com/aws/aws-sdk-js-v3).
-
-[dynamodb-store-v3-url]: https://www.npmjs.com/package/dynamodb-store-v3
-[dynamodb-store-v3-image]: https://badgen.net/github/stars/FryDay/dynamodb-store-v3?label=%E2%98%85
-
-[![★][express-etcd-image] express-etcd][express-etcd-url] An [etcd](https://github.com/stianeikeland/node-etcd) based session store.
-
-[express-etcd-url]: https://www.npmjs.com/package/express-etcd
-[express-etcd-image]: https://badgen.net/github/stars/gildean/express-etcd?label=%E2%98%85
-
-[![★][express-mysql-session-image] express-mysql-session][express-mysql-session-url] A session store using native
-[MySQL](https://www.mysql.com/) via the [node-mysql](https://github.com/felixge/node-mysql) module.
-
-[express-mysql-session-url]: https://www.npmjs.com/package/express-mysql-session
-[express-mysql-session-image]: https://badgen.net/github/stars/chill117/express-mysql-session?label=%E2%98%85
-
-[![★][express-nedb-session-image] express-nedb-session][express-nedb-session-url] A NeDB-based session store.
-
-[express-nedb-session-url]: https://www.npmjs.com/package/express-nedb-session
-[express-nedb-session-image]: https://badgen.net/github/stars/louischatriot/express-nedb-session?label=%E2%98%85
-
-[![★][express-oracle-session-image] express-oracle-session][express-oracle-session-url] A session store using native
-[oracle](https://www.oracle.com/) via the [node-oracledb](https://www.npmjs.com/package/oracledb) module.
-
-[express-oracle-session-url]: https://www.npmjs.com/package/express-oracle-session
-[express-oracle-session-image]: https://badgen.net/github/stars/slumber86/express-oracle-session?label=%E2%98%85
-
-[![★][express-session-cache-manager-image] express-session-cache-manager][express-session-cache-manager-url]
-A store that implements [cache-manager](https://www.npmjs.com/package/cache-manager), which supports
-a [variety of storage types](https://www.npmjs.com/package/cache-manager#store-engines).
-
-[express-session-cache-manager-url]: https://www.npmjs.com/package/express-session-cache-manager
-[express-session-cache-manager-image]: https://badgen.net/github/stars/theogravity/express-session-cache-manager?label=%E2%98%85
-
-[![★][express-session-etcd3-image] express-session-etcd3][express-session-etcd3-url] An [etcd3](https://github.com/mixer/etcd3) based session store.
-
-[express-session-etcd3-url]: https://www.npmjs.com/package/express-session-etcd3
-[express-session-etcd3-image]: https://badgen.net/github/stars/willgm/express-session-etcd3?label=%E2%98%85
-
-[![★][express-session-level-image] express-session-level][express-session-level-url] A [LevelDB](https://github.com/Level/levelup) based session store.
-
-[express-session-level-url]: https://www.npmjs.com/package/express-session-level
-[express-session-level-image]: https://badgen.net/github/stars/tgohn/express-session-level?label=%E2%98%85
-
-[![★][express-session-rsdb-image] express-session-rsdb][express-session-rsdb-url] Session store based on Rocket-Store: A very simple, super fast and yet powerful, flat file database.
-
-[express-session-rsdb-url]: https://www.npmjs.com/package/express-session-rsdb
-[express-session-rsdb-image]: https://badgen.net/github/stars/paragi/express-session-rsdb?label=%E2%98%85
-
-[![★][express-sessions-image] express-sessions][express-sessions-url] A session store supporting both MongoDB and Redis.
-
-[express-sessions-url]: https://www.npmjs.com/package/express-sessions
-[express-sessions-image]: https://badgen.net/github/stars/konteck/express-sessions?label=%E2%98%85
-
-[![★][firestore-store-image] firestore-store][firestore-store-url] A [Firestore](https://github.com/hendrysadrak/firestore-store)-based session store.
-
-[firestore-store-url]: https://www.npmjs.com/package/firestore-store
-[firestore-store-image]: https://badgen.net/github/stars/hendrysadrak/firestore-store?label=%E2%98%85
-
-[![★][fortune-session-image] fortune-session][fortune-session-url] A [Fortune.js](https://github.com/fortunejs/fortune)
-based session store. Supports all backends supported by Fortune (MongoDB, Redis, Postgres, NeDB).
-
-[fortune-session-url]: https://www.npmjs.com/package/fortune-session
-[fortune-session-image]: https://badgen.net/github/stars/aliceklipper/fortune-session?label=%E2%98%85
-
-[![★][hazelcast-store-image] hazelcast-store][hazelcast-store-url] A Hazelcast-based session store built on the [Hazelcast Node Client](https://www.npmjs.com/package/hazelcast-client).
-
-[hazelcast-store-url]: https://www.npmjs.com/package/hazelcast-store
-[hazelcast-store-image]: https://badgen.net/github/stars/jackspaniel/hazelcast-store?label=%E2%98%85
-
-[![★][level-session-store-image] level-session-store][level-session-store-url] A LevelDB-based session store.
-
-[level-session-store-url]: https://www.npmjs.com/package/level-session-store
-[level-session-store-image]: https://badgen.net/github/stars/toddself/level-session-store?label=%E2%98%85
-
-[![★][lowdb-session-store-image] lowdb-session-store][lowdb-session-store-url] A [lowdb](https://www.npmjs.com/package/lowdb)-based session store.
-
-[lowdb-session-store-url]: https://www.npmjs.com/package/lowdb-session-store
-[lowdb-session-store-image]: https://badgen.net/github/stars/fhellwig/lowdb-session-store?label=%E2%98%85
-
-[![★][medea-session-store-image] medea-session-store][medea-session-store-url] A Medea-based session store.
-
-[medea-session-store-url]: https://www.npmjs.com/package/medea-session-store
-[medea-session-store-image]: https://badgen.net/github/stars/BenjaminVadant/medea-session-store?label=%E2%98%85
-
-[![★][memorystore-image] memorystore][memorystore-url] A memory session store made for production.
-
-[memorystore-url]: https://www.npmjs.com/package/memorystore
-[memorystore-image]: https://badgen.net/github/stars/roccomuso/memorystore?label=%E2%98%85
-
-[![★][mssql-session-store-image] mssql-session-store][mssql-session-store-url] A SQL Server-based session store.
-
-[mssql-session-store-url]: https://www.npmjs.com/package/mssql-session-store
-[mssql-session-store-image]: https://badgen.net/github/stars/jwathen/mssql-session-store?label=%E2%98%85
-
-[![★][nedb-session-store-image] nedb-session-store][nedb-session-store-url] An alternate NeDB-based (either in-memory or file-persisted) session store.
-
-[nedb-session-store-url]: https://www.npmjs.com/package/nedb-session-store
-[nedb-session-store-image]: https://badgen.net/github/stars/JamesMGreene/nedb-session-store?label=%E2%98%85
-
-[![★][@quixo3/prisma-session-store-image] @quixo3/prisma-session-store][@quixo3/prisma-session-store-url] A session store for the [Prisma Framework](https://www.prisma.io).
-
-[@quixo3/prisma-session-store-url]: https://www.npmjs.com/package/@quixo3/prisma-session-store
-[@quixo3/prisma-session-store-image]: https://badgen.net/github/stars/kleydon/prisma-session-store?label=%E2%98%85
-
-[![★][restsession-image] restsession][restsession-url] Store sessions utilizing a RESTful API
-
-[restsession-url]: https://www.npmjs.com/package/restsession
-[restsession-image]: https://badgen.net/github/stars/jankal/restsession?label=%E2%98%85
-
-[![★][sequelstore-connect-image] sequelstore-connect][sequelstore-connect-url] A session store using [Sequelize.js](http://sequelizejs.com/).
-
-[sequelstore-connect-url]: https://www.npmjs.com/package/sequelstore-connect
-[sequelstore-connect-image]: https://badgen.net/github/stars/MattMcFarland/sequelstore-connect?label=%E2%98%85
-
-[![★][session-file-store-image] session-file-store][session-file-store-url] A file system-based session store.
-
-[session-file-store-url]: https://www.npmjs.com/package/session-file-store
-[session-file-store-image]: https://badgen.net/github/stars/valery-barysok/session-file-store?label=%E2%98%85
-
-[![★][session-pouchdb-store-image] session-pouchdb-store][session-pouchdb-store-url] Session store for PouchDB / CouchDB. Accepts embedded, custom, or remote PouchDB instance and realtime synchronization.
-
-[session-pouchdb-store-url]: https://www.npmjs.com/package/session-pouchdb-store
-[session-pouchdb-store-image]: https://badgen.net/github/stars/solzimer/session-pouchdb-store?label=%E2%98%85
-
-[![★][@cyclic.sh/session-store-image] @cyclic.sh/session-store][@cyclic.sh/session-store-url] A DynamoDB-based session store for [Cyclic.sh](https://www.cyclic.sh/) apps.
-
-[@cyclic.sh/session-store-url]: https://www.npmjs.com/package/@cyclic.sh/session-store
-[@cyclic.sh/session-store-image]: https://badgen.net/github/stars/cyclic-software/session-store?label=%E2%98%85
-
-[![★][@databunker/session-store-image] @databunker/session-store][@databunker/session-store-url] A [Databunker](https://databunker.org/)-based encrypted session store.
-
-[@databunker/session-store-url]: https://www.npmjs.com/package/@databunker/session-store
-[@databunker/session-store-image]: https://badgen.net/github/stars/securitybunker/databunker-session-store?label=%E2%98%85
-
-[![★][sessionstore-image] sessionstore][sessionstore-url] A session store that works with various databases.
-
-[sessionstore-url]: https://www.npmjs.com/package/sessionstore
-[sessionstore-image]: https://badgen.net/github/stars/adrai/sessionstore?label=%E2%98%85
-
-[![★][tch-nedb-session-image] tch-nedb-session][tch-nedb-session-url] A file system session store based on NeDB.
-
-[tch-nedb-session-url]: https://www.npmjs.com/package/tch-nedb-session
-[tch-nedb-session-image]: https://badgen.net/github/stars/tomaschyly/NeDBSession?label=%E2%98%85
-
-## Examples
-
-### View counter
-
-A simple example using `express-session` to store page views for a user.
-
-```js
-var express = require('express')
-var parseurl = require('parseurl')
-var session = require('express-session')
-
-var app = express()
-
-app.use(session({
-  secret: 'keyboard cat',
-  resave: false,
-  saveUninitialized: true
-}))
-
-app.use(function (req, res, next) {
-  if (!req.session.views) {
-    req.session.views = {}
-  }
-
-  // get the url pathname
-  var pathname = parseurl(req).pathname
-
-  // count the views
-  req.session.views[pathname] = (req.session.views[pathname] || 0) + 1
-
-  next()
-})
-
-app.get('/foo', function (req, res, next) {
-  res.send('you viewed this page ' + req.session.views['/foo'] + ' times')
-})
-
-app.get('/bar', function (req, res, next) {
-  res.send('you viewed this page ' + req.session.views['/bar'] + ' times')
-})
-
-app.listen(3000)
-```
-
-### User login
-
-A simple example using `express-session` to keep a user log in session.
-
-```js
-var escapeHtml = require('escape-html')
-var express = require('express')
-var session = require('express-session')
-
-var app = express()
-
-app.use(session({
-  secret: 'keyboard cat',
-  resave: false,
-  saveUninitialized: true
-}))
-
-// middleware to test if authenticated
-function isAuthenticated (req, res, next) {
-  if (req.session.user) next()
-  else next('route')
-}
-
-app.get('/', isAuthenticated, function (req, res) {
-  // this is only called when there is an authentication user due to isAuthenticated
-  res.send('hello, ' + escapeHtml(req.session.user) + '!' +
-    ' <a href="/logout">Logout</a>')
-})
-
-app.get('/', function (req, res) {
-  res.send('<form action="/login" method="post">' +
-    'Username: <input name="user"><br>' +
-    'Password: <input name="pass" type="password"><br>' +
-    '<input type="submit" text="Login"></form>')
-})
-
-app.post('/login', express.urlencoded({ extended: false }), function (req, res) {
-  // login logic to validate req.body.user and req.body.pass
-  // would be implemented here. for this example any combo works
-
-  // regenerate the session, which is good practice to help
-  // guard against forms of session fixation
-  req.session.regenerate(function (err) {
-    if (err) next(err)
-
-    // store user information in session, typically a user id
-    req.session.user = req.body.user
-
-    // save the session before redirection to ensure page
-    // load does not happen before session is saved
-    req.session.save(function (err) {
-      if (err) return next(err)
-      res.redirect('/')
-    })
-  })
-})
-
-app.get('/logout', function (req, res, next) {
-  // logout logic
-
-  // clear the user from the session object and save.
-  // this will ensure that re-using the old session id
-  // does not have a logged in user
-  req.session.user = null
-  req.session.save(function (err) {
-    if (err) next(err)
-
-    // regenerate the session, which is good practice to help
-    // guard against forms of session fixation
-    req.session.regenerate(function (err) {
-      if (err) next(err)
-      res.redirect('/')
-    })
-  })
-})
-
-app.listen(3000)
-```
-
-## Debugging
-
-This module uses the [debug](https://www.npmjs.com/package/debug) module
-internally to log information about session operations.
-
-To see all the internal logs, set the `DEBUG` environment variable to
-`express-session` when launching your app (`npm start`, in this example):
-
-```sh
-$ DEBUG=express-session npm start
-```
-
-On Windows, use the corresponding command;
-
-```sh
-> set DEBUG=express-session & npm start
-```
-
-## License
-
-[MIT](LICENSE)
-
-[rfc-6265bis-03-4.1.2.7]: https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-03#section-4.1.2.7
-[rfc-cutler-httpbis-partitioned-cookies]: https://tools.ietf.org/html/draft-cutler-httpbis-partitioned-cookies/
-[rfc-west-cookie-priority-00-4.1]: https://tools.ietf.org/html/draft-west-cookie-priority-00#section-4.1
-[ci-image]: https://badgen.net/github/checks/expressjs/session/master?label=ci
-[ci-url]: https://github.com/expressjs/session/actions?query=workflow%3Aci
-[coveralls-image]: https://badgen.net/coveralls/c/github/expressjs/session/master
-[coveralls-url]: https://coveralls.io/r/expressjs/session?branch=master
-[node-url]: https://nodejs.org/en/download
-[npm-downloads-image]: https://badgen.net/npm/dm/express-session
-[npm-url]: https://npmjs.org/package/express-session
-[npm-version-image]: https://badgen.net/npm/v/express-session
diff --git a/_includes/readmes/timeout.md b/_includes/readmes/timeout.md
deleted file mode 100644
index 01586dd32c..0000000000
--- a/_includes/readmes/timeout.md
+++ /dev/null
@@ -1,165 +0,0 @@
-# connect-timeout
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Build Status][travis-image]][travis-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-Times out a request in the Connect/Express application framework.
-
-## Install
-
-This is a [Node.js](https://nodejs.org/en/) module available through the
-[npm registry](https://www.npmjs.com/). Installation is done using the
-[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
-
-```sh
-$ npm install connect-timeout
-```
-
-## API
-
-**NOTE** This module is not recommend as a "top-level" middleware (i.e.
-`app.use(timeout('5s'))`) unless you take precautions to halt your own
-middleware processing. See [as top-level middleware](#as-top-level-middleware)
-for how to use as a top-level middleware.
-
-While the library will emit a 'timeout' event when requests exceed the given
-timeout, node will continue processing the slow request until it terminates.
-Slow requests will continue to use CPU and memory, even if you are returning
-a HTTP response in the timeout callback. For better control over CPU/memory,
-you may need to find the events that are taking a long time (3rd party HTTP
-requests, disk I/O, database calls) and find a way to cancel them, and/or
-close the attached sockets.
-
-### timeout(time, [options])
-
-Returns middleware that times out in `time` milliseconds. `time` can also
-be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
-module. On timeout, `req` will emit `"timeout"`.
-
-#### Options
-
-The `timeout` function takes an optional `options` object that may contain
-any of the following keys:
-
-##### respond
-
-Controls if this module will "respond" in the form of forwarding an error.
-If `true`, the timeout error is passed to `next()` so that you may customize
-the response behavior. This error has a `.timeout` property as well as
-`.status == 503`. This defaults to `true`.
-
-### req.clearTimeout()
-
-Clears the timeout on the request. The timeout is completely removed and
-will not fire for this request in the future.
-
-### req.timedout
-
-`true` if timeout fired; `false` otherwise.
-
-## Examples
-
-### as top-level middleware
-
-Because of the way middleware processing works, once this module
-passes the request to the next middleware (which it has to do in order
-for you to do work), it can no longer stop the flow, so you must take
-care to check if the request has timedout before you continue to act
-on the request.
-
-```javascript
-var bodyParser = require('body-parser')
-var cookieParser = require('cookie-parser')
-var express = require('express')
-var timeout = require('connect-timeout')
-
-// example of using this top-level; note the use of haltOnTimedout
-// after every middleware; it will stop the request flow on a timeout
-var app = express()
-app.use(timeout('5s'))
-app.use(bodyParser())
-app.use(haltOnTimedout)
-app.use(cookieParser())
-app.use(haltOnTimedout)
-
-// Add your routes here, etc.
-
-function haltOnTimedout (req, res, next) {
-  if (!req.timedout) next()
-}
-
-app.listen(3000)
-```
-
-### express 3.x
-
-```javascript
-var express = require('express')
-var bodyParser = require('body-parser')
-var timeout = require('connect-timeout')
-
-var app = express()
-app.post('/save', timeout('5s'), bodyParser.json(), haltOnTimedout, function (req, res, next) {
-  savePost(req.body, function (err, id) {
-    if (err) return next(err)
-    if (req.timedout) return
-    res.send('saved as id ' + id)
-  })
-})
-
-function haltOnTimedout (req, res, next) {
-  if (!req.timedout) next()
-}
-
-function savePost (post, cb) {
-  setTimeout(function () {
-    cb(null, ((Math.random() * 40000) >>> 0))
-  }, (Math.random() * 7000) >>> 0)
-}
-
-app.listen(3000)
-```
-
-### connect
-
-```javascript
-var bodyParser = require('body-parser')
-var connect = require('connect')
-var timeout = require('connect-timeout')
-
-var app = connect()
-app.use('/save', timeout('5s'), bodyParser.json(), haltOnTimedout, function (req, res, next) {
-  savePost(req.body, function (err, id) {
-    if (err) return next(err)
-    if (req.timedout) return
-    res.send('saved as id ' + id)
-  })
-})
-
-function haltOnTimedout (req, res, next) {
-  if (!req.timedout) next()
-}
-
-function savePost (post, cb) {
-  setTimeout(function () {
-    cb(null, ((Math.random() * 40000) >>> 0))
-  }, (Math.random() * 7000) >>> 0)
-}
-
-app.listen(3000)
-```
-
-## License
-
-[MIT](LICENSE)
-
-[npm-image]: https://img.shields.io/npm/v/connect-timeout.svg
-[npm-url]: https://npmjs.org/package/connect-timeout
-[travis-image]: https://img.shields.io/travis/expressjs/timeout/master.svg
-[travis-url]: https://travis-ci.org/expressjs/timeout
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/timeout/master.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/timeout?branch=master
-[downloads-image]: https://img.shields.io/npm/dm/connect-timeout.svg
-[downloads-url]: https://npmjs.org/package/connect-timeout
diff --git a/_includes/readmes/vhost.md b/_includes/readmes/vhost.md
deleted file mode 100644
index 422e67f476..0000000000
--- a/_includes/readmes/vhost.md
+++ /dev/null
@@ -1,163 +0,0 @@
-# vhost
-
-[![NPM Version][npm-image]][npm-url]
-[![NPM Downloads][downloads-image]][downloads-url]
-[![Build Status][github-actions-ci-image]][github-actions-ci-url]
-[![Test Coverage][coveralls-image]][coveralls-url]
-
-## Install
-
-```sh
-$ npm install vhost
-```
-
-## API
-
-```js
-var vhost = require('vhost')
-```
-
-### vhost(hostname, handle)
-
-Create a new middleware function to hand off request to `handle` when the incoming
-host for the request matches `hostname`. The function is called as
-`handle(req, res, next)`, like a standard middleware.
-
-`hostname` can be a string or a RegExp object. When `hostname` is a string it can
-contain `*` to match 1 or more characters in that section of the hostname. When
-`hostname` is a RegExp, it will be forced to case-insensitive (since hostnames are)
-and will be forced to match based on the start and end of the hostname.
-
-When host is matched and the request is sent down to a vhost handler, the `req.vhost`
-property will be populated with an object. This object will have numeric properties
-corresponding to each wildcard (or capture group if RegExp object provided) and the
-`hostname` that was matched.
-
-```js
-var connect = require('connect')
-var vhost = require('vhost')
-var app = connect()
-
-app.use(vhost('*.*.example.com', function handle (req, res, next) {
-  // for match of "foo.bar.example.com:8080" against "*.*.example.com":
-  console.dir(req.vhost.host) // => 'foo.bar.example.com:8080'
-  console.dir(req.vhost.hostname) // => 'foo.bar.example.com'
-  console.dir(req.vhost.length) // => 2
-  console.dir(req.vhost[0]) // => 'foo'
-  console.dir(req.vhost[1]) // => 'bar'
-}))
-```
-
-## Examples
-
-### using with connect for static serving
-
-```js
-var connect = require('connect')
-var serveStatic = require('serve-static')
-var vhost = require('vhost')
-
-var mailapp = connect()
-
-// add middlewares to mailapp for mail.example.com
-
-// create app to serve static files on subdomain
-var staticapp = connect()
-staticapp.use(serveStatic('public'))
-
-// create main app
-var app = connect()
-
-// add vhost routing to main app for mail
-app.use(vhost('mail.example.com', mailapp))
-
-// route static assets for "assets-*" subdomain to get
-// around max host connections limit on browsers
-app.use(vhost('assets-*.example.com', staticapp))
-
-// add middlewares and main usage to app
-
-app.listen(3000)
-```
-
-### using with connect for user subdomains
-
-```js
-var connect = require('connect')
-var serveStatic = require('serve-static')
-var vhost = require('vhost')
-
-var mainapp = connect()
-
-// add middlewares to mainapp for the main web site
-
-// create app that will server user content from public/{username}/
-var userapp = connect()
-
-userapp.use(function (req, res, next) {
-  var username = req.vhost[0] // username is the "*"
-
-  // pretend request was for /{username}/* for file serving
-  req.originalUrl = req.url
-  req.url = '/' + username + req.url
-
-  next()
-})
-userapp.use(serveStatic('public'))
-
-// create main app
-var app = connect()
-
-// add vhost routing for main app
-app.use(vhost('userpages.local', mainapp))
-app.use(vhost('www.userpages.local', mainapp))
-
-// listen on all subdomains for user pages
-app.use(vhost('*.userpages.local', userapp))
-
-app.listen(3000)
-```
-
-### using with any generic request handler
-
-```js
-var connect = require('connect')
-var http = require('http')
-var vhost = require('vhost')
-
-// create main app
-var app = connect()
-
-app.use(vhost('mail.example.com', function (req, res) {
-  // handle req + res belonging to mail.example.com
-  res.setHeader('Content-Type', 'text/plain')
-  res.end('hello from mail!')
-}))
-
-// an external api server in any framework
-var httpServer = http.createServer(function (req, res) {
-  res.setHeader('Content-Type', 'text/plain')
-  res.end('hello from the api!')
-})
-
-app.use(vhost('api.example.com', function (req, res) {
-  // handle req + res belonging to api.example.com
-  // pass the request to a standard Node.js HTTP server
-  httpServer.emit('request', req, res)
-}))
-
-app.listen(3000)
-```
-
-## License
-
-[MIT](LICENSE)
-
-[npm-image]: https://img.shields.io/npm/v/vhost.svg
-[npm-url]: https://npmjs.org/package/vhost
-[coveralls-image]: https://img.shields.io/coveralls/expressjs/vhost/master.svg
-[coveralls-url]: https://coveralls.io/r/expressjs/vhost
-[downloads-image]: https://img.shields.io/npm/dm/vhost.svg
-[downloads-url]: https://npmjs.org/package/vhost
-[github-actions-ci-image]: https://img.shields.io/github/actions/workflow/status/expressjs/vhost/ci.yml?branch=master&label=ci
-[github-actions-ci-url]: https://github.com/expressjs/vhost/actions/workflows/ci.yml
diff --git a/_includes/util-list.md b/_includes/util-list.md
deleted file mode 100644
index 8abc5d6a5d..0000000000
--- a/_includes/util-list.md
+++ /dev/null
@@ -1,38 +0,0 @@
-## Utility modules in jshttp
-
-- [negotiator](/{{page.lang}}/resources/utils/negotiator.html)
-- [cookie](/{{page.lang}}/resources/utils/cookie.html)
-- [fresh](/{{page.lang}}/resources/utils/fresh.html)
-- [range-parser](/{{page.lang}}/resources/utils/range-parser.html)
-- [methods](/{{page.lang}}/resources/utils/methods.html)
-- [basic-auth](/{{page.lang}}/resources/utils/basic-auth.html)
-- [compressible](/{{page.lang}}/resources/utils/compressible.html)
-- [on-finished](/{{page.lang}}/resources/utils/on-finished.html)
-- [http-assert](/{{page.lang}}/resources/utils/http-assert.html)
-- [accepts](/{{page.lang}}/resources/utils/accepts.html)
-- [type-is](/{{page.lang}}/resources/utils/type-is.html)
-- [statuses](/{{page.lang}}/resources/utils/statuses.html)
-- [mime-types](/{{page.lang}}/resources/utils/mime-types.html)
-- [proxy-addr](/{{page.lang}}/resources/utils/proxy-addr.html)
-- [on-headers](/{{page.lang}}/resources/utils/on-headers.html)
-- [vary](/{{page.lang}}/resources/utils/vary.html)
-- [media-typer](/{{page.lang}}/resources/utils/media-typer.html)
-- [etag](/{{page.lang}}/resources/utils/etag.html)
-- [mime-db](/{{page.lang}}/resources/utils/mime-db.html)
-- [http-/{{page.lang}}/resources/utils](/{{page.lang}}/resources/utils/http-/{{page.lang}}/resources/utils.html)
-- [spdy-push](/{{page.lang}}/resources/utils/spdy-push.html)
-- [http-errors](/{{page.lang}}/resources/utils/http-errors.html)
-- [content-disposition](/{{page.lang}}/resources/utils/content-disposition.html)
-- [forwarded](/{{page.lang}}/resources/utils/forwarded.html)
-- [content-type](/{{page.lang}}/resources/utils/content-type.html)
-
-## Utility modules in pillarjs
-
-- [cookies](/{{page.lang}}/resources/utils/cookies.html)
-- [csrf](/{{page.lang}}/resources/utils/csrf.html)
-- [finalhandler](/{{page.lang}}/resources/utils/finalhandler.html)
-- [parseurl](/{{page.lang}}/resources/utils/parseurl.html)
-- [path-to-regexp](/{{page.lang}}/resources/utils/path-to-regexp.html)
-- [resolve-path](/{{page.lang}}/resources/utils/resolve-path.html)
-- [router](/{{page.lang}}/resources/utils/router.html)
-- [send](/{{page.lang}}/resources/utils/send.html)
diff --git a/_layouts/404.html b/_layouts/404.html
deleted file mode 100644
index 84f18bfff3..0000000000
--- a/_layouts/404.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<!DOCTYPE html>
-
-<html lang="en">
-  {% include head.html %}
-
-  {% if page.lang == 'en' %}
-  <body class="en-doc">
-  {% else %}
-  <body class="non-en-doc">
-  {% endif %}
-    {% include header.html %}
-    <div id="overlay"></div>
-    <main class="content-404">
-      {{ content }}
-    </main>
-    {% include footer.html %}
-  </body>
-</html>
\ No newline at end of file
diff --git a/_layouts/api.html b/_layouts/api.html
deleted file mode 100644
index 6e01f7f6cd..0000000000
--- a/_layouts/api.html
+++ /dev/null
@@ -1,27 +0,0 @@
-<!DOCTYPE html>
-<html lang="{{ page.lang }}">
-
-  {% include head.html %}
-
-  <body>
-    {% include header.html %}
-    <div id="overlay"></div>
-
-    <div class="content">
-      <nav aria-labelledby="sidebar-heading">
-        <div class="toc-container">
-          <h3 id="sidebar-heading" class="toc-heading"><em>On this page</em></h3>
-          {% include api/en/{{page.version}}/menu.md %}
-        </div>
-      </nav>
-      <main>
-        {{ content }}
-        {% include github-edit-btn.html %}
-      </main>
-    </div>
-
-    {% include footer.html %}
-
-  </body>
-
-</html>
diff --git a/_layouts/feed.xml b/_layouts/feed.xml
deleted file mode 100644
index 09a7aab788..0000000000
--- a/_layouts/feed.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
-  <title type="text">{{ page.title }}</title>
-  <link href="{{ site.url }}{{ page.html_url }}" rel="alternate" type="text/html" />
-  <link href="{{ site.url }}{{ page.url }}" rel="self" type="application/atom+xml" />
-  <id>{{ site.url }}{{ page.url }}</id>
-  <rights>Copyright The Express Contributors</rights>
-  <updated>{{ site.time | date_to_xmlschema }}</updated>
-  {{ content }}
-</feed>
diff --git a/_layouts/home.html b/_layouts/home.html
deleted file mode 100644
index 8d5abafc95..0000000000
--- a/_layouts/home.html
+++ /dev/null
@@ -1,29 +0,0 @@
-<!DOCTYPE html>
-<html class="light-mode" lang="{{ page.lang }}">
-
-  {% include head.html %}
-
-  {% if page.lang == 'en' %}
-  <body class="en-doc">
-  {% else %}
-  <body class="non-en-doc">
-  {% endif %}
-
-    {% include header.html %}
-
-    <div id="overlay"></div>
-
-    {% if page.lang != 'en' %}
-        <div id="i18n-notice-box" class="doc-notice" hidden>
-          {% include i18n-notice.html %}
-        </div>
-    {% endif %}
-
-    <main class="home">
-      {{ content }}
-    </main>
-
-    {% include footer.html %}
-  </body>
-
-</html>
diff --git a/_layouts/middleware.html b/_layouts/middleware.html
deleted file mode 100644
index 07c9a7e66c..0000000000
--- a/_layouts/middleware.html
+++ /dev/null
@@ -1,39 +0,0 @@
----
-layout: page
----
-
-<nav aria-labelledby="sidebar-heading">
-  <div class="toc-container">
-    <h3 id="sidebar-heading" class="toc-heading"><em>Middlewares</em></h3>
-    <button id="menu-toggle" title="show express middlewares">Middlewares <span>&#x25BA;</span></button>
-    <ul id="menu">
-        {% if page.title contains 'middleware' %}
-          {% capture readme %}{% include mw-list.md %}{% endcapture %}
-        {% else %}
-          {% capture readme %}{% include util-list.md %}{% endcapture %}
-        {% endif %}
-        {{ readme | markdownify }}
-    </ul>
-  </div>
-</nav>
-
-<main id="page-doc">
-    {% if page.module == 'mw-home' %}    
-      {{content}} 
-      
-    {% elsif page.module %}
-      {% capture note-middleware %}
-        This page was generated from the <a target="_blank" href="https://github.com/expressjs/{{page.module}}">{{page.module}} README</a>.
-      {% endcapture %}
-
-      {% include admonitions/note.html content=note-middleware %}
-
-      {% capture included-readme %}{% include readmes/{{page.module}}.md %}{% endcapture %}
-      
-      {{ included-readme | markdownify }}
-
-    {% else %}
-      <h3>ERROR: No source specified for README {{page.module}}</h3>
-    {% endif %}
-
-</main>
diff --git a/_layouts/page.html b/_layouts/page.html
deleted file mode 100644
index e013c5b3ab..0000000000
--- a/_layouts/page.html
+++ /dev/null
@@ -1,42 +0,0 @@
-<!DOCTYPE html>
-{% if page.lang %}
-<html lang="{{ page.lang }}" prefix="og: http://ogp.me/ns#">
-
-  {% include head.html %}
-
-  {% if page.lang == 'en' %}
-  <body class="en-doc">
-  {% else %}
-  <body class="non-en-doc">
-  {% endif %}
-
-  {% include header.html %}
-
-  <div id="overlay"></div>
-
-  {% if page.lang != 'en' %}
-       <div id="i18n-notice-box" class="doc-notice" hidden>
-          {% include i18n-notice.html %}
-      </div>
-  {% endif %}
-
-  {% if page.layout == 'middleware' %}
-    <div class="content flex-row-content">
-      {{ content }}
-    </div>
-  {% else %}
-    <div class="content">
-      <main>
-        {{ content }}
-        {% include bottom-navigation.html %}
-        {% include github-edit-btn.html %}
-      </main>
-    </div>
-  {% endif %}
-
-  {% include footer.html %}
-
-  </body>
-
-</html>
-{% endif %}
diff --git a/_layouts/post.html b/_layouts/post.html
deleted file mode 100644
index 4f79504c5b..0000000000
--- a/_layouts/post.html
+++ /dev/null
@@ -1,36 +0,0 @@
-<!DOCTYPE html>
-<html lang="{{ page.lang }}">
-  {% include head.html %}
-  
-  <body>
-    {% include header.html %}
-    <div id="overlay"></div>
-    
-    <div class="content flex-row-content">
-      <nav aria-labelledby="sidebar-heading">
-        <div class="toc-container">
-          <h3 id="sidebar-heading" class="toc-heading"><em>Blog posts</em></h3>
-          {% include blog/posts-menu.md %}
-        </div>
-      </nav>
-      <main id="blog-doc" markdown="1">
-          {% if page.title %}
-          <h1>{{page.title}}</h1>
-          {% endif %} 
-          {% if page.sub_title %}
-          <h2>{{page.sub_title}}</h2>
-          {% endif %}
-          <div class="blog-details">
-            {% include blog/authors.html authors=page.authors %}
-            <div class="blog-date">{{page.date| date: "%d %b %Y" }}</div>
-          </div>
-        {{ content }}
-        {% include github-edit-btn.html %}
-      </main>
-    </div>
-
-    {% include footer.html %}
-
-  </body>
-
-</html>
diff --git a/_posts/2024-07-16-welcome-post.md b/_posts/2024-07-16-welcome-post.md
deleted file mode 100644
index 52fc60a25a..0000000000
--- a/_posts/2024-07-16-welcome-post.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Welcome to The Express Blog!
-description: Introducing the new Express blog — a primary platform for announcements, updates, and communication from the Express technical committee.
-tags: site-admin
-authors:
-  - name: Rand McKinney
-    github: crandmck
-  - name: Chris Del
-    github: chrisdel101
----
-
-Welcome to the new Express blog!  The blog is meant to be a primary means of communication for the Express technical committee (TC).  While we currently have other channels such as X, LinkedIn, and of course GitHub, there's no authoritative "soapbox" for announcements and general communication.
-
-Initially, the Express blog will be a venue:
-- For periodic announcements of new releases, pre-releases, plans, and ongoing work on the project.
-- For the Express TC to discuss issues of particular importance to the Express community.
-- To highlight security issues or other urgent information.
- 
-Eventually, we hope the blog will evolve into a more general communication hub for the entire Express community; for example to share examples, tips, and experiences with the Express ecosystem and other information that's not simply technical documentation or GitHub discussion.
-
-Initially, posts will be written by TC members (potentially collaborating others), mainly because we don't have bandwidth to review general posts from the broader community. Eventually, we would love to open up the blog for broader contributions, but for now the focus is on trying to release Express 5.0, and the reality of an open-source project is that everyone has finite time to contribute. 
-
-Express TC member [Ulises Gascón](https://github.com/UlisesGascon) suggested a number of interesting topics for blog posts in [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500), but there are undoubtedly many others. 
-
-If you have an idea for a post, feel free to pitch the idea! You can add a comment to [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500) or open a new issue, and then after appropriate discussion, open a PR.  We've also written up simple [instructions to create a blog post](/en/blog/write-post.html). 
-
-Happy blogging!
diff --git a/_posts/2024-09-29-security-releases.md b/_posts/2024-09-29-security-releases.md
deleted file mode 100644
index 658fe345f5..0000000000
--- a/_posts/2024-09-29-security-releases.md
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: September 2024 Security Releases
-description: Security releases for Express, body-parser, send, serve-static, and path-to-regexp have been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascón
-    github: UlisesGascon
----
-
-Recently, the Express team has been made aware of a number of security vulnerabilities in the Express project.  We have released a number of patches to address these vulnerabilities.  
-
-{% include admonitions/warning.html 
-content="We strongly recommend that you upgrade these modules to the recommended (or latest) version as soon as possible."
-%}
-
-The following vulnerabilities have been addressed:
-
-- [High severity vulnerability CVE-2024-45590 in body-parser middleware](#high-severity-vulnerability-cve-2024-45590-in-body-parser-middleware)
-- [High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware](#high-severity-vulnerability-cve-2024-47178-in-basic-auth-connect-middleware)
-- [Moderate severity vulnerability CVE-2024-43796 in Express core](#moderate-severity-vulnerability-cve-2024-43796-in-express-core)
-- [Moderate severity vulnerability CVE-2024-43799 in send utility module](#moderate-severity-vulnerability-cve-2024-43799-in-send-utility-module)
-- [Moderate severity vulnerability CVE-2024-43800 in serve-static middleware](#moderate-severity-vulnerability-cve-2024-43800-in-serve-static-middleware)
-- [Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module](#moderate-severity-vulnerability-cve-2024-45296-in-path-to-regexp-utility-module)
-
-## High severity vulnerability CVE-2024-45590 in body-parser middleware
-
-**[body-parser](https://www.npmjs.com/package/body-parser) version `<1.20.3` is vulnerable to denial of service when URL-encoding is enabled**
-
-A malicious actor using a specially-crafted payload could flood the server with a large number of requests, resulting in denial of service.
-
-**Affected versions**: `<1.20.3`
-
-**Patched versions**: `>=1.20.3`
-
-This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
-
-For more details, see [GHSA-qwcr-r2fm-qrc7](https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7).
-
-## High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware
-
-**[basic-auth-connect](https://www.npmjs.com/package/basic-auth-connect) uses a timing-unsafe equality comparison**
-
-basic-auth-connect `<1.1.0` uses a timing-unsafe equality comparison that can leak timing information
-
-**Affected versions**
-- `<1.1.0`
-
-**Patched versions**
-- `>=1.1.0`
-
-This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express Securty triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
-
-More details area available in [GHSA-7p89-p6hx-q4fw](https://github.com/expressjs/basic-auth-connect/security/advisories/GHSA-7p89-p6hx-q4fw)
-
-
-
-## Moderate severity vulnerability CVE-2024-43796 in Express core
-
-The core **[express](https://www.npmjs.com/package/express) package is vulnerable to cross-site scripting (XSS) attack via `response.redirect()`**.
-
-In Express version <4.20.0, passing untrusted user input&mdash;even after sanitizing it&mdash;to `response.redirect()` may execute untrusted code.
-
-**Affected versions**:
-- `<4.20.0`
-- `>=5.0.0-alpha.1`, `<5.0.0`
-
-**Patched versions**:
-- `>=4.20.0`
-- `>=5.0.0`
-
-This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
-
-For more details, see [GHSA-qw6h-vgh9-j6wx](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx).
-
-
-## Moderate severity vulnerability CVE-2024-43799 in send utility module
-
-The **[send](https://www.npmjs.com/package/send) utility module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
-
-Passing untrusted user input&mdash;even after sanitizing it&mdash;to `SendStream.redirect()` can execute untrusted code.
-
-**Affected versions**: `< 0.19.0`
-
-**Patched versions**: `>=0.19.0`
-
-This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
-
-For more details, see [GHSA-m6fv-jmcg-4jfg](https://github.com/pillarjs/send/security/advisories/GHSA-m6fv-jmcg-4jfg).
-
-
-## Moderate severity vulnerability CVE-2024-43800 in serve-static middleware
-
-The **[serve-static](https://www.npmjs.com/package/serve-static) middleware module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
-
-Passing untrusted user input&mdash;even after sanitizing it&mdash;to `redirect()` can execute untrusted code.
-
-**Affected versions**: 
-- `< 1.16.0`
-- `>=2.0.0`, `<2.1.0`
-
-**Patched versions**:
-- `>=1.16.0`
-- `>=2.1.0`
-
-This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
-
-For more details, see [GHSA-cm22-4g7w-348p](https://github.com/expressjs/serve-static/security/advisories/GHSA-cm22-4g7w-348p)
-
-
-## Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module
-
-The **[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) utility module is vulnerable to regular expression denial of service (ReDoS) attack**.
-
-A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (`.`). For example, `/:a-:b`.
-
-Using `/:a-:b` will produce the regular expression `/^\/([^\/]+?)-([^\/]+?)\/?$/`. This can be exploited by a path such as `/a${'-a'.repeat(8_000)}/a`. [OWASP](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) has a good example of why this occurs, but in essence, the `/a` at the end ensures this route would never match, but due to naive backtracking it will still attempt every combination of the `:a-:b` on the repeated 8,000 `-a`.
-
-Because JavaScript is single-threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment, using Express v4 and ten concurrent connections results in an average latency of ~600ms vs 1ms.
-
-**Affected versions**:
-- `>=4.0.0`, `<8.0.0`
-- `>=0.2.0`, `<1.9.0`
-- `<0.1.10`
-- `>=2.0.0`, `<3.3.0`
-- `>=4.0.0`, `<6.3.0`
-
-**Patched versions**:
-- `>=8.0.0`
-- `>=1.9.0`
-- `>=0.1.10`
-- `>=3.3.0`
-- `>=6.3.0`
-
-Thanks to [Blake Embrey](https://github.com/blakeembrey) who reported and created the security patch.
-
-For more details, see [GHSA-9wv6-86v2-598j](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)
-
diff --git a/_posts/2025-05-19-security-releases.md b/_posts/2025-05-19-security-releases.md
deleted file mode 100644
index bfab761a5b..0000000000
--- a/_posts/2025-05-19-security-releases.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: May 2025 Security Releases
-description: Security release for Multer has been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascón
-    github: UlisesGascon
----
-
-The Express team has released a new major version of [Multer](https://www.npmjs.com/package/multer) addressing two high-severity security vulnerabilities. This update improves the reliability and security of handling file uploads in Express applications.
-
-{% include admonitions/warning.html 
-content="We strongly recommend that you upgrade to Multer v2.0.0 or later as soon as possible."
-%}
-
-The following vulnerabilities have been addressed:
-
-- [High severity vulnerability CVE-2025-47935 in Multer middleware](#high-severity-vulnerability-cve-2025-47935-in-multer-middleware)
-- [High severity vulnerability CVE-2025-47944 in Multer middleware](#high-severity-vulnerability-cve-2025-47944-in-multer-middleware)
-
-## High severity vulnerability CVE-2025-47935 in Multer middleware
-
-**[Multer](https://www.npmjs.com/package/multer) versions `<2.0.0` are vulnerable to denial of service due to a memory leak caused by improper stream handling.**
-
-When the HTTP request stream emits an error, the internal `busboy` stream is not closed, violating Node.js stream safety guidance.
-
-This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.
-
-**Affected versions**: `<2.0.0`  
-**Patched version**: `>=2.0.0`
-
-For more details, see [GHSA-44fp-w29j-9vj5](https://github.com/expressjs/multer/security/advisories/GHSA-44fp-w29j-9vj5).
-
-## High severity vulnerability CVE-2025-47944 in Multer middleware
-
-**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.0` are vulnerable to a denial of service via a malformed multipart request.**
-
-A specially crafted request can cause an unhandled exception inside Multer, resulting in a crash of the server process.
-
-**Affected versions**: `>=1.4.4-lts.1` and `<2.0.0`  
-**Patched version**: `>=2.0.0`
-
-For more details, see [GHSA-4pg4-qvpc-4q3h](https://github.com/expressjs/multer/security/advisories/GHSA-4pg4-qvpc-4q3h).
-
----
-
-**Multer v2.0.0** also introduces a breaking change:
-
-- The minimum supported Node.js version is now **10.16.0**.
-
-We recommend upgrading to the latest version of Multer immediately to secure your applications.
diff --git a/_posts/2025-07-18-security-releases.md b/_posts/2025-07-18-security-releases.md
deleted file mode 100644
index e6e4d86033..0000000000
--- a/_posts/2025-07-18-security-releases.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: June 2025 Security Releases
-description: Security update for Multer released. All users are encouraged to upgrade.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascón
-    github: UlisesGascon
----
-
-The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer), addressing a high-severity vulnerability that could lead to a Denial of Service (DoS) attack.
-
-{% include admonitions/warning.html 
-content="We strongly recommend that all users upgrade to Multer v2.0.1 or later immediately."
-%}
-
-This release addresses the following vulnerability:
-
-### High severity vulnerability CVE-2025-48997 in Multer middleware
-
-**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.1` are vulnerable to a Denial of Service (DoS) attack.**
-
-An attacker can trigger this vulnerability by sending an upload request with an empty string as the field name. This malformed request causes an unhandled exception, leading to a crash of the server process.
-
-**Affected versions**: `>=1.4.4-lts.1` and `<2.0.1`  
-**Patched version**: `2.0.1`
-
-For more details, see [GHSA-g5hg-p3ph-g8qg](https://github.com/expressjs/multer/security/advisories/GHSA-g5hg-p3ph-g8qg).
-
-
diff --git a/_posts/2025-12-01-security-releases.md b/_posts/2025-12-01-security-releases.md
deleted file mode 100644
index 3ec8a23a3b..0000000000
--- a/_posts/2025-12-01-security-releases.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: November 2025 Security Releases
-description: Security release for body-parser has been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascón
-    github: UlisesGascon
----
-
-The Express team has released a new patch version of [body-parser](https://www.npmjs.com/package/body-parser) addressing a moderate-severity security vulnerability.
-
-
-{% include admonitions/warning.html 
-content="We recommend upgrading to the latest version of body-parser to secure your applications."
-%}
-
-The following vulnerabilities have been addressed:
-
-- [CVE-2025-13466 in body-parser middleware (Moderate)](#cve-2025-13466-in-body-parser-middleware-moderate)
-
-## CVE-2025-13466 in Body-parser middleware (Moderate)
-
-**[body-parser](https://www.npmjs.com/package/body-parser) version `2.2.0` is vulnerable to denial of service when url encoding is used**
-
-body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.
-
-**Affected versions**: `2.2.0`  
-**Patched version**: `>= 2.2.1`
-
-For more details, see [GHSA-wqch-xfxh-vrr4](https://github.com/expressjs/body-parser/security/advisories/GHSA-wqch-xfxh-vrr4).
-
----
-
-We recommend upgrading to the latest version of body-parser to secure your applications.
diff --git a/_posts/2026-02-27-security-releases.md b/_posts/2026-02-27-security-releases.md
deleted file mode 100644
index dc3ec2021b..0000000000
--- a/_posts/2026-02-27-security-releases.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: February 2026 Security Releases
-description: Security release for multer has been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascón
-    github: UlisesGascon
----
-
-The Express team has released a new patch version of [multer](https://www.npmjs.com/package/multer) addressing two high-severity security vulnerabilities.
-
-
-{% include admonitions/warning.html
-content="We recommend upgrading to the latest version of multer to secure your applications."
-%}
-
-The following vulnerabilities have been addressed:
-
-- [CVE-2026-3304 in multer middleware (High)](#cve-2026-3304-in-multer-middleware-high)
-- [CVE-2026-2359 in multer middleware (High)](#cve-2026-2359-in-multer-middleware-high)
-
-## CVE-2026-3304 in multer middleware (High)
-
-**[multer](https://www.npmjs.com/package/multer) versions `<2.1.0` are vulnerable to denial of service via incomplete cleanup**
-
-A vulnerability in Multer versions <2.1.0 allows an attacker to trigger a Denial of Service (DoS) by sending malformed requests, potentially causing resource exhaustion.
-
-**Affected versions**: `< 2.1.0`
-**Patched version**: `>= 2.1.0`
-
-For more details, see [GHSA-xf7r-hgr6-v32p](https://github.com/expressjs/multer/security/advisories/GHSA-xf7r-hgr6-v32p).
-
-## CVE-2026-2359 in multer middleware (High)
-
-**[multer](https://www.npmjs.com/package/multer) versions `<2.1.0` are vulnerable to denial of service via resource exhaustion**
-
-A vulnerability in Multer versions <2.1.0 allows an attacker to trigger a Denial of Service (DoS) by dropping connection during file upload, potentially causing resource exhaustion.
-
-**Affected versions**: `< 2.1.0`
-**Patched version**: `>= 2.1.0`
-
-For more details, see [GHSA-v52c-386h-88mc](https://github.com/expressjs/multer/security/advisories/GHSA-v52c-386h-88mc).
-
----
-
-We recommend upgrading to the latest version of multer to secure your applications.
diff --git a/_posts/2026-03-30-security-releases.md b/_posts/2026-03-30-security-releases.md
deleted file mode 100644
index b3f4564fe8..0000000000
--- a/_posts/2026-03-30-security-releases.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: March 2026 Security Releases
-description: Security releases for path-to-regexp have been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
-authors:
-  - name: Ulises Gascon
-    github: UlisesGascon
----
-
-The Express team has released new patch versions of [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) addressing three regular expression denial of service vulnerabilities.
-
-{% capture warning_content %}
-We recommend upgrading to the latest version of path-to-regexp to secure your applications. If you have a `package-lock.json`, you can update the dependency by running:
-
-```sh
-npm update path-to-regexp
-```
-{% endcapture %}
-{% include admonitions/warning.html content=warning_content %}
-
-The following vulnerabilities have been addressed:
-
-- [CVE-2026-4867 in path-to-regexp utility module (High)](#cve-2026-4867-in-path-to-regexp-utility-module-high)
-- [CVE-2026-4926 in path-to-regexp utility module (High)](#cve-2026-4926-in-path-to-regexp-utility-module-high)
-- [CVE-2026-4923 in path-to-regexp utility module (Medium)](#cve-2026-4923-in-path-to-regexp-utility-module-medium)
-
-## CVE-2026-4867 in path-to-regexp utility module (High)
-
-**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `<= 0.1.12` are vulnerable to regular expression denial of service via multiple route parameters**
-
-A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period. For example, `/:a-:b-:c`. The backtrack protection added in v0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, causing catastrophic backtracking.
-
-**Affected versions**: `<= 0.1.12`
-**Patched version**: `>= 0.1.13`
-
-For more details, see [GHSA-37ch-88jc-xwx2](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-37ch-88jc-xwx2).
-
-## CVE-2026-4926 in path-to-regexp utility module (High)
-
-**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `>= 8.0.0` are vulnerable to denial of service via sequential optional groups**
-
-A bad regular expression is generated any time you have multiple sequential optional groups, such as `{a}{b}{c}:z`. The generated regex grows exponentially with the number of groups, causing denial of service. Avoid passing user-controlled input as route patterns.
-
-**Affected versions**: `>= 8.0.0`
-**Patched version**: `>= 8.4.0`
-
-For more details, see [GHSA-j3q9-mxjg-w52f](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-j3q9-mxjg-w52f).
-
-## CVE-2026-4923 in path-to-regexp utility module (Medium)
-
-**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `>= 8.0.0, <= 8.3.0` are vulnerable to regular expression denial of service via multiple wildcards**
-
-When using multiple wildcards combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. The second wildcard must be somewhere other than the end of the path. For example, `/*foo-*bar-:baz`.
-
-**Affected versions**: `>= 8.0.0, <= 8.3.0`
-**Patched version**: `>= 8.4.0`
-
-For more details, see [GHSA-27v5-c462-wpq7](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-27v5-c462-wpq7).
-
----
-
-We recommend upgrading to the latest version of path-to-regexp to secure your applications.
diff --git a/astro.config.mjs b/astro.config.mjs
new file mode 100644
index 0000000000..557730f332
--- /dev/null
+++ b/astro.config.mjs
@@ -0,0 +1,77 @@
+// @ts-check
+import { defineConfig } from 'astro/config';
+import mdx from '@astrojs/mdx';
+import sitemap from '@astrojs/sitemap';
+import icon from 'astro-icon';
+import expressiveCode from 'astro-expressive-code';
+import react from '@astrojs/react';
+import svgr from 'vite-plugin-svgr';
+import Icons from 'unplugin-icons/vite';
+import rehypeSlug from 'rehype-slug';
+import rehypeAutolinkHeadings from 'rehype-autolink-headings';
+import redirects from './src/config/redirect.js';
+import { accessibleTablesIntegration } from './src/plugins/rehype-accessible-tables.mjs';
+
+/* https://docs.netlify.com/configure-builds/environment-variables/#read-only-variables */
+const NETLIFY_PREVIEW_SITE = process.env.CONTEXT !== 'production' && process.env.DEPLOY_PRIME_URL;
+
+const site = NETLIFY_PREVIEW_SITE || 'https://expressjs.com';
+
+// https://astro.build/config
+export default defineConfig({
+  redirects,
+  site,
+  markdown: {
+    rehypePlugins: [
+      rehypeSlug,
+      [
+        rehypeAutolinkHeadings,
+        {
+          behavior: 'wrap',
+        },
+      ],
+    ],
+  },
+  vite: {
+    plugins: [
+      // Transforms SVG files imported with the `?react` suffix into React components
+      // (used for local SVG assets like logos).
+      svgr(),
+      // Resolves `~icons/collection/icon-name` imports into React components,
+      // bundling only the SVG paths for icons actually used (no full icon set in the bundle).
+      Icons({ compiler: 'jsx', jsx: 'react' }),
+    ],
+  },
+  integrations: [
+    expressiveCode({
+      themes: ['github-dark'],
+      styleOverrides: {
+        uiFontSize: 'var(--font-size-sm)',
+        codeFontSize: 'var(--font-size-sm)',
+        borderRadius: 'var(--radius-base)',
+        borderWidth: 'var(--border-width-1)',
+      },
+    }),
+    accessibleTablesIntegration(),
+    mdx(),
+    icon(),
+    react(),
+    sitemap({
+      i18n: {
+        defaultLocale: 'en',
+        locales: {
+          de: 'de',
+          en: 'en',
+          es: 'es',
+          fr: 'fr',
+          ja: 'ja',
+          it: 'it',
+          ko: 'ko',
+          'pt-br': 'pt-BR',
+          'zh-cn': 'zh-CN',
+          'zh-tw': 'zh-TW',
+        },
+      },
+    }),
+  ],
+});
diff --git a/crowdin.yml b/crowdin.yml
index e8c2ad2c2e..821ccb4bf9 100644
--- a/crowdin.yml
+++ b/crowdin.yml
@@ -1,13 +1,10 @@
 files:
-  - source: /en/**/*.*
-    ignore:
-      - /en/blog/**/*.*
-      - /**/changelog/index.md
-    translation: /%two_letters_code%/**/%original_file_name%
-  - source: /_data/en/**/*.*
-    translation: /_data/%two_letters_code%/**/%original_file_name%
-  - source: /index.md
-    translation: /%two_letters_code%/index.md
+  - source: /src/content/pages/en/**/*.*
+    translation: /src/content/pages/%two_letters_code%/**/%original_file_name%
+  - source: /src/content/docs/en/**/*.*
+    translation: /src/content/docs/%two_letters_code%/**/%original_file_name%
+  - source: /src/i18n/ui/en.json
+    translation: /src/i18n/ui/%two_letters_code%.json
 preserve_hierarchy: true
 project_id_env: CROWDIN_PROJECT_ID
 base_url: 'https://express.api.crowdin.com'
diff --git a/css/langs/de.css b/css/langs/de.css
deleted file mode 100644
index df6795b5a2..0000000000
--- a/css/langs/de.css
+++ /dev/null
@@ -1,14 +0,0 @@
-/* For image callouts in writing-middleware.md  */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 135px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
-
diff --git a/css/langs/en.css b/css/langs/en.css
deleted file mode 100644
index 8f2e5ac2dd..0000000000
--- a/css/langs/en.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/langs/es.css b/css/langs/es.css
deleted file mode 100644
index dd8a578f8e..0000000000
--- a/css/langs/es.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 140px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/langs/fr.css b/css/langs/fr.css
deleted file mode 100644
index 1c9938c3f7..0000000000
--- a/css/langs/fr.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/langs/it.css b/css/langs/it.css
deleted file mode 100644
index 6b0bbc10b8..0000000000
--- a/css/langs/it.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/langs/ja.css b/css/langs/ja.css
deleted file mode 100644
index 1c162162cd..0000000000
--- a/css/langs/ja.css
+++ /dev/null
@@ -1,15 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-.callout {position: relative;}
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/langs/ko.css b/css/langs/ko.css
deleted file mode 100644
index d4c2b2ac66..0000000000
--- a/css/langs/ko.css
+++ /dev/null
@@ -1,19 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-@import url('../../fonts/ko/pretendard.css');
-
-html, body {font-family: Pretendard, Arial, sans-serif;}
-
-.callout {position: relative;}
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 165px;}
-
-#callout6 {top: 185px;}
diff --git a/css/langs/pt-br.css b/css/langs/pt-br.css
deleted file mode 100644
index dd8a578f8e..0000000000
--- a/css/langs/pt-br.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 140px;}
-
-#callout5 {top: 150px;}
-
-#callout6 {top: 160px;}
diff --git a/css/langs/zh-cn.css b/css/langs/zh-cn.css
deleted file mode 100644
index 8f2e5ac2dd..0000000000
--- a/css/langs/zh-cn.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/langs/zh-tw.css b/css/langs/zh-tw.css
deleted file mode 100644
index 8f2e5ac2dd..0000000000
--- a/css/langs/zh-tw.css
+++ /dev/null
@@ -1,13 +0,0 @@
-/* For image callouts in writing-middleware.md */
-
-#callout1 {top: 40px; }
-
-#callout2 {top: 60px;}
-
-#callout3 {top: 75px;}
-
-#callout4 {top: 145px;}
-
-#callout5 {top: 170px;}
-
-#callout6 {top: 195px;}
diff --git a/css/search.css b/css/search.css
deleted file mode 100644
index cb60915c73..0000000000
--- a/css/search.css
+++ /dev/null
@@ -1,22 +0,0 @@
-#q {
-  display: none;
-  height: 2.5em;
-  min-width: 100%;
-  padding: 5px;
-}
-
-.algolia-autocomplete {
-  min-width: 12em;
-  max-width: 12em;
-  top: -0.2em;
-}
-
-.algolia-autocomplete #q {
-  display: initial
-}
-
-@media all and (max-width: 899px) {
-  .algolia-autocomplete {
-    display: none !important;
-  }
-}
diff --git a/css/sintax.css b/css/sintax.css
deleted file mode 100644
index e33e6fbee9..0000000000
--- a/css/sintax.css
+++ /dev/null
@@ -1,141 +0,0 @@
-:root {
-  --orange: #953800;
-  --green: #116329;
-  --blue-light: #0550ae;
-  --blue-darker: #0a3069;
-  --pupple: #8250df;
-  --gray: #6e7781;
-  --red: #cf222e;
-  --red-darker: #82071e;
-}
-
-.dark-mode:root {
-  --orange: #ffa657;
-  --green: #79c0ff;
-  --blue-light: #a5d6ff;
-  --blue-darker: #1f6feb;
-  --pupple: #d2a8ff;
-  --gray: #8b949e;
-  --red: #ff7b72;
-  --red-darker: #8e1519;
-}
-
-.highlight table td { padding: 5px; }
-.highlight table pre { margin: 0; }
-
-.highlight, .highlight .w {
-  color: #24292f;
-  background-color: var(--code-bg);
-}
-
-.highlight .k, .highlight .kd, .highlight .kn, .highlight .kp, .highlight .kr, .highlight .kt, .highlight .kv {
-  color: var(--red);
-}
-
-.highlight .gr {
-  color: #f6f8fa;
-}
-
-.highlight .gd {
-  color: var(--red-darker);
-  background-color: #ffebe9;
-}
-
-.highlight .nb,
-.highlight .nc,
-.highlight .no,
-.highlight .nn  {
-  color: var(--orange);
-}
-
-.highlight .sr,.highlight .na, .highlight .nt, .highlight .gi {
-  color: var(--green);
-}
-
-.highlight .gi {
-  background-color: #dafbe1;
-}
-
-.highlight .ges {
-  font-weight: bold;
-  font-style: italic;
-}
-
-.highlight .l, 
-.highlight .ld, 
-.highlight .m, 
-.highlight .mb, 
-.highlight .mf, 
-.highlight .mh, 
-.highlight .mi, 
-.highlight .il, 
-.highlight .mo, 
-.highlight .mx,
-.highlight .kc,
-.highlight .sb,
-.highlight .bp,
-.highlight .ne,
-.highlight .nl,
-.highlight .py
-.highlight .nv, 
-.highlight .vc, 
-.highlight .vg, 
-.highlight .vi, 
-.highlight .vm,
-.highlight .s1,
-.highlight .o, 
-.highlight .ow,
-.highlight .gh,
-.highlight .gu,
-.highlight .s2,
-.highlight .dl   {
-  color: var(--blue-light);
-}
-
-.highlight .gh {
-  font-weight: bold;
-}
-.highlight .gu {
-  font-weight: bold;
-}
-.highlight .s, .highlight .sa, .highlight .sc, .highlight .sd,  .highlight .se, .highlight .sh, .highlight .sx, .highlight .ss {
-  color: var(--blue-darker);
-}
-.highlight .nd, .highlight .nf, .highlight .fm {
-  color: var(--pupple);
-}
-
-.highlight .err {
-  color: #f6f8fa;
-  background-color: #82071e;
-}
-.highlight .c, 
-.highlight .gl
-.highlight .ch,
-.highlight .cd, 
-.highlight .cm, 
-.highlight .cp, 
-.highlight .cpf, 
-.highlight .cs,
-.highlight .gt {
-  color: var(--gray);
-}
-
-.highlight .c1 {
-  color: var(--green);
-}
-
-.highlight .ni,
-.highlight .ge,
-.highlight .si,
-.highlight .gs {
-  color: #24292f;
-}
-
-.highlight .ge {
-  font-style: italic;
-}
-
-.highlight .gs {
-  font-weight: bold;
-}
diff --git a/css/style.css b/css/style.css
deleted file mode 100644
index 7931ca1eed..0000000000
--- a/css/style.css
+++ /dev/null
@@ -1,1783 +0,0 @@
-:root {
-  --header-height: 57px;
-}
-
-* {
-  box-sizing: border-box;
-  -webkit-tap-highlight-color: transparent;
-  scroll-behavior: smooth;
-}
-
-/* handle header offset with scroll-margin */
-h1, h2, h3, h4, h5, h6,
-[id] {
-  scroll-margin-top: 60px;
-}
-
-/* Respect user motion preferences for access */
-@media (prefers-reduced-motion: reduce) {
-  html {
-    scroll-behavior: auto;
-  }
-}
-
-body {
-  height: 100vh;
-  font: 400 14px/1.6 "Open Sans", sans-serif;
-  background: var(--bg);
-  margin: 0;
-  padding: 0;
-  color: var(--fg);
-  display: grid;
-  grid-template-areas:
-  'header'
-  'i18n'
-  'content'
-  'footer'
-}
-
-header {
-  grid-area: header;
-  height: var(--header-height);
-}
-
-.content {
-  grid-area: content;
-}
-
-footer {
-  margin-top: auto;
-  grid-area: footer;
-}
-
-body.no-scroll{
-  overflow: hidden;
-}
-
-h1 {
-  font-size: 30px;
-  line-height: 36px;
-}
-
-#intro h2, #api-doc h1 {
-  font-weight: normal;
-}
-
-h1, h2, h3 {
-  margin: 5px 0;
-  color: var(--card-fg);
-  -webkit-font-smoothing: antialiased;
-
-}
-
-.content h1 {
-  margin-bottom: 20px;
-}
-
-.content table a.ignore-underline {
-  text-decoration: none;
-}
-
-p em {
-  font-weight: bold;
-  color: var(--card-fg);
-}
-
-p {
-  margin: 10px 0;
-  line-height: 1.35em;
-}
-
-strong, th {
-  color: var(--card-fg);
-}
-
-#overlay {
-  position: fixed;
-  left: 0;
-  top: 0;
-  opacity: 0.6;
-  width: 100%;
-  height: 100%;
-  display: none;
-  z-index: 1;
-  background-color: var(--bg);
-}
-
-main.home {
-  max-width: 75rem;
-  margin: 40px auto 2%;
-  padding-inline: 5%;
-  grid-area: content;
-}
-
-#home-content {
-  display: flex;
-}
-
-#homepage-leftpane {
-  min-width: 500px;
-  margin-right: 30px;
-  font-size: 90%;
-  padding-top: 13px;
-}
-
-#homepage-rightpane {
-  min-width: 500px;
-  padding: 25px 30px 0px 0px;
-}
-
-#homepage-rightpane iframe {
-  min-width: 100%;
-  min-height: 273px;
-}
-
-#announcements {
-  margin-top: 40px;
-  padding: 0 16px;
-  background: var(--notice-bg);
-  border: 1px solid var(--notice-accent);
-  border-radius: 3px;
-  font-size: 0.9em;
-  & a {
-    color: var(--notice-accent);
-    text-decoration: underline;
-  }
-}
-
-#announcements ul {
-  padding-left: 0;
-}
-
-#announcements li {
-  list-style: none;
-  margin-bottom: 16px;
-}
-
-#announcements p {
-  margin: 6px 0;
-}
-
-#announcements time {
-  font-weight: normal;
-  margin-right: 12px;
-}
-
-.announcement-title {
-  font-weight: bold;
-  margin-bottom: 11px;
-  display: flex;
-  align-items: center;
-  column-gap: 8px
-}
-
-.install-command {
-  font-family: Consolas, Monaco, "Andale Mono", monospace;
-  padding: 10px;
-  border: 1px solid var(--border);
-  border-radius: 3px;
-  max-width: 375px;
-  background-color: inherit;
-
-  code {
-    background-color: inherit;
-  }
-}
-
-.content {
-  display: flex;
-  flex-direction: row-reverse;
-  padding-inline-start: 1rem;
-  margin-block-start: 3.5rem;
-}
-
-.content main {
-  max-width: 900px;
-  margin-inline: auto;
-}
-
-.flex-row-content {
-  flex-direction: row;
-}
-
-span.block-section {
-  display: block;
-}
-
-#intro h2 {
-  font-size: 25px;
-  margin-bottom: 10px;
-}
-
-#api-doc section {
-  padding-left: 20px;
-}
-
-#api-doc > h3 {
-  padding-top: 10px;
-  padding-bottom: 5px;
-  font-weight: bold;
-  font-size: 24px;
-  color: var(--menu-grey)
-}
-
-#api-doc h2 {
-  font-weight: bold;
-  font-size: 29px;
-  margin: 40px 0 20px;
-}
-
-#api-doc section h3 {
-  padding-top: 10px;
-  padding-bottom: 5px;
-  font-weight: bold;
-  font-size: 18px;
-}
-
-#api-doc h4 {
-  font-size: 16px;
-  font-weight: bold;
-}
-
-#api-doc h5 {
-  font-size: 14px;
-  font-weight: bold;
-  color: var(--menu-grey)
-}
-
-/* scroll */
-
-*::-webkit-scrollbar {
-  background-color: opacity(var(--box-fg), 0.145);
-  width: 16px;
-}
-
-*::-webkit-scrollbar-thumb {
-  border-radius: 8px;
-  border: 4px solid transparent;
-  background-clip: content-box;
-  background-color: var(--menu-grey);
-}
-
-*::-webkit-scrollbar-thumb:hover {
-  background-color: var(--hover-bg);
-}
-
-*::-webkit-scrollbar-thumb:active {
-  background-color: var(--menu-grey);
-}
-
-/* links */
-
-a {
-  color: var(--link);
-  text-decoration: underline;
-}
-
-.h2:target {
-  display: block;
-  padding-top: 40px;
-}
-
-
-/* logo */
-.logo-container a {
-  text-decoration: none;
-  display: flex;
-  justify-content: center;
-  align-items : center;
-}
-
-.express-logo {
-  fill : var(--card-fg);
-}
-
-#description .express {
-  display: block;
-  font: 4.5em "Helvetica Neue", "Open Sans", sans-serif;
-  font-weight: 100;
-  margin-bottom: .25em;
-}
-
-#description .express > span {
-  color: var(--card-fg);
-}
-
-#description .express a#express-version {
-  font-size: 0.2em;
-  margin-left: 0.5em;
-  color: var(--link);
-  font-weight: 400;
-  text-decoration: underline;
-}
-
-#description {
-  margin-bottom: 43px;
-  -webkit-font-smoothing: antialiased;
-}
-
-#description .description {
-  position: relative;
-  top: -5px;
-  font: 100 4.1em "Helvetica Neue", "Open Sans", sans-serif;
-  color: var(--menu-grey);
-  line-height: .87;
-  margin: unset
-}
-
-#description .description a {
-  text-decoration-thickness: 1px;
-  text-underline-offset: 3px;
-}
-
-.header-right {
-  display: flex;
-  align-items: center;
-  gap: 20px;
-}
-
-header {
-  background: var(--card-bg);
-  height: 57px;
-  display: flex;
-  align-items: center;
-  justify-content: space-between;
-  padding-inline: 1rem;
-  border-bottom: 1px solid var(--hover-fg);
-}
-
-.scroll header {
-    box-shadow: 0 0 4px var(--card-bg);
-}
-
-/* code */
-
-code {
-  background-color: var(--code-bg);
-  color: var(--card-fg);
-  margin-block: -.125rem;
-  font-size: 13px;
-  padding: .125rem .375rem;
-  border-radius: 6px;
-}
-
-pre {
-  padding: 16px;
-  border-radius: 3px;
-  border: 1px solid var(--border);
-  background-color: var(--code-bg);
-/* keyboard focus offset improve visibility */
-    &:focus {
-      border-color: var(--hover-border);
-    }
-}
-
-pre code {
-  padding: 0;
-}
-
-pre:has(code) {
-  position: relative;
-
-  &:is(:hover, :focus) {
-    button {
-      display: flex;
-    }
-  }
-  /* focus copy btn by keyboard */
-  &:focus-within button {
-    display: flex;
-  }
-}
-
-pre:has(code) button {
-  position: absolute;
-  top: 5px;
-  right: 5px;
-  border: none;
-  z-index: 100;
-  display: none;
-  cursor: pointer;
-  background-color: inherit;
-  padding: 2px;
-  border-radius: 5px;
-
-  &::after {
-  content: "";
-  background-color: var(--card-fg);
-  mask-image: url("/images/copy-btn.svg");
-  mask-size: 1.5rem;
-  mask-repeat: no-repeat;
-  width: 1.5rem;
-  height: 1.5rem;
-  }
-
-  &:is(:hover, :focus) {
-    background-color: var(--hover-bg);
-    outline: 2px solid var(--hover-border);
-  }
-
-  @media all and (max-width: 370px) { 
-    padding: 1px;
-
-    &::after {
-      mask-size: 1rem;
-      width: 1rem;
-      height: 1rem;
-    }
-  }
-}
-
-pre:has(code) button.copied {
-  outline-color: var(--supported-fg);
-
-  &::after { 
-    background-color: var(--supported-fg);
-  }
-  
-  &::before {
-    font-size: 0.85rem;
-    position: absolute;
-    left: -58px;
-    content: "copied!";
-
-    width: fit-content;
-    height: fit-content;
-    padding: 4px;
-    border-radius: 2px;
-    color: var(--card-fg);
-    background-color: var(--card-bg);
-    outline: 1px solid var(--supported-fg);
-  }
-
-  @media all and (max-width: 400px) { 
-    &::before {
-      left: -50px;
-      font-size: 0.7rem;
-      padding: 3px;
-    }
-  }
-}
-
-pre:has(code) button.failed {
-  outline-color: var(--eol-fg);
-
-  &::after { 
-    background-color: var(--eol-fg);
-  }
-  
-  &::before {
-    font-size: 0.85rem;
-    position: absolute;
-    left: -58px;
-    content: "failed!";
-
-    width: fit-content;
-    height: fit-content;
-    padding: 4px;
-    border-radius: 2px;
-    color: var(--card-fg);
-    background-color: var(--card-bg);
-    outline: 1px solid var(--eol-fg);
-  }
-
-  @media all and (max-width: 400px) { 
-    &::before {
-      left: -50px;
-      font-size: 0.7rem;
-      padding: 3px;
-    }
-  }
-}
-
-/* scroll to top button */
-
-.scroll #top {
-  opacity: .5;
-  display: initial
-}
-
-.scroll #top:hover {
-  opacity: 1;
-}
-
-#top {
-  line-height: 0;
-  border-radius: 2px;
-  position: fixed;
-  bottom: 15px;
-  right: 15px;
-  padding: 8px;
-  text-decoration: none;
-  opacity: 0;
-  transition: opacity 300ms;
-  border: 1px solid var(--border); 
-  background-color: var(--card-bg);
-  color: var(--card-fg);
-  display: none;
-}
-
-/* clearfix */
-
-.clearfix:after {
-  content: ".";
-  display: block;
-  clear: both;
-  visibility: hidden;
-  line-height: 0;
-  height: 0;
-}
-
-.clearfix {
-  display: inline-block;
-}
-
-html[xmlns] .clearfix {
-  display: block;
-}
-
-* html .clearfix {
-  height: 1%;
-}
-
-/* boxes */
-
-#boxes {
-  display: grid;
-  grid-template-columns: repeat(4, 1fr);
-  row-gap: 20px;
-  column-gap: 50px;
-  margin-top: 30px;
-}
-
-#boxes h2 {
-  line-height: 1.25em;
-  color: var(--card-fg);
-  background: none;
-  margin-top: 0;
-  padding-top: 0;
-}
-
-#boxes h2 a {
-  text-decoration: none;
-  color: var(--card-fg);
-}
-
-#boxes div {
-  list-style: none;
-}
-
-/* tables specific */
-
-table {
-  margin: 1em 0;
-  border: 1px solid var(--border);
-  border-collapse: collapse;
-  width: 100%;
-  @media screen and (max-width:600px) {
-    font-size: smaller;
-  }
-}
-
-table td, table th {
-  padding: 7px;
-  line-height: 120%;
-  vertical-align: top;
-  border: 1px solid var(--border);
-}
-
-table tr th {
-  background: var(--card-bg);
-  font-size: 110%;
-}
-
-table td p:first-child {
-  margin-top: 0;
-}
-
-table td p, li p {
-  width: 100% !important;
-}
-
-table ul {
-  margin: 20px 0
-}
-
-/* doc boxes */
-
-.doc-box {
-  padding: 16px;
-  color: var(--box-fg);
-  border-radius: 0 6px 6px 0;
-  margin-bottom: 1rem;
-}
-
-.doc-box p {
-  margin: 0 0 8px 0;
-}
-
-.doc-box p:last-child {
-  margin: 0;
-}
-
-.doc-title {
-  display: flex;
-  align-items: center;
-  gap: 3px;
-  font-weight: 600;
-}
-
-/* i18n box */
-.doc-notice {
-  padding-block: 1rem;
-  padding-inline: 2.5rem;
-  color: var(--box-fg);
-  border-radius: 0 6px 6px 0;
-  background: var(--notice-bg);
-  border-left: 3px solid var(--notice-accent);
-  margin-inline: auto;
-  margin-block-start: 2rem;
-  position: relative;
-  grid-area: i18n;
-  display: block;
-}
-
-.doc-notice a{
-  color: var(--notice-accent);
-  text-decoration: underline;
-}
-
-.doc-notice[hidden] {
-  display: none;
-}
-
-.doc-info {
-  background: var(--info-bg);
-  border-left: 3px solid var(--info-accent);
-}
-
-.doc-info a{
-  color: var(--info-accent);
-  text-decoration: underline;
-}
-
-.doc-warn {
-  background: var(--warn-bg);
-  border-left: 3px solid var(--warn-accent);
-}
-
-.doc-warn a {
-  color: var(--warn-accent);
-  text-decoration: underline;
-}
-
-#close-i18n-notice-box {
-  position: absolute;
-  top: 3px;
-  right: 9px;
-  color: var(--notice-accent);
-  cursor: pointer;
-}
-
-/* general */
-
-#app-settings-property {
-  width: 200px;
-}
-
-div.header-btn {
-  display: flex;
-  padding: 3px;
-  border-radius: 3px;
-  cursor: pointer;
-  color: var(--box-fg);
-}
-
-a.edit-github-btn,
-a.bottom-nav-prev,
-a.bottom-nav-next {
-  display: flex;
-  gap: 0.5rem;
-  align-items: center;
-  width: fit-content;
-  padding: 0.5rem;
-  border-radius: 0.3rem;
-  text-decoration: none;
-
-  &:is(:hover, :active, :focus) {
-    color: var(--fg);
-    background-color: var(--hover-bg);
-    outline: 1px solid var(--card-fg);
-  }
-}
-
-#mobile-menu {
-  display: none;
-  position: relative;
-}
-
-pre, code {
-  white-space: pre-wrap !important;
-}
-
-/* footer */
-
-footer {
-  font-size: 12px;
-  display: flex;
-  gap: 24px;
-  flex-direction: column;
-  padding-block: 2rem;
-  padding-inline: 3rem;
-
-  @media screen and (max-width : 360px) {
-    padding: 1rem;
-  }
-}
-
-#footer-content {
-  width: 100%;
-  justify-content: space-between;
-  gap: 32px;
-  display: flex;
-  flex-direction: column;
-}
-
-#footer-trademark-legal {
-  font-size: 0.8rem;
-  opacity: 0.8;
-  margin-top: 8px;
-  text-align: center;
-  max-width: 35rem;
-}
-
-#footer-copyright {
-  display: flex;
-  flex-direction: column;
-  justify-content: center;
-  align-items: center;
-  gap: 20px;
-}
-
-#footer-policy {
-  display: flex;
-  flex-wrap: wrap;
-  column-gap: 20px;
-  row-gap: 8px;
-  justify-content: center;
-  font-size: 15px;
-}
-
-#footer-links {
-  display: flex;
-  gap: 20px;
-  flex-wrap: wrap;
-  align-items: center;
-  justify-content: center;
-}
-
-.footer-social {
-  display: flex;
-  gap: 20px;
-}
-
-.footer-social a {
-  color: inherit;
-}
-
-/* icons */
-a.openjs-logo {
-  display: inline-block;
-  width: 125px;
-  height: 39px;
-  cursor: pointer;
-}
-
-/* theme and lang btn */
-button.theme-btn {
-  width: 2rem;
-  height: 2rem;
-  border: none;
-  cursor: pointer;
-  color: var(--fg);
-  background-color: inherit;
-  display: flex;
-  justify-content: center;
-  align-items: center;
-}
-
-#icon-moon,
-#icon-sun { 
-  display: none;
-  align-self: center;
-}
-html.light-mode #icon-moon { 
-  display: inline; 
-}
-
-button.lang-btn {
-  appearance: none;
-  background-color: inherit;
-  border: 0;
-  cursor: pointer;
-  color: var(--card-fg);
-  padding: 0.2rem;
-  width: fit-content;
-  aspect-ratio: 1;
-}
-
-div.desktop-lang-switcher {
-  position: relative;
-
-  > ul.lang-list {
-    display: none;
-    opacity: 0;
-    position: absolute;
-    list-style: none;
-    visibility: hidden;
-    left: -75px;
-    z-index: 100;
-    background-color: var(--card-bg);
-    border: 1px solid;
-    border-radius: 10px;
-    padding: 0px;
-    min-width: max-content;
-    
-    li  a {
-      display: block;
-      padding: 5px 20px 5px 20px;
-      text-decoration: none;
-      color: var(--card-fg);
-      &:is(:hover, :focus) {
-        background: var(--hover-bg);
-      }
-    }
-
-   > li:first-child > a {
-      border-start-start-radius: 10px;
-      border-start-end-radius: 10px;
-    }
-
-   > li:last-child > a {
-      border-end-start-radius: 10px;
-      border-end-end-radius: 10px;
-    }
-  }
-
-  > ul.lang-list.open {
-    display: block;
-    opacity: 1;
-    visibility: visible;
-  }
-}
-
-/* navigation */
-#navbar {
-  line-height: 30px;
-  display: flex;
-  align-items: center;
-}
-
-#navbar a {
-  color: var(--card-fg);
-  text-decoration: none;
-}
-
-#navbar a.active {
-  font-weight: bold;
-}
-
-#navbar ul {
-  list-style: none;
-}
-
-#navmenu {
-  display: flex;
-  gap: 20px;
-}
-
-/* content doc */
-
-#blog-doc {
-  padding: 0.5rem;
-  width: fit-content;
-}
-
-/* dropdown menu */
-
-.submenu {
-  position: relative;
-  list-style: none;
-}
-
-.submenu-content {
-  position: absolute;
-  top: 100%;
-  left: 50%;
-  transform: translate(-50%);
-  margin: auto;
-  box-shadow: 1px 2px var(--hover-fg);
-  z-index: 1000;
-  min-width: max-content;
-  width: fit-content;
-  border: 1px solid var(--border);
-  border-radius: 12px;
-  background-color: var(--bg);
-  padding: 0;
-  display: none;
-}
-
-.submenu-content li:first-child a {
-  border-radius: 12px 12px 0 0;
-}
-
-.submenu-content li:last-child a {
-  border-radius: 0px 0px 12px 12px;
-}
-
-.submenu.open .submenu-content {
-  display: initial;
-}
-
-#navmenu {
-  padding: 0;
-  margin: 0;
-  right: 0px;
-  z-index: 1000;
-  margin-right: 15px;
-}
-
-.submenu-content li a {
-  display: block;
-  padding: 2px 20px 2px 20px;
-}
-
-#navbar .submenu-content a:hover {
-  background: var(--hover-bg);
-  text-decoration: none;
-}
-
-
-/* TOC side menu */
-
-.toc-container {
-  position: sticky;
-  top: 100px;
-  width: 270px
-}
-
-#menu {
-  min-width: 13rem;
-  padding-inline: 0.5rem;
-  font-size: 1rem;
-  overflow-y: auto;
-  max-height: 65vh;
-  padding-block-end: 0.5rem;
-  margin-block: 0;
-}
-
-#menu.blog-side-menu {
-  max-width: 20rem;
-  max-height: fit-content;
-}
-
-#menu ul a,
-#menu > li > a {
-  display: block;
-  color: var(--menu-grey);
-  padding-inline: 0.5rem;
-  text-decoration: none;
-
-  &:is(:hover,:active,:focus) {
-    border-radius: 0.3rem;
-    color: var(--fg);
-    outline: 1px solid var(--card-fg);
-  }
-}
-
-#menu ul a.active {
-  border-radius: 0.3rem;    
-  color: var(--fg);
-  outline: 1px solid var(--card-fg); 
-}
-
-#menu em {
-  font-weight: bold;
-  color: var(--menu-em);
-  font-size: 1rem;
-}
-
-#menu li {
-  cursor: pointer;
-  list-style: none;
-  margin-block-start: 0.3rem;
-}
-
-#menu ul,
-ul#side-menu  {
-  display: none;
-  opacity: 0;
-  height: 0;
-  overflow: hidden;
-}
-
-#menu ul.active,
-ul#side-menu.active {
-  height: auto;
-  padding-inline: 0.5rem;
-  display: block;
-  opacity: 1;
-  padding-block: 0.5rem;
-}
-
-#menu > li > a {
-  font-weight: bold;
-  font-size: 1rem;
-  padding-inline-start: 1rem;
-}
-
-/* can't find this in proj*/
-h2 a {
-  color: var(--card-fg) !important;
-}
-
-/* search */
-
-#q {
-  display: none;
-  height: 2.5em;
-  max-width: 100%;
-  padding: 5px;
-} 
-
-.algolia-autocomplete {
-  max-width: 9em;
-  > input {
-    color: var(--fg);
-    background-color: var(--bg);
-  }
-  > input::placeholder {
-    color: var(--fg);
-  }
-  #q {
-    display: initial;
-    border-radius: 8px;
-    border: 1px solid var(--border);
-    transition: color .3s ease;
-    padding-inline: 12px;
-    outline: none;
-    &:focus-visible,
-    &:focus {
-      border-color: var(--hover-border);
-      border-width: 2px;
-    }
-  }
-}
-
- #navbar {
-  .ds-dropdown-menu .ds-dataset-1 {
-    background-color: var(--bg);
-    .ds-suggestions {
-      /* background-color: var(--bg); */
-      color: var(--fg);
-    }
-    .ds-suggestion a {
-      background-color: var(--bg);
-      color: var(--fg);
-    }
-    .ds-suggestion a {
-      background-color: var(--bg);
-      color: var(--fg);
-    }
-    .algolia-docsearch-suggestion--category-header {
-      color: var(--fg);
-    }
-    .algolia-docsearch-suggestion--wrapper {
-      background-color: var(--bg);
-      .algolia-docsearch-suggestion--subcategory-column {
-        color: var(--menu-grey);
-  
-      }
-      .algolia-docsearch-suggestion--title, 
-      .algolia-docsearch-suggestion--text  {
-        color: var(--fg);
-      }
-      .algolia-docsearch-suggestion--highlight {
-        color: var(--link);
-        background-color: initial;
-      }
-    }
-    .algolia-docsearch-suggestion {
-        background-color: initial;
-      }
-      .algolia-docsearch-suggestion--content .algolia-docsearch-suggestion--no-results{
-        background-color: initial; 
-      }
-    
-  }
-   .ds-suggestion.ds-cursor .algolia-docsearch-suggestion--title,
-   .ds-suggestion.ds-cursor .algolia-docsearch-suggestion--content {
-     background-color: var(--hover-bg);
-   }
- }
-
-
-.content-404 {
-  height: 70vh;
-  padding: 153px 32px 7%;
-  text-align: center;
-  display: flex;
-  justify-content: center;
-  flex-direction: column;
-  grid-area: content;
-}
-
-.content-404 p {
-  font-size: 16px;
-}
-
-/* search-bar desktop re-sizing */
-@media all and (min-width: 950px) {
-  .algolia-autocomplete {
-    margin-right:15px;
-    max-width: 12em;
-  }
-}
-
-/* toc title */
-.toc-heading {
-  display: block;
-  cursor: default;
-  padding-inline-start: 1rem;
-  & > em {
-    font-weight: bold;
-    color: var(--menu-em);
-    font-size: 1rem;
-  }
-}
-
-
-/* TOC btn */
-
-#menu-toggle {
-  cursor: pointer;
-  display: none;
-  font-size: 1rem;
-  padding: 0.5rem;
-  opacity: 0;
-  width: fit-content;
-  border: 1px solid #000;
-  border-radius: 0.3rem;
-  color: #000;
-  background-color: #fff;
-
-   &::after {
-    content: "";
-    display: block;
-    width: 0.8em;
-    height: 0.5em;
-    background-color: var(--card-bg);
-    clip-path: polygon(100% 0%, 0 0%, 50% 100%);
-    cursor: pointer;
-    pointer-events: none;
-    transition: transform 0.2s ease-in-out;
-    transform: rotate(-90deg);
-  }
-
-  &:is(:hover, :active, :focus) {
-    background-color: #ebf2f5;
-  }
-}
-
-/* 'Prev' left and 'Next' right btn */
-.bottom-navigation {
-  display: flex;
-  justify-content: space-between;
-  flex-wrap: wrap;
-  margin-block: 1rem;
-  font-weight: 500;
-  font-size: 1.2rem;
-}
-
-.bottom-nav-prev {
-  text-align: left;
-  max-width: 50%;
-}
-
-.bottom-nav-next {
-  text-align: right;
-  max-width: 50%;
-}
-
-/* routing methods columns */
-.methods-columns {
-  display: flex;
-  gap: 2rem;
-  justify-content: space-between;
-  flex-wrap: wrap;
-
-  @media screen and (max-width: 460px) {
-    flex-direction: column;
-    gap: 0.3rem;
-  }
-}
-
-/* responsive */
-
-@media all and (max-width: 1440px) {
-  #menu{
-    top: 75px;
-  }
-}
-
-@media all and (max-width: 1110px) {
-  #boxes {
-    grid-template-columns: 1fr 1fr;
-  }
-
-  #home-content {
-    flex-direction: column;
-  }
-
-  .install-command {
-    display: none;
-  }
-
-  #home-content .pane {
-    min-width: auto;
-    font-size: 74%;
-  }
-
-  #homepage-leftpane {
-    padding-top: 0px;
-  }
-
-  #homepage-rightpane {
-    padding-top: 0;
-    padding-right: 0;
-  }
-
-  .table-scroller {
-    width: 100%;
-    overflow: scroll;
-    scrollbar-width: thin;
-  }
-
-  code {
-    word-break: break-all;
-  }
-
-  ul {
-    padding-left: 5%;
-  }
-
-  h1 {
-    font-size: 22px;
-    line-height: 26px;
-  }
-
-  h2 {
-    font-size: 18px;
-    line-height: 25px;
-  }
-
-  h3 {
-    font-size: 16px;
-    line-height: 23px;
-    word-break: break-all;
-  }
-
-  h4 {
-    font-size: 16px;
-    line-height: 18px;
-    font-weight: normal;
-  }
-
-  #home-content {
-    margin: 60px 0 0 5%;
-    padding-right: 5%;
-  }
-
-  #description {
-    margin-bottom: 35px;
-  }
-
-  #description .description {
-    font-size: 3em;
-    line-height: .9em;
-    font-weight: 200;
-  }
-
-  .logo-container {
-    margin-inline: auto;
-  }
-
-  #home-menu {
-    display: block;
-    position: absolute;
-    top: 7px;
-  }
-
-  #overlay.blurs{
-    display: block;
-  }
-
-  .menu ul {
-    display: block;
-  }
-
-  #footer-content {
-    flex-wrap: wrap;
-    justify-content: center;
-  }
-
-  #footer-copyright > a {
-    width: 100%;
-    display: flex;
-    justify-content: center;
-  }
-
-  .header-right {
-    display: flex;
-    gap: 8px;
-  }
-}
-
-/* TOC responsive */
-@media all and (max-width: 800px) {
-  .content {
-    flex-direction: column;
-    padding-inline-start : 0;
-    margin-block-start: 1rem;
-  }
-
-  .content main {
-    padding-inline: 1rem;
-    width: 100vw;
-    margin-top: 0;
-    margin-inline: 0;
-  }
-  
-  #api-doc,
-  #blog-doc,
-  #page-doc {
-    width: 100%;
-  }
-
-  #api-doc section {
-    padding-left: 0;
-  }
-
-  .toc-container {
-    display: flex;
-    flex-direction: column;
-    gap: 0;
-    padding: 1rem;
-  }
-
-  #menu {
-    display: none;
-    opacity: 0;
-    max-height: 0;
-    background-color: var(--card-bg);
-    min-width: 100%;
-  }
-
-  #menu.open {
-    display: block;
-    opacity: 1;
-    max-height: 35vh;
-    padding-inline: 1rem;
-    border-left: 2px solid var(--border);
-    margin-top: 0.3rem;
-    border-bottom-right-radius: 0.5rem;
-    border-top-right-radius: 0.5rem;
-  }
-
-  .toc-container {
-    width: 100%;
-  }
-
-  #menu-toggle.show {
-    display: flex;
-    gap: 0.5rem;
-    align-items: center;
-    opacity: 1;
-  }
-
-  #menu-toggle.show.rotate::after {
-    transform: rotate(0deg);
-  }
-
-  #menu > li > a,
-  #menu ul a {
-    padding: 0.5rem;
-    &:is(:hover,:active,:focus) {
-      background: var(--hover-bg);
-    }
-  }
-
-  #menu li ul li > em {
-    font-size: 0.8rem;
-    padding-inline: 1rem;
-    padding-block: 0.3rem;
-    background-color: var(--hover-bg);
-    border-radius: 0.3rem;
-   }
-
-   .toc-heading{
-    display: none;
-  }
-}
-
-
-@media all and (max-width: 540px) {
-  #boxes {
-    grid-template-columns: 1fr;
-  }
-}
-
-@media all and (max-width: 420px) {
-  #app-settings-property {
-    width: auto;
-  }
-}
-
-
-@media print {
-
-  header {
-    position: absolute;
-  }
-}
-
-/* For image callouts in writing-middleware.md  */
-
-.callout {position: relative;}
-
-#mw-fig { 
-  border-collapse: separate; 
-  padding: 0; 
-  border: 0; 
-  width: 960px; 
-  margin-bottom: 20px;
-}
-#mw-fig-imgcell {
-  margin: 0;
-  padding: 0px;
-  border: 0;
-  width: 410px;
-}
-#mw-fig-img {
-  margin: 0px;
-  padding: 0px;
-  width: 410px;
-  height: 308px;
-}
-
-.mw-fig-callouts {
-  margin: 0;
-  padding: 0 0 0 5px;
-  border: 0;
-  width: 550px;
-}
-
-/* Blog page styles*/
-#blog-doc {
-  margin: 0 1rem;
-  @media all and (max-width: 800px) {
-    margin: 0;
-  }
-}
-#blog-doc:has(> h1#express-blog),
-#blog-doc:has(> h1#write-a-blog-post) {
-  min-height: 300px;
-}
-#blog-doc .blog-details ~ p > img {
-  width: 200px;
-  float: right;
-  margin: 0.5rem;
-}
-#blog-doc p {
-  font-size: 1.1em;
-}
-.blog-posts {
-  display: flex;
-  flex-direction: column;
-  row-gap: 10px;
-}
-.blog-post {
-  width: 100%;
-  background-color: var(--card-bg);
-  display: flex;
-  padding: 10px;
-  flex-direction: column;
-  justify-content: space-between;
-  border-radius: 5px;
-  border: 1px solid var(--border);
-  box-shadow: 2px 3px var(--hover-fg);
-  transition: 0.3s;
-}
-.blog-post:hover {
-  background-color: var(--hover-bg);
-  border: 1px solid var(--hover-border);
-  box-shadow: 2px 3px var(--menu-grey);
-}
-.blog-post img {
-  max-width: 100%;
-  max-height: 100%;
-  object-fit: cover;
-}
-.blog-post .blog-details {
-  display: flex;
-  flex-direction: column;
-}
-.blog-details div:first-child {
-  margin-bottom: 5px;
-}
-.blog-tag {
-  font-size: 12px;
-}
-.blog-title {
-  font-size: 1.3rem;
-  line-height: 1.5rem;
-  font-weight: 500;
-  padding-right: .2em;
-}
-.blog-title a {
-  color: var(--card-fg)
-}
-.blog-excerpt {
-  font-size: .75rem;
-}
-.blog-img {
-  max-width: 100%;
-  margin: auto;
-}
-.blog-authors {
-  font-style: italic;
-}
-.blog-author-link {
-  color: inherit;
-  margin-left: 0.5ch;
-  text-decoration: none;
-}
-.blog-author-link-label {
-  text-decoration: underline;
-}
-.blog-author-avatar {
-  border-radius: 50%;
-  display: inline-block;
-  vertical-align: middle;
-  width: 1.5em;
-  height: 1.5em;
-}
-.blog-date {
-  font-weight: bold;
-  font-size: 85%;
-}
-/* mobile-only */
-@media (max-width: 500px) {
-  #blog-doc {
-    display: flex;
-    flex-wrap: wrap;
-    flex-direction: column;
-    align-items: center;
-    margin-right: 0;
-    padding-right: 10px;
-  }
-  #blog-doc .blog-details + p > img {
-    margin-bottom: 15px;
-  }
-}
-
-
-
-/* blog tablet and up*/
-@media (min-width: 768px) {
-  .blog-post {
-    margin: auto;
-  }
-  .blog-tags {
-    margin-bottom: 20px;
-  }
-  .blog-title {
-    font-size: 1.3rem;
-    margin-bottom: 20px;
-    line-height: 1.5rem;
-  }
-  .blog-post .blog-details {
-    display: flex;
-    flex-direction: row;
-    margin-left: 1rem;
-    font-size: 90%;
-  }
-  .blog-post .blog-details div:first-child {
-    margin-right: 20px;
-  }
-  .blog-details  {
-    font-size: 1rem;
-  }
-  .blog-excerpt {
-    line-height: initial;
-    font-size: .85rem;
-    font-weight: 300;
-    margin-top: auto;
-    margin-bottom: 10px;
-    max-width: 80%;
-  }
-}
-
-strong.supported {
-  color: var(--supported-fg) ;
-}
-strong.eol {
-  color: var(--eol-fg) ;
-}
-
-.logo-table {
-  display: flex;
-  flex-wrap: wrap;
-  row-gap: 8px;
-  column-gap: 48px;
-}
-
-.logo-table h3{
-  margin-bottom: 12px;
-}
-
-blockquote {
-  margin-left: 0;
-  font-weight: 600;
-  font-style: italic;
-  padding-left: 1.2em;
-  border-left: .25rem solid var(--border);
-}
-
-@media all and (max-width: 1110px) {
-  .algolia-autocomplete {
-    display: none !important;
-  }
-
-  #mobile-menu {
-    display: block;
-  }
-
-  #navbar {
-    padding: 0;
-    top: 1px;
-    position: static;
-  }
-
-  #navmenu>li:first-child {
-    display: none;
-  }
-
-  #navmenu>li {
-    border-bottom: 1px solid var(--border);
-    margin: 0;
-    min-height: 47px;
-    background: var(--card-bg);
-    cursor: pointer;
-    display: flex;
-    align-items: center;
-  }
-
-  #navmenu>li.open:hover {
-    background: var(--card-bg);
-  }
-  #navmenu>li:hover {
-    background: var(--hover-bg);
-    & ul {
-      background-color: var(--card-bg);
-    }
-  }
-
-  #navmenu {
-    left: 0;
-    padding: 0;
-    top: 57px;
-    width: 100%;
-    position: absolute;
-    display: none;
-  }
-
-  #navmenu.opens {
-    display: block;
-    max-height: calc(100dvh - var(--header-height));
-    overflow-y: auto;
-    overscroll-behavior: contain;
-  }
-
-  #navbar a {
-    font-size: 19px;
-    margin: 0;
-    width: 100%;
-    height: 100%;
-    padding-left: 5%;
-  }
-
-  #navbar .submenu.open {
-    flex-direction: column;
-    align-items: initial;
-    > a {
-      border-bottom: 1px solid var(--border);
-    }
-  }
-
-  .submenu.open > a {
-    display: flex;
-    align-items: center;
-    min-height: 47px;
-  }
-
-  .submenu-content {
-    width: 100%;
-    position: static;
-    display: none;
-    margin-top: 7px;
-    background-color: var(--card-bg);
-    padding: 0;
-    margin: 0;
-    border: none;
-    border-radius: 0;
-    box-shadow: none;
-    max-height: 190px;
-    overflow-y: auto;
-    overflow-x: hidden;
-    transform: none;
-    cursor: pointer;
-  }
-
-  .submenu-content li > a {
-    width: 100%;
-  }
-
-  .submenu-content li:first-child a {
-    border-radius: 0;
-  }
-
-  .submenu-content li:last-child {
-    border-bottom: 0;
-  }
-
-  .submenu-content li:last-child a {
-    border-radius: 0;
-  }
-
-  .submenu-content.open {
-    display: inline-block;
-  }
-
-  #navbar .submenu-content li a {
-    font-size: 16px;
-    padding: 5px 5px 5px 5%;
-    padding-left: 10%;
-  }
-
-  .submenu-content li {
-    border-bottom: 1px solid var(--border);
-  }
-}
-
-
diff --git a/css/themes/dark-theme.css b/css/themes/dark-theme.css
deleted file mode 100644
index 0c6a563696..0000000000
--- a/css/themes/dark-theme.css
+++ /dev/null
@@ -1,21 +0,0 @@
-html.dark-mode {
-
-  #icon-sun { 
-    display: inline; 
-  }
-  
-  .submenu-content {
-    box-shadow: 1px 2px var(--hover-bg);
-    background-color: var(--card-bg);
-  }
-
-  #navmenu>li:hover {
-    ul {
-      background-color: var(--card-bg);
-    }
-  }
-  
-  .blog-excerpt {
-    color: var(--notice-accent);
-  }
-}
\ No newline at end of file
diff --git a/css/variables.css b/css/variables.css
deleted file mode 100644
index 5680810934..0000000000
--- a/css/variables.css
+++ /dev/null
@@ -1,52 +0,0 @@
-:root.light-mode {
-  --grey-fg: #aeaeae;
-  --bg: #ffffff;
-  --fg: #383838;
-  --card-bg: #f0f1f3; 
-  --card-fg: #383838; 
-  /* text (api side menus h3...)  */
-  --menu-grey: #888; 
-  --hover-border: #484848; 
-  --hover-bg: #D3D3D3; 
-  --hover-fg: #fafafa;
-  --border: #d9e1e4; 
-  --link: #0e78ce;
-    /* docs related */
-  --box-fg: #181818;
-  --info-bg: #cfd4fc;
-  --info-accent: #0f1c8a;
-  --notice-bg: #fceac5;
-  --notice-accent: #2E1D00;
-  --warn-bg: #fad1df;
-  --warn-accent: #8a0f3a;
-  --code-bg: #f0f1f3;
-  /* support page related */
-  --supported-fg: #009000;
-  --eol-fg: #ff0000;
-}
-:root.dark-mode {
-  --bg: #0c0c0c;
-  --fg: #fafafa;
-  --card-bg: #181818;  
-  --card-fg: #f7f4f4;
-  --hover-bg: #262626;
-  --hover-fg: #f2f2f2;
-  --hover-border: #fafafa;
-  --border: #d9e1e4;
-  /* text (api side menus h3...) */
-  --menu-grey: silver;
-  --link: #259dff;
-  --menu-em: #a2a0a0eb;
-    /* docs related */
-  --box-fg: #ffffff;
-  --info-bg: #171d4f;
-  --info-accent: #bdc3ff;
-  --notice-bg: #4e4022;
-  --notice-accent: #f9e8c3;
-  --warn-bg: #4e2232;
-  --warn-accent: #f9c3d6;
-  --code-bg: #2b2b2b;
-    /* support page related */
-  --supported-fg:#299009;
-  --eol-fg: #ff1a1a;
-}
diff --git a/de/3x/api.md b/de/3x/api.md
deleted file mode 100644
index e3655297ab..0000000000
--- a/de/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API-Referenz
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x WIRD NICHT MEHR GEWARTET**
-
-Bekannte und unbekannte Probleme bei Sicherheit und Leistung in 3.x wurden seit dem letzten Update (1. August 2015) noch nicht behoben. Es wird dringend empfohlen, die aktuelle Version von Express zu verwenden.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>3.x-API</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/de/4x/api.md b/de/4x/api.md
deleted file mode 100644
index ffdc703de2..0000000000
--- a/de/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API-Referenz
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>4.x-API</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/de/5x/api.md b/de/5x/api.md
deleted file mode 100644
index cb8a847d02..0000000000
--- a/de/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API-Referenz
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/de/advanced/best-practice-performance.md b/de/advanced/best-practice-performance.md
deleted file mode 100644
index 9ea397be26..0000000000
--- a/de/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: Leistungsspezifische Best Practices für Express-Anwendungen in Produktionsumgebungen
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# Best Practices in Produktionsumgebungen: Leistung und Zuverlässigkeit
-
-In diesem Beitrag werden Best Practices in Bezug auf Leistung und Zuverlässigkeit für Express-Anwendungen behandelt, die in der Produktionsumgebung bereitgestellt werden.
-
-Dieses Thema gehört sicherlich zur "DevOps"-Welt und deckt traditionelle Entwicklungs- und Betriebsprozesse ab. Entsprechend sind die Informationen hier in zwei Teile unterteilt:
-
-- Things to do in your code (the dev part):
-  - Für statische Dateien Middleware verwenden
-  - Keine synchronen Funktionen verwenden
-  - [Do logging correctly](#do-logging-correctly)
-  - [Handle exceptions properly](#handle-exceptions-properly)
-- Things to do in your environment / setup (the ops part):
-  - NODE_ENV auf "production" festlegen
-  - Automatischen Neustart Ihrer Anwendung sicherstellen
-  - Anwendung in einem Cluster ausführen
-  - Anforderungsergebnisse im Cache speichern
-  - Load Balancer verwenden
-  - Reverse Proxy verwenden
-
-## Things to do in your code {#in-code}
-
-Dies sind einige Beispiele für Maßnahmen, die Sie an Ihrem Code vornehmen können, um die Anwendungsleistung zu verbessern:
-
-- Für statische Dateien Middleware verwenden
-- Keine synchronen Funktionen verwenden
-- [Do logging correctly](#do-logging-correctly)
-- [Handle exceptions properly](#handle-exceptions-properly)
-
-### GZIP-Komprimierung verwenden
-
-Mit der GZIP-Komprimierung lässt sich die Größe des Antworthauptteils deutlich verringern und somit die Geschwindigkeit der Webanwendung erhöhen. Verwenden Sie die Middleware [compression](https://www.npmjs.com/package/compression) für die GZIP-Komprimierung in Ihrer Express-Anwendung. Beispiel:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-Bei Websites mit hohem Datenverkehr in Produktionsumgebungen lässt sich die Komprimierung am besten installieren, indem sie auf Reverse Proxy-Ebene implementiert wird (siehe [Reverse Proxy verwenden](#proxy)). In diesem Fall wird die Middleware "compression" nicht benötigt. Details zur Aktivierung der GZIP-Komprimierung in Nginx siehe [Modul ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) in der Nginx-Dokumentation.
-
-### Keine synchronen Funktionen verwenden
-
-Synchrone Funktionen und Methoden belasten den Ausführungsprozess, bis sie zurückgegeben werden. Ein einzelner Aufruf für eine synchrone Funktion kann in wenigen Mikrosekunden oder Millisekunden zurückgegeben werden. Bei Websites mit hohem Datenverkehr hingegen summieren sich diese Aufrufe und verringern die Leistung der Anwendung. Sie sollten also deren Verwendung in Produktionsumgebungen vermeiden.
-
-Auch wenn Node und viele andere Module synchrone und asynchrone Versionen ihrer Funktionen bieten, sollten Sie in Produktionsumgebungen immer die asynchrone Version verwenden. Nur beim ersten Systemstart ist die Verwendung einer synchronen Funktion begründet.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Auch wenn Sie diese natürlich nicht in der Produktionsumgebung verwenden werden, soll dadurch trotzdem sichergestellt werden, dass Ihr Code in der Produktionsumgebung eingesetzt werden kann. Weitere Informationen hierzu siehe [Wöchentliches Update für io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0).
-
-### Do logging correctly
-
-Im Allgemeinen gibt es für die Protokollierung Ihrer Anwendung zwei Gründe: 1) Debugging und 2) Protokollierung von Anwendungsaktivitäten (im Wesentlichen alles andere, außer Debugging). Die Verwendung von`console.log()` oder `console.err()` zur Ausgabe von Protokollnachrichten an das Terminal ist in der Entwicklung gängige Praxis. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### Für Debuggingzwecke
-
-Wenn Sie die Protokollierung für Debuggingzwecke nutzen, sollten Sie statt `console.log()` besser ein spezielles Debuggingmodul wie [debug](https://www.npmjs.com/package/debug) verwenden. Mit einem solchen Modul können Sie über die Umgebungsvariable DEBUG steuern, welche Debugnachrichten an `console.err()` gesendet werden (falls vorhanden). Um Ihre Anwendung rein asynchron zu halten, können Sie trotzdem `console.err()` per Pipe zu einem anderen Programm umleiten. Sie nehmen dann aber kein Debugging in der Produktionsumgebung vor, richtig?
-
-#### Für Anwendungsaktivitäten
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Ausnahmebedingungen ordnungsgemäß handhaben
-
-Node-Anwendungen stürzen ab, wenn eine nicht abgefangene Ausnahmebedingung vorkommt. Wenn diese Ausnahmebedingungen nicht behandelt und entsprechende Maßnahmen eingeleitet werden, stürzt Ihre Express-Anwendung ab und geht offline. Wenn Sie dem nachfolgenden Rat in [Sicherstellen, dass Ihre Anwendung automatisch neu gestartet wird](#restart) folgen, wird Ihre Anwendung nach einem Absturz wiederhergestellt. Glücklicherweise haben Express-Anwendungen nur eine kurze Initialisierungszeit. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
-
-Mit folgenden Verfahren stellen Sie sicher, dass alle Ausnahmebedingungen gehandhabt werden:
-
-- ["try-catch" verwenden](#try-catch)
-- ["Promises" verwenden](#promises)
-
-Um näher auf diese Themen eingehen zu können, müssen Sie sich ein grundlegendes Verständnis der Fehlerbehandlung in Node und Express aneignen: Verwendung von Error-first-Callbacks und Propagieren von Fehlern in Middleware. Node verwendet die Konvention "Error-first-Callback" für die Rückgabe von Fehlern von asynchronen Funktionen, bei denen der erste Parameter zur Callback-Funktion das Fehlerobjekt ist, gefolgt von Ergebnisdaten in den nachfolgenden Parametern. Um anzugeben, dass kein Fehler vorliegt, müssen Sie "null" als ersten Parameter übergeben. Die Callback-Funktion muss der Konvention "Error-first-Callback" folgen, um den Fehler sinnvoll bearbeiten zu können. In Express hat sich bewährt, die Funktion "next()" zu verwenden, um Fehler über die Middleware-Chain zu propagieren.
-
-Weitere Informationen zu den Grundlagen der Fehlerbehandlung siehe:
-
-- [Fehlerbehandlung in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### "try-catch" verwenden
-
-"try-catch" ist ein JavaScript-Sprachkonstrukt, mit dem Sie Ausnahmebedingungen in synchronem Code abfangen können. Verwenden Sie "try-catch" beispielsweise, um JSON-Parsing-Fehler wie unten gezeigt zu bearbeiten.
-
-Dies ist ein Beispiel zur Verwendung von "try-catch", um eine potenzielle "process-crashing"-Ausnahmebedingung zu handhaben.
-Diese Middlewarefunktion akzeptiert einen Abfragefeldparameter mit dem Namen "params", der ein JSON-Objekt ist.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-"try-catch" funktioniert jedoch nur in synchronem Code. Da die Node-Plattform primär asynchron ist (insbesondere in einer Produktionsumgebung), lassen sich mit "try-catch" nicht besonders viele Ausnahmebedingungen abfangen.
-
-#### "Promises" verwenden
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### What not to do
-
-Sie sollten _auf keinen_ Fall per Listener das Ereignis `uncaughtException` überwachen, das ausgegeben wird, wenn eine Ausnahmebedingung bis zurück zur Ereignisschleife bestehen bleibt. Durch das Hinzufügen eines Ereignislisteners für `uncaughtException` verändert sich das Standardverhalten des Prozesses, über das eine Ausnahmebedingung festgestellt wird. Das Ausführen einer Anwendung nach einer nicht abgefangenen Ausnahmebedingung ist aber eine durchaus riskante Vorgehensweise und wird nicht empfohlen, da der Prozessstatus störanfällig und unvorhersehbar wird.
-
-Außerdem wird die Verwendung von `uncaughtException` offiziell als [grobes Vorgehen](https://nodejs.org/api/process.html#process_event_uncaughtexception) angesehen, sodass es den [Vorschlag](https://github.com/nodejs/node-v0.x-archive/issues/2582) gibt, die Funktion aus dem Kern zu entfernen. Das Überwachen von `uncaughtException` per Listener ist also keine gute Idee. Daher empfehlen wir Dinge wie Mehrfachprozesse und Supervisoren: Ein Absturz und anschließender Neustart ist häufig die zuverlässigste Art der Fehlerbehebung.
-
-Zudem empfehlen wir, [domains](https://nodejs.org/api/domain.html) nicht zu verwenden. Mit diesem Modul, das zudem veraltet ist, lässt sich das Problem in der Regel nicht lösen.
-
-## Things to do in your environment / setup {#in-environment}
-
-Dies sind einige Beispiele für Maßnahmen, die Sie an Ihrer Systemumgebung vornehmen können, um die Anwendungsleistung zu verbessern:
-
-- NODE_ENV auf "production" festlegen
-- Automatischen Neustart Ihrer Anwendung sicherstellen
-- Anwendung in einem Cluster ausführen
-- Anforderungsergebnisse im Cache speichern
-- Load Balancer verwenden
-- Reverse Proxy verwenden
-
-### NODE_ENV auf "production" festlegen
-
-In der Umgebungsvariablen NODE_ENV wird die Umgebung angegeben, in der eine Anwendung ausgeführt wird (in der Regel ist dies die Entwicklungs- oder Produktionsumgebung). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-Durch das Festlegen von NODE_ENV auf "production" führt Express Folgendes aus:
-
-- Speichern von Anzeigevorlagen im Cache.
-- Speichern von CSS-Dateien, die aus CSS-Erweiterungen generiert wurden, im Cache.
-- Generieren von weniger ausführlichen Fehlernachrichten.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-Wenn Sie umgebungsspezifischen Code schreiben müssen, können Sie den Wert von NODE_ENV mit `process.env.NODE_ENV` überprüfen. Beachten Sie, dass die Überprüfung des Werts seiner Umgebungsvariablen eine leistungsbezogene Penalisierung nach sich zieht.
-
-In einer Entwicklungsumgebung wird die Umgebungsvariable in der Regel in Ihrer interaktiven Shell festgelegt, indem Sie beispielsweise `export` oder Ihre Datei `.bash_profile` verwenden. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). Der nächste Abschnitt enthält weitere Details zur Verwendung des Init-Systems im Allgemeinen. Die Festlegung von NODE_ENV ist jedoch für das Leistungsverhalten so wichtig (und so einfach durchzuführen), dass hier besonders darauf eingegangen wird.
-
-Verwenden Sie bei systemd die Anweisung `Environment` in Ihrer Einheitendatei. Beispiel:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### Automatischen Neustart Ihrer Anwendung sicherstellen
-
-In der Produktionsumgebung sollte die Anwendung nie offline sein. Das bedeutet, dass Sie sicherstellen müssen, dass die Anwendung bei einem Absturz der Anwendung oder des Servers immer wieder neu gestartet wird. Auch wenn man hofft, das keines dieser Ereignisse jemals eintritt, muss man doch mit beiden Möglichkeiten rechnen und:
-
-- einen Prozessmanager verwenden, um die Anwendung (und Node) bei einem Absturz neu zu starten.
-- das Init-System Ihres Betriebssystems verwenden, um den Prozessmanager bei einem Absturz des Betriebssystems neu zu starten. Außerdem kann das Init-System auch ohne einen Prozessmanager verwendet werden.
-
-Node-Anwendungen stürzen ab, wenn eine nicht abgefangene Ausnahmebedingung auftritt. Als Erstes müssen Sie in einem solchen Fall sicherstellen, dass Ihre Anwendung ausreichend getestet wurde und in der Lage ist, alle Ausnahmebedingungen zu handhaben (weitere Informationen siehe [Ausnahmebedingungen ordnungsgemäß handhaben](#exceptions)). Die sicherste Maßnahme ist jedoch, einen Mechanismus zu implementieren, über den bei einem Absturz der Anwendung ein automatischer Neustart der Anwendung ausgeführt wird.
-
-#### Prozessmanager verwenden
-
-In Entwicklungumgebungen wird die Anwendung einfach über die Befehlszeile mit `node server.js` oder einer vergleichbaren Datei gestartet. In der Produktionsumgebung hingegen ist durch diese Vorgehensweise die Katastrophe bereits vorprogrammiert. Wenn die Anwendung abstürzt, ist sie solange offline, bis Sie sie erneut starten. Um sicherzustellen, dass Ihre Anwendung nach einem Absturz neu gestartet wird, sollten Sie einen Prozessmanager verwenden. Ein Prozessmanager ist ein "Container" für Anwendungen, der die Bereitstellung erleichtert, eine hohe Verfügbarkeit sicherstellt und  die Verwaltung der Anwendung zur Laufzeit ermöglicht.
-
-Neben einem Neustart der Anwendung nach einem Absturz bietet ein Prozessmanager noch weitere Möglichkeiten:
-
-- Einblicke in die Laufzeitleistung und die Ressourcennutzung
-- Dynamische Änderung der Einstellungen zur Verbesserung des Leistungsverhaltens
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### Init-System verwenden
-
-Als nächste Ebene der Zuverlässigkeit müssen Sie sicherstellen, dass Ihre Anwendung bei einem Serverneustart neu gestartet wird. Systeme können immer wieder aus verschiedenen Gründen abstürzen. Um sicherzustellen, dass Ihre Anwendung bei einem Serverabsturz neu gestartet wird, können Sie das in Ihr Betriebssystem integrierte Init-System verwenden. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-Es gibt zwei Möglichkeiten, Init-Systeme mit Ihrer Express-Anwendung zu verwenden:
-
-- Ausführung Ihrer Anwendung in einem Prozessmanager und Installation des Prozessmanagers als Service mit dem Init-System. Der Prozessmanager wird neu gestartet, wenn Ihre Anwendung abstürzt. Dies ist die empfohlene Vorgehensweise.
-- Ausführung Ihrer Anwendung (und von Node) direkt mit dem Init-System. Diese Vorgehensweise ist zwar etwas einfacher, Sie profitieren jedoch nicht von den zusätzlichen Vorteilen des Einsatzes eines Prozessmanagers.
-
-##### systemd
-
-"systemd" ist ein Linux-System und Service-Manager. Die meisten wichtigen Linux-Distributionen haben "systemd" als Init-Standardsystem übernommen.
-
-Eine "systemd"-Servicekonfigurationsdatei wird als _Einheitendatei_ bezeichnet, die die Endung ".service" hat. Dies ist ein Beispiel für eine Einheitendatei zur direkten Verwaltung einer Node-Anwendung (ersetzen Sie den Text in Fettdruck durch Werte für Ihr System und Ihre Anwendung): Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Weitere Informationen zu "systemd" siehe [systemd-Referenz (Man-Page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-### Anwendung in einem Cluster ausführen
-
-In einem Multi-Core-System können Sie die Leistung einer Node-Anwendung mehrmals erhöhen, indem Sie einen Cluster von Prozessen starten. Ein Cluster führt mehrere Instanzen der Anwendung aus, idealerweise eine Instanz auf jedem CPU-Core.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-Wichtig. Da die Anwendungsinstanzen als separate Prozesse ausgeführt werden, nutzen sie nicht dieselbe Hauptspeicherkapazität gemeinsam. Das heißt, Objekte befinden sich für jede Instanz der Anwendung auf lokaler Ebene. Daher kann der Status im Anwendungscode nicht beibehalten werden. Sie können jedoch einen speicherinternen Datenspeicher wie [Redis](http://redis.io/) verwenden, um sitzungsrelevante Daten und Statusinformationen zu speichern. Diese Einschränkung trifft im Wesentlichen auf alle Formen der horizontalen Skalierung zu, unabhängig davon, ob es sich um Clustering mit mehreren Prozessen oder mehreren physischen Servern handelt.
-
-Bei in Gruppen zusammengefassten Anwendungen (geclusterte Anwendungen) können Verarbeitungsprozesse einzeln ausfallen, ohne dass sich dies auf die restlichen Prozesse auswirkt. Neben den Leistungsvorteilen ist die Fehlerisolierung ein weiterer Grund, einen Cluster von Anwendungsprozessen auszuführen. Wenn ein Verarbeitungsprozess abstürzt, müssen Sie sicherstellen, dass das Ereignis protokolliert und ein neuer Prozess mithilfe von "cluster.fork()" gestartet wird.
-
-#### Clustermodule von Node verwenden
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). Dadurch wird ein Masterprozess eingeleitet, um Verarbeitungsprozesse zu starten und eingehende Verbindungen auf die Verarbeitungsprozesse zu verteilen.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### Anforderungsergebnisse im Cache speichern
-
-Eine weitere Strategie zur Verbesserung des Leistungsverhaltens in Produktionsumgebungen ist das Speichern von Anforderungergebnissen im Cache. Ihre Anwendung muss also diese Operation nicht wiederholt ausführen, um dieselbe Anforderung wiederholt zu bedienen.
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### Load Balancer verwenden
-
-Unabhängig davon, wie gut eine Anwendung optimiert wurde, kann eine Einzelinstanz nur eine begrenzte Arbeitslast oder einen begrenzten Datenverkehr handhaben. Eine Möglichkeit, eine Anwendung zu skalieren, ist die Ausführung mehrerer Instanzen dieser Anwendung und die Verteilung des Datenverkehrs über eine Lastausgleichsfunktion (Load Balancer) vorzunehmen. Die Einrichtung eines solchen Load Balancer kann helfen, Leistung und Geschwindigkeit Ihrer Anwendung zu verbessern.
-
-Ein Load Balancer ist in der Regel ein Reverse Proxy, der den Datenverkehr zu und von mehreren Anwendungsinstanzen und Servern koordiniert. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Bei einer solchen Lastverteilung müssen Sie sicherstellen, dass Anforderungen, die einer bestimmten Sitzungs-ID zugeordnet sind, mit dem Prozess verbunden sind, von dem sie ursprünglich stammen. Dies wird auch als _Sitzungsaffinität_ oder _Affine Sitzungen_ bezeichnet und kann durch den obigen Vorschlag, einen Datenspeicher wie Redis für Sitzungsdaten zu verwenden (je nach Anwendung), umgesetzt werden. Eine Beschreibung hierzu siehe [Mehrere Knoten verwenden](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Reverse Proxy verwenden
-
-Ein Reverse Proxy befindet sich vor einer Webanwendung und führt Unterstützungsoperationen für die Anforderungen aus (außer das Weiterleiten von Anforderungen an die Anwendung). Fehlerseiten, Komprimierungen und Caching bearbeiten, Dateien bereitstellen und Lastverteilungen vornehmen.
-
-Durch die Übergabe von Tasks, die keine Kenntnis des Anwendungsstatus erfordern, an einen Reverse Proxy muss Express keine speziellen Anwendungstasks mehr ausführen. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/de/advanced/best-practice-security.md b/de/advanced/best-practice-security.md
deleted file mode 100644
index 75d473657d..0000000000
--- a/de/advanced/best-practice-security.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-layout: page
-title: Sicherheitsspezifische Best Practices für Express-Anwendungen in Produktionsumgebungen
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# Best Practices in Produktionsumgebungen: Sicherheit
-
-## Überblick
-
-Der Begriff _"Produktion"_ bezieht sich auf die Phase im Softwarelebenszyklus, in der eine Anwendung oder API für Endbenutzer oder Verbraucher allgemein verfügbar ist. Im Gegensatz dazu wird in der Phase _"Entwicklung"_ noch aktiv Code geschrieben und getestet. Die Anwendung ist in dieser Phase noch nicht für externen Zugriff verfügbar. Die entsprechenden Systemumgebungen werden als _Produktionsumgebungen_ und _Entwicklungsumgebungen_ bezeichnet.
-
-Entwicklungs- und Produktionsumgebungen werden in der Regel unterschiedlich konfiguriert und weisen deutliche Unterschiede bei den Anforderungen auf. Was in der Entwicklung funktioniert, muss in der Produktion nicht unbedingt akzeptabel sein. Beispiel: In einer Entwicklungsumgebung ist eine ausführliche Protokollierung von Fehlern für Debuggingzwecke sinnvoll. Dieselbe Vorgehensweise kann in einer Produktionsumgebung jedoch zu einem Sicherheitsproblem führen. In einer Entwicklungsumgebung müssen Sie sich keine Gedanken zu Themen wie Skalierbarkeit, Zuverlässigkeit und Leistung machen, während dies in einer Produktionsumgebung kritische Faktoren sind.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-In diesem Beitrag werden einige der Best Practices in Bezug auf das Thema Sicherheit für Express-Anwendungen behandelt, die in der Produktionsumgebung bereitgestellt werden.
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - Über [hsts](https://github.com/helmetjs/hsts) werden `Strict-Transport-Security`-Header festgelegt, über die sichere (HTTP over SSL/TLS) Verbindungen zum Server durchgesetzt werden.
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - "Helmet" ist eine Ansammlung von neun kleineren Middlewarefunktionen, über die sicherheitsrelevante HTTP-Header festgelegt werden.
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - Über [xssFilter](https://github.com/helmetjs/x-xss-protection) werden `X-XSS-Protection`-Header festgelegt, um XSS-Filter (Cross-site Scripting) in den meisten aktuellen Web-Browsern zu aktivieren.
-    - Über [noCache](https://github.com/helmetjs/nocache) werden `Cache-Control`- und Pragma-Header festgelegt, um clientseitiges Caching zu deaktivieren.
-    - Über [ieNoOpen](https://github.com/helmetjs/ienoopen) werden `X-Download-Options`-Header für IE8+ festgelegt.
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
-  - [Additional considerations](#additional-considerations)
-
-## Verwenden Sie keine veralteten oder anfälligen Versionen von Express
-
-Express 2.x und 3.x werden nicht mehr gepflegt. Sicherheits- und Leistungsprobleme in diesen Versionen werden nicht mehr behoben. Verwenden Sie diese Versionen nicht! Wenn Sie noch nicht auf Version 4 umgestellt haben, befolgen Sie die Anweisungen im [Migrationshandbuch](/{{ page.lang }}/guide/migrating-4.html).
-
-Stellen Sie außerdem sicher, dass Sie keine anfälligen Express-Versionen verwenden, die auf der [Seite mit den Sicherheitsupdates](/{{ page.lang }}/advanced/security-updates.html) aufgelistet sind. Falls doch, führen Sie ein Update auf eines der stabileren Releases durch, bevorzugt das aktuelle Release.
-
-## TLS verwenden
-
-Wenn über Ihre Anwendung vertrauliche Daten bearbeitet oder übertragen werden, sollten Sie [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) verwenden, um die Verbindung und die Daten zu schützen. Diese Technologie verschlüsselt Daten, bevor sie vom Client zum Server gesendet werden. Dadurch lassen sich einige gängige (und einfache) Hackerattacken vermeiden. Auch wenn Ajax- und POST-Anforderungen nicht sofort offensichtlich und in Browsern "versteckt" zu sein scheinen, ist deren Netzverkehr anfällig für das [Ausspionieren von Paketen](https://en.wikipedia.org/wiki/Packet_analyzer) und [Man-in-the-Middle-Attacken](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-Möglicherweise sind Sie mit SSL-Verschlüsselung (Secure Socket Layer) bereits vertraut. [TLS ist einfach der nächste Entwicklungsschritt bei SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). In anderen Worten: Wenn Sie bisher SSL verwendet haben, sollten Sie ein Upgrade auf TLS in Erwägung ziehen. Generell empfehlen wir für TLS den Nginx-Server. Eine gute Referenz zum Konfigurieren von TLS auf Nginx (und anderen Servern) ist [Empfohlene Serverkonfigurationen (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-Ein handliches Tool zum Abrufen eines kostenloses TLS-Zertifikats ist außerdem [Let's Encrypt](https://letsencrypt.org/about/), eine kostenlose, automatisierte und offene Zertifizierungsstelle der [Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/).
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## "Helmet" verwenden
-
-[Helmet](https://www.npmjs.com/package/helmet) kann beim Schutz Ihrer Anwendung gegen einige gängige Schwachstellen hilfreiche Dienste leisten, indem die HTTP-Header entsprechend konfiguriert werden.
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-Installieren Sie "Helmet" wie alle anderen Module:
-
-```bash
-$ npm install helmet
-```
-
-So verwenden Sie "Helmet" in Ihrem Code:
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-Ein bewährtes Verfahren ist also, diesen Header mit der Methode `app.disable()` zu deaktivieren:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Cookies sicher verwenden
-
-Um sicherzustellen, dass Cookies Ihre Anwendung nicht für Angriffsmöglichkeiten öffnen, sollten Sie den standardmäßigen Namen des Sitzungscookies nicht verwenden und die Cookie-Sicherheitsoptionen entsprechend festlegen.
-
-Es gibt zwei wesentliche Middleware-Cookie-Sitzungsmodule:
-
-- [express-session](https://www.npmjs.com/package/express-session), das in Express 3.x integrierte `express.session`-Middleware ersetzt.
-- [cookie-session](https://www.npmjs.com/package/cookie-session), das in Express 3.x integrierte `express.cookieSession`-Middleware ersetzt.
-
-Der Hauptunterschied zwischen diesen beiden Modulen liegt darin, wie die Cookie-Sitzungsdaten gespeichert werden. Die [express-session](https://www.npmjs.com/package/express-session)-Middleware speichert Sitzungsdaten auf dem Server. Sie speichert nur die Sitzungs-ID im Cookie und nicht die Sitzungsdaten. Standardmäßig wird dabei der speicherinterne Speicher verwendet. Eine Verwendung der Middleware in der Produktionsumgebung ist nicht vorgesehen. In der Produktionsumgebung müssen Sie einen skalierbaren "Session-Store" einrichten. Siehe hierzu die Liste der [kompatiblen Session-Stores](https://github.com/expressjs/session#compatible-session-stores).
-
-Im Gegensatz dazu implementiert die [cookie-session](https://www.npmjs.com/package/cookie-session)-Middleware cookiegestützten Speicher: Sie serialisiert die gesamte Sitzung zum Cookie und nicht nur einen Sitzungsschlüssel. Diese Middleware sollten Sie nur verwenden, wenn Sitzungsdaten relativ klein sind und einfach als primitive Werte (und nicht als Objekte) codiert sind. Auch wenn Browser mindestens 4096 Byte pro Cookie unterstützen sollten, müssen Sie sicherstellen, dass dieses Limit nicht überschritten wird. Überschreiten Sie auf keinen Fall die Größe von 4093 Byte pro Domäne. Achten Sie zudem darauf, dass die Cookiedaten für den Client sichtbar sind. Wenn also ein Grund vorliegt, die Daten sicher oder unkenntlich zu machen, ist "express-session" möglicherweise die bessere Wahl.
-
-### Verwenden Sie nicht den standardmäßigen Namen des Sitzungscookies
-
-Die Verwendung des standardmäßigen Namens des Sitzungscookies kann Ihre Anwendung anfällig für Attacken machen. Das mögliche Sicherheitsproblem ist vergleichbar mit `X-Powered-By`: ein potenzieller Angreifer kann diesen Header verwenden, um einen elektronischen Fingerabdruck des Servers zu erstellen und Attacken entsprechend zu platzieren.
-
-Über [noSniff](https://github.com/helmetjs/dont-sniff-mimetype) werden `X-Content-Type-Options`-Header festgelegt, um bei Browsern MIME-Sniffing von Antworten weg vom deklarierten Inhaltstyp (declared content-type) vorzubeugen.
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Cookie-Sicherheitsoptionen festlegen
-
-Legen Sie die folgenden Cookieoptionen fest, um die Sicherheit zu erhöhen:
-
-- `secure` - Stellt sicher, dass der Browser das Cookie nur über HTTPS sendet.
-- `httpOnly` - Stellt sicher, dass das Cookie nur über HTTP(S) und nicht über das Client-JavaScript gesendet wird und dadurch Schutz gegen Cross-Site Scripting-Attacken besteht.
-- `domain` - Gibt die Domäne des Cookies an, die für den Vergleich mit der Domäne des Servers verwendet wird, in der die URL angefordert wird. Stimmen diese beiden überein, müssen Sie das Pfadattribut überprüfen.
-- `path` - Gibt den Pfad des Cookies an, der für den Vergleich mit dem Anforderungspfad verwendet wird. Wenn dieser Pfad und die Domäne übereinstimmen, können Sie das Cookie in der Anforderung senden.
-- `expires` - Wird verwendet, um das Ablaufdatum für persistente Cookies festzulegen.
-
-Dies ist ein Beispiel zur Verwendung der [cookie-session](https://www.npmjs.com/package/cookie-session)-Middleware:
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### Vermeiden Sie andere Schwachstellen
-
-Achten Sie auf [Node Security Project](https://npmjs.com/advisories)-Empfehlungen, die Express oder andere Module, die Ihre Anwendung nutzt, beeinträchtigen können. Im Allgemeinen ist Node Security Project aber eine exzellente Ressource mit Wissen und Tools zur Sicherheit von Node.
-
-Letztendlich können Express-Anwendungen – wie viele andere Webanwendungen auch – anfällig für eine Vielzahl webbasierter Attacken sein. Machen Sie sich deshalb mit bekannten [webspezifischen Schwachstellen](https://www.owasp.org/www-project-top-ten/) vertraut und treffen Sie die geeigneten Vorkehrungen, um diese zu vermeiden.
-
-## Weitere Überlegungen
-
-Dies sind einige weitere Empfehlungen aus der hervorragenden [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). In diesem Blogbeitrag finden Sie alle Details zu diesen Empfehlungen:
-
-- Filtern und bereinigen Sie immer Benutzereingaben, um sich gegen XS-Angriffe (Cross-Site Scripting) und Befehlsinjektionsattacken zu schützen.
-- Implementieren Sie Verteidungsmaßnahmen gegen SQL-Injection-Attacken, indem sie parametrisierte Abfragen oder vorbereitete Anweisungen einsetzen.
-- Nutzen Sie das Open-Source-Tool [sqlmap](http://sqlmap.org/), um SQL-Injection-Schwachstellen in Ihrer Anwendung zu erkennen.
-- Verwenden Sie die Tools [nmap](https://nmap.org/) und [sslyze](https://github.com/nabla-c0d3/sslyze), um die Konfiguration Ihrer SSL-Verschlüsselungen, -Schlüssel und Neuvereinbarungen sowie die Gültigkeit Ihres Zertifikats zu testen.
-- Verwenden Sie [safe-regex](https://www.npmjs.com/package/safe-regex), um sicherzustellen, dass Ihre regulären Ausdrücke nicht für [Denial-of-Service-Attacken](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) anfällig sind.
-
-[helmet]: <Wenn Sie `helmet.js` verwenden, kümmert sich das Tool darum.>
\ No newline at end of file
diff --git a/de/advanced/developing-template-engines.md b/de/advanced/developing-template-engines.md
deleted file mode 100644
index 82f5e3b8ed..0000000000
--- a/de/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Template-Engines für Express entwickeln
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Template-Engines für Express entwickeln
-
-Verwenden Sie die Methode `app.engine(ext, callback)`, um Ihre eigene Template-Engine zu erstellen. `ext` bezieht sich auf die Dateierweiterung, `callback` ist die Template-Engine-Funktion, die die folgenden Elemente als Parameter akzeptiert: die Position der Datei, das Optionsobjekt und die Callback-Funktion.
-
-Der folgende Code ist ein Beispiel für die Implementierung einer sehr einfachen Template-Engine für die Ausgabe von `.ntl`-Dateien.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Ihre Anwendung ist jetzt in der Lage, `.ntl`-Dateien auszugeben. Erstellen Sie im Verzeichnis `views` eine Datei namens `index.ntl` mit dem folgenden Inhalt.
-
-```pug
-#title#
-#message#
-```
-
-Erstellen Sie dann in Ihrer Anwendung die folgende Route.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Wenn Sie eine Anforderung zur Homepage einleiten, wird `index.ntl` im HTML-Format ausgegeben.
\ No newline at end of file
diff --git a/de/advanced/healthcheck-graceful-shutdown.md b/de/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 0f508986cc..0000000000
--- a/de/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### Beispiel
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/de/advanced/security-updates.md b/de/advanced/security-updates.md
deleted file mode 100644
index eb001048c0..0000000000
--- a/de/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Express-Sicherheitsupdates
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# Sicherheitsupdates
-
-<div class="doc-box doc-notice" markdown="1">
-Schwachstellen bei Node.js wirken sich direkt auf Express aus. Daher sollten Sie [ein Auge auf Schwachstellen bei Node.js haben](https://nodejs.org
-/en/blog/vulnerability/) und sicherstellen, dass Sie die aktuelle stabile Version von Node.js haben.
-</div>
-
-Die folgende Liste enthält die Express-Schwachstellen, die im angegebenen Versionsupdate behoben wurden.
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
-- 4.10.7
-  - Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
-- 4.8.8
-  - Schwachstellen durch Directory-Traversal-Technik in `express.static` ([Empfehlung](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)) behoben.
-- 4.8.4
-  - Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
-- 4.8.0
-  - Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
-  - Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x WIRD NICHT MEHR GEWARTET**
-
-Bekannte und unbekannte Probleme bei Sicherheit und Leistung in 3.x wurden seit dem letzten Update (1. August 2015) noch nicht behoben. Es wird dringend empfohlen, die aktuelle Version von Express zu verwenden.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - Offenlegungsgefahr beim Rootpfad in `express.static`, `res.sendfile` und `res.sendFile` behoben.
-- 3.19.0
-  - Offene Umadressierungsschwachstelle in `express.static` ([Empfehlung](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)) behoben.
-- 3.16.10
-  - Schwachstellen durch Directory-Traversal-Technik in `express.static` behoben.
-- 3.16.6
-  - Node.js 0.10 kann in bestimmten Situationen Lecks bei `fd` aufweisen, die sich auf `express.static` und `res.sendfile` auswirken. Böswillige Anforderungen können zu Lecks bei `fd` führen und letztendlich `EMFILE`-Fehler nach sich ziehen und bewirken, dass Server nicht antworten.
-- 3.16.0
-  - Sparse-Arrays mit extrem hohen Indizes in der Abfragezeichenfolge können bewirken, dass für die Prozessausführung nicht genügend Arbeitsspeicher zur Verfügung steht und es zu einem Serverabsturz kommt.
-  - Extrem verschachtelte Abfragezeichenfolgenobjekte können bewirken, dass der Prozess blockiert und der Server dadurch vorübergehend nicht antwortet.
-- 3.3.0
-  - Die Antwort 404 bei einem nicht unterstützten Überschreibungsversuch war anfällig gegen Cross-Site Scripting-Attacken.
\ No newline at end of file
diff --git a/de/api.md b/de/api.md
deleted file mode 100644
index 815162cbec..0000000000
--- a/de/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API-Referenz
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/de/changelog/index.md b/de/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/de/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/de/guide/behind-proxies.md b/de/guide/behind-proxies.md
deleted file mode 100644
index 3bf62362de..0000000000
--- a/de/guide/behind-proxies.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-layout: page
-title: Express hinter Proxys
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# Express hinter Proxys
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-Bei der Ausführung einer Express-Anwendung hinter einem Proxy legen Sie die Anwendungsvariable `trust proxy` (mithilfe von [app.set()](/{{ page.lang }}/4x/api.html#app.set)) auf einen der in der folgenden Tabelle enthaltenen Werte fest:
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Typ</th><th>Wert</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Boolesch</td>
-<td markdown="1">Wenn `true` angegeben wird, wird die IP-Adresse des Clients als der äußerst rechte Eintrag im Header `X-Forwarded-*` interpretiert.
-
-Wenn `false` angegeben wird, wird die Anwendung als direkte Verbindung zum Internet gesehen. Die IP-Adresse des Clients wird dann von `req.connection.remoteAddress` abgeleitet. Dies ist die Standardeinstellung.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-Sie können IP-Adressen wie folgt festlegen:
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-Sobald die Werte angegeben wurden, werden die betreffenden IP-Adressen und Teilnetze aus dem Adressfeststellungsprozess ausgeschlossen. Die nicht vertrauenswürdige IP-Adresse, die am nächsten zum Anwendungsserver liegt, wird als IP-Adresse des Clients festgelegt. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>Zahl</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">Der Wert für [req.hostname](/{{ page.lang }}/api.html#req.hostname) wird vom Wert abgeleitet, der im Header `X-Forwarded-Host` festgelegt wurde. Dieser Wert kann vom Client oder Proxy festgelegt werden.</li>
-  <li markdown="1">`X-Forwarded-Proto` kann vom Reverse Proxy festgelegt werden, um der Anwendung mitzuteilen, ob es sich um `https` oder `http` oder sogar um einen ungültigen Namen handelt. Dieser Wert wird durch [req.protocol](/{{ page.lang }}/api.html#req.protocol) abgebildet.
-  </li>
-  <li markdown="1">Als Werte für [req.ip](/{{ page.lang }}/api.html#req.ip) und [req.ips](/{{ page.lang }}/api.html#req.ips) wird die Liste der Adressen aus `X-Forwarded-For` herangezogen.
-  </li>
-</ul>
-
-Die Einstellung für `trust proxy` wird mithilfe des [proxy-addr](https://www.npmjs.com/package/proxy-addr)-Pakets implementiert. Weitere Informationen finden Sie in der zugehörigen Dokumentation.
diff --git a/de/guide/database-integration.md b/de/guide/database-integration.md
deleted file mode 100644
index 0a39aab7ea..0000000000
--- a/de/guide/database-integration.md
+++ /dev/null
@@ -1,505 +0,0 @@
----
-layout: page
-title: Datenbankintegration in Express
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# Datenbankintegration
-
-Die Herstellung einer Verbindung zwischen Datenbanken und Express-Anwendungen erfolgt einfach durch Laden eines geeigneten Node.js-Treibers für die Datenbank in Ihre Anwendung. In diesem Dokument wird in Kurzform beschrieben, wie einige der gängigsten Node.js-Module für Datenbanksysteme Ihrer Express-Anwendung hinzugefügt und verwendet werden:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-Diese Datenbanktreiber sind neben zahlreichen anderen Treibern verfügbar. Weitere Optionen finden Sie auf der [npm](https://www.npmjs.com/)-Site.
-</div>
-
-## Cassandra
-
-**Modul**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Beispiel
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### Installation
-
-```bash
-$ npm install couchbase
-```
-
-### Beispiel
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Modul**: [nano](https://github.com/dscape/nano)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install nano
-```
-
-### Beispiel
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Modul**: [levelup](https://github.com/rvagg/node-levelup)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Beispiel
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Modul**: [mysql](https://github.com/felixge/node-mysql/)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install mysql
-```
-
-### Beispiel
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Modul**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-Wenn Sie nach einem Objektmodelltreiber für MongoDB suchen, schauen Sie unter [Mongoose](https://github.com/LearnBoost/mongoose) nach.
-
-## Neo4j
-
-**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
-
-### Installation
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Beispiel
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Modul**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### Installation
-
-Anmerkung: [Siehe Installations-Voraussetzungen](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Beispiel
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Modul**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install pg-promise
-```
-
-### Beispiel
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Modul**: [redis](https://github.com/mranney/node_redis)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install redis
-```
-
-### Beispiel
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### Installation
-
-```bash
-$ npm install tedious
-```
-
-### Beispiel
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Modul**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install sqlite3
-```
-
-### Beispiel
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**Modul**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install elasticsearch
-```
-
-### Beispiel
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/de/guide/debugging.md b/de/guide/debugging.md
deleted file mode 100644
index 570e26d6d7..0000000000
--- a/de/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: Debugging bei Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Debugging bei Express
-
-Wenn Sie alle in Express verwendeten internen Protokolle anzeigen wollen, legen Sie beim Starten Ihrer Anwendung die Umgebungsvariable `DEBUG` auf `express:*` fest.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-Verwenden Sie unter Windows den entsprechenden Befehl.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-Die Ausführung dieses Befehls für die durch [express generator](/{{ page.lang }}/starter/generator.html) generierte Standardanwendung resultiert in folgender Ausgabe:
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-Bei einer Anforderung an die Anwendung sind die Protokolle im Express-Code angegeben:
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-Wenn Sie nur die Protokolle von der Routerimplementierung sehen wollen, legen Sie den Wert für `DEBUG` auf `express:router` fest. Gleichermaßen gilt: Wenn Sie nur die Protokolle von der Anwendungsimplementierung sehen wollen, legen Sie den Wert für `DEBUG` auf `express:application` fest, usw.
-
-## Von `express` generierte Anwendungen
-
-An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
-
-Beispiel: Wenn Sie die Anwendung mit `$ express sample-app` generiert haben, können Sie die Debuganweisungen mit dem folgenden Befehl aktivieren:
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-Sie können mehrere Debug-Namespaces in einer durch Kommas getrennten Namensliste angeben:
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/de/guide/error-handling.md b/de/guide/error-handling.md
deleted file mode 100644
index 54c252ea71..0000000000
--- a/de/guide/error-handling.md
+++ /dev/null
@@ -1,284 +0,0 @@
----
-layout: page
-title: Fehlerbehandlung in Express
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# Fehlerbehandlung
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. Beispiel:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, nur, dass Fehlerbehandlungsfunktionen vier anstatt drei Argumente aufweisen:
-`(err, req, res, next)`.  Beispiel:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Middleware für die Fehlerbehandlung wird ganz zuletzt nach allen anderen `app.use()`- und Weiterleitungsaufrufen definiert.
-Beispiel:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-Wenn Sie Übergaben an die Funktion `next()` vornehmen (außer die Zeichenfolge `'route'`), sieht Express die aktuelle Anforderung als Fehler an und überspringt alle verbleibenden fehlerfreien Behandlungsroutinen und Middlewarefunktionen.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-Bei einem Routenhandler mit mehreren Callback-Funktionen können Sie den Parameter `route` verwenden, um den nächsten Routenhandler zu überspringen. Beispiel:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  Beispiel:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. Beispiel:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## Die Standardfehlerbehandlungsroutine (Default Error Handler)
-
-Express ist bereits mit einer integrierten Fehlerbehandlungsroutine ausgestattet, mit der alle in der Anwendung festgestellten Fehler gehandhabt werden können. Diese Middleware für die Fehlerbehandlung wird am Ende des Middleware-Funktionsstack hinzugefügt.
-
-Wenn Sie einen Fehler an `next()` übergeben und diesen nicht mit einem Error-Handler bearbeiten, wird dieser über den integrierten Error-Handler bearbeitet. Der Fehler wird mit dem Stack-Trace zum Client geschrieben. Der Stack-Trace ist in der Produktionsumgebung nicht verfügbar.
-
-<div class="doc-box doc-info" markdown="1">
-Legen Sie die Umgebungsvariable `NODE_ENV` auf `production` fest, um die Anwendung im Produktionsmodus auszuführen.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-Wenn `next()` mit einem Fehler aufgerufen wird, nachdem Sie mit dem Schreiben der Antwort begonnen haben (z. B., wenn Sie beim Streamen der Antwort zum Client einen Fehler feststellen), schließt die Standardfehlerbehandlungsroutine in Express die Verbindung, und die Anforderung schlägt fehl.
-
-Wenn Sie also einen angepassten Error-Handler hinzufügen, empfiehlt es sich, eine Delegierung zur Standardfehlerbehandlungsroutine in Express vorzunehmen, wenn die Header bereits an den Client gesendet wurden:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. Beispiel:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-You define error-handling middleware last, after other `app.use()` and routes calls; for example:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Antworten von der Middlewarefunktion können das von Ihnen gewünschte Format aufweisen wie beispielsweise eine Fehlerseite im HTML-Format, eine einfache Nachricht oder eine JSON-Zeichenfolge.
-
-Für organisatorische Zwecke (und Frameworks der höheren Ebene) können Sie mehrere Middlewarefunktionen für die Fehlerbehandlung definieren, wie Sie dies bei regulären Middlewarefunktionen auch tun würden. Wenn Sie beispielsweise eine Fehlerbehandlungsroutine (Error-Handler) für Anforderungen über `XHR` und andere Anforderungen definieren wollen, können Sie die folgenden Befehle verwenden:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-In diesem Beispiel kann die generische `logErrors`-Funktion Anforderungs- und Fehlerinformationen in `stderr` schreiben:
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-In diesem Beispiel wird `clientErrorHandler` wie folgt definiert. In diesem Fall wird der Fehler explizit an den nächsten Error-Handler übergeben:
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-Die `errorHandler`-Funktion "catch-all" kann wie folgt implementiert werden:
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. Beispiel:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-In diesem Beispiel wird der Handler `getPaidContent` übersprungen. Alle verbleibenden Handler in `app` für `/a_route_behind_paywall` werden jedoch weiter ausgeführt.
-
-<div class="doc-box doc-info" markdown="1">
-Aufrufe zu `next()` und `next(err)` geben an, dass der aktuelle Handler abgeschlossen ist und welchen Status er aufweist.  Durch `next(err)` werden alle verbleibenden Handler in der Kette übersprungen. Ausgenommen hiervor sind die Handler, die konfiguriert sind, um Fehler wie oben beschrieben zu behandeln.
-</div>
diff --git a/de/guide/migrating-4.md b/de/guide/migrating-4.md
deleted file mode 100644
index 2292800f1a..0000000000
--- a/de/guide/migrating-4.md
+++ /dev/null
@@ -1,555 +0,0 @@
----
-layout: page
-title: Migration auf Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Wechsel zu Express 4
-
-<h2 id="overview">Überblick</h2>
-
-Express 4 bietet grundlegende Veränderungen im Vergleich zu Express 3. Das bedeutet, dass eine Express 3-Anwendung nicht funktioniert, wenn Sie die Express-Version in ihren Abhängigkeiten aktualisieren.
-
-In diesem Beitrag werden folgende Themen behandelt:
-
-<ul class="doclist">
-  <li><a href="#changes">Änderungen in Express 4</a></li>
-  <li><a href="#example-migration">Beispiel</a> für die Migration einer Express 3-Anwendung auf Express 4</li>
-  <li><a href="#app-gen">Upgrade auf den Express 4 App Generator</a></li>
-</ul>
-
-<h2 id="changes">Änderungen in Express 4</h2>
-
-In Express 4 wurden einige signifikante Änderungen vorgenommen:
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Änderungen am Weiterleitungssystem (Routingsystem).</a></li>
-  <li><a href="#other-changes">Weitere Änderungen.</a></li>
-</ul>
-
-Siehe hierzu auch:
-
-- [Neue Features/Funktionen in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migration von 3.x auf 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Änderungen am Express-Core- und Middlewaresystem</h3>
-
-In Express 4 bestehen keine Abhängigkeiten mehr zu Connect. Alle integrierten Middlewarefunktionen werden aus dem Core entfernt. Ausgenommen hiervon ist die Funktion `express.static`. Das bedeutet, dass Express nun ein unabhängiges Routing- und Middleware-Web-Framework ist und Express-Versionierung und -Releases von Middleware-Updates nicht betroffen sind.
-
-Ohne integrierte Middleware müssen Sie explizit alle Middlewarefunktionen hinzufügen, die für die Ausführung Ihrer Anwendung erforderlich sind. Befolgen Sie einfach diese Schritte:
-
-1. Installieren des Moduls: `npm install --save <modulname>`
-2. Anfordern des Moduls in Ihrer Anwendung: `require('modulname')`
-3. Verwendung des Moduls gemäß Dokumentation: `app.use( ... )`
-
-In der folgenden Tabelle sind Express 3-Middlewarefunktionen und deren Entsprechungen in Express 4 aufgelistet.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Hier finden Sie die [komplette Liste](https://github.com/senchalabs/connect#middleware) der Express 4-Middleware.
-
-In den meisten Fällen können Sie einfach nur die Middleware der alten Version 3 durch deren Entsprechung in Express 4 ersetzen. Details hierzu finden Sie in der modulspezifischen Dokumentation in GitHub.
-
-<h4 id="app-use"><code>app.use</code> akzeptiert Parameter. </h4>
-
-In Version 4 können Sie über einen Variablenparameter den Pfad definieren, in den Middlewarefunktionen geladen werden. Dann können Sie den Wert des Parameters aus dem Routenhandler laden.
-Beispiel:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-Das Routingsystem
-</h3>
-
-Anwendungen laden nun implizit Routing-Middleware. Sie müssen sich also keine Gedanken mehr über die Reihenfolge machen, in der die Middleware in Bezug auf die `router`-Middleware geladen wird.
-
-Das Routingsystem verfügt jedoch über zwei neue Funktionen, die beim Organisieren Ihrer Weiterleitungen helfen:
-
-{: .doclist }
-
-- Die neue Methode `app.route()` zum Erstellen verkettbarer Routenhandler für einen Weiterleitungspfad
-- Die neue Klasse `express.Router` zum Erstellen modular einbindbarer Routenhandler
-
-<h4 id="app-route">Die Methode <code>app.route()</code></h4>
-
-Die neue Methode `app.route()` hilft beim Erstellen verkettbarer Routenhandler für einen Weiterleitungspfad. Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [`Router()`](/{{ page.lang }}/4x/api.html#router).
-
-Dies ist ein Beispiel für verkettete Routenhandler, die mit der Funktion `app.route()` definiert werden.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router">Die Klasse <code>express.Router</code></h4>
-
-Eine weitere Funktion, die beim Organisieren von Weiterleitungen hilft, ist die neue Klasse `express.Router`. Über diese Klasse können Sie modular einbindbare Routenhandler erstellen. Eine `Router`-Instanz ist ein vollständiges Middleware- und Routingsystem. Aus diesem Grund wird diese Instanz oft auch als "Mini-App" bezeichnet.
-
-Im folgenden Beispiel wird ein Router als Modul erstellt, Middleware in das Modul geladen, es werden Weiterleitungen definiert und das Modul letztendlich in einen Pfad in der Hauptanwendung eingebunden.
-
-Beispiel: Erstellen Sie eine Routerdatei namens `birds.js` mit dem folgenden Inhalt im Anwendungsverzeichnis:
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Laden Sie dann das Routermodul in die Anwendung:
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-Die Anwendung kann nun Anforderungen an die Pfade `/birds` und `/birds/about` bearbeiten und ruft die Middleware `timeLog` auf, die speziell für diese Weiterleitung bestimmt ist.
-
-<h3 id="other-changes">
-Weitere Änderungen </h3>
-
-In der folgenden Tabelle sind andere kleinere, aber trotzdem wichtige Änderungen in Express 4 aufgeführt:
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Objekt</th>
-<th>Beschreibung</th>
-</tr>
-<tr>
-<td>Node.js
-</td>
-<td>Express 4 erfordert Node.js 0.10.x oder höher und unterstützt nicht mehr Node.js 0.8.x.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-Das Modul `http` wird nicht mehr benötigt, es sei denn, Sie müssen direkt mit dem Modul arbeiten (socket.io/SPDY/HTTPS). Die Anwendung kann mithilfe der Funktion `app.listen()` gestartet werden.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-Die Funktion `app.configure()` wurde entfernt.  Verwenden Sie die Funktion `process.env.NODE_ENV` oder `app.get('env')`, um die Umgebung zu erkennen und die Anwendung entsprechend zu konfigurieren.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-Die Anwendungseigenschaft `json spaces` ist in Express 4 standardmäßig inaktiviert.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Verwenden Sie `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()` und `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-Löst keine relativen URLs mehr auf.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-War bisher ein Array, ist nun ein Objekt.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-War bisher eine Funktion, ist nun ein Objekt.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-Geändert in `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Nun verfügbar als `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Entfernt.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Entfernt.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Die Funktionalität ist nun auf die Einstellung des Basis-Cookiewerts begrenzt. Verwenden Sie `res.cookie()`, um weitere Funktionalität zu erhalten.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">Beispiel für eine Anwendungsmigration</h2>
-
-Dies ist ein Beispiel für die Migration einer Express 3-Anwendung auf Express 4.
-Die dabei interessanten Dateien sind `app.js` und `package.json`.
-
-<h3 id="">
-Anwendung der Version 3
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Es wird eine Express v.3-Anwendung mit der folgenden Datei `app.js` angenommen:
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-Die zugehörige `package.json`-Datei der Version 3 sieht in etwa wie folgt aus:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Prozess
-</h3>
-
-Beginnen Sie den Migrationsprozess mit der Installation der erforderlichen Middleware für die Express 4-Anwendung und der Aktualisierung von Express und Pug auf die aktuellen Versionen. Verwenden Sie hierzu den folgenden Befehl:
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Nehmen Sie an `app.js` die folgenden Änderungen vor:
-
-1. Die integrierten Express-Middlewarefunktionen `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` und
-   `express.errorHandler` sind im Objekt `express` nicht mehr verfügbar. Sie müssen deren Alternativen manuell installieren und in die Anwendung laden.
-
-2. Sie müssen die Funktion `app.router` nicht mehr laden.
-   Sie ist kein gültiges Express 4-Anwendungsobjekt. Entfernen Sie also den Code `app.use(app.router);`.
-
-3. Stellen Sie sicher, dass die Middlewarefunktionen in der richtigen Reihenfolge geladen werden – laden Sie `errorHandler` nach dem Laden der Anwendungsweiterleitungen.
-
-<h3 id="">Anwendung der Version 4 </h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-Durch Ausführung des Befehls `npm` wird `package.json` wie folgt aktualisiert:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Entfernen Sie dann ungültigen Code, laden Sie die erforderliche Middleware und nehmen Sie andere Änderungen nach Bedarf vor. Die Datei `app.js` sieht dann wie folgt aus:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">Wenn Sie nicht direkt mit dem Modul `http` arbeiten müssen (socket.io/SPDY/HTTPS), ist das Laden des Moduls nicht erforderlich. Die Anwendung kann dann einfach wie folgt gestartet werden:
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Anwendung ausführen</h3>
-
-Der Migrationsprozess ist abgeschlossen und die Anwendung ist nun eine Express 4-Anwendung. Zum Bestätigen starten Sie die Anwendung mit dem folgenden Befehl:
-
-```bash
-$ node .
-```
-
-Laden Sie [http://localhost:3000](http://localhost:3000) und sehen Sie, wie die Homepage von Express 4 wiedergegeben wird.
-
-<h2 id="app-gen">Upgrade auf den Express 4 App Generator</h2>
-
-Das Befehlszeilentool zum Generieren einer Express-Anwendung ist nach wie vor `express`. Für ein Upgrade auf die neue Version müssen Sie jedoch den Express 3 App Generator deinstallieren und dann den neuen Generator `express-generator` installieren.
-
-<h3 id="">Installation</h3>
-
-Wenn der Express 3 App Generator bereits auf Ihrem System installiert ist, müssen Sie diesen deinstallieren:
-
-```bash
-$ npm uninstall -g express
-```
-
-Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
-
-Installieren Sie nun den neuen Generator:
-
-```bash
-$ npm install -g express-generator
-```
-
-Abhängig davon, wie Ihre Datei- und Verzeichnissberechtigungen konfiguriert sind, müssen Sie diesen Befehl möglicherweise mit `sudo` ausführen.
-
-Nun wird der Befehl `express` auf Ihrem System auf den Express 4 App Generator aktualisiert.
-
-<h3 id="">Änderungen am App Generator </h3>
-
-Befehlsoptionen und -nutzung bleiben größtenteils unverändert. Es gelten jedoch folgende Ausnahmen:
-
-{: .doclist }
-
-- Option `--sessions` wurde entfernt.
-- Option `--jshtml` wurde entfernt.
-- Option `--hogan` wurde hinzugefügt, um [Hogan.js](http://twitter.github.io/hogan.js/) zu unterstützen.
-
-<h3 id="">Beispiel</h3>
-
-Führen Sie den folgenden Befehl aus, um eine Express 4-Anwendung zu erstellen:
-
-```bash
-$ express app4
-```
-
-Wenn Sie sich den Inhalt der Datei `app4/app.js` ansehen, werden Sie feststellen, dass alle Middlewarefunktionen (außer `express.static`), die für die Anwendung  erforderlich sind, als unabhängige Module geladen werden und die Middleware `router` nicht mehr explizit in die Anwendung geladen wird.
-
-Sie werden auch feststellen, dass die Datei `app.js` nun ein Node.js-Modul ist – im Gegensatz zur eigenständigen Anwendung, die vom bisherigen Generator generiert wurde.
-
-Starten Sie nach der Installation der Abhängigkeiten die Anwendung mit dem folgenden Befehl:
-
-```bash
-$ npm start
-```
-
-Wenn Sie sich das npm-Startscript in der Datei `package.json` näher ansehen, werden Sie feststellen, dass der eigentliche Befehl, der die Anwendung startet, `node ./bin/www` heißt. Dieser Befehl lautete in Express 3 `node app.js`.
-
-Da die Datei `app.js`, die vom Express 4 Generator erstellt wurde, nun ein Node.js-Modul ist, kann dieses nicht mehr wie bisher unabhängig als Anwendung gestartet werden (es sei denn, Sie ändern den Code). Das Modul muss in eine Node.js-Datei geladen und über die Node.js-Datei gestartet werden. Die Node.js-Datei ist in diesem Fall `./bin/www`.
-
-Weder das Verzeichnis `bin` noch die erweiterungslose Datei `www` ist für das Erstellen einer Express-Anwendung oder das Starten der Anwendung zwingend erforderlich. Dies sind lediglich Vorschläge des Generators. Sie können diese also je nach Ihren Anforderungen ändern.
-
-Um das Verzeichnis `www` zu löschen und alles im "Express 3-Stil" zu belassen, löschen Sie die Zeile mit dem Eintrag `module.exports = app;` am Ende der Datei `app.js`. Fügen Sie dann stattdessen den folgenden Code an derselben Position ein:
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Stellen Sie sicher, dass Sie das Modul `debug` am Anfang der Datei `app.js` laden. Verwenden Sie dazu den folgenden Code:
-
-```js
-var debug = require('debug')('app4')
-```
-
-Ändern Sie als Nächstes `"start": "node ./bin/www"` in der Datei `package.json` in `"start": "node app.js"`.
-
-Sie haben nun die Funktionalität von `./bin/www` wieder in `app.js` verschoben. Diese Änderung wird nicht empfohlen. Die Übung hat Ihnen jedoch geholfen, zu verstehen, wie die Datei `./bin/www` funktioniert und warum die Datei `app.js` nicht mehr automatisch gestartet wird.
diff --git a/de/guide/migrating-5.md b/de/guide/migrating-5.md
deleted file mode 100644
index 35dd65e8b7..0000000000
--- a/de/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: Migration auf Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Wechsel zu Express 5
-
-<h2 id="overview">Überblick</h2>
-
-Express 5.0 befindet sich noch in der Beta-Release-Phase. Hier finden Sie jedoch bereits eine Vorschau zu den Änderungen in diesem Release und zur Migration Ihrer Express 4-Anwendung auf Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-Sie können Ihre automatisierten Tests ausführen, um zu sehen, was fehlschlägt, und Probleme gemäß den folgenden Updates beheben. Nachdem Sie alle Testfehler behoben haben, führen Sie Ihre Anwendung aus, um zu sehen, welche Fehler noch auftreten. Sie werden sofort feststellen, ob die Anwendung Methoden oder Eigenschaften verwendet, die nicht unterstützt werden.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Änderungen in Express 5</h2>
-
-**Entfernte Methoden und Eigenschaften**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Pluralisierte Methodennamen</a></li>
-  <li><a href="#leading">Führender Doppelpunkt im Namensargument für app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Verbesserungen**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**Geändert**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Entfernte Methoden und Eigenschaften
-
-Wenn Sie eine dieser Methoden oder Eigenschaften in Ihrer Anwendung verwenden, stürzt die Anwendung ab. Sie müssen also Ihre Anwendung ändern, wenn Sie auf Version 5 umgestellt haben.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 unterstützt die Funktion `app.del()` nicht mehr. Wenn Sie diese Funktion verwenden, wird ein Fehler ausgelöst. Für die Registrierung von HTTP DELETE-Weiterleitungen verwenden Sie stattdessen die Funktion `app.delete()`.
-
-Anfänglich wurde `del` statt `delete` verwendet, weil `delete` in JavaScript ein reserviertes Schlüsselwort ist. Ab ECMAScript 6 jedoch können `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-Die Signatur `app.param(fn)` wurde für die Änderung der Verhaltensweise der Funktion `app.param(name, fn)` verwendet. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt.
-
-<h3 id="plural">Pluralisierte Methodennamen</h3>
-
-Die folgenden Methodennamen wurden pluralisiert. In Express 4 wurde bei Verwendung der alten Methoden eine Warnung zur Einstellung der Unterstützung ausgegeben. Express 5 unterstützt diese Methoden nicht mehr.
-
-`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt.
-
-`req.acceptsCharset()` wird durch `req.acceptsCharsets()` ersetzt.
-
-`req.acceptsEncoding()` wird durch `req.acceptsEncodings()` ersetzt.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Führender Doppelpunkt (:) im Namen für app.param(name, fn)</h3>
-
-Ein führendes Doppelpunktzeichen (:) im Namen für die Funktion `app.param(name, fn)` ist ein Überbleibsel aus Express 3. Aus Gründen der Abwärtskompatibilität wurde dieser Name in Express 4 mit einem Hinweis zu veralteten Versionen weiter unterstützt. In Express 5 wird dieser Name stillschwiegend ignoriert und der Namensparameter ohne einen vorangestellten Doppelpunkt verwendet.
-
-Dies dürfte keine Auswirkungen auf Ihren Code haben, wenn Sie die Express 4-Dokumentation zu [app.param](/{{ page.lang }}/4x/api.html#app.param) befolgen, da dort der führende Doppelpunkt nicht erwähnt wird.
-
-<h3 id="req.param">req.param(name)</h3>
-
-Dieses potenziell verwirrende und durchaus riskante Verfahren des Abrufens von Formulardaten wurde entfernt. Sie müssen nun ganz speziell nach dem übergebenen Parameternamen im Objekt `req.params`, `req.body` oder `req.query` suchen.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 unterstützt die Signatur `res.json(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.json()`-Methoden wie  dieser verketten: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 unterstützt die Signatur `res.jsonp(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.jsonp()`-Methoden wie  dieser verketten: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 unterstützt die Signatur `res.send(obj, status)` nicht mehr. Stattdessen müssen Sie den Status festlegen und diesen dann mit `res.send()`-Methoden wie  dieser verketten: `res.status(status).send(obj)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 unterstützt die Signatur <code>res.send(<em>status</em>)</code>, nicht mehr, wobei _`status`_ für eine Zahl steht. Verwenden Sie stattdessen die Funktion `res.sendStatus(statusCode)`, mit der der Statuscode für den HTTP-Antwort-Header festgelegt und die Textversion des Codes gesendet wird: "Not Found" (Nicht gefunden), "Internal Server Error" (Interner Serverfehler) usw.
-Wenn Sie eine Zahl senden und hierfür die Funktion `res.send()` verwenden müssen, müssen Sie die Zahl in Anführungszeichen setzen, um diese in eine Zeichenfolge zu konvertieren. Dadurch interpretiert Express diese Zahl nicht als Versuch, die nicht mehr unterstützte alte Signatur zu verwenden.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-Die Funktion `res.sendfile()` wurde durch eine Version in Camel-Schreibweise von `res.sendFile()` in Express 5 ersetzt.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Seit v4.11.0 wurde sie nicht mehr verwendet. In Express 5 wird sie überhaupt nicht mehr unterstützt.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Geändert
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. Beispiel:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-Beispiel:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-Das Objekt `app.router`, das in Express 4 entfernt wurde, ist in Express 5 wieder verfügbar. In der neuen Version fungiert dieses Objekt nur als Referenz zum Express-Basisrouter – im Gegensatz zu Express 3, wo die Anwendung dieses Objekt explizit laden musste.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-In Express 4 übergab die Funktion `req.host` nicht ordnungsgemäß eine eventuell vorhandene Portnummer. In Express 5 wird die Portnummer beibehalten.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Verbesserungen
-
-<h3 id="res.render">res.render()</h3>
-
-Diese Methode erzwingt nun asynchrones Verhalten für alle View-Engines, sodass durch View-Engines mit synchroner Implementierung verursachte Fehler vermieden werden, durch die die empfohlene Schnittstelle nicht verwendet werden konnte.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/de/guide/overriding-express-api.md b/de/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/de/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/de/guide/routing.md b/de/guide/routing.md
deleted file mode 100644
index 8d76504d18..0000000000
--- a/de/guide/routing.md
+++ /dev/null
@@ -1,411 +0,0 @@
----
-layout: page
-title: Weiterleitung in Express
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# Weiterleitung (Routing)
-
-Der Begriff _Weiterleitung_ (Routing) bezieht sich auf die Definition von Anwendungsendpunkten (URIs) und deren Antworten auf Clientanforderungen.
-Eine Einführung in dieses Routing siehe [Basisrouting](/{{ page.lang }}/starter/basic-routing.html).
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-Der folgende Code ist ein Beispiel für ein sehr einfaches Basisrouting.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Weiterleitungsmethoden</h2>
-
-Eine Weiterleitungsmethode wird von einer HTTP-Methode abgeleitet und an eine Instanz der Klasse `express` angehängt.
-
-Der folgende Code ist ein Beispiel für Weiterleitungen, die für die Methoden GET und POST zum Stamm (Root) der Anwendung definiert werden.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-Es gibt eine spezielle Weiterleitungsmethode, `app.all()`, die nicht von einer HTTP-Methode abgeleitet wird. Diese Methode wird zum Laden von Middlewarefunktionen bei einem Pfad für alle Anforderungsmethoden verwendet. Im folgenden Beispiel wird der Handler für Anforderungen zur Weiterleitung "/secret" ausgeführt, um herauszufinden, ob Sie GET-, POST-, PUT-, DELETE- oder andere HTTP-Anforderungsmethoden verwenden, die im [HTTP-Modul](https://nodejs.org/api/http.html#http_http_methods) unterstützt werden.
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Weiterleitungspfade</h2>
-
-Über Weiterleitungspfade werden in Kombination mit einer Anforderungsmethode die Endpunkte definiert, bei denen Anforderungen erfolgen können. Weiterleitungspfade können Zeichenfolgen, Zeichenfolgemuster oder reguläre Ausdrücke sein.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) ist ein handliches Tool zum Testen von Express-Basisweiterleitungen, auch wenn dieses Tool keine Musterabgleiche unterstützt.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Route paths based on strings
-
-Dieser Weiterleitungspfad gleicht Weiterleitungsanforderungen zum Stammverzeichnis (`/`) ab.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-Dieser Weiterleitungspfad gleicht Anforderungen mit `/about` ab.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-Dieser Weiterleitungspfad gleicht Anforderungen mit `/random.text` ab.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Route paths based on string patterns
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-Dieser Weiterleitungspfad gleicht `acd` und `abcd` ab.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgemustern.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-Dies sind einige Beispiele für Weiterleitungspfade auf Basis von Zeichenfolgen.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-Dieser Weiterleitungspfad gleicht `/abe` und `/abcde` ab.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Route paths based on regular expressions
-
-Dieser Weiterleitungspfad gleicht alle Weiterleitungsnamen ab, die den Buchstaben "a" enthalten.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-Dieser Weiterleitungspfad gleicht `butterfly` und `dragonfly`, jedoch nicht `butterflyman`, `dragonfly man` usw.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">Route parameters</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Routenhandler (Weiterleitungsroutinen)</h2>
-
-Sie können mehrere Callback-Funktionen angeben, die sich wie [Middleware](/{{ page.lang }}/guide/using-middleware.html) verhalten, um eine Anforderung zu verarbeiten. Die einzige Ausnahme hierbei ist, dass diese Callbacks möglicherweise `next('route')` aufrufen, um die verbleibenden Weiterleitungs-Callbacks zu umgehen. Mit diesem Verfahren können Sie Vorabbedingungen für eine Weiterleitung festlegen und dann die Steuerung an nachfolgende Weiterleitungen übergeben, wenn kein Grund vorliegt, mit der aktuellen Weiterleitung fortzufahren.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Routenhandler können eine Funktion und/oder ein Funktionsarray sein, wie in den folgenden Beispielen zu sehen ist.
-
-Eine einzelne Callback-Funktion kann eine Weiterleitung verarbeiten. Beispiel:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-Mehrere Callback-Funktionen können eine Weiterleitung verarbeiten (achten Sie darauf, dass Sie das Objekt `next` angeben). Beispiel:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-Ein Array von Callback-Funktionen kann eine Weiterleitung verarbeiten. Beispiel:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-Eine Kombination aus unabhängigen Funktionen und Funktionsarrays kann eine Weiterleitung verarbeiten. Beispiel:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Antwortmethoden</h2>
-
-Über die Methoden für das Antwortobjekt (`res`) in der folgenden Tabelle kann eine Antwort an den Client gesendet und der Anforderung/Antwort-Zyklus beendet werden. Wenn keine dieser Methoden über einen Routenhandler aufgerufen wird, bleibt die Clientanforderung im Status "blockiert".
-
-| Methode                                                                                                                                                                                                                   | Beschreibung                                                                                                    |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | Gibt eine Eingabeaufforderung zum Herunterladen einer Datei aus.                                |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | End the response process.                                                                       |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | Sendet eine JSON-Antwort.                                                                       |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | Sendet eine JSON-Antwort mit JSONP-Unterstützung.                                               |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | Leitet eine Anforderung um.                                                                     |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Render a view template.                                                                         |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | Sendet eine Antwort mit unterschiedlichen Typen.                                                |
-| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile)                          | Sendet eine Datei als Oktett-Stream.                                                            |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Legt den Antwortstatuscode fest und sendet dessen Zeichenfolgedarstellung als Antworthauptteil. |
-
-<h2 id="app-route">app.route()</h2>
-
-Sie können mithilfe von `app.route()` verkettbare Routenhandler für einen Weiterleitungspfad erstellen.
-Da der Pfad an einer einzelnen Position angegeben wird, ist das Erstellen modularer Weiterleitungen hilfreich, da Redundanzen und Schreibfehler reduziert werden. Weitere Informationen zu Weiterleitungen finden Sie in der Dokumentation zu [Router()](/{{ page.lang }}/4x/api.html#router).
-
-Dies ist ein Beispiel für verkettete Routenhandler, die mit der Funktion `app.route()` definiert werden.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Mit der Klasse `express.Router` lassen sich modular einbindbare Routenhandler erstellen. Eine `Router`-Instanz ist ein vollständiges Middleware- und Routingsystem. Aus diesem Grund wird diese Instanz oft auch als "Mini-App" bezeichnet.
-
-Im folgenden Beispiel wird ein Router als Modul erstellt, eine Middlewarefunktion in das Modul geladen, es werden Weiterleitungen definiert und das Modul letztendlich in einen Pfad in der Hauptanwendung eingebunden.
-
-Erstellen Sie eine Routerdatei namens `birds.js` mit dem folgenden Inhalt im Anwendungsverzeichnis:
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Laden Sie dann das Routermodul in die Anwendung:
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-Die Anwendung kann nun Anforderungen an die Pfade `/birds` und `/birds/about` bearbeiten und ruft die Middlewarefunktion `timeLog` auf, die speziell für diese Weiterleitung bestimmt ist.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/de/guide/using-middleware.md b/de/guide/using-middleware.md
deleted file mode 100644
index 4e67b123c3..0000000000
--- a/de/guide/using-middleware.md
+++ /dev/null
@@ -1,277 +0,0 @@
----
-layout: page
-title: Express-Middleware verwenden
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# Middleware verwenden
-
-Express ist ein Weiterleitungs- und Middleware-Web-Framework, das selbst nur minimale Funktionalität aufweist: Eine Express-Anwendung besteht im Wesentlichen aus einer Reihe von Middlewarefunktionsaufrufen.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
-
-Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
-
-- Ausführen von Code
-- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
-- End the request-response cycle.
-- Aufrufen der nächsten Middlewarefunktion im Stack
-
-Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über.
-
-Eine Express-Anwendung kann die folgenden Middlewaretypen verwenden:
-
-- [Middleware auf Anwendungsebene](#middleware.application)
-- [Middleware auf Routerebene](#middleware.router)
-- [Middleware für die Fehlerbehandlung](#middleware.error-handling)
-- [Integrierte Middleware](#middleware.built-in)
-- [Middleware anderer Anbieter](#middleware.third-party)
-
-Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mountpfad laden.
-Sie können auch eine Reihe von Middlewarefunktionen zusammen laden. Dadurch wird ein Sub-Stack des Middlewaresystems am Mountpunkt erstellt.
-
-<h2 id='middleware.application'>Middleware auf Anwendungsebene</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-Dieses Beispiel zeigt eine Middlewarefunktion ohne Mountpfad. Die Funktion wird immer dann ausgeführt, wenn die Anwendung eine Anforderung erhält.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-Dieses Beispiel zeigt eine Middlewarefunktion mit dem Mountpfad `/user/:id`. Die Funktion wird für jede Art von HTTP-Anforderung auf dem Pfad `/user/:id` ausgeführt.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Dieses Beispiel zeigt eine Weiterleitung und deren Handlerfunktion (Middlewaresystem). Die Funktion verarbeitet GET-Anforderungen zum Pfad `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Dies ist ein Beispiel zum Laden einer Reihe von Middlewarefunktionen an einem Mountpunkt mit einem Mountpfad.
-Das Beispiel veranschaulicht einen Middleware-Stack, über den Anforderungsinformationen  zu einer HTTP-Anforderung zum Pfad `/user/:id` ausgegeben werden.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Mit einem Routenhandler können Sie mehrere Weiterleitungen für einen Pfad definieren. Im folgenden Beispiel werden zwei Weiterleitungen für GET-Anforderungen zum Pfad `/user/:id` definiert. Die zweite Weiterleitung verursacht zwar keine Probleme, wird jedoch nie aufgerufen, da durch die erste Weiterleitung der Anforderung/Antwort-Zyklus beendet wird.
-
-Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-Wenn Sie den Rest der Middlewarefunktionen eines Weiterleitungs-Middleware-Stack überspringen wollen, rufen Sie `next('route')` auf, um die Steuerung an die nächste Weiterleitung zu übergeben.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-Dies ist ein Beispiel zur Verwendung der Middlewarefunktion `express.static` mit einem ausführlich dargestellten Optionsobjekt:
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Middleware auf Routerebene</h2>
-
-Middleware auf Routerebene funktioniert in der gleichen Weise wie Middleware auf Anwendungsebene, mit dem einzigen Unterschied, dass sie an eine Instanz von `express.Router()` gebunden ist.
-
-```js
-const router = express.Router()
-```
-
-Laden Sie Middleware auf Routerebene über die Funktionen `router.use()` und `router.METHOD()`.
-
-Der folgende Beispielcode repliziert das Middlewaresystem, das oben für die Middleware auf Anwendungsebene gezeigt wird, durch Verwendung von Middleware auf Routerebene.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-To skip the rest of the router's middleware functions, call `next('router')`
-to pass control back out of the router instance.
-
-Dieses Beispiel zeigt einen Middleware-Sub-Stack, über den GET-Anforderungen zum Pfad `/user/:id` verarbeitet werden.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Middleware für die Fehlerbehandlung</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Middleware für die Fehlerbehandlung benötigt immer *vier* Argumente. Sie müssen vier Argumente angeben, um die Erkennung als Middlewarefunktion für die Fehlerbehandlung zu ermöglichen. Selbst wenn das Objekt `next` nicht verwenden müssen, müssen Sie dies angeben, um die Signatur beizubehalten. Andernfalls wird das Objekt `next` als reguläre Middleware interpretiert, sodass keine Fehlerbehandlung möglich ist.
-</div>
-
-Middlewarefunktionen für die Fehlerbehandlung werden in derselben Weise definiert wie andere Middlewarefunktionen, außer dass Fehlerbehandlungsfunktionen speziell bei Signaturen vier anstatt drei Argumente aufweisen `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Details zu Middleware für die Fehlerbehandlung siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Integrierte Middleware</h2>
-
-Seit Version 4.x bestehen bei Express keine Abhängigkeiten zu [Connect](https://github.com/senchalabs/connect) mehr. Mit Ausnahme von `express.static` befinden sich nun alle Middlewarefunktionen, die bisher in Express enthalten waren, in separaten Modulen. Sehen Sie sich hierzu auch die [Liste der Middlewarefunktionen](https://github.com/senchalabs/connect#middleware) an.
-
-Die einzige integrierte Middlewarefunktion in Express ist `express.static`.
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Middleware anderer Anbieter</h2>
-
-Mit Middleware anderer Anbieter können Sie Express-Anwendungen um neue Funktionalität erweitern.
-
-Installieren Sie das Modul Node.js für die erforderliche Funktionalität. Laden Sie das Modul dann in Ihre Anwendung auf Anwendungsebene oder auf Routerebene.
-
-Das folgende Beispiel veranschaulicht das Installieren und Laden der Middlewarefunktion `cookie-parser` für das Cookie-Parsing.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Eine nicht vollständige Liste zu den Middlewarefunktionen anderer Anbieter, die im Allgemeinen mit Express verwendet werden, finden Sie unter [Middleware anderer Anbieter](../resources/middleware.html).
diff --git a/de/guide/using-template-engines.md b/de/guide/using-template-engines.md
deleted file mode 100644
index 7dd34574e1..0000000000
--- a/de/guide/using-template-engines.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-layout: page
-title: Template-Engines in Express verwenden
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Template-Engines in Express verwenden
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, das Verzeichnis, in dem sich die Vorlagendateien befinden. Beispiel: `app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, die zu verwendende Template-Engine. Beispiel: `app.set('view engine', 'pug')`
-
-Installieren Sie dann das entsprechende npm-Paket für die Template-Engine:
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">Express-konforme Template-Engines wie Pug exportieren eine Funktion namens `__express(filePath, options, callback)`, die über die Funktion `res.render()` aufgerufen wird, um den Vorlagencode ausgeben zu können.
-
-Einige Template-Engines folgen dieser Konvention nicht. Die Bibliothek [Consolidate.js](https://www.npmjs.org/package/consolidate) folgt dieser Konvention, indem alle gängigen Node.js-Template-Engines zugeordnet werden. Daher ist eine reibungslose Funktion in Express gewährleistet.
-
-</div>
-
-Nach der Festlegung der View-Engine muss die Engine nicht angegeben oder das Template-Engine-Modul nicht in Ihre Anwendung geladen werden. Express lädt das Modul intern (wie unten für das obige Beispiel gezeigt).
-
-```js
-app.set('view engine', 'pug')
-```
-
-Erstellen Sie eine Pug-Vorlagendatei namens `index.pug` im Verzeichnis `views` mit dem folgenden Inhalt:
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Dann erstellen Sie eine Weiterleitung, um die Datei `index.pug` auszugeben. Wenn die Eigenschaft `view engine` nicht festgelegt wurde, müssen Sie die Erweiterung der Datei `view` angeben. Andernfalls müssen Sie diese Erweiterung nicht angeben.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Wenn Sie eine Anforderung zur Homepage ausführen, wird die Datei `index.pug` im HTML-Format ausgegeben.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/de/guide/writing-middleware.md b/de/guide/writing-middleware.md
deleted file mode 100644
index b6fd011d01..0000000000
--- a/de/guide/writing-middleware.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: Middleware für die Verwendung in Express-Anwendungen schreiben
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Middleware für die Verwendung in Express-Anwendungen schreiben
-
-<h2>Überblick</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
-
-Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
-
-- Ausführen von Code
-- Vornehmen von Änderungen an der Anforderung und an Antwortobjekten
-- End the request-response cycle.
-- Aufrufen der nächsten Middleware im Stack
-
-Wenn über die aktuelle Middlewarefunktion der Anforderung/Antwort-Zyklus nicht beendet werden kann, muss `next()` aufgerufen werden, um die Steuerung an die nächste Middlewarefunktion zu übergeben. Andernfalls geht die Anforderung in den Status "Blockiert" über.
-
-Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">HTTP-Methode, für die die Middlewarefunktion angewendet wird.</div></tbody>
-
-<div class="callout" id="callout2">Pfad (Weiterleitung), für den die Middlewarefunktion angewendet wird.</div>
-
-<div class="callout" id="callout3">Die Middlewarefunktion.</div>
-
-<div class="callout" id="callout4">Callback-Argument zur Middlewarefunktion, die nach der geltenden Konvention als "next" bezeichnet wird.</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Beispiel</h2>
-
-Here is an example of a simple "Hello World" Express application.
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Dies ist ein Beispiel einer einfachen Express-Anwendung namens "Hello World", für die Sie zwei Middlewarefunktionen definieren:</h3>
-Dies ist ein einfaches Beispiel einer Middlewarefunktion namens "myLogger". Diese Funktion gibt lediglich "LOGGED" aus, wenn eine Anforderung zur Anwendung über diese Funktion läuft. Die Middlewarefunktion ist der Variablen `myLogger` zugeordnet.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Beachten Sie den Aufruf oben zu `next()`. Durch den Aufruf dieser Funktion wird die nächste Middlewarefunktion in der Anwendung aufgerufen.
-Die Funktion `next()` ist nicht Teil der Node.js- oder Express-API, sondern das dritte Argument, das an die Middlewarefunktion übergeben wird. Die Funktion `next()` kann jeden beliebigen Namen haben, per Konvention erhält sie jedoch immer den Namen "next".
-Um Unklarheiten zu vermeiden, sollten Sie immer diese Konvention verwenden.
-</div>
-
-Zum Laden der Middlewarefunktion rufen Sie `app.use()` auf und geben die Middlewarefunktion an.
-Beispiel: Durch den folgenden Code wird die Middlewarefunktion `myLogger` vor der Weiterleitung zum Stammverzeichnispfad (/) geladen.
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Sobald die Anwendung eine Anforderung erhält, gibt sie die Nachricht "LOGGED" an das Terminal aus.
-
-Die Reihenfolge beim Laden der Middleware ist wichtig: Middlewarefunktionen, die zuerst geladen werden, werden auch zuerst ausgeführt.
-
-Wenn `myLogger` nach der Weiterleitung zum Stammverzeichnispfad geladen wird, erreicht die Weiterleitung die Middlewarefunktion nicht. Die Anwendung gibt "LOGGED" nicht aus, weil der Routenhandler für den Stammverzeichnispfad den Anforderung/Antwort-Zyklus beendet.
-
-Die Middlewarefunktion `myLogger` gibt einfach eine Nachricht aus und übergibt dann die Anforderung zur nächsten Middlewarefunktion im Stack durch Aufruf der Funktion `next()`.
-
-<h3>Middleware function requestTime</h3>
-
-Im nächsten Beispiel wird die Eigenschaft `requestTime` zum Anforderungsobjekt hinzugefügt. Diese Middlewarefunktion erhält den Namen "requestTime".
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-Die Anwendung verwendet nun die Middlewarefunktion `requestTime`. Außerdem verwendet die Callback-Funktion der Weiterleitung zum Stammverzeichnispfad die Eigenschaft, die die Middlewarefunktion zu `req` (dem Anforderungsobjekt) hinzufügt.
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-Wenn Sie eine Anforderung zum Stammverzeichnis der Anwendung einleiten, zeigt die Anwendung nun die Zeitmarke Ihrer Anforderung im Browser an.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Da Sie Zugriff auf das Anforderungsobjekt, das Antwortobjekt, die nächste Middlewarefunktion im Stack und die gesamte Node.js-API haben, sind die Möglichkeiten, die Sie mit Middlewarefunktionen haben, nahezu unendlich.
-
-Weitere Informationen zur Verwendung von Middleware in Express siehe [ Express-Middleware verwenden](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/de/index.md b/de/index.md
deleted file mode 100644
index 00be6c05be..0000000000
--- a/de/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js Web Application Framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express ist ein minimalistisches und flexibles Node.js Web Application Framework, das eine robustes Reihe an Funktionen für Web- und mobile Anwendungen bereitstellt.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/de/resources/community.md b/de/resources/community.md
deleted file mode 100644
index 1fc9cecffd..0000000000
--- a/de/resources/community.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-layout: page
-title: Express-Community
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# Community
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-Unsere lebhafte Community hat zu einer Vielzahl von Erweiterungen, [Middlewaremodulen](/{{ page.lang }}/resources/middleware.html) und Frameworks der höheren Ebene geführt.
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Probleme
-
-Wenn Sie Ihrer Meinung nach einen Fehler festgestellt haben oder lediglich ein Feature/eine Funktion anfordern wollen, können Sie in der [Issue Queue](https://github.com/expressjs/express/issues) ein Ticket öffnen.
-
-## Beispiele
-
-Zeigen Sie Dutzende von [Beispielen](https://github.com/expressjs/express/tree/master/examples) zu Express-Anwendungen im Repository an, das alles abdeckt – von API-Design und Authentifizierung bis zur Einbindung von Template-Engines.
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/de/resources/contributing.md b/de/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/de/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/de/resources/glossary.md b/de/resources/glossary.md
deleted file mode 100644
index bbbd9f6eca..0000000000
--- a/de/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express-Glossar
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# Glossar
-
-### Anwendung
-
-Im Allgemeinen besteht eine Anwendung aus einem oder mehreren Programmen, über die Operationen für bestimmte Zwecke ausgeführt werden.  Im Zusammenhang mit Express ist eine Anwendung ein Programm, das die auf der Node.js-Plattform laufende Express-API nutzt.  Wird auch als [Anwendungsobjekt](/{{ page.lang }}/api.html#express) bezeichnet.
-
-### API
-
-Anwendungsprogrammierschnittstelle (Application Programming Interface). Abkürzung bei der ersten Verwendung ausschreiben.
-
-### Express
-
-Schnelles, offenes, unkompliziertes Web-Framework für Node.js-Anwendungen. Im Allgemeinen wird der Name "Express" eher verwendet als "Express.js", auch wenn "Express.js" ebenfalls verwendet werden kann.
-
-### libuv
-
-Eine plattformübergreifende Unterstützungsbibliothek, bei der die asynchrone Ein-/Ausgabe im Mittelpunkt steht. Sie wurde in erster Linie für die Verwendung in Node.js entwickelt.
-
-### middleware
-
-Eine Funktion, die über die Weiterleitungsebene in Express vor dem letzten Anforderungshandler aufgerufen wird. Deshalb befindet sich diese Funktion in der Mitte zwischen einer unformatierten Anforderung und der endgültigen beabsichtigten Weiterleitung. Nachfolgend finden Sie einige Details zur Middlewareterminologie:
-
-- `var foo = require('middleware')` bedeutet, dass ein Node.js-Modul _benötigt_ oder _verwendet_ wird. Dann gibt die Anweisung `var mw = foo()` in der Regel die Middleware zurück.
-- `app.use(mw)` bedeutet, dass die _Middleware dem globalen Verarbeitungsstack hinzugefügt wird_.
-- `app.get('/foo', mw, function (req, res) { ... })` bedeutet, dass die _Middleware dem "GET /foo"-Verarbeitungsstack hinzugefügt wird_.
-
-### Node.js
-
-Eine Softwareplattform, die für die Erstellung skalierbarer Netzanwendungen verwendet wird. Node.js verwendet JavaScript als Scripting-Sprache und erzielt den hohen Durchsatz durch nicht blockierende Ein-/Ausgabe und eine Ereignisschleife mit einem Thread. Siehe auch [nodejs.org](http://nodejs.org/). **Hinweis**: Der ursprüngliche Name lautet "Node.js".
-
-### Open-Source
-
-Bei Verwendung als Adjektiv muss dieser Begriff mit Bindestrichen gekoppelt werden: Beispiel: "Dies ist eine Open-Source-Software." Siehe auch [Open-Source-Software in Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### Anforderung
-
-Eine HTTP-Antwort. Ein Server gibt eine HTTP-Antwortnachricht an den Client zurück.  Die Antwort enthält Informationen zum Beendigungsstatus in Bezug auf die Anforderung und kann im Nachrichtenhauptteil auch angeforderten Inhalt enthalten.
-
-### Antwort
-
-Eine HTTP-Anforderung. Ein Client übergibt eine HTTP-Anforderungsnachricht an einen Server, der wiederum eine Antwort zurückgibt. The response contains completion status information about the request and might also contain requested content in its message body.
-
-### Weiterleitung (Route)
-
-Teil einer URL, die eine Ressource angibt. Beispiel: In `http://foo.com/products/id` ist "/products/id" die Weiterleitung.
-
-### Router
-
-Siehe [Router](/{{ page.lang }}/4x/api.html#router) in der API-Referenz.
diff --git a/de/resources/middleware.md b/de/resources/middleware.md
deleted file mode 100644
index 3657f5b2ba..0000000000
--- a/de/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Express-Middleware
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Express-Middleware
-
-Nachfolgend sind einige Express-Middlewaremodule aufgeführt:
-
-| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung                                                                                                                        |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)                                                                                                                  | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)                                                                                                                  | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)                                                                                                                  | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)                                                                                                              | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)                                                                                                            | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                                                                                                                                | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)                                                                                                                | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html)                                                                                                          | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                                                                                                                            | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                                                                                                                            | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)                                                                                                              | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)                                                                                                              | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)                                                                                                                  | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)                                                                                                                | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                                                                                                                          | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                                                                                                                          | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                                                                                                                              | Create virtual domains.                                                                                             |
-
-## Informationen zu weiteren Middlewaremodulen siehe:
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| [express-slash](https://github.com/ericf/express-slash): Express-Middlewaremodul für Benutzer, die hohen Wert auf abschließende Schrägstriche legen. | Beschreibung                                                                                                                                                                                  |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet): Modul zur Sicherung Ihrer Anwendungen durch Festlegung verschiedener HTTP-Header.                      | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport): Express-Middlewaremodul für die Authentifizierung.                                              | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/de/resources/middleware/body-parser.md b/de/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/de/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/de/resources/middleware/compression.md b/de/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/de/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/de/resources/middleware/connect-rid.md b/de/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/de/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/de/resources/middleware/cookie-parser.md b/de/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/de/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/de/resources/middleware/cookie-session.md b/de/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/de/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/de/resources/middleware/cors.md b/de/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/de/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/de/resources/middleware/errorhandler.md b/de/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/de/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/de/resources/middleware/method-override.md b/de/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/de/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/de/resources/middleware/morgan.md b/de/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/de/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/de/resources/middleware/multer.md b/de/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/de/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/de/resources/middleware/response-time.md b/de/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/de/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/de/resources/middleware/serve-favicon.md b/de/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/de/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/de/resources/middleware/serve-index.md b/de/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/de/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/de/resources/middleware/serve-static.md b/de/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/de/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/de/resources/middleware/session.md b/de/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/de/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/de/resources/middleware/timeout.md b/de/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/de/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/de/resources/middleware/vhost.md b/de/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/de/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/de/resources/utils.md b/de/resources/utils.md
deleted file mode 100644
index f5ba489b99..0000000000
--- a/de/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | Beschreibung                                                                                                                                                                                                               |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/de/starter/basic-routing.md b/de/starter/basic-routing.md
deleted file mode 100644
index e264e27975..0000000000
--- a/de/starter/basic-routing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: Basisrouting in Express
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# Basisrouting
-
-Per _Routing_ wird bestimmt, wie eine Antwort auf eine Clientanforderung an einem bestimmten Endpunkt antwortet. Dies ist eine URI (oder ein Pfad) und eine bestimmte HTTP-Anforderungsmethode (GET, POST usw.).
-
-Jede Weiterleitung (Route) kann eine oder mehrere Handlerfunktionen haben, die ausgeführt werden, wenn die Weiterleitung abgeglichen wird.
-
-Weiterleitungsdefinitionen haben die folgende Struktur:
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Where:
-
-- `app` ist eine Instanz von `express`.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` ist ein Pfad auf dem Server.
-- `HANDLER` ist die Funktion, die ausgeführt wird, wenn die Weiterleitung abgeglichen wird.
-
-<div class="doc-box doc-notice" markdown="1">
-In diesem Lernprogramm wird vorausgesetzt, dass eine Instanz von `express` namens `app` erstellt und der Server ausgeführt wird. Wenn Sie mit dem Erstellen und Starten von Anwendungen nicht vertraut sind, spielen Sie das [Beispiel "Hello World"](/{{ page.lang }}/starter/hello-world.html) durch.
-</div>
-
-Die folgenden Beispiele veranschaulichen das Definieren einfacher Weiterleitungen.
-
-Antworten Sie mit `Hello World!` auf der Homepage:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Antworten Sie auf eine PUT-Anforderung zur Weiterleitung `/user`:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Antworten Sie auf eine DELETE-Anforderung zur Weiterleitung `/user`:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-Details zum Thema Routing finden Sie in der entsprechenden [Routinganleitung](/{{ page.lang }}/guide/routing.html).
-
diff --git a/de/starter/examples.md b/de/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/de/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/de/starter/faq.md b/de/starter/faq.md
deleted file mode 100644
index 3769257e13..0000000000
--- a/de/starter/faq.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-layout: page
-title: Häufig gestellte Fragen zu Express
-description: Finden Sie Antworten auf häufig gestellte Fragen zu Express.js, darunter Themen wie Anwendungsstruktur, Models, Authentifizierung, Template-Engines, Fehlerbehandlung und mehr.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# Häufig gestellte Fragen
-
-## Wie muss ich meine Anwendung strukturieren?
-
-Auf diese Frage gibt es keine verbindliche Antwort. Die Antwort hängt vom Umfang Ihrer Anwendung und dem eingebundenen Team ab. Um so flexibel wie möglich zu sein, gibt es bei Express keine Voraussetzungen hinsichtlich der Struktur.
-
-Weiterleitungen und andere anwendungsspezifische Logik können in einer beliebigen Anzahl von Dateien und in jeder von Ihnen bevorzugten Verzeichnisstruktur vorkommen. Die folgenden Beispiele sollen als Entscheidungshilfe dienen:
-
-- [Weiterleitungslisten](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Weiterleitungszuordnung](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [Controller im MVC-Stil](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Darüber hinaus gibt es Erweiterungen anderer Anbieter für Express, die zur Vereinfachung einiger dieser Muster beitragen:
-
-- [Weiterleitung mit "express-resource"](https://github.com/expressjs/express-resource)
-
-## Wie definiere ich Modelle?
-
-Express hat keine Vorstellungen von einer Datenbank. Dieses Konzept bleibt Node-Modulen anderer Anbieter überlassen, wodurch Schnittstellen zu allen Datenbank möglich sind.
-
-[LoopBack](http://loopback.io) zeigt ein Express-basiertes Framework, um das Modelle angeordnet sind.
-
-## Wie kann ich Benutzer authentifizieren?
-
-Die Authentifizierung ist ein weiterer meinungsstarker Bereich, in den Express nicht eingreift. Sie können ein Authentifizierungsschema nach Ihren Vorstellungen verwenden.
-Ein einfaches Benutzername/Kennwort-Schema können Sie in [diesem Beispiel](https://github.com/expressjs/express/tree/master/examples/auth) sehen.
-
-## Welche Template-Engines unterstützt Express?
-
-Express unterstützt jede Template-Engine, die der `(path, locals, callback)`-Signatur entspricht.
-Informationen zur Normalisierung von Template-Engine-Schnittstellen und -Caching siehe das Projekt [consolidate.js](https://github.com/visionmedia/consolidate.js). Nicht aufgelistete Template-Engines können trotzdem die Express-Signatur unterstützen.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## Wie handhabe ich 404-Antworten?
-
-In Express sind 404-Antworten nicht das Ergebnis eines Fehlers, sodass diese Antworten von der Fehlerbehandlungsroutine nicht erfasst werden. Dieses Verhalten ist damit zu erklären, dass eine 404-Antwort einfach angibt, dass keine weiteren Arbeiten auszuführen sind. In anderen Worten: Express hat alle Middlewarefunktionen und Weiterleitungen ausgeführt und festgestellt, dass keine Funktion eine Antwort zurückgegeben hat. Sie müssen also bei der Handhabung der 404-Antwort nur eine Middlewarefunktion am Ende des Stacks (unterhalb von allen anderen Funktionen) hinzufügen:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## Wie richte ich eine Fehlerbehandlungsroutine ein?
-
-Middleware für die Fehlerbehandlung wird in derselben Weise definiert wie andere Middleware; außer dass sie vier anstatt drei Argumente aufweist. Dies gilt speziell bei der Signatur `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Weitere Informationen siehe [Fehlerbehandlung](/{{ page.lang }}/guide/error-handling.html).
-
-## Wie gebe ich normales HTML-Format aus?
-
-Das ist nicht Ihre Aufgabe! Sie müssen kein HTML-Format mit der Funktion `res.render()` ausgeben.
-Verwenden Sie die Funktion `res.sendFile()`, wenn Sie es mit einer bestimmten Datei zu tun haben.
-Wenn Sie viele Assets aus einem Verzeichnis bedienen müssen, verwenden Sie die Middlewarefunktion `express.static()`.
-
-## Welche Version von Node.js benötigt Express?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/de/starter/generator.md b/de/starter/generator.md
deleted file mode 100644
index e0c0a551ac..0000000000
--- a/de/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Express-Anwendungsgenerator
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Express-Anwendungsgenerator
-
-Mit dem Application Generator Tool `express` können Sie innerhalb kürzester Zeit ein Anwendungsgerüst erstellen.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Zeigen Sie die Befehlsoptionen mit der Option `-h` an:
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-Im folgenden Beispiel wird eine Express-Anwendung mit dem Namen _myapp_ im aktuellen Arbeitsverzeichnis erstellt: The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-Installieren Sie dann Abhängigkeiten:
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-Verwenden Sie unter Windows diesen Befehl:
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-Führen Sie unter MacOS oder Linux die Anwendung mit diesem Befehl aus:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-Laden Sie dann `http://localhost:3000/` in Ihren Browser, um auf die Anwendung zuzugreifen.
-
-Die erstellte Anwendung hat die folgende Verzeichnisstruktur:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-Die vom Generator erstellte Anwendungsstruktur ist nur eine der vielen Möglichkeiten, Express-Anwendungen zu strukturieren. Sie können diese Struktur verwenden oder sie an Ihre Anforderungen anpassen.
-</div>
\ No newline at end of file
diff --git a/de/starter/hello-world.md b/de/starter/hello-world.md
deleted file mode 100644
index ea21ea36ff..0000000000
--- a/de/starter/hello-world.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-layout: page
-title: Beispiel "Hello World" in Express
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Beispiel "Hello World"
-
-<div class="doc-box doc-info" markdown="1">
-Dies ist wohl die einfachste Express-Anwendung, die Sie erstellen können. Es handelt sich um eine Anwendung mit nur einer Datei und &mdash; *nicht* das, was Sie mit dem [Express Generator](/{{ page.lang }}/starter/generator.html) erhalten würden. Mit dem Generator würde das Gerüst für eine vollständige Anwendung mit zahlreichen JavaScript-Dateien, Jade-Vorlagen und Unterverzeichnissen für verschiedene Zwecke erstellt werden.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-Die Anwendung startet einen Server und ist an Port 3000 empfangsbereit für Verbindungen. Die Anwendung antwortet mit "Hello World!" auf Anforderungen zur Stamm-URL (`/`) oder zu _route_. Bei jedem anderen Pfad lautet die Antwort **404 Not Found**.
-
-### Running Locally
-
-Erstellen Sie zunächst ein Verzeichnis namens `myapp`, wechseln Sie in das Verzeichnis und führen Sie `npm init` aus. Installieren Sie dann `express` als Abhängigkeit, wie im [Installationshandbuch](/{{ page.lang }}/starter/installing.html) beschrieben.
-
-Erstellen Sie im Verzeichnis `myapp` eine Datei namens `app.js` und fügen Sie den folgenden Code hinzu:
-
-<div class="doc-box doc-notice" markdown="1">`req` (Anforderung) und `res` (Antwort) sind genau dieselben Objekte, die Node bereitstellt. Sie können also `req.pipe()`, `req.on('data', callback)` und alle anderen Tasks, die Sie ausführen wollen, ohne Express ausführen.</div>
-
-Führen Sie die Anwendung mit dem folgenden Befehl aus:
-
-```bash
-$ node app.js
-```
-
-Laden Sie dann [http://localhost:3000/](http://localhost:3000/) in einen Browser, um die Ausgabe zu sehen.
\ No newline at end of file
diff --git a/de/starter/installing.md b/de/starter/installing.md
deleted file mode 100644
index 7e2b55fc4b..0000000000
--- a/de/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Express installieren
-description: Erfahren Sie, wie Sie Express.js in Ihrer Node.js-Umgebung installieren, wie Sie Ihr Projektverzeichnis aufsetzen und Abhängigkeiten mit npm verwalten.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# Installation
-
-Angenommen, Sie haben [Node.js](https://nodejs.org/) bereits installiert. Erstellen Sie ein Verzeichnis für Ihre Anwendung und definieren Sie dieses Verzeichnis als Ihr Arbeitsverzeichnis.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Erstellen Sie mit dem Befehl `npm init` eine Datei namens `package.json` für Ihre Anwendung.
-Weitere Informationen zur Funktionsweise von `package.json` finden Sie in den [Angaben zur Handhabung der npm-Datei package.json](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-Dieser Befehl fordert Sie zur Eingabe verschiedener Angaben wie Name und Version Ihrer Anwendung auf.
-For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-```
-entry point: (index.js)
-```
-
-Geben Sie `app.js` oder einen Namen Ihrer Vorstellung als Namen für die Hauptdatei ein. Wenn dieser Name `index.js` lauten soll, drücken Sie die Eingabetaste, um den vorgeschlagenen Standarddateinamen zu akzeptieren.
-
-Installieren Sie jetzt Express im Verzeichnis `myapp` und speichern Sie es in der Abhängigkeitsliste. Beispiel:
-
-```bash
-$ npm install express
-```
-
-Wenn Sie Express vorübergehend installieren und nicht zur Abhängigkeitsliste hinzufügen wollen, geben Sie die Option `--save` nicht an:
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-Node-Module, die mit der Option `--save` installiert werden, werden zur `Abhängigkeitsliste` in der Datei `package.json` hinzugefügt. Danach werden bei der Ausführung von `npm install` im Verzeichnis `app` automatisch alle Module in der Abhängigkeitsliste installiert.
-</div>
\ No newline at end of file
diff --git a/de/starter/static-files.md b/de/starter/static-files.md
deleted file mode 100644
index 79258d1360..0000000000
--- a/de/starter/static-files.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-layout: page
-title: Statische Dateien in Express bereitstellen
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Statische Dateien in Express bereitstellen
-
-Wenn Sie statische Dateien wie Bilder, CSS-Dateien und JavaScript-Dateien bereitstellen wollen, verwenden Sie die in Express integrierte Middlewarefunktion `express.static`.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-Beispiel: Verwenden Sie den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis namens `public` bereitzustellen:
-
-```js
-app.use(express.static('public'))
-```
-
-Jetzt können Sie die Dateien laden, die sich im Verzeichnis `public` befinden:
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">Express sucht nach den Dateien, die sich auf das Verzeichnis mit den statischen Assets beziehen. Der Name dieses Verzeichnisses ist also nicht Teil der URL.</div>
-
-Wenn Sie mehrere Verzeichnisse mit statischen Assets verwenden wollen, rufen Sie die Middlewarefunktion `express.static` mehrmals auf:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express sucht in der Reihenfolge nach den Dateien, in der sie die Verzeichnisse mit den statischen Assets über die Middlewarefunktion `express.static` festgelegt haben.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Jetzt können Sie die Dateien, die sich im Verzeichnis `public` befinden, aus dem Pfadpräfix `/static` laden.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-Der Pfad, den Sie für die Funktion `express.static` angeben, ist jedoch relativ zum Verzeichnis, aus dem Sie Ihren Prozess `node` starten. Wenn Sie die Express-Anwendung aus einem anderen Verzeichnis ausführen, ist es sicherer, den absoluten Pfad des Verzeichnisses zu verwenden, das Sie bereitstellen wollen:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/de/support/index.md b/de/support/index.md
deleted file mode 100644
index 3b0c7ad325..0000000000
--- a/de/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version-Support
-description: Finden Sie Informationen über den Support-Zeitplan für verschiedene Express.js Versionen, einschließlich der aktuellen Versionen und der End-of-Life-Richtlinien.
-menu: support
----
-
-# Version-Support
-
-Es wird nur die neueste Version einer bestimmten Hauptversionslinie unterstützt.
-
-Versionen, die EOL (End-of-Life) sind, _können_ Updates für kritische Sicherheitslücken erhalten, aber das Express-Team bietet keine Garantie und plant nicht, Fixes für gefundene Fehler zu entwickeln oder zu veröffentlichen.
-
-| Major Version                                                                                                                                              | Minimale Node.js Version | Support Startdatum | Support-Enddatum                                                 |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------ | ---------------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                       | September 2024     | **läuft derzeit**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0   | April 2014         | **läuft derzeit**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0    | Oktober 2012       | Juli 2015                                                        |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1    | März 2011          | Juli 2012                                                        |
-| **v1.x**{: .eol }                                                                                          | 0.2.0    | Dezember 2010      | März 2011                                                        |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98   | Dezember 2010      | Dezember 2010                                                    |
-
-## Kommerzielle Support Optionen
-
-Wenn Sie nicht auf eine unterstützte Version von Express aktualisieren können, wenden Sie sich bitte an einen unserer Partner, um Sicherheitsaktualisierungen zu erhalten:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/docs/configuration.md b/docs/configuration.md
new file mode 100644
index 0000000000..e3d5d0bda6
--- /dev/null
+++ b/docs/configuration.md
@@ -0,0 +1,182 @@
+# Configuration
+
+## Menu
+
+The navigation menus are configured in `src/config/menu/`. The type definitions are in `src/config/types.ts`.
+
+### Menu Structure
+
+Menus are composed of **sections** and **items**:
+
+```
+Menu
+├── sections[]           # Groups of menu items
+│   ├── title?           # Optional section header
+│   ├── basePath?        # Base path prepended to all item hrefs
+│   ├── omitFrom?        # Versions to exclude this section from
+│   └── items[]          # Menu items in this section
+└── items[]              # Alternative: flat list of items (no sections)
+```
+
+### Configuration Files
+
+| File            | Purpose                                     |
+| --------------- | ------------------------------------------- |
+| `main.ts`       | Top-level navigation (Docs, API, Resources) |
+| `docs.ts`       | Documentation sidebar menu                  |
+| `api.ts`        | API reference sidebar menu                  |
+| `resources.ts`  | Resources section menu                      |
+| `middleware.ts` | Middleware submenu                          |
+
+### Adding Menu Items
+
+Basic menu item with a link:
+
+```typescript
+{ href: `/guide/routing`, label: 'Routing', ariaLabel: 'Routing guide' }
+```
+
+Menu item with a submenu:
+
+```typescript
+{
+  label: 'Properties',
+  ariaLabel: 'Application properties',
+  submenu: {
+    items: [
+      { href: `/api/application/app-locals`, label: 'app.locals' },
+      { href: `/api/application/app-mountpath`, label: 'app.mountpath' },
+    ],
+  },
+}
+```
+
+### Adding Sections
+
+Sections group related menu items with an optional title:
+
+```typescript
+{
+  title: 'Getting started',
+  items: [
+    { href: `/starter/installing`, label: 'Installing' },
+    { href: `/starter/hello-world`, label: 'Hello world' },
+  ],
+}
+```
+
+### Version Specific Menus
+
+**Enabling versioning on a submenu** — Use `versioned` to specify which versions the menu supports. The version prefix will be automatically prepended to URLs:
+
+```typescript
+{
+  label: 'API Reference',
+  submenu: {
+    versioned: ['5x', '4x', '3x'],  // Supports all three versions
+    sections: apiMenu.sections,
+  },
+}
+```
+
+**Omitting items from specific versions** — Use `omitFrom` to hide an item in certain versions:
+
+```typescript
+{
+  href: `/api/application/app-mountpath`,
+  label: 'app.mountpath',
+  omitFrom: ['3x'],  // Not available in Express 3.x
+}
+```
+
+**Omitting entire sections from specific versions**:
+
+```typescript
+{
+  title: 'Router',
+  omitFrom: ['3x'],  // Router section doesn't exist in 3.x
+  items: [
+    { href: `/api/router/overview`, label: 'Overview' },
+  ],
+}
+```
+
+## Announcement Bar
+
+The announcement bar is a banner displayed at the top of the homepage. It supports two modes: **automatic** (latest blog post) and **custom** (manual configuration).
+
+The announcement bar is configured via `src/config/announcement.json`:
+
+```json
+{
+  "title": "",
+  "description": "",
+  "link": "",
+  "variant": "info",
+  "startDate": "",
+  "endDate": ""
+}
+```
+
+### Fields
+
+| Field         | Type     | Description                                                                                          |
+| ------------- | -------- | ---------------------------------------------------------------------------------------------------- |
+| `title`       | `string` | Banner title. If set, the custom announcement is used instead of the blog.                           |
+| `description` | `string` | Body text displayed below the title.                                                                 |
+| `link`        | `string` | Optional URL for a call-to-action link. The link text is managed via i18n (`announcement.readMore`). |
+| `variant`     | `string` | Visual style: `"info"` (blue) or `"warning"` (orange/red). Defaults to `"info"`.                     |
+| `startDate`   | `string` | ISO date (`YYYY-MM-DD`). Banner is hidden before this date. If empty, shows immediately.             |
+| `endDate`     | `string` | ISO date (`YYYY-MM-DD`). Banner is hidden after this date. If empty, shows indefinitely.             |
+
+### Custom Announcement
+
+When `title` has a value, the banner displays the custom announcement with the configured fields. This takes priority over the blog fallback.
+
+**Example — time-limited announcement:**
+
+```json
+{
+  "title": "Express@5.1.0: Now the Default on npm",
+  "description": "Express 5.1.0 is now the default on npm with an official LTS schedule.",
+  "link": "/en/blog/v5-1-latest-release",
+  "variant": "info",
+  "startDate": "2026-03-01",
+  "endDate": "2026-05-31"
+}
+```
+
+**Example — persistent warning:**
+
+```json
+{
+  "title": "Critical Security Update",
+  "description": "Please upgrade path-to-regexp to the latest version.",
+  "link": "/en/blog/2026-03-30-security-releases",
+  "variant": "warning",
+  "startDate": "",
+  "endDate": ""
+}
+```
+
+### Latest Blog (Default)
+
+When `title` is empty, the banner automatically displays the most recent blog post. In this mode:
+
+- The **title** and **description** are pulled from the blog post's frontmatter.
+- A **"Read more"** link points to the full blog post.
+- The banner is **visible for 1 month** after the blog's publication date (derived from the filename, e.g., `2026-03-30-security-releases.mdx` → starts `2026-03-30`, ends `2026-04-30`).
+- If the blog post has the `security` tag, the banner uses the `warning` variant. Otherwise, it uses `info`.
+
+To reset the announcement bar to this default behavior, clear the `title` field:
+
+```json
+{
+  "title": "",
+  "description": "",
+  "link": "",
+  "variant": "info",
+  "startDate": "",
+  "endDate": ""
+}
+```
diff --git a/docs/content.md b/docs/content.md
new file mode 100644
index 0000000000..9be6e6cb65
--- /dev/null
+++ b/docs/content.md
@@ -0,0 +1,210 @@
+# Content
+
+The site uses Astro's [Content Collections](https://docs.astro.build/en/guides/content-collections/) to manage documentation and resources. The configuration is defined in `src/content.config.ts`.
+
+## Collections
+
+| Collection | Location             | Description                                                    |
+| ---------- | -------------------- | -------------------------------------------------------------- |
+| `docs`     | `src/content/docs/`  | Versioned documentation pages (guides)                         |
+| `api`      | `src/content/api/`   | Versioned API reference documentation                          |
+| `pages`    | `src/content/pages/` | Global pages: non-versioned docs, resources, support, and more |
+| `blog`     | `src/content/blog/`  | Blog posts                                                     |
+
+> [!NOTE]
+> For a guide on writing and publishing blog posts, see [How to write a blog post](https://expressjs.com/en/blog/write-post).
+
+## Frontmatter Schema
+
+Each content file requires frontmatter with the following properties:
+
+```yaml
+---
+title: 'Page Title' # Required: The page title
+description: 'Description' # Optional: Page description for SEO
+---
+```
+
+## Using Components in Content (MDX)
+
+Content files that need to use interactive components must use the `.mdx` extension instead of `.md`. MDX allows you to import and use Astro components directly inside your markdown content.
+
+### Available Components
+
+| Component | Import                                                         | Description                                                 |
+| --------- | -------------------------------------------------------------- | ----------------------------------------------------------- |
+| `Alert`   | `import Alert from '@components/primitives/Alert/Alert.astro'` | Contextual alerts with `info`, `warning`, and `alert` types |
+
+### Example
+
+```mdx
+---
+title: My page title
+description: A page with alerts
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Regular markdown content here.
+
+<Alert type="info">This is an informational note.</Alert>
+
+<Alert type="warning">This is a warning message.</Alert>
+
+<Alert type="alert">This is a critical alert.</Alert>
+```
+
+> Component imports must be placed **after** the frontmatter block and **before** the content where they are used. Do not place imports inside the frontmatter (`---`) block.
+
+## API Reference
+
+The API reference lives in its own collection at `src/content/api/`, organized by version. Unlike `docs`, the API collection is not language-scoped — it is only available in English.
+
+### Structure
+
+```
+src/content/api/
+├── 3x/
+│   ├── api.mdx                    # API overview
+│   └── api/
+│       ├── application/           # express() and app methods
+│       ├── middleware/             # Built-in middleware
+│       ├── request/               # req object
+│       └── response/              # res object
+├── 4x/
+│   ├── api.mdx
+│   └── api/
+│       ├── application/
+│       ├── express/               # express module-level methods
+│       ├── middleware/
+│       ├── request/
+│       ├── response/
+│       └── router/                # Router (added in 4.x)
+└── 5x/
+    ├── api.mdx
+    └── api/
+        ├── application/
+        ├── middleware/
+        ├── request/
+        ├── response/
+        └── router/
+```
+
+### URL Patterns
+
+- Versioned: `/en/5x/api/application` → Express 5.x application API
+- Non-versioned: `/en/api/application` → Defaults to Express 5.x
+
+## Versioning
+
+The Express.js documentation supports multiple versions. Content is organized by version in both the `docs` and `api` collections.
+
+### Version Structure
+
+```
+src/content/docs/
+└── en/
+    ├── 3x/          # Express 3.x documentation
+    ├── 4x/          # Express 4.x documentation
+    └── 5x/          # Express 5.x documentation (default)
+```
+
+### How Versioning Works
+
+- **Default Version**: `5x` is the current default version
+- **Supported Versions**: `5x`, `4x`, `3x`
+- **URL Patterns**:
+  - Versioned: `/en/5x/api/` → Express 5.x API docs
+  - Non-versioned: `/en/api/` → Defaults to Express 5.x
+
+### Adding Version Specific Content
+
+1. Create your content file in the appropriate version directory:
+
+   ```
+   src/content/docs/en/5x/guide/my-new-page.md
+   ```
+
+2. The versioning system (configured in `src/pages/[lang]/[...slug].astro`) will automatically:
+   - Serve the page at `/en/5x/guide/my-new-page`
+   - Create non-versioned aliases for default version content
+
+### Adding a New Version
+
+To add support for a new Express version (e.g., `6x`):
+
+1. **Create content directories:**
+   - `src/content/docs/en/6x/` — Guides and documentation
+   - `src/content/api/6x/` — API reference
+
+2. **Update the version type** in `src/config/types.ts`:
+
+   ```typescript
+   export type VersionPrefix = '6x' | '5x' | '4x' | '3x';
+   ```
+
+3. **Update default version and prefixes** in `src/pages/[lang]/[...slug].astro`:
+
+   ```typescript
+   const DEFAULT_VERSION = '6x';
+   const VERSION_PREFIXES = ['6x', '5x', '4x', '3x'];
+   ```
+
+4. **Update the sidebar** in `src/components/patterns/Sidebar/Sidebar.astro`:
+   - Add the new version to the `versions` array
+   - Update `defaultVersion`
+
+5. **Update menu versioning** in `src/config/menu/main.ts`:
+   - Add `'6x'` to the `versioned` arrays
+
+6. **Review `omitFrom` entries** in `src/config/menu/api.ts`:
+   - Determine which API features exist or are deprecated in the new version
+
+### Global Pages (Non-Versioned)
+
+Some documentation pages are shared across all versions and don't belong to a specific Express version (e.g., security updates, migration guides, performance best practices). These pages live in the `pages` collection instead of `docs`.
+
+#### Structure
+
+```
+src/content/pages/
+└── en/
+    ├── advanced/
+    │   ├── best-practice-performance.md
+    │   ├── best-practice-security.mdx
+    │   ├── healthcheck-graceful-shutdown.md
+    │   └── security-updates.mdx
+    ├── guide/
+    │   ├── database-integration.mdx
+    │   ├── migrating-4.mdx
+    │   └── migrating-5.mdx
+    ├── resources/
+    │   ├── community.md
+    │   ├── contributing.md
+    │   ├── glossary.mdx
+    │   ├── utils.md
+    └── support.md
+```
+
+Pages with a slug starting with `resources/` are treated as resource pages and won't show "Docs" in the breadcrumbs.
+
+#### Adding a Global Page
+
+1. Create your content file in `src/content/pages/`:
+
+   ```
+   src/content/pages/en/guide/my-global-page.md
+   ```
+
+2. Add the menu item in `src/config/menu/docs.ts` with `global: true`:
+
+   ```typescript
+   {
+     href: `/guide/my-global-page`,
+     label: 'menu.myGlobalPage',
+     ariaLabel: 'menu.myGlobalPageAria',
+     global: true,
+   }
+   ```
+
+   The `global: true` flag tells the sidebar to generate the link without a version prefix and prevents the version switcher from modifying its URL.
diff --git a/docs/design-system.md b/docs/design-system.md
new file mode 100644
index 0000000000..ea6d7bde81
--- /dev/null
+++ b/docs/design-system.md
@@ -0,0 +1,93 @@
+# Design System
+
+Primitive components, tokens, and patterns used across the Express.js website.
+
+All components are imported from `@components/primitives`.
+
+## Typography
+
+**Fonts:** Helvetica Neue for body and headings, JetBrains Mono for code, Inter (bold) for OG images.
+
+**Headings:** `H1` (page titles), `H2` (sections), `H3` (subsections), `H4` (minor), `H5` (lead text).
+
+**Body:** `Body` (default), `BodyMd` (secondary content), `BodySm` (captions/metadata), `BodyXs` (fine print).
+
+**Code:** `Code` for inline code blocks.
+
+**Weights:** `light` (300), `normal` (400), `medium` (500), `semibold` (600), `bold` (700).
+
+All typography components support `as` prop for polymorphic rendering (e.g., `<H1 as="h2">`).
+
+## Iconography
+
+Uses `astro-icon` with [Fluent Icons](https://icon-sets.iconify.design/fluent/) (prefix `fluent:`).
+
+```astro
+import {Icon} from "astro-icon/components";
+<Icon name="fluent:airplane-24-regular" size="24" />
+```
+
+## Color Tokens
+
+**Primitives:** `--white`, `--black`, `--gray-{50-950}`, `--sky-{50,500,700,800}`, `--green-{50,300,500,700,900}`, `--amber-{50,300,500,600,700,900}`, `--red-{50,300,500,600,700,900}`.
+
+**Semantic (light / dark):**
+
+| Token                      | Light                 | Dark                  |
+| -------------------------- | --------------------- | --------------------- |
+| `--color-bg-primary`       | `--white` #FFFFFF     | `--black` #000000     |
+| `--color-bg-secondary`     | `--gray-50` #FAFAFA   | `--gray-900` #141414  |
+| `--color-bg-tertiary`      | `--gray-150` #EEEEEE  | `--gray-800` #262626  |
+| `--color-bg-inverse`       | `--gray-900` #141414  | `--gray-100` #F6F6F6  |
+| `--color-bg-mute`          | `--gray-200` #E5E5E5  | `--gray-600` #525252  |
+| `--color-bg-success`       | `--green-50` #F0FDF4  | `--green-950` #052E16 |
+| `--color-bg-warning`       | `--amber-50` #FFFBEB  | `--amber-950` #451A03 |
+| `--color-bg-error`         | `--red-50` #FEF2F2    | `--red-950` #450A0A   |
+| `--color-text-primary`     | `--gray-900` #141414  | `--gray-100` #F6F6F6  |
+| `--color-text-secondary`   | `--gray-600` #525252  | `--gray-150` #EEEEEE  |
+| `--color-text-tertiary`    | `--gray-500` #737373  | `--gray-500` #737373  |
+| `--color-text-inverse`     | `--gray-100` #F6F6F6  | `--gray-900` #141414  |
+| `--color-text-mute`        | `--gray-500` #737373  | `--gray-500` #737373  |
+| `--color-text-success`     | `--green-700` #15803D | `--green-400` #4ADE80 |
+| `--color-text-warning`     | `--amber-700` #B45309 | `--amber-400` #FBBF24 |
+| `--color-text-error`       | `--red-700` #B91C1C   | `--red-400` #F87171   |
+| `--color-border-primary`   | `--gray-300` #D4D4D4  | `--gray-500` #737373  |
+| `--color-border-secondary` | `--gray-200` #E5E5E5  | `--gray-800` #262626  |
+| `--color-border-tertiary`  | `--gray-400` #A3A3A3  | `--gray-400` #A3A3A3  |
+| `--color-border-inverse`   | `--gray-700` #404040  | `--gray-200` #E5E5E5  |
+| `--color-border-mute`      | `--gray-300` #D4D4D4  | `--gray-700` #404040  |
+| `--color-border-success`   | `--green-200` #BBF7D0 | `--green-800` #166534 |
+| `--color-border-warning`   | `--amber-200` #FDE68A | `--amber-800` #92400E |
+| `--color-border-error`     | `--red-200` #FECACA   | `--red-800` #991B1B   |
+
+Colors are defined using OKLCH color space with `light-dark()` for theme switching.
+
+## Spacing
+
+`--space-{0.5,1,2,3,4,6,8,12,16}` mapping to `2px` through `64px`.
+
+## Type Scale
+
+`--font-size-{xs,sm,base,lg,xl,2xl,3xl,4xl,5xl,6xl}` mapping to `12px` through `54px`.
+
+## Buttons
+
+`<Button>` supports `variant` (`primary`, `secondary`), `size` (`md`, `sm`, `xs`), `ghost` (transparent bg), `disabled`, and `as="a"` for links.
+
+## Form Elements
+
+`<Select>` — custom dropdown with WAI-ARIA support. Variants: `default`, `ghost`, `minimal`, `icon`. Sizes: `sm`, `md`, `lg`. Emits `select-change` event.
+
+## Grid & Layout
+
+- `<Grid>` + `<Col>` — 12-column responsive grid. Props: `xs`, `md`, `lg`, `gap`.
+- `<Flex>` + `<FlexItem>` — Flexbox layouts. Props: `direction`, `gap`, `justify`, `align`, `grow`, `basis`.
+- `<Container>` — Centered wrapper (`max-width: 1440px`).
+
+## Breakpoints
+
+| Name | Range          | Media query            |
+| ---- | -------------- | ---------------------- |
+| `xs` | < 768px        | `--xs-only`            |
+| `md` | 768px – 1439px | `--md-only`, `--md-up` |
+| `lg` | >= 1440px      | `--lg-up`, `--lg-down` |
diff --git a/docs/i18n.md b/docs/i18n.md
new file mode 100644
index 0000000000..a209321fcb
--- /dev/null
+++ b/docs/i18n.md
@@ -0,0 +1,142 @@
+# Internationalization (i18n)
+
+The expressjs.com website supports multiple languages through a combination of Astro routing, TypeScript utilities, and Crowdin integration.
+
+## Contributing Translations
+
+We use Crowdin to manage our translations in multiple languages and to enable automatic translation with artificial intelligence. Since AI translations can be imperfect, we welcome community contributions to improve translation accuracy and quality.
+
+### How to Translate
+
+1. Request to join the [Express.js Website project on Crowdin](https://express.crowdin.com/website)
+2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
+3. [Start translating in the Crowdin editor](https://support.crowdin.com/online-editor/)
+
+> Translation contributions must be made through Crowdin, not directly to the repository. Direct edits to translation files will be overwritten by Crowdin syncs.
+
+## Adding a New Language
+
+To add a new language to the website, follow this process:
+
+1. **Request language support** - Contact a website captain to request a new language in Crowdin. Only website maintainers can add new languages to the Crowdin project.
+
+2. **Crowdin will generate files** - Once approved in Crowdin, translation files will be automatically created:
+   - `src/i18n/ui/[lang-code].json` - UI strings
+   - Content files in `src/content/docs/[lang-code]/`
+
+3. **Update `src/i18n/locales.ts`** - Once files are created by Crowdin:
+   - Add the language to the `languages` object
+   - Import the new language's JSON file from `src/i18n/ui/`
+
+## Supported Languages
+
+- `en` - English
+- `de` - German (Deutsch)
+- `es` - Spanish (Español)
+- `fr` - French (Français)
+- `it` - Italian (Italiano)
+- `ja` - Japanese (日本語)
+- `ko` - Korean (한국어)
+- `pt-br` - Brazilian Portuguese (Português)
+- `zh-cn` - Chinese Simplified (简体中文)
+- `zh-tw` - Chinese Traditional (繁體中文)
+
+## How i18n Works
+
+### Architecture Overview
+
+The i18n system is built on these key components:
+
+1. **Locales Configuration** (`src/i18n/locales.ts`):
+   - Defines all supported languages and their metadata
+   - Imports UI translation strings from JSON files
+   - Exports types for type-safe translations
+
+2. **i18n Utilities** (`src/i18n/utils.ts`):
+   - `getLangFromUrl()` - Extracts the language code from the URL
+   - `useTranslations()` - Returns a translation function for the current language
+   - Helper functions for language path manipulation
+
+3. **Routing** (`src/pages/[lang]/[...slug].astro`):
+   - Dynamic routing with the `[lang]` parameter for language selection
+   - Supports URLs like `/en/api/`, `/fr/api/`, `/de/api/`, etc.
+
+4. **UI Translations** (`src/i18n/ui/`):
+   - JSON files for each supported language (e.g., `en.json`, `fr.json`)
+   - Contains UI strings like navigation labels, buttons, and UI elements
+   - Managed through Crowdin for easier translation
+
+## Using Translations in Components
+
+```astro
+---
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+<button aria-label={t('nav.toggleMenu')}>Menu</button>
+<h1>{t('common.welcome')}</h1>
+```
+
+The `Astro.url` object automatically provides the current page URL, making it easy to extract the language code and get the appropriate translations.
+
+## Content Organization
+
+### UI Translations
+
+UI strings are stored in JSON files in `src/i18n/ui/`. For example, `src/i18n/ui/en.json`:
+
+```json
+{
+  "common": {
+    "home": "Home",
+    "about": "About",
+    "contact": "Contact"
+  },
+  "navigation": {
+    "docs": "Documentation",
+    "api": "API Reference"
+  }
+}
+```
+
+### Content Translations
+
+Documentation content is stored separately from UI translations:
+
+- **Docs**: `src/content/docs/[lang-code]/[version]/` - Versioned documentation pages
+- **Pages**: `src/content/pages/[lang-code]/` - Global pages (non-versioned docs, resources, support)
+
+The following content is currently not translated:
+
+- **API reference**
+- **Blog posts**
+
+## Adding UI Translations
+
+When adding new UI strings:
+
+1. Add the string to `src/i18n/ui/en.json` first
+2. The structure will be synced to Crowdin
+3. Translators will translate it through Crowdin
+4. Updated translations will be synced back
+
+## Crowdin Integration
+
+The `crowdin.yml` configuration file defines:
+
+- Source files and their Crowdin translation targets
+- Directory structure for translations
+- API configuration for automation
+
+When translations are completed in Crowdin:
+
+- Files are automatically synced to the repository
+- A bot automatically creates pull requests with the translation updates
+
+> [!WARNING]
+> **Do not manually create or edit translation files** (`src/i18n/ui/*.json` and `src/content/docs/[lang-code]/*.*`)
+> These files are automatically managed by Crowdin and will be overwritten if you make manual changes.
+> All translation updates must go through the Crowdin workflow.
diff --git a/docs/project-structure.md b/docs/project-structure.md
new file mode 100644
index 0000000000..a4dd8cb55b
--- /dev/null
+++ b/docs/project-structure.md
@@ -0,0 +1,61 @@
+# Project Structure
+
+```
+├── src/
+│   ├── assets/              # Static assets (images, icons, etc.)
+│   ├── components/          # Reusable UI components
+│   │   ├── patterns/        # Complex UI patterns
+│   │   └── primitives/      # Base UI primitives
+│   ├── config/              # Configuration files
+│   │   ├── menu/            # Menu configuration files (sidebars)
+│   ├── content/             # Content collections
+│   │   ├── docs/            # Versioned documentation content
+│   │   └── pages/           # Global pages (non-versioned docs, resources, support)
+│   ├── i18n/                # Internationalization
+│   ├── icons/               # Icon components
+│   ├── layouts/             # Page layouts
+│   ├── pages/               # Route pages
+│   │   └── [lang]/          # Localized pages
+│   ├── plugins/             # Custom plugins
+│   ├── styles/              # Global styles
+│   │   ├── base/            # Base styles
+│   │   ├── tokens/          # Design tokens
+│   │   └── utilities/       # Utility classes
+│   └── utils/               # Utility functions
+├── public/                  # Static assets
+│   └── fonts/               # Font files
+├── docs/                    # Internal documentation for contributors
+├── astro.config.mjs         # Astro configuration
+```
+
+## Architecture Policy
+
+Although Astro supports integrations with frameworks such as React or Vue, this project intentionally avoids additional frontend frameworks.
+
+The expressjs.com website is designed to use:
+
+- HTML
+- CSS
+- TypeScript
+
+This decision helps keep the codebase lightweight, easier to maintain, and accessible to a broader range of contributors.
+
+### Do not introduce new frontend frameworks
+
+Please do not introduce React, Vue, or other client-side frameworks without prior discussion and approval.
+
+If a proposed feature appears to require a framework integration:
+
+1. Open an issue first.
+2. Explain the use case and why the existing stack (HTML, CSS, and TypeScript) is insufficient.
+3. Wait for approval from the maintainers before proceeding.
+
+Pull requests that introduce new framework dependencies without prior discussion may be closed.
+
+### Existing exception
+
+> The search component is implemented using React to support the Orama-powered search experience.
+> This is a limited, isolated integration and does not indicate that React (or other frameworks) should be used elsewhere in the project.
+
+> [!IMPORTANT]
+> Pull requests that introduce new framework dependencies without prior discussion may not be accepted.
diff --git a/en/3x/api.md b/en/3x/api.md
deleted file mode 100644
index b421e2afe6..0000000000
--- a/en/3x/api.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API Reference
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "/3x/api.html"
----
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
-
-  Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-  If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-  </div>
-
-  <h1>3.x API</h1>
-
-  {% include api/en/3x/express.md %}
-  {% include api/en/3x/app.md %}
-  {% include api/en/3x/req.md %}
-  {% include api/en/3x/res.md %}
-  {% include api/en/3x/middleware.md %}
-
-</div>
diff --git a/en/4x/api.md b/en/4x/api.md
deleted file mode 100644
index e2c12f01ef..0000000000
--- a/en/4x/api.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API Reference
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "/4x/api.html"
----
-<div id="api-doc" markdown="1">
-
-  <h1>4.x API</h1>
-
-  {% capture node-version %}
-
-  Express 4.0 requires Node.js 0.10 or higher.
-
-  {% endcapture %}
-  
-  {% include admonitions/note.html content=node-version %}
-  
-  <a id='express' class='h2'></a>
-  {% include api/en/4x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/4x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/4x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/4x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/4x/router.md %}
-</div>
diff --git a/en/5x/api.md b/en/5x/api.md
deleted file mode 100644
index 94d0a3c2d1..0000000000
--- a/en/5x/api.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API Reference
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "/5x/api.html"
----
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-  {% capture node-version %}
-
-  Express 5.0 requires Node.js 18 or higher.
-
-  {% endcapture %}
-
-  {% include admonitions/note.html content=node-version %}
-
-  <a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-
-</div>
diff --git a/en/advanced/best-practice-performance.md b/en/advanced/best-practice-performance.md
deleted file mode 100644
index 887775c4d2..0000000000
--- a/en/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
-layout: page
-title: Performance Best Practices Using Express in Production
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "/advanced/best-practice-performance.html"
----
-# Production best practices: performance and reliability
-
-This article discusses performance and reliability best practices for Express applications deployed to production.
-
-This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
-
-* Things to do in your code (the dev part):
-  * [Use gzip compression](#use-gzip-compression)
-  * [Don't use synchronous functions](#dont-use-synchronous-functions)
-  * [Do logging correctly](#do-logging-correctly)
-  * [Handle exceptions properly](#handle-exceptions-properly)
-* Things to do in your environment / setup (the ops part):
-  * [Set NODE_ENV to "production"](#set-node_env-to-production)
-  * [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
-  * [Run your app in a cluster](#run-your-app-in-a-cluster)
-  * [Cache request results](#cache-request-results)
-  * [Use a load balancer](#use-a-load-balancer)
-  * [Use a reverse proxy](#use-a-reverse-proxy)
-
-## Things to do in your code {#in-code}
-
-Here are some things you can do in your code to improve your application's performance:
-
-* [Use gzip compression](#use-gzip-compression)
-* [Don't use synchronous functions](#dont-use-synchronous-functions)
-* [Do logging correctly](#do-logging-correctly)
-* [Handle exceptions properly](#handle-exceptions-properly)
-
-### Use gzip compression
-
-Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. For details on enabling gzip compression in Nginx, see [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) in the Nginx documentation.
-
-### Don't use synchronous functions
-
-Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
-
-Although Node and many modules provide synchronous and asynchronous versions of their functions, always use the asynchronous version in production. The only time when a synchronous function can be justified is upon initial startup.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
-
-### Do logging correctly
-
-In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### For debugging
-
-If you're logging for purposes of debugging, then instead of using `console.log()`, use a special debugging module like [debug](https://www.npmjs.com/package/debug). This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
-
-#### For app activity
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Handle exceptions properly
-
-Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
-
-To ensure you handle all exceptions, use the following techniques:
-
-* [Use try-catch](#use-try-catch)
-* [Use promises](#use-promises)
-
-Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
-
-For more on the fundamentals of error handling, see:
-
-* [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Use try-catch
-
-Try-catch is a JavaScript language construct that you can use to catch exceptions in synchronous code. Use try-catch, for example, to handle JSON parsing errors as shown below.
-
-Here is an example of using try-catch to handle a potential process-crashing exception.
-This middleware function accepts a query field parameter named "params" that is a JSON object.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-However, try-catch works only for synchronous code. Because the Node platform is primarily asynchronous (particularly in a production environment), try-catch won't catch a lot of exceptions.
-
-#### Use promises
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### What not to do
-
-One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
-
-Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process.html#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-
-We also don't recommend using [domains](https://nodejs.org/api/domain.html). It generally doesn't solve the problem and is a deprecated module.
-
-## Things to do in your environment / setup {#in-environment}
-
-Here are some things you can do in your system environment to improve your app's performance:
-
-* [Set NODE_ENV to "production"](#set-node_env-to-production)
-* [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
-* [Run your app in a cluster](#run-your-app-in-a-cluster)
-* [Cache request results](#cache-request-results)
-* [Use a load balancer](#use-a-load-balancer)
-* [Use a reverse proxy](#use-a-reverse-proxy)
-
-### Set NODE_ENV to "production"
-
-The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-Setting NODE_ENV to "production" makes Express:
-
-* Cache view templates.
-* Cache CSS files generated from CSS extensions.
-* Generate less verbose error messages.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
-
-In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
-
-With systemd, use the `Environment` directive in your unit file. For example:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### Ensure your app automatically restarts
-
-In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
-
-* Using a process manager to restart the app (and Node) when it crashes.
-* Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
-
-Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
-
-#### Use a process manager
-
-In development, you started your app simply from the command line with `node server.js` or something similar. But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
-
-In addition to restarting your app when it crashes, a process manager can enable you to:
-
-* Gain insights into runtime performance and resource consumption.
-* Modify settings dynamically to improve performance.
-* Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### Use an init system
-
-The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-There are two ways to use init systems with your Express app:
-
-* Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
-* Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
-
-##### Systemd
-
-Systemd is a Linux system and service manager. Most major Linux distributions have adopted systemd as their default init system.
-
-A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-### Run your app in a cluster
-
-In a multi-core system, you can increase the performance of a Node app by many times by launching a cluster of processes. A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
-
-In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
-
-#### Using Node's cluster module
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### Cache request results
-
-Another strategy to improve the performance in production is to cache the result of requests, so that your app does not repeat the operation to serve the same request repeatedly.
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### Use a load balancer
-
-No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
-
-A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Use a reverse proxy
-
-A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
-
-Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/en/advanced/best-practice-security.md b/en/advanced/best-practice-security.md
deleted file mode 100644
index ae294403c0..0000000000
--- a/en/advanced/best-practice-security.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-layout: page
-title: Security Best Practices for Express in Production
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "/advanced/best-practice-security.html"
----
-
-# Production Best Practices: Security
-
-## Overview
-
-The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
-
-Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-Security best practices for Express applications in production include:
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [Use TLS](#use-tls)
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [Use Helmet](#use-helmet)
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - [Use cookies securely](#use-cookies-securely)
-    - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
-    - [Set cookie security options](#set-cookie-security-options)
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
-  - [Additional considerations](#additional-considerations)
-
-## Don't use deprecated or vulnerable versions of Express
-
-Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html) or consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/{{ page.lang }}/advanced/security-updates.html). If you are, update to one of the stable releases, preferably the latest.
-
-## Use TLS
-
-If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status. 
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks. 
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Use Helmet
-
-[Helmet][helmet] can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-Install Helmet like any other module:
-
-```bash
-$ npm install helmet
-```
-
-Then to use it in your code:
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself, 
-reducing the ability to fingerprint an application improves its overall security posture. 
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in 
-the HTTP response headers. 
-
-By default, Express sends the `X-Powered-By` response header that you can 
-disable using the `app.disable()` method:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Use cookies securely
-
-To ensure cookies don't open your app to exploits, don't use the default session cookie name and set cookie security options appropriately.
-
-There are two main middleware cookie session modules:
-
-* [express-session](https://www.npmjs.com/package/express-session) that replaces `express.session` middleware built-in to Express 3.x.
-* [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
-
-The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-
-In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
-
-### Don't use the default session cookie name
-
-Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
-
-To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Set cookie security options
-
-Set the following cookie options to enhance security:
-
-* `secure` - Ensures the browser only sends the cookie over HTTPS.
-* `httpOnly` - Ensures the cookie is sent only over HTTP(S), not client JavaScript, helping to protect against cross-site scripting attacks.
-* `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
-* `path` - indicates the path of the cookie; use it to compare against the request path. If this and domain match, then send the cookie in the request.
-* `expires` - use to set expiration date for persistent cookies.
-
-Here is an example using [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-1. The number of consecutive failed attempts by the same user name and IP address. 
-1. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### Avoid other known vulnerabilities
-
-Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
-
-Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
-
-## Additional considerations
-
-Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
-
-* Always filter and sanitize user input to protect against cross-site scripting (XSS) and command injection attacks.
-* Defend against SQL injection attacks by using parameterized queries or prepared statements.
-* Use the open-source [sqlmap](http://sqlmap.org/) tool to detect SQL injection vulnerabilities in your app.
-* Use the [nmap](https://nmap.org/) and [sslyze](https://github.com/nabla-c0d3/sslyze) tools to test the configuration of your SSL ciphers, keys, and renegotiation as well as the validity of your certificate.
-* Use [safe-regex](https://www.npmjs.com/package/safe-regex) to ensure your regular expressions are not susceptible to [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacks.
-
-[helmet]: https://helmetjs.github.io/
\ No newline at end of file
diff --git a/en/advanced/developing-template-engines.md b/en/advanced/developing-template-engines.md
deleted file mode 100755
index 9bbfb2fb2f..0000000000
--- a/en/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-layout: page
-title: Developing template engines for Express
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "/advanced/developing-template-engines.html"
----
-
-# Developing template engines for Express
-
-Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
-
-The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
-
-```pug
-#title#
-#message#
-```
-Then, create the following route in your app.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-When you make a request to the home page, `index.ntl` will be rendered as HTML.
\ No newline at end of file
diff --git a/en/advanced/healthcheck-graceful-shutdown.md b/en/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 84eb5d0766..0000000000
--- a/en/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "/advanced/healthcheck-graceful-shutdown.html"
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### Example 
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-* `liveness`, that determines when to restart a container.
-* `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/en/advanced/security-updates.md b/en/advanced/security-updates.md
deleted file mode 100755
index d6d20dd6e4..0000000000
--- a/en/advanced/security-updates.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-layout: page
-title: Express security updates
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "/advanced/security-updates.html"
----
-
-# Security updates
-
-<div class="doc-box doc-notice" markdown="1">
-Node.js vulnerabilities directly affect Express. Therefore, [keep a watch on Node.js vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest stable version of Node.js.
-</div>
-
-The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
-
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-  * 4.21.2
-    * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-  * 4.21.1
-    * The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-  * 4.20.0
-    * Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-    * The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-    * The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-    * The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-    * The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-  * 4.19.0, 4.19.1
-    * Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-  * 4.17.3
-    * The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-  * 4.16.0
-    * The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-    * The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-    * The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-  * 4.15.5
-    * The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-    * The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-  * 4.15.3
-    * The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-  * 4.15.2
-    * The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-  * 4.11.1
-    * Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
-  * 4.10.7
-    * Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-  * 4.8.8
-    * Fixed directory traversal vulnerabilities in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-  * 4.8.4
-    * Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-  * 4.8.0
-    * Sparse arrays that have extremely high indexes in the query string could cause the process to run out of memory and crash the server.
-    * Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
-
-  Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-  If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-  </div>
-
-  * 3.19.1
-    * Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
-  * 3.19.0
-    * Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-  * 3.16.10
-    * Fixed directory traversal vulnerabilities in `express.static`.
-  * 3.16.6
-    * Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-  * 3.16.0
-    * Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
-    * Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
-  * 3.3.0
-    * The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
\ No newline at end of file
diff --git a/en/api.md b/en/api.md
deleted file mode 100644
index 41382818cc..0000000000
--- a/en/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API Reference
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "/api.html"
----
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1>
-  <a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/en/blog/posts.md b/en/blog/posts.md
deleted file mode 100644
index b5be34e66c..0000000000
--- a/en/blog/posts.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-layout: post
-title: Express Blog Posts
-description: Explore the latest articles, announcements, and updates from the Express.js team and community on the Express blog.
-menu: blog
-redirect_from: "/blog/posts.html"
----
- 
-Want to write a post? See the submission [guidelines.](/en/blog/write-post.html)
-
-{% if site.posts.size !=  0 %}
-<div class="blog-posts">
-{% for post in site.posts %}
-  <div class="blog-post">
-      <div class="blog-title">
-        <a href="{{ post.url }}"> {{ post.title }}</a>
-      </div>
-      <div class="blog-details">
-        {% include blog/authors.html authors=post.authors %}
-        <div >{{ post.date | date:"%b %d, %Y" }}</div> 
-      </div>   
-      <div class="blog-excerpt"> {{post.excerpt | truncate: 240 | markdownify }} </div>
-  </div>
-{% endfor %}
-</div>
-{% else %}
-  There are currently no blog posts.
-{% endif %}
diff --git a/en/blog/write-post.md b/en/blog/write-post.md
deleted file mode 100644
index 21cfc5b4b3..0000000000
--- a/en/blog/write-post.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-layout: post
-title: How to write a blog post
-description: Learn how to propose and write a blog post for the Express.js blog, including submission guidelines and steps to contribute your content.
-menu: blog
-redirect_from: "/blog/write.html"
----
-
-![Blogger]({{site.url}}/images/blogger.jpg)
-
-If you have an idea for a blog post, follow these steps to propose it and potentially get it published!
-
-1. ### Propose your post
-Before taking the time to write a post, please confirm that we will be able to publish it. We're looking for topics specifically related to Express, and so we want to pre-approve all posts. For the moment, this means we aren't accepting any unsolicited posts. To propose a blog post, [open an issue](https://github.com/expressjs/expressjs.com/issues) entitled  `Blog post proposal: <your idea>`.
-
-
-1. ### Fork the repository 
-If the Express TC accepts your proposal, start to write your post by forking the [expressjs.com](https://github.com/expressjs/expressjs.com) repository and cloning it to your local machine. Once you open a pull request, you'll be able to preview your post on GitHub. See step six below.
-
-	Optional: To run the site locally and preview your post before opening a PR, see the [setup instructions in the README](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#expressjscom).
-	{: .doc-box .doc-info}
-
-1. ### Create a new file
-Create a new file in the `_posts` directory named using following the format: `YYYY-MM-DD-title.md`.
-
-1. ### Add the required front matter
-    Copy the following front matter, including the dotted lines, and paste it at the top of file you just created. Replace the placeholder values with as desired.
-
-    ```markdown
-    ---
-    title: <your-title>
-    sub_title: <your-optional-sub-title>
-    description: <description-of-your-post>
-    tags: <white-space-separated-topics>
-    authors:
-      - name: <your-name>
-        github: <github-username>
-    ---
-    ```
-
-    The `github` property of an author is optional. Including your username only (not your full profile URL) will ensure that your blog post links out to it.
-
-2. ### Add your content
-    Finally, start writing your content below the front matter.  Use standard markdown formatting.
-
-1. ### Open a pull request (PR)
-   Once you open a PR, you will be able to preview your results: There will be a section on the page entitled `Deploy Preview for expressjscom-preview ready!` Click the link to see the site rendered from your fork/branch.
-   
-   You can use this feature over multiple commits to refine your post by making a `draft` pull request. Once it's ready for review, switch it to a formal PR.
-
-   
\ No newline at end of file
diff --git a/en/changelog/index.md b/en/changelog/index.md
deleted file mode 100644
index 5ccf36e463..0000000000
--- a/en/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from: 
-  - "/changelog/4x.html"
-  - "en/changelog/4x.html"
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/en/guide/behind-proxies.md b/en/guide/behind-proxies.md
deleted file mode 100755
index 669e65d9c3..0000000000
--- a/en/guide/behind-proxies.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-layout: page
-title: Express behind proxies
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "/guide/behind-proxies.html"
----
-
-# Express behind proxies
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-The application setting `trust proxy` may be set to one of the values listed in the following table.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Type</th><th>Value</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Boolean</td>
-<td markdown="1">
-If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
-
-If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-* loopback - `127.0.0.1/8`, `::1/128`
-* linklocal - `169.254.0.0/16`, `fe80::/10`
-* uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-You can set IP addresses in any of the following ways:
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-</td>
-    </tr>
-    <tr>
-      <td>Number</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">The value of [req.hostname](/{{ page.lang }}/api.html#req.hostname) is derived from the value set in the `X-Forwarded-Host` header, which can be set by the client or by the proxy.
-  </li>
-  <li markdown="1">`X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or  `http` or even an invalid name. This value is reflected by [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">The [req.ip](/{{ page.lang }}/api.html#req.ip) and [req.ips](/{{ page.lang }}/api.html#req.ips) values are populated based on the socket address and `X-Forwarded-For` header, starting at the first untrusted address.
-  </li>
-</ul>
-
-The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/en/guide/database-integration.md b/en/guide/database-integration.md
deleted file mode 100644
index a2b63ac5b5..0000000000
--- a/en/guide/database-integration.md
+++ /dev/null
@@ -1,498 +0,0 @@
----
-layout: page
-title: Express database integration
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "/guide/database-integration.html"
----
-
-# Database integration
-
-Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
-
-* [Cassandra](#cassandra)
-* [Couchbase](#couchbase)
-* [CouchDB](#couchdb)
-* [LevelDB](#leveldb)
-* [MySQL](#mysql)
-* [MongoDB](#mongodb)
-* [Neo4j](#neo4j)
-* [Oracle](#oracle)
-* [PostgreSQL](#postgresql)
-* [Redis](#redis)
-* [SQL Server](#sql-server)
-* [SQLite](#sqlite)
-* [Elasticsearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-These database drivers are among many that are available. For other options,
-search on the [npm](https://www.npmjs.com/) site.
-</div>
-
-## Cassandra
-
-**Module**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-
-### Installation
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Example
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### Installation
-
-```bash
-$ npm install couchbase
-```
-
-### Example
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Module**: [nano](https://github.com/dscape/nano)
-
-### Installation
-
-```bash
-$ npm install nano
-```
-
-### Example
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Module**: [levelup](https://github.com/rvagg/node-levelup)
-
-### Installation
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Example
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Module**: [mysql](https://github.com/felixge/node-mysql/)
-
-### Installation
-
-```bash
-$ npm install mysql
-```
-
-### Example
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Module**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-
-### Installation
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-
-If you want an object model driver for MongoDB, look at [Mongoose](https://github.com/LearnBoost/mongoose).
-
-## Neo4j
-
-**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
-
-### Installation
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Example
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Module**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### Installation
-
- NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Example
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-
-### Installation
-
-```bash
-$ npm install pg-promise
-```
-
-### Example
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Module**: [redis](https://github.com/mranney/node_redis)
-
-### Installation
-
-```bash
-$ npm install redis
-```
-
-### Example
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### Installation
-
-```bash
-$ npm install tedious
-```
-
-### Example
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Module**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-
-### Installation
-
-```bash
-$ npm install sqlite3
-```
-
-### Example
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## Elasticsearch
-
-**Module**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-
-### Installation
-
-```bash
-$ npm install elasticsearch
-```
-
-### Example
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/en/guide/debugging.md b/en/guide/debugging.md
deleted file mode 100755
index e71cce273a..0000000000
--- a/en/guide/debugging.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-layout: page
-title: Debugging Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "/guide/debugging.html"
----
-
-# Debugging Express
-
-To see all the internal logs used in Express, set the `DEBUG` environment variable to
-`express:*` when launching your app.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-On Windows, use the corresponding command.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-Running this command on the default app generated by the [express generator](/{{ page.lang }}/starter/generator.html) prints the following output:
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &lt;anonymous&gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &lt;anonymous&gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &lt;anonymous&gt; +0ms
-  express:router:layer new / +0ms
-```
-
-When a request is then made to the app, you will see the logs specified in the Express code:
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
-
-## Applications generated by `express`
-
-An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
-
-For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-You can specify more than one debug namespace by assigning a comma-separated list of names:
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name      | Purpose                                         |
-|-----------|-------------------------------------------------|
-| `DEBUG`   | Enables/disables specific debugging namespaces. |
-| `DEBUG_COLORS`| Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH` | Object inspection depth. |
-| `DEBUG_FD`    | File descriptor to write debug output to. |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects. |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/en/guide/error-handling.md b/en/guide/error-handling.md
deleted file mode 100755
index 1dcc0cf470..0000000000
--- a/en/guide/error-handling.md
+++ /dev/null
@@ -1,302 +0,0 @@
----
-layout: page
-title: Express error handling
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "/guide/error-handling.html"
----
-
-# Error Handling
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. For example:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-For errors returned from asynchronous functions invoked by route handlers
-and middleware, you must pass them to the `next()` function, where Express will
-catch and process them.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Starting with Express 5, route handlers and middleware that return a Promise
-will call `next(value)` automatically when they reject or throw an error.
-For example:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-If you pass anything to the `next()` function (except the string `'route'`),
-Express regards the current request as being an error and will skip any
-remaining non-error handling routing and middleware functions.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. For example:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. For example:
-
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## The default error handler
-
-Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
-
-If you pass an error to `next()` and you do not handle it in a custom error
-handler, it will be handled by the built-in error handler; the error will be
-written to the client with the stack trace. The stack trace is not included
-in the production environment.
-
-<div class="doc-box doc-info" markdown="1">
-Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-* The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-* The `res.statusMessage` is set according to the status code.
-* The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-* Any headers specified in an `err.headers` object.
-
-If you call `next()` with an error after you have started writing the
-response (for example, if you encounter an error while streaming the
-response to the client), the Express default error handler closes the
-connection and fails the request.
-
-So when you add a custom error handler, you must delegate to
-the default Express error handler, when the headers
-have already been sent to the client:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. For example:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-You define error-handling middleware last, after other `app.use()` and routes calls; for example:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
-
-For organizational (and higher-level framework) purposes, you can define
-several error-handling middleware functions, much as you would with
-regular middleware functions. For example, to define an error-handler
-for requests made by using `XHR` and those without:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-In this example, the generic `logErrors` might write request and
-error information to `stderr`, for example:
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-Implement the "catch-all" `errorHandler` function as follows (for example):
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
-
-<div class="doc-box doc-info" markdown="1">
-Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.  `next(err)` will skip all remaining handlers in the chain except for those that are set up to handle errors as described above.
-</div>
diff --git a/en/guide/migrating-4.md b/en/guide/migrating-4.md
deleted file mode 100755
index a45f550a27..0000000000
--- a/en/guide/migrating-4.md
+++ /dev/null
@@ -1,609 +0,0 @@
----
-layout: page
-title: Migrating to Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "/guide/migrating-4.html"
----
-
-# Moving to Express 4
-
-<h2 id="overview">Overview</h2>
-
-Express 4 is a breaking change from Express 3. That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
-
-This article covers:
-
-<ul class="doclist">
-  <li><a href="#changes">Changes in Express 4</a>.</li>
-  <li><a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.</li>
-  <li><a href="#app-gen">Upgrading to the Express 4 app generator</a>.</li>
-</ul>
-
-<h2 id="changes">Changes in Express 4</h2>
-
-There are several significant changes in Express 4:
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Changes to the routing system.</a></li>
-  <li><a href="#other-changes">Various other changes.</a></li>
-</ul>
-
-See also:
-
-* [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-* [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Changes to Express core and middleware system
-</h3>
-
-Express 4 no longer depends on Connect, and removes all built-in
-middleware from its core, except for the `express.static` function. This means that
-Express is now an independent routing and middleware web framework, and
-Express versioning and releases are not affected by middleware updates.
-
-Without built-in middleware, you must explicitly add all the
-middleware that is required to run your app. Simply follow these steps:
-
-1. Install the module: `npm install --save <module-name>`
-2. In your app, require the module: `require('module-name')`
-3. Use the module according to its documentation: `app.use( ... )`
-
-The following table lists Express 3 middleware and their counterparts in Express 4.
-
-<table class="doctable" border="1">
-<tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</table>
-
-Here is the [complete list](https://github.com/senchalabs/connect#middleware) of Express 4 middleware.
-
-In most cases, you can simply replace the old version 3 middleware with
-its Express 4 counterpart. For details, see the module documentation in
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> accepts parameters</h4>
-
-In version 4 you can use a variable parameter to define the path where middleware functions are loaded, then read the value of the parameter from the route handler.
-For example:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-<h3 id="routing">
-The routing system
-</h3>
-
-Apps now implicitly load routing middleware, so you no longer have to
-worry about the order in which middleware is loaded with respect to
-the `router` middleware.
-
-The way you define routes is unchanged, but the routing system has two
-new features to help organize your routes:
-
-{: .doclist }
-* A new method, `app.route()`, to create chainable route handlers for a route path.
-* A new class, `express.Router`, to create modular mountable route handlers.
-
-<h4 id="app-route"><code>app.route()</code> method</h4>
-
-The new `app.route()` method enables you to create chainable route handlers
-for a route path. Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
-information about routes, see [`Router()` documentation](/{{ page.lang }}/4x/api.html#router).
-
-Here is an example of chained route handlers that are defined by using the `app.route()` function.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> class</h4>
-
-The other feature that helps to organize routes is a new class,
-`express.Router`, that you can use to create modular mountable
-route handlers. A `Router` instance is a complete middleware and
-routing system; for this reason it is often referred to as a "mini-app".
-
-The following example creates a router as a module, loads middleware in
-it, defines some routes, and mounts it on a path on the main app.
-
-For example, create a router file named `birds.js` in the app directory,
-with the following content:
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Then, load the router module in the app:
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-The app will now be able to handle requests to the `/birds` and
-`/birds/about` paths, and will call the `timeLog`
-middleware that is specific to the route.
-
-<h3 id="other-changes">
-Other changes
-</h3>
-
-The following table lists other small but important changes in Express 4:
-
-<table class="doctable" border="1">
-<tr>
-<th>Object</th>
-<th>Description</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 requires Node.js 0.10.x or later and has dropped support for
-Node.js 0.8.x.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-The `http` module is no longer needed, unless you need to directly work with it (socket.io/SPDY/HTTPS). The app can be started by using the
-`app.listen()` function.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-The `app.configure()` function has been removed.  Use the
-`process.env.NODE_ENV` or
-`app.get('env')` function to detect the environment and configure the app accordingly.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-The `json spaces` application property is disabled by default in Express 4.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Use `req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()`, and `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-No longer resolves relative URLs.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Was an array; now an object.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Was a function; now an object.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-Changed to `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Now available as `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Removed.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Removed.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Functionality is now limited to setting the basic cookie value. Use
-`res.cookie()` for added functionality.
-</td>
-</tr>
-</table>
-
-<h2 id="example-migration">Example app migration</h2>
-
-Here is an example of migrating an Express 3 application to Express 4.
-The files of interest are `app.js` and `package.json`.
-
-<h3 id="">
-Version 3 app
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Consider an Express v.3 application with the following `app.js` file:
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-The accompanying version 3 `package.json` file might look
-  something like this:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Process
-</h3>
-
-Begin the migration process by installing the required middleware for the
-Express 4 app and updating Express and Pug to their respective latest
-version with the following command:
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Make the following changes to `app.js`:
-
-1. The built-in Express middleware functions `express.favicon`,
-    `express.logger`, `express.methodOverride`,
-    `express.session`, `express.bodyParser` and
-    `express.errorHandler` are no longer available on the
-    `express` object. You must install their alternatives
-    manually and load them in the app.
-
-2. You no longer need to load the `app.router` function.
-    It is not a valid Express 4 app object, so remove the
-    `app.use(app.router);` code.
-
-3. Make sure that the middleware functions are loaded in the correct order - load `errorHandler` after loading the app routes.
-
-<h3 id="">Version 4 app</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-Running the above `npm` command will update `package.json` as follows:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Then, remove invalid code, load the required middleware, and make other
-changes as necessary. The `app.js` file will look like this:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-Unless you need to work directly with the `http` module (socket.io/SPDY/HTTPS), loading it is not required, and the app can be simply started this way:
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-</div>
-
-<h3 id="">Run the app</h3>
-
-The migration process is complete, and the app is now an
-Express 4 app. To confirm, start the app by using the following command:
-
-```bash
-$ node .
-```
-
-Load [http://localhost:3000](http://localhost:3000)
-  and see the home page being rendered by Express 4.
-
-<h2 id="app-gen">Upgrading to the Express 4 app generator</h2>
-
-The command-line tool to generate an Express app is still
-  `express`, but to upgrade to the new version, you must uninstall
-  the Express 3 app generator and then install the new
-  `express-generator`.
-
-<h3 id="">Installing </h3>
-
-If you already have the Express 3 app generator installed on your system,
-you must uninstall it:
-
-```bash
-$ npm uninstall -g express
-```
-Depending on how your file and directory privileges are configured,
-you might need to run this command with `sudo`.
-
-Now install the new generator:
-
-```bash
-$ npm install -g express-generator
-```
-
-Depending on how your file and directory privileges are configured,
-you might need to run this command with `sudo`.
-
-Now the `express` command on your system is updated to the
-Express 4 generator.
-
-<h3 id="">Changes to the app generator </h3>
-
-Command options and use largely remain the same, with the following exceptions:
-
-{: .doclist }
-* Removed the `--sessions` option.
-* Removed the `--jshtml` option.
-* Added the `--hogan` option to support [Hogan.js](http://twitter.github.io/hogan.js/).
-
-<h3 id="">Example</h3>
-
-Execute the following command to create an Express 4 app:
-
-```bash
-$ express app4
-```
-
-If you look at the contents of the `app4/app.js` file, you will notice
-that all the middleware functions (except `express.static`) that are required for
-the app are loaded as independent modules, and the `router` middleware
-is no longer explicitly loaded in the app.
-
-You will also notice that the `app.js` file is now a Node.js module, in contrast to the standalone app that was generated by the old generator.
-
-After installing the dependencies, start the app by using the following command:
-
-```bash
-$ npm start
-```
-
-If you look at the `npm start` script in the `package.json` file,
-you will notice that the actual command that starts the app is
-`node ./bin/www`, which used to be `node app.js`
-in Express 3.
-
-Because the `app.js` file that was generated by the Express 4 generator
-is now a Node.js module, it can no longer be started independently as an app
-(unless you modify the code). The module must be loaded in a Node.js file
-and started via the Node.js file. The Node.js file is `./bin/www`
-in this case.
-
-Neither the `bin` directory nor the extensionless `www`
-file is mandatory for creating an Express app or starting the app. They are
-just suggestions made by the generator, so feel free to modify them to suit your
-needs.
-
-To get rid of the `www` directory and keep things the "Express 3 way",
-delete the line that says `module.exports = app;` at the end of the
-`app.js` file, then paste the following code in its place:
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Ensure that you load the `debug` module at the top of the `app.js` file by using the following code:
-
-```js
-var debug = require('debug')('app4')
-```
-
-Next, change `"start": "node ./bin/www"` in the `package.json` file to `"start": "node app.js"`.
-
-You have now moved the functionality of `./bin/www` back to
-`app.js`. This change is not recommended, but the exercise helps you
-to understand how the `./bin/www` file works, and why the `app.js` file
-no longer starts on its own.
diff --git a/en/guide/migrating-5.md b/en/guide/migrating-5.md
deleted file mode 100755
index 4541a282c9..0000000000
--- a/en/guide/migrating-5.md
+++ /dev/null
@@ -1,613 +0,0 @@
----
-layout: page
-title: Migrating to Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "/guide/migrating-5.html"
----
-
-# Moving to Express 5
-
-<h2 id="overview">Overview</h2>
-
-Express 5 is not very different from Express 4; although it maintains the same basic API, there are still changes that break compatibility with the previous version. Therefore, an application built with Express 4 might not work if you update it to use Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-You can then run your automated tests to see what fails, and fix problems according to the updates listed below. After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Changes in Express 5</h2>
-
-**Removed methods and properties**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Pluralized method names</a></li>
-  <li><a href="#leading">Leading colon in name argument to app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Changed**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-
-**Improvements**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Removed methods and properties
-
-If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 no longer supports the `app.del()` function. If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
-
-Initially, `del` was used instead of `delete`, because `delete` is a reserved keyword in JavaScript. However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-The `app.param(fn)` signature was used for modifying the behavior of the `app.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="plural">Pluralized method names</h3>
-
-The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
-
-`req.acceptsCharset()` is replaced by `req.acceptsCharsets()`.
-
-`req.acceptsEncoding()` is replaced by `req.acceptsEncodings()`.
-
-`req.acceptsLanguage()` is replaced by `req.acceptsLanguages()`.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Leading colon (:) in the name for app.param(name, fn)</h3>
-
-A leading colon character (:) in the name for the `app.param(name, fn)` function is a remnant of Express 3, and for the sake of backwards compatibility, Express 4 supported it with a deprecation notice. Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
-
-This should not affect your code if you follow the Express 4 documentation of [app.param](/{{ page.lang }}/4x/api.html#app.param), as it makes no mention of the leading colon.
-
-<h3 id="req.param">req.param(name)</h3>
-
-This potentially confusing and dangerous method of retrieving form data has been removed. You will now need to specifically look for the submitted parameter name in the `req.params`, `req.body`, or `req.query` object.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 no longer supports the signature `res.json(obj, status)`. Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 no longer supports the signature `res.jsonp(obj, status)`. Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
-If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-The `res.sendfile()` function has been replaced by a camel-cased version `res.sendFile()` in Express 5.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Changed
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. For example:
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-should be changed to:
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-For example:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-The `app.router` object, which was removed in Express 4, has made a comeback in Express 5. In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-In Express 4, the `req.host` function incorrectly stripped off the port number if it was present. In Express 5, the port number is maintained.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Improvements
-
-<h3 id="res.render">res.render()</h3>
-
-This method now enforces asynchronous behavior for all view engines, avoiding bugs caused by view engines that had a synchronous implementation and that violated the recommended interface.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/en/guide/overriding-express-api.md b/en/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/en/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/en/guide/routing.md b/en/guide/routing.md
deleted file mode 100755
index 835a7a7338..0000000000
--- a/en/guide/routing.md
+++ /dev/null
@@ -1,412 +0,0 @@
----
-layout: page
-title: Express routing
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "/guide/routing.html"
----
-
-# Routing
-
-_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
-For an introduction to routing, see [Basic routing](/{{ page.lang }}/starter/basic-routing.html).
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.  
-
-The following code is an example of a very basic route.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Route methods</h2>
-
-A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
-
-The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Route paths</h2>
-
-Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Route paths based on strings
-
-This route path will match requests to the root route, `/`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-This route path will match requests to `/about`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-This route path will match requests to `/random.text`.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Route paths based on string patterns
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-This route path will match `acd` and `abcd`.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-This route path will match `/abe` and `/abcde`.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Route paths based on regular expressions
-
-This route path will match anything with an "a" in it.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">Route parameters</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Route handlers</h2>
-
-You can provide multiple callback functions that behave like [middleware](/{{ page.lang }}/guide/using-middleware.html) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
-
-A single callback function can handle a route. For example:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-More than one callback function can handle a route (make sure you specify the `next` object). For example:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-An array of callback functions can handle a route. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-A combination of independent functions and arrays of functions can handle a route. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Response methods</h2>
-
-The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
-
-| Method                                                          | Description                                                                           |
-| --------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/5x/api.html#res.download)     | Prompt a file to be downloaded.                                                       |
-| [res.end()](/{{ page.lang }}/5x/api.html#res.end)               | End the response process.                                                             |
-| [res.json()](/{{ page.lang }}/5x/api.html#res.json)             | Send a JSON response.                                                                 |
-| [res.jsonp()](/{{ page.lang }}/5x/api.html#res.jsonp)           | Send a JSON response with JSONP support.                                              |
-| [res.redirect()](/{{ page.lang }}/5x/api.html#res.redirect)     | Redirect a request.                                                                   |
-| [res.render()](/{{ page.lang }}/5x/api.html#res.render)         | Render a view template.                                                               |
-| [res.send()](/{{ page.lang }}/5x/api.html#res.send)             | Send a response of various types.                                                     |
-| [res.sendFile()](/{{ page.lang }}/5x/api.html#res.sendFile)     | Send a file as an octet stream.                                                       |
-| [res.sendStatus()](/{{ page.lang }}/5x/api.html#res.sendStatus) | Set the response status code and send its string representation as the response body. |
-
-<h2 id="app-route">app.route()</h2>
-
-You can create chainable route handlers for a route path by using `app.route()`.
-Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/{{ page.lang }}/5x/api.html#router).
-
-Here is an example of chained route handlers that are defined by using `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
-
-The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
-
-Create a router file named `birds.js` in the app directory, with the following content:
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Then, load the router module in the app:
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/en/guide/using-middleware.md b/en/guide/using-middleware.md
deleted file mode 100644
index c0469d03ca..0000000000
--- a/en/guide/using-middleware.md
+++ /dev/null
@@ -1,278 +0,0 @@
----
-layout: page
-title: Using Express middleware
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "/guide/using-middleware.html"
----
-
-# Using middleware
-
-Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
-
-Middleware functions can perform the following tasks:
-
-* Execute any code.
-* Make changes to the request and the response objects.
-* End the request-response cycle.
-* Call the next middleware function in the stack.
-
-If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
-
-An Express application can use the following types of middleware:
-
- - [Application-level middleware](#middleware.application)
- - [Router-level middleware](#middleware.router)
- - [Error-handling middleware](#middleware.error-handling)
- - [Built-in middleware](#middleware.built-in)
- - [Third-party middleware](#middleware.third-party)
-
-You can load application-level and router-level middleware with an optional mount path.
-You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
-
-<h2 id='middleware.application'>Application-level middleware</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
-HTTP request on the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Here is an example of loading a series of middleware functions at a mount point, with a mount path.
-It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
-
-This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Router-level middleware</h2>
-
-Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
-
-```js
-const router = express.Router()
-```
-Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
-
-The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-To skip the rest of the router's middleware functions, call `next('router')`
-to pass control back out of the router instance.
-
-This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Error-handling middleware</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors.
-</div>
-
-Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-For details about error-handling middleware, see: [Error handling](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Built-in middleware</h2>
-
-Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
-functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
-
-Express has the following built-in middleware functions:
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Third-party middleware</h2>
-
-Use third-party middleware to add functionality to Express apps.
-
-Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
-
-The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware.html).
diff --git a/en/guide/using-template-engines.md b/en/guide/using-template-engines.md
deleted file mode 100755
index 9921ce5b7a..0000000000
--- a/en/guide/using-template-engines.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Using template engines with Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "/guide/using-template-engines.html"
----
-
-# Using template engines with Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-* `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
-This defaults to the `views` directory in the application root directory.
-* `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
-
-Then install the corresponding template engine npm package; for example to install Pug:
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
-which `res.render()` calls to render the template code.
-
-Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
-library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
-</div>
-
-After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
-Express loads the module internally, for example:
-
-```js
-app.set('view engine', 'pug')
-```
-
-Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Create a route to render the `index.pug` file. If the `view engine` property is not set,
-you must specify the extension of the `view` file. Otherwise, you can omit it.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-When you make a request to the home page, the `index.pug` file will be rendered as HTML.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/en/guide/writing-middleware.md b/en/guide/writing-middleware.md
deleted file mode 100755
index 1f3272f7e4..0000000000
--- a/en/guide/writing-middleware.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-layout: page
-title: Writing middleware for use in Express apps
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "/guide/writing-middleware.html"
----
-
-# Writing middleware for use in Express apps
-
-<h2>Overview</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
-
-Middleware functions can perform the following tasks:
-
-* Execute any code.
-* Make changes to the request and the response objects.
-* End the request-response cycle.
-* Call the next middleware in the stack.
-
-If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
-
-The following figure shows the elements of a middleware function call:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">HTTP method for which the middleware function applies.</div>
-
-<div class="callout" id="callout2">Path (route) for which the middleware function applies.</div>
-
-<div class="callout" id="callout3">The middleware function.</div>
-
-<div class="callout" id="callout4">Callback argument to the middleware function, called "next" by convention.</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Example</h2>
-
-Here is an example of a simple "Hello World" Express application.
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Here is a simple example of a middleware function called "myLogger". This function just prints "LOGGED" when a request to the app passes through it. The middleware function is assigned to a variable named `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Notice the call above to `next()`. Calling this function invokes the next middleware function in the app.
-The `next()` function is not a part of the Node.js or Express API, but is the third argument that is passed to the middleware function. The `next()` function could be named anything, but by convention it is always named "next".
-To avoid confusion, always use this convention.
-</div>
-
-To load the middleware function, call `app.use()`, specifying the middleware function.
-For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Every time the app receives a request, it prints the message "LOGGED" to the terminal.
-
-The order of middleware loading is important: middleware functions that are loaded first are also executed first.
-
-If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
-
-The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
-
-<h3>Middleware function requestTime</h3>
-
-Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
-to the request object.
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
-
-For more information about Express middleware, see: [Using Express middleware](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/en/resources/community.md b/en/resources/community.md
deleted file mode 100755
index 108226d722..0000000000
--- a/en/resources/community.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: page
-title: Express community
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "/resources/community.html"
----
-
-# Community
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-Our vibrant community has created a large variety of extensions,
-[middleware modules](/{{ page.lang }}/resources/middleware.html) and higher-level frameworks.
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Issues
-
-If you've come across what you think is a bug, or just want to make
-a feature request open a ticket in the [issue queue](https://github.com/expressjs/express/issues).
-
-## Examples
-
-View dozens of Express application [examples](https://github.com/expressjs/express/tree/master/examples)
-in the repository covering everything from API design and authentication to template engine integration.
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3>
-        <a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3>
-        <a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/en/resources/contributing.md b/en/resources/contributing.md
deleted file mode 100644
index f259a3c1c1..0000000000
--- a/en/resources/contributing.md
+++ /dev/null
@@ -1,509 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "/resources/community.html"
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-* [Technical committee](#technical-committee)
-* [Community contributing guide](#community-contributing-guide)
-* [Collaborator's guide](#collaborators-guide)
-* [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-* Encourages new contributions.
-* Encourages contributors to remain involved.
-* Avoids unnecessary processes and bureaucracy whenever possible.
-* Creates a transparent decision making process that makes it clear how
-contributors can be involved in decision making.
-
-### Vocabulary
-
-* A **Contributor** is any individual creating or commenting on an issue or pull request.
-* A **Committer** is a subset of contributors who have been given write access to the repository.
-* A **Project Captain** is the lead maintainer of a repository.
-* A **TC (Technical Committee)** is a group of committers representing the required technical
-expertise to resolve rare disputes.
-* A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-* Repos can have as many captains as make sense for the scope of work.
-* A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-* If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-* The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-* The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-* In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-* Tests must pass.
-* Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-* If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-* Full and runnable JS code.
-* Clear description of the problem or unexpected behavior.
-* Clear description of the expected result.
-* Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input. 
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-  * [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-  * [Disclosure Policy](#disclosure-policy)
-  * [Comments on this Policy](#comments-on-this-policy)
-  * [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability  
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously. 
-Thank you for improving the security of Express and related projects. 
-We appreciate your efforts in responsible disclosure and will make every effort 
-to acknowledge your contributions.  
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage) 
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md) 
-will acknowledge your report as soon as possible. 
-These timelines may extend when our triage 
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)  
-
-The preferred way to report security vulnerabilities is through 
-[GitHub Security Advisories](https://github.com/advisories). 
-This allows us to collaborate on a fix while maintaining the 
-confidentiality of the report.  
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):  
-1. Visit the **Security** tab of the affected repository on GitHub.  
-2. Click **Report a vulnerability** and follow the provided steps.  
-
-This process applies to any repositories within the Express ecosystem. 
-If you are unsure whether a repository falls under this policy, 
-feel free to reach out via email.  
-
-#### Reporting via Email  
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.  
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.  
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.  
-
-#### Third-Party Modules  
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.  
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-  * Confirm the problem and determine the affected versions.
-  * Audit code to find any potential similar problems.
-  * Prepare fixes for all releases still under maintenance. These fixes will be
-    released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-    - Display or screen sizing problems
-    - Mobile responsiveness issues
-    - Missing or broken accessibility features 
-    - Website outages
-    - Broken links
-    - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-    - Spelling errors
-    - Incorrect/outdated Express.js documentation
-    - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-    - Fix spelling errors 
-    - Fix incorrect/poorly translated words
-    - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first. 
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-So you've found a problem that you want to fix, or have a site enhancement you want to make. 
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals. 
-    - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-    - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-    - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback. 
-    - For submissions proposing significant change, we encourage you to follow the review process before starting work. 
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes! 
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.  
-
-**Markdown Page Files**: 
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup. 
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example. 
-
-**Includes Partials and Layout Templates**
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages. 
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-- These files make up the individual blog posts. If you want to contribute a blog post please
-follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory. 
-
-**CSS or Javascript**
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options. 
-
-
-1. __Run Locally__: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.  
-    - This is the recommended option for moderate to complex work. 
-
-2. __Run using Deploy Preview__: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/). 
-    1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a *draft* pull request. 
-    2. After the build steps are complete, you'll have access to a __Deploy Preview__ tab that will run your changes on the web, rebuilding after each commit is pushed. 
-    3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-  
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/en/resources/glossary.md b/en/resources/glossary.md
deleted file mode 100755
index c743b8fafd..0000000000
--- a/en/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express glossary
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "/resources/glossary.html"
----
-
-# Glossary
-
-### application
-
-In general, one or more programs that are designed to carry out operations for a specific purpose.  In the context of Express, a program that uses the Express API running on the Node.js platform.  Might also refer to an [app object](/{{ page.lang }}/api.html#express).
-
-### API
-
-Application programming interface. Spell out the abbreviation when it is first used.
-
-### Express
-
-A fast, un-opinionated, minimalist web framework for Node.js applications. In general, "Express" is preferred to "Express.js," though the latter is acceptable.
-
-### libuv
-
-A multi-platform support library which focuses on asynchronous I/O, primarily developed for use by Node.js.
-
-### middleware 
-
-A function that is invoked by the Express routing layer before the final request handler, and thus sits in the middle between a raw request and the final intended route. A few fine points of terminology around middleware:
-
-  * `var foo = require('middleware')` is called _requiring_ or _using_ a Node.js module. Then the statement `var mw = foo()` typically returns the middleware.
-  * `app.use(mw)` is called _adding the middleware to the global processing stack_.
-  * `app.get('/foo', mw, function (req, res) { ... })` is called _adding the middleware to the "GET /foo" processing stack_.
-
-### Node.js
-
-A software platform that is used to build scalable network applications. Node.js uses JavaScript as its scripting language, and achieves high throughput via non-blocking I/O and a single-threaded event loop. See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
-
-### open-source, open source
-
-When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software). 
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### request
-
-An HTTP request. A client submits an HTTP request message to a server, which returns a response.  The request must use one of several [request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) such as GET, POST, and so on.
-
-### response
-
-An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
-
-### route
-
-Part of a URL that identifies a resource. For example, in `http://foo.com/products/id`, "/products/id" is the route.
-
-### router
-
-See [router](/{{ page.lang }}/api.html#router) in the API reference.
diff --git a/en/resources/middleware.md b/en/resources/middleware.md
deleted file mode 100755
index ce9b2ef19f..0000000000
--- a/en/resources/middleware.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-layout: middleware
-title: Express middleware
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "/resources/middleware.html"
-module: mw-home
----
-
-## Express middleware
-
-The Express middleware modules listed here are maintained by the
-[Expressjs team](https://github.com/orgs/expressjs/people).
-
-| Middleware module                                                         | Description                                                                                         |
-| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                   |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                                 |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                             |
-
-## Additional middleware modules
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Middleware module                                   | Description                                                                                                                                   |
-| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet)        | Helps secure your apps by setting various HTTP headers.                                                                                       |
-| [passport](https://github.com/jaredhanson/passport) | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/en/resources/middleware/body-parser.md b/en/resources/middleware/body-parser.md
deleted file mode 100644
index 8ccac905c5..0000000000
--- a/en/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '/resources/middleware/body-parser.html'
-module: body-parser
----
diff --git a/en/resources/middleware/compression.md b/en/resources/middleware/compression.md
deleted file mode 100644
index a3cc042841..0000000000
--- a/en/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '/resources/middleware/compression.html'
-module: compression
----
diff --git a/en/resources/middleware/connect-rid.md b/en/resources/middleware/connect-rid.md
deleted file mode 100644
index ea5e61ea4d..0000000000
--- a/en/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '/resources/middleware/connect-rid.html'
-module: connect-rid
----
diff --git a/en/resources/middleware/cookie-parser.md b/en/resources/middleware/cookie-parser.md
deleted file mode 100644
index 4e5c6de057..0000000000
--- a/en/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '/resources/middleware/cookie-parser.html'
-module: cookie-parser
----
diff --git a/en/resources/middleware/cookie-session.md b/en/resources/middleware/cookie-session.md
deleted file mode 100644
index 31766811d5..0000000000
--- a/en/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '/resources/middleware/cookie-session.html'
-module: cookie-session
----
diff --git a/en/resources/middleware/cors.md b/en/resources/middleware/cors.md
deleted file mode 100644
index 21f2169ec5..0000000000
--- a/en/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '/resources/middleware/cors.html'
-module: cors
----
diff --git a/en/resources/middleware/errorhandler.md b/en/resources/middleware/errorhandler.md
deleted file mode 100644
index 208524bc55..0000000000
--- a/en/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '/resources/middleware/errorhandler.html'
-module: errorhandler
----
diff --git a/en/resources/middleware/method-override.md b/en/resources/middleware/method-override.md
deleted file mode 100644
index a3e5544f37..0000000000
--- a/en/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '/resources/middleware/method-override.html'
-module: method-override
----
diff --git a/en/resources/middleware/morgan.md b/en/resources/middleware/morgan.md
deleted file mode 100644
index 5407b23ae2..0000000000
--- a/en/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '/resources/middleware/morgan.html'
-module: morgan
----
diff --git a/en/resources/middleware/multer.md b/en/resources/middleware/multer.md
deleted file mode 100644
index 621660a92e..0000000000
--- a/en/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '/resources/middleware/multer.html'
-module: multer
----
diff --git a/en/resources/middleware/response-time.md b/en/resources/middleware/response-time.md
deleted file mode 100644
index e005f72465..0000000000
--- a/en/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '/resources/middleware/response-time.html'
-module: response-time
----
diff --git a/en/resources/middleware/serve-favicon.md b/en/resources/middleware/serve-favicon.md
deleted file mode 100644
index b0e9fac621..0000000000
--- a/en/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '/resources/middleware/serve-favicon.html'
-module: serve-favicon
----
diff --git a/en/resources/middleware/serve-index.md b/en/resources/middleware/serve-index.md
deleted file mode 100644
index 0adf89229f..0000000000
--- a/en/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '/resources/middleware/serve-index.html'
-module: serve-index
----
diff --git a/en/resources/middleware/serve-static.md b/en/resources/middleware/serve-static.md
deleted file mode 100644
index 6103a26b40..0000000000
--- a/en/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '/resources/middleware/serve-static.html'
-module: serve-static
----
diff --git a/en/resources/middleware/session.md b/en/resources/middleware/session.md
deleted file mode 100644
index 2e95e8456c..0000000000
--- a/en/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '/resources/middleware/session.html'
-module: session
----
diff --git a/en/resources/middleware/timeout.md b/en/resources/middleware/timeout.md
deleted file mode 100644
index 0b9d2253f8..0000000000
--- a/en/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '/resources/middleware/timeout.html'
-module: timeout
----
diff --git a/en/resources/middleware/vhost.md b/en/resources/middleware/vhost.md
deleted file mode 100644
index 7f42ece96b..0000000000
--- a/en/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '/resources/middleware/vhost.html'
-module: vhost
----
diff --git a/en/resources/utils.md b/en/resources/utils.md
deleted file mode 100644
index e70416706c..0000000000
--- a/en/resources/utils.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "/resources/utilities.html"
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules | Description|
-|-----------------|------------|
-| [cookies](https://www.npmjs.com/package/cookies) | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware.|
-| [csrf](https://www.npmjs.com/package/csrf) | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.|
-| [finalhandler](https://www.npmjs.com/package/finalhandler) | Function to invoke as the final step to respond to HTTP request.|
-| [parseurl](https://www.npmjs.com/package/parseurl) | Parse a URL with caching. |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as ``/user/:name` into a regular expression.|
-| [resolve-path](https://www.npmjs.com/package/resolve-path) | Resolves a relative path against a root path with validation. |
-| [router](https://www.npmjs.com/package/router) | Simple middleware-style router. |
-| [send](https://www.npmjs.com/package/send) | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.|
-
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/en/starter/basic-routing.md b/en/starter/basic-routing.md
deleted file mode 100755
index 700eafd1f1..0000000000
--- a/en/starter/basic-routing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: Express basic routing
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "/starter/basic-routing.html"
----
-
-# Basic routing
-
-_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
-
-Each route can have one or more handler functions, which are executed when the route is matched.
-
-Route definition takes the following structure:
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Where:
-
-- `app` is an instance of `express`.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` is a path on the server.
-- `HANDLER` is the function executed when the route is matched.
-
-<div class="doc-box doc-notice" markdown="1">
-This tutorial assumes that an instance of `express` named `app` is created and the server is running. If you are not familiar with creating an app and starting it, see the [Hello world example](/{{ page.lang }}/starter/hello-world.html).
-</div>
-
-The following examples illustrate defining simple routes.
-
-Respond with `Hello World!` on the homepage:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Respond to a PUT request to the `/user` route:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Respond to a DELETE request to the `/user` route:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-For more details about routing, see the [routing guide](/{{ page.lang }}/guide/routing.html).
-
diff --git a/en/starter/examples.md b/en/starter/examples.md
deleted file mode 100755
index 228509a17b..0000000000
--- a/en/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "/starter/examples.html"
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/en/starter/faq.md b/en/starter/faq.md
deleted file mode 100755
index 03cd0bf69a..0000000000
--- a/en/starter/faq.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-layout: page
-title: Express FAQ
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "/starter/faq.html"
----
-
-# FAQ
-
-## How should I structure my application?
-
-There is no definitive answer to this question. The answer depends
-on the scale of your application and the team that is involved. To be as
-flexible as possible, Express makes no assumptions in terms of structure.
-
-Routes and other application-specific logic can live in as many files
-as you wish, in any directory structure you prefer. View the following
-examples for inspiration:
-
-* [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
-* [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-* [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Also, there are third-party extensions for Express, which simplify some of these patterns:
-
-* [Resourceful routing](https://github.com/expressjs/express-resource)
-
-## How do I define models?
-
-Express has no notion of a database. This concept is
-left up to third-party Node modules, allowing you to
-interface with nearly any database.
-
-See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
-
-## How can I authenticate users?
-
-Authentication is another opinionated area that Express does not
-venture into. You may use any authentication scheme you wish.
-For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
-
-
-## Which template engines does Express support?
-
-Express supports any template engine that conforms with the `(path, locals, callback)` signature.
-To normalize template engine interfaces and caching, see the
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-project for support. Unlisted template engines might still support the Express signature.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## How do I handle 404 responses?
-
-In Express, 404 responses are not the result of an error, so
-the error-handler middleware will not capture them. This behavior is
-because a 404 response simply indicates the absence of additional work to do;
-in other words, Express has executed all middleware functions and routes,
-and found that none of them responded. All you need to
-do is add a middleware function at the very bottom of the stack (below all other functions)
-to handle a 404 response:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## How do I setup an error handler?
-
-You define error-handling middleware in the same way as other middleware,
-except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-For more information, see [Error handling](/{{ page.lang }}/guide/error-handling.html).
-
-## How do I render plain HTML?
-
-You don't! There's no need to "render" HTML with the `res.render()` function.
-If you have a specific file, use the `res.sendFile()` function.
-If you are serving many assets from a directory, use the `express.static()`
-middleware function.
-
-## What version of Node.js does Express require?
-
-* [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-* [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/en/starter/generator.md b/en/starter/generator.md
deleted file mode 100755
index e2d3437be5..0000000000
--- a/en/starter/generator.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-layout: page
-title: Express application generator
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "/starter/generator.html"
----
-
-# Express application generator
-
-Use the application generator tool, `express-generator`, to quickly create an application skeleton.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Display the command options with the `-h` option:
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-Then install dependencies:
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-On MacOS or Linux, run the app with this command:
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-On Windows Command Prompt, use this command:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-
-Then, load `http://localhost:3000/` in your browser to access the app.
-
-The generated app has the following directory structure:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-The app structure created by the generator is just one of many ways to structure Express apps. Feel free to use this structure or modify it to best suit your needs.
-</div>
\ No newline at end of file
diff --git a/en/starter/hello-world.md b/en/starter/hello-world.md
deleted file mode 100755
index 9edbcf2d34..0000000000
--- a/en/starter/hello-world.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-layout: page
-title: Express "Hello World" example
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "/starter/hello-world.html"
----
-
-# Hello world example
-
-<div class="doc-box doc-info" markdown="1">
-Embedded below is essentially the simplest Express app you can create. It is a single file app &mdash; _not_ what you'd get if you use the [Express generator](/{{ page.lang }}/starter/generator.html), which creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and sub-directories for various purposes.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
-to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
-
-### Running Locally
-
-First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/{{ page.lang }}/starter/installing.html).
-
-In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
-
-<div class="doc-box doc-notice" markdown="1">
-The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can invoke
-`req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express involved.
-</div>
-
-Run the app with the following command:
-
-```bash
-$ node app.js
-```
-
-Then, load `http://localhost:3000/` in a browser to see the output.
\ No newline at end of file
diff --git a/en/starter/installing.md b/en/starter/installing.md
deleted file mode 100755
index e115db5cc4..0000000000
--- a/en/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Installing Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "/starter/installing.html"
----
-
-# Installing
-
-Assuming you've already installed [Node.js](https://nodejs.org/), create a directory to hold your application, and make that your working directory.
-
-* [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-* [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Use the `npm init` command to create a `package.json` file for your application.
-For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-This command prompts you for a number of things, such as the name and version of your application.
-For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-```
-entry point: (index.js)
-```
-
-Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
-
-Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
-
-```bash
-$ npm install express
-```
-
-To install Express temporarily and not add it to the dependencies list:
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the `package.json` file; with earlier versions of npm, you must specify the `--save` option explicitly. Then, afterwards, running `npm install` in the app directory will automatically install modules in the dependencies list.
-</div>
\ No newline at end of file
diff --git a/en/starter/static-files.md b/en/starter/static-files.md
deleted file mode 100755
index 1ee822011c..0000000000
--- a/en/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: Serving static files in Express
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "/starter/static-files.html"
----
-
-# Serving static files in Express
-
-To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-Now, you can load the files that are in the `public` directory:
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express looks up the files relative to the static directory, so the name of the static directory is not part of the URL.
-</div>
-
-To use multiple static assets directories, call the `express.static` middleware function multiple times:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Now, you can load the files that are in the `public` directory from the `/static` path prefix.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/en/support/index.md b/en/support/index.md
deleted file mode 100644
index dcd2620b8f..0000000000
--- a/en/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version | Minimum Node.js Version | Support Start Date | Support End Date |
-| -- | -- | -- | -- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18 | September 2024 | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0 | April 2014 | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline} | 0.8.0 | October 2012 | July 2015 |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline} | 0.4.1 | March 2011 | July 2012 |
-| **v1.x**{: .eol } | 0.2.0 | December 2010 | March 2011 |
-| **v0.14.x**{: .eol } | 0.1.98 | December 2010 | December 2010 |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
- - [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/es/3x/api.md b/es/3x/api.md
deleted file mode 100644
index 686bac7ccc..0000000000
--- a/es/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - Referencia de API
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x YA NO SE MANTIENE**
-
-Los problemas de rendimiento y seguridad conocidos y desconocidos en 3.x no se han solucionado desde la última actualización (1 de agosto de 2015). Se recomienda especialmente utilizar la última versión de Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>API de 3.x</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/es/4x/api.md b/es/4x/api.md
deleted file mode 100644
index 8095c157ab..0000000000
--- a/es/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - Referencia de API
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>API de 4.x</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/es/5x/api.md b/es/5x/api.md
deleted file mode 100644
index 650d5e951a..0000000000
--- a/es/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Referencia de API
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/es/advanced/best-practice-performance.md b/es/advanced/best-practice-performance.md
deleted file mode 100644
index 817f934314..0000000000
--- a/es/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: Mejores prácticas de rendimiento cuando se utiliza Express en producción
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# Production best practices: performance and reliability
-
-En este artículo se describen las mejores prácticas de rendimiento y fiabilidad para las aplicaciones Express desplegadas en producción.
-
-Este tema entra claramente dentro del área de "DevOps", que abarca operaciones y desarrollos tradicionales. Por lo tanto, la información se divide en dos partes:
-
-- Cosas que hacer en el código (la parte de desarrollo):
-  - [Utilizar la compresión de gzip](#utilizar-la-compresión-de-gzip)
-  - [No utilizar funciones síncronas](#no-utilizar-funciones-síncronas)
-  - [Realizar un registro correcto](#realizar-un-registro-correcto)
-  - [Manejar las excepciones correctamente](#manejar-las-excepciones-correctamente)
-- Cosas que hacer en el entorno / configuración (la parte de operaciones):
-  - [Establecer NODE_ENV en "production"](#establecer-node_env-en-production)
-  - [Asegurarse de que la aplicación se reinicia automáticamente](#asegurarse-de-que-la-aplicación-se-reinicia-automáticamente)
-  - [Ejecutar la aplicación en un clúster](#ejecutar-la-aplicación-en-un-clúster)
-  - [Almacenar en la caché los resultados de la solicitud](#almacenar-en-la-caché-los-resultados-de-la-solicitud)
-  - [Utilizar un equilibrador de carga](#utilizar-un-equilibrador-de-carga)
-  - [Utilizar un proxy inverso](#utilizar-un-proxy-inverso)
-
-## Cosas que hacer en el código
-
-Estas son algunas de las cosas que puede hacer en el código para mejorar el rendimiento de la aplicación:
-
-- [Utilizar la compresión de gzip](#utilizar-la-compresión-de-gzip)
-- [No utilizar funciones síncronas](#no-utilizar-funciones-síncronas)
-- [Realizar un registro correcto](#realizar-un-registro-correcto)
-- [Manejar las excepciones correctamente](#manejar-las-excepciones-correctamente)
-
-### Utilizar la compresión de gzip
-
-La compresión de gzip puede disminuir significativamente el tamaño del cuerpo de respuesta y, por lo tanto, aumentar la velocidad de una aplicación web. Utilice el middleware de [compresión](https://www.npmjs.com/package/compression) para la compresión de gzip en la aplicación Express. For example:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-Para un sitio web con un tráfico elevado en producción, la mejor forma de aplicar la compresión es implementarla como un nivel de proxy inverso (consulte [Utilizar un proxy inverso](#proxy)). En este caso, no es necesario utilizar el middleware de compresión. Para obtener detalles sobre cómo habilitar la compresión de gzip en Nginx, consulte [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) en la documentación de Nginx.
-
-### No utilizar funciones síncronas
-
-Las funciones síncronas y los métodos impiden el avance del proceso de ejecución hasta que vuelven. Una llamada individual a una función síncrona puede volver en pocos microsegundos o milisegundos, aunque en sitios web de tráfico elevado, estas llamadas se suman y reducen el rendimiento de la aplicación. Evite su uso en producción.
-
-Aunque Node y muchos módulos proporcionan versiones síncronas y asíncronas de las funciones, utilice siempre la versión asíncrona en producción. La única vez que está justificado utilizar una función síncrona es en el arranque inicial.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Desde luego, no deseará utilizarlo en producción, sólo para garantizar que el código está listo para producción. Consulte [Weekly update for io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0) para obtener más información.
-
-### Realizar un registro correcto
-
-En general, hay dos motivos para realizar un registro desde la aplicación: a efectos de depuración o para registrar la actividad de la aplicación (básicamente, todo lo demás). El uso de `console.log()` o `console.err()` para imprimir mensajes de registro en el terminal es una práctica común en el desarrollo. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### For debugging
-
-Si realiza el registro a efectos de depuración, en lugar de utilizar `console.log()`, utilice un módulo de depuración especial como [debug](https://www.npmjs.com/package/debug). Este módulo permite utilizar la variable de entorno DEBUG para controlar qué mensajes de depuración se envían a `console.err()`, si se envía alguno. Para mantener la aplicación básicamente asíncrona, deberá canalizar `console.err()` a otro programa. Pero en este caso, realmente no va a depurar en producción, ¿no?
-
-#### Para la actividad de la aplicación
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Manejar las excepciones correctamente
-
-Las aplicaciones Node se bloquean cuando encuentran una excepción no capturada. Si no maneja las excepciones ni realiza las acciones necesarias, la aplicación Express se bloqueará y quedará fuera de línea. Si sigue el consejo de [Asegurarse de que la aplicación se reinicia automáticamente](#restart) más abajo, la aplicación se recuperará de un bloqueo. Afortunadamente, las aplicaciones Express normalmente necesitan un breve tiempo de arranque. No obstante, desea evitar el bloqueo en primer lugar y, para ello, deberá manejar correctamente las excepciones.
-
-Para asegurarse de manejar todas las excepciones, siga estas técnicas:
-
-- [Utilizar try-catch](#try-catch)
-- [Utilizar promesas](#utilizar-promesas)
-
-Antes de profundizar en estos temas, deberá tener unos conocimientos básicos del manejo de errores de Node/Express: el uso de devoluciones de llamada error-first y la propagación de errores en el middleware. Node utiliza un convenio de "devolución de llamada error-first" para devolver los errores de las funciones asíncronas, donde el primer parámetro en la función de devolución de llamada es el objeto de error, seguido de los datos de resultados en los parámetros posteriores. Para indicar que no hay ningún error, pase null como el primer parámetro. La función de devolución de llamada debe seguir por lo tanto el convenio de devolución de llamada error-first para manejar correctamente el error. En Express, la práctica recomendada es utilizar la función next() para propagar los errores a través de la cadena de middleware.
-
-Para obtener más información sobre los aspectos básicos del manejo de errores, consulte:
-
-- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Utilizar try-catch
-
-Try-catch es una construcción de lenguaje JavaScript que puede utilizar para capturar excepciones en código síncrono. Por ejemplo, utilice try-catch para manejar los errores de análisis de JSON, como se muestra a continuación.
-
-A continuación, se muestra un ejemplo de uso de try-catch para manejar una posible excepción de bloqueo de proceso.
-Esta función de middleware acepta un parámetro de campo de consulta denominado "params" que es un objeto JSON.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-No obstante, try-catch sólo funciona para el código síncrono. Como la plataforma de Node es principalmente asíncrona (particularmente en un entorno de producción), try-catch no capturará muchas excepciones.
-
-#### Use promises
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### Qué no debe hacer
-
-Algo que _no_ debe hacer es escuchar el suceso `uncaughtException`, que se emite cuando una excepción se reproduce hacia atrás en el bucle de sucesos. La adición de un escucha de sucesos para `uncaughtException` cambiará el comportamiento predeterminado del proceso que se encuentra con la excepción; el proceso continuará ejecutándose a pesar de la excepción. Esto puede parecer una buena forma de evitar el bloqueo de la aplicación, pero continuar ejecutando la aplicación después de una excepción no capturada es una práctica peligrosa y no se recomienda, ya que el estado del proceso se vuelve imprevisible y poco fiable.
-
-Asimismo, el uso de `uncaughtException` se reconoce oficialmente como un mecanismo [arduo](https://nodejs.org/api/process.html#process_event_uncaughtexception) y hay una [propuesta](https://github.com/nodejs/node-v0.x-archive/issues/2582) para eliminarlo del núcleo. Por lo tanto, la escucha `uncaughtException` no es una buena idea. Es por esto por lo que se recomiendan varios procesos y supervisores; el bloqueo y el reinicio es a menudo la forma más fiable de recuperarse de un error.
-
-Tampoco se recomienda el uso de [dominios](https://nodejs.org/api/domain.html). Generalmente no soluciona el problema y es un módulo en desuso.
-
-## Cosas que hacer en el entorno / configuración
-
-Estas son algunas de las cosas que puede hacer en el entorno del sistema para mejorar el rendimiento de la aplicación:
-
-- [Establecer NODE_ENV en "production"](#establecer-node_env-en-production)
-- [Asegurarse de que la aplicación se reinicia automáticamente](#asegurarse-de-que-la-aplicación-se-reinicia-automáticamente)
-- [Ejecutar la aplicación en un clúster](#ejecutar-la-aplicación-en-un-clúster)
-- [Almacenar en la caché los resultados de la solicitud](#almacenar-en-la-caché-los-resultados-de-la-solicitud)
-- [Utilizar un equilibrador de carga](#utilizar-un-equilibrador-de-carga)
-- [Utilizar un proxy inverso](#utilizar-un-proxy-inverso)
-
-### Establecer NODE_ENV en "production"
-
-La variable de entorno NODE_ENV especifica el entorno en el que se ejecuta una aplicación (normalmente, desarrollo o producción). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-Si establece NODE_ENV en "production", Express:
-
-- Almacena en la caché las plantillas de vistas.
-- Almacena en la caché los archivos CSS generados en las extensiones CSS.
-- Genera menos mensajes de error detallados.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Tenga en cuenta que comprobar el valor de una variable de entorno supone una reducción de rendimiento, por lo que debe hacerse moderadamente.
-
-En el desarrollo, normalmente establece las variables de entorno en el shell interactivo, por ejemplo, utilizando `export` o su archivo `.bash_profile`. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). En la siguiente sección se proporcionan más detalles sobre el uso del sistema init en general, pero el establecimiento de NODE_ENV es tan importante (y fácil de hacer) para el rendimiento, que se resalta aquí.
-
-Con systemd, utilice la directiva `Environment` en el archivo unit. For example:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### Asegurarse de que la aplicación se reinicia automáticamente
-
-En la producción, no desea que la aplicación esté nunca fuera de línea. Esto significa que debe asegurarse de que se reinicia si la aplicación o el servidor se bloquean. Aunque espera que no se produzca ninguno de estos sucesos, si somos realistas, debe tener en cuenta ambas eventualidades de la siguiente manera:
-
-- Utilizando un gestor de procesos para reiniciar la aplicación (y Node) cuando se bloquea.
-- Utilizando el sistema init que proporciona su sistema operativo para reiniciar el gestor de procesos cuando se bloquea el sistema operativo. También puede utilizar el sistema init sin un gestor de procesos.
-
-Las aplicaciones Node se bloquean si encuentran una excepción no capturada. Lo primero que debe hacer es asegurarse de que se realizan las pruebas correctas en la aplicación y que se manejan todas las excepciones (consulte [Manejar correctamente las excepciones](#exceptions) para obtener detalles). No obstante, para estar libre de errores, aplique un mecanismo para garantizar que cuando se bloquee la aplicación, se reinicie automáticamente.
-
-#### Utilizar un gestor de procesos
-
-En el desarrollo, la aplicación se inicia simplemente desde la línea de mandatos con `node server.js` o algo similar. Pero hacer esto en la producción es sinónimo de desastre. Si la aplicación se bloquea, estará fuera de línea hasta que la reinicie. Para garantizar el reinicio de la aplicación si se bloquea, utilice un gestor de procesos. Un gestor de procesos es un "contenedor" de aplicaciones que facilita el despliegue, proporciona una alta disponibilidad y permite gestionar la aplicación en el tiempo de ejecución.
-
-Además de reiniciar la aplicación cuando se bloquea, un gestor de procesos permite:
-
-- Obtener información útil sobre el rendimiento en tiempo de ejecución y el consumo de recursos.
-- Modificar dinámicamente los valores para mejorar el rendimiento.
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### Utilizar un sistema init
-
-La siguiente capa de fiabilidad es garantizar que la aplicación se reinicie cuando se reinicie el servidor. Los sistemas pueden bloquearse por una amplia variedad de motivos. Para garantizar que la aplicación se reinicie si se bloquea el servidor, utilice el sistema init incorporado en su sistema operativo. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-Hay dos formas de utilizar los sistemas init con la aplicación Express:
-
-- Ejecutar la aplicación en un gestor de procesos e instalar el gestor de procesos como un servicio con el sistema init. El gestor de procesos reiniciará la aplicación cuando esta se bloquee y el sistema init reiniciará el gestor de procesos cuando se reinicie el sistema operativo. This is the recommended approach.
-- Ejecutar la aplicación (y Node) directamente con el sistema init. Esta opción parece más simple, pero no tiene las ventajas adicionales de utilizar el gestor de procesos.
-
-##### Systemd
-
-Systemd es un administrador de servicios y sistemas Linux. La mayoría de las principales distribuciones Linux han adoptado systemd como su sistema init predeterminado.
-
-Un archivo de configuración de servicio de systemd se denomina un _archivo unit_, con un nombre de archivo terminado en .service. A continuación, se muestra un archivo unit de ejemplo para gestionar directamente una aplicación Node (sustituya el texto en negrita por los valores de su sistema y su aplicación): Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Para obtener más información sobre systemd, consulte [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-### Ejecutar la aplicación en un clúster
-
-En un sistema multinúcleo, puede multiplicar el rendimiento de una aplicación Node iniciando un clúster de procesos. Un clúster ejecuta varias instancias de la aplicación, idealmente una instancia en cada núcleo de CPU, lo que permite distribuir la carga y las tareas entre las instancias.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANTE: como las instancias de aplicación se ejecutan como procesos independientes, no comparten el mismo espacio de memoria. Es decir, los objetos son locales para cada instancia de la aplicación. Por lo tanto, no puede mantener el estado en el código de aplicación. No obstante, puede utilizar un almacén de datos en memoria como [Redis](http://redis.io/) para almacenar los datos y los estados relacionados con la sesión. Esta advertencia se aplica básicamente a todas las formas de escalado horizontal, ya sean clústeres con varios procesos o varios servidores físicos.
-
-En las aplicaciones en clúster, los procesos de trabajador pueden bloquearse individualmente sin afectar al resto de los procesos. Aparte de las ventajas de rendimiento, el aislamiento de errores es otro motivo para ejecutar un clúster de procesos de aplicación. Siempre que se bloquee un proceso de trabajador, asegúrese de registrar el suceso y generar un nuevo proceso utilizando cluster.fork().
-
-#### Mediante el módulo de clúster de Node
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). Esto permite al proceso maestro generar procesos de trabajador y distribuir las conexiones entrantes entre los trabajadores.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### Almacenar en la caché los resultados de la solicitud
-
-Otra estrategia para mejorar el rendimiento en la producción es almacenar en la caché el resultado de las solicitudes, para que la aplicación no repita la operación de dar servicio a la misma solicitud repetidamente.
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### Utilizar un equilibrador de carga
-
-Independientemente de lo optimizada que esté una aplicación, una única instancia sólo puede manejar una cantidad limitada de carga y tráfico. Una forma de escalar una aplicación es ejecutar varias instancias de la misma y distribuir el tráfico utilizando un equilibrador de carga. La configuración de un equilibrador de carga puede mejorar el rendimiento y la velocidad de la aplicación, lo que permite escalarla más que con una única instancia.
-
-Un equilibrador de carga normalmente es un proxy inverso que orquesta el tráfico hacia y desde los servidores y las instancias de aplicación. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Con el equilibrio de carga, deberá asegurarse de que las solicitudes asociadas con un determinado ID de sesión se conecten al proceso que las ha originado. Esto se conoce como _afinidad de sesiones_ o _sesiones adhesivas_, y puede solucionarse con la recomendación anterior de utilizar un almacén de datos como, por ejemplo, Redis para los datos de sesión (dependiendo de la aplicación). Para obtener más información, consulte [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Utilizar un proxy inverso
-
-Un proxy inverso se coloca delante de una aplicación web y realiza operaciones de soporte en las solicitudes, aparte de dirigir las solicitudes a la aplicación. Puede manejar las páginas de errores, la compresión, el almacenamiento en memoria caché, el servicio de archivos y el equilibrio de carga, entre otros.
-
-La entrega de tareas que no necesitan saber el estado de la aplicación a un proxy inverso permite a Express realizar tareas de aplicación especializadas. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/es/advanced/best-practice-security.md b/es/advanced/best-practice-security.md
deleted file mode 100644
index 3aec0f1197..0000000000
--- a/es/advanced/best-practice-security.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-layout: page
-title: Mejores prácticas de seguridad para Express en producción
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# Production Best Practices: Security
-
-## Overview
-
-El término _"producción"_ hace referencia a la etapa del ciclo de vida del software donde una aplicación o una API tiene disponibilidad general para sus consumidores o usuarios finales. Por su parte, en la etapa de _"desarrollo"_, todavía estás escribiendo y probando activamente el código, y la aplicación no está abierta para el acceso externo. Los correspondientes entornos del sistema se conocen como los entornos de _producción_ y _desarrollo_, respectivamente.
-
-Los entornos de desarrollo y producción se configuran normalmente de forma diferente y tiene requisitos también muy diferentes. Lo que funciona en el desarrollo puede que no sea aceptable en la producción. Por ejemplo, en un entorno de desarrollo, puede que desee el registro detallado de errores a efecto de depuración, mientras que el mismo comportamiento puede suponer un problema de seguridad en un entorno de producción. De la misma forma, en el desarrollo, no es necesario preocuparse por la escalabilidad, la fiabilidad y el rendimiento, mientras que estos son clave en la producción.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-Security best practices for Express applications in production include:
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [Utilizar TLS](#utilizar-tls)
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [Utilizar Helmet](#utilizar-helmet)
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - [Utilizar cookies de forma segura](#utilizar-cookies-de-forma-segura)
-    - [noCache](https://github.com/helmetjs/nocache) establece cabeceras `Cache-Control` y Pragma para inhabilitar el almacenamiento en memoria caché del lado de cliente.
-    - [ieNoOpen](https://github.com/helmetjs/ienoopen) establece `X-Download-Options` para IE8+.
-  - [Prevenir ataques de fuerza bruta a la autenticación](#prevenir-ataques-de-fuerza-bruta-a-la-autenticación)
-  - [Asegurarse de que las dependencias sean seguras](#asegurarse-de-que-las-dependencias-sean-seguras)
-    - [Evitar otras vulnerabilidades conocidas](#evitar-otras-vulnerabilidades-conocidas)
-  - [Consideraciones adicionales](#consideraciones-adicionales)
-
-## No utilizar versiones en desuso o vulnerables de Express
-
-Express 2.x y 3.x ya no se mantienen. Los problemas de seguridad y rendimiento en estas versiones no se solucionarán. No las utilice. Si no ha cambiado todavía a la versión 4, siga la [guía de migración](/{{ page.lang }}/guide/migrating-4.html).
-
-Asimismo, asegúrese de que no está utilizando ninguna de las versiones vulnerables de Express que se listan en la [página Actualizaciones de seguridad](/{{ page.lang }}/advanced/security-updates.html). Si las utiliza, actualícese a uno de los releases estables, preferiblemente el más reciente.
-
-## Utilizar TLS
-
-Si la aplicación maneja o transmite datos confidenciales, utilice [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) para proteger la conexión y los datos. Esta tecnología cifra los datos antes de enviarlos desde el cliente al servidor, lo que evita algunos de los ataques de pirateo más comunes (y sencillos). Aunque las solicitudes Ajax y POST no sean obvias visiblemente y parezca que están "ocultas" en los navegadores, su tráfico de red es vulnerable para los [rastreos de paquetes](https://en.wikipedia.org/wiki/Packet_analyzer) y los [ataques de intermediarios](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-Es posible que esté familiarizado con el cifrado SSL (Secure Socket Layer). [TLS es simplemente el siguiente paso después de SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). Es decir, si antes utilizaba SSL, se recomienda actualizar a TLS. En general, se recomienda Nginx para manejar TLS. Encontrará una buena referencia para configurar TLS en Nginx (y otros servidores) en [la wiki de Mozilla Recommended Server Configurations](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-Asimismo, una herramienta muy útil para obtener un certificado de TLS gratis es [Let's Encrypt](https://letsencrypt.org/about/), una entidad emisora de certificados (CA) abierta, automatizada y gratuita proporcionada por [Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/).
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Utilizar Helmet
-
-[Helmet](https://www.npmjs.com/package/helmet) ayuda a proteger la aplicación de algunas vulnerabilidades web conocidas mediante el establecimiento correcto de cabeceras HTTP.
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-Instale Helmet como cualquier otro módulo:
-
-```bash
-$ npm install helmet
-```
-
-A continuación, utilícelo en el código:
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-Por lo tanto, se recomienda desactivar la cabecera con el método `app.disable()`:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Establecer las opciones de seguridad de las cookies
-
-Para garantizar que las cookies no abran la aplicación para ataques, no utilice el nombre de cookie de sesión predeterminado y establezca las opciones de seguridad de las cookies correctamente.
-
-Hay dos módulos de sesión de cookies de middleware principales:
-
-- [express-session](https://www.npmjs.com/package/express-session), que sustituye el middleware `express.session` incorporado en Express 3.x.
-- [cookie-session](https://www.npmjs.com/package/cookie-session), que sustituye el middleware `express.cookieSession` incorporado en Express 3.x.
-
-La principal diferencia entre los dos módulos es cómo guardan los datos de sesión de las cookies. El middleware [express-session](https://www.npmjs.com/package/express-session) almacena los datos de sesión en el servidor; sólo guarda el ID de sesión en la propia cookie, no los datos de sesión. De forma predeterminada, utiliza el almacenamiento en memoria y no está diseñado para un entorno de producción. En la producción, deberá configurar un almacenamiento de sesión escalable; consulte la lista de [almacenes de sesión compatibles](https://github.com/expressjs/session#compatible-session-stores).
-
-Por su parte, el middleware [cookie-session](https://www.npmjs.com/package/cookie-session) implementa un almacenamiento basado en cookies: serializa la sesión completa en la cookie, en lugar de sólo una clave de sesión. Utilícelo sólo cuando los datos de sesión sean relativamente pequeños y fácilmente codificables como valores primitivos (en lugar de objetos). Aunque se supone que los navegadores pueden dar soporte a 4096 bytes por cookie como mínimo, para no exceder el límite, no supere un tamaño de 4093 bytes por dominio. Asimismo, asegúrese de que los datos de la cookie estén visibles para el cliente, para que si se deben proteger u ocultar por cualquier motivo, se utilice mejor la opción express-session.
-
-### No utilizar el nombre de cookie de sesión predeterminado
-
-Si utiliza el nombre de cookie de sesión predeterminado, la aplicación puede quedar abierta a los ataques. El problema de seguridad que supone es similar a `X-Powered-By`: un posible atacante puede utilizarlo para firmar digitalmente el servidor y dirigir los ataques en consecuencia.
-
-Para evitar este problema, utilice nombres de cookie genéricos, por ejemplo, con el middleware [express-session](https://www.npmjs.com/package/express-session):
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Utilizar cookies de forma segura
-
-Establezca las siguientes opciones de cookies para mejorar la seguridad:
-
-- `secure` - Garantiza que el navegador sólo envíe la cookie a través de HTTPS.
-- `httpOnly` - Garantiza que la cookie sólo se envíe a través de HTTP(S), no a través de JavaScript de cliente, para la protección contra ataques de scripts entre sitios.
-- `domain` - Indica el dominio de la cookie; utilícelo para compararlo con el dominio del servidor donde se está solicitando el URL. Si coinciden, compruebe el atributo de vía de acceso a continuación.
-- `path` - Indica la vía de acceso de la cookie; utilícela para compararla con la vía de acceso de la solicitud. Si esta y el dominio coinciden, envíe la cookie en la solicitud.
-- `expires` - Se utiliza para establecer la fecha de caducidad de las cookies persistentes.
-
-A continuación, se muestra un ejemplo de uso del middleware [cookie-session](https://www.npmjs.com/package/cookie-session):
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevenir ataques de fuerza bruta a la autenticación
-
-Asegurate de que los puntos finales del inicio de sesión están protegidos para convertir los datos privados más seguros.
-
-Una simple y potente técnica es bloquear intentos de autorización usando dos métricas:
-
-1. Según el número de intentos fallidos consecutivos por el mismo nombre de usuario y dirección IP.
-2. Según el número fallido de intentos desde una dirección IP a lo largo de un cierto período de tiempo. Por ejemplo, bloquear una dirección IP si realiza 100 intentos fallidos en un día.
-
-El paquete [rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) ofrece herramientas para realizar esta técnica de forma fácil y rápida. Aquí puedes encontrar un [ejemplo de protección de fuerza bruta en la documentación](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection).
-
-## Asegurarse de que las dependencias sean seguras
-
-El uso de npm para gestionar las dependencias de la aplicación es muy útil y cómodo. No obstante, los paquetes que utiliza pueden contener vulnerabilidades de seguridad críticas que también pueden afectar a la aplicación. La seguridad de la aplicación sólo es tan fuerte como el "enlace más débil" de las dependencias.
-
-Since npm@6, npm automatically reviews every install request. También puedes utilizar 'npm audit' para analizar tu árbol de dependencias.
-
-```bash
-$ npm audit
-```
-
-Si quieres mantener más seguro, considera [Snyk](https://snyk.io/).
-
-Snyk ofrece tanto [herramienta de línea de comandos](https://www.npmjs.com/package/snyk) como una [integración de Github](https://snyk.io/docs/github) que comprueba tu aplicación contra [la base de datos de código abierto sobre vulnerabilidades de Snyk](https://snyk.io/vuln/) por cualquier vulnerabilidad conocida en tus dependencias. Instala la interfaz de línea de comandos:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Usa este comando para comprobar tu aplicación contra vulnerabilidades:
-
-```bash
-$ snyk test
-```
-
-### Avoid other known vulnerabilities
-
-Esté atento a las advertencias de [Node Security Project](https://npmjs.com/advisories) que puedan afectar a Express u otros módulos que utilice la aplicación. En general, Node Security Project es un excelente recurso de herramientas e información sobre la seguridad de Node.
-
-Por último, las aplicaciones de Express, como cualquier otra aplicación web, son vulnerables a una amplia variedad de ataques basados en web. Familiarícese con las [vulnerabilidades web](https://www.owasp.org/www-project-top-ten/) conocidas y tome precauciones para evitarlas.
-
-## Additional considerations
-
-A continuación, se muestran algunas recomendaciones para la excelente lista de comprobación [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Consulte el post de este blog para ver todos los detalles de estas recomendaciones:
-
-- Filtre y sanee siempre la entrada de usuario para protegerse contra los ataques de scripts entre sitios (XSS) e inyección de mandatos.
-- Defiéndase contra los ataques de inyección de SQL utilizando consultas parametrizadas o sentencias preparadas.
-- Utilice la herramienta [sqlmap](http://sqlmap.org/) de código abierto para detectar vulnerabilidades de inyección de SQL en la aplicación.
-- Utilice las herramientas [nmap](https://nmap.org/) y [sslyze](https://github.com/nabla-c0d3/sslyze) para probar la configuración de los cifrados SSL, las claves y la renegociación, así como la validez del certificado.
-- Utilice [safe-regex](https://www.npmjs.com/package/safe-regex) para asegurarse de que las expresiones regulares no sean susceptibles de ataques de [denegación de servicio de expresiones regulares](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
-
-[helmet]: <Si utiliza `helmet.js`, lo hace automáticamente.>
\ No newline at end of file
diff --git a/es/advanced/developing-template-engines.md b/es/advanced/developing-template-engines.md
deleted file mode 100644
index eb8f2ee917..0000000000
--- a/es/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Desarrollo de motores de plantilla para Express
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Desarrollo de motores de plantilla para Express
-
-Utilice el método `app.engine(ext, callback)` para crear su propio motor de plantilla. `ext` hace referencia a la extensión de archivo y `callback` es la función de motor de plantilla, que acepta los siguientes elementos como parámetros: la ubicación del archivo, el objeto options y la función callback.
-
-El siguiente código es un ejemplo de implementación de un motor de plantilla muy simple para la representación de archivos `.ntl`.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-La aplicación ahora podrá representar archivos `.ntl`. Cree un archivo denominado `index.ntl` en el directorio `views` con el siguiente contenido.
-
-```pug
-#title#
-#message#
-```
-
-A continuación, cree la ruta siguiente en la aplicación.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Cuando realice una solicitud a la página de inicio, `index.ntl` se representará como HTML.
\ No newline at end of file
diff --git a/es/advanced/healthcheck-graceful-shutdown.md b/es/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index a91cddada0..0000000000
--- a/es/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### <a name="redis"></a>
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/es/advanced/security-updates.md b/es/advanced/security-updates.md
deleted file mode 100644
index 5674fb92f6..0000000000
--- a/es/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Actualizaciones de seguridad de Express
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# Actualizaciones de seguridad
-
-<div class="doc-box doc-notice" markdown="1">
-Node.js vulnerabilities directly affect Express. Por lo tanto, [vigile las vulnerabilidades de Node.js](https://nodejs.org
-/en/blog/vulnerability/) y asegúrese de utilizar la versión estable más reciente de Node.js.
-</div>
-
-En la lista siguiente se muestran las vulnerabilidades de Express que se han solucionado en la actualización de versión especificada.
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - Se ha solucionado la vulnerabilidad de divulgación de vía de acceso raíz en `express.static`, `res.sendfile` y `res.sendFile`
-- 4.10.7
-  - Se ha solucionado la vulnerabilidad de Open Redirect en `express.static` ([anuncio](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 4.8.8
-  - Se han solucionado las vulnerabilidades de cruce de directorios en `express.static` ([anuncio](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-- 4.8.4
-  - Node.js 0.10 puede tener fugas de `fd` en determinadas situaciones que afectan a `express.static` y `res.sendfile`. Las solicitudes maliciosas pueden provocar la fuga de `fd` y, en última instancia, generar errores `EMFILE` y anular la capacidad de respuesta del servidor.
-- 4.8.0
-  - Las matrices dispersas que tienen índices extremadamente altos en la serie de consulta pueden hacer que el proceso se quede sin memoria y se bloquee el servidor.
-  - Los objetos de serie de consulta extremadamente anidados pueden hacer que se bloquee el proceso y anular la capacidad de respuesta del servidor temporalmente.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x YA NO SE MANTIENE**
-
-Los problemas de rendimiento y seguridad conocidos y desconocidos en 3.x no se han solucionado desde la última actualización (1 de agosto de 2015). Se recomienda especialmente utilizar la última versión de Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - Se ha solucionado la vulnerabilidad de divulgación de vía de acceso raíz en `express.static`, `res.sendfile` y `res.sendFile`
-- 3.19.0
-  - Se ha solucionado la vulnerabilidad de Open Redirect en `express.static` ([anuncio](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 3.16.10
-  - Se han solucionado las vulnerabilidades de cruce de directorios en `express.static`.
-- 3.16.6
-  - Node.js 0.10 puede tener fugas de `fd` en determinadas situaciones que afectan a `express.static` y `res.sendfile`. Las solicitudes maliciosas pueden provocar la fuga de `fd` y, en última instancia, generar errores `EMFILE` y anular la capacidad de respuesta del servidor.
-- 3.16.0
-  - Las matrices dispersas que tienen índices extremadamente altos en la serie de consulta pueden hacer que el proceso se quede sin memoria y se bloquee el servidor.
-  - Los objetos de serie de consulta extremadamente anidados pueden hacer que se bloquee el proceso y anular la capacidad de respuesta del servidor temporalmente.
-- 3.3.0
-  - La respuesta 404 de un intento de alteración temporal de método no soportado era susceptible de ataques de scripts entre sitios.
\ No newline at end of file
diff --git a/es/api.md b/es/api.md
deleted file mode 100644
index 6fe643ea9e..0000000000
--- a/es/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Referencia de API
-description: Acceda a la referencia de la API para Express.js detallando todos los módulos, métodos y propiedades para construir aplicaciones web con esta versión.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/es/changelog/index.md b/es/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/es/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/es/guide/behind-proxies.md b/es/guide/behind-proxies.md
deleted file mode 100644
index 365fdee6ee..0000000000
--- a/es/guide/behind-proxies.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: page
-title: Express detrás de proxies
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# Express detrás de proxies
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-The application setting `trust proxy` may be set to one of the values listed in the following table.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Type</th><th>Value</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Booleano</td>
-<td markdown="1">
-Si es `true`, la dirección IP del cliente se entiende como la entrada más a la izquierda en la cabecera `X-Forwarded-*`.
-
-Si es `false`, la aplicación se entiende como orientada directamente a Internet, y la dirección IP del cliente se obtiene de `req.connection.remoteAddress`. Este es el valor predeterminado.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-Puede establecer direcciones IP de varias formas:
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-Cuando se especifican, las direcciones IP o las subredes se excluyen del proceso de determinación de direcciones, y la dirección IP no de confianza más próxima al servidor de aplicaciones se establece como la dirección IP del cliente. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>Number</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">El valor de [req.hostname](/{{ page.lang }}/api.html#req.hostname) se obtiene del valor definido en la cabecera `X-Forwarded-Host`, que puede estar establecido por el cliente o el proxy.
-  </li>
-  <li markdown="1">El proxy inverso puede establecer `X-Forwarded-Proto` para indicar a la aplicación si es `https`, `http` o incluso un nombre no válido. [req.protocol](/{{ page.lang }}/api.html#req.protocol) refleja este valor.
-  </li>
-  <li markdown="1">Los valores [req.ip](/{{ page.lang }}/api.html#req.ip) y [req.ips](/{{ page.lang }}/api.html#req.ips) se rellenan con la lista de direcciones de `X-Forwarded-For`.
-  </li>
-</ul>
-
-El valor `trust proxy` se implementa utilizando el paquete [proxy-addr](https://www.npmjs.com/package/proxy-addr). For more information, see its documentation.
diff --git a/es/guide/database-integration.md b/es/guide/database-integration.md
deleted file mode 100644
index ece4daf098..0000000000
--- a/es/guide/database-integration.md
+++ /dev/null
@@ -1,513 +0,0 @@
----
-layout: page
-title: Integración de la base de datos de Express
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# Integración de la base de datos
-
-La adición de la funcionalidad de conectar bases de datos a las aplicaciones Express se consigue simplemente cargando el controlador de Node.js adecuado para la base de datos en la aplicación. En este documento se describe brevemente cómo añadir y utilizar algunos de los módulos de Node.js más conocidos para los sistemas de base de datos en la aplicación Express:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-Estos son algunos de los muchos controladores de base de datos que hay disponibles. Para ver otras opciones, realice búsquedas en el sitio [npm](https://www.npmjs.com/).
-</div>
-
-## Cassandra
-
-**Módulo**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install cassandra-driver
-```
-
-### <a name="redis"></a>
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install couchbase
-```
-
-### <a name="redis"></a>
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Módulo**: [nano](https://github.com/dscape/nano)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install nano
-```
-
-### <a name="redis"></a>
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Módulo**: [levelup](https://github.com/rvagg/node-levelup)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### <a name="redis"></a>
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Módulo**: [mysql](https://github.com/felixge/node-mysql/)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install mysql
-```
-
-### <a name="redis"></a>
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Módulo**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### <a name="cassandra"></a>
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-Si desea un controlador de modelo de objeto para MongoDB, consulte [Mongoose](https://github.com/LearnBoost/mongoose).
-
-## Neo4j
-
-<code class="language-javascript" translate="no">
-var apoc = require('apoc');apoc.query('match (n) return n').exec().then(
-function (response) {
-console.log(response);
-},
-function (fail) {
-console.log(fail);
-}
-); </code>
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install neo4j-driver
-```
-
-### <a name="redis"></a>
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Module**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### <a name="elasticsearch"></a>
-
-NOTA: [Vea los requisitos previos de instalación](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### <a name="redis"></a>
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Módulo**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install pg-promise
-```
-
-### <a name="redis"></a>
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Módulo**: [redis](https://github.com/mranney/node_redis)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install redis
-```
-
-### <a name="redis"></a>
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install tedious
-```
-
-### <a name="redis"></a>
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Módulo**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install sqlite3
-```
-
-### <a name="redis"></a>
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**Módulo**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-**Instalación**
-
-### <a name="elasticsearch"></a>
-
-```bash
-$ npm install elasticsearch
-```
-
-### <a name="redis"></a>
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/es/guide/debugging.md b/es/guide/debugging.md
deleted file mode 100644
index 3e67e963e9..0000000000
--- a/es/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: Depuración de Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Depuración de Express
-
-Para ver todos los registros internos utilizados en Express, establezca la variable de entorno `DEBUG` en `express:*` cuando inicie la aplicación.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-En Windows, utilice el mandato correspondiente.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-La ejecución de este mandato en la aplicación predeterminada generada por el [generador de Express](/{{ page.lang }}/starter/generator.html) imprime la siguiente salida:
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-Cuando se realiza una solicitud a la aplicación, verá los registros especificados en el código de Express:
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-Para ver sólo los registros de la implementación de direccionador, establezca el valor de `DEBUG` en `express:router`. De la misma forma, para ver sólo los registros de la implementación de aplicación, establezca el valor de `DEBUG` en `express:application`, etc.
-
-## Applications generated by `express`
-
-Una aplicación generada por el mandato `express` utiliza el módulo `debug`, y el ámbito de su espacio de nombres de depuración se establece en el nombre de la aplicación.
-
-Por ejemplo, si ha generado la aplicación con `$ express sample-app`, puede habilitar las sentencias de depuración con el siguiente mandato:
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-Puede especificar más de un espacio de nombres de depuración asignando una lista separada por comas de nombres:
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/es/guide/error-handling.md b/es/guide/error-handling.md
deleted file mode 100644
index df2451a690..0000000000
--- a/es/guide/error-handling.md
+++ /dev/null
@@ -1,284 +0,0 @@
----
-layout: page
-title: Manejo de errores de Express
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# Error Handling
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. For example:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-Defina las funciones de middleware de manejo de errores de la misma forma que otras funciones de middleware, excepto que las funciones de manejo de errores tienen cuatro argumentos en lugar de tres: `(err, req, res, next)`.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Si tiene un manejador de rutas con varias funciones de devolución de llamada, puede utilizar el parámetro `route` para omitir el siguiente manejador de rutas.
-For example:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-Si pasa cualquier valor a la función `next()` (excepto la serie `'route'`), Express considera que la solicitud actual tiene un error y omitirá las restantes funciones de middleware y direccionamiento que no son de manejo de errores.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. For example:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. For example:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## El manejador de errores predeterminado
-
-Express se suministra con un manejador de errores incorporado, que se encarga de los errores que aparecen en la aplicación. Esta función de middleware de manejo de errores predeterminada se añade al final de la pila de funciones de middleware.
-
-Si pasa un error a `next()` y no lo maneja en el manejador de errores, lo manejará el manejador de errores incorporado; el error se escribirá en el cliente con el seguimiento de la pila. El seguimiento de la pila no se incluye en el entorno de producción.
-
-<div class="doc-box doc-info" markdown="1">
-Establezca la variable de entorno `NODE_ENV` en `production`, para ejecutar la aplicación en modalidad de producción.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-Si invoca `next()` con un error después de haber empezado a escribir la respuesta (por ejemplo, si encuentra un error mientras se envía la respuesta en modalidad continua al cliente), el manejador de errores predeterminado de Express cierra la conexión y falla la solicitud.
-
-Por lo tanto, cuando añade un manejador de errores personalizado, se recomienda delegar en los mecanismos de manejo de errores predeterminados de Express, cuando las cabeceras ya se han enviado al cliente:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. For example:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-El middleware de manejo de errores se define al final, después de otras llamadas de rutas y `app.use()`; por ejemplo:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Las respuestas desde una función de middleware pueden estar en el formato que prefiera, por ejemplo, una página de errores HTML, un mensaje simple o una serie JSON.
-
-A efectos de la organización (y de infraestructura de nivel superior), puede definir varias funciones de middleware de manejo de errores, de la misma forma que con las funciones de middleware normales. Por ejemplo, si desea definir un manejador de errores para las solicitudes realizadas utilizando `XHR`, y las que no lo tienen, puede utilizar los siguientes mandatos:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-En este ejemplo, los `logErrors` genéricos pueden escribir información de solicitudes y errores en `stderr`, por ejemplo:
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-También en este ejemplo, `clientErrorHandler` se define de la siguiente manera; en este caso, el error se pasa de forma explícita al siguiente:
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-La función que detecta todos los errores de `errorHandler` puede implementarse de la siguiente manera:
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-En este ejemplo, se omitirá el manejador `getPaidContent`, pero los restantes manejadores en `app` para `/a_route_behind_paywall` continuarán ejecutándose.
-
-<div class="doc-box doc-info" markdown="1">
-Las llamadas a `next()` y `next(err)` indican que el manejador actual está completo y en qué estado.  `next(err)` omitirá los demás manejadores de la cadena, excepto los que se hayan configurado para manejar errores como se ha descrito anteriormente.
-</div>
diff --git a/es/guide/migrating-4.md b/es/guide/migrating-4.md
deleted file mode 100644
index da2d060819..0000000000
--- a/es/guide/migrating-4.md
+++ /dev/null
@@ -1,563 +0,0 @@
----
-layout: page
-title: Migración a Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Migración a Express 4
-
-<h2 id="overview">Overview</h2>
-
-Express 4 es un cambio que rompe el código existente de Express 3, etc. Esto implica que una aplicación Express 3 existente no funcionará si actualiza la versión de Express en sus dependencias.
-
-En este artículo se describen:
-
-<ul class="doclist">
-  <li><a href="#changes">Los cambios en Express 4.</a></li>
-  <li><a href="#example-migration">Un ejemplo</a> de migración de una aplicación Express 3 a Express 4.</li>
-  <li><a href="#app-gen">La actualización al generador de aplicaciones Express 4.</li>
-</ul>
-
-<h2 id="changes">Los cambios en Express 4</h2>
-
-Se han realizado varios cambios importantes en Express 4:
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Cambios en el sistema de direccionamiento.</a></li>
-  <li><a href="#other-changes">Otros cambios.</a></li>
-</ul>
-
-Vea también:
-
-- [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Cambios en el sistema principal y de middleware de Express
-</h3>
-
-Express 4 ya no depende de Connect y elimina todo el middleware incorporado de su núcleo, excepto la función `express.static`. Esto significa que ahora Express es una infraestructura web de middleware y direccionamiento independiente, y que los releases y las versiones de Express no se ven afectados por las actualizaciones de middleware.
-
-Sin el middleware incorporado, debe añadir explícitamente todo el
-middleware necesario para ejecutar la aplicación. Sólo tiene que seguir estos pasos:
-
-1. Instalar el módulo: `npm install --save <module-name>`
-2. En su aplicación, requerir el módulo: `require('module-name')`
-3. Utilizar el módulo según su documentación: `app.use( ... )`
-
-En la tabla siguiente se lista el middleware de Express 3 y su contrapartida en Express 4.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Esta es la [lista completa](https://github.com/senchalabs/connect#middleware) de middleware de Express 4.
-
-En la mayoría de los casos, sólo tiene que sustituir el middleware de la versión 3 antigua por su contrapartida de Express 4. Para obtener detalles, consulte la documentación del módulo en GitHub.
-
-<h4 id="app-use"><code>app.use</code> accepts parameters</h4>
-
-En la versión 4, puede utilizar un parámetro de variable para definir la vía de acceso donde se cargan las funciones de middleware y, a continuación, leer el valor del parámetro en el manejador de rutas.
-For example:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-El sistema de direccionamiento
-</h3>
-
-Ahora las aplicaciones cargan implícitamente el middleware de direccionamiento, por lo que ya no tiene que preocuparse del orden con el que se carga el middleware respecto al middleware de `router`.
-
-La forma en que define las rutas no varía, pero el sistema de direccionamiento tiene dos nuevas características que permiten organizar las rutas:
-
-{: .doclist }
-
-- Un nuevo método, `app.route()`, para crear manejadores de rutas encadenables para una vía de acceso de ruta.
-- Una nueva clase, `express.Router`, para crear manejadores de rutas montables modulares.
-
-<h4 id="app-route"><code>app.route()</code> method</h4>
-
-El nuevo método `app.route()` permite crear manejadores de rutas encadenables para una vía de acceso de ruta. Como la vía de acceso se especifica en una única ubicación, la creación de rutas modulares es muy útil, al igual que la reducción de redundancia y errores tipográficos. Para obtener más información sobre las rutas, consulte la [`documentación` de Router()](/{{ page.lang }}/4x/api.html#router).
-
-A continuación, se muestra un ejemplo de manejadores de rutas encadenados que se definen utilizando la función `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> class</h4>
-
-La otra característica que permite organizar las rutas es una nueva clase, `express.Router`, que puede utilizar para crear manejadores de rutas montables modulares. Una instancia `Router` es un sistema de middleware y direccionamiento completo; por este motivo, a menudo se conoce como una "miniaplicación".
-
-El siguiente ejemplo crea un direccionador como un módulo, carga el middleware en él, define algunas rutas y lo monta en una vía de acceso en la aplicación principal.
-
-Por ejemplo, cree un archivo de direccionador denominado `birds.js` en el directorio de la aplicación, con el siguiente contenido:
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-A continuación, cargue el módulo de direccionador en la aplicación:
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-La aplicación ahora podrá manejar solicitudes a las vías de acceso `/birds` y `/birds/about`, e invocará el middleware `timeLog` que es específico de la ruta.
-
-<h3 id="other-changes">
-Other changes
-</h3>
-
-En la tabla siguiente se muestran otros cambios pequeños pero importantes en Express 4:
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Object</th>
-<th>Description</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 requiere Node.js 0.10.x o posterior y deja de dar soporte a
-Node.js 0.8.x.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-The `http` module is no longer needed, unless you need to directly work with it (socket.io/SPDY/HTTPS). La aplicación puede iniciarse utilizando la función `app.listen()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-La función `app.configure()` se ha eliminado.  Utilice la función `process.env.NODE_ENV` o
-`app.get('env')` para detectar el entorno y configure la aplicación según corresponda.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-La propiedad de aplicación `json spaces` está inhabilitada de forma predeterminada en Express 4.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Utilice `req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()` y `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-Ya no resuelve los URL relativos.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Era una matriz, ahora es un objeto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Era una función, ahora es un objeto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-Se ha cambiado por `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Ahora está disponible como `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Se ha eliminado.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Se ha eliminado.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-La funcionalidad está ahora limitada a establecer el valor de cookie básico. Utilice `res.cookie()` para obtener la funcionalidad adicional.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">Migración de aplicación de ejemplo</h2>
-
-A continuación, se muestra un ejemplo de migración de una aplicación Express 3 a Express 4.
-The files of interest are `app.js` and `package.json`.
-
-<h3 id="">
-Aplicación versión 3
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Consider an Express v.3 application with the following `app.js` file:
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-El archivo `package.json` de la versión 3 correspondiente será similar al siguiente:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Proceso
-</h3>
-
-Para empezar el proceso de migración, instale el middleware necesario para la aplicación Express 4 y actualice Express y Pug a su versión respectiva más reciente con el siguiente mandato:
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Realice los cambios siguientes en `app.js`:
-
-1. Las funciones de middleware de Express incorporadas `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` y
-   `express.errorHandler` ya no están disponibles en el objeto `express`. Debe instalar sus alternativas manualmente y cargarlas en la aplicación.
-
-2. Ya no es necesario cargar la función `app.router`.
-   No es un objeto de aplicación Express 4 válido, por lo que debe eliminar el código `app.use(app.router);`.
-
-3. Asegúrese de que las funciones de middleware se cargan en el orden correcto: cargue `errorHandler` después de cargar las rutas de aplicación.
-
-<h3 id="">Aplicación versión 4</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-La ejecución del mandato `npm` anterior actualizará `package.json` de la siguiente manera:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-A continuación, elimine el código no válido, cargue el middleware necesario y realice otros cambios según sea necesario. El archivo `app.js` será parecido al siguiente:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-A menos que necesite trabajar directamente con el módulo `http` (socket.io/SPDY/HTTPS), no es necesario cargarlo y la aplicación puede iniciarse simplemente de la siguiente manera:
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Run the app</h3>
-
-El proceso de migración está completo y la aplicación es ahora una aplicación
-Express 4. Para confirmarlo, inicie la aplicación utilizando el siguiente mandato:
-
-```bash
-$ node .
-```
-
-Cargue [http://localhost:3000](http://localhost:3000) y vea la página de inicio que representa Express 4.
-
-<h2 id="app-gen">La actualización al generador de aplicaciones Express 4</h2>
-
-La herramienta de línea de mandatos para generar una aplicación Express continúa siendo `express`, pero para actualizar a la nueva versión, debe desinstalar el generador de aplicaciones Express 3 e instalar el nuevo `express-generator`.
-
-<h3 id="">Instalación </h3>
-
-Si ya ha instalado el generador de aplicaciones Express 3 en el sistema, debe desinstalarlo:
-
-```bash
-$ npm uninstall -g express
-```
-
-Dependiendo de cómo se configuren los privilegios de archivos y directorios, deberá ejecutar este mandato con `sudo`.
-
-A continuación, instale el nuevo generador:
-
-```bash
-$ npm install -g express-generator
-```
-
-Dependiendo de cómo se configuren los privilegios de archivos y directorios, deberá ejecutar este mandato con `sudo`.
-
-Ahora el mandato `express` en el sistema se actualiza al generador de Express 4.
-
-<h3 id="">Cambios en el generador de aplicaciones </h3>
-
-Las opciones de mandato y el uso continúan prácticamente iguales, con las siguientes excepciones:
-
-{: .doclist }
-
-- Removed the `--sessions` option.
-- Removed the `--jshtml` option.
-- Se ha añadido la opción `--hogan` para dar soporte a [Hogan.js](http://twitter.github.io/hogan.js/).
-
-<h3 id=""><a name="redis"></a></h3>
-
-Ejecute el siguiente mandato para crear una aplicación Express 4:
-
-```bash
-$ express app4
-```
-
-Si consulta el contenido del archivo `app4/app.js`, observará que todas las funciones de middleware (excepto `express.static`) que son necesarias para la aplicación se cargan como módulos independientes y que el middleware de `router` ya no se carga de forma explícita en la aplicación.
-
-También observará que el archivo `app.js` es ahora un módulo Node.js, a diferencia de la aplicación autónoma que generaba el antiguo generador.
-
-Después de instalar las dependencias, inicie la aplicación utilizando el siguiente mandato:
-
-```bash
-$ npm start
-```
-
-Si consulta el script de inicio npm en el archivo `package.json`, observará que el mandato que inicia la aplicación es `node ./bin/www`, que antes era `node app.js` en Express 3.
-
-Como el archivo `app.js` que generaba el generador de Express 4 ahora es un módulo Node.js, ya no puede iniciarse independientemente como una aplicación (a menos que modifique el código). El módulo debe cargarse en un archivo Node.js e iniciarse utilizando el archivo Node.js. El archivo Node.js es `./bin/www` en este caso.
-
-Ni el directorio `bin` ni el archivo `www`
-sin extensión son obligatorios para crear una aplicación Express o iniciar la aplicación. Son sólo sugerencias realizadas por el generador, por lo que puede modificarlos según sus necesidades.
-
-Para eliminar el directorio `www` y dejarlo todo como en "Express 3",
-suprima la línea `module.exports = app;` al final del archivo `app.js` y pegue el siguiente código en su lugar:
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Asegúrese de cargar el módulo `debug` encima del archivo `app.js` utilizando el código siguiente:
-
-```js
-var debug = require('debug')('app4')
-```
-
-A continuación, cambie `"start": "node ./bin/www"` en el archivo `package.json` por `"start": "node app.js"`.
-
-Ahora ha devuelto la funcionalidad de `./bin/www` a `app.js`. Este cambio no se recomienda, pero el ejercicio permite entender cómo funciona el archivo `./bin/www` y por qué el archivo `app.js` ya no se inicia solo.
diff --git a/es/guide/migrating-5.md b/es/guide/migrating-5.md
deleted file mode 100644
index 00ff676040..0000000000
--- a/es/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: Migración a Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Migración a Express 5
-
-<h2 id="overview">Overview</h2>
-
-Express 5 no es muy diferente de Express 4: los cambios en la API no son tan significativos como los de la migración de 3.0 a 4.0. Aunque la API básica permanece igual, continúa habiendo cambios que rompen el código existente; es decir, un programa de Express 4 existente no funcionará si lo actualiza para que utilice Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-A continuación, puede ejecutar las pruebas automatizadas para ver qué falla y solucionar los problemas según las actualizaciones siguientes. Después de solucionar los errores de las pruebas, ejecute la aplicación para ver qué errores se producen. Verá rápidamente si la aplicación utiliza métodos o propiedades que no están soportados.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Changes in Express 5</h2>
-
-**Métodos y propiedades eliminados**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Nombres de métodos pluralizados</a></li>
-  <li><a href="#leading">Dos puntos delanteros en el argumento de nombre en app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Mejoras**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**Modificados**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Removed methods and properties
-
-Si utiliza cualquiera de estos métodos o propiedades en la aplicación, se bloqueará. Por lo tanto, deberá cambiar la aplicación después de actualizar a la versión 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 ya no da soporte a la función `app.del()`. Si utiliza esta función, se genera un error. Para registrar las rutas HTTP DELETE, utilice la función `app.delete()` en su lugar.
-
-Inicialmente, se utilizaba `del` en lugar de `delete`, porque `delete` es una palabra clave reservada en JavaScript. No obstante, a partir de ECMAScript 6, `delete` y otras palabras clave reservadas pueden utilizarse correctamente como nombres de propiedad.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-La firma `app.param(fn)` se utilizaba para modificar el comportamiento de la función `app.param(name, fn)`. Está en desuso desde v4.11.0 y Express 5 ya no le da soporte.
-
-<h3 id="plural">Pluralized method names</h3>
-
-Los siguientes nombres de métodos se han pluralizado. En Express 4, el uso de los métodos antiguos daba como resultado un aviso de obsolescencia. Express 5 ya no les da soporte:
-
-`req.acceptsLanguage()` se ha sustituido por `req.acceptsLanguages()`.
-
-`req.acceptsCharset()` se ha sustituido por `req.acceptsCharsets()`.
-
-`req.acceptsEncoding()` se ha sustituido por `req.acceptsEncodings()`.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Dos puntos (:) delanteros en el nombre de app.param(name, fn)</h3>
-
-El carácter de dos puntos (:) delanteros en el nombre de la función `app.param(name, fn)` es un remanente de Express 3 y, a efectos de retrocompatibilidad, Express 4 le daba soporte con un aviso de obsolescencia. Express 5 lo ignorará de forma silenciosa y utilizará el parámetro de nombre sin añadir el prefijo de dos puntos.
-
-Esto no afectará al código si sigue la documentación de Express 4 de [app.param](/{{ page.lang }}/4x/api.html#app.param), ya que no hace ninguna referencia a los dos puntos delanteros.
-
-<h3 id="req.param">req.param(name)</h3>
-
-Este método potencialmente confuso y peligroso de recuperar datos de formulario se ha eliminado. No necesitará buscar específicamente el nombre de parámetro enviado en el objeto `req.params`, `req.body` o `req.query`.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 ya no da soporte a la firma `res.json(obj, status)`. En su lugar, establezca el estado y encadénelo al método `res.json()` de la siguiente manera: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 ya no da soporte a la firma `res.jsonp(obj, status)`. En su lugar, establezca el estado y encadénelo al método `res.jsonp()` de la siguiente manera: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 ya no da soporte a la firma `res.send(obj, status)`. En su lugar, establezca el estado y encadénelo al método `res.send()` de la siguiente manera: `res.status(status).send(obj)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 ya no da soporte a la firma <code>res.send(<em>status</em>)</code>, donde _`status`_ es un número. En su lugar, utilice la función `res.sendStatus(statusCode)`, que establece el código de estado de la cabecera de respuesta HTTP y envía la versión de texto del código: "Not Found", "Internal Server Error", etc.
-Si necesita enviar un número utilizando la función `res.send()`, escríbalo entre comillas para convertirlo en una serie, para que Express no lo interprete como un intento de utilizar la firma antigua no soportada.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-La función `res.sendfile()` se ha sustituido por una versión de la función `res.sendFile()` con cada palabra en mayúscula en Express 5.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Está en desuso desde v4.11.0 y Express 5 ya no le da soporte.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Modificados
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. For example:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-For example:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-El objeto `app.router`, que se ha eliminado en Express 4, ha vuelto en Express 5. En la nueva versión, este objeto es sólo una referencia al direccionador de Express base, a diferencia de en Express 3, donde una aplicación debía cargarlo explícitamente.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-En Express 4, la función `req.host` fragmentaba incorrectamente el número de puerto si estaba presente. In Express 5, the port number is maintained.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Improvements
-
-<h3 id="res.render">res.render()</h3>
-
-Este método ahora impone un comportamiento asíncrono para todos los motores de vistas, lo que evita los errores provocados por los motores de vistas que tenían una implementación síncrona e incumplían la interfaz recomendada.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/es/guide/overriding-express-api.md b/es/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/es/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/es/guide/routing.md b/es/guide/routing.md
deleted file mode 100644
index dd764c96fe..0000000000
--- a/es/guide/routing.md
+++ /dev/null
@@ -1,411 +0,0 @@
----
-layout: page
-title: Direccionamiento de Express
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# Direccionamiento
-
-_Direccionamiento_ hace referencia a la definición de puntos finales de aplicación (URI) y cómo responden a las solicitudes de cliente.
-Para ver una introducción al direccionamiento, consulte [Direccionamiento básico](/{{ page.lang }}/starter/basic-routing.html).
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-The following code is an example of a very basic route.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Route methods</h2>
-
-A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
-
-El siguiente código es un ejemplo de las rutas que se definen para los métodos GET y POST a la raíz de la aplicación.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-Hay un método de direccionamiento especial, `app.all()`, que no se deriva de ningún método HTTP. Este método se utiliza para cargar funciones de middleware en una vía de acceso para todos los métodos de solicitud. En el siguiente ejemplo, el manejador se ejecutará para las solicitudes a "/secret", tanto si utiliza GET, POST, PUT, DELETE, como cualquier otro método de solicitud HTTP soportado en el [módulo http](https://nodejs.org/api/http.html#http_http_methods).
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Vías de acceso de ruta</h2>
-
-Las vías de acceso de ruta, en combinación con un método de solicitud, definen los puntos finales en los que pueden realizarse las solicitudes. Las vías de acceso de ruta pueden ser series, patrones de serie o expresiones regulares.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) es una herramienta muy útil para probar rutas básicas de Express, aunque no da soporte a la coincidencia de patrones.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Route paths based on strings
-
-Esta vía de acceso de ruta coincidirá con las solicitudes a la ruta raíz, `/`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con las solicitudes a `/about`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con las solicitudes a `/random.text`.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Route paths based on string patterns
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-Esta vía de acceso de ruta coincidirá con `acd` y `abcd`.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con `abcd`, `abbcd`, `abbbcd`, etc.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con `abcd`, `abxcd`, `abRABDOMcd`, `ab123cd`, etc.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con `/abe` y `/abcde`.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Ejemplos de vías de acceso de ruta basadas en expresiones regulares:
-
-Esta vía de acceso de ruta coincidirá con cualquier valor con una "a" en el nombre de la ruta.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-Esta vía de acceso de ruta coincidirá con `butterfly` y `dragonfly`, pero no con `butterflyman`, `dragonfly man`, etc.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">Route parameters</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Route handlers</h2>
-
-Puede proporcionar varias funciones de devolución de llamada que se comportan como [middleware](/{{ page.lang }}/guide/using-middleware.html) para manejar una solicitud. La única excepción es que estas devoluciones de llamada pueden invocar `next('route')` para omitir el resto de las devoluciones de llamada de ruta. Puede utilizar este mecanismo para imponer condiciones previas en una ruta y, a continuación, pasar el control a las rutas posteriores si no hay motivo para continuar con la ruta actual.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Los manejadores de rutas pueden tener la forma de una función, una matriz de funciones o combinaciones de ambas, como se muestra en los siguientes ejemplos.
-
-Una función de devolución de llamada individual puede manejar una ruta. For example:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-Más de una función de devolución de llamada puede manejar una ruta (asegúrese de especificar el objeto `next`). For example:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-Una matriz de funciones de devolución de llamada puede manejar una ruta. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-Una combinación de funciones independientes y matrices de funciones puede manejar una ruta. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Response methods</h2>
-
-Los métodos en el objeto de respuesta (`res`) de la tabla siguiente pueden enviar una respuesta al cliente y terminar el ciclo de solicitud/respuestas. Si ninguno de estos métodos se invoca desde un manejador de rutas, la solicitud de cliente se dejará colgada.
-
-| Method                                                                                                                                                                                                                    | Description                                                                                                                   |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | Solicita un archivo para descargarlo.                                                                         |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | Finaliza el proceso de respuesta.                                                                             |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | Envía una respuesta JSON.                                                                                     |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | Send a JSON response with JSONP support.                                                                      |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | Redirecciona una solicitud.                                                                                   |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Representa una plantilla de vista.                                                                            |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | Envía una respuesta de varios tipos.                                                                          |
-| [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile)     | Envía un archivo como una secuencia de octetos.                                                               |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Establece el código de estado de la respuesta y envía su representación de serie como el cuerpo de respuesta. |
-
-<h2 id="app-route">app.route()</h2>
-
-Puede crear manejadores de rutas encadenables para una vía de acceso de ruta utilizando `app.route()`.
-Como la vía de acceso se especifica en una única ubicación, la creación de rutas modulares es muy útil, al igual que la reducción de redundancia y errores tipográficos. Para obtener más información sobre las rutas, consulte: [Documentación de Router()](/{{ page.lang }}/4x/api.html#router).
-
-A continuación, se muestra un ejemplo de manejadores de rutas encadenados que se definen utilizando `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Utilice la clase `express.Router` para crear manejadores de rutas montables y modulares. Una instancia `Router` es un sistema de middleware y direccionamiento completo; por este motivo, a menudo se conoce como una "miniaplicación".
-
-El siguiente ejemplo crea un direccionador como un módulo, carga una función de middleware en él, define algunas rutas y monta el módulo de direccionador en una vía de acceso en la aplicación principal.
-
-Cree un archivo de direccionador denominado `birds.js` en el directorio de la aplicación, con el siguiente contenido:
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-A continuación, cargue el módulo de direccionador en la aplicación:
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-La aplicación ahora podrá manejar solicitudes a `/birds` y `/birds/about`, así como invocar la función de middleware `timeLog` que es específica de la ruta.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/es/guide/using-middleware.md b/es/guide/using-middleware.md
deleted file mode 100644
index f4fcc65c67..0000000000
--- a/es/guide/using-middleware.md
+++ /dev/null
@@ -1,276 +0,0 @@
----
-layout: page
-title: Utilización del middleware de Express
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# Utilización del middleware
-
-Express es una infraestructura web de direccionamiento y middleware que tiene una funcionalidad mínima propia: una aplicación Express es fundamentalmente una serie de llamadas a funciones de middleware.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
-
-Las funciones de middleware pueden realizar las siguientes tareas:
-
-- Execute any code.
-- Realizar cambios en la solicitud y los objetos de respuesta.
-- Finalizar el ciclo de solicitud/respuestas.
-- Invocar la siguiente función de middleware en la pila.
-
-Si la función de middleware actual no finaliza el ciclo de solicitud/respuestas, debe invocar `next()` para pasar el control a la siguiente función de middleware. Otherwise, the request will be left hanging.
-
-An Express application can use the following types of middleware:
-
-- [Application-level middleware](#middleware.application)
-- [Middleware de nivel de direccionador](#middleware.router)
-- [Error-handling middleware](#middleware.error-handling)
-- [Built-in middleware](#middleware.built-in)
-- [Third-party middleware](#middleware.third-party)
-
-Puede cargar middleware de nivel de aplicación y de nivel de direccionador con una vía de acceso de montaje opcional.
-También puede cargar una serie de funciones de middleware a la vez, lo que crea una subpila del sistema de middleware en un punto de montaje.
-
-<h2 id='middleware.application'>Application-level middleware</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-Este ejemplo muestra una función de middleware sin ninguna vía de acceso de montaje. The function is executed every time the app receives a request.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-Este ejemplo muestra una función de middleware montada en la vía de acceso `/user/:id`. La función se ejecuta para cualquier tipo de solicitud HTTP en la vía de acceso `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Este ejemplo muestra una ruta y su función de manejador (sistema de middleware). La función maneja las solicitudes GET a la vía de acceso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-A continuación, se muestra un ejemplo de carga de una serie de funciones de middleware en un punto de montaje, con una vía de acceso de montaje.
-Ilustra una subpila de middleware que imprime información de solicitud para cualquier tipo de solicitud HTTP en la vía de acceso `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Los manejadores de rutas permiten definir varias rutas para una vía de acceso. El ejemplo siguiente define dos rutas para las solicitudes GET a la vía de acceso `/user/:id`. La segunda ruta no dará ningún problema, pero nunca se invocará, ya que la primera ruta finaliza el ciclo de solicitud/respuestas.
-
-Este ejemplo muestra una subpila de middleware que maneja solicitudes GET a la vía de acceso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-Para omitir el resto de las funciones de middleware de una pila de middleware de direccionador, invoque `next('route')` para pasar el control a la siguiente ruta.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-Este ejemplo muestra una subpila de middleware que maneja solicitudes GET a la vía de acceso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-A continuación, se muestra un ejemplo de uso de la función de middleware `express.static` con un objeto de opciones elaboradas:
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Middleware de nivel de direccionador</h2>
-
-El middleware de nivel de direccionador funciona de la misma manera que el middleware de nivel de aplicación, excepto que está enlazado a una instancia de `express.Router()`.
-
-```js
-const router = express.Router()
-```
-
-Cargue el middleware de nivel de direccionador utilizando las funciones `router.use()` y `router.METHOD()`.
-
-El siguiente código de ejemplo replica el sistema de middleware que se ha mostrado anteriormente para el middleware de nivel de aplicación, utilizando el middleware de nivel de direccionador:
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-Para obtener más detalles sobre la función `serve-static` y sus opciones, consulte la documentación de [serve-static](https://github.com/expressjs/serve-static).
-
-Este ejemplo muestra una subpila de middleware que maneja solicitudes GET a la vía de acceso `/user/:id`.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Error-handling middleware</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-El middleware de manejo de errores siempre utiliza *cuatro* argumentos. Debe proporcionar cuatro argumentos para identificarlo como una función de middleware de manejo de errores. Aunque no necesite utilizar el objeto `next`, debe especificarlo para mantener la firma. De lo contrario, el objeto `next` se interpretará como middleware normal y no podrá manejar errores.
-</div>
-
-Defina las funciones de middleware de manejo de errores de la misma forma que otras funciones de middleware, excepto con cuatro argumentos en lugar de tres, específicamente con la firma `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Para obtener detalles sobre el middleware de manejo de errores, consulte: [Manejo de errores](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Built-in middleware</h2>
-
-Desde la versión 4.x, Express ya no depende de [Connect](https://github.com/senchalabs/connect). Excepto `express.static`, todas las funciones de middleware que se incluían previamente con Express están ahora en módulos diferentes. Consulte [la lista de funciones de middleware](https://github.com/senchalabs/connect#middleware).
-
-La única función de middleware incorporado en Express es `express.static`.
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Third-party middleware</h2>
-
-Utilice el middleware de terceros para añadir funcionalidad a las aplicaciones Express.
-
-Instale el módulo Node.js para la funcionalidad necesaria y cárguelo en la aplicación a nivel de aplicación o a nivel de direccionador.
-
-El siguiente ejemplo ilustra la instalación y carga de la función de middleware de análisis de cookies `cookie-parser`.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Para ver una lista parcial de las funciones de middleware de terceros que más se utilizan con Express, consulte: [Middleware de terceros](../resources/middleware.html).
diff --git a/es/guide/using-template-engines.md b/es/guide/using-template-engines.md
deleted file mode 100644
index c88b786ff6..0000000000
--- a/es/guide/using-template-engines.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Utilización de motores de plantilla con Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Utilización de motores de plantilla con Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, el directorio donde se encuentran los archivos de plantilla. Ejemplo: `app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, el motor de plantilla que se utiliza. Ejemplo: `app.set('view engine', 'pug')`
-
-A continuación, instale el paquete npm de motor de plantilla correspondiente:
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
-which `res.render()` calls to render the template code.
-
-Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
-library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
-
-</div>
-
-After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
-Express loads the module internally, for example:
-
-```js
-app.set('view engine', 'pug')
-```
-
-Cree un archivo de plantilla Pug denominado `index.pug` en el directorio `views`, con el siguiente contenido:
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-A continuación, cree una ruta para representar el archivo `index.pug`. Si la propiedad `view engine` no se establece, debe especificar la extensión del archivo `view`. De lo contrario, puede omitirla.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Cuando realice una solicitud a la página de inicio, el archivo `index.pug` se representará como HTML.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/es/guide/writing-middleware.md b/es/guide/writing-middleware.md
deleted file mode 100644
index 93a6260428..0000000000
--- a/es/guide/writing-middleware.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: Escritura de middleware para su uso en aplicaciones Express
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Escritura de middleware para su uso en aplicaciones Express
-
-<h2>Overview</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
-
-Las funciones de middleware pueden realizar las siguientes tareas:
-
-- Execute any code.
-- Realizar cambios en la solicitud y los objetos de respuesta.
-- Finalizar el ciclo de solicitud/respuestas.
-- Invocar el siguiente middleware en la pila.
-
-Si la función de middleware actual no finaliza el ciclo de solicitud/respuestas, debe invocar `next()` para pasar el control a la siguiente función de middleware. Otherwise, the request will be left hanging.
-
-El siguiente ejemplo muestra los elementos de una llamada a función de middleware:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">Método HTTP para el que se aplica la función de middleware.</div></tbody>
-
-<div class="callout" id="callout2">Vía de acceso (ruta) para la que se aplica la función de middleware.</div>
-
-<div class="callout" id="callout3">La función de middleware.</div>
-
-<div class="callout" id="callout4">Argumento de devolución de llamada a la función de middleware, denominado "next" por convención.</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2><a name="redis"></a></h2>
-
-A continuación, se muestra un ejemplo de una aplicación Express simple, "Hello World", para la que definirá dos funciones de middleware:
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Este es un ejemplo simple de una función de middleware denominada "myLogger". Esta función simplemente imprime "LOGGED" cuando una solicitud de la aplicación pasa por ella. La función de middleware se asigna a una variable denominada `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Observe la llamada anterior a `next()`. La llamada a esta función invoca la siguiente función de middleware en la aplicación.
-La función `next()` no forma parte de la API de Express o Node.js, pero es el tercer argumento que se pasa a la función de middleware. La función `next()` puede tener cualquier nombre, pero por convención siempre se denomina "next".
-Para evitar confusiones, utilice siempre esta convención.
-</div>
-
-Para cargar la función de middleware, llame a `app.use()`, especificando la función de middleware.
-Por ejemplo, el siguiente código carga la función de middleware `myLogger` antes de la ruta a la vía de acceso raíz (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Every time the app receives a request, it prints the message "LOGGED" to the terminal.
-
-El orden de carga del middleware es importante: las funciones de middleware que se cargan primero también se ejecutan primero.
-
-Si `myLogger` se carga después de la ruta a la vía de acceso raíz, la solicitud nunca la alcanza y la aplicación no imprime "LOGGED", ya que el manejador de rutas de la vía de acceso raíz determina el ciclo de solicitud/respuestas.
-
-La función de middleware `myLogger` simplemente imprime un mensaje y, a continuación, pasa la solicitud a la siguiente función de middleware de la pila llamando a la función `next()`.
-
-<h3>Middleware function requestTime</h3>
-
-El siguiente ejemplo añade una propiedad denominada `requestTime` al objeto de solicitud. Llamaremos a esta función de middleware "requestTime".
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-The app now uses the `requestTime` middleware function. Asimismo, la función de devolución de llamada de la ruta de vía de acceso raíz utiliza la propiedad que la función de middleware añade a `req` (el objeto de solicitud).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-Cuando realiza una solicitud a la raíz de la aplicación, la aplicación ahora muestra la indicación de fecha y hora de la solicitud en el navegador.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Como tiene acceso al objeto de solicitud, el objeto de respuesta, la siguiente función de middleware de la pila y toda la API de Node.js, las posibilidades con las funciones de middleware son ilimitadas.
-
-Para obtener más información sobre el middleware de Express, consulte: [Utilización del middleware de Express](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/es/index.md b/es/index.md
deleted file mode 100644
index f5910e241c..0000000000
--- a/es/index.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-layout: home
-title: Express - Node.js Marco de aplicación web
-description: "Express es un marco web rápido, sin opinión y minimalista para Node.js, que proporciona un robusto conjunto de características para aplicaciones web y móviles."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Marco web rápido, sin opinión y minimalista para <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Aplicaciones web</h2> Express es un minimalista y flexible framework de aplicaciones web de Node.js que provee un conjunto robusto de características para aplicaciones web y móviles</div>
-    <div id="apis">
-      <h2>APIs</h2> Con una gran cantidad de métodos de utilidad HTTP y middleware a tu disposición, crear una API robusta es rápido y fácil.
-    </div>
-    <div id="performance">
-      <h2>Rendimiento</h2> Express proporciona una capa delgada de características fundamentales de la aplicación web, sin ocultar las características de Node.js que usted conoce y ama.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express es un marco de enrutamiento ligero y flexible con las características básicas mínimas 
-      destinado a aumentarse mediante el uso de  módulos <a href="{{ page.lang }}/resources/middleware.html">middleware</a>.
-    </div>
-  </div>
-</section>
diff --git a/es/resources/community.md b/es/resources/community.md
deleted file mode 100644
index 8e753b8c70..0000000000
--- a/es/resources/community.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-layout: page
-title: Comunidad de Express
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# Comunidad
-
-## Technical committee
-
-El comité técnico de Express se reúne en línea cada dos semanas (según sea necesario) para discutir el desarrollo y el mantenimiento de Express, entre otros problemas relevantes para el proyecto Express. Cada reunión se anuncia normalmente en un [problema de expressjs/discussions](https://github.com/expressjs/discussions/issues) con un enlace para unirse o ver la reunión, que está abierta a todos los observadores.
-
-Las reuniones son grabadas; para ver la lista de las grabaciones, consulte el [canal de YouTube de Express.js](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Los miembros del comité técnico de Express son:
-
-**Activos:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactivos:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-Nuestra vibrante comunidad ha creado una larga variedad de extensiones, [módulos intermedios](/{{ page.lang }}/resources/middleware.html) y frameworks de nivel superior.
-
-Además, la comunidad de Express mantiene módulos en estas dos organizaciones de GitHub:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-Para mantenerse al tanto de lo que está sucediendo en toda la comunidad, consulte [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Issues
-
-Si ha encontrado lo que cree que es un error, o simplemente quiere hacer una solicitud de función, abre un ticket en la [cola de problemas](https://github.com/expressjs/express/issues).
-
-## Examples
-
-Mire docenas de [ejemplos](https://github.com/expressjs/express/tree/master/examples) de aplicaciones Express en el repositorio que cubren todo, desde el diseño y la autenticación de API hasta la integración del motor de plantillas.
-
-## Discusiones de Github
-
-La sección de [Discusiones de GitHub](https://github.com/expressjs/discussions) es un excelente espacio para participar en conversaciones sobre el desarrollo y mantenimiento de Express, así como para compartir ideas y debatir temas relacionados con su uso.
-
-# Branding of Express.js
-
-## Logo de Express.js
-
-Express is a project of the OpenJS Foundation. Por favor, revise la [política de marcas registradas](https://trademark-policy.openjsf.org/) para obtener información sobre el uso permitido de los logotipos y marcas de Express.js.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logo de Marca</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/es/resources/contributing.md b/es/resources/contributing.md
deleted file mode 100644
index dbcd71524d..0000000000
--- a/es/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contribuir a Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contribuir a Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/es/resources/glossary.md b/es/resources/glossary.md
deleted file mode 100644
index ece172a295..0000000000
--- a/es/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Glosario de Express
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# Glosario
-
-### application
-
-En general, uno o varios programas diseñados para realizar operaciones para un determinado propósito.  En el contexto de Express, un programa que utiliza la API de Express que se ejecuta en la plataforma Node.js.  También puede hacer referencia a un [objeto de aplicación](/{{ page.lang }}/api.html#express).
-
-### API
-
-Application programming interface. Explique la abreviatura la primera vez que la utilice.
-
-### Express
-
-Una infraestructura web rápida, minimalista y flexible para las aplicaciones Node.js. En general, se prefiere "Express" a "Express.js", aunque esta también se acepta.
-
-### libuv
-
-Una biblioteca de soporte multiplataforma que se centra en la E/S asíncrona, desarrollada principalmente para su uso en Node.js.
-
-### middleware
-
-Una función invocada por la capa de direccionamiento de Express antes del manejador de la última solicitud, por lo que se sitúa en medio de una solicitud sin formato y la última ruta prevista. Algunos puntos delicados de terminología relacionados con el middleware:
-
-- `var foo = require('middleware')` significa que _requiere_ o _utiliza_ un módulo Node.js. A continuación, la sentencia `var mw = foo()` normalmente devuelve el middleware.
-- `app.use(mw)` significa que _se añade el middleware a la pila de procesos global_.
-- `app.get('/foo', mw, function (req, res) { ... })` significa que _se añade el middleware a la pila de procesos "GET /foo"_.
-
-### Node.js
-
-Una plataforma de software que se utiliza para crear aplicaciones de red escalables. Node.js utiliza JavaScript como lenguaje de script y consigue un elevado rendimiento mediante E/S sin bloqueo y un bucle de sucesos de una sola hebra. Consulte [nodejs.org](http://nodejs.org/). **Nota de uso**: inicialmente, "Node.js", posteriormente "Node".
-
-### Consulte [Open source software en la Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### request
-
-Una solicitud HTTP. Un cliente envía un mensaje de solicitud HTTP a un servidor, que devuelve una respuesta.  La solicitud debe utilizar uno de los [métodos de solicitud](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) como, por ejemplo, GET, POST, etc.
-
-### response
-
-An HTTP response. A server returns an HTTP response message to the client. La respuesta contiene información de estado de finalización sobre la solicitud y también puede contener contenido de la solicitud en el cuerpo del mensaje.
-
-### route
-
-Parte de un URL que identifica un recurso. For example, in `http://foo.com/products/id`, "/products/id" is the route.
-
-### router
-
-Consulte [direccionador](/{{ page.lang }}/4x/api.html#router) en la referencia de API.
diff --git a/es/resources/middleware.md b/es/resources/middleware.md
deleted file mode 100644
index 037474b9f6..0000000000
--- a/es/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Middleware de Express
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Middleware de Express
-
-Estos son algunos módulos de middleware de Express:
-
-| Módulo Middleware                                                           | Description                                                                                                                         |
-| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                                             |
-
-## Para ver más módulo de middleware, consulte:
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Módulo Middleware                                   | Description                                                                                                                                                                                   |
-| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet)        | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport) | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/es/resources/middleware/body-parser.md b/es/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/es/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/es/resources/middleware/compression.md b/es/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/es/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/es/resources/middleware/connect-rid.md b/es/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/es/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/es/resources/middleware/cookie-parser.md b/es/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/es/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/es/resources/middleware/cookie-session.md b/es/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/es/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/es/resources/middleware/cors.md b/es/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/es/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/es/resources/middleware/errorhandler.md b/es/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/es/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/es/resources/middleware/method-override.md b/es/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/es/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/es/resources/middleware/morgan.md b/es/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/es/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/es/resources/middleware/multer.md b/es/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/es/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/es/resources/middleware/response-time.md b/es/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/es/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/es/resources/middleware/serve-favicon.md b/es/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/es/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/es/resources/middleware/serve-index.md b/es/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/es/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/es/resources/middleware/serve-static.md b/es/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/es/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/es/resources/middleware/session.md b/es/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/es/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/es/resources/middleware/timeout.md b/es/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/es/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/es/resources/middleware/vhost.md b/es/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/es/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/es/resources/utils.md b/es/resources/utils.md
deleted file mode 100644
index 4c1a17b886..0000000000
--- a/es/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | Description                                                                                                                                                                                                                |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/es/starter/basic-routing.md b/es/starter/basic-routing.md
deleted file mode 100644
index 39b31fcb0f..0000000000
--- a/es/starter/basic-routing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: Direccionamiento básico de Express
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# Direccionamiento básico
-
-El _direccionamiento_ hace referencia a la determinación de cómo responde una aplicación a una solicitud de cliente en un determinado punto final, que es un URI (o una vía de acceso) y un método de solicitud HTTP específico (GET, POST, etc.).
-
-Cada ruta puede tener una o varias funciones de manejador, que se excluyen cuando se correlaciona la ruta.
-
-Route definition takes the following structure:
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Donde:
-
-- `app` es una instancia de `express`.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` es una vía de acceso en el servidor.
-- `HANDLER` es la función que se ejecuta cuando se correlaciona la ruta.
-
-<div class="doc-box doc-notice" markdown="1">
-En esta guía de aprendizaje se supone que se crea una instancia de `express` denominada `app` y que el servidor está en ejecución. Si no está familiarizado con la creación y el inicio de una aplicación, consulte el [Ejemplo Hello world](/{{ page.lang }}/starter/hello-world.html).
-</div>
-
-El siguiente ejemplo ilustra la definición de rutas simples.
-
-Responda con `Hello World!` en la página inicial:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Responda a una solicitud PUT en la ruta `/user`:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Responda a una solicitud DELETE en la ruta `/user`:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-Para obtener más detalles sobre el direccionamiento, consulte la [guía de direccionamiento](/{{ page.lang }}/guide/routing.html).
-
diff --git a/es/starter/examples.md b/es/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/es/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/es/starter/faq.md b/es/starter/faq.md
deleted file mode 100644
index c89471f4b2..0000000000
--- a/es/starter/faq.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-layout: page
-title: Preguntas más frecuentes sobre Express
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# Preguntas más frecuentes
-
-## How should I structure my application?
-
-There is no definitive answer to this question. La respuesta depende de la escala de la aplicación y del equipo implicado. Para ser lo más flexible posible, Express no realiza suposiciones en cuanto a la estructura.
-
-Las rutas y otra lógica específica de la aplicación puede residir en tantos archivos como desee, con la estructura de directorios que prefiera. Vea los siguientes ejemplos como inspiración:
-
-- [Listas de rutas](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Correlación de rutas](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [Controladores de estilo MVC](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Asimismo, hay extensiones de terceros para Express, que simplifican algunos de estos patrones:
-
-- [express-resource](https://github.com/expressjs/express-resource)
-
-## ¿Cómo debo definir los modelos?
-
-Express no tiene ninguna noción de base de datos. Este concepto se deja para los módulos de Node de terceros, lo que permite interactuar con prácticamente cualquier base de datos.
-
-Consulte [LoopBack](http://loopback.io) para ver una infraestructura basada en Express centrada en modelos.
-
-## ¿Cómo puedo autenticar los usuarios?
-
-La autenticación es otra área rígida en la que no entra Express. Puede utilizar el esquema de autenticación que desee.
-Para ver un esquema simple de nombre de usuario/contraseña, consulte [este ejemplo](https://github.com/expressjs/express/tree/master/examples/auth).
-
-## ¿A qué motor de plantilla da soporte Express?
-
-Express da soporte a cualquier motor de plantilla que cumpla la firma `(path, locals, callback)`.
-Para normalizar las interfaces de motor de plantilla y el almacenamiento en memoria caché, consulte el proyecto [consolidate.js](https://github.com/visionmedia/consolidate.js) para ver el soporte. Otros motores de plantilla que no aparezcan en la lista también pueden dar soporte a la firma de Express.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## How do I handle 404 responses?
-
-En Express, las respuestas 404 no son el resultado de un error, por lo que el middleware de manejador de errores no las capturará. Este comportamiento se debe a que una respuesta 404 simplemente indica la ausencia de trabajo adicional pendiente; es decir, Express ha ejecutado todas las rutas y funciones de middleware, y ha comprobado que ninguna de ellas responde. Lo único que debe hacer es añadir una función de middleware al final de la pila (debajo de las demás funciones) para manejar una respuesta 404:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## ¿Cómo configuro un manejador de errores?
-
-El middleware de manejo de errores se define de la misma forma que otro middleware, excepto con cuatro argumentos en lugar de tres; específicamente con la firma `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Para obtener más información, consulte [Manejo de errores](/{{ page.lang }}/guide/error-handling.html).
-
-## ¿Cómo represento el HTML sin formato?
-
-De ninguna manera. No es necesario "representar" HTML con la función `res.render()`.
-Si tiene un archivo específico, utilice la función `res.sendFile()`.
-Para el servicio de muchos activos desde un directorio, utilice la función de middleware `express.static()`.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/es/starter/generator.md b/es/starter/generator.md
deleted file mode 100644
index b33f2ae808..0000000000
--- a/es/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Generador de aplicaciones Express
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Generador de aplicaciones Express
-
-Utilice la herramienta de generador de aplicaciones, `express`, para crear rápidamente un esqueleto de aplicación.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Muestre las opciones de mandato con la opción `-h`:
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-Por ejemplo, el código siguiente crea una aplicación Express denominada _myapp_. La aplicación será creada en una carpeta llamada _myapp_ en el directorio de trabajo actual y el motor de vistas será asignado a <a href="https://pugjs.org/" target="_blank" title="Documentación de Pug">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-A continuación, instale las dependencias:
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-En MacOS o Linux, ejecute la aplicación con este mandato:
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-En Windows, utilice este mandato:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-A continuación, cargue `http://localhost:3000/` en el navegador para acceder a la aplicación.
-
-The generated app has the following directory structure:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-La estructura de la aplicación creada por el generador es sólo una de las muchas formas de estructurar las aplicaciones Express. Puede utilizar esta estructura o modificarla según sus necesidades.
-</div>
\ No newline at end of file
diff --git a/es/starter/hello-world.md b/es/starter/hello-world.md
deleted file mode 100644
index 053cd78b5b..0000000000
--- a/es/starter/hello-world.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-layout: page
-title: Ejemplo "Hello World" de Express
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Ejemplo Hello world
-
-<div class="doc-box doc-info" markdown="1">
-Esta es básicamente la aplicación Express más sencilla que puede crear. Es una aplicación de archivo simple &mdash; *no* lo que obtendrá si utiliza el [generador de Express](/{{ page.lang }}/starter/generator.html), que crea el andamiaje para una aplicación completa con varios archivos JavaScript, plantillas Jade y subdirectorios para distintos propósitos.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-La aplicación inicia un servidor y escucha las conexiones en el puerto 3000. La aplicación responde con "Hello World!" para las solicitudes al URL raíz (`/`) o a la _ruta_ raíz. Para cada vía de acceso diferente, responderá con un error **404 Not Found**.
-
-### Ejecutando localmente
-
-En primer lugar, cree un directorio denominado `myapp`, cámbielo y ejecute `npm init`. A continuación, instale `express` como una dependencia, según se describe en la [guía de instalación](/{{ page.lang }}/starter/installing.html).
-
-En el directorio `myapp`, cree un archivo denominado `app.js` y añada el código siguiente:
-
-<div class="doc-box doc-notice" markdown="1">
-`req` (solicitud) y `res` (respuesta) son exactamente los mismos objetos que proporciona Node, por lo que puede invocar `req.pipe()`, `req.on('data', callback)` y cualquier otro objeto que invocaría sin estar Express implicado.
-</div>
-
-Ejecute la aplicación con el siguiente mandato:
-
-```bash
-$ node app.js
-```
-
-A continuación, cargue [http://localhost:3000/](http://localhost:3000/) en un navegador para ver la salida.
\ No newline at end of file
diff --git a/es/starter/installing.md b/es/starter/installing.md
deleted file mode 100644
index e4b98996d6..0000000000
--- a/es/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Instalación de Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# Instalación
-
-Suponiendo que ya ha instalado [Node.js](https://nodejs.org/), cree un directorio para que contenga la aplicación y conviértalo en el directorio de trabajo.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Utilice el mandato `npm init` para crear un archivo `package.json` para la aplicación.
-Para obtener más información sobre cómo funciona `package.json`, consulte [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-Este mandato solicita varios elementos como, por ejemplo, el nombre y la versión de la aplicación.
-Por ahora, sólo tiene que pulsar INTRO para aceptar los valores predeterminados para la mayoría de ellos, con la siguiente excepción:
-
-```
-entry point: (index.js)
-```
-
-Especifique `app.js` o el nombre que desee para el archivo principal. Si desea que sea `index.js`, pulse INTRO para aceptar el nombre de archivo predeterminado recomendado.
-
-A continuación, instale Express en el directorio `myapp` y guárdelo en la lista de dependencias. For example:
-
-```bash
-$ npm install express
-```
-
-Para instalar Express temporalmente y no añadirlo a la lista de dependencias, omita la opción `--save`:
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-Los módulos de Node que se instalan con la opción `--save` se añaden a la lista `dependencies` en el archivo `package.json`. Posteriormente, si ejecuta `npm install` en el directorio `app`, los módulos se instalarán automáticamente en la lista de dependencias.
-</div>
\ No newline at end of file
diff --git a/es/starter/static-files.md b/es/starter/static-files.md
deleted file mode 100644
index e138455a67..0000000000
--- a/es/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: Servicio de archivos estáticos en Express
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Servicio de archivos estáticos en Express
-
-Para el servicio de archivos estáticos como, por ejemplo, imágenes, archivos CSS y archivos JavaScript, utilice la función de middleware incorporado `express.static` de Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-Por ejemplo, utilice el siguiente código para el servicio de imágenes, archivos CSS y archivos JavaScript en un directorio denominado `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-Ahora, puede cargar los archivos que hay en el directorio `public`:
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express busca los archivos relativos al directorio estático, por lo que el nombre del directorio estático no forma parte del URL.
-</div>
-
-Para utilizar varios directorios de activos estáticos, invoque la función de middleware `express.static` varias veces:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express busca los archivos en el orden en el que se definen los directorios estáticos con la función de middleware `express.static`.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Ahora, puede cargar los archivos que hay en el directorio `public` desde el prefijo de vía de acceso `/static`.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-No obstante, la vía de acceso que proporciona a la función `express.static` es relativa al directorio desde donde inicia el proceso `node`. Si ejecuta la aplicación Express desde cualquier otro directorio, es más seguro utilizar la vía de acceso absoluta del directorio al que desea dar servicio:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/es/support/index.md b/es/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/es/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/eslint.config.js b/eslint.config.js
new file mode 100644
index 0000000000..764105c090
--- /dev/null
+++ b/eslint.config.js
@@ -0,0 +1,43 @@
+import eslint from '@eslint/js';
+import tseslint from 'typescript-eslint';
+import eslintAstroPlugin from 'eslint-plugin-astro';
+import jsxA11y from 'eslint-plugin-jsx-a11y';
+import eslintConfigPrettier from 'eslint-config-prettier';
+import globals from 'globals';
+import { globalIgnores } from 'eslint/config';
+
+export default [
+  // Global ignores
+  globalIgnores(['dist/*', '.astro/*', 'node_modules/*', 'package-lock.json']),
+  {
+    languageOptions: {
+      globals: {
+        ...globals.browser,
+        ...globals.node,
+      },
+    },
+    ignores: ['dist/', '.astro/', 'node_modules/', 'package-lock.json'],
+  },
+
+  // Base ESLint recommended rules
+  eslint.configs.recommended,
+
+  // TypeScript ESLint recommended rules
+  ...tseslint.configs.recommended,
+
+  // Astro files
+  ...eslintAstroPlugin.configs.recommended,
+  ...eslintAstroPlugin.configs['jsx-a11y-recommended'],
+
+  // JSX Accessibility for non-Astro files
+  {
+    files: ['**/*.{jsx,tsx}'],
+    plugins: {
+      'jsx-a11y': jsxA11y,
+    },
+    rules: jsxA11y.configs.recommended.rules,
+  },
+
+  // Prettier - keep as last to override conflicting rules
+  eslintConfigPrettier,
+];
diff --git a/feed.xml b/feed.xml
deleted file mode 100644
index d5d8b9fcea..0000000000
--- a/feed.xml
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: feed
-sitemap: false
-title: Express Blog
-html_url: /en/blog/posts.html
----
-{% assign posts = site.posts | sort: "date" | reverse %}
-{% for post in posts %}
-{% include feed-entry.xml entry=post %}
-{% endfor %}
diff --git a/fonts/ko/pretendard.css b/fonts/ko/pretendard.css
deleted file mode 100644
index 962feab7b2..0000000000
--- a/fonts/ko/pretendard.css
+++ /dev/null
@@ -1,71 +0,0 @@
-/*
-Copyright (c) 2021 Kil Hyung-jin, with Reserved Font Name Pretendard.
-https://github.com/orioncactus/pretendard
-
-This Font Software is licensed under the SIL Open Font License, Version 1.1.
-This license is copied below, and is also available with a FAQ at:
-http://scripts.sil.org/OFL
-*/
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 900;
-	font-display: swap;
-	src: local('Pretendard Black'), url(./woff2/Pretendard-Black.woff2) format('woff2'), url(./woff/Pretendard-Black.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 800;
-	font-display: swap;
-	src: local('Pretendard ExtraBold'), url(./woff2/Pretendard-ExtraBold.woff2) format('woff2'), url(./woff/Pretendard-ExtraBold.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 700;
-	font-display: swap;
-	src: local('Pretendard Bold'), url(./woff2/Pretendard-Bold.woff2) format('woff2'), url(./woff/Pretendard-Bold.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 600;
-	font-display: swap;
-	src: local('Pretendard SemiBold'), url(./woff2/Pretendard-SemiBold.woff2) format('woff2'), url(./woff/Pretendard-SemiBold.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 500;
-	font-display: swap;
-	src: local('Pretendard Medium'), url(./woff2/Pretendard-Medium.woff2) format('woff2'), url(./woff/Pretendard-Medium.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 400;
-	font-display: swap;
-	src: local('Pretendard Regular'), url(./woff2/Pretendard-Regular.woff2) format('woff2'), url(./woff/Pretendard-Regular.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 300;
-	font-display: swap;
-	src: local('Pretendard Light'), url(./woff2/Pretendard-Light.woff2) format('woff2'), url(./woff/Pretendard-Light.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 200;
-	font-display: swap;
-	src: local('Pretendard ExtraLight'), url(./woff2/Pretendard-ExtraLight.woff2) format('woff2'), url(./woff/Pretendard-ExtraLight.woff) format('woff');
-}
-
-@font-face {
-	font-family: 'Pretendard';
-	font-weight: 100;
-	font-display: swap;
-	src: local('Pretendard Thin'), url(./woff2/Pretendard-Thin.woff2) format('woff2'), url(./woff/Pretendard-Thin.woff) format('woff');
-}
diff --git a/fonts/ko/woff/Pretendard-Black.woff b/fonts/ko/woff/Pretendard-Black.woff
deleted file mode 100644
index d07848c81b..0000000000
Binary files a/fonts/ko/woff/Pretendard-Black.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-Bold.woff b/fonts/ko/woff/Pretendard-Bold.woff
deleted file mode 100644
index 7837ae52d8..0000000000
Binary files a/fonts/ko/woff/Pretendard-Bold.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-ExtraBold.woff b/fonts/ko/woff/Pretendard-ExtraBold.woff
deleted file mode 100644
index 8058b76104..0000000000
Binary files a/fonts/ko/woff/Pretendard-ExtraBold.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-ExtraLight.woff b/fonts/ko/woff/Pretendard-ExtraLight.woff
deleted file mode 100644
index f9498d85aa..0000000000
Binary files a/fonts/ko/woff/Pretendard-ExtraLight.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-Light.woff b/fonts/ko/woff/Pretendard-Light.woff
deleted file mode 100644
index 2cad608276..0000000000
Binary files a/fonts/ko/woff/Pretendard-Light.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-Medium.woff b/fonts/ko/woff/Pretendard-Medium.woff
deleted file mode 100644
index 537040914f..0000000000
Binary files a/fonts/ko/woff/Pretendard-Medium.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-Regular.woff b/fonts/ko/woff/Pretendard-Regular.woff
deleted file mode 100644
index e3b3a3580b..0000000000
Binary files a/fonts/ko/woff/Pretendard-Regular.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-SemiBold.woff b/fonts/ko/woff/Pretendard-SemiBold.woff
deleted file mode 100644
index 682e7a4533..0000000000
Binary files a/fonts/ko/woff/Pretendard-SemiBold.woff and /dev/null differ
diff --git a/fonts/ko/woff/Pretendard-Thin.woff b/fonts/ko/woff/Pretendard-Thin.woff
deleted file mode 100644
index d28e4486c7..0000000000
Binary files a/fonts/ko/woff/Pretendard-Thin.woff and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Black.woff2 b/fonts/ko/woff2/Pretendard-Black.woff2
deleted file mode 100644
index eafe683536..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Black.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Bold.woff2 b/fonts/ko/woff2/Pretendard-Bold.woff2
deleted file mode 100644
index 4d40a1ab89..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Bold.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-ExtraBold.woff2 b/fonts/ko/woff2/Pretendard-ExtraBold.woff2
deleted file mode 100644
index dcd57e757d..0000000000
Binary files a/fonts/ko/woff2/Pretendard-ExtraBold.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-ExtraLight.woff2 b/fonts/ko/woff2/Pretendard-ExtraLight.woff2
deleted file mode 100644
index e5104022b4..0000000000
Binary files a/fonts/ko/woff2/Pretendard-ExtraLight.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Light.woff2 b/fonts/ko/woff2/Pretendard-Light.woff2
deleted file mode 100644
index 7f82fe8478..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Light.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Medium.woff2 b/fonts/ko/woff2/Pretendard-Medium.woff2
deleted file mode 100644
index f8c743d603..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Medium.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Regular.woff2 b/fonts/ko/woff2/Pretendard-Regular.woff2
deleted file mode 100644
index a9f62319b7..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Regular.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-SemiBold.woff2 b/fonts/ko/woff2/Pretendard-SemiBold.woff2
deleted file mode 100644
index 4c6a32de1a..0000000000
Binary files a/fonts/ko/woff2/Pretendard-SemiBold.woff2 and /dev/null differ
diff --git a/fonts/ko/woff2/Pretendard-Thin.woff2 b/fonts/ko/woff2/Pretendard-Thin.woff2
deleted file mode 100644
index 6c9bc96040..0000000000
Binary files a/fonts/ko/woff2/Pretendard-Thin.woff2 and /dev/null differ
diff --git a/fonts/open-sans/fonts.css b/fonts/open-sans/fonts.css
deleted file mode 100644
index b9f165eae3..0000000000
--- a/fonts/open-sans/fonts.css
+++ /dev/null
@@ -1,21 +0,0 @@
-@font-face {
-  font-family: "Open Sans";
-  font-style: normal;
-  font-weight: 300 800;
-  font-display: swap;
-  src: local("Open Sans"),
-        url("./woff2/open-sans-latin-wght-normal.woff2") format("woff2-variations"),
-        url("./woff/OpenSans.woff")   format("woff");
-  unicode-range: U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD;
-}
-
-@font-face {
-  font-family: "Open Sans";
-  font-style: italic;
-  font-weight: 300 800;
-  font-display: swap;
-  src: local("Open Sans"),
-       url("./woff2/open-sans-latin-wght-italic.woff2") format("woff2-variations"),
-       url("./woff/OpenSans-Italic.woff")   format("woff");
-  unicode-range: U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD;
-}
diff --git a/fonts/open-sans/woff/OpenSans-Italic.woff b/fonts/open-sans/woff/OpenSans-Italic.woff
deleted file mode 100644
index ba548c33fd..0000000000
Binary files a/fonts/open-sans/woff/OpenSans-Italic.woff and /dev/null differ
diff --git a/fonts/open-sans/woff/OpenSans.woff b/fonts/open-sans/woff/OpenSans.woff
deleted file mode 100644
index f03b4add70..0000000000
Binary files a/fonts/open-sans/woff/OpenSans.woff and /dev/null differ
diff --git a/fonts/open-sans/woff2/open-sans-latin-wght-italic.woff2 b/fonts/open-sans/woff2/open-sans-latin-wght-italic.woff2
deleted file mode 100644
index 5d9194cd18..0000000000
Binary files a/fonts/open-sans/woff2/open-sans-latin-wght-italic.woff2 and /dev/null differ
diff --git a/fonts/open-sans/woff2/open-sans-latin-wght-normal.woff2 b/fonts/open-sans/woff2/open-sans-latin-wght-normal.woff2
deleted file mode 100644
index 4e8b905cec..0000000000
Binary files a/fonts/open-sans/woff2/open-sans-latin-wght-normal.woff2 and /dev/null differ
diff --git a/fr/3x/api.md b/fr/3x/api.md
deleted file mode 100644
index f9232fe731..0000000000
--- a/fr/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - Référence de l'API
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x N'EST PLUS PRIS EN CHARGE**
-
-Les problèmes de performances et de sécurité connus et inconnus n'ont pas été traités depuis la dernière mise à jour (1er août 2015). Il est fortement recommandé d'utiliser la dernière version d'Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>API 3.x</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/fr/4x/api.md b/fr/4x/api.md
deleted file mode 100644
index 851dab5cd9..0000000000
--- a/fr/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - Référence de l'API
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>API 4.x</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/fr/5x/api.md b/fr/5x/api.md
deleted file mode 100644
index bd4de7b4e3..0000000000
--- a/fr/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Référence de l'API
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/fr/advanced/best-practice-performance.md b/fr/advanced/best-practice-performance.md
deleted file mode 100644
index bc82d29503..0000000000
--- a/fr/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: Meilleures pratiques en termes de performances pour l'utilisation d'Express en production
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# Meilleures pratiques en production : performances et fiabilité
-
-Cet article traite des meilleures pratiques en termes de performances et de fiabilité pour les applications Express déployées en production.
-
-La présente rubrique s'inscrit clairement dans le concept "devops", qui couvre à la fois le développement traditionnel et l'exploitation. Ainsi, les informations se divisent en deux parties :
-
-- Things to do in your code (the dev part):
-  - Utiliser le middleware pour exploiter les fichiers statiques
-  - [Asynchronous Error Handling in Express with Promises, Generators and ES7](https://web.archive.org/web/20240000000000/https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/)
-  - [Do logging correctly](#do-logging-correctly)
-  - Traiter correctement les exceptions
-- [A faire dans votre environnement/configuration](#env) (partie exploitation, "ops").
-  - Définir NODE_ENV sur "production"
-  - Vérifier que votre application redémarre automatiquement
-  - Exécuter votre application dans un cluster
-  - [Cache request results](#cache-request-results)
-  - Utilisation de StrongLoop PM avec un équilibreur de charge Nginx
-  - Encore mieux, utilisez un proxy inverse pour exploiter les fichiers statiques ; pour plus d'informations, voir [Utiliser un proxy inverse](#proxy).
-
-## A faire dans votre code
-
-Les actions suivantes peuvent être réalisées dans votre code afin d'améliorer les performances de votre application :
-
-- Utiliser le middleware pour exploiter les fichiers statiques
-- [Asynchronous Error Handling in Express with Promises, Generators and ES7](https://web.archive.org/web/20240000000000/https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/)
-- [Do logging correctly](#do-logging-correctly)
-- Traiter correctement les exceptions
-
-### Utiliser la compression gzip
-
-La compression Gzip peut considérablement réduire la taille du corps de réponse et ainsi augmenter la vitesse d'une application Web. Utilisez le middleware [compression](https://www.npmjs.com/package/compression) pour la compression gzip dans votre application Express. Par exemple :
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-Pour un site Web en production dont le trafic est élevé, la meilleure méthode pour mettre en place la compression consiste à l'implémenter au niveau d'un proxy inverse (voir [Utiliser un proxy inverse](#proxy)). Dans ce cas, vous n'avez pas besoin d'utiliser le middleware compression. Pour plus de détails sur l'activation de la compression gzip dans Nginx, voir [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) dans la documentation Nginx.
-
-### Ne pas utiliser les fonctions synchrones
-
-Les fonctions et les méthodes synchrones ralentissent le processus d'exécution jusqu'à leur retour. Un simple appel à une fonction synchrone peut revenir en quelques microsecondes ou millisecondes ; pour les sites Web dont le trafic est élevé, ces appels s'additionnent et réduisent les performances de l'application. Evitez de les utiliser en production.
-
-Bien que Node et plusieurs modules mettent à disposition les versions synchrone et asynchrone de leurs fonctions, utilisez toujours la version asynchrone en production. L'utilisation d'une fonction synchrone n'est justifiée que lors du démarrage initial.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Bien entendu vous n'utiliserez pas réellement cette option en production, mais plutôt pour vérifier que votre code est prêt pour la phase production. Pour plus d'informations, voir [Weekly update for io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0).
-
-### Procéder à une journalisation correcte
-
-En règle générale, vous utilisez la journalisation à partir de votre application à deux fins : le débogage et la journalisation de l'activité de votre application (principalement tout le reste). L'utilisation de `console.log()` ou de `console.err()` pour imprimer des messages de journal sur le terminal est une pratique courante en développement. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### Pour le débogage
-
-Si vous utilisez la journalisation à des fins de débogage, utilisez un module de débogage spécial tel que [debug](https://www.npmjs.com/package/debug) plutôt que d'utiliser `console.log()`. Ce module vous permet d'utiliser la variable d'environnement DEBUG pour contrôler les messages de débogage envoyés à `console.err()`, le cas échéant. Pour que votre application reste exclusivement asynchrone, vous devrez toujours diriger `console.err()` vers un autre programme. Mais bon, vous n'allez pas vraiment procéder à un débogage en production, n'est-ce pas ?
-
-#### Pour journaliser l'activité de votre application
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Traiter correctement les exceptions
-
-Les applications Node plantent lorsqu'elles tombent sur une exception non interceptée. Si vous ne traitez pas les exceptions et ne prenez pas les décisions appropriées, votre application Express plantera et sera déconnectée. Si vous suivez les conseils de la rubrique ci-dessous intitulée [Vérifier que votre application redémarre automatiquement](#restart), votre application pourra être restaurée suite à un plantage. Le délai de démarrage des applications Express est heureusement court en règle générale. Vous souhaitez toutefois éviter tout plantage en priorité et pour ce faire, vous devez traiter les exceptions correctement.
-
-Pour vérifier que vous traitez toutes les exceptions, procédez comme suit :
-
-- [Utiliser try-catch](#try-catch)
-- [Utiliser des promesses](#promises)
-
-Avant de s'immerger dans les rubriques qui suivent, il est conseillé de posséder des connaissances de base concernant le traitement des erreurs Node/Express, à savoir l'utilisation des rappels "error-first" et la propagation des erreurs dans le middleware. Node utilise la convention de "rappel error-first" pour renvoyer les erreurs issues des fonctions asynchrones, dans laquelle le premier paramètre de la fonction callback est l'objet error, suivi par les données de résultat dans les paramètres suivants. Pour n'indiquer aucune erreur, indiquez null comme premier paramètre. La fonction de rappel doit suivre la convention de rappel "error-first" de sorte à traiter l'erreur de manière significative. Dans Express, la meilleure pratique consiste à utiliser la fonction next() pour propager les erreurs via la chaîne du middleware.
-
-Pour plus d'informations sur les bases du traitement des erreurs, voir :
-
-- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Utiliser try-catch
-
-Try-catch est un élément de langage JavaScript que vous pouvez utiliser pour intercepter les exceptions dans le code synchrone. Utilisez try-catch pour traiter les erreurs d'analyse JSON, comme indiqué ci-dessous, par exemple.
-
-Voici un exemple d'utilisation de try-catch pour traiter une exception potentielle de plantage de processus.
-Cette fonction middleware accepte un paramètre de zone de requête nommé "params" qui est un objet JSON.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-Toutefois, try-catch ne fonctionne que dans le code synchrone. Etant donné que la plateforme Node est principalement asynchrone (en particulier dans un environnement de production), try-catch n'interceptera pas beaucoup d'exceptions.
-
-#### Utiliser des promesses
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### A ne pas faire
-
-Vous ne devriez _pas_ écouter l'événement `uncaughtException`, émis lorsqu'une exception remonte vers la boucle d'événements. L'ajout d'un programme d'écoute d'événement pour `uncaughtException` va modifier le comportement par défaut du processus qui rencontre une exception ; le processus va continuer à s'exécuter malgré l'exception. Cela pourrait être un bon moyen d'empêcher votre application de planter, mais continuer à exécuter l'application après une exception non interceptée est une pratique dangereuse qui n'est pas recommandée, étant donné que l'état du processus devient peu fiable et imprévisible.
-
-De plus, l'utilisation d'`uncaughtException` est officiellement reconnue comme étant [rudimentaire](https://nodejs.org/api/process.html#process_event_uncaughtexception) et il a été [proposé](https://github.com/nodejs/node-v0.x-archive/issues/2582) de le supprimer. Ecouter `uncaughtException` n'est qu'une mauvaise idée. Voilà pourquoi nous recommandons d'utiliser plusieurs processus et superviseurs à la place : faire planter son application et la redémarrer est souvent plus sûr que de la restaurer après une erreur.
-
-L'utilisation de [domain](https://nodejs.org/api/domain.html) n'est également pas recommandée. Ce module obsolète ne résout globalement pas le problème.
-
-## A faire dans votre environnement/configuration
-
-Les actions suivantes peuvent être réalisées dans votre environnement système afin d'améliorer les performances de votre application :
-
-- Définir NODE_ENV sur "production"
-- Vérifier que votre application redémarre automatiquement
-- Exécuter votre application dans un cluster
-- [Cache request results](#cache-request-results)
-- Utilisation de StrongLoop PM avec un équilibreur de charge Nginx
-- Encore mieux, utilisez un proxy inverse pour exploiter les fichiers statiques ; pour plus d'informations, voir [Utiliser un proxy inverse](#proxy).
-
-### Définir NODE_ENV sur "production"
-
-La variable d'environnement NODE_ENV spécifie l'environnement dans lequel une application s'exécute (en règle générale, développement ou production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-En définissant NODE_ENV sur "production", Express :
-
-- Met en cache les modèles d'affichage.
-- Met en cache les fichiers CSS générés à partir d'extensions CSS.
-- Génère moins de messages d'erreur prolixes.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-Si vous avez besoin d'écrire du code spécifique à un environnement, vous pouvez vérifier la valeur de NODE_ENV avec `process.env.NODE_ENV`. Sachez que la vérification de la valeur de n'importe quelle variable d'environnement pénalise les performances et devrait donc être effectuée avec modération.
-
-En développement, vous définissez généralement les variables d'environnement dans votre shell interactif, à l'aide de `export` ou de votre fichier `.bash_profile` par exemple. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). La section qui suit fournit des détails sur l'utilisation de votre système init en général, mais la définition de NODE_ENV est tellement importante pour les performances (et facile à réaliser), qu'elle est mise en évidence ici.
-
-Avec systemd, utilisez la directive `Environment` dans votre fichier d'unité. Par exemple :
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### Vérifier que votre application redémarre automatiquement
-
-En production, vous ne souhaitez jamais que votre application soit déconnectée. Vous devez donc veiller à ce qu'elle redémarre si elle plante et si le serveur plante. Même si vous espérez que cela n'arrive pas, vous devez en réalité considérer ces deux éventualités en :
-
-- Utilisant un gestionnaire de processus pour redémarrer l'application (et Node) lorsqu'elle plante.
-- Utilisant le système init fourni par votre système d'exploitation pour redémarrer le gestionnaire de processus lorsque le système d'exploitation plante. Vous pouvez également utiliser le système init sans gestionnaire de processus.
-
-Les applications Node plantent si elles tombent sur une exception non interceptée. Avant toute chose, vérifiez que votre application est correctement testée et qu'elle traite toutes les exceptions (voir [Traiter correctement les exceptions](#exceptions) pour plus de détails). En cas d'échec, mettez en place un mécanisme qui garantit que si et lorsque votre application plante, elle redémarre automatiquement.
-
-#### Utiliser un gestionnaire de processus
-
-En développement, vous avez simplement démarré votre application à partir de la ligne de commande avec `node server.js` ou une instruction similaire. En production, cela vous mènera droit au désastre. Si l'application plante, elle sera déconnectée tant que vous ne la redémarrerez pas. Pour garantir que votre application redémarre si elle plante, utilisez un gestionnaire de processus. Un gestionnaire de processus est un "conteneur" d'applications qui facilite le déploiement, offre une haute disponibilité et vous permet de gérer l'application lors de son exécution.
-
-En plus de redémarrer votre application lorsqu'elle plante, un gestionnaire de processus peut vous permettre :
-
-- De vous informer sur les performances d'exécution et la consommation des ressources.
-- De modifier les paramètres de manière dynamique afin d'améliorer les performances.
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### Utiliser un système init
-
-Le niveau de fiabilité suivant consiste à garantir que votre application redémarre lorsque le serveur redémarre. Les systèmes peuvent toujours tomber en panne pour divers motifs. Pour garantir que votre application redémarre si le serveur plante, utilisez le système init intégré à votre système d'exploitation. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-Vous pouvez utiliser les systèmes init de deux manières dans votre application Express :
-
-- Exécutez votre application dans un gestionnaire de processus, puis installez le gestionnaire de processus en tant que service avec le système init. Le gestionnaire de processus va redémarrer votre application lorsqu'elle plantera et le système init va redémarrer le gestionnaire de processus lorsque le système d'exploitation redémarrera. Il s'agit de la méthode recommandée.
-- Exécutez votre application (et Node) directement avec le système init. Cette méthode est plus simple, mais vous ne profitez pas des avantages d'un gestionnaire de processus.
-
-##### Systemd
-
-Systemd est un système Linux et un gestionnaire de services. La plupart des distributions Linux principales ont adopté systemd comme leur système init par défaut.
-
-Un fichier de configuration de service systemd est appelé _fichier d'unité_ et porte l'extension .service. Voici un exemple de fichier d'unité permettant de gérer une application Node directement (remplacez le texte en gras par les valeurs appropriées à votre système et votre application) : Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Pour plus d'informations sur systemd, voir la [page d'aide de systemd](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-### Exécuter votre application dans un cluster
-
-Dans un système multicoeur, vous pouvez augmenter les performances d'une application Node en lançant un cluster de processus. Un cluster exécute plusieurs instances de l'application, idéalement une instance sur chaque coeur d'UC, répartissant ainsi la charge et les tâches entre les instances.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANT : étant donné que les instances d'application s'exécutent en tant que processus distincts, elles ne partagent pas le même espace mémoire. Autrement dit, les objets sont en local sur chaque instance de l'application. Par conséquent, vous ne pouvez pas conserver l'état dans le code de l'application. Vous pouvez toutefois utiliser un magasin de données en mémoire tel que [Redis](http://redis.io/) pour stocker les données de session et l'état. Cette fonctionnalité s'applique essentiellement à toutes les formes de mise à l'échelle horizontale, que la mise en cluster soit effectuée avec plusieurs processus ou avec plusieurs serveurs physiques.
-
-Dans les applications mises en cluster, les processus de traitement peuvent planter individuellement sans impacter le reste des processus. Outre les avantages en termes de performance, l'isolement des pannes constitue une autre raison d'exécuter un cluster de processus d'application. Chaque fois qu'un processus de traitement plante, veillez toujours à consigner l'événement et à génération un nouveau processus à l'aide de cluster.fork().
-
-#### Utilisation du module cluster de Node
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). Ce module permet à un processus maître de générer des processus de traitement et de répartir les connexions entrantes parmi ces processus.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### Mettre en cache les résultats d'une demande
-
-Pour améliorer les performances en production, vous pouvez également mettre en cache le résultat des demandes, de telle sorte que votre application ne répète pas l'opération de traitement de la même demande plusieurs fois.
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### Utiliser un équilibreur de charge
-
-Quel que soit le niveau d'optimisation d'une application, une instance unique ne peut traiter qu'un volume limité de charge et de trafic. Pour faire évoluer une application, vous pouvez exécuter plusieurs instances de cette application et répartir le trafic en utilisant un équilibreur de charge. La configuration d'un équilibreur de charge peut améliorer les performances et la vitesse de votre application et lui permettre d'évoluer plus largement qu'avec une seule instance.
-
-Un équilibreur de charge est généralement un proxy inverse qui orchestre le trafic entrant et sortant de plusieurs instances d'application et serveurs. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Avec l'équilibrage de charge, vous devrez peut-être vérifier que les demandes associées à un ID de session spécifique sont connectées au processus dont elles sont issues. Ce procédé est appelé _affinité de session_ (ou _sessions persistantes_) et peut être effectué en utilisant un magasin de données tel que Redis pour les données de session (en fonction de votre application), comme décrit ci-dessus. Pour en savoir plus, voir [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Utiliser un proxy inverse
-
-Un proxy inverse accompagne une application Web et exécute des opérations de prise en charge sur les demandes, en plus de diriger les demandes vers l'application. Il peut gérer les pages d'erreur, la compression, la mise en cache, le dépôt de fichiers et l'équilibrage de charge entre autres.
-
-La transmission de tâches qui ne requièrent aucune connaissance de l'état d'application à un proxy inverse permet à Express de réaliser des tâches d'application spécialisées. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/fr/advanced/best-practice-security.md b/fr/advanced/best-practice-security.md
deleted file mode 100644
index c079c3aca9..0000000000
--- a/fr/advanced/best-practice-security.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-layout: page
-title: Meilleures pratiques de sécurité pour Express en production
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# Meilleures pratiques en production : Sécurité
-
-## Présentation
-
-Le terme _"production"_ fait référence à la phase du cycle de vie du logiciel au cours de laquelle une application ou une API est généralement disponible pour ses consommateurs ou utilisateurs finaux. En revanche, en phase de _"développement"_, l'écriture et le test de code se poursuivent activement et l'application n'est pas ouverte pour un accès externe. Les environnements système correspondants sont respectivement appelés environnement de _production_ et environnement de _développement_.
-
-Les environnements de développement et de production sont généralement configurés différemment et leurs exigences divergent grandement. Ce qui convient parfaitement en développement peut être inacceptable en production. Par exemple, dans un environnement de développement, vous pouvez souhaiter une consignation prolixe des erreurs en vue du débogage, alors que ce type de comportement présente des risques au niveau de sécurité en environnement de production. De plus, en environnement de développement, vous n'avez pas à vous soucier de l'extensibilité, de la fiabilité et des performances, tandis que ces éléments sont essentiels en environnement de production.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-Cet article traite des meilleures pratiques en terme de sécurité pour les applications Express déployées en production.
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [hsts](https://github.com/helmetjs/hsts) définit l'en-tête `Strict-Transport-Security` qui impose des connexions (HTTP sur SSL/TLS) sécurisées au serveur.
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) supprime l'en-tête `X-Powered-By`.
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - [xssFilter](https://github.com/helmetjs/x-xss-protection) définit `X-XSS-Protection` afin d'activer le filtre de script intersites (XSS) dans les navigateurs Web les plus récents.
-    - [noCache](https://github.com/helmetjs/nocache) définit des en-têtes `Cache-Control` et Pragma pour désactiver la mise en cache côté client.
-    - [ieNoOpen](https://github.com/helmetjs/ienoopen) définit `X-Download-Options` pour IE8+.
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - Désactivez au minimum l'en-tête X-Powered-By
-  - [Additional considerations](#additional-considerations)
-
-## N'utilisez pas de versions obsolètes ou vulnérables d'Express
-
-Les versions 2.x et 3.x d'Express ne sont plus prises en charge. Les problèmes liés à la sécurité et aux performances dans ces versions ne seront pas corrigés. Ne les utilisez pas ! Si vous êtes passé à la version 4, suivez le [guide de migration](/{{ page.lang }}/guide/migrating-4.html).
-
-Vérifiez également que vous n'utilisez aucune des versions vulnérables d'Express répertoriées sur la [page Mises à jour de sécurité](/{{ page.lang }}/advanced/security-updates.html). Si tel est le cas, procédez à une mise à jour vers une version stable, de préférence la plus récente.
-
-## Utilisez TLS
-
-Si votre application traite ou transmet des données sensibles, utilisez [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) (Transport Layer Security) afin de sécuriser la connexion et les données. Cette technologie de l'information chiffre les données avant de les envoyer du client au serveur, ce qui vous préserve des risques d'hameçonnage les plus communs (et faciles). Même si les requêtes Ajax et POST ne sont pas clairement visibles et semblent "masquées" dans les navigateurs, leur trafic réseau n'est pas à l'abri d'une [détection de paquet](https://en.wikipedia.org/wiki/Packet_analyzer) ni des [attaques d’intercepteur](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-Vous connaissez sans doute le chiffrement SSL (Secure Socket Layer). [TLS est simplement une évolution de SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). En d'autres termes, si vous utilisiez SSL auparavant, envisagez de passer à TLS. Nous recommandons généralement Nginx pour gérer TLS. Pour des informations de référence fiables concernant la configuration de TLS sur Nginx (et d'autres serveurs), voir [Configurations de serveur recommandées (wiki Mozilla)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-Par ailleurs, un outil très pratique, [Let's Encrypt](https://letsencrypt.org/about/), autorité de certification gratuite, automatisée et ouverte fournie par le groupe de recherche sur la sécurité sur Internet, [ISRG (Internet Security Research Group)](https://letsencrypt.org/isrg/), vous permet de vous procurer gratuitement un certificat TLS.
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Utilisez Helmet
-
-[Helmet](https://www.npmjs.com/package/helmet) vous aide à protéger votre application de certaines des vulnérabilités bien connues du Web en configurant de manière appropriée des en-têtes HTTP.
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-Installez Helmet comme n'importe quel autre module :
-
-```bash
-$ npm install helmet
-```
-
-Puis, pour l'utiliser dans votre code :
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-By default, Express sends the `X-Powered-By` response header that you can
-disable using the `app.disable()` method:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Utilisez les cookies de manière sécurisée
-
-Pour garantir que les cookies n'ouvrent pas votre application aux attaques, n'utilisez pas le nom du cookie de session par défaut et définissez de manière appropriée des options de sécurité des cookies.
-
-Il existe deux modules principaux de session de cookie de middleware :
-
-- [express-session](https://www.npmjs.com/package/express-session) qui remplace le middleware `express.session` intégré à Express 3.x.
-- [cookie-session](https://www.npmjs.com/package/cookie-session) qui remplace le middleware `express.cookieSession` intégré à Express 3.x.
-
-La principale différence entre ces deux modules tient à la manière dont ils sauvegardent les données de session des cookies. Le middleware [express-session](https://www.npmjs.com/package/express-session) stocke les données de session sur le serveur ; il ne sauvegarde que l'ID session dans le cookie lui-même, mais pas les données de session. Par défaut, il utilise le stockage en mémoire et n'est pas conçu pour un environnement de production. En production, vous devrez configurer un magasin de sessions évolutif (voir la liste des [magasins de sessions compatibles](https://github.com/expressjs/session#compatible-session-stores)).
-
-En revanche, le middleware [cookie-session](https://www.npmjs.com/package/cookie-session) implémente un stockage sur cookie, c'est-à-dire qu'il sérialise l'intégralité de la session sur le cookie, et non simplement une clé de session. Utilisez-le uniquement lorsque les données de session sont relativement peu nombreuses et faciles à coder sous forme de valeurs primitives (au lieu d'objets). Même si les navigateurs sont censés prendre en charge au moins 4096 octets par cookie, pour ne pas risquer de dépasser cette limite, limitez-vous à 4093 octets par domaine. De plus, n'oubliez pas que les données de cookie seront visibles du client et que s'il n'est pas nécessaire qu'elles soient sécurisées ou illisibles, express-session est probablement la meilleure solution.
-
-### N'utilisez pas de nom de cookie de session par défaut
-
-L'utilisation d'un nom de cookie de session par défaut risque d'ouvrir votre application aux attaques. Le problème de sécurité qui en découle est similaire à `X-Powered-By` : une personne potentiellement malveillante peut l'utiliser pour s'identifier auprès du serveur et cibler ses attaques en conséquence.
-
-Pour éviter ce problème, utilisez des noms de cookie génériques, par exemple à l'aide du middleware [express-session](https://www.npmjs.com/package/express-session) :
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Définissez des options de sécurité de cookie
-
-Définissez les options de cookie suivantes pour accroître la sécurité :
-
-- `secure` - Garantit que le navigateur n'envoie le cookie que sur HTTPS.
-- `httpOnly` - Garantit que le cookie n'est envoyé que sur HTTP(S), pas au JavaScript du client, ce qui renforce la protection contre les attaques de type cross-site scripting.
-- `domain` - Indique le domaine du cookie ; utilisez cette option pour une comparaison avec le domaine du serveur dans lequel l'URL est demandée. S'ils correspondent, vérifiez ensuite l'attribut de chemin.
-- `path` - Indique le chemin du cookie ; utilisez cette option pour une comparaison avec le chemin demandé. Si le chemin et le domaine correspondent, envoyez le cookie dans la demande.
-- `expires` - Utilisez cette option pour définir la date d'expiration des cookies persistants.
-
-Exemple d'utilisation du middleware [cookie-session](https://www.npmjs.com/package/cookie-session) :
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Implémentez la limitation de débit pour empêcher les attaques de force brute liées à l'authentification.
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### Eviter les autres vulnérabilités connues
-
-Gardez un oeil sur les recommandations [Node Security Project](https://npmjs.com/advisories) qui peuvent concerner Express ou d'autres modules utilisés par votre application. En règle générale, Node Security Project est une excellente ressource de connaissances et d'outils sur la sécurité de Node.
-
-Pour finir, les applications Express - comme toutes les autres applications Web - peuvent être vulnérables à une variété d'attaques Web. Familiarisez vous avec les [vulnérabilités Web](https://www.owasp.org/www-project-top-ten/) connues et prenez des précautions pour les éviter.
-
-## Autres considérations
-
-Voici d'autres recommandations issues de l'excellente [liste de contrôle de sécurité Node.js](https://blog.risingstack.com/node-js-security-checklist/). Pour tous les détails sur ces recommandations, reportez-vous à cet article de blogue :
-
-- Filtrez et nettoyez toujours les entrées utilisateur pour vous protéger contre les attaques de cross-site scripting (XSS) et d'injection de commande.
-- Défendez-vous contre les attaques par injection SQL en utilisant des requêtes paramétrées ou des instructions préparées.
-- Utilisez l'outil [sqlmap](http://sqlmap.org/) à code source ouvert pour détecter les vulnérabilités par injection SQL dans votre application.
-- Utilisez les outils [nmap](https://nmap.org/) et [sslyze](https://github.com/nabla-c0d3/sslyze) pour tester la configuration de vos chiffrements, clés et renégociations SSL, ainsi que la validité de votre certificat.
-- Utilisez [safe-regex](https://www.npmjs.com/package/safe-regex) pour s'assurer que vos expressions régulières ne sont pas exposées à des attaques ReDoS ([regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS)).
-
-[helmet]: <Si vous utilisez `helmet.js`, cette opération s'effectue automatiquement.>
\ No newline at end of file
diff --git a/fr/advanced/developing-template-engines.md b/fr/advanced/developing-template-engines.md
deleted file mode 100644
index 133037ad85..0000000000
--- a/fr/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Développement de moteurs de modèles pour Express
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Développement de moteurs de modèles pour Express
-
-Utilisez la méthode `app.engine(ext, callback)` pour créer votre propre moteur de modèle. `ext` fait référence à l'extension de fichier et `callback` est la fonction du moteur de modèle, qui accepte les éléments suivants en tant que paramètres : l'emplacement du fichier, l'objet options et la fonction callback.
-
-Le code suivant est un exemple d'implémentation d'un moteur de modèle très simple qui permet d'afficher le rendu des fichiers `.ntl`.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Votre application est désormais en mesure d'afficher le rendu des fichiers `.ntl`. Créez un fichier nommé  `index.ntl` dans le répertoire `views` avec le contenu suivant.
-
-```pug
-#title#
-#message#
-```
-
-ENsuite, créez la route suivante dans votre application.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Lorsque vous effectuerez une demande à la page d'accueil, `index.ntl` sera rendu au format HTML.
\ No newline at end of file
diff --git a/fr/advanced/healthcheck-graceful-shutdown.md b/fr/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 53dd47edba..0000000000
--- a/fr/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### Exemple
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/fr/advanced/security-updates.md b/fr/advanced/security-updates.md
deleted file mode 100644
index d7c02f1492..0000000000
--- a/fr/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Express security updates
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# Mises à jour de sécurité
-
-<div class="doc-box doc-notice" markdown="1">
-Les vulnérabilités Node.js affectent directement Express. Cependant, [gardez un oeil sur les vulnérabilités Node.js](https://nodejs.org
-/en/blog/vulnerability/) et assurez-vous d'utiliser la dernière version stable de Node.js.
-</div>
-
-La liste ci-dessous répertorie les vulnérabilités Express qui ont été corrigées dans la mise à jour de la version spécifiée.
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - Correction de la vulnérabilité de divulgation de racine dans `express.static`, `res.sendfile` et `res.sendFile`
-- 4.10.7
-  - Correction de la vulnérabilité de redirection ouverte dans `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 4.8.8
-  - Correction des vulnérabilités de traversée de répertoire dans `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-- 4.8.4
-  - Node.js 0.10 peut divulguer des `fd` dans certaines situations qui affectent `express.static` et `res.sendfile`. Des demandes malveillantes pouvaient entraîner la divulgation de `fd`, ainsi que des erreurs `EMFILE` et une absence de réponse du serveur.
-- 4.8.0
-  - Les tableaux creux qui possèdent des index très élevés dans la chaîne de requête pouvaient entraîner la saturation de mémoire et la panne du serveur.
-  - Les objets contenant des chaînes de requête extrêmement imbriquées pouvaient entraîner le blocage du processus et figer temporairement le serveur.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x N'EST PLUS PRIS EN CHARGE**
-
-Les problèmes de performances et de sécurité connus et inconnus n'ont pas été traités depuis la dernière mise à jour (1er août 2015). Il est fortement recommandé d'utiliser la dernière version d'Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - Correction de la vulnérabilité de divulgation de racine dans `express.static`, `res.sendfile` et `res.sendFile`
-- 3.19.0
-  - Correction de la vulnérabilité de redirection ouverte dans `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 3.16.10
-  - Correction des vulnérabilités de traversée de répertoire dans `express.static`.
-- 3.16.6
-  - Node.js 0.10 peut divulguer des `fd` dans certaines situations qui affectent `express.static` et `res.sendfile`. Des demandes malveillantes pouvaient entraîner la divulgation de `fd`, ainsi que des erreurs `EMFILE` et une absence de réponse du serveur.
-- 3.16.0
-  - Les tableaux creux qui possèdent des index très élevés dans la chaîne de requête pouvaient entraîner la saturation de mémoire et la panne du serveur.
-  - Les objets contenant des chaînes de requête extrêmement imbriquées pouvaient entraîner le blocage du processus et figer temporairement le serveur.
-- 3.3.0
-  - La réponse 404 à une tentative de substitution de méthode non prise en charge était susceptible d'entraîner des attaques de type cross-site scripting.
\ No newline at end of file
diff --git a/fr/api.md b/fr/api.md
deleted file mode 100644
index a49068f28f..0000000000
--- a/fr/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Référence de l'API
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/fr/changelog/index.md b/fr/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/fr/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/fr/guide/behind-proxies.md b/fr/guide/behind-proxies.md
deleted file mode 100644
index 9bb9cf59fa..0000000000
--- a/fr/guide/behind-proxies.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-layout: page
-title: Serveurs proxy derrière Express
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# Serveurs proxy derrière Express
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-The application setting `trust proxy` may be set to one of the values listed in the following table.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Type</th><th>Valeur</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Booléen</td>
-<td markdown="1">Si la valeur est `true`, l'adresse IP du client est interprétée comme étant l'entrée la plus à gauche dans l'en-tête `X-Forwarded-*`.
-
-Si la valeur est `false`, l'application est interprétée comme étant directement accessible sur Internet et l'adresse IP du client est dérivée de `req.connection.remoteAddress`. Il s'agit du paramètre par défaut.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-Vous pouvez définir les adresses IP de l'une des manières suivantes :
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-S'ils sont spécifiés, les sous-réseaux ou les adresses IP sont exclus du processus d'identification d'adresse, et l'adresse IP sans confiance la plus proche du serveur d'applications est identifiée comme étant l'adresse IP du client. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>Numérique</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">La valeur de [req.hostname](/{{ page.lang }}/api.html#req.hostname) est dérivée de l'ensemble de valeurs indiqué dans l'en-tête `X-Forwarded-Host`, qui peut être défini par le client ou par le proxy.
-  </li>
-  <li markdown="1">`X-Forwarded-Proto` peut être défini par le proxy inverse pour indiquer à l'application s'il s'agit de `https` ou de `http`, voire d'un nom non valide. Cette valeur est reflétée par [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">Les valeurs [req.ip](/{{ page.lang }}/api.html#req.ip) et [req.ips](/{{ page.lang }}/api.html#req.ips) sont renseignées avec la liste des adresses provenant de `X-Forwarded-For`.
-  </li>
-</ul>
-
-Le paramètre `trust proxy` est implémenté à l'aide du package [proxy-addr](https://www.npmjs.com/package/proxy-addr). Pour plus d'informations, consultez la documentation associée.
diff --git a/fr/guide/database-integration.md b/fr/guide/database-integration.md
deleted file mode 100644
index 4118af91ee..0000000000
--- a/fr/guide/database-integration.md
+++ /dev/null
@@ -1,507 +0,0 @@
----
-layout: page
-title: Express database integration
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# Intégration de bases de données
-
-L'ajout de la fonctionnalité permettant de connecter des bases de données aux applications Express consiste simplement à charger un pilote Node.js approprié pour les bases de données de votre application. Ce document explique brièvement comment ajouter et utiliser dans votre application Express certains des modules Node.js les plus populaires pour les systèmes de base de données :
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-Ces pilotes de base de données ne sont qu'une partie de ceux disponibles. Pour d'autres options,
-consultez le site [npm](https://www.npmjs.com/).
-</div>
-
-## Cassandra
-
-**Module** : [cassandra-driver](https://github.com/datastax/nodejs-driver)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Exemple
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### Installation
-
-```bash
-$ npm install couchbase
-```
-
-### Exemple
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Module** : [nano](https://github.com/dscape/nano)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install nano
-```
-
-### Exemple
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Module** : [levelup](https://github.com/rvagg/node-levelup)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Exemple
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Module** : [mysql](https://github.com/felixge/node-mysql/)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install mysql
-```
-
-### Exemple
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Module** : [mongodb](https://github.com/mongodb/node-mongodb-native)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-Si vous voulez un pilote de modèle d'objet pour MongoDB, recherchez [Mongoose](https://github.com/LearnBoost/mongoose).
-
-## Neo4j
-
-**Module** : [apoc](https://github.com/hacksparrow/apoc)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Exemple
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Module**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### Installation
-
-Remarque: [Voir les conditions préalables à l'installation](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Exemple
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Module** : [pg-promise](https://github.com/vitaly-t/pg-promise)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install pg-promise
-```
-
-### Exemple
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Module** : [redis](https://github.com/mranney/node_redis)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install redis
-```
-
-### Exemple
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### Installation
-
-```bash
-$ npm install tedious
-```
-
-### Exemple
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Module** : [sqlite3](https://github.com/mapbox/node-sqlite3)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install sqlite3
-```
-
-### Exemple
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**Module** : [elasticsearch](https://github.com/elastic/elasticsearch-js)
-**Installation**
-
-### Installation
-
-```bash
-$ npm install elasticsearch
-```
-
-### Exemple
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/fr/guide/debugging.md b/fr/guide/debugging.md
deleted file mode 100644
index 4ae539dfab..0000000000
--- a/fr/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: Débogage d'Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Débogage d'Express
-
-Pour afficher tous les journaux internes utilisés dans Express, affectez à la variable d'environnement `DEBUG` la valeur `express:*` lors du lancement de votre application.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-Sous Windows, utilisez la commande correspondante.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-L'exécution de cette commande sur l'application par défaut générée par le [générateur express](/{{ page.lang }}/starter/generator.html) imprime le résultat suivant :
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-Si une demande est par la suite effectuée à l'application, vous verrez les journaux spécifiés dans le code Express :
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-Pour afficher les journaux uniquement à partir de l'implémentation du routeur, affectez à la variable d'environnement `DEBUG` la valeur `express:router`. De la même façon, pour afficher les journaux uniquement à partir de l'implémentation de l'application, affectez à la variable d'environnement `DEBUG` la valeur `express:application`, et ainsi de suite.
-
-## Applications générées par la commande `express`
-
-Une application générée par la commande `express` également appel au module `debug` et son espace de nom de débogage est délimité par le nom de l'application.
-
-Ainsi, si vous avez généré l'application à l'aide de `$ express sample-app`, vous pouvez activer les instructions de débogage en exécutant la commande suivante :
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-Vous pouvez spécifier plusieurs espaces de noms de débogage en affectant une liste de noms séparés par des virgules :
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/fr/guide/error-handling.md b/fr/guide/error-handling.md
deleted file mode 100644
index 30cf7dc093..0000000000
--- a/fr/guide/error-handling.md
+++ /dev/null
@@ -1,294 +0,0 @@
----
-layout: page
-title: Traitement d'erreurs Express
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# Traitement d'erreurs
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. Par exemple :
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-Définissez les fonctions middleware de traitement d'erreurs de la même manière que les autres fonctions middleware,
-à l'exception près que les fonctions de traitement d'erreurs se composent de quatre arguments et non de trois :
-`(err, req, res, next)`.  Par exemple :
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Si vous disposez d'un gestionnaire de routage avec plusieurs fonctions callback, vour pouvez utiliser le paramètre `route` pour passer au gestionnaire de routage suivant.
-Par exemple :
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-Si vous transmettez tout à la fonction `next()` (sauf la chaîne `'route'`), Express considère la demande en cours
-comme étant erronée et ignorera tout routage de gestion non lié à une erreur et toute fonction middleware restants.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. Par exemple :
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  Par exemple :
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. Par exemple :
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## Le gestionnaire de traitement d'erreurs par défaut
-
-Express propose un gestionnaire d'erreurs intégré, qui traite toutes les erreurs qui pourraient survenir dans l'application. Cette fonction middleware de traitement d'erreurs par défaut est ajoutée à la fin de la pile de fonctions middleware.
-
-Si vous transmettez l'erreur à `next()` et que vous ne voulez pas la gérer dans
-un gestionnaire d'erreurs, elle sera gérée par le gestionnaire d'erreurs intégré ; l'erreur sera alors écrite dans le client avec la
-trace de pile. La trace de pile n'est pas incluse dans l'environnement de production.
-
-<div class="doc-box doc-info" markdown="1">
-Définissez la variable d'environnement `NODE_ENV` sur `production` afin d'exécuter l'application en mode production.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-Si vous appelez `next()` avec une erreur après avoir démarré l'écriture de la
-réponse (par exemple, si vous rencontrez une erreur lors de la diffusion en flux de la
-réponse au client) le gestionnaire de traitement d'erreurs par défaut Express ferme la
-connexion et met la demande en échec.
-
-De ce fait, lorsque vous ajoutez un gestionnaire d'erreurs personnalisé, vous devriez déléguer
-les mécanismes de gestion d'erreur par défaut à Express, lorsque les en-têtes
-ont déjà été envoyés au client :
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. Par exemple :
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Définissez le middleware de traitement d'erreurs en dernier, après les autres appels `app.use()` et de routes ; par exemple :
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Les réponses issues d'une fonction middleware peuvent être au format de votre choix, par exemple une page d'erreur HTML, un simple message ou une chaîne JSON.
-
-A des fins organisationnelles (et d'infrastructure de niveau supérieur), vous pouvez définir plusieurs fonctions middleware de traitement d'erreurs, tout comme vous le feriez avec d'autres fonctions middleware ordinaires. Par exemple, si vous vouliez définir un gestionnaire d'erreurs pour les demandes réalisées avec `XHR` et pour celles réalisées sans, vous pourriez utiliser les commandes suivantes :
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-Dans cet exemple, les erreurs `logErrors` génériques pourraient écrire des informations de demande et d'erreur dans `stderr`, par exemple :
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-Egalement dans cet exemple, `clientErrorHandler` est défini comme suit ; dans ce cas, l'erreur est explicitement transmise à la fonction suivante :
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-La fonction "catch-all" `errorHandler` peut être mise en oeuvre comme suit :
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. Par exemple :
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-Dans cet exemple, le gestionnaire `getPaidContent` sera ignoré, mais tous les gestionnaires restants dans `app` pour `/a_route_behind_paywall` continueront d'être exécutés.
-
-<div class="doc-box doc-info" markdown="1">
-Les appels `next()` et `next(err)` indiquent que le gestionnaire en cours a fini et quel est son état.  `next(err)` ignorera tous les gestionnaires restants dans la chaîne, sauf ceux définis pour gérer les erreurs tel que décrit ci-dessus.
-</div>
diff --git a/fr/guide/migrating-4.md b/fr/guide/migrating-4.md
deleted file mode 100644
index ce9d27085a..0000000000
--- a/fr/guide/migrating-4.md
+++ /dev/null
@@ -1,597 +0,0 @@
----
-layout: page
-title: Migration vers Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Migration vers Express 4
-
-<h2 id="overview">Présentation</h2>
-
-Express 4 est un changement novateur d'Express 3. Cela signifie qu'une application Express 3 existante ne fonctionnera pas si vous mettez à jour la version Express dans les dépendances.
-
-Cet article couvre :
-
-<ul class="doclist">
-  <li><a href="#changes">Modifications dans Express 4.</a></li>
-  <li><a href="#example-migration">Un exemple</a> de migration d'une application Express 3 vers Express 4.</li>
-  <li><a href="#app-gen">Mise à niveau vers le générateur d'applications Express 4.</a></li>
-</ul>
-
-<h2 id="changes">Modifications dans Express 4</h2>
-
-De nombreuses modifications importantes ont été faites dans Express 4 :
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Modifications du système de routage.</a></li>
-  <li><a href="#other-changes">Autres modifications diverses.</a></li>
-</ul>
-
-Voir aussi :
-
-- [Nouvelles fonctions dans la version 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migration de la version 3.x vers 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Modification du système principal et middleware d'Express
-</h3>
-
-Express 4 ne dépend plus de Connect, et supprime tous les middleware intégrés de son noyau, sauf la fonction `express.static`. Cela signifie qu'Express
-est désormais un canevas Web de routage et de middleware indépendant et que les versions et
-éditions d'Express ne sont pas affectées par les mises à jour de middleware.
-
-Sans middleware intégré, vous devez explicitement ajouter tous les
-middleware requis pour exécuter votre application. Procédez comme suit :
-
-1. Installez le module : `npm install --save <module-name>`
-2. Dans votre application, demandez le module : `require('module-name')`
-3. Utilisez le module en fonction de cette documentation: `app.use( ... )`
-
-La table suivante répertorie le middelware Express 3 et ces équivalents dans Express 4.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Vous trouverez ici la [liste complète](https://github.com/senchalabs/connect#middleware) du middleware Express 4.
-
-Dans la plupart des cas, il vous suffit de remplacer l'ancienne version du middelware 3 par
-son équivalent Express 4. Pour plus d'informations, consultez la documentation relative au module dans
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> accepte les paramètres</h4>
-
-Dans la version 4 vous pouvez utilisez un paramètre variable pour définir le chemin vers lequel les fonctions middleware sont chargées, puis lire la valeur de ce paramètre dans le gestionnaire de routage.
-Par exemple :
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-Le système de routage
-</h3>
-
-Les applications chargent dorénavant les middleware de routage de manière implicite, ce qui fait que vous n'avez plus à vous
-soucier de l'ordre dans lequel les middleware sont chargés par rapport au middleware `router`.
-
-La façon de définir des routes n'a pas changé mais le système de routage possède deux nouvelles fonctions
-pour vous aider à organiser vos routes :
-
-{: .doclist }
-
-- Une nouvelle méthode, `app.route()`, permettant de créer des gestionnaires de routage sous forme de chaîne pour un chemin de routage.
-- Une nouvelle classe, `express.Router`, permettant de créer des gestionnaires de routage modulaires pouvant être montés.
-
-<h4 id="app-route">méthode <code>app.route()</code></h4>
-
-La nouvelle méthode `app.route()` vous permet de créer des gestionnaires de routage sous forme de chaîne pour un chemin de routage. Etant donné que le chemin est spécifié à une seul emplacement, la création de routes modulaires est utile car elle réduit la redondance et les erreurs. Pour plus d'informations sur les routes, voir la [documentation `Router()`](/{{ page.lang }}/4x/api.html#router).
-
-Voici quelques exemples de gestionnaires de chemin de chaînage définis à l'aide de la fonction `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router">classe <code>express.Router</code> </h4>
-
-L'autre fonction qui aide à organiser les routes est une nouvelle classe,
-`express.Router`, que vous pouvez utiliser pour créer des gestionnaires de routage modulaires pouvant être
-montés. Une instance `Router` est un middleware et un système de routage complet ; pour cette raison, elle est souvent appelée "mini-app".
-
-L'exemple suivant créé une routeur en tant que module, charge un middleware dans celui-ci, définit des routes et monte le module sur un chemin dans l'application principale.
-
-Par exemple, créez un fichier de routage nommé `birds.js` dans le répertoire app, avec le contenu suivant :
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Puis, chargez le module de routage dans l'application :
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-L'application pourra gérer des demandes dans les chemins `/birds` et
-`/birds/about`, et appellera le middleware `timeLog` spécifique à la route.
-
-<h3 id="other-changes">
-Autres modifications
-</h3>
-
-Le tableau suivant répertorie les autres modifications mineures mais importantes dans Express 4 :
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Objet</th>
-<th>Description</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 nécessite Node.js 0.10.x ou ultérieur et a abandonné la prise en charge de
-Node.js 0.8.x.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-Le module `http` n'est plus nécessaire, à moins que vous ne l'utilisiez directement (socket.io/SPDY/HTTPS). L'application peut être démarrée à l'aide de la fonction
-`app.listen()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-La fonction `app.configure()` a été supprimée.  Utilisez
-la fonction `process.env.NODE_ENV` ou
-`app.get('env')` pour détecter l'environnement et configurer l'application, le cas échéant.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-La propriété d'application `json spaces` est désactivée par défaut dans Express 4.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Use `req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()` et `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-Ne résout plus les adresses URL relatives.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Was an array; now an object.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Anciennement une fonction ; il s'agit dorénavant d'un objet.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-A été modifié en `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Dorénavant disponible comme `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Supprimé.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Supprimé.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Cette fonctionnalité se limite désormais à définir la valeur de cookie de base. Utilisez
-`res.cookie()` pour plus de fonctionnalités.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">Exemple de migration d'application</h2>
-
-Voici un exemple de migration d'une application Express 3 vers Express 4.
-Les fichiers qui nous intéressent sont `app.js` et `package.json`.
-
-<h3 id="">
-Application de la version 3
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Examinons une application Express v.3 avec le fichier `app.js` suivant :
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-Voici à quoi ressemble le fichier `package.json` qui accompagne la version 3 :
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Processus
-</h3>
-
-Commencez le processus de migration en installant le middleware requis pour l'application
-Express 4 et en mettant à jour Express et Pug vers leur version la plus récente respective à l'aide de la commande suivante :
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Apportez les modifications suivantes à `app.js` :
-
-1. Les fonctions Express Middleware intégrées `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` et
-   `express.errorHandler` ne sont plus disponibles sur l'objet
-   `express`. Vous devez installer leurs fonctions alternatives
-   manuellement et les charger dans l'application.
-
-2. Vous ne devez plus charger la fonction `app.router`.
-   Il ne s'agit pas d'un objet d'application Express 4 valide. Supprimez le code
-   `app.use(app.router);`.
-
-3. Assurez-vous que les fonctions middleware sont chargées dans l'ordre correct - chargez `errorHandler` après avoir chargé les routes d'application.
-
-<h3 id="">Application de la version 4</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-Le fait d'exécuter la commande `npm` ci-dessus mettra à jour `package.json` comme suit :
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Puis, supprimez le code non valide, chargez les middleware requis et procédez aux autres changements,
-le cas échéant. Voici à quoi ressemble le fichier `app.js` :
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-A mois que vous deviez utiliser le module `http` (socket.io/SPDY/HTTPS) directement, vous n'avez pas à le charger et l'application peut être démarrée comme suit :
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Exécutez l'application</h3>
-
-Le processus de migration est terminé et l'application est désormais une application
-Express 4. Pour confirmer, démarrez l'application en utilisant la commande suivante :
-
-```bash
-$ node .
-```
-
-Chargez [http://localhost:3000](http://localhost:3000)
-et voyez comment la page d'accueil est générée par Express 4.
-
-<h2 id="app-gen">Mise à niveau vers le générateur d'applications Express 4</h2>
-
-L'outil de ligne de commande qui permet de générer une application Express est toujours
-`express`, mais pour effectuer la mise à niveau vers la nouvelle version, vous devez désinstaller
-le générateur d'applications Express 3 puis installer la nouvelle version d'`express-generator`.
-
-<h3 id="">Installation </h3>
-
-Si le générateur d'applications Express 3 est installé sur votre système, vous devez le désinstaller :
-
-```bash
-$ npm uninstall -g express
-```
-
-En fonction de la configuration de vos privilèges de fichier et de répertoire,
-vous devrez exécuter cette commande avec `sudo`.A présent, installez le nouveau générateur :
-
-Now install the new generator:
-
-```bash
-$ npm install -g express-generator
-```
-
-En fonction de la configuration de vos privilèges de fichier et de répertoire,
-vous devrez exécuter cette commande avec `sudo`.A présent, installez le nouveau générateur :
-
-Désormais, la commande `express` sur votre système est mise à jour vers le générateur Express 4.
-
-<h3 id="">Modifications du générateur d'applications </h3>
-
-Les options et les syntaxe de commande restent généralement identiques, avec les exceptions suivantes :
-
-{: .doclist }
-
-- L'option `--sessions` a été supprimée.
-- L'option `--jshtml` a été supprimée.
-- L'option `--hogan` a été ajoutée à la prise en charge de [Hogan.js](http://twitter.github.io/hogan.js/).
-
-<h3 id="">Exemple</h3>
-
-Exécutez la commande suivante pour créer une application Express 4 :
-
-```bash
-$ express app4
-```
-
-Si vous examinez le contenu du fichier `app4/app.js`, vous remarquerez que toutes
-les fonctions middleware (sauf `express.static`) qui sont requises pour
-l'application sont chargées en tant que modules indépendants, et le middleware `router` n'est plus chargé
-explicitement dans l'application.
-
-Vous noterez également que le fichier `app.js` est désormais un module Node.js, contrairement à l'application autonome qui a été générée par l'ancien générateur.
-
-Après avoir installé les dépendances, démarrez l'application en utilisant la commande suivante :
-
-```bash
-$ npm start
-```
-
-Si vous examinez le script de démarrage npm dans le fichier `package.json`,
-vous remarquerez dorénavant que la commande qui démarre l'application est
-`node ./bin/www` alors qu'il s'agissait de `node app.js`
-dans Express 3.
-
-Puisque le fichier `app.js` qui a été généré par le générateur Express 4 est
-désormais un module Node.js, il ne peut plus être démarré indépendamment en tant qu'application
-(sauf si vous modifiez le code). Le module doit être chargé dans un fichier Node.js et démarré
-via le fichier Node.js. Dans cet exemple, le fichier Node.js est `./bin/www`.
-
-Ni le répertoire `bin` ni le fichier `www`
-sans extension n'est obligatoire pour créer une application Express ou démarrer celle-ci. Ce ne sont ici que des suggestions faites par le générateur, donc n'hésitez pas à les modifier si besoin.
-
-Pour se débarrasser du répertoire `www` et garder la présentation d'Express 3,
-supprimez la ligne `module.exports = app;` à la fin du fichier
-`app.js`, puis collez le code suivant à la place :
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Assurez-vous d'avoir chargé le module `debug` en haut du fichier `app.js` à l'aide du code suivant :
-
-```js
-var debug = require('debug')('app4')
-```
-
-Ensuite, modifiez `"start": "node ./bin/www"` dans le fichier `package.json` en `"start": "node app.js"`.
-
-Vous avez à présent déplacé la fonctionnalité depuis `./bin/www` de nouveau
-dans `app.js`. Cette modification n'est pas recommandée, mais l'exercice vous aide à comprendre le mode de fonctionnement
-du fichier `./bin/www` et la raison pour laquelle le fichier `app.js` ne se lance plus seul.
diff --git a/fr/guide/migrating-5.md b/fr/guide/migrating-5.md
deleted file mode 100644
index 9cb36583a3..0000000000
--- a/fr/guide/migrating-5.md
+++ /dev/null
@@ -1,677 +0,0 @@
----
-layout: page
-title: Migration vers Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Migration vers Express 5
-
-<h2 id="overview">Présentation</h2>
-
-Express 5 n'est pas très différent d'Express 4 : les
-modifications apportées à l'API ne sont pas aussi importantes qu'entre
-les versions 3.0 et 4.0. Bien que l'API de base reste identique, des modifications radicales ont été apportées ; en d'autres termes, un programme Express 4 risque de ne pas fonctionner si
-vous le mettez à jour pour utiliser Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-Vous pouvez alors exécuter les tests automatisés pour voir les
-échecs et corriger les problèmes en fonction des mises à jour
-répertoriées ci-dessous. Après avoir traité les échecs de test,
-exécutez votre application pour détecter les erreurs qui se
-produisent. Vous saurez tout de suite si l'application utilise des
-méthodes ou des propriétés.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Modifications dans Express 5</h2>
-
-**Méthodes et propriétés supprimées**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Noms de méthodes au pluriel</a></li>
-  <li><a href="#leading">Signe deux-points de tête dans l'argument du
-nom pour app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Améliorations**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**Modifié**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Méthodes et propriétés supprimées
-
-Si vous utilisez une de ces méthodes ou propriétés dans votre
-application, elle tombera en panne. Vous devrez donc modifier votre
-application après la mise à jour vers la version 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 ne prend plus en charge la fonction
-`app.del()`. Si vous utilisez cette fonction, une
-erreur est émise. Pour enregistrer des routes HTTP DELETE, utilisez la fonction
-`app.delete()` à la place.
-
-Initialement, `del` était utilisé au lieu de
-`delete` car `delete` est un mot
-clé réservé dans JavaScript. Cependant, à partir d'ECMAScript 6,
-`delete` et les autres mots clés réservés peuvent
-être utilisés en toute légalité comme noms de propriété.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-La signature `app.param(fn)` servait à
-modifier le comportement de la fonction
-`app.param(name, fn)`. Elle est obsolète depuis la
-version 4.11.0 et Express 5 ne la prend plus en charge.
-
-<h3 id="plural">Noms de méthodes au pluriel</h3>
-
-Les noms de méthode suivants ont été mis au pluriel. Dans Express 4, l'utilisation des anciennes méthodes ont généré un avertissement
-d'obsolescence. Express 5 ne les prend plus du tout en charge :
-
-`req.acceptsLanguage()` est remplacé par
-`req.acceptsLanguages()`.
-
-`req.acceptsCharset()` est remplacé par
-`req.acceptsCharsets()`.
-
-`req.acceptsEncoding()` est remplacé par
-`req.acceptsEncodings()`.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Signe deux-points (:) de tête dans le nom de la
-fonction app.param(name, fn)</h3>
-
-Le signe deux-points (:) de tête dans le nom de la fonction
-`app.param(name, fn)` est une subsistance d'Express 3 et, pour des raisons de
-compatibilité avec les versions antérieures, Express 4 la prenait en
-charge avec un avis sur l'obsolescence. Express 5 l'ignore
-automatiquement et utilise le paramètre de nom sans le préfixer d'un
-signe deux-points.
-
-Cela n'affectera normalement pas votre code si vous lisez la documentation Express 4
-d'[app.param](/{{ page.lang }}/4x/api.html#app.param) car cela ne mentionne pas le signe deux-points de tête.
-
-<h3 id="req.param">req.param(name)</h3>
-
-Cette méthode potentiellement déroutante et dangereuse
-d'extraction des données de formulaire a été supprimée. Vous devrez
-désormais rechercher spécifiquement le nom du paramètre soumis dans
-l'objet `req.params`, `req.body` ou `req.query`.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 ne prend plus en charge la signature
-`res.json(obj, status)`. A la place, définissez le
-statut et enchaînez-le à la méthode
-`res.json()` comme suit :
-`res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 ne prend plus en charge la signature
-`res.jsonp(obj, status)`. A la place, définissez le
-statut et enchaînez-le à la méthode `res.jsonp()`
-comme suit : `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 ne prend plus en charge la signature
-`res.send(obj, status)`. A la place, définissez le
-statut et enchaînez-le à la méthode `res.send()`
-comme suit : `res.status(status).send(obj)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 ne prend plus en charge la signature <code>res.send(<em>statut</em>)</code>, où _`statut`_
-est un nombre. A la place, utilisez la fonction
-`res.sendStatus(statusCode)`
-qui définit le code de statut de l'en-tête de réponse HTTP et envoie
-la version texte du code: "Not Found", "Internal Server Error", etc.
-Si vous devez envoyer un nombre à l'aide de la fonction `res.send()`,
-mettez ce nombre entre guillemets pour qu'Express ne l'interprète pas
-comme une tentative d'utilisation de l'ancienne signature non prise en charge.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-La fonction `res.sendfile()` a été remplacée
-par une
-version CamelCase `res.sendFile()` dans Express 5.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Elle est obsolète depuis la
-version 4.11.0 et Express 5 ne la prend plus en charge.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Modifié
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. Par exemple :
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-Par exemple :
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-L'objet `app.router`, qui a été supprimé dans Express 4, est revenu dans Express 5. Dans la version, cet objet
-n'est qu'une référence dans le routeur Express de base, contrairement à Express 3, où une application devait le charger explicitement.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-Dans Express 4, la `req.host` retirait de
-manière incorrecte le numéro de port s'il était présent. Dans Express 5, ce numéro de port est conservé.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Améliorations
-
-<h3 id="res.render">res.render()</h3>
-
-Cette méthode impose désormais un comportement asynchrone pour
-tous les moteurs de vue. Cela évite les bogues générés par les
-moteurs de vue qui avaient une implémentation synchrone et qui
-ne prenaient pas en compte l'interface recommandée.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/fr/guide/overriding-express-api.md b/fr/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/fr/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/fr/guide/routing.md b/fr/guide/routing.md
deleted file mode 100644
index 2b6e7430e0..0000000000
--- a/fr/guide/routing.md
+++ /dev/null
@@ -1,410 +0,0 @@
----
-layout: page
-title: Routage Express
-description: Apprenez à définir et à utiliser des routes dans les applications Express.js, y compris les méthodes de routes, les chemins de routes, les paramètres et l’utilisation de Router pour un routage modulaire.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# Routage
-
-_Routage_ fait référence à la définition de points finaux d'application (URI) et à la façon dont ils répondent aux demandes client.
-Pour une introduction au routage, voir [Basic routing](/{{ page.lang }}/starter/basic-routing.html).
-
-Vous définissez le routage à l’aide des méthodes de l’objet app d’Express correspondant aux méthodes HTTP :
-par exemple, `app.get()` pour les requêtes GET et `app.post` pour les requêtes POST. Pour la liste complète,
-voir [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). Vous pouvez également utiliser [app.all()](/{{ page.lang }}/5x/api.html#app.all) pour gérer toutes les méthodes HTTP et [app.use()](/{{ page.lang }}/5x/api.html#app.use) spécifier le middleware comme fonction de rappel (Voir [Utilisation du middleware](/{{ page.lang }}/guide/using-middleware.html) pour plus de détails).
-
-Ces méthodes de routage spécifient une fonction de rappel (parfois "appelée fonction de gestion") qui est appelée lorsque l'application reçoit une requête correspondant à la route (point de terminaison) et à la méthode HTTP spécifiées. Autrement dit, l'application "écoute" les requêtes qui correspondent à la ou aux routes et à la ou aux méthodes spécifiées, et lorsqu'une correspondance est détectée, elle appelle la fonction de rappel définie.
-
-En réalité, les méthodes de routage peuvent accepter plusieurs fonctions de rappel comme arguments.
-Lorsqu'il y a plusieurs fonctions de rappel, il est important de fournier `next` comme argument à la fonction de rappel, puis d'appeler `next()` dans le corps de la fonction afin de passer le contrôle à la fonction de rappel suivante.
-
-Le code suivant est un exemple de routage très basique.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Méthodes de routage</h2>
-
-Une méthode de routage est dérivée de l'une des méthodes HTTP, et est liée à une instance de la classe `express`.
-
-Le code suivant est un exemple de routes qui sont définies pour les méthodes GET et POST jusqu'à la route de l'application.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express prend en charge des méthodes correspondant à toutes les méthodes de requête HTTP : `get`, `post`, etc. Pour la liste complète, voir [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-Pour la liste complète, voir [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-Il existe une méthode de routage spéciale, `app.all()`, qui n'est pas dérivée d'une méthode HTTP. Cette méthode est utilisée pour charger des fonctions middleware à un chemin d'accès pour toutes les méthodes de demande.
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Chemins de routage</h2>
-
-Les chemins de routage, combinés à une méthode de demande, définissent les noeuds finaux sur lesquels peuvent être effectuées les demandes. Les chemins de routage peuvent être des chaînes, des masques de chaîne ou des expressions régulières.
-
-{% capture caution-character %} Dans Express 5, les caractères `?`, `+`, `*`, `[]`, et `()` sont traités différemment par rapport à la version 4. Veuillez consulter le [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) pour plus d'informations.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}Dans Express 4, les caractères d'expression régulière tels que `$` doivent être échappés avec un `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express utilise [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) pour faire correspondre les chemins de routes ; consultez la documentation de path-to-regexp pour connaître toutes les possibilités de définition des chemins de routes. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) est un outil pratique permettant de tester des routes Express de base, bien qu'il ne prenne pas en charge le filtrage par motif.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Les chaînes de requête (query strings) ne font pas partie du chemin de la route.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Il s'agit d'exemples de chemins de routage basés sur des chaînes.
-
-Ce chemin de routage fera correspondre des demandes à la route racine, `/`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-Ce chemin de routage fera correspondre des demandes à `/about`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-Ce chemin de routage fera correspondre des demandes à `/random.text`.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Il s'agit d'exemples de chemins de routage basés sur des masques de chaîne.
-
-{% capture caution-string-patterns %} Les motifs de chaînes (string patterns) ne fonctionnent plus dans Express 5. Veuillez consulter [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) pour plus d'informations.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-Ce chemin de routage fait correspondre `acd` et `abcd`.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-Ce chemin de routage fait correspondre `abcd`, `abbcd`, `abbbcd`, etc.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-Ce chemin de routage fait correspondre `abcd`, `abxcd`, `abRABDOMcd`, `ab123cd`, etc.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-Ce chemin de routage fait correspondre `/abe` et `/abcde`.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Exemples de chemins de routage basés sur des expressions régulières :
-
-Ce chemin de routage fera correspondre tout élément dont le nom de chemin comprend la lettre "a".
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-Ce chemin de routage fera correspondre `butterfly` et `dragonfly`, mais pas `butterflyman`, `dragonfly man`, etc.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">
-Les chaînes de requête ne font pas partie du chemin de routage.
-</h2>
-
-Les paramètres de route sont des segments nommés de l'URL utilisés pour capturer les valeurs spécifiées à leur position dans l'URL. Les valeurs capturées sont placées dans l'objet `req.params`, avec le nom du paramètre de route spécifié dans le chemin comme clé correspondante.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-Pour définir des routes avec des paramètres de route, il suffit de spécifier les paramètres dans le chemin de la route comme indiqué ci-dessous.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Le nom des paramètres de route doit être composé de "caractères alphanumériques" ([A-Za-z0-9_]).</div>
-
-Comme le tiret (`-`) et le point (`.`) sont interprétés littéralement, ils peuvent être utilisés avec les paramètres de route à des fins pratiques.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-Dans Express 5, les caractères Regexp ne sont pas pris en chage dans les chemins de route. Pour plus d'informations, veuillez consulter le [guide de migration](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-Pour mieux contrôler la chaîne exacte pouvant être capturée par un paramètre de route, vous pouvez ajouter une expression régulière entre parenthèses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Comme l'expression régulière fait généralement partie d'une chaîne littérale, veillez à échapper tout caractère `\` avec un antislash supplémentaire, par exemple `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-Dans Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">le caractère `*` dans une expression régulière n'est pas interprété de manière habituelle</a>. Comme solution de contournement, utilisez `{0,}` au lieu de `*`. Cela sera probablement corrigé dans Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Gestionnaires de routage</h2>
-
-Vous pouvez fournir plusieurs fonctions de rappel qui se comportent comme des [middleware](/{{ page.lang }}/guide/using-middleware.html) pour gérer une demande. La seule exception est que ces fonctions de rappel peuvent faire appel à `next('route')` pour ignorer les rappels de route restants. Vous pouvez utiliser ce mécanisme pour imposer des conditions préalables sur une route, puis passer aux routes suivantes si aucune raison n'est fournie pour traiter la route actuelle.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-Dans cet exemple :
-
-- `GET /user/5` → géré par la première route → envoie "User 5"
-- `GET /user/0` → la première route appelle `next('route')`, en passant à la prochaine route correspondant à `/user/:id`
-
-Les gestionnaires de route se trouvent sous la forme d'une fonction, d'un tableau de fonctions ou d'une combinaison des deux, tel qu'indiqué dans les exemples suivants.
-
-Une fonction de rappel unique peut traiter une route. Par exemple :
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-Plusieurs fonctions de rappel peuvent traiter une route (n'oubliez pas de spécifier l'objet `next`). Par exemple :
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-Un tableau de fonctions de rappel peut traiter une route. Par exemple :
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-Une combinaison de fonctions indépendantes et des tableaux de fonctions peuvent gérer une route. Par exemple :
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Méthodes de réponse</h2>
-
-Les méthodes de l'objet de réponse (`res`) décrites dans le tableau suivant peuvent envoyer une réponse au client, et mettre fin au cycle de demande-réponse. Si aucune de ces méthodes n'est appelée par un gestionnaire de routage, la demande du client restera bloquée.
-
-| Méthode                                                                                                                                                                                                                   | Description                                                                                                                   |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | Vous invite à télécharger un fichier.                                                                         |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | Met fin au processus de réponse.                                                                              |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | Envoie une réponse JSON.                                                                                      |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | Envoie une réponse JSON avec une prise en charge JSONP.                                                       |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | Redirige une demande.                                                                                         |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Génère un modèle de vue.                                                                                      |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | Envoie une réponse de divers types.                                                                           |
-| [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile)     | Envoyer un fichier sous forme de flux octet.                                                                  |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Définit le code de statut de réponse et envoie sa représentation sous forme de chaîne comme corps de réponse. |
-
-<h2 id="app-route">app.route()</h2>
-
-Vous pouvez créer des gestionnaires de routage sous forme de chaîne pour un chemin de routage en utilisant `app.route()`.
-Etant donné que le chemin est spécifié à une seul emplacement, la création de routes modulaires est utile car elle réduit la redondance et les erreurs. Pour plus d'informations sur les routes, voir la [documentation Router()](/{{ page.lang }}/4x/api.html#router).
-
-Voici quelques exemples de gestionnaires de chemin de chaînage définis à l'aide de `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Utilisez la classe `express.Router` pour créer des gestionnaires de route modulaires et pouvant être montés. Une instance `Router` est un middleware et un système de routage complet ; pour cette raison, elle est souvent appelée "mini-app".
-
-L'exemple suivant créé une routeur en tant que module, charge une fonction middleware, définit des routes et monte le module de routeur sur un chemin dans l'application principale.
-
-Créez un fichier de routage nommé `birds.js` dans le répertoire app, avec le contenu suivant :
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Puis, chargez le module de routage dans l'application :
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-L'application pourra dorénavant gérer des demandes dans `/birds` et `/birds/about`, et appeler la fonction middleware `timeLog` spécifique à la route.
-
-Mais si la route parente `/birds` possède des paramètres de chemin, ils ne seront pas accessibles par défaut depuis les sous-routes. Pour qu'ils soient accessibles, vous devez passer l'option `mergeParams` au constructeur de Router [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/fr/guide/using-middleware.md b/fr/guide/using-middleware.md
deleted file mode 100644
index 8695b3f1e3..0000000000
--- a/fr/guide/using-middleware.md
+++ /dev/null
@@ -1,278 +0,0 @@
----
-layout: page
-title: Utilisation de middleware Express
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# Utilisation de middleware
-
-Express est une infrastructure web middleware et de routage, qui a des fonctions propres minimes : une application Express n'est ni plus ni moins qu'une succession d'appels de fonctions middleware.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
-
-Les fonctions middleware effectuent les tâches suivantes :
-
-- Exécuter tout type de code.
-- Apporter des modifications aux objets de demande et de réponse.
-- Terminer le cycle de demande-réponse.
-- Appeler la fonction middleware suivant dans la pile.
-
-Si la fonction middleware en cours ne termine pas le cycle de demande-réponse, elle doit appeler la fonction `next()` pour transmettre le contrôle à la fonction middleware suivant. Sinon, la demande restera bloquée.
-
-Une application Express peut utiliser les types de middleware suivants :
-
-- [Middleware niveau application](#middleware.application)
-- [Middleware niveau routeur](#middleware.router)
-- [Middleware de traitement d'erreurs](#middleware.error-handling)
-- [Middleware intégré](#middleware.built-in)
-- [Middleware tiers](#middleware.third-party)
-
-Vous pouvez charger le middleware niveau application et niveau routeur à l'aide d'un chemin de montage facultatif.
-Vous pouvez également charger une série de fonctions middleware ensemble, ce qui crée une sous-pile du système de middleware à un point de montage.
-
-<h2 id='middleware.application'>Middleware niveau application</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-Cet exemple illustre une fonction middleware sans chemin de montage. La fonction est exécutée à chaque fois que l'application reçoit une demande.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-Cet exemple illustre une fonction middleware montée sur le chemin `/user/:id`. La fonction est exécutée pour tout type de
-demande HTTP sur le chemin`/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Cet exemple illustre une route et sa fonction de gestionnaire (système de middleware). La fonction gère les demandes GET adressées au chemin `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Voici un exemple de chargement d'une série de fonctions middleware sur un point de montage, avec un chemin de montage.
-Il illustre une sous-pile de middleware qui imprime les infos de demande pour tout type de demande HTTP adressée au chemin `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Les gestionnaires de routage vous permettent de définir plusieurs routes pour un chemin. L'exemple ci-dessous définit deux routes pour les demandes GET adressées au chemin `/user/:id`. La deuxième route ne causera aucun problème, mais ne sera jamais appelée puisque la première route boucle le cycle demande-réponse.
-
-Cet exemple illustre une sous-pile de middleware qui gère les demandes GET adressées au chemin `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-Pour ignorer les fonctions middleware issues d'une pile de middleware de routeur, appelez `next('route')` pour passer le contrôle à la prochaine route.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-Cet exemple illustre une sous-pile de middleware qui gère les demandes GET adressées au chemin `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-Voici un exemple d'utilisation de la fonction middleware `express.static` avec un objet options élaboré :
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Middleware niveau routeur</h2>
-
-Le middleware niveau routeur fonctionne de la même manière que le middleware niveau application, à l'exception près qu'il est lié à une instance de `express.Router()`.
-
-```js
-const router = express.Router()
-```
-
-Chargez le middleware niveau routeur par le biais des fonctions `router.use()` et `router.METHOD()`.
-
-Le code d'exemple suivant réplique le système de middleware illustré ci-dessus pour le middleware niveau application, en utilisant un middleware niveau routeur :
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-Pour obtenir plus de détails sur la fonction `serve-static` et ses options, reportez-vous à la documentation [serve-static](https://github.com/expressjs/serve-static).
-
-Cet exemple illustre une sous-pile de middleware qui gère les demandes GET adressées au chemin `/user/:id`.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Middleware de traitement d'erreurs</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Le middleware de traitement d'erreurs comporte toujours *quatre* arguments. Vous devez fournir quatre arguments pour l'identifier comme une fonction middleware de traitement d'erreurs. Même si vous n'avez pas besoin d'utiliser l'objet `next`, vous devez le spécifier pour maintenir la signature. Sinon, l'objet `next` sera interprété comme un middleware ordinaire et n'arrivera pas à gérer les erreurs.
-</div>
-
-Définissez les fonctions middleware de traitement d'erreurs de la même façon que d'autres fonctions middleware, à l'exception près qu'il faudra 4 arguments au lieu de 3, et plus particulièrement avec la signature `(err, req, res, next)`) :
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Pour obtenir des détails sur le middleware de traitement d'erreurs, reportez-vous à : [Traitement d'erreurs](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Middleware intégré</h2>
-
-Depuis la version 4.x, Express ne dépend plus de [Connect](https://github.com/senchalabs/connect). A l'exception de `express.static`, toutes les fonctions middleware
-précédemment incluses à Express' font désormais partie de modules distincts. Veuillez vous reporter à [la liste des fonctions middleware](https://github.com/senchalabs/connect#middleware).
-
-La seule fonction middleware intégrée dans Express est `express.static`.
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Middleware tiers</h2>
-
-Utilisez un middleware tiers pour ajouter des fonctionnalités à des applications Express.
-
-Installez le module Node.js pour la fonctionnalité requise, puis chargez-le dans votre application au niveau application ou au niveau router.
-
-L'exemple suivant illustre l'installation et le chargement de la fonction middleware d'analyse de cookie `cookie-parser`.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Pour obtenir une liste non exhaustive des fonctions middleware tiers utilisées couramment avec Express, reportez-vous à : [Middleware tiers](../resources/middleware.html).
diff --git a/fr/guide/using-template-engines.md b/fr/guide/using-template-engines.md
deleted file mode 100644
index 80dbe62570..0000000000
--- a/fr/guide/using-template-engines.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: page
-title: Utilisation de moteurs de modèles avec Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Utilisation de moteurs de modèles avec Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, le répertoire dans lequel se trouvent les fichiers modèles. Par exemple : `app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, le moteur de modèle à utiliser. Par exemple : `app.set('view engine', 'pug')`
-
-Ensuite, installez le package npm du moteur de modèle correspondant :
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Les moteurs de modèles conformes à Express tels que Pug exportent une fonction nommée `__express(filePath, options, callback)`, qui est appelée par la fonction `res.render()` pour générer le code de modèle.
-
-Certaines moteurs de modèles ne suivent pas cette convention. La bibliothèque [Consolidate.js](https://www.npmjs.org/package/consolidate) suit cette convention en mappant tous les moteurs de modèles Node.js répandus, et fonctionne donc parfaitement avec Express.
-
-</div>
-
-Une fois le moteur de vue défini, vous n'avez pas à spécifier le moteur ou à charger le module de moteur de modèles dans votre application ; Express charge le module en interne, comme indiqué ci-dessous (pour l'exemple ci-dessus).
-
-```js
-app.set('view engine', 'pug')
-```
-
-Créez un fichier de modèle Pug nommé `index.pug` dans le répertoire `views`, avec le contenu suivant :
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Puis, créez une route pour générer le fichier `index.pug`. Si la propriété `view engine` n'est pas définie, vous devez spécifier l'extension du fichier `view`. Sinon, vous pouvez l'omettre.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Lorsque vous faites une demande vers la page d'accueil, le fichier `index.pug` est généré en HTML.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/fr/guide/writing-middleware.md b/fr/guide/writing-middleware.md
deleted file mode 100644
index 6caada7d64..0000000000
--- a/fr/guide/writing-middleware.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: Ecriture de middleware utilisable dans les applications Express
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Ecriture de middleware utilisable dans les applications Express
-
-<h2>Présentation</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
-
-Les fonctions middleware effectuent les tâches suivantes :
-
-- Exécuter tout type de code.
-- Apporter des modifications aux objets de demande et de réponse.
-- Terminer le cycle de demande-réponse.
-- Appeler le middleware suivant dans la pile.
-
-Si la fonction middleware en cours ne termine pas le cycle de demande-réponse, elle doit appeler la fonction `next()` pour transmettre le contrôle à la fonction middleware suivant. Sinon, la demande restera bloquée.
-
-L'exemple suivant montre les éléments d'un appel de fonction middleware:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">Méthode HTTP à laquelle la fonction middleware s'applique.</div></tbody>
-
-<div class="callout" id="callout2">Chemin (route) auquel la fonction middleware s'applique.</div>
-
-<div class="callout" id="callout3">Fonction de middleware.</div>
-
-<div class="callout" id="callout4">Argument de rappel à la fonction middleware, appelée "next" par convention.</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Exemple</h2>
-
-Voici un exemple d'une application Express "Hello World" simple, pour laquelle vous allez définir deux fonctions middleware :
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Voici un exemple simple de fonction middleware appelée "myLogger". Cette fonction imprime simplement "LOGGED" lorsqu'une demande traverse l'application. La fonction middleware est affectée à une variable nommée `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Notice the call above to `next()`. Notez l'appel ci-dessus de la fonction `next()`,  qui appelle la fonction middleware suivant dans l'application.
-La fonction `next()` ne fait pas partie du Node.js ou de l'API Express, mais c'est le troisième argument qui est transmis à la fonction middleware. La fonction `next()` peut porter n'importe quel nom, mais par convention elle est toujours appelée "next".
-Pour éviter toute confusion, il est préférable de respecter cette convention.
-</div>
-
-Pour charger la fonction middleware, appelez `app.use()` en spécifiant la fonction middleware.
-Par exemple, le code suivant charge la fonction middleware `myLogger` avant la route au chemin racine (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Chaque fois que l'application reçoit une demande, elle imprime le message "LOGGED" sur le terminal.
-
-L'ordre de chargement des middleware est important : les fonctions middleware chargées en premier sont également exécutées en premier.
-
-Si `myLogger` est chargé après la route au chemin racine, la demande ne l'atteindra jamais et l'application n'imprimera pas "LOGGED", car le gestionnaire de route du chemin racine interrompra le cycle de demande-réponse.
-
-La fonction middleware `myLogger` imprime simplement un message, puis traite la demande à la fonction middleware suivant dans la pile en appelant la fonction `next()`.
-
-<h3>Middleware function requestTime</h3>
-
-L'exemple suivant ajoute une propriété appelée `requestTime` à l'objet Request. Nous nommerons cette fonction middleware "requestTime".
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-L'application utilise désormais la fonction middleware `requestTime`. De plus, la fonction callback de la route du chemin racine utilise la propriété que la fonction middleware ajoute à `req` (l'objet Request).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-Si vous effectuez une demande à la racine de l'application, cette dernière affiche maintenant l'horodatage de la demande dans le navigateur.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Puisque vous avez accès à l'objet Request, à l'objet Response, à la fonction middleware suivant dans la pile et à l'API Node.js complète, le champ des possibles avec les fonctions middleware est infini.
-
-Pour plus d'informations sur les middleware Express, voir [Utilisation de middleware Express](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/fr/index.md b/fr/index.md
deleted file mode 100644
index 9e755d243a..0000000000
--- a/fr/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/fr/resources/community.md b/fr/resources/community.md
deleted file mode 100644
index 12904a9584..0000000000
--- a/fr/resources/community.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-layout: page
-title: Communauté Express
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# Communauté
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-Notre communauté si animée a créé une large gamme d'extensions,
-[modules middleware](/{{ page.lang }}/resources/middleware.html) et des
-infrastructures de niveau supérieur.
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Problèmes
-
-Si vous êtes tombé sur ce que vous pensez être un bug, ou si vous voulez seulement faire une demande
-de fonctionnalité, ouvrez un ticket dans la [file d'attente d'incidents](https://github.com/expressjs/express/issues).
-
-## Exemples
-
-Regardez des douzaines d'[exemples](https://github.com/expressjs/express/tree/master/examples) d'applications Express dans le référentiel qui couvre tous les sujets, en allant de l'authentification et la conception de l'interface de
-programme d'application jusqu'à l'intégration du moteur modèle.
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/fr/resources/contributing.md b/fr/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/fr/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/fr/resources/glossary.md b/fr/resources/glossary.md
deleted file mode 100644
index e8379279bc..0000000000
--- a/fr/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Glossaire Express
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# Glossaire
-
-### application
-
-En général, un ou plusieurs programmes conçus pour réaliser des opérations dans un but précis.  Dans le contexte d'Express, il s'agit d'un programme qui utilise l'API Express s'exécutant sur la plateforme Node.js.  Peut également faire référence à un [objet d'application](/{{ page.lang }}/api.html#express).
-
-### API
-
-Interface de programme d'application. Développez l'abréviation lorsqu'elle est utilisée pour la première fois.
-
-### Express
-
-Infrastructure Web minimaliste, souple et rapide pour les applications Node.js. En général, on préfère utiliser "Express" que "Express.js," bien que ce dernier soit acceptable.
-
-### libuv
-
-Bibliothèque de prise en charge multiplateforme qui se centralise sur les E-S asynchrones, développée principalement pour être utilisée par Node.js.
-
-### middleware
-
-Fonction qui est appelée par la couche de routage Express avant le gestionnaire de demande final, et qui se trouve entre une demande brute et la route finale prévue. Quelques points subtiles de terminologie autour des middleware :
-
-- `var foo = require('middleware')` est appelé _demande_ ou _utilisation_ d'un module Node.js. Ensuite, l'instruction `var mw = foo()`  renvoie généralement le middleware.
-- `app.use(mw)` est appelé _ajout du middleware à la pile de processus global_.
-- `app.get('/foo', mw, function (req, res) { ... })` est appelé _ajout du middleware à la pile de processus "GET /foo"_.
-
-### Node.js
-
-Plateforme logicielle utilisée pour générer des applications réseau évolutives. Node.js utilise JavaScript comme langage de script, et atteint un rendement élevé via une E-S non bloquante et une boucle d'événements à une seule unité d'exécution. Voir [nodejs.org](http://nodejs.org/). **Note d'utilisation** : En général, "Node.js," "Node" par la suite.
-
-### open-source, open source
-
-Lorsqu'il est utilisé comme adjectif, utilisez la forme avec le trait d'union. Par exemple : "Il s'agit d'un logiciel open-source." Voir [Open-source software sur Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### demande
-
-Demande HTTP. Un client soumet un message de demande HTTP à un serveur, qui renvoie une réponse.  La demande doit utiliser une des [méthodes de demande](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) telles que GET, POST...
-
-### réponse
-
-Réponse HTTP. Un serveur renvoie un message de réponse HTTP au client. La réponse contient des informations relatives à l'état d'achèvement de la demande et peut également contenir le contenu demandé dans le corps du message.
-
-### route
-
-Partie de l'URL qui permet d'identifier une ressource. Par exemple, dans `http://foo.com/products/id`, "/products/id" est la route.
-
-### routeur
-
-Voir [routeur](/{{ page.lang }}/4x/api.html#router) dans Référence de l'API.
diff --git a/fr/resources/middleware.md b/fr/resources/middleware.md
deleted file mode 100644
index 4be979f928..0000000000
--- a/fr/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Middleware Express
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Middleware Express
-
-Voici quelques modules de middleware Express :
-
-| [express-slash](https://github.com/ericf/express-slash) : module Express Middleware destiné aux personnes qui sont strictes sur le respect des barres obliques. | Description                                                                                                                         |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)                                                                                                                             | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)                                                                                                                             | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)                                                                                                                             | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)                                                                                                                         | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)                                                                                                                       | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                                                                                                                                           | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)                                                                                                                           | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html)                                                                                                                     | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                                                                                                                                       | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                                                                                                                                       | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)                                                                                                                         | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)                                                                                                                         | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)                                                                                                                             | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)                                                                                                                           | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                                                                                                                                     | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                                                                                                                                     | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                                                                                                                                         | Create virtual domains.                                                                                             |
-
-## Pour découvrir plus de modules de middleware, voir :
-
-[view-helpers](https://github.com/madhums/node-view-helpers) : module Express Middleware qui offre des méthodes d'auxiliaires courantes destinées aux vues.
-
-{% include community-caveat.html %}
-
-| [express-slash](https://github.com/ericf/express-slash) : module Express Middleware destiné aux personnes qui sont strictes sur le respect des barres obliques. | Description                                                                                                                                                                                   |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet) : module qui aide à sécuriser vos applications en définissant divers en-têtes HTTP.                                | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport) : module de middleware Express dédié à l'authentification.                                                  | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/fr/resources/middleware/body-parser.md b/fr/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/fr/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/fr/resources/middleware/compression.md b/fr/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/fr/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/fr/resources/middleware/connect-rid.md b/fr/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/fr/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/fr/resources/middleware/cookie-parser.md b/fr/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/fr/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/fr/resources/middleware/cookie-session.md b/fr/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/fr/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/fr/resources/middleware/cors.md b/fr/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/fr/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/fr/resources/middleware/errorhandler.md b/fr/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/fr/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/fr/resources/middleware/method-override.md b/fr/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/fr/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/fr/resources/middleware/morgan.md b/fr/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/fr/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/fr/resources/middleware/multer.md b/fr/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/fr/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/fr/resources/middleware/response-time.md b/fr/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/fr/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/fr/resources/middleware/serve-favicon.md b/fr/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/fr/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/fr/resources/middleware/serve-index.md b/fr/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/fr/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/fr/resources/middleware/serve-static.md b/fr/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/fr/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/fr/resources/middleware/session.md b/fr/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/fr/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/fr/resources/middleware/timeout.md b/fr/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/fr/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/fr/resources/middleware/vhost.md b/fr/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/fr/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/fr/resources/utils.md b/fr/resources/utils.md
deleted file mode 100644
index 4c1a17b886..0000000000
--- a/fr/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | Description                                                                                                                                                                                                                |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/fr/starter/basic-routing.md b/fr/starter/basic-routing.md
deleted file mode 100644
index 4c1404c08d..0000000000
--- a/fr/starter/basic-routing.md
+++ /dev/null
@@ -1,69 +0,0 @@
----
-layout: page
-title: Routage de base Express
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# Routage de base
-
-_Routage_ fait référence à la détermination de la façon dont une application répond à un
-nœud final spécifique, c'est-à-dire un URI (ou chemin) et une méthode de requête HTTP (GET, POST, etc.).
-
-Chaque route peut avoir une ou plusieurs fonctions de gestionnaire, qui sont exécutées lorsque la route est mise en correspondance.
-
-La définition de la route utilise la structure suivante :
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Où :
-
-- `app` est une instance d'`express`.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` est un chemin sur le serveur.
-- `HANDLER` est la fonction exécutée lorsque la route est mise en correspondance.
-
-<div class="doc-box doc-notice" markdown="1">
-Ce tutoriel suppose qu'une instance d'`express` appelée `app` soit créée et que le serveur soit en cours d'exécution. Si vous ne savez pas créer et démarrer une application, reportez-vous à l'[exemple Hello world](/{{ page.lang }}/starter/hello-world.html).
-</div>
-
-Les exemples suivants illustrent la définition de routes simples.
-
-Réponse `Hello World!` sur la page d'accueil :
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Réponse à une demande PUT sur la route `/user` :
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Réponse à une demande DELETE sur la route `/user` :
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-Pour plus de détails sur le routage, reportez-vous au [guide de routage](/{{ page.lang }}/guide/routing.html).
-
diff --git a/fr/starter/examples.md b/fr/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/fr/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/fr/starter/faq.md b/fr/starter/faq.md
deleted file mode 100644
index d234897893..0000000000
--- a/fr/starter/faq.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-layout: page
-title: FAQ Express
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# FAQ
-
-## Comment puis-je structurer mon application ?
-
-Il n'existe pas de réponse définitive à cette question. La réponse dépend
-de l'échelle de votre application et de l'équipe qui est impliquée. Pour être aussi
-flexible que possible, Express ne fait aucune supposition en terme de structure.
-
-Les routes et la logique propre à l'application peuvent être opérationnelles dans autant de fichiers
-que vous le souhaitez, et dans les structures de répertoire que vous préférez. Pour plus d'inspiration,
-consultez les exemples suivants :
-
-- [Listes de routes](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Feuille de route](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [Contrôleurs de style MVC](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Il existe aussi des extensions tiers pour Express, permettant de simplifier certains de ces modèles :
-
-- [Routage ingénieux](https://github.com/expressjs/express-resource)
-
-## Comment puis-je définir des modèles ?
-
-Express ne connaît pas les bases de données. Ce concept est
-laissé aux modules Node tiers, vous permettant ainsi
-d'interagir avec quasiment toutes les bases de données.
-
-Voir [LoopBack](http://loopback.io) pour obtenir une infrastructure basée sur Express et centrée autour de modèles.
-
-## Comment puis-je authentifier des utilisateurs ?
-
-L'authentification est une autre partie complexe dans laquelle Express
-ne s'aventure pas. Vous pouvez utiliser tous les schémas d'authentification que vous voulez.
-Pour un schéma simple de type nom d'utilisateur/mot de passe, voir [cet exemple](https://github.com/expressjs/express/tree/master/examples/auth).
-
-## Quels moteurs de modèles Express prend-il en charge ?
-
-Express prend en charge tous les moteurs de modèles conformes à la signature `(path, locals, callback)`.
-Pour normaliser les interfaces de moteur de modèles et la mise en cache, voir le
-projet [consolidate.js](https://github.com/visionmedia/consolidate.js)
-pour la prise en charge. Des moteurs de modèles non répertoriés peuvent encore prendre en charge la signature Express.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## Comment puis-je gérer des réponses 404 ?
-
-Dans Express, étant donné que les réponses 404 ne sont pas le résultat d'une erreur,
-le middleware de traitement d'erreurs ne les traite pas. Ce comportement est
-dû au fait qu'une réponse 404 indique simplement l'absence d'un travail supplémentaire à effectuer. En d'autres termes, Express a exécuté toutes les routes et fonctions middleware,
-et aucune n'a répondu. Tout ce que vous avez à faire est
-d'ajouter une fonction middleware à la toute fin de la pile (en-dessous de toutes les autres fonctions)
-pour gérer une réponse 404 :
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## Comment puis-je configurer un gestionnaire d'erreurs ?
-
-Vous pouvez définir un middleware de traitement d'erreurs de la même façon qu'un autre middleware,
-à l'exception qu'il faudra 4 arguments au lieu de 3 ; et plus particulièrement avec la signature `(err, req, res, next)` :
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Pour plus d'informations, voir [Traitement d'erreurs](/{{ page.lang }}/guide/error-handling.html).
-
-## Comment puis-je générer un fichier HTML simple ?
-
-Vous ne pouvez pas ! Il n'est pas nécessaire de "générer" un fichier HTML avec la fonction `res.render()`.
-Si vous avez un fichier spécifique, utilisez la fonction `res.sendFile()`.
-Si vous utilisez plusieurs actifs d'un répertoire, utilisez la fonction middleware `express.static()`.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/fr/starter/generator.md b/fr/starter/generator.md
deleted file mode 100644
index 36ed111830..0000000000
--- a/fr/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Générateur d'applications Express
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Générateur d'applications Express
-
-Utilisez l'outil de générateur d'applications, `express`, pour créer rapidement un squelette d'application.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Affichez les options de commande à l'aide de l'option `-h` :
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-Par exemple, ce code crée une application Express nomée _myapp_. L'application sera crée dans le dossier _myapp_, lui meme placé dans le repertoir de travail courant. Le moteur de vue sera configuré avec <a href="pugjs.org" target="_blank" title="Documentation Pug">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-Ensuite, installez les dépendances :
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-Sous MacOS ou Linux, exécutez l'application à l'aide de la commande suivante :
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-Sous Windows, utilisez la commande suivante :
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-Installez `express` à l'aide de la commande suivante :
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-Ensuite, chargez 'http://hôte_local:3000/' dans votre navigateur pour accéder à l'application.
-
-L'application générée possède la structure de répertoire suivante :
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-La structure d'application créée par le générateur est l'une des nombreuses manières possibles de structurer les applications Express. Vous avez toute latitude pour l'utiliser ou la modifier en fonction de vos besoins.
-</div>
\ No newline at end of file
diff --git a/fr/starter/hello-world.md b/fr/starter/hello-world.md
deleted file mode 100644
index 9dbd498fe4..0000000000
--- a/fr/starter/hello-world.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-layout: page
-title: Exemple "Hello world" Express
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Exemple Hello world
-
-<div class="doc-box doc-info" markdown="1">
-Il s'agit de l'application Express la plus simple que vous puissiez créer. Cette application ne contient qu'un seul fichier, c'est-à-dire *tout l'inverse* de ce que vous obtiendriez avec le
-[générateur Express](/{{ page.lang }}/starter/generator.html), qui crée l'échafaudage d'une application entière, avec des fichiers JavaScript, des modèles <a href="pugjs.org" target="_blank" title="Documentation Pug">Pug</a> et des sous-répertoires pour divers motifs.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-L'application démarre un serveur et écoute le port 3000 à la recherche de connexions. L'application répond "Hello World!" aux demandes adressées
-à l'URL racine (`/`) ou à la _route_ racine. Pour tous les autres chemins d'accès, elle répondra par **404 Not Found**.
-
-### Running Locally
-
-Premièrement, créez un répertoire appelé `myapp`, rendez-vous dedans et exécutez la commande `npm init`. Ensuite, installez `express` en tant que dépendance en suivant les instructions du [guide d'installation](/{{ page.lang }}/starter/installing.html).
-
-Dans le répertoire `myapp`, créez un fichier appelé `app.js` et ajoutez le code suivant :
-
-<div class="doc-box doc-notice" markdown="1">
-Les objets `req` (demande) et `res` (réponse) sont exactement les mêmes que ceux que Node fournit, vous pouvez donc appeler
-`req.pipe()`, `req.on('data', callback)` et tout autre objet sans recourir à Express.
-</div>
-
-Exécutez l'application avec la commande suivante :
-
-```bash
-$ node app.js
-```
-
-Puis chargez [http://localhost:3000/](http://localhost:3000/) dans un navigateur pour consulter le résultat.
\ No newline at end of file
diff --git a/fr/starter/installing.md b/fr/starter/installing.md
deleted file mode 100644
index b893475347..0000000000
--- a/fr/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Installation d'Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# Installation
-
-En supposant que [Node.js](https://nodejs.org/) est déjà installé, créez un répertoire pour héberger votre application et faites-en votre répertoire de travail.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Utilisez la commande `npm init` afin de créer un fichier `package.json` pour votre application.
-Pour plus d'informations sur le fonctionnement du fichier `package.json`, voir [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-Cette commande vous invite à fournir un certain nombre d'informations, telles que le nom et la version de votre application.
-Pour le moment, vous pouvez simplement appuyer sur la touche RETURN pour accepter les valeurs par défaut, à l'exception de ce qui suit :
-
-```
-entry point: (index.js)
-```
-
-Entrez `app.js` ou un nom de votre choix pour le fichier principal. Si vous souhaitez que le nom soit `index.js`, appuyez sur la touche RETURN pour accepter le nom de fichier par défaut suggéré.
-
-Installez ensuite Express dans le répertoire `myapp`, puis sauvegardez-le dans la liste des dépendances. Par exemple :
-
-```bash
-$ npm install express
-```
-
-Pour installer Express de façon temporaire et ne pas l'ajouter à la liste des dépendances, omettez l'option `--save` :
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-` ajoute automatiquement le module Node.js à la liste des dépendances. Par la suite, l'exécution de `npm install` dans le répertoire de l'application installera automatiquement les modules présents dans la liste des dépendances.
-</div>
\ No newline at end of file
diff --git a/fr/starter/static-files.md b/fr/starter/static-files.md
deleted file mode 100644
index b964295b11..0000000000
--- a/fr/starter/static-files.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-layout: page
-title: Servir des fichiers statiques dans Express
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Servir des fichiers statiques dans Express
-
-Pour servir des fichiers statiques tels que les images, les
-fichiers CSS et les fichiers JavaScript, utilisez la fonction de
-logiciel intermédiaire intégré `express.static` dans Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-Par exemple, utilisez le code suivant pour
-servir des images, des fichiers CSS et des fichiers JavaScript dans
-un répertoire nommé `public` :
-
-```js
-app.use(express.static('public'))
-```
-
-Maintenant, vous pouvez charger les fichiers qui sont dans le
-répertoire `public` :
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express recherche les fichiers relatifs au répertoire statique, donc
-le nom du répertoire statique ne fait pas partie de l'URL.
-</div>
-
-Pour utiliser plusieurs répertoires statiques actifs,
-utilisez la fonction middleware
-`express.static` plusieurs fois :
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express recherche les fichiers dans l'ordre dans lequel vous
-avez établi les répertoires statiques avec la fonction middleware `express.static`.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Maintenant, vous pouvez charger les fichiers qui sont dans le
-répertoire `public` à partir du préfixe de chemin
-d'accès `/static`.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-Cependant, le chemin d'accès que vous fournissez à la
-fonction `express.static` est en rapport avec
-le répertoire à partir duquel vous lancez votre processus `node`. Si
-vous exécutez l'application express à partir d'un autre répertoire, il
-est plus sûr d'utiliser le chemin d'accès absolu que vous voulez
-servir :
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/fr/support/index.md b/fr/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/fr/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/images/blogger.jpg b/images/blogger.jpg
deleted file mode 100644
index 52bca213fc..0000000000
Binary files a/images/blogger.jpg and /dev/null differ
diff --git a/images/brand/logo-dark.svg b/images/brand/logo-dark.svg
deleted file mode 100644
index 30cdfc0ff2..0000000000
--- a/images/brand/logo-dark.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 861.6297 500">
-  <path fill="#fff" d="M822.05434 464.78529c-23.57102 8.91305-50.08664-1.16881-61.78139-23.49073l-112.4692-155.53981-16.30803-21.72701-130.51543 177.49688c-11.00437 21.35391-36.14786 31.22309-58.7396 23.05618l168.14149-225.57746L453.94772 35.178469c23.20955-8.38407 49.07747.715704 61.98587 21.727011l116.55901 157.4569L749.74175 57.518928c11.0937-21.002063 36.16603-30.356097 58.30506-21.752557l-60.70782 80.543289-82.23033 107.02469c-9.6735 8.63851-9.6735 23.77308 0 32.41158l156.61338 209.03936ZM39.626477 236.19163l13.700796-67.66046C90.953337 34.743916 244.32044-20.928337 349.83703 61.941017 411.61839 110.45615 427.0318 179.1902 424.01558 256.64057H75.94892C70.325459 394.9777 170.14188 478.51165 297.82 435.87559c42.0737-15.33669 73.74401-50.3044 84.17297-93.75842 6.74816-21.72701 17.89283-25.45896 38.29067-19.1709-6.89256 53.65922-37.9963 101.20027-84.40304 129.00732-77.62638 42.45286-173.75024 30.1679-238.204672-30.44338-31.082401-34.94215-49.844311-79.11186-53.49956-125.76104 0-7.66837-2.556118-14.82549-4.345401-21.727-.170408-12.89987-.255612-25.51006-.255612-37.83054zm36.756986-9.35539H391.14389c-1.96821-100.27654-65.2577-171.413323-149.66074-172.077907C147.52023 53.480264 80.294322 123.05782 76.153409 226.40169Z"/>
-</svg>
diff --git a/images/brand/logo-light.svg b/images/brand/logo-light.svg
deleted file mode 100644
index 3b9e2cbb57..0000000000
--- a/images/brand/logo-light.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 861.6297 500">
-  <path d="M822.05434 464.78529c-23.57102 8.91305-50.08664-1.16881-61.78139-23.49073l-112.4692-155.53981-16.30803-21.72701-130.51543 177.49688c-11.00437 21.35391-36.14786 31.22309-58.7396 23.05618l168.14149-225.57746L453.94772 35.178469c23.20955-8.38407 49.07747.715704 61.98587 21.727011l116.55901 157.4569L749.74175 57.518928c11.0937-21.002063 36.16603-30.356097 58.30506-21.752557l-60.70782 80.543289-82.23033 107.02469c-9.6735 8.63851-9.6735 23.77308 0 32.41158l156.61338 209.03936ZM39.626477 236.19163l13.700796-67.66046C90.953337 34.743916 244.32044-20.928337 349.83703 61.941017 411.61839 110.45615 427.0318 179.1902 424.01558 256.64057H75.94892C70.325459 394.9777 170.14188 478.51165 297.82 435.87559c42.0737-15.33669 73.74401-50.3044 84.17297-93.75842 6.74816-21.72701 17.89283-25.45896 38.29067-19.1709-6.89256 53.65922-37.9963 101.20027-84.40304 129.00732-77.62638 42.45286-173.75024 30.1679-238.204672-30.44338-31.082401-34.94215-49.844311-79.11186-53.49956-125.76104 0-7.66837-2.556118-14.82549-4.345401-21.727-.170408-12.89987-.255612-25.51006-.255612-37.83054zm36.756986-9.35539H391.14389c-1.96821-100.27654-65.2577-171.413323-149.66074-172.077907C147.52023 53.480264 80.294322 123.05782 76.153409 226.40169Z"/>
-</svg>
diff --git a/images/brand/logotype-dark.svg b/images/brand/logotype-dark.svg
deleted file mode 100644
index 41894aa481..0000000000
--- a/images/brand/logotype-dark.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1120.322 250">
-  <path fill="#fff" d="M347.47162 250V4.890464h13.29516v38.55596a50.415241 50.415241 0 0 0 4.33954-5.43506c11.10412-23.03785 34.52487-37.57744 60.09412-37.29026 30.31296-.90408 54.94623 10.31704 69.422 37.29026a119.86915 119.86915 0 0 1 2.89302 109.881816c-13.4866 30.22788-46.79895 45.25672-82.46189 39.73657a66.688515 66.688515 0 0 1-53.22317-35.12049v97.4801zm13.29516-158.403836 2.97812 28.781356c5.25425 32.75927 24.62263 52.11702 55.03132 55.75458a62.540425 62.540425 0 0 0 68.69874-39.73657c11.82737-28.18574 10.95521-60.094116-2.33995-87.620406a61.26409 61.26409 0 0 0-64.54001-35.66294 59.668671 59.668671 0 0 0-53.30827 44.07611 304.40595 304.40595 0 0 0-6.51995 34.39724zm420.10574 33.312346a71.687494 71.687494 0 0 1-70.06017 63.35941c-55.75458 2.80794-81.91945-34.21642-86.07817-76.94174a123.27271 123.27271 0 0 1 10.85948-67.890396 75.729222 75.729222 0 0 1 78.83497-42.26797 72.432023 72.432023 0 0 1 64.26348 55.12705 371.94535 371.94535 0 0 1 6.24341 40.73636H638.50796c-2.71221 38.736776 18.10269 69.879356 47.6073 77.388456 36.74782 9.04071 68.1563-6.88157 79.55823-41.82125 2.5314-8.96625 7.14748-10.23195 15.29475-7.68992zM638.4016 84.629504h130.97326c-.81898-41.26817-26.51586-71.26205-61.37045-71.60241-39.35367-.63816-67.89039 28.15383-69.60281 71.60241zm169.53986 41.183076h12.83781a51.478853 51.478853 0 0 0 30.22787 44.35265 79.026422 79.026422 0 0 0 68.61365-1.80814 30.844768 30.844768 0 0 0 18.10269-30.3236 27.973013 27.973013 0 0 0-18.82595-27.97301c-14.12477-5.25425-29.14298-8.14727-43.53366-12.763346a319.0838 319.0838 0 0 1-43.81021-16.01801c-23.18675-11.31684-24.62263-55.39295 1.62733-69.34755a92.427941 92.427941 0 0 1 88.34367-1.36142c16.95398 9.35979 26.32441 28.26019 23.53775 47.43712h-11.00839c0-.5318-.9998-.99979-.9998-1.54223-1.36142-35.09922-30.86604-46.07571-62.54043-42.99123-9.57251 1.06361-18.64513 3.95664-27.15403 8.23236a27.122123 27.122123 0 0 0-15.74147 27.15404 27.122123 27.122123 0 0 0 18.10269 25.5267c13.82697 5.07343 28.50482 8.32809 42.81041 12.306l34.56741 9.04071a40.842727 40.842727 0 0 1 28.05811 36.843536c2.76539 18.56004-6.70076 36.801-23.44203 45.25672-30.22787 17.10289-80.01558 12.58254-102.1919-9.04071-11.34875-11.41256-17.67724-26.9094-17.54961-42.99123zm306.10774-67.794666h-12.0401c0-1.62733-.6382-3.19084-.819-4.43526a39.353669 39.353669 0 0 0-32.0466-37.83271 79.026422 79.026422 0 0 0-50.7769 2.44631 30.844768 30.844768 0 0 0-22.35715 29.41953 28.398458 28.398458 0 0 0 21.71895 28.60054l55.0313 14.12478a153.05386 153.05386 0 0 1 17.5497 5.33934c17.5496 6.381666 29.462 22.676216 29.9938 41.300076a45.203539 45.203539 0 0 1-27.6539 42.96995 100.72412 100.72412 0 0 1-81.4621.81898 56.477833 56.477833 0 0 1-34.0356-54.85051h11.76356c4.42463 21.32544 19.07054 39.08777 39.16224 47.49031 20.0916 8.40254 43.0337 6.33913 61.3066-5.48824a32.333825 32.333825 0 0 0 17.3794-30.22787 27.973013 27.973013 0 0 0-19.1024-27.7922c-14.1248-5.25425-29.143-8.05155-43.5337-12.763356a320.67922 320.67922 0 0 1-44.0761-15.83719c-22.6337-11.13602-24.44184-54.8505 1.3614-68.79447a91.151606 91.151606 0 0 1 89.7902-.99979 47.330764 47.330764 0 0 1 22.7188 46.43733zM325.59311 183.84329a20.740447 20.740447 0 0 1-25.70752-9.7746l-46.79895-64.72083-6.78585-9.04071-54.30807 73.85727a19.889557 19.889557 0 0 1-24.44182 9.59378l69.96445-93.863816-65.0931-84.81247c9.6576-3.48865 20.42136.29781 25.79261 9.04071l48.50074 65.51854 48.78791-65.26328a19.464112 19.464112 0 0 1 24.261-9.05134l-25.2608 33.51443-34.21642 44.53347a9.040708 9.040708 0 0 0 0 13.48661l65.16755 86.982236zM622.66013 4.177844v12.76335a65.624902 65.624902 0 0 0-69.87935 67.79467v99.564786h-12.94417V4.975554h12.76336v36.74781c15.65637-26.80304 39.82165-36.74781 70.14525-37.47107ZM.021272 88.724414l5.700964-28.15383c15.656379-55.66949 79.473139-78.83497 123.379074-44.35265 25.70751 20.18737 32.1211 48.78792 30.86604 81.01538H15.135208C12.79526 154.79603 54.329335 189.55489 107.45679 171.81383c17.50706-6.38167 30.68522-20.93189 35.02476-39.01331 2.80794-9.04071 7.44529-10.59359 15.93292-7.9771a73.495636 73.495636 0 0 1-35.12049 53.68054 85.089014 85.089014 0 0 1-99.118064-12.66763c-12.93353-14.53959-20.740447-32.91881-22.261413-52.32975 0-3.19084-1.063613-6.16895-1.808142-9.0407Q0 96.414334 0 88.724414Zm15.294751-3.89282H146.28929c-.81898-41.72553-27.15403-71.32587-62.274525-71.60241-39.098402-.53181-67.071415 28.41973-68.794468 71.42159Z"/>
-</svg>
diff --git a/images/brand/logotype-light.svg b/images/brand/logotype-light.svg
deleted file mode 100644
index c5532657d6..0000000000
--- a/images/brand/logotype-light.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1120.322 250">
-  <path d="M347.47162 250V4.890464h13.29516v38.55596a50.415241 50.415241 0 0 0 4.33954-5.43506c11.10412-23.03785 34.52487-37.57744 60.09412-37.29026 30.31296-.90408 54.94623 10.31704 69.422 37.29026a119.86915 119.86915 0 0 1 2.89302 109.881816c-13.4866 30.22788-46.79895 45.25672-82.46189 39.73657a66.688515 66.688515 0 0 1-53.22317-35.12049v97.4801zm13.29516-158.403836 2.97812 28.781356c5.25425 32.75927 24.62263 52.11702 55.03132 55.75458a62.540425 62.540425 0 0 0 68.69874-39.73657c11.82737-28.18574 10.95521-60.094116-2.33995-87.620406a61.26409 61.26409 0 0 0-64.54001-35.66294 59.668671 59.668671 0 0 0-53.30827 44.07611 304.40595 304.40595 0 0 0-6.51995 34.39724zm420.10574 33.312346a71.687494 71.687494 0 0 1-70.06017 63.35941c-55.75458 2.80794-81.91945-34.21642-86.07817-76.94174a123.27271 123.27271 0 0 1 10.85948-67.890396 75.729222 75.729222 0 0 1 78.83497-42.26797 72.432023 72.432023 0 0 1 64.26348 55.12705 371.94535 371.94535 0 0 1 6.24341 40.73636H638.50796c-2.71221 38.736776 18.10269 69.879356 47.6073 77.388456 36.74782 9.04071 68.1563-6.88157 79.55823-41.82125 2.5314-8.96625 7.14748-10.23195 15.29475-7.68992zM638.4016 84.629504h130.97326c-.81898-41.26817-26.51586-71.26205-61.37045-71.60241-39.35367-.63816-67.89039 28.15383-69.60281 71.60241zm169.53986 41.183076h12.83781a51.478853 51.478853 0 0 0 30.22787 44.35265 79.026422 79.026422 0 0 0 68.61365-1.80814 30.844768 30.844768 0 0 0 18.10269-30.3236 27.973013 27.973013 0 0 0-18.82595-27.97301c-14.12477-5.25425-29.14298-8.14727-43.53366-12.763346a319.0838 319.0838 0 0 1-43.81021-16.01801c-23.18675-11.31684-24.62263-55.39295 1.62733-69.34755a92.427941 92.427941 0 0 1 88.34367-1.36142c16.95398 9.35979 26.32441 28.26019 23.53775 47.43712h-11.00839c0-.5318-.9998-.99979-.9998-1.54223-1.36142-35.09922-30.86604-46.07571-62.54043-42.99123-9.57251 1.06361-18.64513 3.95664-27.15403 8.23236a27.122123 27.122123 0 0 0-15.74147 27.15404 27.122123 27.122123 0 0 0 18.10269 25.5267c13.82697 5.07343 28.50482 8.32809 42.81041 12.306l34.56741 9.04071a40.842727 40.842727 0 0 1 28.05811 36.843536c2.76539 18.56004-6.70076 36.801-23.44203 45.25672-30.22787 17.10289-80.01558 12.58254-102.1919-9.04071-11.34875-11.41256-17.67724-26.9094-17.54961-42.99123zm306.10774-67.794666h-12.0401c0-1.62733-.6382-3.19084-.819-4.43526a39.353669 39.353669 0 0 0-32.0466-37.83271 79.026422 79.026422 0 0 0-50.7769 2.44631 30.844768 30.844768 0 0 0-22.35715 29.41953 28.398458 28.398458 0 0 0 21.71895 28.60054l55.0313 14.12478a153.05386 153.05386 0 0 1 17.5497 5.33934c17.5496 6.381666 29.462 22.676216 29.9938 41.300076a45.203539 45.203539 0 0 1-27.6539 42.96995 100.72412 100.72412 0 0 1-81.4621.81898 56.477833 56.477833 0 0 1-34.0356-54.85051h11.76356c4.42463 21.32544 19.07054 39.08777 39.16224 47.49031 20.0916 8.40254 43.0337 6.33913 61.3066-5.48824a32.333825 32.333825 0 0 0 17.3794-30.22787 27.973013 27.973013 0 0 0-19.1024-27.7922c-14.1248-5.25425-29.143-8.05155-43.5337-12.763356a320.67922 320.67922 0 0 1-44.0761-15.83719c-22.6337-11.13602-24.44184-54.8505 1.3614-68.79447a91.151606 91.151606 0 0 1 89.7902-.99979 47.330764 47.330764 0 0 1 22.7188 46.43733zM325.59311 183.84329a20.740447 20.740447 0 0 1-25.70752-9.7746l-46.79895-64.72083-6.78585-9.04071-54.30807 73.85727a19.889557 19.889557 0 0 1-24.44182 9.59378l69.96445-93.863816-65.0931-84.81247c9.6576-3.48865 20.42136.29781 25.79261 9.04071l48.50074 65.51854 48.78791-65.26328a19.464112 19.464112 0 0 1 24.261-9.05134l-25.2608 33.51443-34.21642 44.53347a9.040708 9.040708 0 0 0 0 13.48661l65.16755 86.982236zM622.66013 4.177844v12.76335a65.624902 65.624902 0 0 0-69.87935 67.79467v99.564786h-12.94417V4.975554h12.76336v36.74781c15.65637-26.80304 39.82165-36.74781 70.14525-37.47107ZM.021272 88.724414l5.700964-28.15383c15.656379-55.66949 79.473139-78.83497 123.379074-44.35265 25.70751 20.18737 32.1211 48.78792 30.86604 81.01538H15.135208C12.79526 154.79603 54.329335 189.55489 107.45679 171.81383c17.50706-6.38167 30.68522-20.93189 35.02476-39.01331 2.80794-9.04071 7.44529-10.59359 15.93292-7.9771a73.495636 73.495636 0 0 1-35.12049 53.68054 85.089014 85.089014 0 0 1-99.118064-12.66763c-12.93353-14.53959-20.740447-32.91881-22.261413-52.32975 0-3.19084-1.063613-6.16895-1.808142-9.0407Q0 96.414334 0 88.724414Zm15.294751-3.89282H146.28929c-.81898-41.72553-27.15403-71.32587-62.274525-71.60241-39.098402-.53181-67.071415 28.41973-68.794468 71.42159Z"/>
-</svg>
diff --git a/images/copy-btn.svg b/images/copy-btn.svg
deleted file mode 100644
index d44b4a72f1..0000000000
--- a/images/copy-btn.svg
+++ /dev/null
@@ -1 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" stroke-width="1.5" stroke="currentColor" aria-hidden="true" data-slot="icon" class="CodeBox_icon__pCRVM"><path stroke-linecap="round" stroke-linejoin="round" d="M15.75 17.25v3.375c0 .621-.504 1.125-1.125 1.125h-9.75a1.125 1.125 0 0 1-1.125-1.125V7.875c0-.621.504-1.125 1.125-1.125H6.75a9.06 9.06 0 0 1 1.5.124m7.5 10.376h3.375c.621 0 1.125-.504 1.125-1.125V11.25c0-4.46-3.243-8.161-7.5-8.876a9.06 9.06 0 0 0-1.5-.124H9.375c-.621 0-1.125.504-1.125 1.125v3.5m7.5 10.375H9.375a1.125 1.125 0 0 1-1.125-1.125v-9.25m12 6.625v-1.875a3.375 3.375 0 0 0-3.375-3.375h-1.5a1.125 1.125 0 0 1-1.125-1.125v-1.5a3.375 3.375 0 0 0-3.375-3.375H9.75"></path></svg>
\ No newline at end of file
diff --git a/images/express-mw.png b/images/express-mw.png
deleted file mode 100644
index d3c5e8fbfb..0000000000
Binary files a/images/express-mw.png and /dev/null differ
diff --git a/images/favicon.ico b/images/favicon.ico
deleted file mode 100755
index f5fdde9ae5..0000000000
Binary files a/images/favicon.ico and /dev/null differ
diff --git a/images/favicon.png b/images/favicon.png
deleted file mode 100644
index cea0804bf8..0000000000
Binary files a/images/favicon.png and /dev/null differ
diff --git a/images/og.png b/images/og.png
deleted file mode 100644
index 07238428ce..0000000000
Binary files a/images/og.png and /dev/null differ
diff --git a/index.md b/index.md
deleted file mode 100644
index fece636e07..0000000000
--- a/index.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "/en/index.html"
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-    
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/it/3x/api.md b/it/3x/api.md
deleted file mode 100644
index 66255944f9..0000000000
--- a/it/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - Riferimento API
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x NON È PIU' SUPPORTATO**
-
-I problemi noti e non noti relativi alla sicurezza presenti in 3.x non sono stati indirizzati dall'ultimo aggiornamento (1 agosto 2015). Si consiglia di utilizzare l'ultima versione di Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>API 3.x</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/it/4x/api.md b/it/4x/api.md
deleted file mode 100644
index 031e84432b..0000000000
--- a/it/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - Riferimento API
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>API 4.x</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/it/5x/api.md b/it/5x/api.md
deleted file mode 100644
index 680945b0df..0000000000
--- a/it/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Riferimento API
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/it/advanced/best-practice-performance.md b/it/advanced/best-practice-performance.md
deleted file mode 100644
index 41c9b9c5ee..0000000000
--- a/it/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: Best Practice sulle prestazioni utilizzando Express in fase di produzione
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# Best practice sulla produzione: prestazioni e affidabilità
-
-In questo articolo vengono descritte le best practice sulle prestazioni e sull'affidabilità per le applicazioni Express implementate per la produzione.
-
-Questo argomento entra nel mondo di "devops", coprendo sia le operazioni che lo sviluppo tradizionale. Di conseguenza, le informazioni sono divise in due parti:
-
-- Things to do in your code (the dev part):
-  - Utilizzare la compressione gzip
-  - [Asynchronous Error Handling in Express with Promises, Generators and ES7](https://web.archive.org/web/20240000000000/https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/)
-  - Gestire in modo appropriato le eccezioni
-  - [Handle exceptions properly](#handle-exceptions-properly)
-- [Operazioni da effettuare nell'ambiente / configurazione](#env) (la parte delle operazioni).
-  - Impostare NODE_ENV su "produzione"
-  - Al contrario, utilizzare il middleware [serve-static](https://www.npmjs.com/package/serve-static) (o qualcosa di equivalente), ottimizzato per servire i file per le applicazioni Express.
-  - Eseguire l'applicazione in un cluster
-  - <a name="try-catch"></a>
-  - Utilizzare un servizio di bilanciamento del carico
-  - Utilizzare un proxy inverso
-
-## Things to do in your code {#in-code}
-
-Di seguito sono elencate alcune operazioni che è possibile effettuare nel codice per migliorare le prestazioni dell'applicazione:
-
-- Utilizzare la compressione gzip
-- [Asynchronous Error Handling in Express with Promises, Generators and ES7](https://web.archive.org/web/20240000000000/https://strongloop.com/strongblog/async-error-handling-expressjs-es7-promises-generators/)
-- Gestire in modo appropriato le eccezioni
-- [Handle exceptions properly](#handle-exceptions-properly)
-
-### Utilizzare la compressione gzip
-
-La compressione gzip è in grado di ridurre notevolmente la dimensione del contenuto della risposta e di conseguenza aumentare la velocità di un'applicazione web. Utilizzare il middleware di [compressione](https://www.npmjs.com/package/compression) per la compressione gzip nell'applicazione Express. Ad esempio:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-Per un sito web ad elevato traffico nella produzione, il miglior modo per utilizzare la compressione è quello di implementarla ad un livello di proxy inverso (consultare [Utilizzare un proxy inverso](#proxy)). In questo caso, non è necessario utilizzare il middleware di compressione. Per dettagli su come abilitare la compressione gzip in Nginx, consultare [Modulo ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) nella documentazione Nginx.
-
-### Non utilizzare funzioni sincrone
-
-I metodi e le funzioni sincrone ostacolano il processo di esecuzione finché non restituiscono un risultato. Una chiamata singola a una funzione sincrona potrebbe restituire un risultato in pochi microsecondi o millisecondi, tuttavia in siti web ad elevato traffico, queste chiamate aggiungono e riducono le prestazioni di un'applicazione. Evitarne l'utilizzo in produzione.
-
-Poiché Node e molti moduli forniscono versioni sicrone e asincrone delle relative funzioni, utilizzare sempre la versione asincrona nella produzione. L'unico caso in cui l'utilizzo di una funzione sincrona è giustificato, è allo startup iniziale.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Naturalmente, non si consiglia di utilizzarlo nella produzione, ma solo per assicurare che il codice sia pronto per la produzione. Consultare l'[aggiornamento settimanale per io.js 2.1.0](https://nodejs.org/en/blog/weekly-updates/weekly-update.2015-05-22/#2-1-0) per ulteriori informazioni.
-
-### Effettuare correttamente la registrazione
-
-Solitamente, esistono due motivi per effettuare la registrazione dall'applicazione: per il debug e la registrazione dell'attività dell'applicazione (sostanzialmente, qualsiasi altra cosa). L'utilizzo di `console.log()` o `console.err()` per stampare i messaggi di log sul terminale, è un'operazione comune nello sviluppo. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### Per il debug
-
-Se si sta effettuando la registrazione per motivi di debug, allora invece di utilizzare `console.log()`, utilizzare un modulo di debug speciale quale [debug](https://www.npmjs.com/package/debug). Questo modulo consente di utilizzare la variabile di ambiente DEBUG per controllare quali messaggi di debug vengono inviati a `console.err()`, se presenti. Per fare in modo che l'applicazione resti strettamente asincrona, è necessario instradare `console.err()` a un altro programma. Però a questo punto, non andrai ad effettuare il debug in fase di produzione giusto?
-
-#### Per l'attività dell'applicazione
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Handle exceptions properly
-
-Le applicazioni Node danno origine a errori quando riscontrano eccezioni non rilevate. Se tali eccezioni non vengono gestite o se non si effettuano operazioni appropriate, l'applicazione Express si arresterà in modo anomalo. Seguendo i consigli descritti in [Riavvio automatico dell'applicazione](#restart), sarà possibile recuperare l'applicazione dopo un arresto anomalo. Fortunatamente, le applicazioni Express solitamente hanno tempi di avvio molto brevi. Tuttavia, per prima cosa è necessario evitare che si verifichino arresti anomali, e per effettuare ciò, è necessario gestire in modo appropriato le eccezioni.
-
-Per essere sicuri di gestire al meglio tutte le eccezioni, utilizzare le seguenti tecniche:
-
-- [Utilizzare try-catch](#try-catch)
-- [Utilizzare promises](#promises)
-
-Prima di leggere questi argomenti, è necessario avere una conoscenza base della gestione degli errori di Node/Express: utilizzo di error-first callback e diffusione degli errori al middleware. Node utilizza la convenzione "error-first callback" per restituire gli errori da funzioni asincrone, dove il primo parametro per la funzione callback è l'oggetto dell'errore, seguito dai dati nei parametri successivi. Per indicare un errore, indicare null come primo parametro. La funzione callback deve seguire in modo corrispondente la convenzione error-first callback per gestire l'errore in modo significativo. In Express, il miglior modo è quello di utilizzare la funzione next() per diffondere gli errori attraverso la catena middleware.
-
-Per ulteriori informazioni sulle nozioni di base della gestione degli errori, consultare:
-
-- [Gestione degli errori in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Utilizzare try-catch
-
-Try-catch è un linguaggio JavaScript che è possibile utilizzare per rilevare eccezioni in codice sincrono. Ad esempio, utilizzare try-catch, per gestire errori di analisi JSON come mostrato di seguito.
-
-Di seguito viene riportato un esempio di utilizzo di try-catch per la gestione di un'eccezione che dà origine a un arresto anomalo del processo.
-Questa funzione middleware accetta un parametro del campo query denominato "params" che è un oggetto JSON.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-Tuttavia, try-catch funziona solo per il codice sincrono. Poiché la piattaforma Node è principalmente asincrona (nello specifico in un ambiente di produzione), try-catch non sarà in grado di rilevare molte eccezioni.
-
-#### Utilizzare promises
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### Cosa non fare
-
-Una cosa da _non_ fare è quella di stare in ascolto per un evento `uncaughtException`, emesso quando un'eccezione si verifica ed è costante nel loop degli eventi. Se si aggiunge un programma di ascolto dell'evento per `uncaughtException` si cambierà il funzionamento predefinito del processo che sta riscontrando un'eccezione; il processo continuerà ad operare malgrado l'eccezione. Questo potrebbe risultare un ottimo modo per prevenire un arresto anomalo dell'applicazione, ma continuare ad utilizzare un'applicazione dopo che si è verificata un'eccezione non rilevata è pericoloso e non è consigliato, poiché lo stato del processo diventa non affidabile e non prevedibile.
-
-Inoltre, l'utilizzo di `uncaughtException` è ufficialmente riconosciuto come [non conforme](https://nodejs.org/api/process.html#process_event_uncaughtexception) ed esiste una [proposta](https://github.com/nodejs/node-v0.x-archive/issues/2582) per la relativa rimozione dal core. Quindi continuare a visualizzare un evento `uncaughtException` non è un buon segno. Ecco perché consigliamo di usufruire di più processi e supervisori: l'arresto anomalo e il riavvio sono spesso il modo più affidabile per ripristinare una situazione dopo un errore.
-
-Inoltre, non si consiglia di utilizzare l'opzione [domini](https://nodejs.org/api/domain.html). Solitamente non risolve il problema ed è considerato un modulo obsoleto.
-
-## Operazioni da effettuare nell'ambiente / configurazione
-
-Di seguito sono elencate alcune operazioni che è possibile effettuare nell'ambiente del sistema per migliorare le prestazioni dell'applicazione:
-
-- Impostare NODE_ENV su "produzione"
-- Al contrario, utilizzare il middleware [serve-static](https://www.npmjs.com/package/serve-static) (o qualcosa di equivalente), ottimizzato per servire i file per le applicazioni Express.
-- Eseguire l'applicazione in un cluster
-- <a name="try-catch"></a>
-- Utilizzare un servizio di bilanciamento del carico
-- Utilizzare un proxy inverso
-
-### Impostare NODE_ENV su "produzione"
-
-La variabile di ambiente NODE_ENV indica l'ambiente in cui è in esecuzione un'applicazione (solitamente, sviluppo o applicazione). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-L'impostazione di NODE_ENV su "produzione" consente ad Express di:
-
-- Memorizzare in cache i template di visualizzazione.
-- Memorizzare in cache i file CSS generati da stensioni CSS.
-- Generare meno messaggi di errore ridondanti.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-Se si ha la necessità di scrivere codice specifico dell'ambiente, è possibile selezionare il valore di NODE_ENV con `process.env.NODE_ENV`. Notare che la selezione del valore di qualsiasi variabile di ambiente influisce sulle prestazioni in modo negativo, quindi questa operazione deve essere effettuata con moderazione.
-
-Nello sviluppo, solitamente si impostano le variabili di ambiente nella shell interattiva, ad esempio utilizzando `export` o il file `.bash_profile`. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). La sezione successiva fornisce ulteriori dettagli sull'utilizzo in generale del sistema init, però anche impostare NODE_ENV è molto importante per le prestazioni (ed è facile da fare), evidenziato di seguito.
-
-Con systemd, utilizzare la direttiva `Environment` nel file unit. Ad esempio:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### Verificare che l'applicazione sia in grado di riavviarsi automaticamente
-
-In fase di produzione, l'applicazione non deve mai andare offline. Ciò significa che deve riavviarsi nel caso in cui sia l'applicazione che il server terminino in modo anomalo. Anche se ovviamente si spera che entrambe queste situazioni non si verifichino mai, realisticamente è necessario considerare l'eventualità di:
-
-- Utilizzare un process manager per riavviare l'applicazione (e Node) quando termina in modo anomalo.
-- Utilizzare il sistema init fornito dal sistema operativo per riavviare il process manager quando il sistema operativo termina in modo anomalo. È inoltre possibile utilizzare il sistema init senza un process manager.
-
-Le applicazioni Node terminano in modo anomalo se riscontrano eccezioni non rilevate. La prima cosa da fare è verificare che l'applicazione sia stata verificata e che sia in grado di gestire tutte le eccezioni (consultare [Gestire in modo appropriato le eccezioni](#exceptions) per dettagli). Come prevenzione, attivare un meccanismo che assicuri che applicazione si riavvii automaticamente in caso di arresto anomalo.
-
-#### Utilizzare un process manager
-
-Nello sviluppo, l'applicazione è stata avviata semplicemente dalla riga comandi con `node server.js` o qualcosa di simile. Ma se si effettua questa stessa operazione in campo di produzione si andrà incontro a situazioni pericolose. Se l'applicazione termina in modo anomalo, sarà offline finché non viene riavviata. Per fare in modo che l'applicazione si riavvii nel caso in cui termini in modo anomalo, utilizzare un process manager. Un process manager è un "contenitore" per le applicazioni che facilita lo sviluppo, fornisce un'elevata disponibilità e consente di gestire l'applicazione al momento del runtime.
-
-Oltre a fare in modo di riavviare l'applicazione in caso di arresto anomalo, un process manager consente di:
-
-- Ottenere insight relativi alle prestazioni di runtime e al consumo delle risorse.
-- Modificare le impostazioni in modo dinamico per migliorare le prestazioni.
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### Utilizzare un sistema init
-
-Il successivo livello di affidabilità è quello di assicurare che l'applicazione venga riavviata quando si riavvia il server. I sistemi possono ancora arrestarsi per moltissimi motivi. Per fare in modo che l'applicazione si riavvii nel caso in cui un server si arresti in modo anomalo, utilizzare il sistema init integrato al sistema operativo. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-Esistono due modi per utilizzare i sistemi init con l'applicazione Express:
-
-- Far eseguire l'applicazione in un process manager e installare il process manager come servizio con il sistema init. Il process manager riavvierà l'applicazione nel caso in cui termini in modo anomalo e il sistema init riavvierà il process manager quando si riavvia il sistema operativo. Questa è la procedura consigliata.
-- Far eseguire l'applicazione (e Node) direttamente con il sistema init. Questa operazione risulta più semplice ma non si hanno gli stessi vantaggi dell'utilizzo di un process manager.
-
-##### Systemd
-
-Systemd è un sistema Linux e un service manager. Le più importanti distribuzioni Linux hanno utilizzato systemd come sistema init predefinito.
-
-Un file di configurazione del servizio systemd è denominato _unit file_, con un nome file che termina con .service. Segue un unit file di esempio per gestire un'applicazione Node direttamente (sostituire il testo in grassetto con i valori appropriati per il proprio sistema e applicazione): Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Per ulteriori informazioni su systemd, consultare [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html).
-
-### Eseguire l'applicazione in un cluster
-
-In un sistema multicore, è possibile aumentare le prestazioni di un'applicazione Node di molte volte avviando un cluster di processi. Un cluster esegue molte istanze di un'applicazione, nel caso ideale, un'istanza su ciascun core CPU, quindi, distribuendo il carico e le attività tra le istanze.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANTE: poiché le istanze dell'applicazione vengono eseguite come processi separati, non condividono lo stesso spazio di memoria. Ossia, gli oggetti sono locali rispetto a ciascuna istanza dell'applicazione. Pertanto, non è possibile conservare lo stato nel codice dell'applicazione. Tuttavia, è possibile utilizzare un datastore in-memory, ad esempio [Redis](http://redis.io/) per memorizzare lo stato e i dati relativi alla sessione. Questa condizione si applica fondamentalmente a tutti i moduli di scaling orizzontale, se il processo di clustering viene effettuato con più processi o più server fisici.
-
-Nelle applicazioni sottoposte a cluster, i processi di lavoro possono ternare in modo anomalo individualmente senza influenzare gli altri processi. Oltre ai vantaggi che si possono ottenere dalle prestazioni, l'isolamento dell'errore è un altro motivo che spinge a eseguire un cluster di processi di applicazioni. Quando un processo di lavoro termina in modo anomalo, ricordarsi sempre di registrare l'evento e di dare origine a un nuovo processo utilizzando cluster.fork().
-
-#### Utilizzo del modulo cluster di Node
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). Ciò consente a un processo principale di dare origine a processi di lavoro e di distribuire le connessioni in entrata tra i processi di lavoro.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### Memorizzare in cache i risultati della richiesta
-
-Un'altra strategia per migliorare le prestazioni in fase di produzione è quella di memorizzare in cache i risultati delle richieste, in modo tale che l'applicazione non debba gestire nuovamente la stessa richiesta.
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### Utilizzare un servizio di bilanciamento del carico
-
-A prescindere da quanto sia ottimizzata un'applicazione, una singola istanza è in grado di gestire solo una quantità limitata di carico e traffico. Un modo per scalare un'applicazione è quello di eseguire più delle proprie istanze e distribuire il traffico tramite un servizio di bilanciamento del carico. L'impostazione di un servizio di bilanciamento del carico può migliorare la velocità e le prestazioni dell'applicazione e abilitarla a scalare di più di quanto sia possibile fare con una singola istanza.
-
-Un servizio di bilanciamento del carico è solitamente un proxy inverso che gestisce il traffico a e d più istanze di applicazione e server. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Con il servizio di bilanciamento del carico, è possibile che sia necessario garantire che le richieste associate a un ID sessione particolare si connettano al processo che le ha originate. Questo processo è noto come _affinità sessione_ o _sessioni delicate_. Si consiglia di utilizzare un data store, ad esempio Redis, per i dati sessione (a seconda dell'applicazione). Per informazioni, consultare [Utilizzo di più nodi](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Utilizzare un proxy inverso
-
-Un proxy inverso si trova davanti a un'applicazione web ed esegue le operazioni di supporto sulle richieste, oltre a indirizzare le richieste all'applicazione. Inoltre, è in grado di gestire pagine di errore, compressioni, memorizzazioni in cache e il bilanciamento del carico.
-
-Le attività di gestione che non richiedono la conoscenza dello stato dell'applicazione per un proxy inverso consentono ad Express di eseguire attività dell'applicazione specializzate. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/it/advanced/best-practice-security.md b/it/advanced/best-practice-security.md
deleted file mode 100644
index f2164c2f9c..0000000000
--- a/it/advanced/best-practice-security.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-layout: page
-title: Best Practice sulla sicurezza per Express in fase di produzione
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# Best Practice sulla produzione: Sicurezza
-
-## Panoramica
-
-Il termine _"produzione"_ si riferisce alla fase nel ciclo di vita del software quando un'applicazione o API è solitamente disponibile per gli utenti finali o i consumatori. Al contrario, nella fase _"sviluppo"_, si sta ancora scrivendo e verificando il codice e l'applicazione non è aperta ad accessi esterni. Gli ambienti di sistema corrispondenti sono noti rispettivamente come ambienti di _produzione_ e di _sviluppo_.
-
-Gli ambienti di sviluppo e produzione sono solitamente configurati diversamente e hanno requisiti molto differenti. Ciò che potrebbe andare bene nello sviluppo potrebbe non essere accettato nella produzione. Ad esempio, in un ambiente di sviluppo è possibile che si richieda una registrazione degli errori ridondante per il processo di debug, mentre la stessa richiesta in un ambiente di produzione potrebbe mettere a rischio la sicurezza. Inoltre, in un ambiente di sviluppo non è necessario preoccuparsi della scalabilità, dell'affidabilità e delle prestazioni, mentre nella produzione è fondamentale tenerne conto.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-In questo articolo vengono descritte alcune best practice sulla sicurezza per le applicazioni Express distribuite per la produzione.
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [hsts](https://github.com/helmetjs/hsts) imposta l'intestazione `Strict-Transport-Security` che rafforza connessioni (HTTP su SSL/TLS) sicure per il server.
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - Se si utilizza `helmet.js`, questa operazione sarà effettuata per conto dell'utente.
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - [xssFilter](https://github.com/helmetjs/x-xss-protection) imposta `X-XSS-Protection` per abilitare il filtro XSS (Cross-site scripting) nei browser web più recenti.
-    - [noCache](https://github.com/helmetjs/nocache) imposta le intestazioni `Cache-Control` e Pragma per disabilitare la memorizzazione in cache della parte client.
-    - [ieNoOpen](https://github.com/helmetjs/ienoopen) imposta `X-Download-Options` per IE8+.
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) rimuove l'intestazione `X-Powered-By`.
-  - [Additional considerations](#additional-considerations)
-
-## Non utilizzare versioni obsolete o vulnerabili di Express
-
-Express 2.x e 3.x non sono più supportati. I problemi relativi alla sicurezza e alle prestazioni in queste versioni non verranno risolti. Non utilizzare queste versioni! Se non è stato effettuato l'aggiornamento alla versione 4, consultare la [guida alla migrazione](/{{ page.lang }}/guide/migrating-4.html).
-
-Inoltre, assicurarsi che non si stia utilizzando nessuna delle versioni vulnerabili di Express elencate nella [pagina Aggiornamenti sulla sicurezza](/{{ page.lang }}/advanced/security-updates.html). Nel caso si stia utilizzando una di queste versioni, effettuare l'aggiornamento a una versione aggiornata, preferibilmente l'ultima.
-
-## Utilizzare TLS
-
-Se l'applicazione utilizza o trasmette dati riservati, utilizzare [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) per proteggere la connessione e i dati. Questa tecnologia codifica i dati prima che vengano inviati dal client al server, proteggendo i dati da alcuni attacchi comuni (e facili) da parte di hacker. Anche se le richieste Ajax e POST possono non essere visibili e "nascoste" nei browser, il relativo traffico di rete è vulnerabile agli attacchi [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) e [man-in-the-middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-Sicuramente si conosce la crittografia SSL (Secure Socket Layer). [TLS non è altro che un miglioramento di SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). In altre parole, se prima si utilizzava SSL, considerare l'opportunità di passare a TLS. Consigliamo di utilizzare Nginx per gestire la TLS. Per informazioni su come configurare correttamente TLS su Nginx (e altri server), consultare [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-Inoltre, uno strumento molto semplice da utilizzare per ottenere un certificato gratuito TLS è [Let's Encrypt](https://letsencrypt.org/about/), un CA (certificate authority) gratuito, automatizzato e open fornito da [Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/).
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Utilizzare Helmet
-
-[Helmet](https://www.npmjs.com/package/helmet) è utile per proteggere l'applicazione da alcune vulnerabilità web note configurando le intestazioni HTTP in modo appropriato.
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-Installare Helmet come qualsiasi altro modulo:
-
-```bash
-$ npm install helmet
-```
-
-Successivamente, per utilizzarlo nel codice:
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-By default, Express sends the `X-Powered-By` response header that you can
-disable using the `app.disable()` method:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Utilizzare i cookie in modo sicuro
-
-Per fare in modo che i cookie non espongano a rischi l'applicazione, non utilizzare il nome cookie della sessione predefinita e impostare le opzioni di sicurezza dei cookie in modo appropriato.
-
-Esistono due moduli di sessione cookie middleware principali:
-
-- [express-session](https://www.npmjs.com/package/express-session) che sostituisce il middleware `express.session` integrato a Express 3.x.
-- [cookie-session](https://www.npmjs.com/package/cookie-session) che sostituisce il middleware `express.cookieSession` integrato a Express 3.x.
-
-La differenza principale tra questi due moduli è nel modo in cui salvano i dati di sessione dei cookie. Il middleware [express-session](https://www.npmjs.com/package/express-session) memorizza i dati di sessione sul server; salva l'ID sessione nello stesso cookie e non nei dati di sessione. Per impostazione predefinita, utilizza il processo di memorizzazione in-memory e non è progettato per un ambiente di produzione. Nella produzione, sarà necessario configurare un processo di memorizzazione della sessione scalabile; consultare l'elenco di [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-
-Al contrario, il middleware [cookie-session](https://www.npmjs.com/package/cookie-session) implementa la memorizzazione di backup dei cookie: suddivide in serie l'intera sessione per il cookie, piuttosto che una chiave di sessione. Utilizzarlo solo quando i dati di sessione sono relativamente piccoli e facilmente codificati come valori primitivi (piuttosto che oggetti). Poiché si presuppone che i browser supportino almeno 4096 byte per cookie, per non superare il limite, non superare la dimensione di 4093 byte per dominio. Inoltre, fare attenzione perché i dati dei cookie saranno visibili al cliente, quindi, se per qualche motivo devono rimanere sicuri o non visibili, la scelta di utilizzare express-session potrebbe essere quella giusta.
-
-### Non utilizzare il nome del cookie della sessione predefinito
-
-L'utilizzo del nome del cookie della sessione predefinito potrebbe esporre l'applicazione ad attacchi da parte di hacker. Il problema di sicurezza messo in discussione è simile a quello di `X-Powered-By`: un potenziale hacker potrebbe utilizzarlo per individuare il server e indirizzare gli attacchi di conseguenza.
-
-Per evitare questo problema, utilizzare i nomi dei cookie predefiniti; ad esempio, utilizzando il middleware [express-session](https://www.npmjs.com/package/express-session):
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Impostare le opzioni di sicurezza dei cookie
-
-Impostare le seguenti opzioni per i cookie per aumentare la sicurezza:
-
-- `secure` - Assicura che il browser invii il cookie solo tramite HTTPS.
-- `httpOnly` - Assicura che il cookie venga inviato solo tramite HTTP, non JavaScript del client, questa procedura consentirà una protezione da attacchi XSS (cross-site scripting).
-- `domain` - Indica il dominio del cookie; utilizzarlo per fare un confronto con il dominio del server in cui è stato richiesto l'URL. Se corrispondono, come fase successiva verificare l'attributo del percorso.
-- `path` - Indica il percorso del cookie; utilizzarlo per fare un confronto con il percorso di richiesta. Se questo e il dominio corrispondono, inviare il cookie nella richiesta.
-- `expires` - Utilizzarlo per impostare la data di scadenza per i cookie permanenti.
-
-Esempio di utilizzo del middleware [cookie-session](https://www.npmjs.com/package/cookie-session):
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### Evitare altre vulnerabilità note
-
-Prestare attenzione alle avvertenze [Node Security Project](https://npmjs.com/advisories) che potrebbero influenzare Express o altri moduli utilizzati dall'applicazione. Solitamente, il Node Security Project è una risorsa eccellente per questioni di apprendimento e per gli strumenti sulla sicurezza di Node.
-
-Infine, le applicazioni Express, come anche altre applicazioni web, possono essere vulnerabili ad una vasta gamma di attacchi basati su web. Cercare di comprendere al meglio le [vulnerabilità web](https://www.owasp.org/www-project-top-ten/) note e prendere precauzioni per evitarle.
-
-## Additional considerations
-
-Ecco alcuni consigli sull'eccellente [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Fare riferimento a quel post del blog per tutti i dettagli su questi consigli:
-
-- Filtrare sempre e verificare gli input utente come protezione contro attacchi XSS (cross-site scripting) e command injection.
-- Creare una difesa contro attacchi SQL injection utilizzando query con parametri o istruzioni preparate.
-- Utilizzare lo strumento [sqlmap](http://sqlmap.org/) open source per rilevare le vulnerabilità SQL injection nell'applicazione.
-- Utilizzare gli strumenti [nmap](https://nmap.org/) e [sslyze](https://github.com/nabla-c0d3/sslyze) per verificare la configurazione delle crittografie SSL, delle chiavi e della rinegoziazione come anche la validità del certificato.
-- Utilizzare [safe-regex](https://www.npmjs.com/package/safe-regex) per assicurarsi che le espressioni regolari non siano suscettibili ad attacchi [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
-
-[helmet]: https://helmetjs.github.io/
\ No newline at end of file
diff --git a/it/advanced/developing-template-engines.md b/it/advanced/developing-template-engines.md
deleted file mode 100644
index 2741f5eaae..0000000000
--- a/it/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Sviluppo dei motori di template per Express
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Sviluppo dei motori di template per Express
-
-Utilizzare il metodo `app.engine(ext, callback)` per creare il proprio motore di template. `ext` è l'estensione file e `callback` è la funzione del motore di template, la quale accetta le seguenti voci come parametri: l'ubicazione del file, l'oggetto delle opzioni e la funzione callback.
-
-Il seguente codice è un esempio di implementazione di un motore di template molto semplice per il rendering del file `.ntl`.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-L'applicazione sarà ora in grado di effettuare il rendering dei file `.ntl`. Creare un file denominato `index.ntl` nella directory `views` con il seguente contenuto.
-
-```pug
-#title#
-#message#
-```
-
-Successivamente, creare il seguente percorso nell'applicazione.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Quando si effettua una richiesta per la home page, `index.ntl` verrà visualizzato come HTML.
\ No newline at end of file
diff --git a/it/advanced/healthcheck-graceful-shutdown.md b/it/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 3afe11f7ce..0000000000
--- a/it/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### Esempio
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/it/advanced/security-updates.md b/it/advanced/security-updates.md
deleted file mode 100644
index 244ad588c6..0000000000
--- a/it/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Aggiornamenti sulla sicurezza Express
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# Aggiornamenti sulla sicurezza
-
-<div class="doc-box doc-notice" markdown="1">
-Le vulnerabilità di Node.js influenzano direttamente Express. Pertanto, [verificare sempre le vulnerabilità Node.js](https://nodejs.org
-/en/blog/vulnerability/) e assicurarsi di utilizzare l'ultima versione corretta di Node.js.
-</div>
-
-L'elenco seguente mostra le vulnerabilità di Express che sono state corrette nell'aggiornamento della versione specificato.
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - Risolta la vulnerabilità del rilevamento del percorso root in `express.static`, `res.sendfile` e `res.sendFile`
-- 4.10.7
-  - Risolta la vulnerabilità del reindirizzamento aperto in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 4.8.8
-  - Risolte le vulnerabilità trasversali della directory in `express.static` ([advisory](http://npmjs.com/advisories/32), [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-- 4.8.4
-  - Node.js 0.10 può portare alla perdita di `fd` in determinate situazioni che influenzano `express.static` e `res.sendfile`. Le richieste sospette potrebbero causare una perdita di `fd` ed eventualmente il verificarsi di errori `EMFILE` e risposte mancate del server.
-- 4.8.0
-  - Le matrici sparse che dispongono di indici estremamente elevati nella stringa di query potrebbero causare errori di memoria nel processo e una chiusura anomala del server.
-  - Gli oggetti di stringa query molto nidificati potrebbero causare un blocco del processo e una mancata risposta da parte del server.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x NON È PIU' SUPPORTATO**
-
-I problemi noti e non noti relativi alla sicurezza presenti in 3.x non sono stati indirizzati dall'ultimo aggiornamento (1 agosto 2015). Si consiglia di utilizzare l'ultima versione di Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - Risolta la vulnerabilità del rilevamento del percorso root in `express.static`, `res.sendfile` e `res.sendFile`
-- 3.19.0
-  - Risolta la vulnerabilità del reindirizzamento aperto in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 3.16.10
-  - Risolte le vulnerabilità trasversali della directory in `express.static`.
-- 3.16.6
-  - Node.js 0.10 può portare alla perdita di `fd` in determinate situazioni che influenzano `express.static` e `res.sendfile`. Le richieste sospette potrebbero causare una perdita di `fd` ed eventualmente il verificarsi di errori `EMFILE` e risposte mancate del server.
-- 3.16.0
-  - Le matrici sparse che dispongono di indici estremamente elevati nella stringa di query potrebbero causare errori di memoria nel processo e una chiusura anomala del server.
-  - Gli oggetti di stringa query molto nidificati potrebbero causare un blocco del processo e una mancata risposta da parte del server.
-- 3.3.0
-  - La risposta 404 di un metodo non supportato sovrascrive un tentativo suscettibili in precedenza ad attacchi XSS (cross-site scripting).
\ No newline at end of file
diff --git a/it/api.md b/it/api.md
deleted file mode 100644
index bc6a90eb05..0000000000
--- a/it/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Riferimento API
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/it/changelog/index.md b/it/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/it/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/it/guide/behind-proxies.md b/it/guide/behind-proxies.md
deleted file mode 100644
index 9b50e2e10d..0000000000
--- a/it/guide/behind-proxies.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: page
-title: Express con i proxy
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# Express con i proxy
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-Quando si esegue un'applicazione Express con un proxy, impostare (utilizzando [app.set()](/{{ page.lang }}/4x/api.html#app.set)) la variabile dell'applicazione `trust proxy` su uno dei valori elencati nella seguente tabella.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Tipo</th><th>Valore</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Booleano</td>
-<td markdown="1">
-Se impostato su `true`, l'indirizzo IP del client viene considerato come la voce a sinistra dell'intestazione `X-Forwarded-*`.
-
-Se impostato su `false`, significa che l'applicazione abbia una connessione diretta a Internet e l'indirizzo IP del client sia arrivato da `req.connection.remoteAddress`. Questa è l'impostazione predefinita.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-È possibile impostare gli indirizzi IP in uno dei seguenti modi:
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-Quando specificati, gli indirizzi IP o le subnet vengono esclusi dal processo di determinazione dell'indirizzo e l'indirizzo IP non attendibile più vicino al server delle applicazioni viene considerato come indirizzo IP del client. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>Numero</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">Il valore di [req.hostname](/{{ page.lang }}/api.html#req.hostname) viene rilevato dalla serie di valori nell'intestazione `X-Forwarded-Host`, la quale può essere impostata dal client o dal proxy.
-  </li>
-  <li markdown="1">`X-Forwarded-Proto` può essere impostata dal proxy inverso per far capire all'applicazione se si tratta di `https` o `http` oppure di un nome non valido. Questo valore viene riportato da [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">I valori [req.ip](/{{ page.lang }}/api.html#req.ip) e [req.ips](/{{ page.lang }}/api.html#req.ips) vengono popolati con l'elenco di indirizzi da `X-Forwarded-For`.
-  </li>
-</ul>
-
-L'impostazione `trust proxy` viene implementata utilizzando il pacchetto [proxy-addr](https://www.npmjs.com/package/proxy-addr). Per ulteriori informazioni, consultare la relativa documentazione.
diff --git a/it/guide/database-integration.md b/it/guide/database-integration.md
deleted file mode 100644
index 52599c4861..0000000000
--- a/it/guide/database-integration.md
+++ /dev/null
@@ -1,513 +0,0 @@
----
-layout: page
-title: Integrazione database Express
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# Integrazione database
-
-L'aggiunta della funzionalità che consente di connettere i database alle applicazioni Express è solo un modo per caricare un driver Node.js appropriato per il database nell'applicazione. Questo documento spiega brevemente come aggiungere e utilizzare alcuni dei moduli Node.js più noti per i sistemi database nell'applicazione Express:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-Questi driver di database sono tra quelli più disponibili. Per altre opzioni,
-effettuare una ricerca nel sito [npm](https://www.npmjs.com/).
-</div>
-
-## Cassandra
-
-**Modulo**: **Installazione**
-[cassandra-driver](https://github.com/datastax/nodejs-driver)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Esempio
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install couchbase
-```
-
-### Esempio
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Modulo**: **Installazione**
-[nano](https://github.com/dscape/nano)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install nano
-```
-
-### Esempio
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Modulo**: **Installazione**
-[levelup](https://github.com/rvagg/node-levelup)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Esempio
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Modulo**: **Installazione**
-[mysql](https://github.com/felixge/node-mysql/)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install mysql
-```
-
-### Esempio
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Modulo**: **Installazione**
-[mongodb](https://github.com/mongodb/node-mongodb-native)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-Se si desidera un driver del modello oggetto per MongoDB, consultare [Mongoose](https://github.com/LearnBoost/mongoose).
-
-## Neo4j
-
-<code class="language-javascript" translate="no">
-var apoc = require('apoc');apoc.query('match (n) return n').exec().then(
-function (response) {
-console.log(response);
-},
-function (fail) {
-console.log(fail);
-}
-); </code>
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Esempio
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Modulo**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### <a name="postgres"></a>
-
-NOTA: [Vedi i prerequisiti di installazione](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Esempio
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install pg-promise
-```
-
-### Esempio
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Modulo**: **Installazione**
-[redis](https://github.com/mranney/node_redis)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install redis
-```
-
-### Esempio
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install tedious
-```
-
-### Esempio
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Modulo**: **Installazione**
-[sqlite3](https://github.com/mapbox/node-sqlite3)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install sqlite3
-```
-
-### Esempio
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**Modulo**: **Installazione**
-[elasticsearch](https://github.com/elastic/elasticsearch-js)
-
-### <a name="postgres"></a>
-
-```bash
-$ npm install elasticsearch
-```
-
-### Esempio
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/it/guide/debugging.md b/it/guide/debugging.md
deleted file mode 100644
index 903a7e19b8..0000000000
--- a/it/guide/debugging.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-layout: page
-title: Debug di Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Debug di Express
-
-Per visualizzare tutti i log interni utilizzati in Express, impostare la variabile di ambiente `DEBUG` su
-`express:*` quando si avvia l'applicazione.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-Su Windows, utilizzare il comando corrispondente.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-L'esecuzione di questo comando sull'applicazione predefinita generata da [Programma di creazione express](/{{ page.lang }}/starter/generator.html) consentirà di stampare il seguente output:
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-Quando successivamente viene effettuata una richiesta all'applicazione, verranno visualizzati i log specificati nel codice Express:
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-Per visualizzare i log solo dall'implementazione router impostare il valore `DEBUG` su `express:router`. In modo simile, per visualizzare i log solo dall'implementazione dell'applicazione impostare il valore `DEBUG` su `express:application` e così via.
-
-## Applicazioni generate da `express`
-
-Un'applicazione generata dal comando `express` utilizza inoltre il modulo `debug` e il relativo spazio dei nomi di debug viene associato al nome dell'applicazione.
-
-Ad esempio, se l'applicazione è stata generata con `$ express sample-app`, è possibile abilitare le istruzioni di debug con il seguente comando:
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-È possibile specificare più di uno spazio dei nomi di debug assegnando un elenco di nomi separati da virgola:
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/it/guide/error-handling.md b/it/guide/error-handling.md
deleted file mode 100644
index 3bb34d7a7a..0000000000
--- a/it/guide/error-handling.md
+++ /dev/null
@@ -1,297 +0,0 @@
----
-layout: page
-title: Gestione degli errori di Express
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# Gestione degli errori
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. Ad esempio:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-Definire le funzioni middleware di gestione degli errori nello stesso modo in cui si definiscono altre funzioni middleware,
-ad eccezione delle funzioni di gestione degli errori che hanno quattro argomenti invece di tre:
-`(err, req, res, next)`.  Ad esempio:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Se si dispone di un gestore route con più funzioni di callback, è possibile utilizzare il parametro `route` per passare al successivo gestore route.
-Ad esempio:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-Se si trasmette qualsiasi cosa alla funzione `next()` (ad eccezione della stringa `'route'`), Express considera la richiesta corrente come se contenesse errori e ignorerà qualsiasi altra funzione middleware e routing di non gestione degli errori restante.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. Ad esempio:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  Ad esempio:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. Ad esempio:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## Il gestore errori predefinito
-
-Express viene fornito insieme a un gestore degli errori integrato, il quale gestisce gli errori che potrebbero verificarsi nell'applicazione. Questa funzione middleware di gestione degli errori viene aggiunta alla fine dello stack della funzione middleware.
-
-Se un errore viene ignorato e passato a `next()` e non viene gestito in un gestore
-degli errori, verrà gestito dal gestore errori integrato; l'errore verrà scritto sul client con la traccia
-stack. La traccia stack non viene inclusa nell'ambiente di produzione.
-
-<div class="doc-box doc-info" markdown="1">
-Impostare la variabile di ambiente `NODE_ENV` su `production`, per eseguire l'applicazione nella modalità di produzione.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-Se si chiama `next()` con un errore dopo che si è iniziato a scrivere la risposta
-(ad esempio, se si riscontra un errore mentre si esegue lo streaming della
-risposta al client) il gestore degli errori predefinito di Express chiude la connessione
-e rifiuta la richiesta.
-
-Pertanto, quando si aggiunge un gestore degli errori personalizzato, si consiglia di associarlo al meccanismo
-di gestione degli errori predefinito in Express, quando le intestazioni
-sono state già inviate al client:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. Ad esempio:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Si definisce il middleware di gestione degli errori per ultimo, successivamente `app.use()` e altre chiamate route; ad esempio:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Le risposte dall'interno delle funzione middleware possono essere in qualsiasi formato desiderato, ad esempio una pagina di errore HTML, un messaggio semplice o una stringa JSON.
-
-Per motivi organizzativi (e framework di livello più alto), è possibile definire
-diverse funzioni middleware di gestione degli errori, come solitamente si fa con
-le funzioni middleware normali. Ad esempio, se si desidera definire un programma di gestione errori per le richieste
-effettuate utilizzando `XHR` e quelle senza, è necessario utilizzare i seguenti comandi:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-In questo esempio, il `logErrors` generico potrebbe scrivere le richieste e le informazioni sull'errore
-su `stderr`, ad esempio:
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-Inoltre, in questo esempio, `clientErrorHandler` viene definito come segue; in questo caso, l'errore viene chiaramente tramandato al successivo:
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-La funzione "catch-all" `errorHandler` potrebbe essere implementata come segue:
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. Ad esempio:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-In questo esempio, il gestore `getPaidContent` verrà ignorato ma qualsiasi altro gestore rimanente in `app` per `/a_route_behind_paywall` verrà eseguito senza interruzione.
-
-<div class="doc-box doc-info" markdown="1">
-Le chiamate a `next()` e `next(err)` indicano che il gestore corrente è completo e in che stato si trova.  `next(err)` ignorerà tutti gli handler rimanenti nella catena ad eccezione degli handler configurati per gestire gli errori come descritto sopra.
-</div>
diff --git a/it/guide/migrating-4.md b/it/guide/migrating-4.md
deleted file mode 100644
index 459f6a2229..0000000000
--- a/it/guide/migrating-4.md
+++ /dev/null
@@ -1,613 +0,0 @@
----
-layout: page
-title: Migrazione a Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Passaggio a Express 4
-
-<h2 id="overview">Panoramica</h2>
-
-Express 4 è stato modificato rispetto a Express 3. Ciò significa che un'applicazione Express 3 esistente non funzionerà se si aggiornano le dipendenze della versione Express.
-
-Argomenti di questo articolo:
-
-<ul class="doclist">
-  <li><a href="#changes">Modifiche in Express 4.</a></li>
-  <li><a href="#example-migration">Un esempio</a> di migrazione di un'applicazione Express 3 a Express 4.</li>
-  <li><a href="#app-gen">Aggiornamento al programma di creazione dell'applicazione Express 4.</a></li>
-</ul>
-
-<h2 id="changes">Modifiche in Express 4</h2>
-
-Sono state apportate diverse modifiche importanti alla versione Express 4:
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Modifiche al sistema di routing.</a></li>
-  <li><a href="#other-changes">Altre modifiche.</a></li>
-</ul>
-
-Consultare inoltre:
-
-- [Nuove funzioni in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migrazione da 3.x a 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Modifiche al sistema middleware e al core di Express
-</h3>
-
-Express 4 non dipende più da Connect e non ha più il middleware integrato nel core,
-ad eccezione della funzione `express.static`. Ciò significa che ora
-Express è un framework web middleware e routing indipendente
-i release e le versioni di Express non vengono influenzate dagli aggiornamenti middleware.
-
-Senza un middleware integrato, è necessario aggiungere esplicitamente tutto il
-middleware richiesto per eseguire l'applicazione. Seguire semplicemente questi passaggi:
-
-1. Installare il modulo: `npm install --save <module-name>`
-2. Nell'applicazione, richiedere il modulo: `require('module-name')`
-3. Utilizzare il modulo relativamente alla propria documentazione: `app.use( ... )`
-
-La seguente tabella elenca il middleware Express 3 e le relative controparti in Express 4.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Segue l'[elenco completo](https://github.com/senchalabs/connect#middleware) di middleware Express 4.
-
-In molti casi, è possibile semplicemente sostituire il middleware della versione 3 meno recente con la relativa controparte
-Express 4. Per dettagli, consultare la documentazione del modulo in
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> accetta i parametri</h4>
-
-Nella versione 4 è possibile utilizzare un parametro di variabile per definire il percorso in cui vengono caricate le funzioni middleware, quindi leggere il valore del parametro dal programma di gestione route.
-Ad esempio:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-Il sistema di routing
-</h3>
-
-Le applicazioni ora sono in grado di caricare il middleware di routing, pertanto non sarà più necessario
-pensare all'ordine in cui è caricato il middleware rispetto al middleware
-`router`.
-
-Il modo in cui viene definita la route non è cambiato ma il sistema di routing dispone di due nuove
-funzioni utili per organizzare le route:
-
-{: .doclist }
-
-- Un nuovo metodo, `app.route()`, per creare handler di route a catena per un percorso route.
-- Un nuova classe, `express.Router`, per creare handler di route assemblabili in modo modulare.
-
-<h4 id="app-route">Metodo <code>app.route()</code></h4>
-
-Il nuovo metodo `app.route()` consente di creare handler di route a catena
-per un percorso route. Poiché il percorso è specificato in una singola ubicazione, la creazione di route modulari è utile, poiché riduce le possibilità di riscontrare errori tipografici e di ridondanza. Per ulteriori informazioni
-sulle route, consultare la documentazione [`Router()`](/{{ page.lang }}/4x/api.html#router).
-
-Segue un esempio di handler di route a catena definiti utilizzando la funzione `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router">Classe <code>express.Router</code></h4>
-
-L'altra funzione che risulta utile per organizzare le route in una nuova classe,
-`express.Router`, che è possibile utilizzare per creare handler di route assemblabili in modo modulare. Un'istanza `Router` è un sistema di routing e middleware completo;
-per questo motivo spesso viene fatto riferimento a questo come "mini-app".
-
-Nel seguente esempio si crea un router come modulo, si carica il middleware all'interno di esso,
-si definiscono alcune route e si caricano su un percorso nell'applicazione principale.
-
-Ad esempio, creare un file router denominato `birds.js` nella directory dell'applicazione,
-con i seguenti contenuti:
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Successivamente, caricare il modulo router nell'applicazione:
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-L'applicazione sarà ora in grado di gestire le richieste per i percorsi `/birds` e
-`/birds/about` e chiamerà il middleware `timeLog`
-specifico per la route.
-
-<h3 id="other-changes">
-Altre modifiche
-</h3>
-
-La seguente tabella elenca altre piccole ma importanti modifiche applicate a Express 4:
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Oggetto</th>
-<th>Descrizione</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 richiede Node.js 0.10.x o versione successiva e non esiste più supporto per
-Node.js 0.8.x.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-Il modulo `http` non è più necessario, a meno che non sia necessario utilizzarlo (socket.io/SPDY/HTTPS). L'applicazione può essere avviata utilizzando
-la funzione `app.listen()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-La funzione `app.configure()` è stata rimossa.  Utilizzare la funzione
-`process.env.NODE_ENV` o
-`app.get('env')` per rilevare l'ambiente e configurare l'applicazione in modo appropriato.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-La proprietà dell'applicazione `json spaces` è disattivata per impostazione predefinita in Express 4.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Utilizzare `req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()` e `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-Non risolve più le URL relative.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Era un array; ora è un oggetto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Era una funzione; ora è un oggetto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-Modificato in `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Ora disponibile come `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Rimosso.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Rimosso.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-La funzionalità ora è limitata alla sola impostazione del valore cookie di base. Utilizzare
-`res.cookie()` per aggiungere altre funzionalità.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">Esempio di migrazione dell'applicazione</h2>
-
-Segue un esempio di migrazione dell'applicazione da Express 3 a Express 4.
-I file da considerare sono `app.js` e `package.json`.
-
-<h3 id="">
-Applicazione con la versione 3
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Prendere in considerazione l'applicazione Express v.3 con il seguente file `app.js`:
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-Il file `package.json` della versione 3 associata deve
-apparire come segue:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Processo
-</h3>
-
-Iniziare il processo di migrazione installando il middleware richiesto per l'applicazione
-Express 4 e aggiornando Express e Pug alla versione aggiornata
-con il seguente comando:
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Apportare le seguenti modifiche a `app.js`:
-
-1. Le funzioni middleware di Express integrate `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` e
-   `express.errorHandler` non sono più disponibili nell'oggetto
-   `express`. È necessario installare le funzioni alternative
-   manualmente e caricarle sull'applicazione.
-
-2. Non è più necessario caricare la funzione `app.router`.
-   Non è un oggetto applicazione Express 4 valido, pertanto rimuovere il codice
-   `app.use(app.router);`.
-
-3. Assicurarsi che le funzioni middleware siano state caricate nell'ordine corretto - caricare `errorHandler` dopo aver caricato le route dell'applicazione.
-
-<h3 id="">Applicazione con la versione 4</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-L'esecuzione del comando `npm` aggiornerà `package.json` come segue:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Successivamente, rimuovere il codice non valido, caricare il middleware richiesto e apportare le modifiche
-necessarie. Il file `app.js` apparirà come segue:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-A meno che non sia necessario gestire direttamente il modulo `http` (socket.io/SPDY/HTTPS), il relativo caricamento non è richiesto e l'applicazione può essere avviata semplicemente come segue:
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Eseguire l'applicazione</h3>
-
-Il processo di migrazione è stato completato e ora l'applicazione
-è stata aggiornata a Express 4. Per confermare, avviare l'applicazione utilizzando il seguente comando:
-
-```bash
-$ node .
-```
-
-Caricare [http://localhost:3000](http://localhost:3000)
-e visualizzare la home page sottoposta a rendering da Express 4.
-
-<h2 id="app-gen">Aggiornamento al programma di creazione dell'applicazione Express 4</h2>
-
-Lo strumento della riga comandi per generare un'applicazione Express è sempre
-`express` ma per effettuare l'aggiornamento alla nuova versione è necessario disinstallare
-il programma di creazione dell'applicazione di Express 3 e successivamente installare il nuovo
-`express-generator`.
-
-<h3 id="">Installazione</h3>
-
-Se il programma di creazione dell'applicazione di Express 3 è già installato sul sistema,
-è necessario disinstallarlo:
-
-```bash
-$ npm uninstall -g express
-```
-
-A seconda di come sono configurati i privilegi del file e della directory,
-potrebbe essere necessario eseguire questo comando con `sudo`.
-
-Ora, installare il nuovo programma di creazione:
-
-```bash
-$ npm install -g express-generator
-```
-
-A seconda di come sono configurati i privilegi del file e della directory,
-potrebbe essere necessario eseguire questo comando con `sudo`.
-
-Ora, il comando `express` sul sistema è aggiornato al programma di creazione
-di Express 4.
-
-<h3 id="">Modifiche al programma di creazione dell'applicazione </h3>
-
-L'utilizzo e le opzioni del comando sono rimaste quasi gli stessi, con le seguenti eccezioni:
-
-{: .doclist }
-
-- È stata rimossa l'opzione `--sessions`.
-- È stata rimossa l'opzione `--jshtml`.
-- È stata aggiunta l'opzione `--hogan` per supportare [Hogan.js](http://twitter.github.io/hogan.js/).
-
-<h3 id="">Esempio</h3>
-
-Eseguire il seguente comando per creare un'applicazione Express 4:
-
-```bash
-$ express app4
-```
-
-Se si visualizzano i contenuti del file `app4/app.js`, si noterà che tutte le funzioni
-middleware (ad eccezione di `express.static`) richieste per l'applicazione,
-sono caricate come moduli indipendenti e il middleware `router`
-non viene più caricato in modo esplicito sull'applicazione.
-
-Si noterà inoltre che il file `app.js` è ora un modulo Node.js, diversamente dall'applicazione autonoma che era stata generate dal vecchio programma di creazione.
-
-Dopo aver installato le dipendenze, avviare l'applicazione utilizzando il seguente comando:
-
-```bash
-$ npm start
-```
-
-Se si visualizza lo script di avvio npm nel file `package.json`,
-si noterà che il comando effettivo che avvia l'applicazione è
-`node ./bin/www`, il quale era `node app.js`
-in Express 3.
-
-Poiché il file `app.js` generato dal programma di creazione di Express 4
-è ora un modulo Node.js, non può essere più avviato individualmente come un'applicazione
-(a meno che non venga modificato il codice). Il modulo deve essere caricato in un file Node.js
-e avviato tramite il file Node.js. Il file Node.js è `./bin/www`
-in questo caso.
-
-La directory `bin` e il file senza estensione `www`
-non sono obbligatori per la creazione di un'applicazione Express o per avviare l'applicazione. Sono solo consigli
-creati dal programma di creazione, pertanto è possibile modificarli a seconda delle
-necessità.
-
-Per rimuovere la directory `www` e conservare le cose "come farebbe Express 3",
-cancellare la riga in cui viene riportata la dicitura `module.exports = app;` alla fine del file
-`app.js`, quindi incollare il seguente codice al proprio posto:
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Assicurarsi di caricare il modulo `debug` all'inizio del file `app.js` utilizzando il seguente codice:
-
-```js
-var debug = require('debug')('app4')
-```
-
-Successivamente, modificare `"start": "node ./bin/www"` nel file `package.json` in `"start": "node app.js"`.
-
-È stata spostata la funzionalità di `./bin/www` di nuovo in
-`app.js`. Questa modifica non è consigliata, ma questa prova consente di comprendere in che modo funziona
-il file `./bin/www` e perché il file `app.js`
-non si avvia più in modo autonomo.
diff --git a/it/guide/migrating-5.md b/it/guide/migrating-5.md
deleted file mode 100644
index 5d58dec589..0000000000
--- a/it/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: Migrazione a Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Passaggio a Express 5
-
-<h2 id="overview">Panoramica</h2>
-
-Express 5 non è molto differente da Express 4: le modifiche all'API non sono così importanti come quelle che sono state effettuate nel passaggio dalla 3.0 alla 4.0. Anche se le API di base sono le stesse, ci sono comunque delle modifiche importanti; in altre parole, un programma Express 4 esistente potrebbe non funzionare se lo si aggiorna per utilizzare Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-È quindi possibile eseguire i test automatizzati per trovare errori e correggere i problemi in base agli aggiornamenti elencati di seguito. Dopo aver gestito gli errori del test, avviare l'applicazione per verificare gli errori. Si noterà subito se l'applicazione utilizza qualsiasi metodo o proprietà non supportati.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Modifiche in Express 5</h2>
-
-**Proprietà e metodi rimossi**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Nomi di metodi al plurale</a></li>
-  <li><a href="#leading">Due punti nell'argomento del nome in app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Miglioramenti**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**Modificato**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Proprietà e metodi rimossi
-
-Se si utilizza uno dei seguenti metodi o proprietà nell'applicazione, quest'ultima si chiuderà in modo anomalo. Quindi, sarà necessario modificare l'applicazione dopo aver effettuato l'aggiornamento alla versione 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 non supporta più la funzione `app.del()`. Se si utilizza questa funzione verrà generato un errore. Per registrare le route HTTP DELETE, utilizzare al contrario la funzione `app.delete()`.
-
-Inizialmente era stato utilizzato il comando `del` al posto di `delete`, perché `delete` è una parola chiave riservata in JavaScript. Tuttavia, a partire da ECMAScript 6, `delete` e altre parole chiave riservate possono essere utilizzate liberamente come nomi di proprietà.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-La firma `app.param(fn)` è stata utilizzata per modificare la funzionalità della funzione `app.param(name, fn)`. È stata considerata obsoleta a partire dalla v4.11.0 e non è più supportata in Express 5.
-
-<h3 id="plural">Nomi di metodi al plurale</h3>
-
-I seguenti nomi di metodi sono stati messi al plurale. In Express 4, l'utilizzo di vecchi metodi ha dato origine ad avvisi di deprecazione. Express 5 non li supporta più in alcun modo:
-
-`req.acceptsLanguage()` è stato sostituito con `req.acceptsLanguages()`.
-
-`req.acceptsCharset()` è stato sostituito con `req.acceptsCharsets()`.
-
-`req.acceptsEncoding()` è stato sostituito con `req.acceptsEncodings()`.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Due punti (:) nel nome per app.param(name, fn)</h3>
-
-I due punti (:) nel nome della funzione `app.param(name, fn)` è una eredità di Express 3 e per il bene della compatibilità con le versioni precedenti, Express 4 supporta questa condizione ma comunque fornendo un messaggio di avviso di deprecazione. Express 5 lo ignorerà senza avvisi e utilizzerà il parametro nome senza inserire i due punti.
-
-Questa procedura non dovrebbe influenzare il codice se si segue correttamente la documentazione di Express 4 di [app.param](/{{ page.lang }}/4x/api.html#app.param), poiché non si parla dei due punti.
-
-<h3 id="req.param">req.param(name)</h3>
-
-Questo metodo poco chiaro e molto pericoloso che si utilizzava per richiamare i dati del modulo è stato rimosso. Ora sarà necessario ricercare il nome del parametro inviato nell'oggetto `req.params`, `req.body` o `req.query`.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 non supporta più la firma `res.json(obj, status)`. Al contrario, impostare lo stato e successivamente associarlo al metodo `res.json()` come segue: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 non supporta più la firma `res.jsonp(obj, status)`. Al contrario, impostare lo stato e successivamente associarlo al metodo `res.jsonp()` come segue: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 non supporta più la firma `res.send(obj, status)`. Al contrario, impostare lo stato e successivamente associarlo al metodo `res.send()` come segue: `res.status(status).send(obj)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 non supporta più la firma <code>res.send(<em>status</em>)</code>, dove _`status`_ è un numero. Al contrario, utilizzare la funzione `res.sendStatus(statusCode)`, la quale imposta il codice di stato dell'intestazione della risposta HTTP e invia la versione di testo del codice: "Non trovato", "Errore interno del server" e così via.
-Se è necessario inviare un numero utilizzando la funzione `res.send()`, citare il numero per convertirlo in una stringa, in modo tale che Express non lo interpreti come un tentativo di utilizzo di una firma vecchia non supportata.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-La funzione `res.sendfile()` è stata sostituita da una versione in cui ogni frase composta inizia con una lettera maiuscola che utilizza ad esempio `res.sendFile()` in Express 5.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. È stata considerata obsoleta a partire dalla v4.11.0 e non è più supportata in Express 5.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Modificato
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. Ad esempio:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-Ad esempio:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-L'oggetto `app.router`, che era stato rimosso in Express 4, è ritornato in Express 5. Nella nuova versione, questo oggetto è solo un riferimento al router Express di base, diversamente da Express 3, in cui un'applicazione aveva il compito esplicito di caricarlo.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-In Express 4, la funzione `req.host` andava a rimuovere in modo non corretto il numero porta nel caso fosse stato presente. In Express 5 il numero porta viene conservato.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Miglioramenti
-
-<h3 id="res.render">res.render()</h3>
-
-Questo metodo ora potenzia i funzionamenti asincroni per tutti i motori di visualizzazione, evitando i bug causati dai motori di visualizzazione con un'implementazione sincrona e che violavano l'interfaccia consigliata.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/it/guide/overriding-express-api.md b/it/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/it/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/it/guide/routing.md b/it/guide/routing.md
deleted file mode 100644
index 416a55dfbe..0000000000
--- a/it/guide/routing.md
+++ /dev/null
@@ -1,413 +0,0 @@
----
-layout: page
-title: Routing Express
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# Routing
-
-_Routing_ fa riferimento alla definizione di endpoint dell'applicazione (URI) e alla loro modalità di risposta alle richieste del client.
-Per un'introduzione al concetto di routing, consultare la sezione [Routing di base](/{{ page.lang }}/starter/basic-routing.html).
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-Il codice seguente è un esempio di una route veramente di base.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Metodi di route</h2>
-
-Un metodo di route deriva da uno dei metodi HTTP ed è collegato ad un'istanza delle classe `express`.
-
-Il codice seguente è un esempio di route definite per i metodi GET e POST nella root dell'app.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-Esiste un metodo di routing speciale, `app.all()`, che non deriva da alcun metodo HTTP. Questo metodo viene utilizzato per caricare funzioni middleware in un percorso per tutti i metodi di richiesta.
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Percorsi di route</h2>
-
-I percorsi di route, in combinazione con un metodo di richiesta, definiscono gli endpoint a cui possono essere rivolte richieste. I percorsi di route possono essere stringhe, modelli di stringa o espressioni regolari.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/) è uno strumento utile per il test delle route Express di base, anche se non supporta la corrispondenza di modelli.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Ecco alcuni esempi di percorsi di route basati su stringhe.
-
-Questo percorso di route corrisponderà a richieste nella route root, `/`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-Questo percorso di route corrisponderà a richieste in `/about`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-Questo percorso di route corrisponderà a richieste in `/random.text`.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Ecco alcuni esempi di percorsi di route basati su modelli di stringa.
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-Questo percorso di route corrisponderà a `acd` e `abcd`.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-Questo percorso di route corrisponderà a `abcd`, `abbcd`, `abbbcd` e così via.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-Questo percorso di route corrisponderà a `abcd`, `abxcd`, `abRABDOMcd`, `ab123cd` e così via.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-Questo percorso di route corrisponderà a `/abe` e `/abcde`.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Esempi di percorsi di route basati su espressioni regolari:
-
-Questo percorso di route corrisponderà a qualsiasi elemento con "a" nel nome route.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-Questo percorso di route corrisponderà a `butterfly` e `dragonfly`, ma non a `butterflyman`, `dragonfly man` e così via.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">
-Le stringhe di query non fanno parte del percorso di route.
-</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Handler di route</h2>
-
-È possibile fornire molteplici funzioni di callback che si comportino come [middleware](/{{ page.lang }}/guide/using-middleware.html) per gestire una richiesta. La sola eccezione è rappresentata dal fatto che queste callback potrebbero richiamare `next('route')` per ignorare le callback di route restanti. È possibile utilizzare questo meccanismo per imporre pre-condizioni su una route, quindi, passare il controllo a route successive, nel caso non ci siano motivi per proseguire con la route corrente.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Gli handler di route possono avere il formato di una funzione, di un array di funzioni o di combinazioni di entrambi, come illustrato nei seguenti esempi.
-
-Una singola funzione di callback può gestire una route. Ad esempio:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-Più funzioni di callback possono gestire una route (assicurarsi di specificare l'oggetto `next`). Ad esempio:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-Un array di funzioni callback possono gestire una route. Ad esempio:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-Una combinazione di funzioni indipendenti e array di funzioni può gestire una route. Ad esempio:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Metodi di risposta</h2>
-
-I metodi sull'oggetto risposta (`res`) nella seguente tabella possono inviare una risposta al client e terminare il ciclo richiesta-risposta. Se nessuno di questi metodi viene richiamato da un handler di route, la richiesta del client verrà lasciata in sospeso.
-
-| Metodo                                                                                                                                                                                                                    | Descrizione                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | Richiedere un file da scaricare.                                                                                         |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | Terminare il processo di risposta.                                                                                       |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | Inviare una risposta JSON.                                                                                               |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | Inviare una risposta JSON con supporto JSONP.                                                                            |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | Reindirizzare una richiesta.                                                                                             |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Eseguire il rendering di un template di vista.                                                                           |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | Inviare una risposta di vari tipi.                                                                                       |
-| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile)                          | Inviare un file come un flusso di ottetti.                                                                               |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Impostare il codice di stato della risposta e inviare la relativa rappresentazione di stringa come corpo della risposta. |
-
-<h2 id="app-route">app.route()</h2>
-
-È possibile creare handler di route concatenabili per un percorso di route, utilizzando `app.route()`.
-Poiché il percorso è specificato in una singola ubicazione, la creazione di route modulari è utile, come lo è la riduzione della ridondanza e degli errori tipografici. Per ulteriori informazioni sulle route, consultare: [Documentazione su Router()](/{{ page.lang }}/4x/api.html#router).
-
-Ecco un esempio di handler di route concatenati, definiti utilizzando `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Utilizzare la classe `express.Router` per creare handler di route modulari, montabili. Un'istanza `Router` è un middleware e un sistema di routing completo; per questa ragione, spesso si definisce "mini-app".
-
-Nel seguente esempio si crea un router come modulo, si carica al suo interno una funzione middleware, si definiscono alcune route e si monta un modulo router su un percorso nell'app principale.
-
-Creare un file router denominato `birds.js` nella directory app, con il seguente contenuto:
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Successivamente, caricare il modulo router nell'applicazione:
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-L'app ora sarà in grado di gestire richieste a `/birds` e `/birds/about`, oltre a richiamare la funzione middleware `timeLog`, specifica per la route.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/it/guide/using-middleware.md b/it/guide/using-middleware.md
deleted file mode 100644
index f2630df172..0000000000
--- a/it/guide/using-middleware.md
+++ /dev/null
@@ -1,278 +0,0 @@
----
-layout: page
-title: Utilizzo del middleware Express
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# Utilizzo del middleware
-
-Express è un framework Web di routing e middleware, con funzionalità sua propria minima: un'applicazione Express è essenzialmente a serie di chiamate a funzioni middleware.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
-
-Le funzioni middleware possono eseguire le attività elencate di seguito:
-
-- Eseguire qualsiasi codice.
-- Apportare modifiche agli oggetti richiesta e risposta.
-- Terminare il ciclo richiesta-risposta.
-- Chiamare la successiva funzione middleware nello stack.
-
-Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve richiamare `next()` per passare il controllo alla successiva funzione middleware. Altrimenti, la richiesta verrà lasciata in sospeso.
-
-Un'applicazione Express può utilizzare i seguenti tipi di middleware:
-
-- [Middleware a livello dell'applicazione](#middleware.application)
-- [Middleware a livello del router](#middleware.router)
-- [Middleware di gestione degli errori](#middleware.error-handling)
-- [Middleware integrato](#middleware.built-in)
-- [Middleware di terzi](#middleware.third-party)
-
-È possibile caricare il middleware a livello dell'applicazione e del router con un percorso di montaggio facoltativo.
-È possibile inoltre caricare una serie di funzioni middleware contemporaneamente e, in questo modo, si crea un sotto-stack del sistema middleware in un punto di montaggio.
-
-<h2 id='middleware.application'>Middleware a livello dell'applicazione</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-Questo esempio presenta una funzione middleware senza percorso di montaggio. La funzione viene eseguita ogni volta che l'app riceve una richiesta.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-Questo esempio presenta una funzione middleware montata nel percorso `/user/:id`. La funzione viene eseguita per qualsiasi tipo di
-richiesta HTTP nel percorso `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Questo esempio presenta una route e la relativa funzione handler (sistema middleware). La funzione gestisce richieste GET nel percorso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Ecco un esempio di caricamento di una serie di funzioni middleware in un punto di montaggio, con un percorso di montaggio.
-Illustra un sotto-stack middleware che stampa informazioni sulla richiesta per qualsiasi tipo di richiesta HTTP nel percorso `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Gli handler di route consentono di definire molteplici route per un percorso. Nell'esempio sottostante sono definite due route per richieste GET nel percorso `/user/:id`. La seconda route non provocherà alcun problema, ma non verrà mai chiamata, poiché la prima route termina il ciclo di richiesta-risposta.
-
-Questo esempio presenta un sotto-stack middleware che gestisce richieste GET nel percorso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-`redirect`
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-Questo esempio presenta un sotto-stack middleware che gestisce richieste GET nel percorso `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-Ecco un esempio di utilizzo della funzione middleware `express.static` con un oggetto opzioni elaborato:
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Middleware a livello del router</h2>
-
-Il middleware a livello del router funziona nello stesso modo di quello a livello dell'applicazione, fatta eccezione per il fatto di essere associato ad un'istanza di `express.Router()`.
-
-```js
-const router = express.Router()
-```
-
-Caricare il middleware a livello del router utilizzando le funzioni `router.use()` e `router.METHOD()`.
-
-Il seguente codice di esempio replica il sistema middleware mostrato sopra per il middleware a livello dell'applicazione, utilizzando il middleware a livello del router:
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-Per ulteriori dettagli sulla funzione `serve-static` e sulle relative opzioni, consultare: documentazione [serve-static](https://github.com/expressjs/serve-static).
-
-Questo esempio presenta un sotto-stack middleware che gestisce richieste GET nel percorso `/user/:id`.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Middleware di gestione degli errori</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Il middleware di gestione degli errori impiega sempre *quattro* argomenti. È necessario fornire quattro argomenti per identificarlo come funzione middleware di gestione degli errori. Anche se non è necessario utilizzare l'oggetto `next`, lo si deve specificare per mantenere la firma. Altrimenti, l'oggetto `next` verrà interpretato come middleware regolare e non sarà in grado di gestire gli errori.
-</div>
-
-Definire le funzioni middleware di gestione degli errori nello stesso modo delle altre funzioni middleware, ma con quattro argomenti invece di tre, nello specifico con la firma `(err, req, res, next)`):
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Per dettagli sul middleware di gestione degli errori, consultare la sezione: [Gestione degli errori](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Middleware integrato</h2>
-
-Dalla versione 4.x, Express non dipende più da [Connect](https://github.com/senchalabs/connect). Fatta eccezione per `express.static`, tutte le funzioni
-middleware che prima erano state incluse in Express, ora sono in moduli separati. Vedere [l'elenco delle funzioni middleware](https://github.com/senchalabs/connect#middleware).
-
-L'unica funzione middleware integrata in Express è `express.static`.
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Middleware di terzi</h2>
-
-Utilizzare il middleware di terzi per aggiungere funzionalità alle app Express.
-
-Installare il modulo Node.js per la funzionalità richiesta, quindi, caricarlo nella propria app a livello dell'applicazione o a livello del router.
-
-Il seguente esempio illustra l'installazione e il caricamento della funzione middleware di analisi dei cookie `cookie-parser`.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Per un elenco parziale delle funzioni middleware di terzi comunemente utilizzate con Express, consultare la sezione: [Middleware di terzi](../resources/middleware.html).
diff --git a/it/guide/using-template-engines.md b/it/guide/using-template-engines.md
deleted file mode 100644
index 68b0825ef6..0000000000
--- a/it/guide/using-template-engines.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: page
-title: Utilizzo di motori di template con Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Utilizzo di motori di template con Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, la directory dove sono ubicati i file di template. Ad esempio: `app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, il motore di template da utilizzare. Ad esempio: `app.set('view engine', 'pug')`
-
-Quindi, installare il pacchetto npm del motore di template corrispondente:
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-I motori di template compatibili con Express, ad esempio Pug esportano una funzione denominata `__express(filePath, options, callback)`, che viene richiamata dalla funzione `res.render()`, per il rendering del codice di template.
-
-Alcuni motori di template non seguono questa convenzione. La libreria [Consolidate.js](https://www.npmjs.org/package/consolidate) segue questa convenzione, associando tutti i motori di template Node.js popolari e, perciò, funziona ininterrottamente in Express.
-
-</div>
-
-Una volta specificata l'impostazione view engine, non è necessario specificare il motore o caricare il modulo del motore di template nella propria app; Express carica il modulo internamente, come mostrato di seguito (per l'esempio precedente).
-
-```js
-app.set('view engine', 'pug')
-```
-
-Creare un file di template Pug denominato `index.pug` nella directory `views`, con il seguente contenuto:
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Quindi, creare una route per il rendering del file `index.pug`. Se la proprietà `view engine` non è impostata, è necessario specificare l'estensione del file `view`. Altrimenti, è possibile ometterla.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Quando si fa una richiesta alla home page, verrà eseguito il rendering del file `index.pug` come HTML.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/it/guide/writing-middleware.md b/it/guide/writing-middleware.md
deleted file mode 100644
index 18300cbc65..0000000000
--- a/it/guide/writing-middleware.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: Compilazione del middleware per l'utilizzo nelle applicazioni Express
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Compilazione del middleware per l'utilizzo nelle applicazioni Express
-
-<h2>Panoramica</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
-
-Le funzioni middleware possono eseguire le attività elencate di seguito:
-
-- Eseguire qualsiasi codice.
-- Apportare modifiche agli oggetti richiesta e risposta.
-- Terminare il ciclo richiesta-risposta.
-- Chiamare il successivo middleware nello stack.
-
-Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve richiamare `next()` per passare il controllo alla successiva funzione middleware. Altrimenti, la richiesta verrà lasciata in sospeso.
-
-I seguenti esempi mostrano gli elementi di una chiamata alla funzione middleware:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">Metodo HTTP per cui si applica la funzione middleware.</div></tbody>
-
-<div class="callout" id="callout2">Percorso (route) per cui si applica la funzione middleware.</div>
-
-<div class="callout" id="callout3">La funzione middleware.</div>
-
-<div class="callout" id="callout4">Argomento di callback nella funzione middleware, denominata per convenzione "next".</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Esempio</h2>
-
-Ecco un esempio di una semplice applicazione Express "Hello World", per cui si definiranno due funzioni middleware:
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Ecco un semplice esempio di una funzione middleware, denominata "myLogger". Questa funzione stampa semplicemente la dicitura "LOGGED" quando una richiesta all'applicazione la attraversa. La funzione middleware è assegnata ad una variabile denominata `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Si noti la chiamata precedente a `next()`. Richiamando questa funzione si richiama la successiva funzione middleware nell'applicazione.
-La funzione `next()` non fa parte dell'API Express o Node.js, ma è il terzo argomento trasmesso alla funzione middleware. La funzione `next()` potrebbe essere denominata in qualsiasi modo, ma per convenzione viene sempre denominata "next".
-Per evitare confusione, utilizzare sempre questa convenzione.
-</div>
-
-Per caricare la funzione middleware, richiamare `app.use()`, specificando la funzione middleware.
-Ad esempio, il seguente codice carica la funzione middleware `myLogger` prima della route al percorso root (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Ogni volta che un'applicazione riceve una richiesta, viene stampato il messaggio "LOGGED" sul terminale.
-
-L'ordine di caricamento del middleware è importante: le funzioni middleware che vengono caricate per prime vengono anche eseguite per prime.
-
-Se `myLogger` viene caricato dopo la route sul percorso root, la richiesta non lo raggiunge mai e l'applicazione non stampa "LOGGED", poiché l'handler di route del percorso root termina il ciclo richiesta-risposta.
-
-La funzione middleware `myLogger` stampa semplicemente un messaggio, successivamente passa la richiesta alla successiva funzione middleware nello stack chiamando la funzione `next()`.
-
-<h3>Middleware function requestTime</h3>
-
-Nel successivo esempio viene aggiunta una proprietà denominata `requestTime` all'oggetto richiesta. Questa funzione middleware verrà denominata "requestTime".
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-L'applicazione utilizza ora la funzione middleware `requestTime`. Inoltre, la funzione di callback della route percorso root utilizza la proprietà che la funzione middleware aggiunge a `req` (l'oggetto richiesta).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-Quando si effettua una richiesta al root dell'applicazione, l'applicazione mostra la cronologia data e ora della richiesta nel browser.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Poiché si dispone dell'accesso all'oggetto richiesta, l'oggetto risposta, la successiva funzione middleware nello stack e l'API Node.js completo, le possibilità con le funzioni middleware sono infinite.
-
-Per ulteriori informazioni sul middleware Express, consultare: [Utilizzo del middleware Express](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/it/index.md b/it/index.md
deleted file mode 100644
index 9e755d243a..0000000000
--- a/it/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/it/resources/community.md b/it/resources/community.md
deleted file mode 100644
index 8fd396e306..0000000000
--- a/it/resources/community.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-layout: page
-title: Community di Express
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# Community
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-La nostra community molto attiva ha creato una vasta varietà di estensioni,
-[moduli middleware](/{{ page.lang }}/resources/middleware.html) e framework di livello più elevato.
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Problematiche
-
-Se si riscontra un bug o un problema oppure se si desidera semplicemente sottoporre una richiesta,
-aprire un ticket in [coda problemi](https://github.com/expressjs/express/issues).
-
-## Esempi
-
-Visualizzare dozzine di [esempi](https://github.com/expressjs/express/tree/master/examples)
-di applicazioni Express nel repository che copre tutto dall'autenticazione e progettazione API
-all'integrazione del motore di template.
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/it/resources/contributing.md b/it/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/it/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/it/resources/glossary.md b/it/resources/glossary.md
deleted file mode 100644
index a02d3b3811..0000000000
--- a/it/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Glossario di Express
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# Glossario
-
-### applicazione
-
-Solitamente, uno o più programmi progettati per gestire operazioni per uno scopo specifico.  In ambito di Express, un programma che utilizza API Express in esecuzione su una piattaforma Node.js.  Potrebbe inoltre fare riferimento a [app object](/{{ page.lang }}/api.html#express).
-
-### API
-
-Interfaccia di programmazione dell'applicazione. Si consiglia di scrivere per intero l'acronimo quando lo si usa per la prima volta.
-
-### Express
-
-Un framework web veloce, non categorico e minimalista per le applicazioni Node.js. Solitamente, si preferisce utilizzare "Express" piuttosto che "Express.js," anche se il secondo è accettabile.
-
-### libuv
-
-Una libreria di supporto multi-piattaforma che si focalizza su I/O asincrono, in principio sviluppato per essere utilizzato da Node.js.
-
-### middleware
-
-Una funzione che viene richiamata dal livello di routing Express prima dell'handler di richiesta finale, pertanto si trova al centro tra una richiesta base e la route prevista. Segue un elenco che indica alcune terminologie utilizzate per middleware:
-
-- `var foo = require('middleware')` significa _richiesta_ o _utilizzo_ di un modulo Node.js. E l'istruzione `var mw = foo()` solitamente restituisce il middleware.
-- `app.use(mw)` significa _aggiunta del middleware allo stack di elaborazione globale_.
-- `app.get('/foo', mw, function (req, res) { ... })` significa _aggiunta del middleware allo stack di elaborazione "GET /foo"_.
-
-### Node.js
-
-Una piattaforma software utilizzata per creare applicazioni di rete scalabili. Node.js utilizza JavaScript e il relativo linguaggio di scripting e raggiunge una trasmissione di dati elevata tramite un I/O non a blocchi e un loop di evento a thread singolo. Consultare [nodejs.org](http://nodejs.org/). **Nota di utilizzo**: Inizialmente, "Node.js," successivamente "Node".
-
-### open-source, open source
-
-Quando utilizzato come aggettivo, viene aggiunto un trattino; ad esempio: "Questo è un software open-source." Consultare [Software open-source su Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### richiesta
-
-Una richiesta HTTP. Un client un messaggio di richiesta HTTP a un server, il quale restituisce una risposta.  La richiesta deve utilizzare uno dei diversi [metodi di richiesta](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) ad esempio GET, POST e così via.
-
-### risposta
-
-Una risposta HTTP. Un server restituisce un messaggio di risposta HTTP al client. La risposta contiene le informazioni sullo stato di completamento su una richiesta e potrebbe inoltre contenere del contenuto richiesto nel corpo del messaggio.
-
-### route
-
-Parte di un URL che identifica una risorsa. Ad esempio, in `http://foo.com/products/id`, "/products/id" è la route.
-
-### router
-
-Consultare [router](/{{ page.lang }}/4x/api.html#router) nei riferimenti API.
diff --git a/it/resources/middleware.md b/it/resources/middleware.md
deleted file mode 100644
index 723da0f4eb..0000000000
--- a/it/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Middleware Express
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Middleware Express
-
-Di seguito vengono riportati alcuni moduli middleware Express:
-
-| Middleware module                                                           | Descrizione                                                                                                                         |
-| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                                             |
-
-## Per ulteriori moduli middleware, consultare:
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Middleware module                                                                                                                                               | Descrizione                                                                                                                                                                                   |
-| --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet): modulo che aiuta a proteggere le applicazioni impostando varie intestazioni HTTP. | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport): modulo middleware Express per l'autenticazione.                            | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/it/resources/middleware/body-parser.md b/it/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/it/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/it/resources/middleware/compression.md b/it/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/it/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/it/resources/middleware/connect-rid.md b/it/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/it/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/it/resources/middleware/cookie-parser.md b/it/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/it/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/it/resources/middleware/cookie-session.md b/it/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/it/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/it/resources/middleware/cors.md b/it/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/it/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/it/resources/middleware/errorhandler.md b/it/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/it/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/it/resources/middleware/method-override.md b/it/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/it/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/it/resources/middleware/morgan.md b/it/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/it/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/it/resources/middleware/multer.md b/it/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/it/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/it/resources/middleware/response-time.md b/it/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/it/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/it/resources/middleware/serve-favicon.md b/it/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/it/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/it/resources/middleware/serve-index.md b/it/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/it/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/it/resources/middleware/serve-static.md b/it/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/it/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/it/resources/middleware/session.md b/it/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/it/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/it/resources/middleware/timeout.md b/it/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/it/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/it/resources/middleware/vhost.md b/it/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/it/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/it/resources/utils.md b/it/resources/utils.md
deleted file mode 100644
index 168c494d51..0000000000
--- a/it/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | Descrizione                                                                                                                                                                                                                |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/it/starter/basic-routing.md b/it/starter/basic-routing.md
deleted file mode 100644
index 87eaadaa72..0000000000
--- a/it/starter/basic-routing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: Routing di base Express
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# Routing di base
-
-Per _Routing_ si intende determinare come un'applicazione risponde a una richiesta client a un endpoint particolare, il quale è un URI (o percorso) e un metodo di richiesta HTTP specifico (GET, POST e così via).
-
-Ciascuna route può disporre di una o più funzioni dell'handler, le quali vengono eseguite quando si trova una corrispondenza per la route.
-
-La definizione della route ha la seguente struttura:
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Dove:
-
-- `app` è un'istanza di `express`.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` è un percorso sul server.
-- `HANDLER` è la funzione eseguita quando si trova una corrispondenza per la route.
-
-<div class="doc-box doc-notice" markdown="1">
-Questo tutorial presume che un'istanza di `express` denominata `app` sia stata creata e che il server sia in esecuzione. Se non si è in grado di creare un'applicazione e avviarla, consultare la sezione [Esempio di Hello world](/{{ page.lang }}/starter/hello-world.html).
-</div>
-
-I seguenti esempi mostrano come definire route semplici.
-
-Rispondere con `Hello World!` sulla homepage:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Rispondere a una richiesta PUT alla route `/user`:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Rispondere a una richiesta DELETE alla route `/user`:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-Per ulteriori dettagli sul routing, consultare il [Manuale routing](/{{ page.lang }}/guide/routing.html).
-
diff --git a/it/starter/examples.md b/it/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/it/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/it/starter/faq.md b/it/starter/faq.md
deleted file mode 100644
index f617055c42..0000000000
--- a/it/starter/faq.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-layout: page
-title: FAQ di Express
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# FAQ
-
-## In che modo devo strutturare l'applicazione?
-
-Non esiste una risposta definitiva a questa domanda. La risposta dipende
-dalla scalabilità dell'applicazione e dal team coinvolto. Per essere molto flessibile,
-Express non fornisce molte indicazioni in termini di struttura.
-
-Le route e altre logiche specifiche dell'applicazione possono essere presenti in molti file,
-in qualsiasi struttura di directory desiderata. Visualizzare i seguenti
-esempi:
-
-- [Elenchi route](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Definizione route](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [Controllori stile MVC](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Inoltre, ci sono delle estensioni di terze parti per Express, le quali semplificano alcuni di questi modelli:
-
-- [Routing pieno di risorse](https://github.com/expressjs/express-resource)
-
-## In che modo è possibile definire i modelli?
-
-Express non ha nessuna nozione di database. Questo concetto viene lasciato a moduli
-Node di terzi, consentendo di interfacciarsi
-con quasi qualsiasi database.
-
-Consultare [LoopBack](http://loopback.io) per un framework basato su Express incentrato sui modelli.
-
-## In che modo è possibile autenticare gli utenti?
-
-L'autenticazione è un'altra area categorica in cui non si
-avventura Express. È possibile utilizzare qualsiasi schema di autenticazione desiderato.
-Per uno schema nome utente / password semplice, consultare [questo esempio](https://github.com/expressjs/express/tree/master/examples/auth).
-
-## Quale motore di template supporta Express?
-
-Express supporta qualsiasi motore di template conforme alla sigla `(path, locals, callback)`.
-Per normalizzare le interfacce del motore di template e la memorizzazione in cache, consultare il progetto
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-per il supporto. I motori di template potrebbero ancora non supportare Express.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## In che modo è possibile gestire le risposte 404?
-
-In Express, le risposte 404 non sono il risultato di un errore, pertanto
-il middleware di gestione degli errori non le individuerà. Questo accade perché
-una risposta 404 indica semplicemente l'assenza di ulteriori operazioni da effettuare;
-in altre parole, Express ha eseguito tutte le funzioni middleware e route
-e non ha riscontrato nessuna risposta da parte di quest'ultimi. L'unica cosa da fare è aggiungere
-una funzione middleware alla parte finale dello stack (sotto tutte le altre funzioni)
-per gestire una risposta 404:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## In che modo è possibile impostare un gestore degli errori?
-
-È possibile definire il middleware di gestione degli errori nello stesso modo in cui si definisce qualsiasi altro middleware,
-ad eccezione delle funzioni di gestione degli errori che hanno quattro argomenti invece di tre; nello specifico la firma `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Per ulteriori informazioni, consultare [Gestione degli errori](/{{ page.lang }}/guide/error-handling.html).
-
-## In che modo è possibile eseguire il rendering dell'HTML normale?
-
-Non è necessario farlo! Non è necessario "eseguire il rendering" dell'HTML con la funzione `res.render()`.
-Se si dispone di un file specifico, utilizzare la funzione `res.sendFile()`.
-Se si stanno gestendo molti asset da una directory, utilizzare la funzione middleware
-`express.static()`.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/it/starter/generator.md b/it/starter/generator.md
deleted file mode 100644
index 4465619aea..0000000000
--- a/it/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Programma di creazione applicazione Express
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Programma di creazione applicazione Express
-
-Utilizzare lo strumento di creazione dell'applicazione, `express`, per creare velocemente una struttura dell'applicazione.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Visualizzare le opzioni del comando con l'opzione `-h`:
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-Ad esempio, quanto segue crea un'applicazione Express denominata _myapp_ nella directory di lavoro corrente: The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-Successivamente, installare le dipendenze:
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-Su Windows, utilizzare questo comando:
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-Su MacOS o Linux, eseguire l'applicazione con il seguente comando:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-Quindi caricare `http://localhost:3000/` sul browser per accedere all'applicazione.
-
-L'applicazione creata dispone della seguente struttura per la directory:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-La struttura dell'applicazione creata dal programma di creazione è solo uno dei tanti modi disponibili per creare la struttura delle applicazioni Express. È possibile utilizzare questa struttura o modificarla a seconda delle proprie necessità.
-</div>
\ No newline at end of file
diff --git a/it/starter/hello-world.md b/it/starter/hello-world.md
deleted file mode 100644
index f7cf1edc38..0000000000
--- a/it/starter/hello-world.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-layout: page
-title: Esempio di "Hello World" di express
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Esempio di Hello world
-
-<div class="doc-box doc-info" markdown="1">
-In sostanza, questa sarà l'applicazione Express più semplice che è possibile creare. È un'applicazione a singolo file &mdash; e *non* quello che si ottiene se si utilizza il [Programma di creazione Express](/{{ page.lang }}/starter/generator.html), il quale crea le fondamenta per un'applicazione completa con molti file JavaScript, template Jade e sotto directory per diversi scopi.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-L'applicazione avvia un server e resta in ascolto sulla porta 3000 per le connessioni. L'applicazione risponde con "Hello World!" per le richieste
-all'URL root (`/`) o _route_. Per qualsiasi altro percorso, risponderà con il messaggio **404 Non trovato**.
-
-### Running Locally
-
-Per prima cosa creare una directory denominata `myapp`, passare a quest'ultima ed eseguire `npm init`. Quindi installare `express` come dipendenza, come descritto nella [Guida all'installazione](/{{ page.lang }}/starter/installing.html).
-
-Nella directory `myapp`, creare un file denominato `app.js` e aggiungere il seguente codice:
-
-<div class="doc-box doc-notice" markdown="1">
-I valori `req` (richiesta) e `res` (risposta) sono esattamente gli stessi oggetti forniti da Node, quindi è possibile richiamare
-`req.pipe()`, `req.on('data', callback)` e qualsiasi cosa che si farebbe senza il coinvolgimento di Express.
-</div>
-
-Eseguire l'applicazione con il seguente comando:
-
-```bash
-$ node app.js
-```
-
-Successivamente, caricare [http://localhost:3000/](http://localhost:3000/) su un browser per visualizzare l'output.
\ No newline at end of file
diff --git a/it/starter/installing.md b/it/starter/installing.md
deleted file mode 100644
index 23b60b8465..0000000000
--- a/it/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Installazione di Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# Installazione
-
-Presumendo che sia stato già installato [Node.js](https://nodejs.org/), creare una directory in cui conservare l'applicazione e renderla la directory di lavoro.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Utilizzare il comando `npm init` per creare un file `package.json` per l'applicazione.
-Per ulteriori informazioni sul funzionamento di `package.json`, consultare [Informazioni specifiche sulla gestione di package.json di npm](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-Questo comando richiede di specificare alcune informazioni, ad esempio il nome e la versione dell'applicazione.
-Per il momento, è possibile semplicemente premere il tasto INVIO per accettare i valori di default per molti di esse, ad eccezione di quanto segue:
-
-```
-entry point: (index.js)
-```
-
-Immettere `app.js` o qualsiasi altra cosa come nome del file principale. Se si desidera che sia `index.js`, premere il tasto INVIO per accettare il nome file predefinito consigliato.
-
-Quindi installare Express nella directory `myapp` e salvarlo nell'elenco delle dipendenze. Ad esempio:
-
-```bash
-$ npm install express
-```
-
-Per installare momentaneamente Express e non aggiungerlo all'elenco di dipendenze, omettere l'opzione `--save`:
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-I moduli Node installati con l'opzione `--save` vengono aggiunti all'elenco `dependencies` nel file `package.json`. Successivamente, l'esecuzione di `npm install` nella directory `app` installerà automaticamente i moduli nell'elenco di dipendenze.
-</div>
\ No newline at end of file
diff --git a/it/starter/static-files.md b/it/starter/static-files.md
deleted file mode 100644
index 76a34532e7..0000000000
--- a/it/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: Gestione dei file statici in Express
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Gestione dei file statici in Express
-
-Per gestire i file statici, quali immagini, file CSS e file JavaScript, utilizzare la funzione middleware integrata `express.static` in Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-Ad esempio, utilizzare il seguente codice per gestire le immagini, i file CSS e i file JavaScript nella directory denominata `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-Ora, è possibile caricare i file che si trovano nella directory `public`:
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express ricerca i file relativi alla directory statica, pertanto il nome della directory statica non è parte dell'URL.
-</div>
-
-Per utilizzare più directory di asset statiche, richiamare la funzione middleware `express.static` più volte:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express ricerca i file nell'ordine in cui sono state impostate le directory statiche con la funzione middleware `express.static`.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Ora, è possibile caricare i file che si trovano nella directory `public` dal prefisso del percorso `/static`.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-Tuttavia, il percorso fornito per la funzione `express.static` è relativo alla directory dalla quale è possibile avviare il processo `node`. Se si esegue l'applicazione express da un'altra directory, è preferibile utilizzare il percorso assoluto della directory che si desidera gestire:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/it/support/index.md b/it/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/it/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/ja/3x/api.md b/ja/3x/api.md
deleted file mode 100644
index 39825ab5e4..0000000000
--- a/ja/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API リファレンス
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x は保守されなくなりました**
-
-3.xの既知および未知のセキュリティ問題は、最終更新（2015年8月1日）以降は対処されていません。3.x系を使用することは安全であると見なされるべきではありません。 It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>3.x API</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/ja/4x/api.md b/ja/4x/api.md
deleted file mode 100644
index 3c4d11eeb7..0000000000
--- a/ja/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API リファレンス
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>4.x API</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/ja/5x/api.md b/ja/5x/api.md
deleted file mode 100644
index 9f1f5222ea..0000000000
--- a/ja/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API リファレンス
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/ja/advanced/best-practice-performance.md b/ja/advanced/best-practice-performance.md
deleted file mode 100644
index e4ce2161c0..0000000000
--- a/ja/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: 実稼働環境における Express の使用におけるパフォーマンスに関するベスト・プラクティス
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# 実稼働環境におけるベスト・プラクティス: パフォーマンスと信頼性
-
-この記事では、実稼働環境にデプロイされた Express アプリケーションのパフォーマンスと信頼性に関するベスト・プラクティスについて説明します。
-
-This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
-
-- コードで実行する処理 (開発部分)
-  - [gzip 圧縮を使用する](#use-gzip-compression)
-  - [同期関数を使用しない](#dont-use-synchronous-functions)
-  - [ロギングを正確に実行する](#do-logging-correctly)
-  - [例外を適切に処理する](#handle-exceptions-properly)
-- 環境/セットアップで実行する処理 (運用部分)
-  - [Set NODE_ENV to "production"](#set-node_env-to-production)
-  - [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
-  - [Run your app in a cluster](#run-your-app-in-a-cluster)
-  - [Cache request results](#cache-request-results)
-  - [Use a load balancer](#use-a-load-balancer)
-  - [Use a reverse proxy](#use-a-reverse-proxy)
-
-## コードで実行する処理 {#in-code}
-
-以下に、アプリケーションのパフォーマンスを向上させるためにコードで実行できる処理をいくつか挙げます。
-
-- [gzip 圧縮を使用する](#use-gzip-compression)
-- [同期関数を使用しない](#dont-use-synchronous-functions)
-- [ロギングを正確に実行する](#do-logging-correctly)
-- [例外を適切に処理する](#handle-exceptions-properly)
-
-### gzip 圧縮を使用する
-
-Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Gzip 圧縮により、応答本体のサイズを大幅に縮小できるため、Web アプリケーションの速度が高くなります。Express アプリケーションで gzip 圧縮として [compression](https://www.npmjs.com/package/compression) ミドルウェアを使用してください。次に例を示します。 For example:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. トラフィックが多い実稼働環境の Web サイトでは、圧縮を適用する最適な方法は、リバース・プロキシー・レベルで実装することです ([リバース・プロキシーの使用](#proxy)を参照)。その場合は、compression ミドルウェアを使用する必要はありません。Nginx で gzip 圧縮を有効にする方法について詳しくは、Nginx 資料の [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html) を参照してください。
-
-### 同期関数を使用しない
-
-同期の関数とメソッドは、返されるまで実行中のプロセスを結合します。同期関数に対する 1 回の呼び出しは数マイクロ秒から数ミリ秒で返される可能性がありますが、トラフィックが多い Web サイトでは、これらの呼び出しを合計すると、アプリケーションのパフォーマンスが低下します。実稼働環境では、これらを使用しないでください。 A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
-
-ノードおよび多くのモジュールは、同期版と非同期版の関数を提供していますが、実稼働環境では必ず非同期版を使用してください。同期関数を使用しても構わないのは、初期始動時のみです。 The only time when a synchronous function can be justified is upon initial startup.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
-
-### ロギングを正確に実行する
-
-In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### For debugging
-
-デバッグの目的でロギングを実行する場合は、`console.log()` を使用するのではなく、[debug](https://www.npmjs.com/package/debug) などの特殊なデバッグ・モジュールを使用します。このモジュールでは、DEBUG 環境変数を使用して、`console.err()` に送信されるデバッグ・メッセージを制御できます。アプリケーションを純粋に非同期的にしておくために、`console.err()` を別のプログラムにパイプ接続することもできます。しかし、実稼働環境ではデバッグを実行することはお勧めしません。 This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
-
-#### アプリケーション・アクティビティー
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### 例外を適切に処理する
-
-Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. [アプリケーションが確実に自動再始動するようにする](#ensure-your-app-automatically-restarts) Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
-
-確実にすべての例外を処理するには、以下の技法を使用します。
-
-- [Try-catch の使用](#try-catch)
-- [Promise の使用](#promises)
-
-Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. 上記のトピックを読む前に、error-first コールバックの使用と、ミドルウェアへのエラーの伝搬という Node/Express エラー処理の基礎を理解しておく必要があります。Node は、非同期関数からエラーを返すために「error-first コールバック」という規則を使用します。この場合、コールバック関数への最初のパラメーターがエラー・オブジェクトで、その後に続くパラメーターに結果データがあります。エラーがないことを示すには、最初のパラメーターとして `null` を渡します。コールバック関数は、エラーを有意に処理するには、error-first コールバック規則に対応して従う必要があります。Express におけるベスト・プラクティスは、next() 関数を使用して、ミドルウェア・チェーンを介してエラーを伝搬することです。 To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
-
-エラー処理のその他の基礎については、下記を参照してください。
-
-- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Try-catch の使用
-
-Try-catch は、同期コードで例外をキャッチするために使用できる JavaScript 言語構造体です。Try-catch は、例えば、下記のように JSON 構文解析エラーを処理するために使用します。 Use try-catch, for example, to handle JSON parsing errors as shown below.
-
-Here is an example of using try-catch to handle a potential process-crashing exception.
-This middleware function accepts a query field parameter named "params" that is a JSON object.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-However, try-catch works only for synchronous code. ただし、Try-catch は同期コードでのみ機能します。Node プラットフォームは主に (特に実稼働環境で) 非同期的であるため、Try-catch は多くの例外をキャッチしません。
-
-#### Promise の使用
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### 実行してはならないこと
-
-One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
-
-さらに、`uncaughtException` の使用は、正式に[粗雑なもの](https://nodejs.org/api/process.html#process_event_uncaughtexception)として認められており、これをコアから削除するための[提案](https://github.com/nodejs/node-v0.x-archive/issues/2582)が出されています。したがって、`uncaughtException` を listen するのは悪い方法です。この理由から複数のプロセスとスーパーバイザーなどの使用をお勧めしています。異常終了と再始動は、場合によってはエラーから復旧するための最も信頼できる方法となります。 So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-
-また、[domain](https://nodejs.org/api/domain.html) の使用もお勧めしません。このモジュールは概して問題を解決しないため、推奨されていません。 It generally doesn't solve the problem and is a deprecated module.
-
-## 環境/セットアップで実行する処理
-
-以下に、アプリケーションのパフォーマンスを向上させるためにシステム環境で実行できる処理をいくつか挙げます。
-
-- [Set NODE_ENV to "production"](#set-node_env-to-production)
-- [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
-- [Run your app in a cluster](#run-your-app-in-a-cluster)
-- [Cache request results](#cache-request-results)
-- [Use a load balancer](#use-a-load-balancer)
-- [Use a reverse proxy](#use-a-reverse-proxy)
-
-### NODE_ENV を「production」に設定する
-
-NODE_ENV 環境変数は、アプリケーションが実行される環境 (通常は開発または実稼働) を指定します。パフォーマンスを向上させるために実行できる最も単純な処理の 1 つは、NODE_ENV を「production」に設定することです。 One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-NODE_ENV を「production」に設定すると、Express は次のようになります。
-
-- ビュー・テンプレートをキャッシュに入れる。
-- CSS 拡張から生成された CSS ファイルをキャッシュに入れる。
-- 詳細度の低いエラー・メッセージを生成する。
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-環境固有のコードを作成する必要がある場合は、`process.env.NODE_ENV` を使用して NODE_ENV の値を確認できます。どの環境変数の値を確認する場合でもパフォーマンスに悪影響が及ぶため、慎重に行ってください。 Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
-
-開発環境では、通常、対話式シェルで環境変数を設定します。例えば、`export` または `.bash_profile` ファイルを使用します。しかし、一般的には実動サーバーではそうしません。代わりに、OS の init システム (systemd または Upstart) を使用します。次のセクションでは、init システムの一般的な使用法について詳しく説明しています。ここで重点的に説明したのは、NODE_ENV の設定がパフォーマンスにとって極めて重要であるため (かつ簡単に実行できるため) です。 But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
-
-systemd では、unit ファイルで `Environment` ディレクティブを使用します。次に例を示します。 For example:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### アプリケーションが確実に自動再始動するようにする
-
-In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
-
-- アプリケーション (および Node) が異常終了した場合にプロセス・マネージャーを使用してそれらを再始動する。
-- Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
-
-Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
-
-#### プロセス・マネージャーを使用する
-
-開発環境では、単にコマンド・ラインから `node server.js` などを使用してアプリケーションを開始しています。ただし、この方法を実稼働環境で実行すると、危険を招くことになります。アプリケーションが異常終了した場合、アプリケーションは再始動されるまでオフラインになります。アプリケーションが異常終了した場合に確実に再始動するようにするには、プロセス・マネージャーを使用します。プロセス・マネージャーは、デプロイメントを容易に行えるようにして、高可用性を実現し、アプリケーションを実行時に管理できるようにする、アプリケーションの「コンテナー」です。 But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
-
-アプリケーションを異常終了時に再始動することに加えて、プロセス・マネージャーでは以下が可能になります。
-
-- ランタイム・パフォーマンスとリソース使用量に関するインサイトを得る。
-- パフォーマンスを向上させるために設定を動的に変更する。
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### init システムの使用
-
-The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-Express アプリケーションで init システムを使用する方法は 2 つあります。
-
-- Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
-- init システムで直接、アプリケーション (および Node) を実行します。この方法の方が単純ですが、プロセス・マネージャーを使用する場合に得られる利点は得られません。 This is somewhat simpler, but you don't get the additional advantages of using a process manager.
-
-##### Systemd
-
-Systemd は、Linux システムとサービス・マネージャーです。大半の主要な Linux ディストリビューションでは、Systemd がデフォルトの init システムとして採用されています。 Most major Linux distributions have adopted systemd as their default init system.
-
-Systemd サービス構成ファイルは、_unit ファイル_ という名前で、ファイル名の末尾は .service です。次に、Node アプリケーションを直接管理するための unit ファイルの例を示します (太字のテキストを、ご使用のシステムとアプリケーションの値に置き換えてください)。 Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Systemd について詳しくは、[systemd の解説 (man ページ)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html) を参照してください。
-
-### アプリケーションをクラスターで実行する
-
-マルチコア・システムでは、プロセスのクラスターを起動することで、Node アプリケーションのパフォーマンスを数倍も向上させることができます。クラスターは、アプリケーションの複数インスタンスを実行して (理想的には CPU コアごとに 1 つのインスタンス)、負荷とタスクをインスタンス間で分散させます。 A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
-
-![クラスター API を使用したアプリケーション・インスタンス間のバランシング](/images/clustering.png)
-
-IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
-
-In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. クラスター・アプリケーションでは、ワーカー・プロセスは、残りのプロセスに影響を与えることなく、個々に異常終了することがあります。パフォーマンス上の利点の他に障害分離は、アプリケーション・プロセスのクラスターを実行するもう 1 つの理由です。ワーカー・プロセスが異常終了するたびに、必ず、イベントをログに記録して、cluster.fork() を使用して新規プロセスを作成してください。
-
-#### Node のクラスター・モジュールの使用
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
-
-#### PM2 の使用
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, a given application with the name `app` can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### 要求の結果をキャッシュに入れる
-
-実稼働環境のパフォーマンスを向上させるもう 1 つの戦略は、アプリケーションが同じ要求に何回も対応するために操作を繰り返すことがないように、要求の結果をキャッシュに入れることです。
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### [ロード・バランサーを使用する](#use-a-load-balancer)
-
-アプリケーションがどれだけ最適化されていても、単一インスタンスは、限られた量の負荷とトラフィックしか処理できません。アプリケーションを拡張する 1 つの方法は、複数インスタンスを実行して、ロード・バランサーを使用してトラフィックを分散させることです。ロード・バランサーをセットアップすると、アプリケーションのパフォーマンスと速度を向上させることができ、単一インスタンスよりも大規模に拡張できます。 One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
-
-A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### [リバース・プロキシーを使用する](#use-a-reverse-proxy)
-
-A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
-
-アプリケーションの状態を知る必要のないタスクをリバース・プロキシーに引き渡すことで、Express が解放されて、特殊なアプリケーション・タスクを実行できるようになります。この理由から、実稼働環境で Express を [Nginx](https://www.nginx.com/) や [HAProxy](http://www.haproxy.org/) などのリバース・プロキシーの背後で実行することをお勧めします。 For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/ja/advanced/best-practice-security.md b/ja/advanced/best-practice-security.md
deleted file mode 100644
index 9aeb18cea5..0000000000
--- a/ja/advanced/best-practice-security.md
+++ /dev/null
@@ -1,282 +0,0 @@
----
-layout: page
-title: 実稼働環境における Express のセキュリティーに関するベスト・プラクティス
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# 実稼働環境におけるベスト・プラクティス: セキュリティー
-
-## 概説
-
-The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
-
-Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-本番環境でのExpressアプリケーションのセキュリティのベスト・プラクティスは次のとおりです。
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [TLS を使用する](#use-tls)
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [Helmet を使用する](#use-helmet)
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - [Cookie をセキュアに使用する](#use-cookies-securely)
-    - 対照的に、[cookie-session](https://www.npmjs.com/package/cookie-session) ミドルウェアは、Cookie が支持するストレージを実装します。セッション・キーだけでなく、セッション全体を Cookie に対して直列化します。これは、セッション・データが比較的小規模で、(オブジェクトではなく) プリミティブ値として容易にエンコードできる場合にのみ使用してください。ブラウザーは Cookie 当たり最小 4096 バイトをサポートすることが想定されますが、その制限を必ず超えないようにするために、ドメイン当たり 4093 バイトのサイズを超えないようにしてください。また、Cookie データがクライアントに対して可視になることに注意してください。何らかの理由でデータを保護したり覆い隠したりする必要がある場合は、express-session を使用することをお勧めします。
-    - デフォルトのセッション Cookie 名を使用すると、アプリケーションが攻撃を受けやすくなります。提起されているセキュリティー問題は `X-Powered-By` と似ています。潜在的なアタッカーがこれを使用して、サーバーに対して指紋認証し、攻撃の標的にする可能性があります。
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [依存関係がセキュアであることを確認する](#ensure-your-dependencies-are-secure)
-    - [その他の既知の脆弱性を回避する](#avoid-other-known-vulnerabilities)
-  - [その他の考慮事項](#additional-considerations)
-
-## 非推奨バージョンや脆弱なバージョンの Express を使用しない
-
-Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html) or consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-また、[セキュリティー更新ページ](/{{ page.lang }}/advanced/security-updates.html)にリストされている脆弱な Express バージョンを使用していないことを確認してください。使用している場合は、安定しているリリース (最新を推奨します) に更新してください。 If you are, update to one of the stable releases, preferably the latest.
-
-## TLS を使用する
-
-If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-You may be familiar with Secure Socket Layer (SSL) encryption. Secure Socket Layer (SSL) 暗号化については理解されていると思います。[TLS は、単に SSL が進化したものです](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx)。つまり、以前に SSL を使用していた場合は、TLS へのアップグレードを検討してください。一般に、TLS を処理するために Nginx を使用することをお勧めします。Nginx (およびその他のサーバー) で TLS を構成するための解説については、[Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations) を参照してください。 In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-また、[Let's Encrypt](https://letsencrypt.org/about/) は、無料の TLS 証明書を取得するための便利なツールです。このツールは、[Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/) が提供する、無料の自動的かつオープンな認証局 (CA) です。
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Helmet を使用する
-
-[Helmet](https://www.npmjs.com/package/helmet) は、HTTP ヘッダーを適切に設定することによって、いくつかの既知の Web の脆弱性からアプリケーションを保護します。
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-その他のモジュールと同様に Helmet をインストールします。
-
-```bash
-$ npm install helmet
-```
-
-次に、コードで使用します。
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-そのため、`app.disable()` メソッドを使用してこのヘッダーをオフにすることがベスト・プラクティスです。
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Cookie をセキュアに使用する
-
-Cookie を介してアプリケーションが悪用されないように、デフォルトの セッション Cookie 名を使用しないでください。また、Cookie のセキュリティー・オプションを適切に設定してください。
-
-主なミドルウェア Cookie セッション・モジュールが 2 つあります。
-
-- [express-session](https://www.npmjs.com/package/express-session) は、Express 3.x に組み込まれていた `express.session` ミドルウェアに取って代わります。
-- [cookie-session](https://www.npmjs.com/package/cookie-session) は、Express 3.x に組み込まれていた `express.cookieSession` ミドルウェアに取って代わります。
-
-The main difference between these two modules is how they save cookie session data. これらの 2 つのモジュールの主な違いは、Cookie セッション・データの保存方法です。[express-session](https://www.npmjs.com/package/express-session) ミドルウェアは、セッション・データをサーバーに保管します。セッション・データではなく、Cookie 自体の中にあるセッション ID のみを保存します。デフォルトで、メモリー内のストレージを使用し、実稼働環境向けには設計されていません。実稼働環境では、スケーラブルなセッション・ストアをセットアップする必要があります。[互換性のあるセッション・ストア](https://github.com/expressjs/session#compatible-session-stores)のリストを参照してください。 By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-
-In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
-
-### デフォルトのセッション Cookie 名を使用しない
-
-Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
-
-この問題を回避するには、汎用な Cookie 名を使用します。例えば、[express-session](https://www.npmjs.com/package/express-session) ミドルウェアを使用します。
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Cookie のセキュリティー・オプションを設定する
-
-セキュリティーを強化するために、以下の Cookie オプションを設定します。
-
-- `secure` - ブラウザーが確実に HTTPS のみを介して Cookie を送信するようにします。
-- `httpOnly` - Cookie がクライアント JavaScript ではなく、HTTP(S) のみを介して送信されるようにして、クロスサイト・スクリプティング攻撃から保護します。
-- `domain` - Cookie のドメインを指定します。URL が要求されているサーバーのドメインとの比較に使用します。一致する場合は、次にパス属性を確認します。 If they match, then check the path attribute next.
-- `path` - Cookie のパスを指定します。要求パスとの比較に使用します。このパスがドメインと一致する場合は、要求の Cookie を送信します。 If this and domain match, then send the cookie in the request.
-- `expires` - 永続的な Cookie の有効期限を設定するために使用します。
-
-次に、[cookie-session](https://www.npmjs.com/package/cookie-session) ミドルウェアの使用例を示します。
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## 依存関係がセキュアであることを確認する
-
-npm を使用したアプリケーションの依存関係の管理は、強力で便利な方法です。ただし、使用するパッケージに、アプリケーションにも影響を与える可能性がある重大なセキュリティーの脆弱性が含まれている可能性があります。アプリケーションのセキュリティーの強さは、依存関係の中で「最も弱いリンク」程度でしかありません。 But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. npm@6以降、npmはすべてのインストール要求を自動的に確認します。また、'npm audit'を使用して依存関係ツリーを分析することもできます。
-
-```bash
-$ npm audit
-```
-
-よりセキュアな状態を保ちたい場合は、[Snyk](https://snyk.io/)を検討してください。
-
-Snykは、[Snykのオープンソース脆弱性データベース](https://snyk.io/vuln/)に対して、依存関係の既知の脆弱性に対するアプリケーションをチェックする[コマンドラインツール](https://www.npmjs.com/package/snyk)と[Github integration](https://snyk.io/docs/github)を提供しています。 次のようにCLIをインストールします。 Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-このコマンドを使用して、アプリケーションの脆弱性をテストします。
-
-```bash
-$ snyk test
-```
-
-### その他の既知の脆弱性を回避する
-
-アプリケーションで使用する Express やその他のモジュールに影響を与える可能性がある [Node Security Project](https://npmjs.com/advisories) のアドバイザリーに常に注意してください。一般に、Node Security Project は、Node のセキュリティーに関する知識とツールの優れたリソースです。 In general, these databases are excellent resources for knowledge and tools about Node security.
-
-最後に、Express アプリケーションは、その他の Web アプリケーションと同様、さまざまな Web ベースの攻撃に対して脆弱になりえます。既知の [Web の脆弱性](https://www.owasp.org/www-project-top-ten/)をよく理解して、それらを回避するための予防措置を取ってください。 Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
-
-## その他の考慮事項
-
-次に、優れた [Node.js セキュリティー・チェックリスト](https://blog.risingstack.com/node-js-security-checklist/)に記載されているその他の推奨事項をリストします。これらの推奨事項の詳細については、ブログの投稿を参照してください。 Refer to that blog post for all the details on these recommendations:
-
-- クロスサイト・スクリプティング (XSS) とコマンド・インジェクション攻撃から保護するために、必ず、ユーザー入力のフィルタリングとサニタイズを実行してください。
-- パラメーター化照会または作成済みステートメントを使用して、SQL インジェクション攻撃に対して防衛してください。
-- オープン・ソースの [sqlmap](http://sqlmap.org/) ツールを使用して、アプリケーションの SQL インジェクションに対する脆弱性を検出してください。
-- [nmap](https://nmap.org/) ツールと [sslyze](https://github.com/nabla-c0d3/sslyze) ツールを使用して、SSL 暗号、鍵、再交渉の構成のほか、証明書の妥当性をテストしてください。
-- [safe-regex](https://www.npmjs.com/package/safe-regex) を使用して、使用している正規表現が[正規表現サービス妨害](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS)攻撃を受けやすくなっていないことを確認してください。
-
-[helmet]: <`helmet.js` を使用する場合は、この操作が自動的に実行されます。>
\ No newline at end of file
diff --git a/ja/advanced/developing-template-engines.md b/ja/advanced/developing-template-engines.md
deleted file mode 100644
index bcc9a3a6e1..0000000000
--- a/ja/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Express 用のテンプレート・エンジンの開発
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Express 用のテンプレート・エンジンの開発
-
-独自のテンプレート・エンジンを作成するには、`app.engine(ext, callback)` メソッドを使用します。`ext` はファイル拡張子を表し、`callback` はテンプレート・エンジン関数です。この関数は、ファイルのロケーション、options オブジェクト、およびコールバック関数の項目をパラメーターとして受け入れます。 `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
-
-次のコードは、`.ntl` ファイルをレンダリングするための極めて単純なテンプレート・エンジンを実装する例です。
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Your app will now be able to render `.ntl` files. これで、アプリケーションは `.ntl` ファイルをレンダリングできるようになります。以下のコンテンツで `index.ntl` というファイルを `views` ディレクトリーに作成します。
-
-```pug
-#title#
-#message#
-```
-
-次に、アプリケーションで次のルートを作成します。
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-ホーム・ページに要求すると、`index.ntl` ファイルは HTML としてレンダリングされます。
\ No newline at end of file
diff --git a/ja/advanced/healthcheck-graceful-shutdown.md b/ja/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index efe4202588..0000000000
--- a/ja/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### 例
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/ja/advanced/security-updates.md b/ja/advanced/security-updates.md
deleted file mode 100644
index 0bf3801f87..0000000000
--- a/ja/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Express のセキュリティー更新
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# セキュリティー更新
-
-<div class="doc-box doc-notice" markdown="1">
-Node.js の脆弱性は Express に直接影響を与えます。そのため、[Node.js の脆弱性の監視を続けて](https://nodejs.org
-/en/blog/vulnerability/)、必ず、安定した最新バージョンの Node.js を使用してください。 Therefore, [keep a watch on Node.js vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest stable version of Node.js.
-</div>
-
-次のリストに、示されているバージョンの更新で修正された Express の脆弱性を列挙します。
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). 依存関係`forwarded`は、[脆弱性](https://npmjs.com/advisories/527)に対処するために更新されました。これは、`req.host`、`req.hostname`、`req.ip`、`req.ips`、`req.protocol`のAPIが使用されている場合、アプリケーションに影響を与える可能性があります。
-  - 依存関係`mime`は[脆弱性](https://npmjs.com/advisories/535)に対処するために更新されましたが、この問題はExpressには影響しません。
-  - 依存関係`send`が更新され、[Node.js 8.5.0の脆弱性](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/)に対する保護が提供されています。これは特定のNode.jsバージョン8.5.0でExpressを実行する場合にのみ影響します。 This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - 依存関係`debug`は[脆弱性](https://snyk.io/vuln/npm:debug:20170905)に対処するために更新されましたが、この問題はExpressには影響しません。
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). 依存関係`fresh`は、[脆弱性](https://npmjs.com/advisories/526)に対処するために更新されました。これは、次のAPIが使用されている場合、アプリケーションに影響します：`express.static`、`req.fresh`、`res.json`、`res.jsonp`、`res.send`、`res.sendfile`、`res.sendFile`、`res.sendStatus`
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). 依存関係`ms`は、[脆弱性](https://snyk.io/vuln/npm:ms:20170412)に対処するために更新されました。`express.static`、`res.sendfile`、および`res.sendFile`のAPIで、信頼できない文字列が入力され`maxAge`オプションに渡されると、アプリケーションに影響を与える可能性があります。
-- 4.15.2
-  - 依存関係`qs`は[脆弱性](https://snyk.io/vuln/npm:qs:20170213)に対処するために更新されましたが、この問題はExpressには影響しません。4.15.2へのアップデートは良い習慣ですが、この脆弱性に対処する必要はありません。 Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - `express.static`、`res.sendfile`、および `res.sendFile` のルート・パス開示の脆弱性を修正しました。
-- 4.10.7
-  - `express.static` のオープン・リダイレクトの脆弱性を修正しました ([アドバイザリー](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164))。
-- 4.8.8
-  - `express.static` のディレクトリー・トラバーサルの脆弱性を修正しました ([アドバイザリー](http://npmjs.com/advisories/32)、[CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394))。
-- 4.8.4
-  - Node.js 0.10 は、特定の状況で `fd` をリークして、`express.static` および `res.sendfile` に影響を及ぼす可能性があります。悪意ある要求によって `fd` がリークされ、最終的に `EMFILE` エラーが発生したり、サーバーが応答しなくなったりする可能性があります。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 4.8.0
-  - クエリストリングに極めて多数の索引が含まれる疎配列により、プロセスがメモリー不足になり、サーバーが異常終了する可能性があります。
-  - 過度にネストされたクエリストリング・オブジェクトにより、プロセスがサーバーをブロックして、サーバーが一時的に応答できなくなる可能性があります。
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x は保守されなくなりました**
-
-3.xの既知および未知のセキュリティ問題は、最終更新（2015年8月1日）以降は対処されていません。3.x系を使用することは安全であると見なされるべきではありません。 It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - `express.static`、`res.sendfile`、および `res.sendFile` のルート・パス開示の脆弱性を修正しました。
-- 3.19.0
-  - `express.static` のオープン・リダイレクトの脆弱性を修正しました ([アドバイザリー](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164))。
-- 3.16.10
-  - `express.static` のディレクトリー・トラバーサルの脆弱性を修正しました。
-- 3.16.6
-  - Node.js 0.10 は、特定の状況で `fd` をリークして、`express.static` および `res.sendfile` に影響を及ぼす可能性があります。悪意ある要求によって `fd` がリークされ、最終的に `EMFILE` エラーが発生したり、サーバーが応答しなくなったりする可能性があります。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 3.16.0
-  - クエリストリングに極めて多数の索引が含まれる疎な配列により、プロセスがメモリー不足になり、サーバーが異常終了する可能性があります。
-  - 過度にネストされたクエリストリング・オブジェクトにより、プロセスがサーバーをブロックして、サーバーが一時的に応答できなくなる可能性があります。
-- 3.3.0
-  - サポートされていないメソッドのオーバーライドの 404 応答は、クロスサイト・スクリプティングの攻撃を受ける可能性がありました。
\ No newline at end of file
diff --git a/ja/api.md b/ja/api.md
deleted file mode 100644
index 204151e989..0000000000
--- a/ja/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API リファレンス
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/ja/changelog/index.md b/ja/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/ja/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/ja/guide/behind-proxies.md b/ja/guide/behind-proxies.md
deleted file mode 100644
index dbedb2ed79..0000000000
--- a/ja/guide/behind-proxies.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-layout: page
-title: プロキシーの背後の Express
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# プロキシーの背後の Express
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-The application setting `trust proxy` may be set to one of the values listed in the following table.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>型</th><th>値</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Boolean</td>
-<td markdown="1">`true` の場合、クライアントの IP アドレスは、`X-Forwarded-*` ヘッダーの左端の項目として理解されます。
-
-`false` の場合、アプリケーションはインターネットに直接接続されているものとして理解され、クライアントの IP アドレスは `req.connection.remoteAddress` から導き出されます。これはデフォルトの設定値です。 This is the default setting.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`、`::1/128`
-- linklocal - `169.254.0.0/16`、`fe80::/10`
-- uniquelocal - `10.0.0.0/8`、`172.16.0.0/12`、`192.168.0.0/16`、`fc00::/7`
-
-以下のどの方法でも IP アドレスを設定できます。
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-IP アドレスまたはサブネットは、指定されると、アドレス決定プロセスから除外されます。アプリケーション・サーバーに最も近い信頼できない IP アドレスがクライアントの IP アドレスに決定されます。 This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>数字</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-`trust proxy`を有効にすると、次の3つの重要な変更が起こります。
-
-<ul>
-  <li markdown="1">[req.hostname](/{{ page.lang }}/api.html#req.hostname) の値は、クライアントまたはプロキシーが設定できる `X-Forwarded-Host` ヘッダーに設定された値から導き出されます。</li>
-  <li markdown="1">`X-Forwarded-Proto` は、`https` と `http` のどちらであるか、または無効な名前であるかをアプリケーションに通知するためにリバース・プロキシーによって設定できます。この値は、[req.protocol](/{{ page.lang }}/api.html#req.protocol) に反映されます。 This value is reflected by [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">[req.ip](/{{ page.lang }}/api.html#req.ip) および [req.ips](/{{ page.lang }}/api.html#req.ips) の値は、`X-Forwarded-For` のアドレス・リストから取り込まれます。</li>
-</ul>
-
-`trust proxy` 設定は、[proxy-addr](https://www.npmjs.com/package/proxy-addr) パッケージを使用して実装されます。詳細については、資料を参照してください。 For more information, see its documentation.
diff --git a/ja/guide/database-integration.md b/ja/guide/database-integration.md
deleted file mode 100644
index 336e9ba204..0000000000
--- a/ja/guide/database-integration.md
+++ /dev/null
@@ -1,497 +0,0 @@
----
-layout: page
-title: Express でのデータベースの統合
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# データベースの統合
-
-Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongodb)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgresql)
-- [Redis](#redis)
-- [SQL Server](#sql-server)
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-These database drivers are among many that are available. For other options,
-search on the [npm](https://www.npmjs.com/) site.
-</div>
-
-## Cassandra
-
-**モジュール**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-
-### **インストール**
-
-```bash
-$ npm install cassandra-driver
-```
-
-### 例
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### **インストール**
-
-```bash
-$ npm install couchbase
-```
-
-### 例
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**モジュール**: [nano](https://github.com/dscape/nano)
-
-### **インストール**
-
-```bash
-$ npm install nano
-```
-
-### 例
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**モジュール**: [levelup](https://github.com/rvagg/node-levelup)
-
-### **インストール**
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### 例
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**モジュール**: [mysql](https://github.com/felixge/node-mysql/)
-
-### **インストール**
-
-```bash
-$ npm install mysql
-```
-
-### 例
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**モジュール**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-
-### **インストール**
-
-```bash
-$ npm install mongodb
-```
-
-### 例 (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### 例 (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-MongoDB 用のオブジェクト・モデル・ドライバーが必要な場合は、[Mongoose](https://github.com/LearnBoost/mongoose) を参照してください。
-
-## Neo4j
-
-データベースを Express アプリケーションに接続できるようにするには、単にデータベースに適切な Node.js ドライバーをアプリケーションにロードするだけですみます。本書では、データベース・システム用の最も一般的な Node.js モジュールを Express アプリケーションに追加して使用する方法について簡単に説明します。
-
-### **インストール**
-
-```bash
-$ npm install neo4j-driver
-```
-
-### 例
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**モジュール**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### **インストール**
-
-NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### 例
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**モジュール**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-
-### **インストール**
-
-```bash
-$ npm install pg-promise
-```
-
-### 例
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**モジュール**: [redis](https://github.com/mranney/node_redis)
-
-### **インストール**
-
-```bash
-$ npm install redis
-```
-
-### 例
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**モジュール**: [tedious](https://github.com/tediousjs/tedious)
-
-### **インストール**
-
-```bash
-$ npm install tedious
-```
-
-### 例
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**モジュール**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-
-### **インストール**
-
-```bash
-$ npm install sqlite3
-```
-
-### 例
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**モジュール**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-
-### **インストール**
-
-```bash
-$ npm install elasticsearch
-```
-
-### 例
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/ja/guide/debugging.md b/ja/guide/debugging.md
deleted file mode 100644
index df0da33bba..0000000000
--- a/ja/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: Express のデバッグ
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Express のデバッグ
-
-Express で使用されているすべての内部ログを表示するには、アプリケーションの起動時に `DEBUG` 環境変数を `express:*` に設定します。
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-Windows では、対応するコマンドを使用します。
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-[express ジェネレーター](/{{ page.lang }}/starter/generator.html) で生成されるデフォルトのアプリケーションでこのコマンドを実行すると、以下の出力が表示されます。
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-その後、アプリケーションに対して要求が出されると、Express コードで指定された次のログが表示されます。
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-ルーター実装からのログのみを表示するには、`DEBUG` の値を `express:router` に設定します。同様に、アプリケーション実装からのログのみを表示するには、`DEBUG` を `express:application` に設定します。その他についても同様に設定します。 Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
-
-## `express` によって生成されるアプリケーション
-
-`express` コマンドによって生成されるアプリケーションも `debug` モジュールを使用します。そのデバッグ名前空間はアプリケーションの名前に設定されます。
-
-例えば、`$ express sample-app` を使用してアプリケーションを生成する場合、次のコマンドを使用してデバッグ・ステートメントを有効にすることができます。
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-名前のコンマ区切りリストを割り当てることで、複数のデバッグ名前空間を指定できます。
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/ja/guide/error-handling.md b/ja/guide/error-handling.md
deleted file mode 100644
index 17e4949ad6..0000000000
--- a/ja/guide/error-handling.md
+++ /dev/null
@@ -1,267 +0,0 @@
----
-layout: page
-title: Express でのエラー処理
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# エラー処理
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## エラーのキャッチ
-
-Expressがルート・ハンドラとミドルウェアの実行中に発生するすべてのエラーを確実にキャッチすることが重要です。
-
-ルート・ハンドラとミドルウェア内の同期コードで発生するエラーは、余分な作業を必要としません。同期コードがエラーをスローすると、Expressはそれをキャッチして処理します。 例えば： If synchronous code throws an error, then Express will
-catch and process it. For example:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-ルート・ハンドラとミドルウェアによって呼び出された非同期関数から返されたエラーについては、それらを`next()`関数に渡す必要があります。ここでExpressはそれらをキャッチして処理します。例えば：  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Starting with Express 5, route handlers and middleware that return a Promise
-will call `next(value)` automatically when they reject or throw an error.
-For example:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-`next()` 関数に (ストリング `'route'` を除く) 何らかを渡すと、Express は、現在のリクエストでエラーが発生したと想定して、エラーが発生していない残りのすべての処理のルーティングとミドルウェア関数をスキップします。そのエラーを何らかの方法で渡す場合は、次のセクションで説明するようにエラー処理ルートを作成する必要があります。
-
-シーケンス内のコールバックにデータがなく、エラーのみが発生する場合は、次のようにこのコードを単純化できます。
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-上記の例では`fs.writeFile`のコールバックとして`next`が提供されています。これはエラーの有無にかかわらず呼び出されます。エラーがなければ、2番目のハンドラが実行されます。それ以外の場合、Expressはエラーをキャッチして処理します。 If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-ルート・ハンドラまたはミドルウェアによって呼び出された非同期コードで発生したエラーをキャッチして、Expressに渡して処理する必要があります。例えば： For example:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-上記の例では、`try ... catch`ブロックを使用して非同期コードのエラーを捕捉してExpressに渡しています。`try ... catch`ブロックが省略された場合、Expressは同期ハンドラ・コードの一部ではないため、エラーをキャッチしません。
-
-Promiseを使って`try..catch`ブロックのオーバーヘッドを避けるか、Promiseを返す関数を使うとき。例えば：  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Promiseは自動的に同期エラーと拒否されたPromiseをキャッチするので、catchハンドラに最初の引数としてエラーが与えられ、最終的なcatchハンドラとして`next`を指定するだけで、Expressはエラーをキャッチします。
-
-また、非同期コードを単純なものに減らすことで、同期エラーのキャッチに依存する一連のハンドラを使用することもできます。例えば： For example:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. 上の例は`readFile`呼び出しからの簡単なステートメントをいくつか持っています。`readFile`でエラーが発生した場合、エラーをExpressに渡します。そうでなければ、チェーン内の次のハンドラで同期エラー処理の世界に素早く戻ります。次に、上記の例ではデータを処理しようとしています。これが失敗すると、同期エラーハンドラはそれをキャッチします。 この処理を`readFile`コールバックの中で行った場合、アプリケーションは終了し、Expressのエラーハンドラは実行されません。 Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-どちらの方法を使用しても、Expressのエラーハンドラを呼び出す場合や、アプリケーションを存続させる場合は、Expressがエラーを受け取るようにする必要があります。
-
-## デフォルトのエラー処理
-
-Expressには、アプリケーションで発生する可能性のあるエラーを処理するビルトインエラーハンドラが付属しています。 このデフォルトのエラー処理ミドルウェア関数は、ミドルウェア関数スタックの最後に追加されます。 This default error-handling middleware function is added at the end of the middleware function stack.
-
-`next()`にエラーを渡し、カスタムエラーハンドラでそれを処理しない場合、それは組み込みのエラーハンドラによって処理されます。エラーはスタックトレースを使用してクライアントに書き込まれます。スタックトレースは本番環境には含まれていません。 The stack trace is not included
-in the production environment.
-
-<div class="doc-box doc-info" markdown="1">プロダクションモードでアプリケーションを実行するには、環境変数`NODE_ENV`を` production`に設定します。</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-レスポンスの記述を開始した後でエラーを伴って`next()`を呼び出すと（例えば、クライアントへの応答をストリーミング中にエラーが発生した場合）、Expressのデフォルトエラーハンドラは接続を閉じてリクエストを失敗します。
-
-したがって、カスタムエラーハンドラを追加するときは、ヘッダーがすでにクライアントに送信されているときに、デフォルトのExpressエラーハンドラに委任する必要があります。
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-カスタムエラー処理ミドルウェアが存在していても、コード内でエラーが2回以上発生したときに`next()`を呼び出すと、デフォルトのエラーハンドラがトリガされることに注意してください。
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## エラー処理を記述する
-
-エラー処理ミドルウェア関数は、その他のミドルウェア関数と同じ方法で定義しますが、エラー処理関数の引数が3つではなく、4つ `(err、req、res、next)` であることが例外です。次に例を示します。 For example:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-エラー処理ミドルウェアは、その他の `app.use()` およびルート呼び出しの後で最後に定義します。次に例を示します。
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-ミドルウェア関数の中からの応答は、HTML エラー・ページ、単純なメッセージ、または JSON ストリングなど、任意の形式にすることができます。
-
-組織的な (および高水準フレームワークの) 目的で、通常のミドルウェア関数と同じように、複数のエラー処理のミドルウェア関数を定義できます。例えば、`XHR` を使用する要求と、使用しない要求のためのエラー・ハンドラーを定義するには、以下のコマンドを使用します。 For example, to define an error-handler
-for requests made by using `XHR` and those without:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-この例では、汎用の `logErrors` が要求とエラーの情報を `stderr` に書き込む可能性があります。次に例を示します。
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-また、この例では、`clientErrorHandler` は次のように定義されます。この場合、エラーは明示的に次のエラーに渡されます。
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-「catch-all」`errorHandler` 関数は、次のように実装されます。
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-複数のコールバック関数を使用するルート・ハンドラーがある場合、`route` パラメーターを使用して、次のルート・ハンドラーまでスキップできます。次に例を示します。 For example:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-この例では、`getPaidContent` ハンドラーはスキップされますが、`/a_route_behind_paywall` の `app` にある残りのハンドラーはすべて引き続き実行されます。
-
-<div class="doc-box doc-info" markdown="1">
-Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.  `next()` および `next(err)` の呼び出しは、現在のハンドラーが完了したことと、その状態を示します。`next(err)` は、上記のようにエラーを処理するようにセットアップされたハンドラーを除き、チェーン内の残りのハンドラーをすべてスキップします。
-</div>
diff --git a/ja/guide/migrating-4.md b/ja/guide/migrating-4.md
deleted file mode 100644
index 7caa5dc571..0000000000
--- a/ja/guide/migrating-4.md
+++ /dev/null
@@ -1,573 +0,0 @@
----
-layout: page
-title: Express 4 への移行
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Express 4 への移行
-
-<h2 id="overview">概説</h2>
-
-Express 4 では、Express 3 とは互換性の _ない_ 変更が行われています。つまり、依存関係にある Express のバージョンを更新すると、既存の Express 3 アプリケーションは機能しません。 That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
-
-この記事では以下の内容を扱います。
-
-<ul class="doclist">
-  <li><a href="#changes">Express 4 における変更点</a></li>
-  <li>Express 3 アプリケーションを Express 4 に移行する<a href="#example-migration">例</a></li>
-  <li><a href="#app-gen">Express 4 アプリケーション・ジェネレーターへのアップグレード</a></li>
-</ul>
-
-<h2 id="changes">Express 4 における変更点</h2>
-
-Express 4 では、いくつかの大きな変更が行われています。
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">ルーティング・システムの変更。</a></li>
-  <li><a href="#other-changes">その他の各種変更。</a></li>
-</ul>
-
-以下も参照してください。
-
-- [4.x の新機能](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [3.x から 4.x への移行](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Express コアおよびミドルウェア・システムの変更
-</h3>
-
-Express 4 は、Connect に依存しなくなり、`express.static` 関数を除くすべての標準装備ミドルウェアをコアから削除しました。つまり、Express は独立したルーティングおよびミドルウェアの Web フレームワークになり、Express のバージョン管理とリリースはミドルウェア更新の影響を受けません。 This means that
-Express is now an independent routing and middleware web framework, and
-Express versioning and releases are not affected by middleware updates.
-
-標準装備ミドルウェアがないため、アプリケーションの実行に必要なすべてのミドルウェアを明示的に追加する必要があります。そのためには、単に以下のステップを実行してください。 Simply follow these steps:
-
-1. モジュールをインストールします。`npm install --save <module-name>`
-2. アプリケーションでモジュールを要求します。`require('module-name')`
-3. モジュールの資料に従ってモジュールを使用します。`app.use( ... )`
-
-次の表に、Express 3 のミドルウェアと、それぞれに対応する Express 4 のミドルウェアをリストします。
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Express 4 のミドルウェアの完全なリストは、[ここ](https://github.com/senchalabs/connect#middleware)を参照してください。
-
-ほとんどの場合、旧バージョン 3 のミドルウェアを単に Express 4 のミドルウェアに置き換えるだけですみます。詳細については、GitHub でモジュールの資料を参照してください。 For details, see the module documentation in
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> がパラメーターを受け入れます</h4>
-
-バージョン 4 では、変数パラメーターを使用して、ミドルウェア関数がロードされるパスを定義し、ルート・ハンドラーからパラメーターの値を読み取ることができます。
-次に例を示します。
-For example:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-ルーティング・システム
-</h3>
-
-アプリケーションがルーティング・ミドルウェアを暗黙的にロードするようになったため、`router` ミドルウェアに関してミドルウェアがロードされる順序を考慮する必要がなくなりました。
-
-ルートの定義方法は変わりませんが、ルーティング・システムには、ルートの編成に役立つ 2 つの新機能があります。
-
-{: .doclist }
-
-- 新しいメソッド `app.route()` は、ルート・パスのチェーン可能なルート・ハンドラーを作成します。
-- 新しいクラス `express.Router` は、モジュール式のマウント可能なルート・ハンドラーを作成します。
-
-<h4 id="app-route"><code>app.route()</code> メソッド</h4>
-
-新しい `app.route()` メソッドを使用すると、ルート・パスのチェーン可能なルート・ハンドラーを作成できます。パスは単一の場所で指定されるため、モジュール式のルートを作成すると、便利であるほか、冗長性とタイプミスを減らすことができます。ルートについて詳しくは、[`Router()` 資料](/{{ page.lang }}/4x/api.html#router)を参照してください。 Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
-information about routes, see [`Router()` documentation](/{{ page.lang }}/4x/api.html#router).
-
-次に、`app.route()` 関数を使用して定義された、チェーニングされたルート・ハンドラーの例を示します。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> クラス</h4>
-
-ルートの編成に役立つもう 1 つの機能は、新しいクラス `express.Router` です。これを使用すると、モジュール式のマウント可能なルート・ハンドラーを作成できます。`Router` インスタンスは、完全なミドルウェアおよびルーティング・システムです。そのため、よく「ミニアプリケーション」と呼ばれます。 A `Router` instance is a complete middleware and
-routing system; for this reason it is often referred to as a "mini-app".
-
-次の例では、ルーターをモジュールとして作成し、その中にミドルウェアをロードして、いくつかのルートを定義し、それをメインアプリケーションのパスにマウントします。
-
-例えば、アプリケーション・ディレクトリーに次の内容で `birds.js` というルーター・ファイルを作成します。
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-次に、ルーター・モジュールをアプリケーションにロードします。
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-これで、アプリケーションは、`/birds` および `/birds/about` のパスに対する要求を処理できるようになり、ルートに固有の `timeLog` ミドルウェアを呼び出します。
-
-<h3 id="other-changes">
-その他の変更点
-</h3>
-
-次の表に、Express 4 におけるその他の小規模ながらも重要な変更点をリストします。
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>オブジェクト</th>
-<th>説明</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 には、Node.js 0.10.x 以降が必要です。Node.js 0.8.x に対するサポートは除去されました。</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-
-`http` モジュールは、このモジュールを直接処理する必要がある場合を除き、不要になりました (socket.io/SPDY/HTTPS)。アプリケーションは、`app.listen()` 関数を使用して開始できます。
- The app can be started by using the
-`app.listen()` function.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-The `app.configure()` function has been removed.  
-`app.configure()` 関数は削除されました。環境を検出して、アプリケーションを適宜に構成するには、`process.env.NODE_ENV` 関数または `app.get('env')` 関数を使用してください。
-
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-`json spaces` アプリケーション・プロパティーは、Express 4 ではデフォルトで無効になっています。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-`req.accepts()`、`req.acceptsEncodings()`、`req.acceptsCharsets()`、および `req.acceptsLanguages()` を使用してください。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-相対 URL を解決しなくなりました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-以前は配列でしたが、現在ではオブジェクトになりました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-以前は関数でしたが、現在ではオブジェクトになりました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-`res.headersSent` に変更されました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-今後は `app.mountpath` として使用できます。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-削除されました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-削除されました。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Functionality is now limited to setting the basic cookie value. 
-機能が基本的な Cookie 値の設定に限定されるようになりました。機能を追加するには、`res.cookie()` を使用してください。
-
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">移行の例</h2>
-
-次に、Express 3 アプリケーションを Express 4 に移行する例を示します。
-使用しているファイルは、`app.js` および `package.json` です。
-The files of interest are `app.js` and `package.json`.
-
-<h3 id="">
-バージョン 3 アプリケーション
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-次の `app.js` ファイルを使用する Express v.3 アプリケーションがあるとします。
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-付随するバージョン 3 の `package.json` ファイルの内容は次のようになります。
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-プロセス
-</h3>
-
-移行プロセスを開始するには、次のコマンドを使用して、Express 4 アプリケーションに必要なミドルウェアをインストールし、Express と Pug をそれぞれの最新バージョンに更新します。
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-`app.js` に以下の変更を加えます。
-
-1. 標準装備の Express ミドルウェア関数 `express.favicon`、`express.logger`、`express.methodOverride`、`express.session`、`express.bodyParser`、および `express.errorHandler` は `express` オブジェクトで使用できなくなりました。代わりの関数を手動でインストールして、アプリケーションにロードする必要があります。 You must install their alternatives
-   manually and load them in the app.
-
-2. You no longer need to load the `app.router` function.
-   `app.router` 関数をロードする必要がなくなりました。この関数は有効な Express 4 アプリケーション・オブジェクトではないため、`app.use(app.router);` コードを削除してください。
-
-3. ミドルウェア関数が正しい順序でロードされていることを確認してください。つまり、アプリケーション・ルートをロードした後で `errorHandler` をロードしてください。
-
-<h3 id="">バージョン 4 アプリケーション</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-上記の `npm` コマンドを実行すると、`package.json` が次のように更新されます。
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Then, remove invalid code, load the required middleware, and make other
-changes as necessary. The `app.js` file will look like this:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">`http` モジュール (socket.io/SPDY/HTTPS) を直接処理する必要がある場合を除き、このモジュールをロードする必要はありません。次のようにして、アプリケーションを簡単に開始できます。
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">アプリケーションの実行</h3>
-
-これで移行プロセスは完了して、アプリケーションは Express 4 アプリケーションになりました。確認するには、次のコマンドを使用してアプリケーションを開始します。 To confirm, start the app by using the following command:
-
-```bash
-$ node .
-```
-
-[http://localhost:3000](http://localhost:3000) をロードして、Express 4 によってレンダリングされるホーム・ページを確認します。
-
-<h2 id="app-gen">Express 4 アプリケーション・ジェネレーターへのアップグレード</h2>
-
-Express アプリケーションを生成するためのコマンド・ライン・ツールは引き続き `express` ですが、新規バージョンにアップグレードするには、Express 3 アプリケーション・ジェネレーターをアンインストールしてから、新しい `express-generator` をインストールする必要があります。
-
-<h3 id="">インストール</h3>
-
-システムに Express 3 アプリケーション・ジェネレーターがインストールされている場合は、次のようにしてアンインストールする必要があります。
-
-```bash
-$ npm uninstall -g express
-```
-
-ファイルおよびディレクトリーの特権が構成されている方法によっては、このコマンドを `sudo` で実行することが必要になる場合があります。
-
-次に、新しいジェネレーターをインストールします。
-
-```bash
-$ npm install -g express-generator
-```
-
-ファイルおよびディレクトリーの特権が構成されている方法によっては、このコマンドを `sudo` で実行することが必要になる場合があります。
-
-これで、システム上の `express` コマンドは Express 4 ジェネレーターに更新されました。
-
-<h3 id="">アプリケーション・ジェネレーターの変更</h3>
-
-コマンドのオプションと使用法の大部分は以前と同じですが、以下の例外があります。
-
-{: .doclist }
-
-- `--sessions` オプションを削除しました。
-- `--jshtml` オプションを削除しました。
-- [Hogan.js](http://twitter.github.io/hogan.js/) をサポートするために `--hogan` オプションを追加しました。
-
-<h3 id="">例</h3>
-
-次のコマンドを実行して、Express 4 アプリケーションを作成します。
-
-```bash
-$ express app4
-```
-
-`app4/app.js` ファイルの内容を見ると、アプリケーションに必要な (`express.static` を除く) すべてのミドルウェア関数が独立したモジュールとしてロードされており、`router` ミドルウェアがアプリケーションに明示的にロードされなくなったことが分かります。
-
-また、`app.js` ファイルが Node.js モジュールになったことも分かります。対照的に以前はジェネレーターによって生成されるスタンドアロン・モジュールでした。
-
-依存関係をインストールした後、次のコマンドを使用してアプリケーションを開始します。
-
-```bash
-$ npm start
-```
-
-`package.json` ファイルで npm start スクリプトを見ると、アプリケーションを開始する実際のコマンドは `node ./bin/www` であることが分かります。これは、Express 3 では `node app.js` でした。
-
-Express 4 ジェネレーターによって生成される `app.js` ファイルが Node.js モジュールになったため、(コードを変更しない限り) アプリケーションとして単独では開始できなくなりました。モジュールを Node.js ファイルにロードして、Node.js ファイルから開始する必要があります。この場合、Node.js ファイルは `./bin/www` です。 The module must be loaded in a Node.js file
-and started via the Node.js file. The Node.js file is `./bin/www`
-in this case.
-
-Express アプリケーションの作成またはアプリケーションの開始のために、`bin` ディレクトリーも、拡張子のない `www` ファイルも必須ではありません。これらは単にジェネレーターが推奨するものであるため、ニーズに合わせて自由に変更してください。 They are
-just suggestions made by the generator, so feel free to modify them to suit your
-needs.
-
-`www` ディレクトリーを削除して、処理を「Express 3 の方法」で実行するには、`app.js` ファイルの最後にある `module.exports = app;` という行を削除して、その場所に以下のコードを貼り付けます。
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-次のコードを使用して `debug` モジュールを `app.js` ファイルの先頭にロードしたことを確認します。
-
-```js
-var debug = require('debug')('app4')
-```
-
-次に、`package.json` ファイル内の `"start": "node ./bin/www"` を `"start": "node app.js"` に変更します。
-
-You have now moved the functionality of `./bin/www` back to
-`app.js`. これで、`./bin/www` の機能を `app.js` に戻しました。この変更は推奨されるものではありませんが、この演習により、`./bin/www` ファイルの仕組みと、`app.js` ファイルが単独で開始されなくなった理由を理解できます。
diff --git a/ja/guide/migrating-5.md b/ja/guide/migrating-5.md
deleted file mode 100644
index 44f494b587..0000000000
--- a/ja/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: Express 5 への移行
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Express 5 への移行
-
-<h2 id="overview">概説</h2>
-
-Express 5 は Express 4 とあまり変わりません。API の変更は、3.0 から 4.0 への変更ほど大きいものではありません。基本的な API は同じままですが、それでも互換性のない変更が行われています。つまり、Express 5 を使用するように既存の Express 4 を更新すると、機能しなくなる可能性があります。 Therefore, an application built with Express 4 might not work if you update it to use Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-その後、自動テストを実行して、どの機能が失敗するかを確認し、下記の更新に従って問題を修正することができます。テストの失敗に対応した後、アプリケーションを実行して、どのようなエラーが発生するかを確認します。サポートされていないメソッドまたはプロパティーをアプリケーションが使用している場合は、すぐに判明します。 After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Express 5 における変更点</h2>
-
-**削除されたメソッドとプロパティー**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">メソッド名の複数化</a></li>
-  <li><a href="#leading">app.param(name, fn) の name 引数の先頭コロン</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**改善**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**変更**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## 削除されたメソッドとプロパティー
-
-If you use any of these methods or properties in your app, it will crash. アプリケーションで以下のいずれかのメソッドまたはプロパティーを使用すると、異常終了します。そのため、バージョン 5 に更新した後で、アプリケーションを変更する必要があります。
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 は、`app.del()` 関数をサポートしなくなりました。この関数を使用すると、エラーがスローされます。HTTP DELETE ルートを登録するには、代わりに `app.delete()` 関数を使用してください。 If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
-
-最初は `del` が `delete` の代わりに使用されていました。`delete` は、JavaScript で予約されているキーワードであるためです。しかし、ECMAScript 6 以降では、`delete` およびその他の予約済みキーワードを正式にプロパティー名として使用できます。ここで、`app.del` 関数の非推奨につながった議論を読むことができます。 However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-`app.param(fn)` シグニチャーは、`app.param(name, fn)` 関数の動作を変更するために使用されていました。v4.11.0 以降では非推奨になったため、Express 5 は完全にサポートしなくなりました。 It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="plural">メソッド名の複数化</h3>
-
-The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
-
-`req.acceptsLanguage()` は `req.acceptsLanguages()` に置き換えられます。
-
-`req.acceptsCharset()` は `req.acceptsCharsets()` に置き換えられます。
-
-`req.acceptsEncoding()` は `req.acceptsEncodings()` に置き換えられます。
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">app.param(name, fn) の name の先頭コロン (:)</h3>
-
-`app.param(name, fn)` 関数の name の先頭コロン文字 (:) は、Express 3 の残余物であり、Express 4 では後方互換性のためにサポートされていましたが、非推奨の通知が出されてました。Express 5 では、サイレントに無視して、先頭にコロンを付けない name パラメーターを使用します。 Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
-
-[app.param](/{{ page.lang }}/4x/api.html#app.param) に関する Express 4 の資料では、先頭のコロンについて言及していないため、この資料に従う場合には、コードに影響は及ばないはずです。
-
-<h3 id="req.param">req.param(name)</h3>
-
-This potentially confusing and dangerous method of retrieving form data has been removed. この混乱を招く可能性がある危険なメソッドは、フォーム・データを取得するためのものでしたが、削除されました。今後は、実行依頼されたパラメーター名を `req.params`、`req.body`、または `req.query` オブジェクトで具体的に見つける必要があります。
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 は、シグニチャー `res.json(obj, status)` をサポートしなくなりました。代わりに、状況を設定してから、`res.status(status).json(obj)` のように `res.json()` メソッドにチェーニングします。 Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 は、シグニチャー `res.jsonp(obj, status)` をサポートしなくなりました。代わりに、状況を設定してから、`res.status(status).jsonp(obj)` のように `res.jsonp()` メソッドにチェーニングします。 Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 は、シグニチャー `res.send(obj, status)` をサポートしなくなりました。代わりに、状況を設定してから、`res.status(status).send(obj)` のように `res.send()` メソッドにチェーニングします。 Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
-If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-`res.sendfile()` 関数は、Express 5 ではキャメルケース版の `res.sendFile()` に置き換えられます。
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## 変更
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. For example:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-For example:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-`app.router` オブジェクトは、Express 4 で削除されましたが、Express 5 で復帰しました。アプリケーションが明示的にロードする必要があった Express 3 とは異なり、新しいバージョンでは、このオブジェクトは基本の Express ルーターの単なる参照です。 In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-Express 4 では、`req.host` 関数は、ポート番号が存在する場合に、ポート番号を誤って削除していました。Express 5 では、ポート番号は維持されます。 In Express 5, the port number is maintained.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## 改善
-
-<h3 id="res.render">res.render()</h3>
-
-このメソッドは、すべてのビュー・エンジンに非同期動作を適用するようになり、同期実装を使用して推奨インターフェースに違反していたビュー・エンジンに起因するバグを回避します。
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/ja/guide/overriding-express-api.md b/ja/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/ja/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/ja/guide/routing.md b/ja/guide/routing.md
deleted file mode 100644
index 1b62a18dfd..0000000000
--- a/ja/guide/routing.md
+++ /dev/null
@@ -1,413 +0,0 @@
----
-layout: page
-title: Express でのルーティング
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# ルーティング
-
-_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
-For an introduction to routing, see [Basic routing](/{{ page.lang }}/starter/basic-routing.html).
-
-ルーティングはHTTPメソッドに対応するExpressの`app`オブジェクトのメソッドを使用して定義します。たとえば、GETリクエストを処理する`app.get()`やPOSTリクエストを処理する`app.post`があります。
-完全なリストについては、[app.METHOD](/{{ page.lang }}/4x/api.html#app.METHOD)を参照してください。
-また、すべてのHTTPメソッドを制御するために[app.all()](/{{ page.lang }}/4x/api.html#app.all)を、ミドルウェアを指定するために[app.use()](/{{ page.lang }}/4x/api.html#app.use)をコールバック関数として使用することができます(詳細については、[Using middleware](/{{ page.lang }}/guide/using-middleware.html)を参照してください)。 For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-これらのルーティングメソッドは、アプリケーションが指定されたルート（エンドポイント）とHTTPメソッドへのリクエストを受け取ったときに呼び出されるコールバック関数（ハンドラ関数とも呼ばれます）を指定します。 つまり、アプリケーションは指定されたルートとメソッドに一致するリクエストをリッスンし、一致を検出すると指定されたコールバック関数を呼び出します。 In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-実際、ルーティングメソッドは複数のコールバック関数を引数として持つことができます。
-複数のコールバック関数では、コールバック関数に引数として`next`を指定し、次のコールバックに制御を渡す関数の本体内で`next()`を呼び出すことが重要です。
-
-次のコードは、極めて基本的なルートの例です。
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">route メソッド</h2>
-
-route メソッドは、いずれかの HTTP メソッドから派生され、`express` クラスのインスタンスに付加されます。
-
-次のコードは、アプリケーションのルートへの GET メソッドと POST メソッドに定義されたルートの例です。
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Expressは、すべてのHTTPリクエストメソッドに対応するメソッド（`get`、`post`など）をサポートしています。
-完全なリストについては、[app.METHOD](/{{ page.lang }}/4x/api.html#app.METHOD)を参照して下さい。
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-_すべての_ HTTPリクエストメソッドのパスにミドルウェア関数をロードするために使用される特別なルーティングメソッド、`app.all()`があります。 たとえば、GET、POST、PUT、DELETE、または[httpモジュール](https://nodejs.org/api/http.html#http_http_methods)でサポートされているその他のHTTPリクエストメソッドを使用するかどうかにかかわらず、"/secret"ルートへのリクエストに対して次のハンドラが実行されます。 For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">ルート・パス</h2>
-
-ルート・パスは、リクエストメソッドとの組み合わせにより、リクエストを実行できるエンドポイントを定義します。ルート・パスは、ストリング、ストリング・パターン、または正規表現にすることができます。 Route paths can be strings, string patterns, or regular expressions.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### 次に、ストリングに基づくルート・パスの例を示します。
-
-このルート・パスは、リクエストをルートのルート `/` にマッチングします。
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-このルート・パスは、リクエストを `/about` にマッチングします。
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-このルート・パスは、リクエストを `/random.text` にマッチングします。
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### 次に、ストリング・パターンに基づくルート・パスの例を示します。
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-このルート・パスは、`acd` および `abcd` をマッチングします。
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-このルート・パスは、`abcd`、`abbcd`、`abbbcd` などをマッチングします。
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-このルート・パスは、`abcd`、`abxcd`、`abRABDOMcd`、`ab123cd` などをマッチングします。
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-このルート・パスは、`/abe` および `/abcde` をマッチングします。
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### 次に、正規表現に基づくルート・パスの例を示します。
-
-このルート・パスは、ルート名に「a」が含まれるすべてのものをマッチングします。
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-このルート・パスは、`butterfly` および `dragonfly` をマッチングしますが、`butterflyman`、`dragonfly man` などはマッチングしません。
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">ルート・パラメータ</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. ルート・パラメータは、URL内の指定された値を取得するために使用されるURLセグメントのことを言います。捕捉された値は`req.params`オブジェクトの中で、パスに指定されたルート・パラメータの名前をそれぞれのキーとして設定されます。
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-ルート・パラメータを使用してルートを定義するには、以下に示すようにルートのパスにルート・パラメータを指定するだけです。
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-ルート・パラメータの名前は、「単語文字」([A-Za-z0-9_])で構成する必要があります。
-</div>
-
-ハイフン（`-`）とドット（`.`）は文字通りに解釈されるので、有用な目的のためにルート・パラメータとともに使用することができます。
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-ルート・パラメータで一致させることができる正確な文字列をより詳細に制御するために、括弧（`()`）内で正規表現を追加できます：
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">ルート・ハンドラー</h2>
-
-リクエストを処理するために、[ミドルウェア](/{{ page.lang }}/guide/using-middleware.html)のように動作する複数のコールバック関数を指定できます。唯一の例外は、これらのコールバックが `next('route')` を呼び出して、残りのルート・コールバックをバイパスすることです。このメカニズムを使用して、ルートに事前条件を適用し、現在のルートで続行する理由がない場合に後続のルートに制御を渡すことができます。 The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-次の例に示すように、ルート・ハンドラーの形式は、関数、関数の配列、または両方の組み合わせにすることができます。
-
-単一のコールバック関数で 1 つのルートを処理できます。次に例を示します。 For example:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-複数のコールバック関数で1つのルートを処理できます (必ず、`next` オブジェクトを指定してください)。次に例を示します。 For example:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-コールバック関数の配列で 1 つのルートを処理できます。次に例を示します。 For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-独立した関数と、関数の配列の組み合わせで1つのルートを処理できます。次に例を示します。 For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">レスポンスメソッド</h2>
-
-次の表に示すレスポンスオブジェクト (`res`) のメソッドは、レスポンスをクライアントに送信して、リクエストとレスポンスのサイクルを終了することができます。これらのメソッドのいずれもルート・ハンドラーから呼び出されない場合、クライアントリクエストはハングしたままになります。 If none of these methods are called from a route handler, the client request will be left hanging.
-
-| メソッド                                                                                                                                                                                                                      | 説明                                             |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | ファイルのダウンロードのプロンプトを出します。                        |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | レスポンスプロセスを終了します。                               |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | JSON レスポンスを送信します。                              |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | JSONP をサポートする JSON レスポンスを送信します。                |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | リクエストをリダイレクトします。                               |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | ビュー・テンプレートをレンダリングします。                          |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | さまざまなタイプのレスポンスを送信します。                          |
-| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile)                          | ファイルをオクテット・ストリームとして送信します。                      |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | レスポンスのステータスコードを設定して、そのストリング表現をレスポンス本文として送信します。 |
-
-<h2 id="app-route">app.route()</h2>
-
-You can create chainable route handlers for a route path by using `app.route()`.
-Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/{{ page.lang }}/5x/api.html#router).
-
-次に、`app.route()` を使用して定義された、チェーニングされたルート・ハンドラーの例を示します。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-モジュール式のマウント可能なルート・ハンドラーを作成するには、`express.Router` クラスを使用します。`Router` インスタンスは、完全なミドルウェアおよびルーティング・システムです。そのため、よく「ミニアプリケーション」と呼ばれます。 A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
-
-次の例では、ルーターをモジュールとして作成し、その中にミドルウェア関数をロードして、いくつかのルートを定義し、ルート・モジュールをメインアプリケーションのパスにマウントします。
-
-アプリケーション・ディレクトリーに次の内容で `birds.js` というルーター・ファイルを作成します。
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-次に、ルーター・モジュールをアプリケーションにロードします。
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-これで、アプリケーションは、`/birds` および `/birds/about` に対するリクエストを処理するほか、ルートに固有の `timeLog` ミドルウェア関数を呼び出すことができるようになります。
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/ja/guide/using-middleware.md b/ja/guide/using-middleware.md
deleted file mode 100644
index 7bfca3a572..0000000000
--- a/ja/guide/using-middleware.md
+++ /dev/null
@@ -1,278 +0,0 @@
----
-layout: page
-title: Express ミドルウェアの使用
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# ミドルウェアの使用
-
-Express は、それ自体では最小限の機能を備えたルーティングとミドルウェアの Web フレームワークです。Express アプリケーションは基本的に一連のミドルウェア関数呼び出しです。
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
-
-ミドルウェア関数は以下のタスクを実行できます。
-
-- 任意のコードを実行する。
-- リクエストオブジェクトとレスポンスオブジェクトを変更する。
-- リクエストレスポンスサイクルを終了する。
-- スタック内の次のミドルウェア関数を呼び出す。
-
-現在のミドルウェア関数がリクエストレスポンスサイクルを終了しない場合は、`next()` を呼び出して、次のミドルウェア関数に制御を渡す必要があります。そうしないと、リクエストはハングしたままになります。 Otherwise, the request will be left hanging.
-
-Express アプリケーションは、以下のタイプのミドルウェアを使用できます。
-
-- [アプリケーション・レベルのミドルウェア](#middleware.application)
-- [ルーター・レベルのミドルウェア](#middleware.router)
-- [エラー処理ミドルウェア](#middleware.error-handling)
-- [標準装備のミドルウェア](#middleware.built-in)
-- [サード・パーティー・ミドルウェア](#middleware.third-party)
-
-アプリケーション・レベルとルーター・レベルのミドルウェアは、オプションのマウント・パスを指定してロードできます。
-また、一連のミドルウェア関数を一緒にロードできます。こうすると、マウント・ポイントにミドルウェア・システムのサブスタックが作成されます。
-You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
-
-<h2 id='middleware.application'>アプリケーション・レベルのミドルウェア</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-This example shows a middleware function mounted on the `/user/:id` path. 次の例は、`/user/:id` パスにマウントされたミドルウェア関数を示しています。この関数は、`/user/:id` パスに対するすべてのタイプの HTTP リクエストで実行されます。
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Here is an example of loading a series of middleware functions at a mount point, with a mount path.
-It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
-
-次の例は、`/user/:id` パスへの GET リクエストを処理するミドルウェア・サブスタックを示しています。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-ルーター・ミドルウェア・スタックの残りのミドルウェア関数をスキップするには、`next('route')` を呼び出して、次のルートに制御を渡します。
-**注**: `next('route')` は、`app.METHOD()` 関数または `router.METHOD()` 関数を使用してロードされたミドルウェア関数でのみ機能します。
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-次の例は、`/user/:id` パスへの GET リクエストを処理するミドルウェア・サブスタックを示しています。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-次の例は、ルートとそのハンドラー関数 (ミドルウェア・システム) を示しています。この関数は、`/user/:id` パスへの GET リクエストを処理します。
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>ルーター・レベルのミドルウェア</h2>
-
-ルーター・レベルのミドルウェアは、`express.Router()` のインスタンスにバインドされる点を除き、アプリケーション・レベルのミドルウェアと同じように動作します。
-
-```js
-const router = express.Router()
-```
-
-`router.use()` 関数と `router.METHOD()` 関数を使用して、ルーター・レベルのミドルウェアをロードします。
-
-次のコードの例では、ルーター・レベルのミドルウェアを使用して、上記のアプリケーション・レベルのミドルウェアで示されているミドルウェア・システムを複製します。
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-ルータのミドルウェア機能の残りの部分をスキップするには、`next('router')`を呼び出してルータインスタンスから制御を戻します。
-
-次の例は、`/user/:id` パスへの GET リクエストを処理するミドルウェア・サブスタックを示しています。
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>エラー処理ミドルウェア</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors.
-</div>
-
-エラー処理ミドルウェア関数は、その他のミドルウェア関数と同じ方法で定義しますが、例外として、シグニチャーで3つではなく4つの引数 `(err、req、res、next)`) を明示的に指定します。
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-エラー処理ミドルウェアについて詳しくは、[エラー処理](/{{ page.lang }}/guide/error-handling.html)を参照してください。
-
-<h2 id='middleware.built-in'>Built-in middleware</h2>
-
-Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). バージョン 4.x 以降、Express は [Connect](https://github.com/senchalabs/connect) に依存しなくなりました。以前に Express に組み込まれていたすべてのミドルウェア関数は個別のモジュールになりました。[ミドルウェア関数のリスト](https://github.com/senchalabs/connect#middleware)を参照してください。
-
-Expressには、次のミドルウェア機能が組み込まれています。
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Third-party middleware</h2>
-
-Express アプリケーションに機能を追加するには、サード・パーティー・ミドルウェアを使用します。
-
-必要な機能を提供する Node.js モジュールをインストールして、アプリケーションにアプリケーション・レベルまたはルーター・レベルでロードします。
-
-次の例は、Cookie 解析ミドルウェア関数 `cookie-parser` のインストールおよびロードを示しています。
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Express で一般的に使用されているサード・パーティー・ミドルウェア関数の一部のリストについては、[サード・パーティー・ミドルウェア](../resources/middleware.html)を参照してください。
diff --git a/ja/guide/using-template-engines.md b/ja/guide/using-template-engines.md
deleted file mode 100644
index 8942cffe7c..0000000000
--- a/ja/guide/using-template-engines.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-layout: page
-title: Express でのテンプレート・エンジンの使用
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Express でのテンプレート・エンジンの使用
-
-A _template engine_ enables you to use static template files in your application. _テンプレートエンジン_ を使用すると、アプリケーションで静的なテンプレートファイルを使用できます。実行時に、テンプレートエンジンはテンプレートファイルの変数を実際の値に置き換え、テンプレートをクライアントに送信するHTMLファイルに変換します。このアプローチにより、HTMLページの設計が容易になります。
-This approach makes it easier to design an HTML page.
-
-Expressで動作する一般的なテンプレートエンジンには、[Pug](https://pugjs.org/api/getting-started.html)、[Mustache](https://www.npmjs.com/package/mustache)、[EJS](https://www.npmjs.com/package/ejs)があります。[Expressアプリケーションジェネレータ](/{{ page.lang }}/starter/generator.html)は[Jade](https://www.npmjs.com/package/jade)をデフォルトとして使用しますが、いくつかの他のものもサポートしています。
-
-テンプレートファイルをレンダリングするには、次の[アプリケーション設定プロパティ](/{{ page.lang }}/4x/api.html#app.set)を設定し、ジェネレータで作成されたデフォルトアプリの`app.js`にセットします。
-
-- `views`, the directory where the template files are located. `views`はテンプレートファイルが置かれているディレクトリ。例：`app.set('views', './views')`。これは、デフォルトではアプリケーションのルートディレクトリ内の`views`ディレクトリになります
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, the template engine to use. `view engine`は使用するテンプレートエンジン。たとえば、Pugテンプレートエンジンを使用するには、`app.set('view engine', 'pug')`を使用します
-
-次に、対応するテンプレートエンジンnpmパッケージをインストールします。たとえばPugをインストールするには：
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">Pug などの Express 対応テンプレート・エンジンは、`__express(filePath, options, callback)` という関数をエクスポートします。この関数は、テンプレート・コードをレンダリングするために `res.render()` 関数によって呼び出されます。
-一部のテンプレート・エンジンは、この規則に従いません。[Consolidate.js](https://www.npmjs.org/package/consolidate) ライブラリーは、すべての一般的な Node.js テンプレート・エンジンをマップすることで、この規則に従います。そのため、Express 内でシームレスに動作します。
-
-Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
-library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
-
-</div>
-
-ビュー・エンジンが設定された後は、アプリケーションでエンジンを指定したり、テンプレート・エンジンをロードしたりする必要はありません。(上記の例に対応した) 下記のように、Express がモジュールを内部的にロードします。
-
-```js
-app.set('view engine', 'pug')
-```
-
-以下の内容で `index.pug` という Pug テンプレート・ファイルを `views` ディレクトリーに作成します。
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Create a route to render the `index.pug` file. If the `view engine` property is not set,
-you must specify the extension of the `view` file. Otherwise, you can omit it.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-ホーム・ページに要求すると、`index.pug` ファイルは HTML としてレンダリングされます。
-
-注：view engine のキャッシュは、テンプレートの出力内容をキャッシュしません。基本となるテンプレート自体だけです。このビューは、キャッシュがオンの場合でも、すべてのリクエストで再レンダリングされます。 The view is still re-rendered with every request even when the cache is on.
diff --git a/ja/guide/writing-middleware.md b/ja/guide/writing-middleware.md
deleted file mode 100644
index 14e5b0e245..0000000000
--- a/ja/guide/writing-middleware.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-layout: page
-title: Express アプリケーションで使用するミドルウェアの作成
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Express アプリケーションで使用するミドルウェアの作成
-
-<h2>概説</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
-
-ミドルウェア関数は以下のタスクを実行できます。
-
-- 任意のコードを実行する。
-- リクエストオブジェクトとレスポンスオブジェクトを変更する。
-- リクエストレスポンスサイクルを終了する。
-- スタック内の次のミドルウェアを呼び出す。
-
-現在のミドルウェア関数がリクエストレスポンスサイクルを終了しない場合は、`next()` を呼び出して、次のミドルウェア関数に制御を渡す必要があります。そうしないと、リクエストはハングしたままになります。 Otherwise, the request will be left hanging.
-
-次の例は、ミドルウェア関数呼び出しの要素を示しています。
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">ミドルウェア関数が適用される HTTP メソッド。</div></tbody>
-
-<div class="callout" id="callout2"> ミドルウェア関数が適用されるパス (ルート)。</div>
-
-<div class="callout" id="callout3">ミドルウェア関数。</div>
-
-<div class="callout" id="callout4">ミドルウェア関数へのコールバック引数 (慣習的に「next」と呼ばれます)。</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>例</h2>
-
-Here is an example of a simple "Hello World" Express application.
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>ミドルウェア関数 myLogger</h3>
-Here is a simple example of a middleware function called "myLogger". This function just prints "LOGGED" when a request to the app passes through it. 次に、"myLogger"というミドルウェア関数の簡単な例を示します。この関数は、アプリケーションへのリクエストがそれを通過するときに、単に "LOGGED"を出力します。ミドルウェア関数は、`myLogger`という名前の変数に割り当てられます。
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Notice the call above to `next()`. Calling this function invokes the next middleware function in the app.
-The `next()` function is not a part of the Node.js or Express API, but is the third argument that is passed to the middleware function. The `next()` function could be named anything, but by convention it is always named "next".
-To avoid confusion, always use this convention.
-</div>
-
-To load the middleware function, call `app.use()`, specifying the middleware function.
-ミドルウェア関数をロードするには、ミドルウェア関数を指定して `app.use()` を呼び出します。
-例えば、次のコードは、ルート・パス (/) へのルートの前に `myLogger` ミドルウェア関数をロードします。
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-アプリケーションは、リクエストを受け取るたびに、端末にメッセージ「LOGGED」を出力します。
-
-ミドルウェアのロードの順序は重要です。最初にロードされたミドルウェア関数が常に最初に実行されます。
-
-`myLogger` がルート・パスの後にロードされた場合、リクエストが到達することはなく、アプリケーションは「LOGGED」を出力しません。ルート・パスのルート・ハンドラーがリクエストレスポンスサイクルを終了するためです。
-
-ミドルウェア関数 `myLogger` は、単にメッセージを出力してから、`next()` 関数を呼び出して、スタック内の次のミドルウェア関数へのリクエストに移ります。
-
-<h3>ミドルウェア関数 requestTime</h3>
-
-次に、「requestTime」というミドルウェア関数を作成し、`requestTime`というプロパティとしてリクエストオブジェクトに追加します。
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-The app now uses the `requestTime` middleware function. これで、アプリケーションが `requestTime` ミドルウェア関数を使用するようになります。また、ルート・パス・ルートのコールバック関数は、ミドルウェア関数が `req` (リクエストオブジェクト) に追加するプロパティーを使用します。
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-アプリケーションのルートにリクエストすると、アプリケーションは、リクエストのタイムスタンプをブラウザーに表示します。
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-リクエストオブジェクト、レスポンスオブジェクト、スタック内の次のミドルウェア関数、および Node.js API を利用できるため、ミドルウェア関数が持つ可能性は無限です。
-
-Express ミドルウェアについて詳しくは、[Express ミドルウェアの使用](/{{ page.lang }}/guide/using-middleware.html)を参照してください。
-
-<h2>設定可能なミドルウェア</h2>
-
-ミドルウェアを設定可能にする必要がある場合は、optionsオブジェクトまたはその他のパラメータを受け入れる関数をエクスポートし、入力パラメータに基づいてミドルウェアの実装を返します。
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-ミドルウェアは以下のように使用できるようになりました。
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-設定可能なミドルウェアの例については、[cookie-session](https://github.com/expressjs/cookie-session)および[compression](https://github.com/expressjs/compression)を参照してください。
diff --git a/ja/index.md b/ja/index.md
deleted file mode 100644
index b3c80a715f..0000000000
--- a/ja/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>ミドルウェア</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/ja/resources/community.md b/ja/resources/community.md
deleted file mode 100644
index 2fb3f05c7e..0000000000
--- a/ja/resources/community.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-layout: page
-title: Express のコミュニティー
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# コミュニティー
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-この活気あるコミュニティーでは、さまざまな拡張機能、[ミドルウェア・モジュール](/{{ page.lang }}/resources/middleware.html)、高水準のフレームワークが作成されています。[Wiki](https://github.com/expressjs/express/wiki) で確認してください。
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## 問題
-
-バグに思われるものが見つかったり、単に機能を要求したりする場合は、[問題のキュー](https://github.com/expressjs/express/issues)でチケットをオープンしてください。
-
-## 例
-
-API の設計や認証からテンプレート・エンジンの統合まで、あらゆるものを扱っている数十の Express アプリケーションの[例](https://github.com/expressjs/express/tree/master/examples)をリポジトリーでご覧ください。
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/ja/resources/contributing.md b/ja/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/ja/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/ja/resources/glossary.md b/ja/resources/glossary.md
deleted file mode 100644
index b5f4b3e80a..0000000000
--- a/ja/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express の用語集
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# 用語集
-
-### アプリケーション
-
-In general, one or more programs that are designed to carry out operations for a specific purpose.  一般に、特定の目的で操作を実行するよう設計された 1 つ以上のプログラム。Express のコンテキストでは、Node.js プラットフォームで稼働する Express API を使用するプログラム。[アプリケーション・オブジェクト](/{{ page.lang }}/api.html#express)と呼ばれることもある。  Might also refer to an [app object](/{{ page.lang }}/api.html#express).
-
-### API
-
-Application programming interface. Spell out the abbreviation when it is first used.
-
-### Express
-
-特定の意見に固執しない、Node.js アプリケーション向けの高速で最小限の Web フレームワーク。一般に、「Express」の望ましい呼び方は「Express.js」であるが、後者でも問題はない。 In general, "Express" is preferred to "Express.js," though the latter is acceptable.
-
-### libuv
-
-主に Node.js で使用するために開発された、非同期入出力に重点を置いたマルチプラットフォーム・サポート・ライブラリー。
-
-### middleware
-
-最後のリクエストハンドラーの前に Express ルーティング層によって呼び出される関数。そのため、未加工要求と最後の目的のルートの間に配置される。ミドルウェアの用語に関しては、微妙な点がいくつかある。 A few fine points of terminology around middleware:
-
-- `var foo = require('middleware')` は、Node.js モジュールを_要求_ または_使用_ することで呼び出される。その後、通常はステートメント `var mw = foo()` がミドルウェアを返す。 Then the statement `var mw = foo()` typically returns the middleware.
-- `app.use(mw)` は、_グローバル処理スタックにミドルウェアを追加_ することで呼び出される。
-- `app.get('/foo', mw, function (req, res) { ... })` は、_「GET /foo」処理スタックにミドルウェアを追加_ することで呼び出される。
-
-### Node.js
-
-A software platform that is used to build scalable network applications. スケーラブルなネットワーク・アプリケーションを作成するために使用されるソフトウェア・プラットフォーム。Node.js は、スクリプト言語として JavaScript を使用し、ノンブロッキング入出力と単一スレッドのイベント・ループを通して高スループットを実現する。[nodejs.org](http://nodejs.org/) を参照。**使用上の注意**: 初回は「Node.js」を使用し、その後は「Node」を使用する。 See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
-
-### オープン・ソース
-
-When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### リクエスト
-
-An HTTP request. HTTP レスポンス。サーバーは、HTTP レスポンスメッセージをクライアントに返す。レスポンスにはリクエストの完了状況情報が含まれ、リクエストされた内容がメッセージの本文に入っている場合もある。  HTTP リクエスト。クライアントは HTTP リクエストメッセージをサーバーに送信して、サーバーはレスポンスを返す。リクエストでは、いずれかの[リクエストメソッド](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) (GET、POST など) を使用する必要がある。
-
-### レスポンス
-
-An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
-
-### ルート
-
-Part of a URL that identifies a resource. リソースを識別する URL の一部。例えば、`http://foo.com/products/id` の中では「/products/id」がルートである。
-
-### ルーター
-
-API リファレンスで[ルーター](/{{ page.lang }}/4x/api.html#router)を参照。
diff --git a/ja/resources/middleware.md b/ja/resources/middleware.md
deleted file mode 100644
index 7eab9e8256..0000000000
--- a/ja/resources/middleware.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-layout: middleware
-title: Express のミドルウェア
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Express のミドルウェア
-
-The Express middleware modules listed here are maintained by the
-[Expressjs team](https://github.com/orgs/expressjs/people).
-
-| Middleware module                                                           | 説明                                                                                                                                  |
-| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                                             |
-
-## Additional middleware modules
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Middleware module                                                                                             | 説明                                                                                                                                                                                            |
-| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet): さまざまな HTTP ヘッダーを設定することでアプリケーションを保護する上で役立つモジュール。 | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport): 認証のための Express ミドルウェア・モジュール。             | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/ja/resources/middleware/body-parser.md b/ja/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/ja/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/ja/resources/middleware/compression.md b/ja/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/ja/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/ja/resources/middleware/connect-rid.md b/ja/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/ja/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/ja/resources/middleware/cookie-parser.md b/ja/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/ja/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/ja/resources/middleware/cookie-session.md b/ja/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/ja/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/ja/resources/middleware/cors.md b/ja/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/ja/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/ja/resources/middleware/errorhandler.md b/ja/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/ja/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/ja/resources/middleware/method-override.md b/ja/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/ja/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/ja/resources/middleware/morgan.md b/ja/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/ja/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/ja/resources/middleware/multer.md b/ja/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/ja/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/ja/resources/middleware/response-time.md b/ja/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/ja/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/ja/resources/middleware/serve-favicon.md b/ja/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/ja/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/ja/resources/middleware/serve-index.md b/ja/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/ja/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/ja/resources/middleware/serve-static.md b/ja/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/ja/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/ja/resources/middleware/session.md b/ja/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/ja/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/ja/resources/middleware/timeout.md b/ja/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/ja/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/ja/resources/middleware/vhost.md b/ja/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/ja/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/ja/resources/utils.md b/ja/resources/utils.md
deleted file mode 100644
index 9d2947a542..0000000000
--- a/ja/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | 説明                                                                                                                                                                                                                         |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/ja/starter/basic-routing.md b/ja/starter/basic-routing.md
deleted file mode 100644
index bc3035c519..0000000000
--- a/ja/starter/basic-routing.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-layout: page
-title: Express の基本的なルーティング
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# 基本的なルーティング
-
-_ルーティング_ とは、アプリケーションが特定のエンドポイントに対するクライアント要求に応答する方法として、URI (またはパス) と特定の HTTP 要求メソッド (GET、POST など) を決定することです。
-
-各ルートには、1 つ以上のハンドラー関数があり、それらはルートが一致したときに実行されます。
-
-ルート定義では、次の構造を使用します。
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Where:
-
-- `app` は、`express` のインスタンスです。
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` は、サーバー上のパスです。
-- `HANDLER` は、ルートが一致したときに実行される関数です。
-
-<div class="doc-box doc-notice" markdown="1">
-This tutorial assumes that an instance of `express` named `app` is created and the server is running. 
-このチュートリアルでは、`app` という名前の `express` のインスタンスが作成されていて、サーバーが稼働中であることを想定しています。アプリケーションの作成と開始に慣れていない場合は、[Hello World の例](/{{ page.lang }}/starter/hello-world.html) を参照してください。
-
-</div>
-
-以下の例は、単純なルートの定義を示しています。
-
-ホーム・ページで `Hello World!` と応答します。
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-`/user` ルートに対する PUT 要求に応答します。
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-`/user` ルートに対する DELETE 要求に応答します。
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-ルーティングについて詳しくは、[ルーティング・ガイド](/{{ page.lang }}/guide/routing.html)を参照してください。
-
diff --git a/ja/starter/examples.md b/ja/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/ja/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/ja/starter/faq.md b/ja/starter/faq.md
deleted file mode 100644
index e21a5f4af4..0000000000
--- a/ja/starter/faq.md
+++ /dev/null
@@ -1,97 +0,0 @@
----
-layout: page
-title: Express に関する FAQ
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# よくある質問
-
-## どのようにしてアプリケーションを構成するのですか?
-
-There is no definitive answer to this question. The answer depends
-on the scale of your application and the team that is involved. To be as
-flexible as possible, Express makes no assumptions in terms of structure.
-
-ルートやその他のアプリケーション固有のロジックは、必要な数だけのファイルや、任意のディレクトリー構造に存在できます。参考のために、以下の例を参照してください。 View the following
-examples for inspiration:
-
-- [ルートのリスト](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [ルートのマップ](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [MVC スタイルのコントローラー](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-また、これらのパターンを簡素化する、サード・パーティー製の Express 拡張版があります。
-
-- [Resourceful ルーティング](https://github.com/expressjs/express-resource)
-
-## どのようにしてモデルを定義するのですか?
-
-Express には、データベースの概念がありません。この概念はサード・パーティーの Node モジュールに任せられているため、ほとんどのデータベースとやりとりできます。 This concept is
-left up to third-party Node modules, allowing you to
-interface with nearly any database.
-
-モデルに関する Express ベースのフレームワークについては、[LoopBack](http://loopback.io) を参照してください。
-
-## どのようにしてユーザーを認証するのですか?
-
-Authentication is another opinionated area that Express does not
-venture into. You may use any authentication scheme you wish.
-認証は、Express が足を踏み入れていないもう 1 つの分野です。任意の認証スキームを使用できます。
-単純なユーザー名/パスワードのスキームについては、[この例](https://github.com/expressjs/express/tree/master/examples/auth)を参照してください。
-
-## Express はどのテンプレート・エンジンをサポートしているのですか?
-
-Express は、`(パス、ロケール、コールバック)` シグニチャーに準拠するすべてのテンプレート・エンジンをサポートします。
-テンプレート・エンジンのインターフェースとキャッシングを正規化するには、[consolidate.js](https://github.com/visionmedia/consolidate.js) プロジェクトでサポートを参照してください。リストされていないテンプレート・エンジンでも Express シグニチャーをサポートしている可能性があります。
-To normalize template engine interfaces and caching, see the
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-project for support. Unlisted template engines might still support the Express signature.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## どのようにして 404 応答に対応するのですか?
-
-Express では、404 応答はエラーの結果ではありません。そのため、エラー・ハンドラー・ミドルウェアはそれらをキャプチャーしません。このように動作するのは、404 応答は単に追加の処理が存在しないことを示しているためです。つまり、Express は、すべてのミドルウェア関数とルートを実行して、そのいずれも応答しなかったことを検出したということです。404 応答に対応するには、スタックの最下部 (他のすべての関数の下) にミドルウェア関数を追加するだけですみます。 This behavior is
-because a 404 response simply indicates the absence of additional work to do;
-in other words, Express has executed all middleware functions and routes,
-and found that none of them responded. All you need to
-do is add a middleware function at the very bottom of the stack (below all other functions)
-to handle a 404 response:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## どのようにしてエラー・ハンドラーをセットアップするのですか?
-
-エラー処理ミドルウェアの定義方法は、他のミドルウェアと同じですが、引数の数が 3 つではなく 4 つである点が異なります。具体的には、シグニチャー `(err、req、res、next)` です。
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-詳細については、[エラー処理](/{{ page.lang }}/guide/error-handling.html)を参照してください。
-
-## どのようにしてプレーン HTML をレンダリングするのですか?
-
-You don't! レンダリングしません。`res.render()` 関数で HTML を「レンダリング」する必要はありません。
-特定のファイルがある場合は、`res.sendFile()` 関数を使用します。
-ディレクトリーから多数の資産を提供する場合は、`express.static()` ミドルウェア関数を使用します。
-If you have a specific file, use the `res.sendFile()` function.
-If you are serving many assets from a directory, use the `express.static()`
-middleware function.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) には Node.js 0.10 以上が必要です。
-- [Express 5.x](/{{ page.lang }}/5x/api.html) には Node.js 18 以上が必要です。
\ No newline at end of file
diff --git a/ja/starter/generator.md b/ja/starter/generator.md
deleted file mode 100644
index 28e96c5540..0000000000
--- a/ja/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Express のアプリケーション生成プログラム
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Express のアプリケーション生成プログラム
-
-アプリケーション生成プログラム・ツールの `express` を使用すると、アプリケーション・スケルトンを素早く作成できます。
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-`-h` オプションを指定してコマンド・オプションを表示します。
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-例えば、以下のコマンドでは、現行作業ディレクトリーに _myapp_ という Express アプリケーションを作成します。 The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-次に、依存関係をインストールします。
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-Windows では、次のコマンドを使用します。
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-On Windows Command Prompt, use this command:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-次に、ブラウザーに `http://localhost:3000/` をロードして、アプリケーションにアクセスします。
-
-生成されたアプリケーションには、以下のディレクトリー構造があります。
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-The app structure created by the generator is just one of many ways to structure Express apps. Feel free to use this structure or modify it to best suit your needs.
-</div>
\ No newline at end of file
diff --git a/ja/starter/hello-world.md b/ja/starter/hello-world.md
deleted file mode 100644
index 1aad108c63..0000000000
--- a/ja/starter/hello-world.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-layout: page
-title: Express の「Hello World」の例
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Hello World の例
-
-<div class="doc-box doc-info" markdown="1">
-Embedded below is essentially the simplest Express app you can create. It is a single file app &mdash; _not_ what you'd get if you use the [Express generator](/{{ page.lang }}/starter/generator.html), which creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and sub-directories for various purposes.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-This app starts a server and listens on port 3000 for connections. アプリケーションは、サーバーを始動して、ポート 3000 で接続を listen します。アプリケーションは、ルート URL (`/`) または_ルート_ に対する要求に「Hello World!」と応答します。その他すべてのパスについては、「**404 Not Found**」と応答します。 For every other path, it will respond with a **404 Not Found**.
-
-### Running Locally
-
-最初に、`myapp` という名前のディレクトリーを作成して、そのディレクトリーに移動し、`npm init` を実行します。次に、[インストール・ガイド](/{{ page.lang }}/starter/installing.html)に従い、依存関係として `express` をインストールします。 Then, install `express` as a dependency, as per the [installation guide](/{{ page.lang }}/starter/installing.html).
-
-`myapp` ディレクトリーで、`app.js` というファイルを作成して、以下のコードを追加します。
-
-<div class="doc-box doc-notice" markdown="1">
-`req` (要求) と `res` (応答) は、Node が提供するのとまったく同じオブジェクトであるため、Express が関与しない場合と同じように、`req.pipe()`、`req.on('data', callback)` などを呼び出すことができます。
-</div>
-
-次のコマンドを使用してアプリケーションを実行します。
-
-```bash
-$ node app.js
-```
-
-次に、ブラウザーに [http://localhost:3000/](http://localhost:3000/) をロードして、出力を確認します。
\ No newline at end of file
diff --git a/ja/starter/installing.md b/ja/starter/installing.md
deleted file mode 100644
index 290c2931f8..0000000000
--- a/ja/starter/installing.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-layout: page
-title: Express のインストール
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# インストール
-
-既に [Node.js](https://nodejs.org/) をインストールしてあることを想定して、ここではアプリケーションを作成するディレクトリーを作り、それを作業ディレクトリーにします。
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) には Node.js 0.10 以上が必要です。
-- [Express 5.x](/{{ page.lang }}/5x/api.html) には Node.js 18 以上が必要です。
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-`npm init` コマンドを使用して、アプリケーション用の `package.json` ファイルを作成します。
-`package.json` の機能について詳しくは、[Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json) を参照してください。
-For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-This command prompts you for a number of things, such as the name and version of your application.
-For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-```
-entry point: (index.js)
-```
-
-`app.js` と入力するか、メインファイルの名前にしたいものを何か入力してください。もしそれを `index.js` にしたいのなら、RETURN キーを押して提案されたデフォルトのファイル名を受け入れてください。 If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
-
-Expressを `myapp` ディレクトリにインストールし、それを依存関係リストに保存してください。例えば： For example:
-
-```bash
-$ npm install express
-```
-
-Express を一時的にインストールし、それを依存関係リストに追加しないようにするには、次のようにします。
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-
-npm 5.0 以降のデフォルトでは、npm install はモジュールを `package.json` ファイルの `dependencies` リストに追加します。以前のバージョンの npm では、`--save` オプションを明示的に指定しなければなりません。その後、app ディレクトリで `npm install` を実行すると、依存関係リストにモジュールが自動的にインストールされます。
- Then, afterwards, running `npm install` in the app directory will automatically install modules in the dependencies list.
-</div>
\ No newline at end of file
diff --git a/ja/starter/static-files.md b/ja/starter/static-files.md
deleted file mode 100644
index 01482e914c..0000000000
--- a/ja/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: Express での静的ファイルの提供
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Express での静的ファイルの提供
-
-イメージ、CSS ファイル、JavaScript ファイルなどの静的ファイルを提供するには、Express に標準実装されている `express.static` ミドルウェア関数を使用します。
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-これで、`public` ディレクトリーに入っているファイルをロードできます。
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express は、静的ディレクトリーから相対的なファイルを検索するため、静的ディレクトリーの名前は URL の一部ではありません。
-</div>
-
-複数の静的アセットディレクトリーを使用するには、`express.static` ミドルウェア関数を複数回呼び出します。
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express は、`express.static` ミドルウェア関数に静的ディレクトリーが設定された順序でファイルを検索します。
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-これで、`public` ディレクトリー内のファイルを `/static` パス・プレフィックスからロードできます。
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-ただし、`express.static` 関数に指定するパスは、`node` プロセスを起動するディレクトリーに対して相対的です。別のディレクトリーから Express アプリケーションを実行する場合は、提供するディレクトリーの絶対パスを使用する方が安全です。 If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/ja/support/index.md b/ja/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/ja/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/js/app.js b/js/app.js
deleted file mode 100644
index b8888e0642..0000000000
--- a/js/app.js
+++ /dev/null
@@ -1,102 +0,0 @@
-const i18nMsgBox = document.getElementById("i18n-notice-box");
-
-// add/remove class 'scroll' on scroll by 5px
-const scrollTarget = document.querySelector('.logo-container');
-const scrollObserver = new IntersectionObserver(
-  ([entry]) => {
-    if (!entry.isIntersecting) {
-      document.body.classList.add('scroll');
-    } else {
-      document.body.classList.remove('scroll');
-    }
-  },
-  {
-    root: null,
-    threshold: 0,
-    rootMargin: '0px 0px 0px 0px'
-  }
-);
-
-if (scrollTarget) scrollObserver.observe(scrollTarget);
-
-// heighlight current Menu on scroll
-const headings = Array.from(document.querySelectorAll("h2, h3"));
-const menuLinks = document.querySelectorAll("#menu li a");
-
-const observerOptions = {
-  root: null,
-  rootMargin: "-10% 0px -65% 0px",
-  threshold: 1,
-};
-
-const menuObserver = new IntersectionObserver((entries) => {
-  entries.forEach((entry) => {
-    if (entry.isIntersecting) {
-      const currentApiPrefix = entry.target.id.split(".")[0];
-      const parentMenuSelector = `#${currentApiPrefix}-menu`;
-      const parentMenuEl = document.querySelector(parentMenuSelector);
-
-      // open submenu on scroll
-      if (parentMenuEl) parentMenuEl.classList.add("active");
-
-      // Remove active class from last menu item
-      const lastActiveMenu = document.querySelector(".active[id$='-menu']");
-      if (lastActiveMenu && lastActiveMenu.id !== parentMenuEl.id) {
-        lastActiveMenu.classList.remove("active");
-      }
-
-      // Update active link
-      menuLinks.forEach((link) => link.classList.remove("active"));
-      const activeLink = document.querySelector(`a[href="#${entry.target.id}"]`);
-      if (activeLink && !activeLink.classList.contains("active")) activeLink.classList.add("active");
-    }
-  });
-}, observerOptions);
-
-headings.forEach((heading) => menuObserver.observe(heading));
-
-// i18n message box : this box appears hidden for all page.lang != 'en'
-const isI18nCookie = readCookie('i18nClose');
-if (i18nMsgBox && !isI18nCookie) {
-  const closeI18nBtn = document.getElementById("close-i18n-notice-box");
-  // show notice box
-  i18nMsgBox.hidden = false;
-  // close notice box
-  if (closeI18nBtn) {
-    closeI18nBtn.addEventListener("click", () => {
-      // hide notice
-      i18nMsgBox.hidden = true;
-      // set session cookie
-      createCookie('i18nClose', 1);
-    });
-
-    // keyboard a11y
-    closeI18nBtn.addEventListener("keydown", (e) => {
-      if (e.key === "Enter" || e.key === " ") {
-        e.preventDefault();
-        closeI18nBtn.click();
-      }
-    });
-  }
-};
-
-function createCookie(name, value, days) {
-  let expires = "";
-  if (days) {
-    const date = new Date();
-    date.setTime(date.getTime() + (days * 864e5));
-    expires = "; expires=" + date.toUTCString();
-  }
-  document.cookie = `${encodeURIComponent(name)}=${encodeURIComponent(value)}${expires}; path=/; SameSite=Lax; Secure`;
-}
-
-function readCookie(name) {
-  const nameEQ = encodeURIComponent(name) + "=";
-  const ca = document.cookie.split(';');
-  for (let i = 0; i < ca.length; i++) {
-    let c = ca[i];
-    while (c.charAt(0) === ' ') c = c.substring(1, c.length);
-    if (c.indexOf(nameEQ) === 0) return decodeURIComponent(c.substring(nameEQ.length, c.length));
-  }
-  return null;
-}
diff --git a/js/copycode.js b/js/copycode.js
deleted file mode 100644
index 2174710746..0000000000
--- a/js/copycode.js
+++ /dev/null
@@ -1,59 +0,0 @@
-const codeBlocks = document.querySelectorAll("pre:has(code)");
-
-codeBlocks.forEach((block) => {
-  // Only add button if browser supports Clipboard API
-  if (!navigator.clipboard) return;
-
-  const button = createCopyButton();
-  block.appendChild(button);
-  block.setAttribute("tabindex", 0); // Add keyboard a11y for <pre></pre>
-
-  button.addEventListener("click", async () => {
-    await copyCode(block, button);
-  });
-});
-
-function createCopyButton() {
-  const button = document.createElement("button");
-  setButtonAttributes(button, {
-    type: "button", // button doesn't act as a submit button
-    title: "copy code",
-    "aria-label": "click to copy code",
-  });
-  return button;
-}
-
-function setButtonAttributes(button, attributes) {
-  for (const [key, value] of Object.entries(attributes)) {
-    button.setAttribute(key, value);
-  }
-}
-
-async function copyCode(block, button) {
-  const code = block.querySelector("code");
-  let text = code.innerText;
-  // remove "$" and space if exists at the beginning of the code
-  text = text.replace(/^\$\s?/,"");
-
-  try {
-    await navigator.clipboard.writeText(text);
-    updateButtonState(button, "copied", "code is copied!");
-  } catch {
-    updateButtonState(button, "failed", "failed!");
-  }
-}
-
-function updateButtonState(button, statusClass, ariaLabel) {
-  button.setAttribute("aria-live", "polite");
-  button.setAttribute("aria-label", ariaLabel);
-  button.classList.add(statusClass);
-
-  // Clear any existing timer
-  if (button.dataset.timerId) clearTimeout(Number(button.dataset.timerId));
-  const timer = setTimeout(() => {
-    button.classList.remove(statusClass);
-    button.setAttribute("aria-label", "click to copy code");
-  }, 1000);
-
-  button.dataset.timerId = timer;
-}
diff --git a/js/menu.js b/js/menu.js
deleted file mode 100644
index 5ee91a6016..0000000000
--- a/js/menu.js
+++ /dev/null
@@ -1,195 +0,0 @@
-// It uses `window.matchMedia` instead of `window.addEventListener('resize')` because `matchMedia` performs better by not changing its value with every screen resize.
-const mobileScreen = window.matchMedia("(max-width: 1110px)");
-let isSmallScreen = mobileScreen?.matches;
-const tocScreen = window.matchMedia("(max-width: 800px)");
-let isTocScreen = tocScreen.matches;
-
-mobileScreen?.addEventListener("change", (event) => {
-	isSmallScreen = event.matches
-
-  if (!isSmallScreen) {
-		document.body.classList.remove("no-scroll")
-	}
-});
-
-// Desktop Menu
-
-const itemsMenu = document.querySelectorAll(".submenu");
-const navDrawers = document.querySelectorAll('#navmenu > li')
-let activeDrawer // active dropdown nav link
-
-
-for (const el of itemsMenu) {
-	el.addEventListener("click", (e) => {
-		if (e.target.parentNode === el && e.pointerType === "touch" && el.querySelector("a.active")) {
-			e.preventDefault(); // Tapping active menu on touchscreen tablet should open menu, not click
-		}
-		if (isSmallScreen || 'ontouchstart' in document.documentElement) {
-		// HANDLE ACTIVE LINKS IN DROPDOWN NAV	
-		// if no activeDrawer set then page was set in md logic
-		if (!activeDrawer) {
-			// remove default active link
-			removeActiveFromDrawers(navDrawers)
-			// set new active drawer to clicked
-			activeDrawer = el
-			// add active class
-			addActiveToDrawer(el)
-		// remove prev activeDrawer and set current to active
-		} else if (activeDrawer.id !== el.id) {
-			activeDrawer.querySelector('a').classList.remove('active')
-			addActiveToDrawer(el)
-			activeDrawer = el
-		}
-
-			for (const item of itemsMenu) {
-        // close any open drawers on click next drawer
-				if (item.id !== el.id) {
-					item.classList.remove("open");
-				}
-			}
-			el.classList.toggle("open");
-		}
-	});
-
-	el.addEventListener("mouseenter", () => {
-		if (!isSmallScreen) {
-			el.classList.add("open");
-		}
-	});
-
-	el.addEventListener("mouseleave", () => {
-		if (!isSmallScreen) {
-			el.classList.remove("open");
-		}
-	});
-}
-
-// Mobile Menu and Language Picker
-const langBtn = document.getElementById("langBtn");
-const langList = document.getElementById("langList");
-const linkItemsMenu = document.querySelectorAll(".submenu > a");
-const menu = document.querySelector("#navmenu");
-const overlay = document.querySelector("#overlay");
-const navButton = document.querySelector("#nav-button");
-
-function closeLangList() {
-  langList.classList.remove("open");
-  langBtn.setAttribute("aria-expanded", false);
-}
-
-function toggleLangList() {
-  const isOpen = langList.classList.toggle("open");
-  langBtn.setAttribute("aria-expanded", isOpen);
-}
-
-// toggle on button click
-langBtn.addEventListener("click", (e) => {
-  e.stopPropagation();
-  toggleLangList();
-});
-
-// close on outside click except for lang btn
-document.body.addEventListener("click", (e) => {
-  if (!langList.contains(e.target)) {
-    closeLangList();
-  }
-});
-
-for (const el of linkItemsMenu) {
-	el.addEventListener("click", (e) => {
-		if (el.classList.contains("open")) {
-			el.classList.remove("open");
-		}
-		
-		if (isSmallScreen || 'ontouchstart' in document.documentElement) {
-			e.preventDefault();
-		}
-	});
-}
-
-navButton?.addEventListener("click", () => {
-	menu?.classList.toggle("opens");
-	overlay?.classList.toggle("blurs");
-	document.body.classList.toggle("no-scroll");
-});
-
-overlay?.addEventListener("click", () => {
-	if (menu?.classList.contains("opens")) {
-		menu.classList.remove("opens");
-	}
-	overlay.classList.remove("blurs");
-	document.body.classList.remove("no-scroll");
-	// TODO : write helper function 
-	const isOpen = langList.classList.toggle("open");
-	langBtn.setAttribute("aria-expanded", isOpen);
-});
-
-document
-	.querySelector(`.submenu-content a[href="{document.location.pathname}"]`)
-	?.classList.add("current");
-
-// when active is unknown, loop over and remove any active link
-function removeActiveFromDrawers(navDrawers) {
-  for (const item of navDrawers) {
-    item.querySelector('a').classList.remove('active')
-  }
-}
-// add active to known link
-function addActiveToDrawer(drawer) {
-	drawer.querySelector('a').classList.add('active')
-}
-
-// TOC 
-const toggleBtn = document.getElementById("menu-toggle");
-const tocList = document.getElementById("menu");
-
-function updateTocVisibility() {
-	if (isTocScreen) {
-	  toggleBtn?.classList.add("show");
-	} else {
-	  toggleBtn?.classList.remove("show");
-	}
-  }
-
-// toc button on page load
-updateTocVisibility();
-
-// Listen for changes in screen size
-tocScreen.addEventListener("change", (event) => {
-  isTocScreen = event.matches;
-  updateTocVisibility();
-});
-
-// Toggle toc menu on button click
-toggleBtn?.addEventListener("click", (e) => {
-	toggleBtn.classList.toggle("rotate");
-  if(tocList?.classList.contains("open")) {
-	tocList.classList.remove("open");
-  } else {
-	tocList.classList.add("open");
-  }
-});
-  
-// Open/Close sub TOC content on click
-document.querySelectorAll("#menu > li > a").forEach((link) => {
-	link.addEventListener("click", function (event) {
-      event.preventDefault(); // stop navigation to submenu
-
-	  // Find the closest parent <li>
-	  const closestLiParent = link.closest("li");
-	  const childUlSubMenu = closestLiParent.children[1];
-  
-	  // If submenu is already active, remove "active" class (toggle behavior)
-	  if (childUlSubMenu?.classList.contains("active")) {
-		childUlSubMenu.classList.remove("active");
-	  } else {
-		// Remove "active" from all other submenus
-		document.querySelectorAll("#menu > li > ul").forEach((subMenu) => {
-		  subMenu.classList.remove("active");
-		});
-  
-		// Add "active" to the clicked submenu
-		childUlSubMenu?.classList.add("active");
-	  }
-	});
-  });
diff --git a/js/theme.js b/js/theme.js
deleted file mode 100644
index 07df05f0db..0000000000
--- a/js/theme.js
+++ /dev/null
@@ -1,96 +0,0 @@
-let themeBtn;
-const themeWatcher = watchColorSchemeChange((colorScheme) => {
-  if (!hasLocalStorage()) {
-    // If localStorage is not supported, use system preference
-    document?.addEventListener('DOMContentLoaded', () => {
-      // remove icon
-      document.querySelector('#theme-toggle').remove()
-      setTheme(colorScheme);
-    })
-  } else {
-    // user's PS system theme settings
-    const systemTheme = localStorage.getItem('system-theme')
-    // setting stored in local storage    
-    const localTheme = localStorage.getItem('local-theme')
-    // if no local theme set - system is default
-    if (localTheme === null) {
-      setTheme(colorScheme)
-      localStorage.setItem('system-theme', colorScheme)
-    // page load - load any stored themes or set theme
-    } else {
-      // listen for system changes, update if any 
-      if (colorScheme != systemTheme) {
-        setTheme(colorScheme)
-        localStorage.setItem('system-theme', colorScheme)
-      } else {
-        // else load local theme
-        setTheme(localTheme);
-      }
-    }
-    // wait for load then and add listener on button
-    document.addEventListener('DOMContentLoaded', () => {
-      const themeToggle = document?.querySelector('#theme-toggle');
-      themeToggle.addEventListener('click', toggleLocalStorageTheme);
-      // set area-label for screen readers
-      themeToggle.setAttribute('aria-label', colorScheme ? 'Switch to light mode' : 'Switch to dark mode');
-    })
-  }
-})
-// apply current theme
-function setTheme(theme) {
-  if (theme === 'dark') {
-    darkModeOn()
-  } else {
-    lightModeOn()
-  }
-}
-// toggle btn themes
-function toggleLocalStorageTheme() {
-  const localTheme = localStorage.getItem('local-theme');
-  if (localTheme === 'light') {
-    setTheme('dark');
-  } else {
-    setTheme('light');
-  }
-}
-function darkModeOn() {
-  document?.documentElement?.classList.remove('light-mode')
-  document?.documentElement?.classList.add('dark-mode')
-  updateThemeIcon('dark');
-  localStorage.setItem('local-theme', 'dark');
-}
-function lightModeOn() {
-  document?.documentElement?.classList.remove('dark-mode')
-  document?.documentElement?.classList.add('light-mode')
-  updateThemeIcon('light');
-  localStorage.setItem('local-theme', 'light');
-}
-function hasLocalStorage() {
-  return typeof Storage !== 'undefined'
-}
-function watchColorSchemeChange(callback) {
-  // get system theme preference
-  const darkMediaQuery = window?.matchMedia('(prefers-color-scheme: dark)')
-
-  const handleChange = (event) => {
-    const newColorScheme = event?.matches ? 'dark' : 'light'
-    callback(newColorScheme)
-  }
-  darkMediaQuery.addEventListener('change', handleChange)
-  // initial call : if system theme is not dark then light mode is choosen
-  callback(darkMediaQuery.matches ? 'dark' : 'light')
-  // remove event from window
-  return () => darkMediaQuery.removeEventListener('change', handleChange)
-}
-
-function updateThemeIcon (theme) {
-  const sun = document?.getElementById('icon-sun');
-  const moon = document?.getElementById('icon-moon');
-  const themeToggle = document?.getElementById('theme-toggle');
-  if (!sun || !moon || !themeToggle) return;
-  const isDark = theme === 'dark';
-  // improve accessibility for screen readers 
-  sun.setAttribute('aria-hidden', isDark ? 'false' : 'true');
-  moon.setAttribute('aria-hidden', isDark ? 'true' : 'false');
-  themeToggle.setAttribute('aria-label', isDark ? 'Switch to light mode' : 'Switch to dark mode');
-};
diff --git a/ko/3x/api.md b/ko/3x/api.md
deleted file mode 100644
index 1e7377cfa5..0000000000
--- a/ko/3x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API 참조
-description: Express.js 3.x 버전의 API 참조에 접근할 수 있습니다. 이 버전은 지원이 종료되었으며 더 이상 유지보수되지 않습니다. 모듈과 메소드에 대한 상세한 정보가 포함되어 있습니다.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x은 더 이상 유지보수되지 않습니다.**
-
-3.x의 알려진 또는 알려지지 않은 보안 및 성능 문제는 마지막 업데이트(2015년 8월 1일) 이후로 처리되지 않고 있습니다. 최신 버전의 Express를 사용할 것을 강력히 권장합니다.
-
-버전 3.x 이상으로 업그레이드할 수 없는 경우, [상업적 지원 옵션](/{{ page.lang }}/support#commercial-support-options)을 고려해주시기 바랍니다.
-
-  </div>
-
-  <h1>3.x API</h1>
-
-{% include api/en/3x/express.md %}
-{% include api/en/3x/app.md %}
-{% include api/en/3x/req.md %}
-{% include api/en/3x/res.md %}
-{% include api/en/3x/middleware.md %}
-
-</div>
diff --git a/ko/4x/api.md b/ko/4x/api.md
deleted file mode 100644
index eb25a7a467..0000000000
--- a/ko/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API 참조
-description: Express.js 4.x의 API 레퍼런스를 확인하여, 이 버전으로 웹 애플리케이션을 구축할 때 사용할 수 있는 모든 모듈, 메서드, 속성에 대해 자세히 알아봅니다.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>4.x API</h1>
-
-{% capture node-version %}
-
-Express 4.0에는  Node.js 0.10 이상이 필요합니다.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/ko/5x/api.md b/ko/5x/api.md
deleted file mode 100644
index 20ceeb8ae1..0000000000
--- a/ko/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 참조
-description: Express.js 5.x의 API 레퍼런스를 확인하여, 이 버전으로 웹 애플리케이션을 구축할 때 사용할 수 있는 모든 모듈, 메서드, 속성에 대해 자세히 알아봅니다.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0에는  Node.js 18 이상이 필요합니다.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/ko/advanced/best-practice-performance.md b/ko/advanced/best-practice-performance.md
deleted file mode 100644
index 32baab92a2..0000000000
--- a/ko/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,313 +0,0 @@
----
-layout: page
-title: 프로덕션 환경에서의 Express 사용을 위한 성능 우수 사례
-description: Express 애플리케이션의 프로덕션 환경에서 성능과 안정성을 최적화하기 위한 모범 사례를 알아봅니다. 여기에는 코드 최적화와 최적의 성능을 위한 환경 설정이 포함됩니다.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# 프로덕션 우수 사례: 성능 및 신뢰성
-
-이 문서에서는 프로덕션 환경에 배치된 Express 애플리케이션을 위한 성능 및 신뢰성 관련 우수 사례에 대해 논의합니다.
-
-이 주제는 명백하게 "DevOps" 분야로 구분할 수 있으며 종래의 개발 및 운영 모두를 다룹니다. 따라서, 정보는 다음과 같은 두 개의 파트로 나뉘어 있습니다.
-
-- [코드에서 수행할 항목](#code) (개발 파트):
-  - [gzip 압축 사용](#use-gzip-compression)
-  - [동기식 함수 사용하지 않기](#dont-use-synchronous-functions)
-  - [정확한 로깅](#do-logging-correctly)
-  - [올바른 예외 처리](#exceptions)
-- [환경/설정에서 수행할 항목](#env) (운영 파트):
-  - [NODE_ENV를 "production"으로 설정](#set-node_env-to-production)
-  - [앱이 자동으로 다시 시작되도록 보장](#ensure-your-app-automatically-restarts)
-  - [앱을 클러스터에서 실행](#run-your-app-in-a-cluster)
-  - [요청 결과를 캐싱](#cache-request-results)
-  - [로드 밸런서 사용](#use-a-load-balancer)
-  - [역방향 프록시 사용](#proxy)
-
-## 코드에서 해야 할 일 {#in-code}
-
-애플리케이션의 성능을 향상시키기 위해서 코드를 통해 할 수 있는 몇 가지는 다음과 같습니다.
-
-- [gzip 압축 사용](#use-gzip-compression)
-- [동기식 함수 사용하지 않기](#dont-use-synchronous-functions)
-- [정확한 로깅](#do-logging-correctly)
-- [올바른 예외 처리](#exceptions)
-
-### gzip 압축 사용
-
-Gzip 압축을 사용하면 응답 본문의 크기를 크게 줄일 수 있으며, 따라서 웹 앱의 속도를 높일 수 있습니다. Express 앱에서 gzip 압축을 사용하려면 [compression](https://www.npmjs.com/package/compression) 미들웨어를 사용하십시오. 예를 들면 다음과 같습니다.
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-많은 트래픽이 발생하는 프로덕션 환경의 웹사이트의 경우, 압축을 실행하는 가장 좋은 방법은 역방향 프록시 레벨에서 압축을 구현하는 것입니다([역방향 프록시 사용](#proxy) 참조). 그러한 경우에는 compression 미들웨어를 사용할 필요가 없습니다. Nginx에서 gzip 압축을 사용하는 방법에 대한 자세한 내용은 Nginx 문서의 [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module.html)을 참조하십시오.
-
-### 동기식 함수 사용하지 않기
-
-동기식 함수 및 메소드는 리턴될 때까지 실행 프로세스를 묶어 둡니다. 동기식 함수에 대한 한 건의 호출은 몇 마이크로초 또는 밀리초 내에 리턴될 수도 있지만, 많은 트래픽이 발생하는 웹사이트에서 이러한 동기식 호출들이 합산되면 앱의 성능이 낮아집니다. 프로덕션 환경에서는 동기식 함수의 사용을 피하십시오.
-
-Node 및 다수의 모듈은 동기식 및 비동기식 버전의 함수를 제공하지만, 프로덕션 환경에서는 항상 비동기식 버전을 사용하십시오. 동기식 함수의 사용이 정당화되는 유일한 경우는 초기 시작 시에 사용되는 경우입니다.
-
-애플리케이션이 동기 API를 사용할 때마다 경고 메시지와 스택 트레이스를 출력하려면 --trace-sync-io 명령줄 플래그를 사용할 수 있습니다. 물론, 프로덕션 환경에서 이러한 플래그를 실제로 사용해서는 안 되며, 이는 코드가 프로덕션 환경에서 사용될 준비가 되었다는 것을 보장하기 위한 것입니다. 자세한 정보는 [node 커맨드라인 옵션 문서](https://nodejs.org/api/cli.html#cli_trace_sync_io)를 참조하십시오.
-
-### 올바른 로깅 방법을 사용해야 합니다
-
-일반적으로 앱은 디버깅 그리고 앱 활동 로깅(사실상 디버깅 이외의 모든 것)이라는 두 가지 이유로 인해 로깅을 실행합니다. `console.log()` 또는 `console.err()`을 사용하여 터미널에 로그 메시지를 출력하는 것이 일반적인 개발 작업 방식입니다. 단, [이 함수들은](https://nodejs.org/api/console.html#console) 출력 대상이 터미널이나 파일일 경우 동기적으로 동작하므로, 출력 결과를 다른 프로그램으로 파이프하지 않는 이상 프로덕션 환경에서는 적합하지 않습니다.
-
-#### 디버깅의 경우
-
-디버깅을 위해 로깅하는 경우에는 `console.log()`를 사용하는 대신 [debug](https://www.npmjs.com/package/debug)와 같은 특별한 디버깅 모듈을 사용하십시오. 이러한 모듈을 이용하면 DEBUG 환경 변수를 사용하여 디버그 메시지 발생 시 어떠한 디버그 메시지가 `console.err()`로 전송되는지 제어할 수 있습니다. 앱을 순수한 비동기식으로 유지하려면 `console.err()`을 다른 프로그램으로 전송해야 합니다. 그러나 아마도 프로덕션 단계에서 디버그를 수행할 필요는 없을 것입니다.
-
-#### 앱 활동의 경우
-
-애플리케이션 활동(예: 트래픽 추적 또는 API 호출 기록)을 로깅할 때는 console.log() 대신 [Pino](https://www.npmjs.com/package/pino)와 같은 로깅 라이브러리를 사용하는 것이 좋습니다. Pino는 가장 빠르고 효율적인 옵션입니다.
-
-### 올바른 예외 처리
-
-Node 앱은 처리되지 않은 예외가 발생할 때 충돌이 발생합니다. 예외를 처리하지 않고 적절한 조치를 취하지 않으면 Express 앱에서 충돌이 발생하고 오프라인 상태가 됩니다. 아래의 [앱이 자동으로 다시 시작되도록 보장](#restart)의 조언을 따르면 앱은 충돌에서부터 복원될 것입니다. 다행히 Express 앱의 일반적인 시작 시간은 짧습니다. 그럼에도 불구하고, 먼저 앱의 충돌을 피하는 것이 중요하며, 이를 위해서는 예외를 올바르게 처리해야 합니다.
-
-모든 예외를 처리하도록 보장하려면 다음의 기법을 사용하십시오.
-
-- [try-catch 사용](#try-catch)
-- [프로미스 사용](#promises)
-
-이 주제에 대해 자세히 살펴보기 전에 먼저 Node/Express의 오류 처리, 즉 오류 우선(error-first) 콜백의 사용 및 미들웨어를 통한 오류의 전파에 대한 기본적인 사항을 이해해야 합니다. Node는 비동기식 함수로부터 오류를 리턴하기 위해 "오류 우선 콜백" 방식을 사용하며, 여기서 콜백 함수의 첫 번째 매개변수는 오류 오브젝트이고 그 후속 매개변수에 결과 데이터가 뒤따릅니다. 오류가 없음을 나타낼 때는 첫 번째 매개변수로 널(null)을 전달합니다. 의미 있는 방식으로 오류를 처리하려면 콜백 함수는 이에 맞게 오류 우선 콜백 방식을 따라야 합니다. 그리고 Express에서의 우수 사례는 next() 함수를 사용하여 미들웨어 체인을 통해 오류를 전파하는 것입니다.
-
-오류 처리의 기본사항 대한 자세한 내용은 다음을 참조하십시오.
-
-- [Node.js의 오류 처리](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### try-catch 사용
-
-Try-catch는 동기식 코드에서 예외를 처리하는 데 사용할 수 있는 JavaScript 언어 구조체입니다. 예를 들면, try-catch를 사용하여 아래와 같이 JSON 구문 분석 오류를 처리할 수 있습니다.
-
-아래에는 try-catch를 사용하여 잠재적인 프로세스 충돌 예외를 처리하는 예가 표시되어 있습니다.
-이 미들웨어 함수는 JSON 오브젝트이자 "params"라는 이름을 갖는 조회 필드를 수락합니다.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-그러나 try-catch는 동기식 코드에 대해서만 작동합니다. Node 플랫폼은 기본적으로 비동기식이므로(특히, 프로덕션 환경의 경우), try-catch를 통해 많은 예외를 처리할 수는 없을 것입니다.
-
-#### 프로미스 사용
-
-async 함수 내에서 에러가 발생하거나, async 함수 안에서 거부된(rejected) 프로미스를 await 할 경우, 해당 에러는`next(err)`를 호출한 것과 동일하게 에러 핸들러로 전달됩니다.
-자세한 내용은 Node.js 에러 처리 문서를 참고하시기 바랍니다.
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-또한 미들웨어에 비동기 함수를 사용할 수 있으며, 만약 프로미스가 실패할 경우 라우터가 자동으로 에러를 처리합니다 예를 들면 다음과 같습니다.
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-성능과 유지 보수 측면에서 가장 좋은 방법은 에러를 가능한 발생 지점 가까이에서 처리하는 것입니다. 따라서 라우터가 에러를 처리할 수 있더라도 별도의 에러 처리 미들웨어에 의존하기보다 미들웨어 내에서 에러를 직접 잡아 처리하는 것이 권장됩니다.
-
-#### 하지 말아야 할 일
-
-수행하지 _않아야_ 할 한 가지 항목은 예외가 이벤트 루프에까지 발생할 때 생성되는 `uncaughtException` 이벤트를 청취하는 것입니다. `uncaughtException`에 대한 이벤트 리스너를 추가하면 예외가 발생하는 프로세스의 기본 작동을 변경할 수 있으며, 해당 프로세스는 예외가 발생하더라도 계속하여 실행될 것입니다. 이러한 방법은 앱에서 충돌이 발생하는 것을 방지하는 좋은 방법인 것처럼 보일 수 있지만, 처리되지 않은 예외가 발생한 후에도 앱이 계속하여 실행되면 프로세스가 불안정하고 예측할 수 없는 상태가 되므로 이러한 방법은 위험한 작업 방식이며 권장되지 않습니다.
-
-또한 `uncaughtException`을 사용하는 것은 [세련되지 못한 방식](https://nodejs.org/api/process.html#process_event_uncaughtexception)인 것으로 공식적으로 인식되고 있으며, 코어로부터 이러한 방식을 제거하는 방법이 [제안](https://github.com/nodejs/node-v0.x-archive/issues/2582)되어 있습니다. 따라서 `uncaughtException`을 청취하는 것은 좋은 생각이 아닙니다. 따라서 여러 프로세스 및 수퍼바이저의 사용 등을 권장하며, 오류로부터 복구되는 가장 안정적인 방법은 충돌이 발생한 후 다시 시작하는 것인 경우가 많습니다.
-
-[도메인](https://nodejs.org/api/domain.html)의 사용 또한 권장하지 않습니다. 일반적으로 도메인은 문제를 해결하지 못하며, 더 이상 사용되지 않는 모듈입니다.
-
-## 환경/설정에서 수행할 항목
-
-앱의 성능을 향상시키기 위해서 시스템 환경에서 할 수 있는 몇 가지는 다음과 같습니다.
-
-- [NODE_ENV를 "production"으로 설정](#set-node_env-to-production)
-- [앱이 자동으로 다시 시작되도록 보장](#ensure-your-app-automatically-restarts)
-- [앱을 클러스터에서 실행](#run-your-app-in-a-cluster)
-- [요청 결과를 캐싱](#cache-request-results)
-- [로드 밸런서 사용](#use-a-load-balancer)
-- [역방향 프록시 사용](#proxy)
-
-### NODE_ENV를 "production"으로 설정
-
-NODE_ENV 환경 변수는 애플리케이션이 실행되는 환경(일반적으로 개발 환경 또는 프로덕션 환경)을 지정합니다. 성능을 향상하는 가장 간단한 방법 중 하나는 환경 변수 NODE_ENV를 `production`으로 설정하는 것입니다.
-
-NODE_ENV를 "production"으로 설정하면 Express는 다음과 같이 동작합니다.
-
-- 보기 템플리트를 캐싱.
-- CSS 확장기능을 통해 생성된 CSS 파일을 캐싱.
-- 더 간결한 오류 메시지를 생성.
-
-[테스트 결과에 따르면]((https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) NODE_ENV를 production으로 설정하는 것만으로도 애플리케이션 성능이 3배 향상될 수 있음이 확인되었습니다.
-
-특정한 환경을 위한 코드를 작성하는 경우, `process.env.NODE_ENV`를 통해 NODE_ENV의 값을 확인할 수 있습니다. 환경 변수의 값을 확인하는 작업은 성능 저하를 유발하므로 이러한 작업은 낮은 빈도로 실행해야 한다는 점에 주의하십시오.
-
-일반적으로 개발 시에는, 예를 들면 `export` 또는 `.bash_profile` 파일을 이용하여 대화식 쉘에서 환경 변수를 설정할 수 있습니다. 하지만 일반적으로 프로덕션 서버에서는 직접 설정하지 않고, 대신 운영체제의 초기화 시스템(systemd 등) 사용하는 것이 권장됩니다. 다음 섹션에서 일반적인 init 시스템의 사용에 대한 자세한 내용을 확인할 수 있지만, NODE_ENV를 설정하는 것은 성능에 매우 중요하므로(또한 쉽게 실행할 수 있으므로) NODE_ENV의 설정을 여기서 강조합니다.
-
-systemd를 이용하는 경우, 유닛 파일에 `Environment` 지시문을 사용하십시오. 예를 들면 다음과 같습니다.
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-자세한 내용은 [systemd 유닛에서 환경 변수 사용하기를](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/) 참고하시기 바랍니다.
-
-### 앱이 자동으로 다시 시작되도록 보장
-
-프로덕션 환경에서 애플리케이션이 오프라인 상태가 되어서는 절대로 안 됩니다. 따라서 앱에서 충돌이 발생하거나 서버 자체에서 충돌이 발생하는 경우 모두 앱이 다시 시작되도록 해야 합니다. 이러한 일 중 어느 하나라도 발생하지 않는 것이 바람직하지만, 현실적으로는 다음과 같은 방법을 통해 이 두 가지 만일의 사태를 처리해야 합니다.
-
-- 앱에서 충돌이 발생하는 경우 프로세스 관리자를 사용하여 앱(및 Node)을 다시 시작.
-- OS에서 충돌이 발생하는 경우 해당 OS에서 제공하는 init 시스템을 사용하여 프로세스 관리자를 다시 시작. 프로세스 관리자 없이도 init 시스템을 사용할 수 있습니다.
-
-처리되지 않은 예외가 발생하는 경우 Node 애플리케이션에서 충돌이 발생합니다. 가장 먼저 해야 할 일은 앱의 테스트가 잘 이루어지도록 하고 앱이 모든 예외를 처리하도록 하는 것입니다(자세한 내용은 [올바른 예외 처리](#exceptions)를 참조). 그러나 하나의 안전 장치로서, 앱에서 충돌이 발생하는 경우에 앱이 자동으로 다시 시작되도록 하는 메커니즘을 실행하십시오.
-
-#### 프로세스 관리자 사용
-
-개발 시에는 단순히 명령행에서 `node server.js` 또는 이와 유사한 명령을 실행하여 앱을 시작했습니다. 그러나 프로덕션 환경에서 이러한 방식으로 앱을 실행하는 것은 매우 위험합니다. 앱에서 충돌이 발생하면 앱은 다시 시작될 때까지 오프라인 상태가 됩니다. 앱에서 충돌이 발생할 때 앱이 다시 시작되도록 하려면 프로세스 관리자를 사용하십시오. 프로세스 관리자는 애플리케이션을 위한 "컨테이너"이며, 배치 작업을 용이하게 하고, 높은 가용성을 제공하고, 런타임 시에 애플리케이션을 관리할 수 있도록 합니다.
-
-앱에서 충돌이 발생할 때 앱이 다시 시작되도록 하는 것 이외에도, 프로세스 관리자를 통해 다음을 실행할 수 있습니다.
-
-- 런타임 성능 및 자원 소비에 대한 통찰력을 획득.
-- 성능 향상을 위해 설정을 동적으로 수정.
-- 제어 클라스터링 (pm2)
-
-과거에는 [PM2](https://github.com/Unitech/pm2)와 같은 Node.js 프로세스 매니저를 사용하는 것이 널리 퍼져 있었습니다. 원하신다면 해당 문서를 참고하시기 바랍니다. 하지만 프로세스 관리를 위해서는 init 시스템을 사용하는 것을 권장합니다.
-
-#### init 시스템 사용
-
-신뢰성의 다음 단계는 서버가 다시 시작될 때 애플리케이션이 다시 시작되도록 하는 것입니다. 시스템은 여전히 여러 이유로 작동이 중단될 수 있습니다. 서버에서 충돌이 발생할 때 앱이 다시 시작되도록 하려면 OS에 내장된 init 시스템을 사용하십시오. 현재 가장 널리 사용되는 init 시스템은 [systemd](https://wiki.debian.org/systemd)입니다.
-
-Express 앱에 init 시스템을 사용하는 데에는 다음과 같은 두 가지 방법이 있습니다.
-
-- 프로세스 관리자에서 앱을 실행한 후, init 시스템을 통해 프로세스 관리자를 서비스로서 설치하십시오. 프로세스 관리자는 앱에서 충돌이 발생할 때 앱을 자동으로 시작하고, init 시스템은 OS가 다시 시작될 때 프로세스 관리자를 다시 시작할 것입니다. 이러한 접근법은 권장되는 접근법입니다.
-- init 시스템을 통해 직접 앱(및 Node)을 실행하십시오. 이 방법은 조금 더 간편하지만, 프로세스 관리자의 사용을 통한 추가적인 이점을 얻을 수 없습니다.
-
-##### Systemd
-
-Systemd는 Linux용 시스템 및 서비스 관리자입니다. 대부분의 주요 Linux 배포판은 systemd를 기본 init 시스템으로 도입했습니다.
-
-systemd 서비스 구성 파일은 \*유닛 파일(unit file)\*로 불리며, 파일 이름이 .service로 끝납니다. 아래는 Node 애플리케이션을 직접 관리하기 위한 파일 예시입니다. 시스템과 애플리케이션에 맞게 `<angle brackets>` 로 표시된 값을 교체하시기 바랍니다.
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-systemd에 대한 자세한 정보는 [systemd 참조 자료(man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit.html)를 참조하십시오.
-
-### 앱을 클러스터에서 실행
-
-멀티코어 시스템에서는 프로세스 클러스터를 실행하여 Node 앱의 성능을 여러 배 높일 수 있습니다. 클러스터는 해당 앱의 인스턴스를 여러 개 실행하여(이상적인 경우 각 CPU 코어에서 하나의 인스턴스를 실행) 인스턴스들 사이에서 로드 및 태스크를 분배합니다.
-
-![클러스터 API를 사용한 애플리케이션 인스턴스간 부하 분산](/images/clustering.png)
-
-중요: 앱 인스턴스들은 별도의 프로세스로서 실행되므로 이러한 인스턴스들은 동일한 메모리 공간을 공유하지 않습니다. 즉, 오브젝트는 해당 앱의 각 인스턴스에 대한 로컬 오브젝트입니다. 따라서 애플리케이션 코드 내의 상태를 유지보수할 수 없습니다. 그러나 [Redis](http://redis.io/)와 같은 인메모리 데이터 저장소를 사용하면 세션과 관련된 데이터 및 상태를 저장할 수 있습니다. 이러한 주의사항은 기본적으로 여러 프로세스를 이용한 클러스터링 또는 여러 대의 실제 서버를 이용한 클러스터링 등 모든 형태의 수평적 확장에 적용됩니다.
-
-클러스터화된 앱에서 작업자 프로세스는 나머지 프로세스에 영향을 미치지 않으면서 개별적으로 충돌이 발생할 수 있습니다. 성능상의 이점 이외에도, 실패 격리는 앱 프로세스 클러스터를 실행해야 하는 또 다른 이유가 됩니다. 한 작업자 프로세스에서 충돌이 발생할 때마다, 항상 반드시 해당 이벤트를 로깅하고 cluster.fork()를 이용해 새로운 프로세스를 복제생성하십시오.
-
-#### Node의 cluster 모듈 사용
-
-클러스터링은 Node의 [cluster 모듈](https://nodejs.org/api/cluster.html)을 통해 가능합니다. 이러한 클러스터링을 통해 마스터 프로세스는 여러 작업자 프로세스를 복제생성하고, 수신되는 연결을 여러 작업자 사이에서 분배할 수 있습니다.
-
-#### PM2 사용
-
-애플리케이션을 PM2에 배치하면, 애플리케이션 코드를 수정하지 _않고도_ 클러스터링을 활용할 수 있습니다. 먼저 [애플리케이션이 상태 비저장(stateless)](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps)인지 확인해야 합니다 즉, 프로세스 내에 세션, 웹소켓 연결 등 로컬 데이터가 저장되어 있지 않아야 합니다.
-
-PM2로 애플리케이션을 실행하고 있을 때, 특정한 수의 인스턴스에 실행하는 **클러스터 모드**를 켤 수 있습니다. 머신의 가용 CPU 수같은 것들이 특정한 수입니다. 애플리케이션을 끌 필요 없이 `pm2` 커맨드라인 명령을 이용해 클러스터에 있는 프로세스의 수를 직접 바꿀 수도 있습니다.
-
-아래와 같은 방법으로 클러스터 모드를 킵니다.
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-이 수는 PM2 프로세스 파일 (`ecosystem.config.js`나 그와 유사한 파일) 안의 `exec_mode`를 `cluster`나 `instances`를 설정해서 수정될 수 있습니다.
-
-실행이 시작되면, `app`으로 이름지어진 애플리케이션을 아래와 같은 방법으로 스케일링 할 수 있습니다.
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-PM2의 클러스터링에 관한 추가 정보는 PM2 문서의 [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/)를 참고해주세요.
-
-### 요청 결과를 캐싱
-
-프로덕션 환경 내에서의 성능을 향상시키기 위한 또 다른 전략은 요청의 결과를 캐싱하여 앱이 동일한 요청을 반복적으로 제공하는 작업을 반복하지 않도록 하는 것입니다.
-
-애플리케이션의 속도와 성능을 크게 향상시키려면 [Varnish](https://www.varnish-cache.org/) 또는 [Nginx](https://blog.nginx.org/blog/nginx-caching-guide)와 같은 캐싱 서버를 사용하는 것이 좋습니다.
-(참고: [Nginx 캐싱 가이드](https://serversforhackers.com/nginx-caching/))
-
-### 로드 밸런서 사용
-
-앱의 최적화 수준에 상관없이, 하나의 인스턴스는 제한된 양의 로드 및 트래픽만을 처리할 수 있습니다. 앱을 확장하는 방법 중 하나는 해당 앱의 인스턴스를 여러 개 실행하고 로드 밸런서를 통해 트래픽을 분배하는 것입니다. 로드 밸런서를 설정하면 앱의 성능 및 속도를 향상시킬 수 있으며, 하나의 인스턴스를 이용할 때보다 훨씬 더 높은 수준으로 확장할 수 있습니다.
-
-로드 밸런서는 일반적으로 여러 애플리케이션 인스턴스 및 서버에 대한 트래픽을 오케스트레이션하는 역방향 프록시입니다. 애플리케이션의 로드 밸런서를 손쉽게 구축하려면 [Nginx](https://nginx.org/en/docs/http/load_balancing.html)또는 [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts)를 활용할 수 있습니다.
-
-로드 밸런싱을 이용하는 경우, 특정한 세션 ID와 연관된 요청이 해당 요청을 발생시킨 프로세스에 연결되도록 해야 할 수도 있습니다. 이러한 경우는 _세션 선호도(session affinity)_ 또는 \*스티키 세션(sticky session)\*으로 알려져 있으며, 세션 데이터를 위해 Redis와 같은 데이터 저장소를 사용하는 위의 제안을 통해 처리할 수도 있습니다(애플리케이션에 따라 다름). 토론을 위해서는 [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/)를 참조하십시오.
-
-### 역방향 프록시 사용
-
-역방향 프록시는 웹 앱의 프론트에 위치하며, 요청이 앱으로 전달되도록 할 뿐만 아니라 요청에 대한 지원 연산을 수행합니다. 이는 오류 페이지, 압축, 캐싱, 파일 제공, 로드 밸런싱 및 기타 여러 작업을 처리할 수 있습니다.
-
-애플리케이션 상태를 알아야 할 필요가 없는 태스크를 역방향 프록시로 이양하면 Express는 더 적은 자원을 차지하게 되어 특성화된 애플리케이션 태스크를 수행할 수 있습니다. 이러한 이유로 프로덕션환경에서는 Express를 [Nginx](https://www.nginx.org/) 또는 [HAProxy](https://www.haproxy.org/)와 같은 리버스 프록시 뒤에서 실행하는 것을 권장합니다.
diff --git a/ko/advanced/best-practice-security.md b/ko/advanced/best-practice-security.md
deleted file mode 100644
index f15744a61c..0000000000
--- a/ko/advanced/best-practice-security.md
+++ /dev/null
@@ -1,273 +0,0 @@
----
-layout: page
-title: 프로덕션 환경의 Express를 위한 보안 우수 사례
-description: Express 애플리케이션을 프로덕션 환경에서 운영할 때 반드시 지켜야 할 중요한 보안 모범 사례를 알아봅니다. 여기에는 TLS 사용, 입력값 검증, 보안 쿠키 설정, 그리고 다양한 취약점 예방 방법이 포함됩니다.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# 프로덕션 우수 사례: 보안
-
-## 개요
-
-**"프로덕션 (production)"** 이라는 용어는 소프트웨어 라이프사이클 중 애플리케이션 또는 API가 최종 사용자 또는 소비자에게 정식으로 제공되는 단계를 말합니다. 이와 반대로 _"개발(development)"_ 단계에서는 아직 코드가 활발하게 작성 및 테스트되며 애플리케이션은 외부 액세스에 개방되지 않습니다. 이에 대응하는 시스템 환경은 각각 _프로덕션_ 환경 및 _개발_ 환경이라고 부릅니다.
-
-개발 환경 및 프로덕션 환경은 일반적으로 서로 다르게 설정되며 두 환경의 요구사항은 크게 다릅니다. 개발 환경에서는 좋은 것일지라도 프로덕션 환경에서는 허용되지 않을 수도 있습니다. 예를 들면, 개발 환경에서는 디버깅을 위해 상세한 오류 로깅이 선호될 수 있지만, 이러한 행동은 프로덕션 환경에서 보안 우려사항이 될 수 있습니다. 그리고 개발 환경에서는 확장성, 신뢰성 및 성능에 대해 걱정할 필요가 없지만, 이러한 요인들은 프로덕션 환경에서 매우 중요해집니다.
-
-{% capture security-note %}
-
-만약 Express에서 보안 취약점을 발견하셨다면, [보안 정책 및 절차](/en/resources/contributing.html#security-policies-and-procedures)를 참고하시기 바랍니다.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-이 문서에서는 프로덕션 환경에 배치된 Express 애플리케이션을 위한 몇 가지 보안 우수 사례에 대해 논의합니다.
-
-- [프로덕션 모범 사례: 보안](#production-best-practices-security)
-  - [개요](#overview)
-  - [Express의 사용 중단되었거나 취약한 버전을 사용하지 않습니다](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [TLS 사용](#use-tls)
-  - [사용자 입력을 신뢰하지 않습니다](#do-not-trust-user-input)
-    - [오픈 리다이렉트를 방지합니다](#prevent-open-redirects)
-  - [Helmet 사용](#use-helmet)
-  - [지문 인식 감소](#reduce-fingerprinting)
-  - [쿠키를 안전하게 사용](#use-cookies-securely)
-    - <a name="use-cookies-securely"></a>
-    - [ieNoOpen](https://github.com/helmetjs/ienoopen)은 IE8 이상에 대해 `X-Download-Options`를 설정합니다.
-  - [인증 체계에 대한 브루스 포트 공격 방지](#prevent-brute-force-attacks-against-authorization)
-  - [종속 항목이 안전한지 확인](#ensure-your-dependencies-are-secure)
-    - [그 외의 알려져 있는 취약점 회피](#avoid-other-known-vulnerabilities)
-  - [추가적인 고려사항](#additional-considerations)
-
-## 더 이상 사용되지 않거나 취약성이 있는 버전의 Express를 사용 중지
-
-Express 2.x 및 3.x에 대한 유지보수는 더 이상 이루어지지 않습니다. 이러한 버전에서의 보안 및 성능 문제는 수정되지 않습니다. 이러한 버전은 사용하지 마십시오! 아직 버전 4로 이전하지 않은 경우에는 [마이그레이션 안내서](/{{ page.lang }}/guide/migrating-4.html)를 따르십시오.
-
-또한 [보안 업데이트 페이지](/{{ page.lang }}/advanced/security-updates.html)의 목록에 포함된 취약성 있는 Express 버전을 사용하고 있지 않은지 확인하십시오. 취약성 있는 Express 버전을 사용하고 있는 경우에는 안정적인 릴리스 중 하나로 업데이트해야 하며, 가능하면 최신 버전으로 업데이트하는 것이 좋습니다.
-
-## TLS 사용
-
-앱이 민감한 데이터를 다루거나 전송하는 경우에는 [전송 계층 보안](https://en.wikipedia.org/wiki/Transport_Layer_Security)(TLS)을 사용하여 연결 및 데이터를 보호하십시오. 이 기술은 데이터를 클라이언트로부터 서버로 전송하기 전에 데이터를 암호화하며, 따라서 몇 가지 일반적인(그리고 쉬운) 해킹을 방지합니다. Ajax 및 POST 요청은 브라우저에서 분명하게 보이지 않고 "숨겨진" 것처럼 보일 수도 있지만, 이러한 요청의 트래픽은 [패킷 가로채기](https://en.wikipedia.org/wiki/Packet_analyzer) 및 [중간자 공격](https://en.wikipedia.org/wiki/Man-in-the-middle_attack)에 취약합니다.
-
-여러분은 SSL(Secure Socket Layer) 암호화에 익숙할 것입니다. [TLS는 단순히 SSL이 다음 단계로 발전된 형태입니다](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). 즉, 이전에 SSL을 사용했다면 TLS로의 업그레이드를 고려해야 합니다. 일반적으로 TLS의 처리를 위해서는 Nginx를 권장합니다. Nginx(및 기타 서버)에서 TLS를 구성하는 방법에 대한 좋은 참조 자료를 확인하려면 [Recommended Server Configurations(Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations)를 참조하십시오.
-
-또한 무료 TLS 인증서를 얻기 위한 편리한 도구 중 하나는 [Internet Security Research Group(ISRG)](https://letsencrypt.org/isrg/)이 제공하는 무료의 자동 개방형 인증 기관(CA)인 [Let's Encrypt](https://letsencrypt.org/about/)입니다.
-
-## 사용자 입력을 신뢰하지 않습니다
-
-웹 애플리케이션에서 가장 중요한 보안 요구 사항 중 하나는 적절한 사용자 입력 검증 및 처리를 수행하는 것입니다. 이는 여러 형태로 나타나며, 이 문서에서는 모든 경우를 다루지 않습니다.
-궁극적으로 애플리케이션이 수용하는 사용자 입력 유형을 검증하고 올바르게 처리하는 책임은 개발자에게 있습니다.
-
-### 오픈 리다이렉트 방지
-
-잠재적으로 위험한 사용자 입력의 예로 오픈 리다이렉트가 있습니다. 이는 애플리케이션이 URL을 사용자 입력으로 받아들여 (예: `?url=https://example.com` 쿼리 문자열)  
-`res.redirect`를 사용해 `location` 헤더를 설정하고 3xx 상태 코드를 반환하는 경우입니다.
-
-애플리케이션은 악성 링크(예: 피싱 사이트) 로 사용자를 유도하는 위험을 방지하기 위해, 들어오는 URL에 대해 리다이렉트를 허용하는지 반드시 검증해야 합니다.
-
-아래는 `res.redirect` 또는 `res.location`을 사용하기 전에 URL을 검증하는 예시입니다.
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Helmet 사용
-
-[Helmet](https://www.npmjs.com/package/helmet)을 이용하면 HTTP 헤더를 적절히 설정하여 몇 가지 잘 알려진 웹 취약성으로부터 앱을 보호할 수 있습니다.
-
-Helmet은 보안 관련 HTTP 응답 헤더를 설정하는 미들웨어 함수입니다. Helmet은 기본적으로 다음 헤더들을 설정합니다.
-
-- `Content-Security-Policy`: 페이지에서 허용되는 콘텐츠를 강력하게 지정하여 여러 공격을 완화합니다.
-- `Cross-Origin-Opener-Policy`: 페이지의 프로세스 격리를 돕습니다.
-- `Cross-Origin-Resource-Policy`: 다른 출처가 리소스를 크로스 오리진으로 로드하는 것을 차단합니다.
-- `Origin-Agent-Cluster`: 프로세스 격리를 출처(origin) 단위로 변경합니다.
-- `Referrer-Policy`: [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) 헤더를 제어합니다.
-- `Strict-Transport-Security`: 브라우저에 HTTPS를 우선 사용하도록 지시합니다.
-- `X-Content-Type-Options`: [MIME 스니핑](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)을 방지합니다.
-- `X-DNS-Prefetch-Control`: DNS 프리페칭 제어를 담당합니다.
-- `X-Download-Options`: 다운로드를 저장하도록 강제합니다 (인터넷 익스플로러 전용)
-- `X-Frame-Options`: [클릭재킹](https://en.wikipedia.org/wiki/Clickjacking) 공격을 완화하기 위한 레거시 헤더입니다.
-- `X-Permitted-Cross-Domain-Policies`: Acrobat과 같은 Adobe 제품의 크로스 도메인 동작을 제어합니다.
-- `X-Powered-By`: 웹 서버 정보에 관한 헤더입니다. 해당 헤더는 단순 공격에 악용될 수 있어 제거되었습니다
-- `X-XSS-Protection`: [XSS 공격](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting)을 완화하려 했던 레거시 헤더이나, 오히려 문제를 악화시키기 때문에 Helmet에서는 비활성화합니다
-
-각 헤더는 필요에 따라 설정하거나 비활성화할 수 있습니다. 자세한 내용은 [Helmet 공식 문서를][helmet] 참고하시기 바랍니다.
-
-다른 모든 모듈처럼 Helmet은 다음과 같이 설치할 수 있습니다.
-
-```bash
-$ npm install helmet
-```
-
-코드에서 Helmet을 사용하는 방법은 문서를 참고하세요
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## 지문 인식(Fingerprinting) 감소
-
-서버가 사용하는 소프트웨어를 공격자가 식별하는 능력을 줄이는 것은 추가적인 보안 계층을 제공할 수 있습니다. 이를 ‘지문 인식(fingerprinting)’이라 합니다. 비록 지문 인식 자체가 직접적인 보안 문제는 아니지만, 이를 줄임으로써 전체적인 보안 수준이 향상됩니다.
-서버 소프트웨어는 특정 요청에 대한 응답 방식, 예를 들어 HTTP 응답 헤더 등에서 특이점을 통해 식별될 수 있습니다.
-
-따라서 우수 사례는 다음과 같이 `app.disable()` 메소드를 이용해 이 헤더를 끄는 것입니다.
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-`X-Powered-By` 헤더를 비활성화하는 것만으로는 숙련된 공격자가 Express를 사용하는 앱임을 완전히 차단할 수 없습니다. 이는 단순한 공격 시도를 막는 데는 도움이 되지만, 앱이 Express로 작동함을 식별할 수 있는 다른 방법도 존재합니다.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express는 자체 포맷의 "404 Not Found" 메시지와 포맷터 오류 응답 메시지도 전송합니다. 이러한 응답은  
-[사용자 정의 404 핸들러 추가](/en/starter/faq.html#how-do-i-handle-404-responses) 및  
-[사용자 정의 에러 핸들러 작성](/en/guide/error-handling.html#writing-error-handlers)을 통해 변경할 수 있습니다.
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## 쿠키를 안전하게 사용
-
-쿠키로 인해 앱이 악용에 노출되지 않도록 하기 위해 기본 세션 쿠키 이름을 사용하지 말고 쿠키 보안 옵션을 적절히 설정하십시오.
-
-두 개의 기본 미들웨어 쿠키 세션 모듈은 다음과 같습니다.
-
-- [express-session](https://www.npmjs.com/package/express-session)(Express 3.x에서 기본 제공되는 `express.session` 미들웨어 대체).
-- [cookie-session](https://www.npmjs.com/package/cookie-session)(Express 3.x에서 기본 제공되는 `express.cookieSession` 미들웨어 대체).
-
-이 두 모듈의 주요 차이점은 쿠키 세션 데이터를 저장하는 방식입니다. [express-session](https://www.npmjs.com/package/express-session) 미들웨어는 세션 데이터를 서버에 저장하며, 쿠키 자체에는 세션 데이터가 아니라 세션 ID만 저장됩니다. 기본적으로 express-session은 인메모리 스토리지를 이용하며, 프로덕션 환경용으로 설계되지 않았습니다. 프로덕션 환경에서는 확장 가능한 session-store를 설정해야 합니다. [호환 가능한 세션 스토어](https://github.com/expressjs/session#compatible-session-stores)의 목록을 참조하십시오.
-
-이와 반대로 [cookie-session](https://www.npmjs.com/package/cookie-session) 미들웨어는 쿠키 기반의 스토리지를 구현하며, 하나의 세션 키가 아니라 세션 전체를 쿠키에 직렬화합니다. cookie-session은 세션 데이터의 크기가 상대적으로 작으며 (오브젝트가 아닌) 원시 값으로 쉽게 인코딩 가능할 때에만 사용하십시오. 브라우저는 하나의 쿠키당 4,096바이트 이상을 지원하도록 되어 있지만, 한계를 초과하지 않도록 보장하려면 하나의 도메인당 4,093바이트의 크기를 초과하지 마십시오. 또한, 클라이언트에서 쿠키 데이터를 볼 수 있으므로, 쿠키 데이터를 안전하게 또는 모호하게 유지해야 할 이유가 있는 경우에는 express-session을 선택하는 것이 더 나을 수 있습니다.
-
-### 기본 세션 쿠키 이름을 사용하지 않음
-
-기본 세션 쿠키 이름을 사용하면 앱을 공격에 노출시킬 수 있습니다. 이로 인해 제기되는 보안 문제는 `X-Powered-By`와 유사하며, 잠재적인 공격자는 이를 이용해 서버의 지문을 채취한 후 이에 따라 공격 대상을 설정할 수 있습니다.
-
-다음에는 [cookie-session](https://www.npmjs.com/package/cookie-session) 미들웨어를 사용한 예가 표시되어 있습니다.
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### 쿠키 보안 옵션 설정
-
-다음과 같은 쿠키 옵션을 설정하여 보안을 강화하십시오.
-
-- `secure` - 브라우저가 HTTPS를 통해서만 쿠키를 전송하도록 합니다.
-- `httpOnly` - 쿠키가 클라이언트 JavaScript가 아닌 HTTP(S)를 통해서만 전송되도록 하며, 이를 통해 XSS(Cross-site scripting) 공격으로부터 보호할 수 있습니다.
-- `domain` - 쿠키의 도메인을 표시합니다. URL이 요청되고 있는 서버의 도메인에 대해 비교할 때 사용하십시오. 두 도메인이 일치하는 경우에는 그 다음으로 경로 속성을 확인하십시오.
-- `path` - 쿠키의 경로를 표시합니다. 요청 경로에 대해 비교할 때 사용하십시오. 이 경로와 도메인이 일치하는 경우에는 요청되고 있는 쿠키를 전송하십시오.
-- `expires` - 지속적 쿠키에 대한 만기 날짜를 설정하는 데 사용됩니다.
-
-[noCache](https://github.com/helmetjs/nocache)는 `Cache-Control` 및 Pragma 헤더를 설정하여 클라이언트 측에서 캐싱을 사용하지 않도록 합니다.
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## 인증에 대한 무차별 대입 공격(Brute-force) 방지
-
-로그인 엔드포인트를 보호하여 개인정보를 안전하게 유지해야 합니다.
-
-간단하면서도 효과적인 방법 중 하나는 다음 두 가지 기준으로 인증 시도를 차단하는 것입니다:
-
-1. .
-2. IP 주소로부터의 오랜 시간 동안의 실패 시도 횟수입니다. 예를 들어, 하루 동안 100번의 실패 시도를 한 경우 해당 IP 주소를 차단할 수 있습니다.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) 패키지는 이 기술을 쉽고 빠르게 구현할 수 있는 도구들을 제공합니다. [문서에서 brute-force 방지 예제](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)를 참고할 수 있습니다.
-
-## 종속 항목이 안전한지 확인
-
-npm을 이용해 애플리케이션의 종속 항목을 관리하는 것은 강력하면서도 편리합니다. 그러나 사용 중인 패키지에는 애플리케이션에 영향을 미칠 수 있는 치명적인 보안 취약성이 포함되어 있을 수도 있습니다. 앱의 보안성은 종속 항목 내의 "가장 약한 링크"의 보안성에 따라 결정됩니다.
-
-npm@6부터 npm은 자동으로 모든 설치 요청을 검사합니다. 또한 `npm audit`을 이용해 여러분의 의존성 트리를 검사할 수 있습니다.
-
-```bash
-$ npm audit
-```
-
-더 강한 보안을 원한다면, [Snyk](https://snyk.io/)를 사용하십시오.
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github 통합](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. 다음과 같이 CLI을 설치합니다:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-아래 명령으로 애플리케이션의 취약점을 검사합니다.
-
-```bash
-$ snyk test
-```
-
-### 그 외의 알려져 있는 취약점 회피
-
-Express에, 또는 앱에 사용되는 다른 모듈에 영향을 미칠 수 있는 [Node Security Project](https://npmjs.com/advisories)의 보안 권고문에 항상 주의를 기울이십시오. 일반적으로 Node Security Project는 Node의 보안과 관련된 지식 및 도구에 대한 훌륭한 자원입니다.
-
-마지막으로, 다른 모든 웹 앱과 마찬가지로 Express 앱은 다양한 웹 기반 공격에 취약할 수 있습니다. 알려져 있는 [웹 취약성](https://www.owasp.org/www-project-top-ten/)을 숙지한 후 이러한 취약성을 피하기 위한 예방 조치를 취하십시오.
-
-## 추가적인 고려사항
-
-유용한 [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/)에서 발췌한 몇 가지 추가적인 권장사항은 다음과 같습니다. 아래의 권장사항에 대한 모든 상세 정보를 확인하려면 해당 블로그 게시물을 참조하십시오.
-
-- 항상 사용자 입력을 필터링하고 사용자 입력에서 민감한 데이터를 제거하여 XSS(Cross-site scripting) 및 명령 인젝션 공격으로부터 보호하십시오.
-- 매개변수화된 조회 또는 준비된 명령문을 이용하여 SQL 인젝션 공격으로부터 방어하십시오.
-- 오픈 소스 방식의 [sqlmap](http://sqlmap.org/) 도구를 이용하여 앱 내의 SQL 인젝션 취약성을 발견하십시오.
-- [nmap](https://nmap.org/) 및 [sslyze](https://github.com/nabla-c0d3/sslyze) 도구를 이용하여 SSL 암호, 키 및 재협상의 구성, 그리고 인증서의 유효성을 테스트하십시오.
-- [safe-regex](https://www.npmjs.com/package/safe-regex)를 이용하여 정규식이 [정규식 서비스 거부](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) 공격을 쉽게 받지 않도록 하십시오.
-
-[helmet]: https://helmetjs.github.io/
\ No newline at end of file
diff --git a/ko/advanced/developing-template-engines.md b/ko/advanced/developing-template-engines.md
deleted file mode 100644
index a55dcfa916..0000000000
--- a/ko/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: Express용 템플릿 엔진 개발
-description: App.engine()을 사용하여 Express.js에서 사용자 정의 템플릿 엔진을 개발하는 방법을 학습합니다. 직접 템플릿 렌더링 로직을 생성하고 통합하는 예제를 함께 제공합니다.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Express용 템플릿 엔진 개발
-
-`app.engine(ext, callback)` 메소드를 사용하면 자신만의 템플릿 엔진을 작성할 수 있습니다. `ext`는 파일 확장자를 나타내며, `callback`은 파일의 위치, 옵션 오브젝트 및 콜백 함수 등의 항목을 매개변수로 수락하는 템플릿 엔진 함수입니다.
-
-다음의 코드는 `.ntl` 파일을 렌더링하기 위한 매우 간단한 템플릿 엔진을 구현하는 예입니다.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-앱은 이제 `.ntl` 파일을 렌더링할 수 있습니다. 다음의 내용이 입력된 `index.ntl`이라는 이름의 파일을 `views` 디렉토리에 작성하십시오.
-
-```pug
-#title#
-#message#
-```
-
-이후 앱에 다음과 같은 라우트를 작성하십시오.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-홈 페이지에 대한 요청을 실행할 때 `index.ntl`은 HTML로 렌더링됩니다.
\ No newline at end of file
diff --git a/ko/advanced/healthcheck-graceful-shutdown.md b/ko/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 42045b8e09..0000000000
--- a/ko/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-layout: page
-title: 상태 검사와 우아한 종료
-description: Express 애플리케이션에서 헬스 체크와 그레이스풀 셧다운(Graceful Shutdown)을 구현하는 방법을 학습합니다. 이 기능은 애플리케이션의 신뢰성을 향상시키고, 배포를 원활하게 관리하며, Kubernetes와 같은 로드 밸런서와의 통합을 지원합니다.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# 상태 검사와 우아한 종료
-
-## 정상 종료
-
-애플리케이션의 새 버전을 배포할 때, 이전 버전을 교체해야 합니다. 여러분이 사용하는 프로세스 매니저 는 애플리케어션에 SIGTERM 신호를 보내 종료를 통보할 것입니다. 애플리케이션이 신호를 받으면, 신규 요청을 받는걸 중단하고, 진행중인 요청을 끝내고, DB 연결이나 파일 사용을 포함한 사용한 리소스를 정리할 것입니다.
-
-### Example
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-로드 밸런서는 헬스 체크를 통해 애플리케이션 인스턴스가 정상적으로 작동 중이며 요청을 수락할 수 있는지 판단합니다. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-로드 밸런서는 상태 확인을 애플리케이션이 장상 작동하고 요청을 받을 수 있는지 판단하는데 사용합니다.
-
-- `liveness`: 언제 컨테이너를 재시작할지 결정합니다.
-- `readiness`: 컨테이너가 트래픽을 받기 시작할 준비가 되었는지 결정합니다. 컨테이너가 준비되지 않았다면, 서비스 로드 밸런서들에게서 제거됩니다.
\ No newline at end of file
diff --git a/ko/advanced/security-updates.md b/ko/advanced/security-updates.md
deleted file mode 100644
index a5ca08ba4e..0000000000
--- a/ko/advanced/security-updates.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-layout: page
-title: Express 보안 업데이트
-description: |-
-  Express.js의 최신 보안 업데이트와 패치 사항을 확인합니다. 
-  각 버전에 대한 상세한 취약점 목록을 포함하여, 애플리케이션의 보안을 유지하는 데 도움이 됩니다.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# 보안 업데이트
-
-<div class="doc-box doc-notice" markdown="1">
-Node.js 취약성은 Express에 직접 영향을 미칩니다. 따라서 [Node.js 취약성을 항상 주시해야 하며](https://nodejs.org
-/en/blog/vulnerability/), 반드시 안정적인 최신 버전의 Node.js를 사용해야 합니다.
-</div>
-
-아래의 목록에는 지정된 버전 업데이트에서 수정된 Express 취약성이 열거되어 있습니다.
-
-{% capture security-policy %} Express에서 보안 취약점을 발견했다고 생각되면, [보안 정책 및 절차](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures)를 참고해 주시기 바랍니다.
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - `path-to-regexp` 모듈이 [보안 취약점](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w)을 해결하기 위해 업데이트되었습니다.
-- 4.21.1
-  - `cookie` 모듈이 [보안 취약점](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x)을 해결하기 위해 업데이트되었습니다. 이 취약점은 `res.cookie`를 사용하는 애플리케이션에 영향을 줄 수 있습니다.
-- 4.20.0
-  - `res.redirect`에서 발생할 수 있는 XSS 취약점이 수정되었습니다 ([권고문](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - `serve-static` 모듈이 [보안 취약점](https://github.com/advisories/GHSA-cm22-4g7w-348p)을 해결하기 위해 업데이트되었습니다.
-  - `send` 모듈이 [보안 취약점](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg)을 해결하기 위해 업데이트되었습니다.
-  - `path-to-regexp` 모듈이 [보안 취약점](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)을 해결하기 위해 추가로 업데이트되었습니다.
-  - `body-parser` 모듈이 [보안 취약점](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7)을 해결하기 위해 업데이트되었습니다 이 취약점은 URL 인코딩이 활성화된 경우 애플리케이션에 영향을 줄 수 있습니다.
-- 4.19.0, 4.19.1
-  - `res.location` 및 `res.redirect`에서 발생할 수 있는 오픈 리디렉션(Open Redirect) 취약점이 수정되었습니다 ([권고문](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc) [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041))
-- 4.17.3
-  - `qs` 모듈이 [보안 취약점](https://github.com/advisories/GHSA-hrpp-h998-j3pp)을 해결하기 위해 업데이트되었습니다. 이 취약점은 `req.query`, `req.body`, `req.param` API 사용 시 애플리케이션에 영향을 줄 수 있습니다.
-- 4.16.0
-  - 의존성 `forwarded`가 [발견된 취약점](https://npmjs.com/advisories/527)에 따라 업데이트되었습니다. `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`을 사용하는 애플리케이션에 영향을 끼칠 수 있습니다.
-  - 의존성 `mime`이 [발견된 취약점](https://npmjs.com/advisories/535)에 따라 업데이트되었으나, Express에 영향을 끼치지는 않습니다.
-  - 의존성 `send`가 [Node.js 8.5.0의 취약점](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/)에 대응하기 위해 업데이트되었습니다. Node.js 버전 8.5.0에서 실행되는 Express에만 영향을 끼칩니다.
-- 4.15.5
-  - 의존성 `debug`가 [발견된 취약점](https://snyk.io/vuln/npm:debug:20170905)에 따라 업데이트되었으나, Express에 영향을 끼치지는 않습니다.
-  - 의존성 `fresh`가 [발견된 취약점](https://npmjs.com/advisories/526)에 따라 업데이트되었습니다. `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`를 사용하고 있는 애플리케이션에 영향을 끼칩니다.
-- 4.15.3
-  - 의존성 `ms`가 [발견된 취약점](https://snyk.io/vuln/npm:ms:20170412)에 따라 업데이트되었습니다. 애플리케이션이 `express.static`, `res.sendfile`, `res.sendFile`의 `maxAge` 옵션에 Untrusted 문자열을 입력받고 있으면 영향을 끼칠 수 있습니다.
-- 4.15.2
-  - 의존성 `qs`가 [발견된 취약점](https://snyk.io/vuln/npm:qs:20170213)에 따라 업데이트되었으나, Express에 영향을 끼치지는 않습니다. 4.15.2로 업데이트하는 것을 권장하나, 취약점을 막는 업데이트는 아닙니다..
-- 4.11.1
-  - `express.static`, `res.sendfile` 및 `res.sendFile`의 루트 경로 노출 취약성을 수정했습니다.
-- 4.10.7
-  - `express.static`의 개방된 경로 재지정 취약성을 수정했습니다([보안 권고문](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 4.8.8
-  - `express.static`의 디렉토리 조회 취약성을 수정했습니다([보안 권고문](http://npmjs.com/advisories/32), [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-- 4.8.4
-  - Node.js 0.10 이용 시, 특정한 상황에서 `fd` 누수가 발생할 수 있으며, 이는 `express.static` 및 `res.sendfile`에 영향을 미칩니다. 악성 요청은 `fd` 누수를 발생시킬 수 있으며, 결국 `EMFILE` 오류와 서버 무응답을 초래할 수 있습니다.
-- 4.8.0
-  - 조회 문자열에서 극단적으로 높은 인덱스를 갖는 스파스 배열은 프로세스가 메모리 부족을 발생시키고 서버에서 충돌이 발생하도록 하는 원인이 될 수 있습니다.
-  - 극단적인 수준으로 중첩된 조회 문자열 오브젝트는 프로세스가 서버를 차단하고 일시적으로 서버를 무응답 상태로 만드는 원인이 될 수 있습니다.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x은 더 이상 유지보수되지 않습니다.**
-
-3.x의 알려진 또는 알려지지 않은 보안 및 성능 문제는 마지막 업데이트(2015년 8월 1일) 이후로 처리되지 않고 있습니다. 최신 버전의 Express를 사용할 것을 강력히 권장합니다.
-
-버전 3.x 이상으로 업그레이드할 수 없는 경우, [상업적 지원 옵션](/{{ page.lang }}/support#commercial-support-options)을 고려해주시기 바랍니다.
-
-  </div>
-
-- 3.19.1
-  - `express.static`, `res.sendfile` 및 `res.sendFile`의 루트 경로 노출 취약성을 수정했습니다.
-- 3.19.0
-  - `express.static`의 개방된 경로 재지정 취약성을 수정했습니다([보안 권고문](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 3.16.10
-  - `express.static`의 디렉토리 조회 취약성을 수정했습니다.
-- 3.16.6
-  - Node.js 0.10 이용 시, 특정한 상황에서 `fd` 누수가 발생할 수 있으며, 이는 `express.static` 및 `res.sendfile`에 영향을 미칩니다. 악성 요청은 `fd` 누수를 발생시킬 수 있으며, 결국 `EMFILE` 오류와 서버 무응답을 초래할 수 있습니다.
-- 3.16.0
-  - 조회 문자열에서 극단적으로 높은 인덱스를 갖는 스파스 배열은 프로세스가 메모리 부족을 발생시키고 서버에서 충돌이 발생하도록 하는 원인이 될 수 있습니다.
-  - 극단적인 수준으로 중첩된 조회 문자열 오브젝트는 프로세스가 서버를 차단하고 일시적으로 서버를 무응답 상태로 만드는 원인이 될 수 있습니다.
-- 3.3.0
-  - 지원되지 않는 메소드 대체 시도의 404 응답은 XSS(Cross-site scripting) 공격을 받기 쉬웠습니다.
\ No newline at end of file
diff --git a/ko/api.md b/ko/api.md
deleted file mode 100644
index 3636ec88d4..0000000000
--- a/ko/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 참조
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/ko/changelog/4x.md b/ko/changelog/4x.md
deleted file mode 100644
index 3704618c53..0000000000
--- a/ko/changelog/4x.md
+++ /dev/null
@@ -1,341 +0,0 @@
----
-layout: page
-title: Express 4.x 업데이트 기록
-menu: changelog
-description: Stay updated with the release change log for Express.js 4.x, detailing
-  new features, bug fixes, and important changes across versions.
-sitemap: false
----
-
-# 업데이트 기록
-
-## 4.17.1 - 출시일: 2019-05-25
-{: id="4.17.1"}
-
-4.17.1 패치에서 하나의 버그가 고쳐졌습니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  `res.status()`가 존재하는 Express 4 애플리케이션에서 재귀를 일으키기 때문에 롤백되었습니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4171--2019-05-25).
-
-## 4.17.0 - 출시일: 2019-05-16
-{: id="4.17.0"}
-
-4.17.0 마이너 릴리즈에서는 버그를 고치고 몇몇 새 기능을 추가했습니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  The `express.raw()` and `express.text()` middleware have been added to provide request body parsing for more raw request payloads. This uses the [expressjs/body-parser module](https://www.npmjs.com/package/body-parser) module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `res.cookie()` API가 이제 `sameSite` 옵션을 위해 `"none"` 값을 지원합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `"trust proxy"` 설정이 활성화되어 있을 때, `req.hostname`가 이제 여러개의 `X-Forwarded-For` 헤더가 요청에 있는 것을 허용합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  이 버전부터 Express가 Node.js 10.x 버전과 12.x 버전을 지원합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `res.sendFile()` API가 이제 비 문자열이 `path` 인수가 되었을 때 더 빠르고 쉽게 이해할 수 있는 에러를 제공합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `res.status()` API가 이제 `null`이나 `undefined`가 인수가 되었을 때 더 빠르고 쉽게 이해할 수 있는 에러를 제공합니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4170--2019-05-16).
-
-## 4.16.4 - 출시일: 2018-10-10
-{: id="4.16.4"}
-
-4.16.4 패치는 여러 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  `res.sendfile`에서 로깅될 수 있는 `"Request aborted"` 오류를 수정되었습니다.
-  </li>
-</ul>
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4164--2018-10-10).
-
-## 4.16.3 - 출시일: 2018-03-12
-{: id="4.16.3"}
-
-4.16.3 패치는 여러 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  `res.location` 메소드나 `res.redirect` 메소드에서 url 끝에 있는 `%` 문자가 `%25`로 인코딩되지 않는 문제를 수정했습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  빈 `req.url` 값이 기본 404 에러 핸들링에서 오류를 발생시키는 문제를 수정했습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `express.static`의 응답이 이제 제대로 `</html>`을 포함합니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4163--2018-03-12).
-
-## 4.16.2 - 출시일: 2017-10-09
-{: id="4.16.2"}
-
-4.16.2 패치는 버그 픽스를 위한 롤백을 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  `res.send` 메소드에서 `Buffer`가 입력되고, `ETag` 헤더가 이미 응답에 설정되었을 때 발생하는 `TypeError`를 수정했습니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4162--2017-10-09).
-
-## 4.16.1 - 출시일: 2017-09-29
-{: id="4.16.1"}
-
-4.16.1 패치는 버그 픽스를 위한 롤백을 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  `express.static`을 사용하는 일부 유저에게 형향을 줄 수 있는 엣지 케이스 시나리오 회귀를 고치기 위해 [pillarjs/send module](https://www.npmjs.com/package/send를 업데이트 했습니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4161--2017-09-29).
-
-## 4.16.0 - 출시일: 2017-09-28
-{: id="4.16.0"}
-
-4.16.0 마이너 릴리즈는 보안 업데이트, 버그 픽스, 최적화, 그리고 새로운 기능을 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  [jshttp/forwarded 모듈](https://www.npmjs.com/package/forwarded)에서 [발견된 취약점](https://npmjs.com/advisories/527)에 따라 업데이트되었습니다. `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`을 사용하는 애플리케이션에 영향을 끼칠 수 있습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [취약점](https://npmjs.com/advisories/535)을 해결하기 위해 [pillarjs/send 모듈](https://www.npmjs.com/package/send)의 의존성 모듈로 사용된 `mime`를 업데이트했습니다. `res.type()`에서 untrusted string을 사용하는 애플리케이션에 영향을 끼칠 수 있습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [pillarjs/send 모듈](https://www.npmjs.com/package/send)가 Node.js 8.5.0 [취약점](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/)에 대응하여 패치를 추가했습니다. Express.js의 이전 버전을 Node.js 8.5.0 (이 특정한 버전만 해당합니다)에서 사용하는 경우, `express.static`, `res.sendfile`과 `res.sendFile` API가 취약해집니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  이 버전부터 Node.js 8.x.를 지원합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  새로운 설정, `"json escape"`는 `res.json()`, `res.jsonp()`가 문자를 escape 할 수 있도록 하고, `res.send()`의 응답을 클라이언트가 `Content-Type`에 따라 인식하는게 아니라 HTML로 인식하도록 합니다. 이건 Express 앱을 XSS 기반의 공격으로부터 지킬 수 있도록 도와줍니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`res.download()` 메소드](/{{ page.lang }}/4x/api.html#res.download)가 이제 `options` 오브젝트를 받습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `express.json()` 과 `express.urlencoded()` 미들웨어가 특수한 바디 파싱을 지원하기 위해 추가되었습니다. 이 기능은 [expressjs/body-parser 모듈](https://www.npmjs.com/package/body-parser)을 기반으로 돌아갑니다. 현재 `body-parser` 모듈을 사용하고 있는 앱들은 빌트인 파서로 바꿀 수 있습니다. 
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`express.static()` 미들웨어](/{{ page.lang }}/4x/api.html#express.static)와 [`res.sendFile()` 메소드](/{{ page.lang }}/4x/api.html#res.sendFile)가 이제 `Cache-Control`에서 `immutable` directive를 설정하는 것을 지원합니다. 적절한 `maxAge`와 함께 이 헤더를 설정함을 통해 지원되는 브라우저에서 파일이 아직 클라이언트 캐시에 남아 있어도 서버로 요청을 보내는 것을 방지할 수 있습니다. 
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [pillarjs/send 모듈](https://www.npmjs.com/package/send)이 업데이트되어 더 많은 MIME 타입 리스트를 제공합니다. 이를 통해 `Content-Type`에 더 많은 파일을 지원할 수 있습니다. 70개의 새 파일 확장자를 지원합니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4160--2017-09-28).
-
-## 4.15.5 - 출시일: 2017-09-24
-{: id="4.15.5"}
-
-4.15.5 패치는 보안 업데이트, 최적화, 그리고 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  [취약점](https://snyk.io/vuln/npm:debug:20170905)이 해결된 [debug 모듈](https://www.npmjs.com/package/debug)로 업데이트했습니다. Express에 영향을 끼치지는 않습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [취약점](https://npmjs.com/advisories/526)이 해결된 [jshttp/fresh 모듈](https://www.npmjs.com/package/fresh)로 업데이트했습니다. 다음과 같은 API에 영향을 끼칩니다. `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [jshttp/fresh 모듈](https://www.npmjs.com/package/fresh)의 업데이트는 유효하지 않은 날짜로 이루어진 수정된 헤더 처리를 수정하고, `If-None-Match`와 같은 조건부 헤더를 파싱하는 것을 빠르게 합니다.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4155--2017-09-24).
-
-## 4.15.4 - 출시일: 2017-08-06
-{: id="4.15.4"}
-
-4.15.4 패치는 마이너 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  인증서 조건에서 관리 중인 `"신뢰할 수 있는 프록시"` 값이 배열이 되던 문제 수정
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4154--2017-08-06).
-
-## 4.15.3 - 출시일: 2017-05-16
-{: id="4.15.3"}
-
-4.15.3 패치는 보안 업데이트와 마이너 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  Update a dependency of the [pillarjs/send module](https://www.npmjs.com/package/send) to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-    
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  `res.set`으로 `Content-Type`에 charset을 추가할 수 없는 오류를 수정했습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  
-  Fix missing `</html>` in HTML document.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4153--2017-05-16).
-
-## 4.15.2 - 출시일: 2017-03-06
-{: id="4.15.2"}
-
-4.15.2 패치는 마이너 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  Fix regression parsing keys starting with `[` in the extended  (default) query parser.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4152--2017-03-06).
-
-## 4.15.1 - 출시일: 2017-03-05
-{: id="4.15.1"}
-
-4.15.1 패치는 마이너 버그 픽스를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  Fix compatibility issue when using the datejs 1.x library where the [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) would incorrectly respond with 412 Precondition Failed.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4151--2017-03-05).
-
-## 4.15.0 - 출시일: 2017-03-01
-{: id="4.15.0"}
-
-4.15.0 마이너 릴리즈는 버그 픽스, 최적화, 마이너 기능 추가를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  이 버전부터 Node.js 7.x.를 합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  The [`express.static()` middleware](/{{ page.lang }}/4x/api.html#express.static) and [`res.sendFile()` method](/{{ page.lang }}/4x/api.html#res.sendFile) now support the `If-Match` and `If-Unmodified-Since` request headers.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  Update to [jshttp/etag module](https://www.npmjs.com/package/etag) to generate the default ETags for responses which work when Node.js has [FIPS-compliant crypto enabled](https://nodejs.org/dist/latest/docs/api/cli.html#cli_enable_fips).
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  Various auto-generated HTML responses like the default not found and error handlers will respond with complete HTML 5 documents and additional security headers.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4150--2017-03-01).
-
-## 4.14.1 - 출시일: 2017-01-28
-{: id="4.14.1"}
-
-4.14.1 패치는 버그 픽스와 최적화를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  Update to [pillarjs/finalhandler module](https://www.npmjs.com/package/finalhandler) fixes an exception when Express handles an `Error` object which has a `headers` property that is not an object.
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4141--2017-01-28).
-
-## 4.14.0 - 출시일: 2016-06-16
-{: id="4.14.0"}
-
-4.14.0 마이너 릴리즈는 버그 픽스, 보안 업데이트, 최적화, 마이너 기능 추가를 포함합니다.
-
-<ul>
-  <li markdown="1" class="changelog-item">
-  이 버전부터 Node.js 6.x.를 지원합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  Update to [jshttp/negotiator module](https://www.npmjs.com/package/negotiator) fixes a [regular expression denial of service vulnerability](https://npmjs.com/advisories/106).
-  [jshttp/negotiator 모듈](https://www.npmjs.com/package/negotiator)을 업데이트해서 [정규 표현식 서비스 거부 취약점](https://npmjs.com/advisories/106)을 수정했습니다..
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`res.sendFile()` 메소드](/{{ page.lang }}/4x/api.html#res.sendFile)가 이제 다음의 2가지 옵션을 지원합니다. `acceptRanges`, `cacheControl`
-
-  - `acceptRanges` (기본값: `true`): ranged requests를 받아 들이는지의 여부를 켜고 끕니다. 꺼져있을 때, 응답은 `accept-Ranges` 헤더를 보내지 않으며, `Range` 요청 헤더를 무시합니다.
-
-  - `cacheControl`, (기본값: `true`):`Cache-Control` 헤더를 켜고 끕니다. 이 헤더를 끄면 `maxAge` 옵션을 무시합니다.
-
-  - 또한 `res.sendFile`이 `Range` 헤더도 처리하고, 리다이렉션도 더 잘 하도록 업데이트 했습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`res.location()` 메소드](/{{ page.lang }}/4x/api.html#res.location) 와 [`res.redirect()` 메소드](/{{ page.lang }}/4x/api.html#res.redirect)가 URL 문자열이 인코딩되어있지 않다면 인코딩합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`res.json()` 메소드](/{{ page.lang }}/4x/api.html#res.json)와 [`res.jsonp()` 메소드](/{{ page.lang }}/4x/api.html#res.jsonp)의 일반적인 상황에서의 성능이 향상되었습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [jshttp/cookie 모듈](https://www.npmjs.com/package/cookie) (다른 향상점과 함께)이 업데이트되었으며, 이제 [`res.cookie()` 메소드](/{{ page.lang }}/4x/api.html#res.cookie)가 `sameSite` 옵션을 지원해서 여러분이 [SameSite 쿠키 옵션](https://tools.ietf.org/html/draft-west-first-party-cookies-07)을 지정할 수 있게 됩니다.  NOTE: 이 속성은 아직 완전히 표준화되지 않았습니다. 미래에 바뀔 수도 있고, 클라이언트가 무시할 수 있습니다.
-
-  `sameSite` 옵션으로 가능한 값:
-
-  - `true`: `SameSite` 속성을 `Strict`로 설정해 strict same site enforcement합니다.
-  - `false`: `SameSite` 속성을 설정하지 않습니다..
-  - `'lax'`, `SameSite` 속성을 `Lax`로 설정해 lax same site enforcement합니다..
-  - `'strict'`, `SameSite` 속성을 `Strict`로 설정해 strict same site enforcement합니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  윈도우에서 절대 경로 검사가 종종 부정확했던 문제를 수정했습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  프록시를 사용하는 IP 주소 결정이 굉장하게 향상되었습니다.
-  </li>
-
-  <li markdown="1" class="changelog-item">
-  [`req.range()` 메소드](/{{ page.lang }}/4x/api.html#req.range) 옵션 객체가 이제 `combine`을 지원합니다.(기본값: `false`) `true`로 설정하면, 오버랩핑과 인접 범위를 결합해서 헤더에서 설정한대로 리턴합니다.
-  
-  </li>
-</ul>
-
-모든 변경 내역 확인: [History.md](https://github.com/expressjs/express/blob/master/History.md#4140--2016-06-16).
diff --git a/ko/changelog/index.md b/ko/changelog/index.md
deleted file mode 100644
index b23705d091..0000000000
--- a/ko/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Express.js의 릴리스 변경 로그를 통해 새로운 기능, 버그 수정 사항, 그리고 각 버전별 주요 변경 사항을 최신 상태로 확인하세요.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/ko/guide/behind-proxies.md b/ko/guide/behind-proxies.md
deleted file mode 100644
index 872b248f1a..0000000000
--- a/ko/guide/behind-proxies.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-layout: page
-title: 프록시 환경에서 Express 사용
-description: Express.js 애플리케이션을 리버스 프록시 뒤에서 올바르게 작동하도록 설정하는 방법을 알아보십시오. 클라이언트 IP 주소를 처리하기 위해 `trust proxy` 설정을 사용하는 것을 포함합니다.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# 프록시 환경에서 Express 사용
-
-Express 앱이 리버스 프록시 뒤에서 실행될 때, 일부 Express API는 예상과 다른 값을 반환할 수 있습니다. 이를 조정하기 위해 `trust proxy` 애플리케이션 설정을 사용하여, Express API에서 리버스 프록시가 제공한 정보를 노출하도록 할 수 있습니다. 가장 흔한 문제는 클라이언트의 IP 주소를 반환하는 Express API가 리버스 프록시의 내부 IP 주소를 대신 보여주는 경우입니다.
-
-<div class="doc-box doc-info" markdown="1">
-`trust proxy` 설정을 구성할 때, 리버스 프록시의 정확한 구성 방식을 이해하는 것이 중요합니다. 이 설정은 요청에 포함된 값을 신뢰하게 만들기 때문에, Express의 설정이 리버스 프록시의 동작 방식과 일치해야 합니다.
-</div>
-
-프록시 뒤에서 Express 앱을 실행할 때는, ([app.set()](/{{ page.lang }}/4x/api.html#app.set)을 이용하여) 애플리케이션 변수 `trust proxy`를 다음 표에 나열된 값 중 하나로 설정하십시오.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>유형</th><th>값</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>부울</td>
-<td markdown="1">
-`true`인 경우, 클라이언트의 IP 주소는 `X-Forwarded-*` 내의 가장 왼쪽 입력 항목인 것으로 인식됩니다.
-
-`false`인 경우, 앱이 직접 인터넷에 연결되는 것으로 인식되며 클라이언트의 IP 주소는 `req.connection.remoteAddress`로부터 도출됩니다. 이 설정이 기본 설정입니다.
-
-<div class="doc-box doc-warn" markdown="1">`trust proxy`를 `true`로 설정할 경우, 마지막으로 신뢰할 수 있는 리버스 프록시가 다음의 HTTP 헤더들을 제거하거나 덮어쓰는지 반드시 확인해야 합니다: `X-Forwarded-For`, `X-Forwarded-Host`, `X-Forwarded-Proto`. 그렇지 않으면 클라이언트가 임의의 값을 제공하는 것이 가능해질 수 있습니다.</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-다음의 방법 중 하나로 IP 주소를 설정할 수 있습니다.
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-IP 주소 또는 서브넷이 지정되는 경우, 해당 IP 주소 또는 서브넷은 주소 결정 프로세스에서 제외되며, 신뢰할 수 있는 것으로 지정되지 않은 IP 주소 중 애플리케이션 서버에서 가장 가까운 IP 주소가 클라이언트의 IP 주소로 결정됩니다. 이 설정은 `req.socket.remoteAddress`가 신뢰된 주소인지 확인하는 방식으로 작동합니다. 신뢰된 경우, `X-Forwarded-For` 헤더에 있는 각 IP 주소를 오른쪽에서 왼쪽으로 검사하며, 처음으로 신뢰되지 않은 주소를 만날 때까지 확인합니다.
-
-</td>
-    </tr>
-    <tr>
-      <td>숫자</td>
-<td markdown="1">
-Express 애플리케이션으로부터 최대 `n` 홉(hop) 떨어진 위치에 있는 주소를 사용하게 됩니다.
- `req.socket.remoteAddress`는 첫 번째 홉이며, 그 외의 주소들은 `X-Forwarded-For` 헤더에서 오른쪽에서 왼쪽 방향으로 조회됩니다. `0` 값을 설정하면, 첫 번째로 신뢰되지 않은 주소는 `req.socket.remoteAddress`가 되며, 이는 리버스 프록시가 없는 상태를 의미합니다.
-
-<div class="doc-box doc-warn" markdown="1">이 설정을 사용할 때는 Express 애플리케이션까지 도달하는 경로가 하나 이상 존재하지 않도록, 즉 서로 다른 홉 수의 경로가 존재하지 않도록 주의해야 합니다. 그렇지 않으면 클라이언트가 설정된 홉 수보다 가까운 위치에서 접근할 수 있게 되어, 임의의 값을 제공하는 것이 가능해질 수 있습니다.</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-`trust proxy`를 활성화하면 다음과 같은 영향을 미칩니다:
-
-<ul>
-  <li markdown="1">[req.hostname](/{{ page.lang }}/api.html#req.hostname)의 값은 `X-Forwarded-Host` 헤더에 설정된 값으로부터 도출되며, 이 값은 클라이언트 또는 프록시에 의해 설정될 수 있습니다.
-  </li>
-  <li markdown="1">`https`인지, `http`인지, 또는 잘못된 이름인지의 여부를 앱에 알리기 위하여 역방향 프록시가 `X-Forwarded-Proto`를 설정할 수 있습니다. 이 값에는 [req.protocol](/{{ page.lang }}/api.html#req.protocol)이 반영됩니다.
-  </li>
-  <li markdown="1">[req.ip](/{{ page.lang }}/api.html#req.ip) 값 및 [req.ips](/{{ page.lang }}/api.html#req.ips) 값에는 `X-Forwarded-For`의 주소 목록이 입력됩니다.
-  </li>
-</ul>
-
-`trust proxy` 설정은 [proxy-addr](https://www.npmjs.com/package/proxy-addr) 패키지를 이용해 구현됩니다. 자세한 정보는 해당 문서를 참조하십시오.
diff --git a/ko/guide/database-integration.md b/ko/guide/database-integration.md
deleted file mode 100644
index 4f0d3c34c2..0000000000
--- a/ko/guide/database-integration.md
+++ /dev/null
@@ -1,506 +0,0 @@
----
-layout: page
-title: Express 데이터베이스 통합
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# 데이터베이스 통합
-
-데이터베이스를 Express 앱에 연결하는 기능을 추가하려면 앱에 포함된 데이터베이스를 위한 적절한 Node.js 드라이버를 로드해야 합니다. 이 문서에서는 Express 앱의 데이터베이스 시스템에 가장 널리 이용되고 있는 Node.js 모듈 중 다음과 같은 몇 개의 모듈을 추가 및 사용하는 방법을 설명합니다.
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-위의 데이터베이스 드라이버는 사용 가능한 여러 데이터베이스 드라이버 중 일부입니다. 다른 옵션을 확인하려면,
-[npm](https://www.npmjs.com/) 사이트에서 검색하십시오.
-</div>
-
-## Cassandra
-
-**모듈**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-**설치**
-
-### 설치
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Example
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**모듈**: [couchnode](https://github.com/couchbase/couchnode)
-
-### 설치
-
-```bash
-$ npm install couchbase
-```
-
-### Example
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**모듈**: [nano](https://github.com/dscape/nano)
-**설치**
-
-### 설치
-
-```bash
-$ npm install nano
-```
-
-### Example
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**모듈**: [levelup](https://github.com/rvagg/node-levelup)
-**설치**
-
-### 설치
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Example
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**모듈**: [mysql](https://github.com/felixge/node-mysql/)
-**설치**
-
-### 설치
-
-```bash
-$ npm install mysql
-```
-
-### Example
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**모듈**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-**설치**
-
-### 설치
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-MongoDB용 오브젝트 모델 드라이버가 필요한 경우에는 [Mongoose](https://github.com/LearnBoost/mongoose)를 확인하십시오.
-
-## Neo4j
-
-**모듈**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
-
-### 설치
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Example
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**모듈**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### 설치
-
-참고: [설치 전제 조건 참조](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Example
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**모듈**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-**설치**
-
-### 설치
-
-```bash
-$ npm install pg-promise
-```
-
-### Example
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**모듈**: [redis](https://github.com/mranney/node_redis)
-**설치**
-
-### 설치
-
-```bash
-$ npm install redis
-```
-
-### Example
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL 서버
-
-**모듈**: [tedious](https://github.com/tediousjs/tedious)
-
-### 설치
-
-```bash
-$ npm install tedious
-```
-
-### Example
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**모듈**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-**설치**
-
-### 설치
-
-```bash
-$ npm install sqlite3
-```
-
-### Example
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**모듈**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-**설치**
-
-### 설치
-
-```bash
-$ npm install elasticsearch
-```
-
-### Example
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/ko/guide/debugging.md b/ko/guide/debugging.md
deleted file mode 100644
index 4d258d491f..0000000000
--- a/ko/guide/debugging.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-layout: page
-title: Express 디버깅
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Express 디버깅
-
-Express에서 사용되는 모든 내부 로그를 확인하려면, 앱을 실행할 때 `DEBUG` 환경 변수를
-`express:*`로 설정하십시오.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-Windows에서는 다음과 같은 명령을 사용하십시오.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-[Express 생성기](/{{ page.lang }}/starter/generator.html)가 생성한 기본 앱에 대해 이 명령을 실행하면 다음과 같이 인쇄됩니다.
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-이후 앱에 대한 요청이 이루어지면, Express 코드에 지정된 로그를 확인할 수 있습니다.
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-라우터 구현의 로그만 확인하려면 `DEBUG`의 값을 `express:router`로 설정하십시오. 마찬가지로, 애플리케이션 구현의 로그만 확인하려면 `DEBUG`의 값을 `express:application`으로 설정하십시오. 나머지도 이와 같습니다.
-
-## `express`를 통해 생성된 애플케이션
-
-`express` 명령을 통해 생성된 애플리케이션 또한 `debug` 모듈을 사용하며, 이러한 애플리케이션의 디버그 네임스페이스의 범위는 애플리케이션의 이름으로 한정됩니다.
-
-예를 들어 `$ express sample-app`을 통해 앱을 생성하는 경우에는 다음과 같은 명령을 통해 디버그 명령문을 사용할 수 있습니다.
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-다음과 같이 쉼표로 구분된 이름 목록을 지정하면 2개 이상의 디버그 네임스페이스를 지정할 수 있습니다.
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/ko/guide/error-handling.md b/ko/guide/error-handling.md
deleted file mode 100644
index 8b88692df5..0000000000
--- a/ko/guide/error-handling.md
+++ /dev/null
@@ -1,265 +0,0 @@
----
-layout: page
-title: Express 오류 처리
-description: Express.js가 동기 및 비동기 코드에서 오류를 처리하는 방식을 이해하고, 애플리케이션에 맞는 사용자 정의 오류 처리 미들웨어를 구현하는 방법을 알아보세요.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# 오류 처리
-
-에러 처리란 Express가 동기 및 비동기적으로 발생하는 에러를 포착하고 처리하는 방식을 의미합니다. Express는 기본 에러 처리기를 제공하므로 시작하기 위해 직접 작성할 필요가 없습니다.
-
-## 에러 포착하기
-
-Express가 라우트 핸들러와 미들웨어 실행 중 발생하는 모든 에러를 포착하는 것이 중요합니다.
-
-라우트 핸들러 및 미들웨어 내부의 동기 코드에서 발생하는 에러는 추가 작업이 필요하지 않습니다. 동기 코드에서 에러가 발생하면 Express가 에러를 감지하여 처리합니다. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-여러 콜백 함수를 갖는 라우트 핸들러가 있는 경우에는 `route` 매개변수를 사용하여 그 다음의 라우트 핸들러로 건너뛸 수 있습니다.  예를 들면 다음과 같습니다.
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-다른 미들웨어 함수와 동일한 방법으로 오류 처리 미들웨어 함수를 정의할 수 있지만,
-오류 처리 함수는 3개가 아닌 4개의 인수, 즉 `(err, req, res, next)`를
-갖는다는 점이 다릅니다.
-예를 들면 다음과 같습니다.
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-`getUserById`에서 에러가 발생하거나 거부(reject)되면, `next`는 발생한 에러 또는 거부된 값을 사용하여 호출됩니다. 만약 거부된 값(rejected value)이 제공되지 않으면 `next`는 Express 라우터가 제공하는 기본 에러 객체와 함께 호출됩니다.
-
-`next()` 함수로 어떠한 내용을 전달하는 경우(`'route'`라는 문자열 제외), Express는 현재의 요청에 오류가 있는 것으로 간주하며, 오류 처리와 관련되지 않은 나머지 라우팅 및 미들웨어 함수를 건너뜁니다.
-
-만약 연속적인 과정(sequence)에서 콜백이 데이터는 제공하지 않고 에러만 제공한다면 다음과 같이 코드를 간소화할 수 있습니다:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-위 예제에서, `next`는 `fs.writeFile`의 콜백으로 제공되며 이 콜백은 에러 발생 여부와 관계없이 호출됩니다. 에러가 없으면 두 번째 핸들러가 실행되고, 그렇지 않으면 Express에서 에러를 포착하여 처리합니다.
-
-라우트 핸들러나 미들웨어에서 호출하는 비동기 코드에서 발생하는 에러는 반드시 포착하여 Express에 전달하여 처리해야 합니다. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-위 예제는 `try...catch` 블록을 사용하여 비동기 코드의 에러를 포착하여 Express에 전달합니다. 만약 `try...catch` 블록이 생략되면, Express는 해당 에러가 동기 핸들러 코드의 일부가 아니므로 에러를 포착하지 못할 것입니다.
-
-프로미스를 사용하면 `try...catch` 블록의 오버헤드를 피하거나 프로미스를 반환하는 함수를 사용할 때 유용합니다. 예를 들면 다음과 같습니다.  예를 들면 다음과 같습니다.
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-프로미스는 동기 에러와 거부된 프로미스를 모두 자동으로 포착하므로, `next`를 최종 catch 핸들러로 제공하기만 해도 Express가 에러를 포착합니다. 이는 catch 핸들러가 에러를 첫 번째 인자로 받기 때문입니다.
-
-또한 비동기 코드를 최소화하여 동기 에러 감지에 의존하는 핸들러 체인을 사용할 수도 있습니다. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-위 예제에는 `readFile` 호출에서 몇 가지 간단한 내용을 포함합니다. 만약 `readFile`에서 에러가 발생한다면 Express로 해당 에러가 전달되고, 그렇지 않으면 체인의 다음 핸들러로 넘어가면서 동기적인 에러 처리 흐름으로 복귀하게 됩니다.  그런 다음 위 예제에서는 데이터 처리를 시도합니다. 만약 이 과정이 실패하면 동기 에러 핸들러가 에러를 포착합니다. 만약 이 처리를 `readFile` 콜백 내부에서 했다면 애플리케이션이 비정상 종료되어 Express 에러 핸들러가 실행되지 못할 수도 있습니다.
-
-어떤 방법을 사용하든, Express 에러 핸들러가 호출되고 애플리케이션이 정상적으로 작동하게 하려면 Express가 에러를 받도록 해야 합니다.
-
-## 기본 오류 핸들러
-
-Express는 내장된 오류 핸들러와 함께 제공되며, 내장 오류 핸들러는 앱에서 발생할 수 있는 모든 오류를 처리합니다. 이러한 기본 오류 처리 미들웨어 함수는 미들웨어 함수 스택의 끝에 추가됩니다.
-
-`next()`로 오류를 전달하지만 오류 핸들러에서 해당 오류를
-처리하지 않는 경우, 기본 제공 오류 핸들러가 해당 오류를 처리하며, 해당 오류는
-클라이언트에 스택 추적과 함께 기록됩니다. 스택 추적은 프로덕션 환경에 포함되어 있지 않습니다.
-
-<div class="doc-box doc-info" markdown="1">
-프로덕션 모드에서 앱을 실행하려면 환경 변수 `NODE_ENV`를 `production`으로 설정하십시오.
-</div>
-
-에러가 기록되면 다음 정보가 응답에 추가됩니다:
-
-- `res.statusCode`는 `err.status` 또는 `err.statusCode`값으로 설정됩니다. 이 값이 4xx 또는 5xx 범위를 벗어나면 500 으로 설정됩니다.
-- `res.statusMessage`는 상태 코드에 따라 설정됩니다.
-- body는 프로덕션 환경일 경우 상태 코드 메시지의 HTML이 되고, 그렇지 않은 경우 `err.stack`이 됩니다.
-- `err.headers` 객체에 지정된 모든 헤더가 포함됩니다.
-
-응답의 기록을 시작한 후에 오류가 있는 `next()`를
-호출하는 경우(예: 응답을 클라이언트로 스트리밍하는 중에 오류가
-발생하는 경우), Express의 기본 오류 핸들러는 해당 연결을 닫고
-해당 요청을 처리하지 않습니다.
-
-따라서 사용자 정의 오류 핸들러를 추가할 때, 헤더가 이미 클라이언트로 전송된 경우에는
-다음과 같이 Express 내의 기본 오류 처리 메커니즘에 위임해야 합니다:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-만약 `next()`를 여러분의 코드에서 여러 번 호출한다면, 사용자 정의 오류 핸들러가 있음에도 불구하고 기본 오류 핸들러가 발동될 수 있음에 주의하십시오.
-
-다른 에러 핸들링 미들웨어는 [Express middleware](/{{ page.lang }}/resources/middleware.html) 에서 확인할 수 있습니다.
-
-## 에러 핸들러 작성하기
-
-에러 핸들링 미들웨어 함수는 다른 미들웨어 함수와 동일한 방식으로 정의합니다. 단, 에러 핸들링 함수는 세 개가 아닌 네 개의 인수(`err`, `req`, `res`, `next`)를 받는다는 점이 다릅니다. 예를 들면 다음과 같습니다.
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-오류 처리 미들웨어는 다른 `app.use()` 및 라우트 호출을 정의한 후에 마지막으로 정의해야 하며, 예를 들면 다음과 같습니다.
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-미들웨어 함수 내부로부터의 응답은 HTML 오류 페이지, 단순한 메시지 또는 JSON 문자열 등 여러분이 선호하는 모든 형식일 수 있습니다.
-
-조직적(및 상위 레벨 프레임워크) 목적을 위해, 여러 오류 처리
-미들웨어 함수를 정의할 수 있으며, 이는 일반적인 미들웨어 함수를 정의할 때와
-매우 비슷합니다. 예를 들어 `XHR`를 이용한 요청 및
-그렇지 않은 요청에 대한 오류 처리를 정의하려는 경우, 다음과 같은 명령을 사용할 수 있습니다.
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-이 예에서 일반 `logErrors`는 요청 및 오류 정보를 `stderr`에
-기록할 수도 있으며, 예를 들면 다음과 같습니다.
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-또한 이 예에서 `clientErrorHandler`는 다음과 같이 정의되며, 이 경우 오류는 명시적으로 그 다음 항목으로 전달됩니다.
-
-에러 핸들링 함수에서 "next"를 호출하지 **않을** 경우, response를 작성하고 종료해야 합니다. 그렇지 않으면 해당 request는 "중단(hang)"되어 가비지 컬렉션 대상이 되지 않습니다.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-"모든 오류를 처리하는(catch-all)" `errorHandler` 함수는 다음과 같이 구현될 수 있습니다.
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-만약 여러개의 콜백 함수가 있는 라우트 핸들러가 있다면 `route` 매개변수를 사용하여 다음 라우트 핸들러로 건너뛸 수 있습니다. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-이 예에서 `getPaidContent` 핸들러의 실행은 건너뛰지만, `/a_route_behind_paywall`에 대한 `app` 내의 나머지 핸들러는 계속하여 실행됩니다.
-
-<div class="doc-box doc-info" markdown="1">
-`next()` 및 `next(err)`에 대한 호출은 현재의 핸들러가 완료되었다는 것과 해당 핸들러의 상태를 표시합니다.  `next(err)`는 위에 설명된 것과 같이 오류를 처리하도록 설정된 핸들러를 제외한 체인 내의 나머지 모든 핸들러를 건너뜁니다.
-</div>
diff --git a/ko/guide/migrating-4.md b/ko/guide/migrating-4.md
deleted file mode 100644
index ecd5a86b2f..0000000000
--- a/ko/guide/migrating-4.md
+++ /dev/null
@@ -1,614 +0,0 @@
----
-layout: page
-title: Express 4로의 마이그레이션
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Express 4로의 이전
-
-<h2 id="overview">개요</h2>
-
-Express 4는 Express 3로부터 근본적으로 변경되었습니다. 따라서 기존 Express 3 앱의 종속 항목의 Express 버전을 업데이트하면 기존 Express 3 앱은 작동하지 않습니다.
-
-이 문서에서는 다음을 다룹니다.
-
-<ul class="doclist">
-  <li><a href="#changes">Express 4에서의 변경사항.</a></li>
-  <li>Express 3 앱의 Express 4로의 마이그레이션의 <a href="#example-migration">예</a>.</li>
-  <li><a href="#app-gen">Express 4 생성기로의 업그레이드.</a></li>
-</ul>
-
-<h2 id="changes">Express 4에서의 변경사항</h2>
-
-Express 4에서는 여러 중요한 부분이 변경되었습니다.
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">라우팅 시스템에 대한 변경.</a></li>
-  <li><a href="#other-changes">기타 다양한 변경사항.</a></li>
-</ul>
-
-또한 다음을 참조하십시오.
-
-- [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Express 코어 및 미들웨어 시스템에 대한 변경
-</h3>
-
-Express 4는 더 이상 Connect에 종속되지 않으며, `express.static` 함수를
-제외한 모든 기본 제공 미들웨어가 Express 4 코어에서 제거되었습니다. 따라서 Express는
-이제 독립적인 라우팅 및 미들웨어 웹 프레임워크가 되었으며, Express 버전화 및 릴리스는
-미들웨어 업데이트의 영향을 받지 않게 되었습니다.
-
-기본 제공 미들웨어가 없으므로 사용자는 앱을 실행하는 데 필요한
-모든 미들웨어를 명시적으로 추가해야 합니다. 이를 위해서는 다음 단계를 따르기만 하면 됩니다.
-
-1. 모듈 설치: `npm install --save <module-name>`
-2. 앱 내에서, 모듈 요청: `require('module-name')`
-3. 해당 모듈의 문서에 따라 모듈 사용: `app.use( ... )`
-
-다음 표에는 Express 3의 미들웨어 및 그에 대응하는 Express 4의 미들웨어가 나열되어 있습니다.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Express 4 미들웨어의 [전체 목록](https://github.com/senchalabs/connect#middleware)을 참조하십시오.
-
-대부분의 경우 구버전인 버전 3의 미들웨어를 Express 4의 대응하는
-미들웨어로 대체할 수 있습니다. 상세 정보는 GitHub 모듈 문서를
-참조하십시오.
-
-<h4 id="app-use"><code>app.use</code>가 매개변수를 수락</h4>
-
-버전 4에서는 미들웨어 함수가 로드되는 경로를 정의하기 위하여 가변 매개변수를 사용할 수 있으며, 이후 라우트 핸들러로부터 매개변수의 값을 읽을 수 있습니다.
-예를 들면 다음과 같습니다.
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-라우팅 시스템
-</h3>
-
-이제 앱은 라우팅 미들웨어를 암시적으로 로드하므로, 더 이상
-`router` 미들웨어에 대한 미들웨어 로드 순서에 대해
-걱정할 필요가 없습니다.
-
-라우트를 정의하는 방법은 변경되지 않았지만, 라우트의 구성을 돕기 위하여
-라우팅 시스템에는 다음과 같은 2개의 새로운 기능이 추가되었습니다.
-
-{: .doclist }
-
-- 라우트 경로에 대하여 체인 가능한 라우트 핸들러를 작성할 수 있는 새로운 메소드인 `app.route()`.
-- 모듈식 마운팅 가능한 라우트 핸들러를 작성할 수 있는 새로운 클래스인 `express.Router`.
-
-<h4 id="app-route"><code>app.route()</code> 메소드</h4>
-
-새롭게 추가된 `app.route()` 메소드를 이용하면 라우트 경로에 대하여 체인 가능한
-라우트 핸들러를 작성할 수 있습니다. 경로는 한 곳에 지정되어 있으므로, 모듈식 라우트를 작성하면 중복성과 오타가 감소하여 도움이 됩니다. 라우트에 대한
-자세한 정보는 [`Router()` 문서](/{{ page.lang }}/4x/api.html#router)를 참조하십시오.
-
-`app.route()` 함수를 사용하여 정의된 체인 라우트 핸들러의 예는 다음과 같습니다.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> 클래스</h4>
-
-라우트의 구성을 돕는 다른 기능은 새롭게 추가된 클래스인
-`express.Router`이며, 이를 이용해 모듈식 마운팅 가능한
-라우트 핸들러를 작성할 수 있습니다. `Router` 인스턴스는 완전한 미들웨어이자
-라우팅 시스템이며, 따라서 "미니 앱(mini-app)"이라고 불리는 경우가 많습니다.
-
-다음 예에서는 라우터를 모듈로서 작성하고, 라우터 모듈에서 미들웨어를 로드하고,
-몇몇 라우트를 정의하고, 기본 앱의 한 경로에 라우터 모듈을 마운트합니다.
-
-예를 들면, 다음의 내용이 입력된 `birds.js`라는 이름의 라우터 파일을
-앱 디렉토리에 작성할 수 있습니다.
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-이후 앱 내에서 다음과 같이 라우터 모듈을 로드하십시오.
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-앱은 이제 `/birds` 및 `/birds/about` 경로에 대한
-요청을 처리할 수 있게 되었으며, 해당 라우트에 대한 특정한 미들웨어인
-`timeLog`를 로드할 것입니다.
-
-<h3 id="other-changes">
-기타 변경사항
-</h3>
-
-다음 표에는 Express 4의 작지만 중요한 다른 변경사항이 나열되어 있습니다.
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>오브젝트</th>
-<th>설명</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4에는 Node.js 0.10.x 이상이 필요하며 Node.js 0.8.x에 대한 지원은
-중단되었습니다.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-`http` 모듈을 이용해 직접 작업해야 하는 경우(socket.io/SPDY/HTTPS)를 제외하면, `http` 모듈이 더 이상 필요하지 않습니다. `app.listen()`
-함수를 이용해 앱을 시작할 수 있습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-`app.configure()` 함수가 제거되었습니다.  환경을 발견하고
-그에 따라 앱을 구성하려면 `process.env.NODE_ENV`
-또는 `app.get('env')` 함수를 사용하십시오.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-Express 4에서는 기본적으로 `json spaces` 애플리케이션 특성을 사용하지 않습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-`req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()` 및 `req.acceptsLanguages()`를 사용하십시오.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-더 이상 상대 URL을 분석하지 않습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-이전에는 배열이었지만 이제 오브젝트가 되었습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-이전에는 함수였지만 이제 오브젝트가 되었습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-`res.headersSent`로 변경되었습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-이제 `app.mountpath`로 사용 가능합니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-제거되었습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-제거되었습니다.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-이제 기능이 기본 쿠키 값의 설정으로 제한되었습니다. 추가적인
-기능을 위해서는 `res.cookie()`를 사용하십시오.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">앱 마이그레이션의 예</h2>
-
-여기서는 Express 3 애플리케이션을 Express 4로 마이그레이션하는 예를 살펴보겠습니다.
-대상 파일은 `app.js` 및 `package.json`입니다.
-
-<h3 id="">
-버전 3 앱
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-다음과 같은 `app.js` 파일을 갖는 Express 버전 3 애플리케이션을 가정합니다.
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-동반되는 버전 3의 `package.json` 파일의 내용은
-다음과 같을 수 있습니다.
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-프로세스
-</h3>
-
-다음의 명령을 통해 Express 4에 필요한 미들웨어를 설치하고 Express 및 Pug를
-각각 최신 버전으로 업데이트하여 마이그레이션 프로세스를
-시작하십시오.
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-`app.js`를 다음과 같이 변경하십시오.
-
-1. 기본 제공 Express 미들웨어 함수인 `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` 및
-   `express.errorHandler`는 더 이상 `express`
-   오브젝트에 사용할 수 없습니다. 이들 함수의 대체 함수를 수동으로
-   설치한 후 앱에서 로드해야 합니다.
-
-2. `app.router` 함수는 이제 로드할 필요가 없습니다.
-   이 함수는 유효한 Express 4 앱 오브젝트가 아니므로
-   `app.use(app.router);` 코드를 제거하십시오.
-
-3. 미들웨어 함수들이 올바른 순서로 로드되는지 확인하십시오(앱 라우트를 로드한 후 `errorHandler`를 로드).
-
-<h3 id="">버전 4 앱</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-위의 `npm` 명령을 실행하면 `package.json`이 다음과 같이 업데이트됩니다.
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-이후 올바르지 않은 코드를 제거하고, 필요한 미들웨어를 로드하고,
-필요에 따라 다른 변경을 실행하십시오. `app.js` 파일의 내용은 다음과 같습니다.
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-`http` 모듈을 이용해 직접 작업해야 하는 경우(socket.io/SPDY/HTTPS)를 제외하면 `http` 모듈을 로드할 필요가 없으며, 다음과 같은 방법으로 간단히 앱을 시작할 수 있습니다.
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Run the app</h3>
-
-마이그레이션 프로세스가 완료되었으며, 이제 앱은
-Express 4 앱이 되었습니다. 확인을 위하여, 다음의 명령을 이용해 앱을 시작하십시오.
-
-```bash
-$ node .
-```
-
-[http://localhost:3000](http://localhost:3000)을
-로드한 후 홈 페이지가 Express 4에 의해 렌더링되는 것을 확인하십시오.
-
-<h2 id="app-gen">Express 4 앱 생성기로의 업그레이드</h2>
-
-Express 앱을 생성하기 위한 명령행 도구는 여전히
-`express`이지만, 새 버전으로 업그레이드하려면
-Express 3 앱 생성기의 설치를 제거한 후 새로운
-`express-generator`를 설치해야 합니다.
-
-<h3 id="">설치 </h3>
-
-Express 3 앱 생성기가 이미 시스템에 설치되어 있는 경우, 다음과 같이
-Express 3 앱 생성기의 설치를 제거해야 합니다.
-
-```bash
-$ npm uninstall -g express
-```
-
-파일 및 디렉토리 권한이 구성된 방식에 따라서, 위의 명령은
-`sudo`를 이용해 실행해야 할 수도 있습니다.
-
-이제 다음과 같이 새 생성기를 설치하십시오.
-
-```bash
-$ npm install -g express-generator
-```
-
-파일 및 디렉토리 권한이 구성된 방식에 따라서, 위의 명령은
-`sudo`를 이용해 실행해야 할 수도 있습니다.
-
-이제 시스템의 `express` 명령이 Express 4 생성기로
-업데이트되었습니다.
-
-<h3 id="">앱 생성기에 대한 변경사항 </h3>
-
-다음을 제외하면, 명령의 옵션 및 용도는 대체로 동일하게 유지되었습니다.
-
-{: .doclist }
-
-- `--sessions` 옵션이 제거되었습니다.
-- `--jshtml` 옵션이 제거되었습니다.
-- [Hogan.js](http://twitter.github.io/hogan.js/)를 지원하기 위한 `--hogan` 옵션이 추가되었습니다.
-
-<h3 id="">Example</h3>
-
-Express 4 앱을 작성하기 위하여 다음의 명령을 실행하십시오.
-
-```bash
-$ express app4
-```
-
-`app4/app.js` 파일의 내용을 살펴보면, 앱에 필요한 모든 미들웨어
-함수(`express.static` 제외)가 독립적인 모듈로서 로드되며
-`router` 미들웨어는 이제 앱에 명시적으로 로드되지 않는다는 것을
-알 수 있습니다.
-
-또한 이전에 `app.js` 파일은 구버전의 생성기에 의해 생성되는 독립형 앱이었지만, 이제는 Node.js의 모듈이 되었다는 것을 알 수 있습니다.
-
-종속 항목을 설치한 후, 다음의 명령을 이용해 앱을 시작하십시오.
-
-```bash
-$ npm start
-```
-
-`package.json` 파일 내의 npm 시작 스크립트를 살펴보면,
-Express 3에서는 `node app.js`를 이용해 앱을 시작했지만,
-이제 앱을 시작하는 실제 명령은 `node ./bin/www`라는 것을
-알 수 있습니다.
-
-Express 4 생성기에 의해 생성된 `app.js` 파일은 이제 Node.js의 모듈이므로,
-`app.js` 파일은 더 이상 하나의 앱으로서 독립적으로 시작될 수
-없습니다(코드를 수정하는 경우 제외). 이러한 모듈은 Node.js 파일에서 로드되어야 하며
-Node.js 파일을 통해 시작되어야 합니다. 이 경우에서 Node.js 파일은
-`./bin/www`입니다.
-
-이제는 Express 앱을 작성하거나 앱을 시작하는 데 있어 `bin` 디렉토리 또는
-확장자 없는 `www` 파일이 필수가 아닙니다. 이들은
-단지 생성기에 의한 추천사항이며, 따라서 필요사항에 맞추어 수정해도
-좋습니다.
-
-`www` 디렉토리를 제거하고 "Express 3의 방식"을 유지하려면,
-`app.js` 파일의 끝에 있는 `module.exports = app;`가
-포함된 행을 삭제한 후 그 자리에 다음의 코드를 붙여넣으십시오.
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-`debug` 모듈은 다음의 코드를 이용하여 `app.js` 파일의 맨 위에서 로드되어야 합니다.
-
-```js
-var debug = require('debug')('app4')
-```
-
-다음으로, `package.json` 파일의 `"start": "node ./bin/www"`를 `"start": "node app.js"`로 변경하십시오.
-
-이제 `./bin/www`의 기능이 다시 `app.js`로
-이전되었습니다. 이러한 변경은 권장되지 않지만, 이러한 연습을 통해
-`./bin/www` 파일의 작동 원리를 이해하고 `app.js` 파일이
-더 이상 자체적으로 시작되지 않는 이유를 이해할 수 있습니다.
diff --git a/ko/guide/migrating-5.md b/ko/guide/migrating-5.md
deleted file mode 100644
index 57fbcff970..0000000000
--- a/ko/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: Express 5로의 마이그레이션
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Express 5로의 이전
-
-<h2 id="overview">개요</h2>
-
-Express 5는 Express 4와 크게 다르지 않으며, API에 대한 변경은 3.0에서 4.0으로의 변경만큼 크지 않습니다. 기본적인 API는 동일하게 유지되지만, 근본적인 변경사항이 존재합니다. 즉, Express 5를 사용하기 위해 기존 Express 4 프로그램을 업데이트하면 기존 Express 4 프로그램은 작동하지 않을 수 있습니다.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-이후 자동화된 테스트를 실행하여 실패하는 항목을 확인하고, 아래에 나열된 업데이트에 따라 문제를 수정할 수 있습니다. 테스트 실패 항목을 처리한 후에는 앱을 실행하여 어떠한 오류가 발생하는지 확인하십시오. 지원되지 않는 메소드나 특성을 앱이 사용하는 경우에는 이를 곧바로 확인할 수 있습니다.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Express 5에서의 변경사항</h2>
-
-**제거된 메소드 및 특성**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">복수형의 메소드 이름</a></li>
-  <li><a href="#leading">app.param(name, fn)에 대한 이름(name) 인수의 첫머리 콜론</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**개선된 항목**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**변경된 항목**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## 제거된 메소드 및 특성
-
-앱에서 이러한 메소드 또는 특성 중 어느 하나라도 사용한다면 앱에서 충돌이 발생합니다. 따라서 버전 5로 업데이트한 후에는 앱을 변경해야 합니다.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5는 `app.del()` 함수를 더 이상 지원하지 않습니다. 이 함수를 사용하면 오류에 대한 예외 처리(throw)가 발생합니다. HTTP DELETE 라우트를 등록하려면 `app.delete()` 함수를 대신 사용하십시오.
-
-`delete`는 JavaScript의 예약된 키워드이므로, 처음에는 `delete` 대신 `del`이 사용되었습니다. 그러나, ECMAScript 6을 기준으로, `delete` 및 다른 예약된 키워드를 정식 특성 이름으로 사용할 수 있게 되었습니다.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-`app.param(fn)` 시그니처는 `app.param(name, fn)` 함수의 작동을 수정하는 데 사용되었습니다. 이 시그니처는 v4.11.0 이후 더 이상 사용되지 않았으며 Express 5에서는 전혀 지원되지 않습니다.
-
-<h3 id="plural">복수형의 메소드 이름</h3>
-
-다음과 같은 메소드 이름은 이제 복수형이 되었습니다. Express 4에서는 구버전의 메소드를 사용하면 사용 중단 경고가 표시되었습니다. Express 5는 구버전의 메소드를 전혀 지원하지 않습니다.
-
-`req.acceptsLanguage()`는 `req.acceptsLanguages()`로 대체되었습니다.
-
-`req.acceptsCharset()`는 `req.acceptsCharsets()`로 대체되었습니다.
-
-`req.acceptsEncoding()`은 `req.acceptsEncodings()`로 대체되었습니다.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">app.param(name, fn)에 대한 이름(name)의 첫머리 콜론(:)</h3>
-
-`app.param(name, fn)` 함수의 이름(name)의 첫머리 콜론 문자(:)는 Express 3의 잔존물이며, 하위 호환성을 위해 Express 4에서는 첫머리 콜론을 지원하면서 사용 중단 알림을 표시했습니다. Express 5는 아무런 메시지 표시 없이 첫머리 콜론을 무시하며, 콜론을 이용한 접두부가 없는 이름 매개변수를 사용합니다.
-
-[app.param](/{{ page.lang }}/4x/api.html#app.param)에 대한 Express 4 문서에는 첫머리 콜론이 언급되어 있지 않으므로, 이 문서를 따라 앱을 작성한 경우에는 이 변경사항이 코드에 영향을 미치지 않을 것입니다.
-
-<h3 id="req.param">req.param(name)</h3>
-
-양식 데이터 검색을 위한 이 메소드는 혼란과 위험을 발생시킬 수 있으므로 제거되었습니다. 이제는 `req.params`, `req.body` 또는 `req.query` 오브젝트에서 제출된 매개변수 이름을 구체적으로 확인해야 합니다.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5는 `res.json(obj, status)` 시그니처를 더 이상 지원하지 않습니다. 대신, 상태를 설정한 후 이를 `res.status(status).json(obj)`과 같은 `res.json()` 메소드에 체인해야 합니다.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5는 `res.jsonp(obj, status)` 시그니처를 더 이상 지원하지 않습니다. 대신, 상태를 설정한 후 이를 `res.status(status).jsonp(obj)`와 같은 `res.jsonp()` 메소드에 체인해야 합니다.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5는 `res.send(obj, status)` 시그니처를 더 이상 지원하지 않습니다. 대신, 상태를 설정한 후 이를 `res.status(status).send(obj)`와 같은 `res.send()` 메소드에 체인해야 합니다.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5는 \*`status`\*가 숫자인 <code>res.send(<em>status</em>)</code> 시그니처를 더 이상 지원하지 않습니다. 대신, HTTP 응답 헤더 상태 코드를 설정하고 해당 코드의 텍스트 버전("Not Found", "Internal Server Error" 등)을 전송하는 `res.sendStatus(statusCode)` 함수를 사용해야 합니다.
-`res.send()` 함수를 이용해 숫자를 전송해야 하는 경우, Express가 그 숫자를 지원되지 않는 구버전 시그니처 사용 시도로 해석하지 않도록 숫자의 앞뒤에 따옴표를 추가하여 숫자를 문자열로 변환하십시오.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-Express 5에서 `res.sendfile()` 함수는 낙타 대문자(camel-cased) 버전인 `res.sendFile()`로 대체되었습니다.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. 이 시그니처는 v4.11.0 이후 더 이상 사용되지 않았으며 Express 5에서는 전혀 지원되지 않습니다.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## 변경된 항목
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-예를 들면 다음과 같습니다.
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-Express 4에서 제거되었던 `app.router` 오브젝트가 Express 5에 되돌아왔습니다. Express 3에서는 앱이 이 오브젝트를 명시적으로 로드해야 했던 것과 달리, 새 버전에서 이 오브젝트는 단순히 기본 Express 라우터에 대한 참조의 역할을 합니다.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-Express 4에서, 포트 번호가 존재하는 경우 `req.host` 함수는 포트 번호를 올바르지 않게 제거했습니다. Express 5에서는 포트 번호가 유지됩니다.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## 개선된 항목
-
-<h3 id="res.render">res.render()</h3>
-
-이 메소드는 이제 모든 보기 엔진에 대해 비동기식 작동을 적용하며, 동기식 구현을 갖는 보기 엔진 및 권장되는 인터페이스를 위반하는 보기 엔진에 의한 버그의 발생을 방지합니다.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/ko/guide/overriding-express-api.md b/ko/guide/overriding-express-api.md
deleted file mode 100644
index e70530488f..0000000000
--- a/ko/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: 프로토타입을 사용해 request와 response 객체의 메서드와 속성을 오버라이드하여 Express.js API를 커스터마이즈하고 확장하는 방법을 알아보세요.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/ko/guide/routing.md b/ko/guide/routing.md
deleted file mode 100644
index ab626cf109..0000000000
--- a/ko/guide/routing.md
+++ /dev/null
@@ -1,413 +0,0 @@
----
-layout: page
-title: Express 라우팅
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# 라우팅
-
-_라우팅_은 애플리케이션 엔드 포인트(URI)의 정의, 그리고 URI가 클라이언트 요청에 응답하는 방식을 말합니다.
-라우팅에 대한 소개는 [기본 라우팅](/{{ page.lang }}/starter/basic-routing.html)을 참조하십시오.
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-특수한 라우팅 메소드인 `app.all()`은 어떠한 HTTP 메소드로부터도 파생되지 않습니다. 이 메소드는 모든 요청 메소드에 대해 한 경로에서 미들웨어 함수를 로드하는 데 사용됩니다.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-다음 코드는 매우 기본적인 라우트의 예입니다.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">라우트 메소드</h2>
-
-라우트 메소드는 HTTP 메소드 중 하나로부터 파생되며, `express` 클래스의 인스턴스에 연결됩니다.
-
-다음 코드는 앱의 루트에 대한 GET 및 POST 메소드에 대해 정의된 라우트의 예입니다.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express는 HTTP 메소드에 해당하는 다음과 같은 라우팅 메소드를 지원합니다.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">라우트 경로</h2>
-
-라우트 경로는, 요청 메소드와의 조합을 통해, 요청이 이루어질 수 있는 엔드포인트를 정의합니다. 라우트 경로는 문자열, 문자열 패턴 또는 정규식일 수 있습니다.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Route Tester](http://forbeslindesay.github.io/express-route-tester/)는 기본적인 Express 라우트의 테스트를 위한 편리한 도구이지만, 패턴 일치는 지원하지 않습니다.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### 문자열을 기반으로 하는 라우트 경로의 몇 가지 예는 다음과 같습니다.
-
-다음의 라우트 경로는 요청을 루트 라우트 `/`에 일치시킵니다.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-다음의 라우트 경로는 요청을 `/about`에 일치시킵니다.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-다음의 라우트 경로는 요청을 `/random.text`에 일치시킵니다.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### 문자열 패턴을 기반으로 하는 라우트 경로의 몇 가지 예는 다음과 같습니다.
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-다음의 라우트 경로는 `acd` 및 `abcd`와 일치합니다.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-다음의 라우트 경로는 `abcd`, `abbcd` 및 `abbbcd` 등과 일치합니다.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-다음의 라우트 경로는 `abcd`, `abxcd`, `abRABDOMcd` 및 `ab123cd` 등과 일치합니다.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-다음의 라우트 경로는 `/abe` 및 `/abcde`와 일치합니다.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### 정규식을 기반으로 하는 라우트 경로의 예:
-
-다음의 라우트 경로는 라우트 이름에 "a"가 포함된 모든 항목과 일치합니다.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-다음의 라우트 경로는 `butterfly` 및 `dragonfly`와 일치하지만, `butterflyman` 및 `dragonfly man` 등과 일치하지 않습니다.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">
-조회 문자열은 라우트 경로의 일부가 아닙니다.
-</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">라우트 핸들러</h2>
-
-[미들웨어](/{{ page.lang }}/guide/using-middleware.html)와 비슷하게 작동하는 여러 콜백 함수를 제공하여 요청을 처리할 수 있습니다. 유일한 차이점은 이러한 콜백은 `next('route')`를 호출하여 나머지 라우트 콜백을 우회할 수도 있다는 점입니다. 이러한 메커니즘을 이용하면 라우트에 대한 사전 조건을 지정한 후, 현재의 라우트를 계속할 이유가 없는 경우에는 제어를 후속 라우트에 전달할 수 있습니다.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-다음 예에 나타난 것과 같이, 라우트 핸들러는 함수나 함수 배열의 형태 또는 둘을 조합한 형태일 수 있습니다.
-
-하나의 콜백 함수는 하나의 라우트를 처리할 수 있습니다. 예를 들면 다음과 같습니다.
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-2개 이상의 콜백 함수는 하나의 라우트를 처리할 수 있습니다(`next` 오브젝트를 반드시 지정해야 함). 예를 들면 다음과 같습니다.
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-하나의 콜백 함수 배열은 하나의 라우트를 처리할 수 있습니다. 예를 들면 다음과 같습니다.
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-독립적인 함수와 함수 배열의 조합은 하나의 라우트를 처리할 수 있습니다. 예를 들면 다음과 같습니다.
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">응답 메소드</h2>
-
-다음 표에 표시된 응답 오브젝트에 대한 메소드(`res`)는 응답을 클라이언트로 전송하고 요청-응답 주기를 종료할 수 있습니다. 라우트 핸들러로부터 다음 메소드 중 어느 하나도 호출되지 않는 경우, 클라이언트 요청은 정지된 채로 방치됩니다.
-
-| 메소드                                                                                                                                                                                                                       | 설명                                                                  |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | 파일이 다운로드되도록 프롬프트합니다.                                |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | 응답 프로세스를 종료합니다.                                     |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | JSON 응답을 전송합니다.                                     |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | JSONP 지원을 통해 JSON 응답을 전송합니다.                        |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | 요청의 경로를 재지정합니다.                                     |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | 보기 템플리트를 렌더링합니다.                                    |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | 다양한 유형의 응답을 전송합니다.                                  |
-| [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile)     | 파일을 옥텟 스트림의 형태로 전송합니다.                              |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | 응답 상태 코드를 설정한 후 해당 코드를 문자열로 표현한 내용을 응답 본문으로서 전송합니다. |
-
-<h2 id="app-route">app.route()</h2>
-
-`app.route()`를 이용하면 라우트 경로에 대하여 체인 가능한 라우트 핸들러를 작성할 수 있습니다.
-경로는 한 곳에 지정되어 있으므로, 모듈식 라우트를 작성하면 중복성과 오타가 감소하여 도움이 됩니다. 라우트에 대한 자세한 정보는 [Router() 문서](/{{ page.lang }}/4x/api.html#router)를 참조하십시오.
-
-`app.route()`를 사용하여 정의된 체인 라우트 핸들러의 예는 다음과 같습니다.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-`express.Router` 클래스를 사용하면 모듈식 마운팅 가능한 핸들러를 작성할 수 있습니다. `Router` 인스턴스는 완전한 미들웨어이자 라우팅 시스템이며, 따라서 "미니 앱(mini-app)"이라고 불리는 경우가 많습니다.
-
-다음 예에서는 라우터를 모듈로서 작성하고, 라우터 모듈에서 미들웨어 함수를 로드하고, 몇몇 라우트를 정의하고, 기본 앱의 한 경로에 라우터 모듈을 마운트합니다.
-
-다음의 내용이 입력된 `birds.js`라는 이름의 라우터 파일을 앱 디렉토리에 작성하십시오.
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-이후 앱 내에서 다음과 같이 라우터 모듈을 로드하십시오.
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-앱은 이제 `/birds` 및 `/birds/about`에 대한 요청을 처리할 수 있게 되었으며, 해당 라우트에 대한 특정한 미들웨어 함수인 `timeLog`를 호출할 것입니다.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/ko/guide/using-middleware.md b/ko/guide/using-middleware.md
deleted file mode 100644
index d80032ca83..0000000000
--- a/ko/guide/using-middleware.md
+++ /dev/null
@@ -1,279 +0,0 @@
----
-layout: page
-title: Express 미들웨어 사용
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# 미들웨어 사용
-
-Express는 자체적인 최소한의 기능을 갖춘 라우팅 및 미들웨어 웹 프레임워크이며, Express 애플리케이션은 기본적으로 일련의 미들웨어 함수 호출입니다.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
-
-미들웨어 함수는 다음과 같은 태스크를 수행할 수 있습니다.
-
-- 모든 코드를 실행.
-- 요청 및 응답 오브젝트에 대한 변경을 실행.
-- 요청-응답 주기를 종료.
-- 스택 내의 그 다음 미들웨어 함수를 호출.
-
-현재의 미들웨어 함수가 요청-응답 주기를 종료하지 않는 경우에는 `next()`를 호출하여 그 다음 미들웨어 함수에 제어를 전달해야 합니다. 그렇지 않으면 해당 요청은 정지된 채로 방치됩니다.
-
-Express 애플리케이션은 다음과 같은 유형의 미들웨어를 사용할 수 있습니다.
-
-- [애플리케이션 레벨 미들웨어](#middleware.application)
-- [라우터 레벨 미들웨어](#middleware.router)
-- [오류 처리 미들웨어](#middleware.error-handling)
-- [기본 제공 미들웨어](#middleware.built-in)
-- [써드파티 미들웨어](#middleware.third-party)
-
-애플리케이션 레벨 및 라우터 레벨 미들웨어는 선택적인 마운트 경로를 통해 로드할 수 있습니다.
-일련의 미들웨어 함수를 함께 로드할 수도 있으며, 이를 통해 하나의 마운트 위치에 미들웨어 시스템의 하위 스택을 작성할 수 있습니다.
-
-<h2 id='middleware.application'>애플리케이션 레벨 미들웨어</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-다음 예에는 마운트 경로가 없는 미들웨어 함수가 표시되어 있습니다. 이 함수는 앱이 요청을 수신할 때마다 실행됩니다.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-다음 예에는 `/user/:id` 경로에 마운트되는 미들웨어 함수가 표시되어 있습니다. 이 함수는 `/user/:id` 경로에
-대한 모든 유형의 HTTP 요청에 대해 실행됩니다.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-다음 예에는 라우트 및 해당 라우트의 핸들러 함수(미들웨어 시스템)이 표시되어 있습니다. 이 함수는 `/user/:id` 경로에 대한 GET 요청을 처리합니다.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-아래에는 하나의 마운트 경로를 통해 일련의 미들웨어 함수를 하나의 마운트 위치에 로드하는 예가 표시되어 있습니다.
-이 예는 `/user/:id` 경로에 대한 모든 유형의 HTTP 요청에 대한 요청 정보를 인쇄하는 미들웨어 하위 스택을 나타냅니다.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-라우트 핸들러를 이용하면 하나의 경로에 대해 여러 라우트를 정의할 수 있습니다. 아래의 예에서는 `/user/:id` 경로에 대한 GET 요청에 대해 2개의 라우트를 정의합니다. 두 번째 라우트는 어떠한 문제도 발생키지 않지만, 첫 번째 라우트가 요청-응답 주기를 종료시키므로 두 번째 라우트는 절대로 호출되지 않습니다.
-
-다음 예에는 `/user/:id` 경로에 대한 GET 요청을 처리하는 미들웨어 하위 스택이 표시되어 있습니다.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-라우터 미들웨어 스택의 나머지 미들웨어 함수들을 건너뛰려면 `next('route')`를 호출하여 제어를 그 다음 라우트로 전달하십시오.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-다음 예에는 `/user/:id` 경로에 대한 GET 요청을 처리하는 미들웨어 하위 스택이 표시되어 있습니다.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-아래에는 상세한 옵션 오브젝트와 함께 `express.static` 미들웨어 함수를 사용하는 예가 표시되어 있습니다.
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>라우터 레벨 미들웨어</h2>
-
-라우터 레벨 미들웨어는 `express.Router()` 인스턴스에 바인드된다는 점을 제외하면 애플리케이션 레벨 미들웨어와 동일한 방식으로 작동합니다.
-
-```js
-const router = express.Router()
-```
-
-`router.use()` 및 `router.METHOD()` 함수를 사용하여 라우터 레벨 미들웨어를 로드하십시오.
-
-다음 예의 코드는 위에서 애플리케이션 레벨 미들웨어에 대해 표시된 미들웨어 시스템을 라우터 레벨 미들웨어를 사용하여 복제합니다.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-To skip the rest of the router's middleware functions, call `next('router')`
-to pass control back out of the router instance.
-
-다음 예에는 `/user/:id` 경로에 대한 GET 요청을 처리하는 미들웨어 하위 스택이 표시되어 있습니다.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>오류 처리 미들웨어</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-오류 처리 미들웨어에는 항상 *4개*의 인수가 필요합니다. 어떠한 함수를 오류 처리 미들웨어 함수로 식별하려면 4개의 인수를 제공해야 합니다. `next` 오브젝트를 사용할 필요는 없지만, 시그니처를 유지하기 위해 해당 오브젝트를 지정해야 합니다. 그렇지 않으면 `next` 오브젝트는 일반적인 미들웨어로 해석되어 오류 처리에 실패하게 됩니다.
-</div>
-
-다른 미들웨어 함수와 동일반 방법으로 다음과 같이 오류 처리 미들웨어 함수를 정의할 수 있지만, 오류 처리 함수는 3개가 아닌 4개의 인수, 구체적으로 말하면 `(err, req, res, next)` 시그니처를 갖는다는 점이 다릅니다.
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-오류 처리 미들웨어에 대한 상세 정보는 [오류 처리](/{{ page.lang }}/guide/error-handling.html)를 참조하십시오.
-
-<h2 id='middleware.built-in'>Built-in middleware</h2>
-
-4.x 버전 이후의 Express는 더 이상 [Connect](https://github.com/senchalabs/connect)에 종속되지 않습니다. `express.static`의 실행을 제외하면, 이전에 Express와 함께
-포함되었던 모든 미들웨어 함수는 이제 별도의 모듈에 포함되어 있습니다. [미들웨어 함수 목록](https://github.com/senchalabs/connect#middleware)을 확인하십시오.
-
-Express has the following built-in middleware functions:
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Third-party middleware</h2>
-
-Express 앱에 기능을 추가하려면 써드파티 미들웨어를 사용하십시오.
-
-필요한 기능을 위한 Node.js 모듈을 설치한 후, 애플리케이션 레벨 또는 라우터 레벨에서 해당 모듈을 앱에 로드하십시오.
-
-다음 예는 쿠키 구문 분석 미들웨어 함수인 `cookie-parser`의 설치 및 로드를 나타냅니다.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Express와 함께 일반적으로 사용되고 있는 써드파티 미들웨어 함수의 일부 목록을 확인하려면 [써드파티 미들웨어](../resources/middleware.html)를 참조하십시오.
diff --git a/ko/guide/using-template-engines.md b/ko/guide/using-template-engines.md
deleted file mode 100644
index a3e2cc5cb7..0000000000
--- a/ko/guide/using-template-engines.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: page
-title: Express와 함께 템플리트 엔진 사용
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Express와 함께 템플리트 엔진 사용
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, 템플리트가 있는 디렉토리. 예: `app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, 사용할 템플리트 엔진. 예: `app.set('view engine', 'pug')`
-
-이후 그에 맞는 템플리트 엔진 npm 패키지를 다음과 같이 설치하십시오.
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Express와 호환되는 템플리트 엔진(예: Pug)은 `__express(filePath, options, callback)`라는 이름의 함수를 내보내며, 이 함수는 `res.render()` 함수에 의해 호출되어 템플리트 코드를 렌더링합니다.
-
-일부 템플리트 엔진은 이러한 방식을 따르지 않습니다. [Consolidate.js](https://www.npmjs.org/package/consolidate) 라이브러리는 널리 이용되고 있는 모든 Node.js 템플리트 엔진을 맵핑함으로써 이러한 방식을 따르므로 Express 내에서 완벽하게 작동합니다.
-
-</div>
-
-보기 엔진을 설정한 후에는 앱에서 엔진을 지정하거나 템플리트 엔진 모듈을 로드할 필요가 없으며, Express는 아래에 표시된 것과 같이 내부적으로 모듈을 로드합니다(위의 예에 대한 코드).
-
-```js
-app.set('view engine', 'pug')
-```
-
-다음의 내용이 입력된 `index.pug`라는 이름의 Pug 템플리트를 `views` 디렉토리에 작성하십시오.
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-이후 `index.pug` 파일을 렌더링할 라우트를 작성하십시오. `view engine` 특성이 설정되어 있지 않은 경우에는 `view` 파일의 확장자를 지정해야 합니다. 해당 특성이 설정되어 있는 경우에는 확장자를 생략할 수 있습니다.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-홈 페이지에 대한 요청을 실행할 때, `index.pug` 파일은 HTML 형식으로 렌더링됩니다.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/ko/guide/writing-middleware.md b/ko/guide/writing-middleware.md
deleted file mode 100644
index ba300da6c6..0000000000
--- a/ko/guide/writing-middleware.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: Express 앱에서 사용하기 위한 미들웨어 작성
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Express 앱에서 사용하기 위한 미들웨어 작성
-
-<h2>개요</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
-
-미들웨어 함수는 다음과 같은 태스크를 수행할 수 있습니다.
-
-- 모든 코드를 실행.
-- 요청 및 응답 오브젝트에 대한 변경을 실행.
-- 요청-응답 주기를 종료.
-- 스택 내의 그 다음 미들웨어를 호출.
-
-현재의 미들웨어 함수가 요청-응답 주기를 종료하지 않는 경우에는 `next()`를 호출하여 그 다음 미들웨어 함수에 제어를 전달해야 합니다. 그렇지 않으면 해당 요청은 정지된 채로 방치됩니다.
-
-다음 예시에 미들웨어 함수 호출의 요소가 표시되어 있습니다.
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">미들웨어 함수가 적용되는 HTTP 메소드.</div></tbody>
-
-<div class="callout" id="callout2">미들웨어 함수가 적용되는 경로(라우트).</div>
-
-<div class="callout" id="callout3">미들웨어 함수.</div>
-
-<div class="callout" id="callout4">미들웨어 함수에 대한 콜백 인수(일반적으로 "next"라 불림).</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Example</h2>
-
-아래에는 간단한 "Hello World" Express 애플리케이션에 대한 예가 표시되어 있으며, 이 애플리케이션을 위해 두 개의 미들웨어 함수를 정의하게 됩니다.
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-아래에는 "myLogger"라는 이름의 미들웨어 함수에 대한 간단한 예가 표시되어 있습니다. 이 함수는 앱에 대한 요청이 해당 함수를 거쳐 전달될 때 단순히 "LOGGED"를 인쇄합니다. 이 미들웨어 함수는 `myLogger`라는 이름의 변수에 지정되어 있습니다.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-위의 예에서 `next()`에 대한 호출에 주목하십시오. 이 함수를 호출하면 앱 내의 그 다음 미들웨어 함수가 호출됩니다.
-`next()` 함수는 Node.js 또는 Express API의 일부가 아니지만, 미들웨어 함수에 전달되는 세 번째 인수입니다. `next()` 함수에는 어떠한 이름을 지정해도 좋지만, 일반적으로 항상 "next"라는 이름을 갖습니다.
-혼란을 방지하려면 항상 이러한 방식을 사용하십시오.
-</div>
-
-미들웨어 함수를 로드하려면 미들웨어 함수를 지정하여 `app.use()`를 호출하십시오.
-예를 들면, 다음의 코드는 루트 경로(/)로 라우팅하기 전에 `myLogger` 미들웨어 함수를 로드합니다.
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-앱이 요청을 수신할 때마다, 앱은 "LOGGED"라는 메시지를 터미널에 인쇄합니다.
-
-미들웨어의 로드 순서는 중요하며, 먼저 로드되는 미들웨어 함수가 먼저 실행됩니다.
-
-루트 경로에 대한 라우팅 이후에 `myLogger`가 로드되면, 루트 경로의 라우트 핸들러가 요청-응답 주기를 종료하므로 요청은 절대로 `myLogger`에 도달하지 못하며 앱은 "LOGGED"를 인쇄하지 않습니다.
-
-미들웨어 함수 `myLogger`는 단순히 메시지를 인쇄한 후 `next()` 함수를 호출하여 스택 내의 그 다음 미들웨어 함수에 요청을 전달합니다.
-
-<h3>Middleware function requestTime</h3>
-
-다음 예에서는 `requestTime`라는 특성을 요청 오브젝트에 추가합니다. 이 미들웨어 함수는 "requestTime"이라고 명명하겠습니다.
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-이제 앱은 `requestTime` 미들웨어 함수를 사용합니다. 또한 루트 경로 라우트의 콜백 함수는 미들웨어 함수가 `req`(요청 오브젝트)에 추가하는 특성을 사용합니다.
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-앱의 루트에 대한 요청을 실행할 때, 앱은 이제 요청의 타임스탬프를 브라우저에 표시합니다.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-사용자는 요청 오브젝트, 응답 오브젝트, 스택 내의 그 다음 미들웨어 함수, 그리고 모든 Node.js API에 대한 액세스 권한을 가지고 있으므로, 미들웨어 함수에 대한 가능성은 끝이 없습니다.
-
-Express 미들웨어에 대한 자세한 정보는 [Express 미들웨어 사용](/{{ page.lang }}/guide/using-middleware.html)을 참조하십시오.
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/ko/index.md b/ko/index.md
deleted file mode 100644
index 5f07009aec..0000000000
--- a/ko/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express는 빠르고, 특정 방식에 얽매이지 않으며, 최소한의 구조를 지닌 Node.js용 웹 프레임워크로, 웹 및 모바일 애플리케이션을 위한 강력한 기능들을 제공합니다."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>미들웨어</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/ko/resources/community.md b/ko/resources/community.md
deleted file mode 100644
index 91788e786c..0000000000
--- a/ko/resources/community.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-layout: page
-title: Express 커뮤니티
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# 커뮤니티
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-활기찬 커뮤니티에서는 매우 다양한 확장기능, [미들웨어 모듈](/{{ page.lang }}/resources/middleware.html)
-및 상위 레벨 프레임워크가 개발되어 왔습니다.
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## 문제
-
-버그라고 생각되는 현상을 겪었거나, 기능에 대한 요청을 하기 원하는 경우에는
-[issue queue](https://github.com/expressjs/express/issues)에서 티켓을 작성하십시오.
-
-## 예제
-
-API 설계에서부터 인증 및 템플리트 엔진 통합에 이르는 모든 주제를 다루는 저장소에서
-수십 개의 Express 애플리케이션 [예제](https://github.com/expressjs/express/tree/master/examples)를
-확인하십시오.
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/ko/resources/contributing.md b/ko/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/ko/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/ko/resources/glossary.md b/ko/resources/glossary.md
deleted file mode 100644
index 1e1f7b4a04..0000000000
--- a/ko/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express 용어집
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# 용어집
-
-### 애플리케이션(application)
-
-일반적으로, 특정한 목적의 연산을 수행하도록 설계된 하나 이상의 프로그램입니다.  Express의 컨텍스트에서는, Node.js 플랫폼에서 실행되며 Express API를 사용하는 프로그램을 말합니다.  또한 [앱 오브젝트](/{{ page.lang }}/api.html#express)를 지칭할 수도 있습니다.
-
-### API
-
-애플리케이션 프로그래밍 인터페이스(Application Programming Interface)입니다. 이 용어를 최초로 사용할 때는 약어를 풀어서 기재하십시오.
-
-### Express
-
-Node.js 애플리케이션을 위한 빠르고 개방적인 간결한 웹 프레임워크입니다. 일반적으로 "Express.js"보다 "Express"가 선호되지만, "Express.js"도 허용됩니다.
-
-### libuv
-
-비동기식 I/O에 초점을 둔 멀티플랫폼 지원 라이브러리이며, 주로 Node.js에 의해 사용되도록 개발됩니다.
-
-### middleware
-
-최종 요청 핸들러 이전의 Express 라우팅 계층에 의해 호출되는 함수이며, 따라서 원시 요청과 의도된 최종 라우트 사이의 미들웨어에 위치합니다. 미들웨어와 관련된 용어의 몇 가지 요점은 다음과 같습니다.
-
-- `var foo = require('middleware')`는 Node.js 모듈을 _요구_ 또는 _사용_하는 것으로 일컬어집니다. 이후 `var mw = foo()` 명령문은 일반적으로 미들웨어를 리턴합니다.
-- `app.use(mw)`는 _미들웨어를 전역 처리 스택에 추가_하는 것으로 일컬어집니다.
-- `app.get('/foo', mw, function (req, res) { ... })`는 _미들웨어를 "GET /foo" 처리 스택에 추가_하는 것으로 일컬어집니다.
-
-### Node.js
-
-확장 가능한 네트워크 애플리케이션을 개발하는 데 사용되는 소프트웨어 플랫폼입니다. Node.js는 JavaScript를 스크립팅 언어로 사용하며, 방해하지 않는 I/O 및 단일 스레드 이벤트 루프를 통해 높은 처리량을 달성합니다. [nodejs.org](http://nodejs.org/)를 참조하십시오. **활용 참고**: 최초에는 "Node.js"였으며 이후 "Node"가 되었습니다.
-
-### 오픈 소스(open-source, open source)
-
-When used as an adjective, hyphenate; for example: "This is open-source software." (예: "이 소프트웨어는 오픈 소스 소프트웨어입니다" [Wikipedia의 Open-source software](http://en.wikipedia.org/wiki/Open-source_software)를 참조하십시오.)
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### 요청(request)
-
-HTTP 요청입니다. 클라이언트는 HTTP 요청 메시지를 서버에 제출하며, 서버는 응답을 리턴합니다.  요청은 여러 [요청 메소드](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) 중 하나를 사용해야 합니다(예: GET, POST 등).
-
-### 응답(response)
-
-HTTP 응답입니다. 서버는 HTTP 응답 메시지를 클라이언트에 리턴합니다. 응답에는 요청에 대한 완료 상태 정보가 포함되어 있으며 응답 메시지 본문에는 요청된 컨텐츠가 포함되어 있을 수도 있습니다.
-
-### 라우트(route)
-
-자원을 식별하는 URL의 일부입니다. 예를 들면, `http://foo.com/products/id`에서 "/products/id"가 라우트입니다.
-
-### 라우터(router)
-
-API 참조의 [라우터](/{{ page.lang }}/4x/api.html#router)를 참조하십시오.
diff --git a/ko/resources/middleware.md b/ko/resources/middleware.md
deleted file mode 100644
index 24e25e3986..0000000000
--- a/ko/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Express 미들웨어
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Express 미들웨어
-
-목록에 적힌 Express 미들웨어 모듈들은 [Expressjs 팀](https://github.com/orgs/expressjs/people)이 유지보수합니다.
-
-| 미들웨어 모듈                                                                     | 설명                                                                                                                    |
-| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | HTTP 요청 body를 파싱합니다.                                                                                  |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | HTTP 요청들을 압축합니다.                                                                                      |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | 고유한 요청 ID를 생성합니다.                                                                                     |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | 쿠키 헤더를 파싱하고 `req.cookies`에 할당합니다. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | 쿠키 기반의 세션을 만듭니다.                                                                                      |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | 다양한 옵션들을 이용하여 Cross-origin resource sharing (CORS)를 활성화합니다.                        |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | 개발 중에 발생하는 에러를 핸들링하고 디버깅합니다.                                                                          |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | 헤더를 이용해 HTTP method를 덮어씁니다.                                                                           |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP 요청 로그를 남깁니다.                                                                                     |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | multi-part 폼 데이터를 처리합니다.                                                                              |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | 응답 시간을 기록합니다.                                                                                         |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                      |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | 주어진 경로의 디렉토리 리스트를 제공합니다.                                                                              |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | 정적 파일을 제공합니다.                                                                                         |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | 서버 기반의 세션을 만듭니다 (개발 전용).                                                           |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                           |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | 가상 도메인을 만듭니다.                                                                                         |
-
-## 추가 미들웨어 모듈
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| 미들웨어 모듈                                             | 설명                                                                                                                                                        |
-| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet)        | 다양한 HTTP 헤더를 설정해 앱이 안전하게 도와줍니다.                                                                                                           |
-| [passport](https://github.com/jaredhanson/passport) | OAuth, OpenID 같은 방법들을 사용하는 인증 체계입니다.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/ko/resources/middleware/body-parser.md b/ko/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/ko/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/ko/resources/middleware/compression.md b/ko/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/ko/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/ko/resources/middleware/connect-rid.md b/ko/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/ko/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/ko/resources/middleware/cookie-parser.md b/ko/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/ko/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/ko/resources/middleware/cookie-session.md b/ko/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/ko/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/ko/resources/middleware/cors.md b/ko/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/ko/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/ko/resources/middleware/errorhandler.md b/ko/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/ko/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/ko/resources/middleware/method-override.md b/ko/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/ko/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/ko/resources/middleware/morgan.md b/ko/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/ko/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/ko/resources/middleware/multer.md b/ko/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/ko/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/ko/resources/middleware/response-time.md b/ko/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/ko/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/ko/resources/middleware/serve-favicon.md b/ko/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/ko/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/ko/resources/middleware/serve-index.md b/ko/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/ko/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/ko/resources/middleware/serve-static.md b/ko/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/ko/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/ko/resources/middleware/session.md b/ko/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/ko/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/ko/resources/middleware/timeout.md b/ko/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/ko/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/ko/resources/middleware/vhost.md b/ko/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/ko/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/ko/resources/utils.md b/ko/resources/utils.md
deleted file mode 100644
index fe36da50f2..0000000000
--- a/ko/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | 설명                                                                                                                                                                                                                         |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/ko/starter/basic-routing.md b/ko/starter/basic-routing.md
deleted file mode 100644
index d428de6877..0000000000
--- a/ko/starter/basic-routing.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: Express 기본 라우팅
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# 기본 라우팅
-
-_라우팅_은 URI(또는 경로) 및 특정한 HTTP 요청 메소드(GET, POST 등)인 특정 엔드포인트에 대한 클라이언트 요청에 애플리케이션이 응답하는 방법을 결정하는 것을 말합니다.
-
-각 라우트는 하나 이상의 핸들러 함수를 가질 수 있으며, 이러한 함수는 라우트가 일치할 때 실행됩니다.
-
-라우트 정의에는 다음과 같은 구조가 필요합니다.
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-여기서,
-
-- `app`은 `express`의 인스턴스입니다.
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH`는 서버에서의 경로입니다.
-- `HANDLER`는 라우트가 일치할 때 실행되는 함수입니다.
-
-<div class="doc-box doc-notice" markdown="1">
-이 학습서에서는 `app`이라는 이름의 `express` 인스턴스가 작성되며 서버가 실행 중인 것으로 가정합니다. 앱의 작성 및 시작에 익숙하지 않은 경우에는 [Hello world 예제](/{{ page.lang }}/starter/hello-world.html)를 참조하십시오.
-</div>
-
-다음 예에서는 간단한 라우트의 정의를 설명합니다.
-
-홈 페이지에서 `Hello World!`로 응답:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-`/user` 라우트에 대한 PUT 요청에 응답:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-`/user` 라우트에 대한 DELETE 요청에 응답:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-라우팅에 대한 자세한 내용을 확인하려면 [라우팅 안내서](/{{ page.lang }}/guide/routing.html)를 참조하십시오.
-
diff --git a/ko/starter/examples.md b/ko/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/ko/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/ko/starter/faq.md b/ko/starter/faq.md
deleted file mode 100644
index eb2d3c48a8..0000000000
--- a/ko/starter/faq.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-layout: page
-title: Express 자주 묻는 질문(FAQ)
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# 자주 묻는 질문(FAQ)
-
-## 애플리케이션을 어떻게 구조화해야 합니까?
-
-이 질문에는 정확한 답이 없습니다. 그 답은
-애플리케이션의 규모 및 참여하는 팀의 규모에 따라 달라질 수 있습니다. 최대한의
-유연성을 유지하기 위하여, Express에는 구조에 대한 전제 조건이 없습니다.
-
-라우트 및 기타 애플리케이션 특정 로직은 원하는 많큼 많은 파일에 존재할 수 있으며,
-선호하는 모든 디렉토리 구조에 존재할 수 있습니다. 도움을 받으려면
-다음의 예를 확인하십시오.
-
-- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-또한, 이러한 패턴을 간략화할 수 있는 다음과 같은 Express용 써드파티 확장기능이 존재합니다.
-
-- [Resourceful routing](https://github.com/expressjs/express-resource)
-
-## 모델을 어떻게 정의해야 합니까?
-
-Express에는 데이터베이스의 개념이 없습니다. 이러한 개념은
-써드파티 Node 모듈에 따라 달라지며, 따라서 개발자는
-거의 모든 데이터베이스를 사용할 수 있습니다.
-
-모델 중심의 Express 기반 프레임워크에 대해서는 [LoopBack](http://loopback.io)을 참조하십시오.
-
-## 어떻게 사용자를 인증할 수 있습니까?
-
-인증은 또 다른 주관적인 영역이며, Express는
-이에 관여하지 않습니다. 개발자는 자신이 원하는 어떠한 인증 체계라도 사용할 수 있습니다.
-사용자 이름 / 비밀번호 체계에 대해서는 [이 예제](https://github.com/expressjs/express/tree/master/examples/auth)를 참조하십시오.
-
-## Express는 어느 템플리트 엔진을 지원합니까?
-
-Express는 `(path, locals, callback)` 시그니처를 준수하는 모든 템플리트 엔진을 지원합니다.
-템플리트 엔진 인터페이스 및 캐싱을 정규화하려면
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-프로젝트를 참조하여 지원을 받으십시오. 목록에 포함되지 않은 템플리트 엔진이 Express 시그니처를 지원할 수도 있습니다.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## 404 응답을 어떻게 처리해야 합니까?
-
-Express에서 404 응답은 오류로 인해 발생하는 결과가 아니며, 따라서
-오류 핸들러(error-handler) 미들웨어는 이를 파악하지 않습니다. 이렇게 작동하는 이유는
-404 응답은 단순히 실행해야 할 추가적인 작업이 없다는 것,
-즉 Express는 모든 미들웨어 함수 및 라우트를 실행했으며 이들 중 어느 것도
-응답하지 않았다는 것을 나타내기 때문입니다. 이를 처리하려면
-다음과 같이 404 응답을 처리하기 위한 미들웨어 함수를 스택의 가장 아래(다른 모든 함수의 아래)에
-추가하기만 하면 됩니다.
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## 오류 핸들러를 어떻게 설정해야 합니까?
-
-오류 처리 미들웨어는 다른 미들웨어와 동일한 방식으로 정의할 수 있지만,
-다음과 같이 오류 처리 함수는 3개가 아닌 4개의 인수, 구체적으로 말하면 `(err, req, res, next)` 시그니처를 갖는다는 점이 다릅니다.
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-자세한 정보는 [오류 처리](/{{ page.lang }}/guide/error-handling.html)를 참조하십시오.
-
-## 일반적인 HTML은 어떻게 렌더링해야 합니까?
-
-렌더링할 필요가 없습니다! `res.render()` 함수를 이용해 HTML을 "렌더링"할 필요는 없습니다.
-특정한 파일을 렌더링해야 하는 경우에는 `res.sendFile()` 함수를 사용하십시오.
-하나의 디렉토리에서 여러 자산을 제공하는 경우에는 `express.static()`
-미들웨어 함수를 사용하십시오.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/ko/starter/generator.md b/ko/starter/generator.md
deleted file mode 100644
index adbf59aa75..0000000000
--- a/ko/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Express 애플리케이션 생성기
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Express 애플리케이션 생성기
-
-애플리케이션의 골격을 신속하게 작성하려면 애플리케이션 생성기 도구인 `express`를 사용하십시오.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-다음과 같이 `-h` 옵션을 이용해 명령의 옵션을 표시하십시오.
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-예를 들면, 다음의 예에서는 _myapp_라는 이름의 Express 앱을 현재 작업 디렉토리에 작성합니다. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-이후 다음과 같이 종속 항목을 설치하십시오.
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-MacOS 또는 Linux에서는 다음 명령을 사용하여 앱을 실행하십시오.
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-Windows에서는 다음 명령을 사용하십시오.
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-다음의 명령을 이용해 `express`를 설치하십시오.
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-이후 브라우저에서 `http://localhost:3000/`을 로드하여 앱에 액세스하십시오.
-
-생성된 앱은 다음과 같은 디렉토리 구조를 갖습니다.
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-생성기에 의해 작성된 앱 구조는 Express 앱을 구조화하는 여러 방법 중 하나에 불과합니다. 이러한 구조를 사용하거나 사용자의 요구사항에 가장 적합하도록 구조를 수정하십시오.
-</div>
\ No newline at end of file
diff --git a/ko/starter/hello-world.md b/ko/starter/hello-world.md
deleted file mode 100644
index 95616e7ea5..0000000000
--- a/ko/starter/hello-world.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-layout: page
-title: Express "Hello World" 예제
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Hello world 예제
-
-<div class="doc-box doc-info" markdown="1">
-기본적으로 이 앱은 여러분이 작성할 수 있는 가장 간단한 Express 앱일 것입니다. 이 앱은 하나의 파일로 된 앱이며 [Express 생성기](/{{ page.lang }}/starter/generator.html)를 통해 얻게 되는 앱과는 같지 *않습니다*. (이 예제와 달리 Express 생성기를 통해 얻게 되는 앱은 다양한 목적을 위한 여러 JavaScript 파일, Jade 템플리트 및 하위 디렉토리를 포함하는 전체 앱에 대한 스캐폴딩을 작성합니다.)
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-앱은 서버를 시작하며 3000번 포트에서 연결을 청취합니다. 앱은 루트 URL(`/`) 또는 _라우트_에
-대한 요청에 "Hello World!"로 응답합니다. 다른 모든 경로에 대해서는 **404 Not Found**로 응답합니다.
-
-### Running Locally
-
-먼저, `myapp`이라는 이름의 디렉토리를 작성한 후 이 디렉토리로 이동하여 `npm init`를 실행하십시오. 이후 [설치 안내서](/{{ page.lang }}/starter/installing.html)에 따라 `express`를 종속 항목으로서 설치하십시오.
-
-`myapp` 디렉토리에 `app.js`라는 이름의 파일을 작성한 후 다음과 같은 코드를 추가하십시오.
-
-<div class="doc-box doc-notice" markdown="1">
-`req`(요청) 및 `res`(응답)는 Node가 제공하는 동일한 오브젝트이며, 따라서
-`req.pipe()`, `req.on('data', callback)` 그리고 Express의 관여가 필요 없는 다른 모든 항목을 호출할 수 있습니다.
-</div>
-
-다음의 명령을 이용하여 앱을 실행하십시오.
-
-```bash
-$ node app.js
-```
-
-이후 브라우저에서 [http://localhost:3000/](http://localhost:3000/)을 로드하여 결과물을 확인하십시오.
\ No newline at end of file
diff --git a/ko/starter/installing.md b/ko/starter/installing.md
deleted file mode 100644
index d25acf062c..0000000000
--- a/ko/starter/installing.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-layout: page
-title: Express 설치
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# 설치
-
-[Node.js](https://nodejs.org/)가 이미 설치되었다고 가정한 상태에서, 애플리케이션을 보관할 디렉토리를 작성하고 그 디렉토리를 작업 디렉토리로 설정하십시오.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-`npm init` 명령을 이용하여 애플리케이션에 대한 `package.json` 파일을 작성하십시오.
-`package.json`의 작동 원리에 대한 자세한 정보는 [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json)을 참조하십시오.
-
-```bash
-$ npm init
-```
-
-이 명령을 실행하면 애플리케이션의 이름 및 버전과 같은 몇 가지 정보에 대해 프롬프트합니다.
-지금은 다음의 항목을 제외한 대부분의 항목에서 ENTER 키를 눌러 기본값을 수락할 수 있습니다.
-
-```
-entry point: (index.js)
-```
-
-기본 파일의 이름을 `app.js`로 입력하거나 자유롭게 입력하십시오. 기본 파일의 이름을 `index.js`로 입력하기 원하는 경우에는 ENTER 키를 눌러 제안된 기본 파일 이름을 수락하십시오.
-
-이제 `myapp` 디렉토리에 Express를 설치한 후 종속 항목 목록에 저장하십시오. 예를 들면 다음과 같습니다.
-
-```bash
-$ npm install express
-```
-
-Express를 임시로 설치하고 종속 항목 목록에 추가하지 않으려면, 다음과 같이 `--save` 옵션을 생략하십시오.
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-`--save` 옵션을 통해 설치된 Node 모듈은 `package.json` 파일 내의 `dependencies` 목록에 추가됩니다. 이후 `app` 디렉토리에서 `npm install`을 실행하면 종속 항목 목록 내의 모듈이 자동으로 설치됩니다.
-</div>
\ No newline at end of file
diff --git a/ko/starter/static-files.md b/ko/starter/static-files.md
deleted file mode 100644
index 847de1f3e7..0000000000
--- a/ko/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: Express에서 정적 파일 제공
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Express에서 정적 파일 제공
-
-이미지, CSS 파일 및 JavaScript 파일과 같은 정적 파일을 제공하려면 Express의 기본 제공 미들웨어 함수인 `express.static`을 사용하십시오.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-예를 들면, 다음과 같은 코드를 이용하여 `public`이라는 이름의 디렉토리에 포함된 이미지, CSS 파일 및 JavaScript 파일을 제공하십시오.
-
-```js
-app.use(express.static('public'))
-```
-
-이제 다음과 같이 `public` 디렉토리에 포함된 파일을 로드할 수 있습니다.
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express는 정적 디렉토리에 대해 상대적으로 파일을 검색하며, 따라서 정적 디렉토리의 이름은 URL의 일부가 아닙니다.
-</div>
-
-여러 개의 정적 자산 디렉토리를 이용하려면 다음과 같이 `express.static` 미들웨어 함수를 여러 번 호출하십시오.
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express는 `express.static` 미들웨어 함수를 이용해 정적 디렉토리를 설정한 순서대로 파일을 검색합니다.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-이제 `/static` 경로 접두부를 통해 `public` 디렉토리에 포함된 파일을 로드할 수 있습니다.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-그러나 `express.static` 함수에 제공되는 경로는 `node` 프로세스가 실행되는 디렉토리에 대해 상대적입니다. Express 앱을 다른 디렉토리에서 실행하는 경우에는 다음과 같이 제공하기 원하는 디렉토리의 절대 경로를 사용하는 것이 더 안전합니다.
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/ko/support/index.md b/ko/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/ko/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/netlify.toml b/netlify.toml
new file mode 100644
index 0000000000..72ac9b9d5f
--- /dev/null
+++ b/netlify.toml
@@ -0,0 +1,6 @@
+[build]
+  command = "npm run build"
+  publish = "dist"
+
+[build.environment]
+  NODE_OPTIONS = "--max-old-space-size=4096"
diff --git a/package-lock.json b/package-lock.json
index 1786982f4f..d5c7b48b19 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,893 +1,9002 @@
 {
-  "name": "expressjs.com",
-  "version": "0.0.0",
+  "name": "expressjs-website",
+  "version": "0.0.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
-      "name": "expressjs.com",
-      "version": "0.0.0",
+      "name": "expressjs-website",
+      "license": "CC-BY-SA-4.0",
+      "dependencies": {
+        "@astrojs/mdx": "^5.0.3",
+        "@astrojs/react": "^5.0.2",
+        "@astrojs/rss": "^4.0.18",
+        "@astrojs/sitemap": "^3.7.2",
+        "@orama/core": "^1.2.19",
+        "@orama/ui": "^1.5.4",
+        "astro": "^6.1.2",
+        "astro-expressive-code": "^0.41.7",
+        "astro-icon": "^1.1.5",
+        "gray-matter": "^4.0.3",
+        "mdast-util-from-markdown": "^2.0.3",
+        "mdast-util-to-string": "^4.0.0",
+        "react": "^19.2.4",
+        "react-dom": "^19.2.4",
+        "rehype-autolink-headings": "^7.1.0",
+        "rehype-slug": "^6.0.0",
+        "satori": "^0.26.0",
+        "sharp": "^0.34.5",
+        "unist-util-visit": "^5.1.0"
+      },
       "devDependencies": {
-        "eslint": "^8.54.0",
-        "eslint-config-standard": "^17.1.0",
-        "eslint-plugin-import": "^2.32.0",
-        "eslint-plugin-markdown": "^2.2.1",
-        "eslint-plugin-n": "^15.0.0",
-        "eslint-plugin-promise": "^6.6.0"
+        "@csstools/postcss-global-data": "^4.0.0",
+        "@eslint/js": "^9.39.2",
+        "@iconify-json/fluent": "^1.2.41",
+        "@playwright/test": "^1.59.1",
+        "@types/node": "^25.3.2",
+        "@types/react": "^19.2.14",
+        "@types/react-dom": "^19.2.3",
+        "eslint": "^9.39.2",
+        "eslint-config-prettier": "^10.1.8",
+        "eslint-plugin-astro": "^1.5.0",
+        "eslint-plugin-jsx-a11y": "^6.10.2",
+        "globals": "^17.4.0",
+        "husky": "^9.1.7",
+        "lint-staged": "^16.2.7",
+        "postcss-custom-media": "^12.0.0",
+        "postcss-nested": "^7.0.2",
+        "prettier": "^3.8.1",
+        "prettier-plugin-astro": "^0.14.1",
+        "typescript": "^5.9.3",
+        "typescript-eslint": "^8.53.1",
+        "unplugin-icons": "^23.0.1",
+        "vite-plugin-svgr": "^4.5.0"
+      }
+    },
+    "node_modules/@antfu/install-pkg": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@antfu/install-pkg/-/install-pkg-1.1.0.tgz",
+      "integrity": "sha512-MGQsmw10ZyI+EJo45CdSER4zEb+p31LpDAFp2Z3gkSd1yqVZGi0Ebx++YTEMonJy4oChEMLsxZ64j8FH6sSqtQ==",
+      "license": "MIT",
+      "dependencies": {
+        "package-manager-detector": "^1.3.0",
+        "tinyexec": "^1.0.1"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/antfu"
       }
     },
-    "node_modules/@eslint-community/eslint-utils": {
-      "version": "4.4.0",
-      "resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.4.0.tgz",
-      "integrity": "sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==",
+    "node_modules/@antfu/utils": {
+      "version": "8.1.1",
+      "resolved": "https://registry.npmjs.org/@antfu/utils/-/utils-8.1.1.tgz",
+      "integrity": "sha512-Mex9nXf9vR6AhcXmMrlz/HVgYYZpVGJ6YlPgwl7UnaFpnshXs6EK/oa5Gpf3CzENMjkvEx2tQtntGnb7UtSTOQ==",
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/antfu"
+      }
+    },
+    "node_modules/@astrojs/compiler": {
+      "version": "2.13.0",
+      "resolved": "https://registry.npmjs.org/@astrojs/compiler/-/compiler-2.13.0.tgz",
+      "integrity": "sha512-mqVORhUJViA28fwHYaWmsXSzLO9osbdZ5ImUfxBarqsYdMlPbqAqGJCxsNzvppp1BEzc1mJNjOVvQqeDN8Vspw==",
       "dev": true,
       "license": "MIT",
+      "peer": true
+    },
+    "node_modules/@astrojs/internal-helpers": {
+      "version": "0.8.0",
+      "resolved": "https://registry.npmjs.org/@astrojs/internal-helpers/-/internal-helpers-0.8.0.tgz",
+      "integrity": "sha512-J56GrhEiV+4dmrGLPNOl2pZjpHXAndWVyiVDYGDuw6MWKpBSEMLdFxHzeM/6sqaknw9M+HFfHZAcvi3OfT3D/w==",
+      "license": "MIT",
       "dependencies": {
-        "eslint-visitor-keys": "^3.3.0"
-      },
-      "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
-      },
-      "peerDependencies": {
-        "eslint": "^6.0.0 || ^7.0.0 || >=8.0.0"
+        "picomatch": "^4.0.3"
       }
     },
-    "node_modules/@eslint-community/regexpp": {
-      "version": "4.10.1",
-      "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.10.1.tgz",
-      "integrity": "sha512-Zm2NGpWELsQAD1xsJzGQpYfvICSsFkEpU0jxBjfdC6uNEWXcHnfs9hScFWtXVDVl+rBQJGrl4g1vcKIejpH9dA==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark": {
+      "version": "7.1.0",
+      "resolved": "https://registry.npmjs.org/@astrojs/markdown-remark/-/markdown-remark-7.1.0.tgz",
+      "integrity": "sha512-P+HnCsu2js3BoTc8kFmu+E9gOcFeMdPris75g+Zl4sY8+bBRbSQV6xzcBDbZ27eE7yBGEGQoqjpChx+KJYIPYQ==",
       "license": "MIT",
-      "engines": {
-        "node": "^12.0.0 || ^14.0.0 || >=16.0.0"
+      "dependencies": {
+        "@astrojs/internal-helpers": "0.8.0",
+        "@astrojs/prism": "4.0.1",
+        "github-slugger": "^2.0.0",
+        "hast-util-from-html": "^2.0.3",
+        "hast-util-to-text": "^4.0.2",
+        "js-yaml": "^4.1.1",
+        "mdast-util-definitions": "^6.0.0",
+        "rehype-raw": "^7.0.0",
+        "rehype-stringify": "^10.0.1",
+        "remark-gfm": "^4.0.1",
+        "remark-parse": "^11.0.0",
+        "remark-rehype": "^11.1.2",
+        "remark-smartypants": "^3.0.2",
+        "retext-smartypants": "^6.2.0",
+        "shiki": "^4.0.0",
+        "smol-toml": "^1.6.0",
+        "unified": "^11.0.5",
+        "unist-util-remove-position": "^5.0.0",
+        "unist-util-visit": "^5.1.0",
+        "unist-util-visit-parents": "^6.0.2",
+        "vfile": "^6.0.3"
       }
     },
-    "node_modules/@eslint/eslintrc": {
-      "version": "2.1.4",
-      "resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-2.1.4.tgz",
-      "integrity": "sha512-269Z39MS6wVJtsoUl10L60WdkhJVdPG24Q4eZTH3nnF6lpvSShEK3wQjDX9JRWAUPvPh7COouPpU9IrqaZFvtQ==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/core": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/core/-/core-4.0.2.tgz",
+      "integrity": "sha512-hxT0YF4ExEqB8G/qFdtJvpmHXBYJ2lWW7qTHDarVkIudPFE6iCIrqdgWxGn5s+ppkGXI0aEGlibI0PAyzP3zlw==",
       "license": "MIT",
       "dependencies": {
-        "ajv": "^6.12.4",
-        "debug": "^4.3.2",
-        "espree": "^9.6.0",
-        "globals": "^13.19.0",
-        "ignore": "^5.2.0",
-        "import-fresh": "^3.2.1",
-        "js-yaml": "^4.1.0",
-        "minimatch": "^3.1.2",
-        "strip-json-comments": "^3.1.1"
+        "@shikijs/primitive": "4.0.2",
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4",
+        "hast-util-to-html": "^9.0.5"
       },
       "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
-      },
-      "funding": {
-        "url": "https://opencollective.com/eslint"
+        "node": ">=20"
       }
     },
-    "node_modules/@eslint/js": {
-      "version": "8.57.0",
-      "resolved": "https://registry.npmjs.org/@eslint/js/-/js-8.57.0.tgz",
-      "integrity": "sha512-Ys+3g2TaW7gADOJzPt83SJtCDhMjndcDMFVQ/Tj9iA1BfJzFKD9mAUXT3OenpuPHbI6P/myECxRJrofUsDx/5g==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/engine-javascript": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-javascript/-/engine-javascript-4.0.2.tgz",
+      "integrity": "sha512-7PW0Nm49DcoUIQEXlJhNNBHyoGMjalRETTCcjMqEaMoJRLljy1Bi/EGV3/qLBgLKQejdspiiYuHGQW6dX94Nag==",
       "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "oniguruma-to-es": "^4.3.4"
+      },
       "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+        "node": ">=20"
       }
     },
-    "node_modules/@humanwhocodes/config-array": {
-      "version": "0.11.14",
-      "resolved": "https://registry.npmjs.org/@humanwhocodes/config-array/-/config-array-0.11.14.tgz",
-      "integrity": "sha512-3T8LkOmg45BV5FICb15QQMsyUSWrQ8AygVfC7ZG32zOalnqrilm018ZVCw0eapXux8FtA33q8PSRSstjee3jSg==",
-      "deprecated": "Use @eslint/config-array instead",
-      "dev": true,
-      "license": "Apache-2.0",
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/engine-oniguruma": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-oniguruma/-/engine-oniguruma-4.0.2.tgz",
+      "integrity": "sha512-UpCB9Y2sUKlS9z8juFSKz7ZtysmeXCgnRF0dlhXBkmQnek7lAToPte8DkxmEYGNTMii72zU/lyXiCB6StuZeJg==",
+      "license": "MIT",
       "dependencies": {
-        "@humanwhocodes/object-schema": "^2.0.2",
-        "debug": "^4.3.1",
-        "minimatch": "^3.0.5"
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2"
       },
       "engines": {
-        "node": ">=10.10.0"
+        "node": ">=20"
       }
     },
-    "node_modules/@humanwhocodes/module-importer": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz",
-      "integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==",
-      "dev": true,
-      "license": "Apache-2.0",
-      "engines": {
-        "node": ">=12.22"
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/langs": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/langs/-/langs-4.0.2.tgz",
+      "integrity": "sha512-KaXby5dvoeuZzN0rYQiPMjFoUrz4hgwIE+D6Du9owcHcl6/g16/yT5BQxSW5cGt2MZBz6Hl0YuRqf12omRfUUg==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2"
       },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/nzakas"
+      "engines": {
+        "node": ">=20"
       }
     },
-    "node_modules/@humanwhocodes/object-schema": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/@humanwhocodes/object-schema/-/object-schema-2.0.3.tgz",
-      "integrity": "sha512-93zYdMES/c1D69yZiKDBj0V24vqNzB/koF26KPaagAfd3P/4gUlh3Dys5ogAK+Exi9QyzlD8x/08Zt7wIKcDcA==",
-      "deprecated": "Use @eslint/object-schema instead",
-      "dev": true,
-      "license": "BSD-3-Clause"
-    },
-    "node_modules/@nodelib/fs.scandir": {
-      "version": "2.1.5",
-      "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
-      "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/themes": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/themes/-/themes-4.0.2.tgz",
+      "integrity": "sha512-mjCafwt8lJJaVSsQvNVrJumbnnj1RI8jbUKrPKgE6E3OvQKxnuRoBaYC51H4IGHePsGN/QtALglWBU7DoKDFnA==",
       "license": "MIT",
       "dependencies": {
-        "@nodelib/fs.stat": "2.0.5",
-        "run-parallel": "^1.1.9"
+        "@shikijs/types": "4.0.2"
       },
       "engines": {
-        "node": ">= 8"
+        "node": ">=20"
       }
     },
-    "node_modules/@nodelib/fs.stat": {
-      "version": "2.0.5",
-      "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
-      "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark/node_modules/@shikijs/types": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/types/-/types-4.0.2.tgz",
+      "integrity": "sha512-qzbeRooUTPnLE+sHD/Z8DStmaDgnbbc/pMrU203950aRqjX/6AFHeDYT+j00y2lPdz0ywJKx7o/7qnqTivtlXg==",
       "license": "MIT",
+      "dependencies": {
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      },
       "engines": {
-        "node": ">= 8"
+        "node": ">=20"
       }
     },
-    "node_modules/@nodelib/fs.walk": {
-      "version": "1.2.8",
-      "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
-      "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
-      "dev": true,
+    "node_modules/@astrojs/markdown-remark/node_modules/shiki": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/shiki/-/shiki-4.0.2.tgz",
+      "integrity": "sha512-eAVKTMedR5ckPo4xne/PjYQYrU3qx78gtJZ+sHlXEg5IHhhoQhMfZVzetTYuaJS0L2Ef3AcCRzCHV8T0WI6nIQ==",
       "license": "MIT",
       "dependencies": {
-        "@nodelib/fs.scandir": "2.1.5",
-        "fastq": "^1.6.0"
+        "@shikijs/core": "4.0.2",
+        "@shikijs/engine-javascript": "4.0.2",
+        "@shikijs/engine-oniguruma": "4.0.2",
+        "@shikijs/langs": "4.0.2",
+        "@shikijs/themes": "4.0.2",
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
       },
       "engines": {
-        "node": ">= 8"
+        "node": ">=20"
       }
     },
-    "node_modules/@rtsao/scc": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/@rtsao/scc/-/scc-1.1.0.tgz",
-      "integrity": "sha512-zt6OdqaDoOnJ1ZYsCYGt9YmWzDXl4vQdKTyJev62gFhRGKdx7mcT54V9KIjg+d2wi9EXsPvAPKe7i7WjfVWB8g==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/@types/json5": {
-      "version": "0.0.29",
-      "resolved": "https://registry.npmjs.org/@types/json5/-/json5-0.0.29.tgz",
-      "integrity": "sha512-dRLjCWHYg4oaA77cxO64oO+7JwCwnIzkZPdrrC71jQmQtlhM556pwKo5bUzqvZndkVbeFLIIi+9TC40JNF5hNQ==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/@types/mdast": {
-      "version": "3.0.15",
-      "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-3.0.15.tgz",
-      "integrity": "sha512-LnwD+mUEfxWMa1QpDraczIn6k0Ee3SMicuYSSzS6ZYl2gKS09EClnJYGd8Du6rfc5r/GZEk5o1mRb8TaTj03sQ==",
-      "dev": true,
+    "node_modules/@astrojs/mdx": {
+      "version": "5.0.3",
+      "resolved": "https://registry.npmjs.org/@astrojs/mdx/-/mdx-5.0.3.tgz",
+      "integrity": "sha512-zv/OlM5sZZvyjHqJjR3FjJvoCgbxdqj3t4jO/gSEUNcck3BjdtMgNQw8UgPfAGe4yySdG4vjZ3OC5wUxhu7ckg==",
       "license": "MIT",
       "dependencies": {
-        "@types/unist": "^2"
+        "@astrojs/markdown-remark": "7.1.0",
+        "@mdx-js/mdx": "^3.1.1",
+        "acorn": "^8.16.0",
+        "es-module-lexer": "^2.0.0",
+        "estree-util-visit": "^2.0.0",
+        "hast-util-to-html": "^9.0.5",
+        "piccolore": "^0.1.3",
+        "rehype-raw": "^7.0.0",
+        "remark-gfm": "^4.0.1",
+        "remark-smartypants": "^3.0.2",
+        "source-map": "^0.7.6",
+        "unist-util-visit": "^5.1.0",
+        "vfile": "^6.0.3"
+      },
+      "engines": {
+        "node": ">=22.12.0"
+      },
+      "peerDependencies": {
+        "astro": "^6.0.0"
       }
     },
-    "node_modules/@types/unist": {
-      "version": "2.0.10",
-      "resolved": "https://registry.npmjs.org/@types/unist/-/unist-2.0.10.tgz",
-      "integrity": "sha512-IfYcSBWE3hLpBg8+X2SEa8LVkJdJEkT2Ese2aaLs3ptGdVtABxndrMaxuFlQ1qdFf9Q5rDvDpxI3WwgvKFAsQA==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/@ungap/structured-clone": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/@ungap/structured-clone/-/structured-clone-1.2.0.tgz",
-      "integrity": "sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==",
-      "dev": true,
-      "license": "ISC"
-    },
-    "node_modules/acorn": {
-      "version": "8.12.0",
-      "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.12.0.tgz",
-      "integrity": "sha512-RTvkC4w+KNXrM39/lWCUaG0IbRkWdCv7W/IOW9oU6SawyxulvkQy5HQPVTKxEjczcUvapcrw3cFx/60VN/NRNw==",
-      "dev": true,
+    "node_modules/@astrojs/prism": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/@astrojs/prism/-/prism-4.0.1.tgz",
+      "integrity": "sha512-nksZQVjlferuWzhPsBpQ1JE5XuKAf1id1/9Hj4a9KG4+ofrlzxUUwX4YGQF/SuDiuiGKEnzopGOt38F3AnVWsQ==",
       "license": "MIT",
-      "bin": {
-        "acorn": "bin/acorn"
+      "dependencies": {
+        "prismjs": "^1.30.0"
       },
       "engines": {
-        "node": ">=0.4.0"
+        "node": ">=22.12.0"
       }
     },
-    "node_modules/acorn-jsx": {
-      "version": "5.3.2",
-      "resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
-      "integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
-      "dev": true,
+    "node_modules/@astrojs/react": {
+      "version": "5.0.2",
+      "resolved": "https://registry.npmjs.org/@astrojs/react/-/react-5.0.2.tgz",
+      "integrity": "sha512-BDpPrapV3Wgp9sD7aTMvP+ORH0jFEue9OmkBu98KcBbTlsQCnvisDW3m7PQrMptXwEDlX5HGfP/CHmkEVY2tZA==",
       "license": "MIT",
+      "dependencies": {
+        "@astrojs/internal-helpers": "0.8.0",
+        "@vitejs/plugin-react": "^5.2.0",
+        "devalue": "^5.6.4",
+        "ultrahtml": "^1.6.0",
+        "vite": "^7.3.1"
+      },
+      "engines": {
+        "node": ">=22.12.0"
+      },
       "peerDependencies": {
-        "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
+        "@types/react": "^17.0.50 || ^18.0.21 || ^19.0.0",
+        "@types/react-dom": "^17.0.17 || ^18.0.6 || ^19.0.0",
+        "react": "^17.0.2 || ^18.0.0 || ^19.0.0",
+        "react-dom": "^17.0.2 || ^18.0.0 || ^19.0.0"
       }
     },
-    "node_modules/ajv": {
-      "version": "6.12.6",
-      "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.12.6.tgz",
-      "integrity": "sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==",
-      "dev": true,
+    "node_modules/@astrojs/rss": {
+      "version": "4.0.18",
+      "resolved": "https://registry.npmjs.org/@astrojs/rss/-/rss-4.0.18.tgz",
+      "integrity": "sha512-wc5DwKlbTEdgVAWnHy8krFTeQ42t1v/DJqeq5HtulYK3FYHE4krtRGjoyhS3eXXgfdV6Raoz2RU3wrMTFAitRg==",
       "license": "MIT",
       "dependencies": {
-        "fast-deep-equal": "^3.1.1",
-        "fast-json-stable-stringify": "^2.0.0",
-        "json-schema-traverse": "^0.4.1",
-        "uri-js": "^4.2.2"
-      },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/epoberezkin"
+        "fast-xml-parser": "^5.5.7",
+        "piccolore": "^0.1.3",
+        "zod": "^4.3.6"
       }
     },
-    "node_modules/ansi-regex": {
-      "version": "5.0.1",
-      "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz",
-      "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==",
-      "dev": true,
+    "node_modules/@astrojs/sitemap": {
+      "version": "3.7.2",
+      "resolved": "https://registry.npmjs.org/@astrojs/sitemap/-/sitemap-3.7.2.tgz",
+      "integrity": "sha512-PqkzkcZTb5ICiyIR8VoKbIAP/laNRXi5tw616N1Ckk+40oNB8Can1AzVV56lrbC5GKSZFCyJYUVYqVivMisvpA==",
       "license": "MIT",
-      "engines": {
-        "node": ">=8"
+      "dependencies": {
+        "sitemap": "^9.0.0",
+        "stream-replace-string": "^2.0.0",
+        "zod": "^4.3.6"
       }
     },
-    "node_modules/ansi-styles": {
-      "version": "4.3.0",
-      "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
-      "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
-      "dev": true,
+    "node_modules/@astrojs/telemetry": {
+      "version": "3.3.0",
+      "resolved": "https://registry.npmjs.org/@astrojs/telemetry/-/telemetry-3.3.0.tgz",
+      "integrity": "sha512-UFBgfeldP06qu6khs/yY+q1cDAaArM2/7AEIqQ9Cuvf7B1hNLq0xDrZkct+QoIGyjq56y8IaE2I3CTvG99mlhQ==",
       "license": "MIT",
       "dependencies": {
-        "color-convert": "^2.0.1"
+        "ci-info": "^4.2.0",
+        "debug": "^4.4.0",
+        "dlv": "^1.1.3",
+        "dset": "^3.1.4",
+        "is-docker": "^3.0.0",
+        "is-wsl": "^3.1.0",
+        "which-pm-runs": "^1.1.0"
       },
       "engines": {
-        "node": ">=8"
+        "node": "18.20.8 || ^20.3.0 || >=22.0.0"
+      }
+    },
+    "node_modules/@babel/code-frame": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.29.0.tgz",
+      "integrity": "sha512-9NhCeYjq9+3uxgdtp20LSiJXJvN0FeCtNGpJxuMFZ1Kv3cWUNb6DOhJwUvcVCzKGR66cw4njwM6hrJLqgOwbcw==",
+      "dependencies": {
+        "@babel/helper-validator-identifier": "^7.28.5",
+        "js-tokens": "^4.0.0",
+        "picocolors": "^1.1.1"
       },
-      "funding": {
-        "url": "https://github.com/chalk/ansi-styles?sponsor=1"
+      "engines": {
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/argparse": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
-      "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
-      "dev": true,
-      "license": "Python-2.0"
+    "node_modules/@babel/compat-data": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/compat-data/-/compat-data-7.29.0.tgz",
+      "integrity": "sha512-T1NCJqT/j9+cn8fvkt7jtwbLBfLC/1y1c7NtCeXFRgzGTsafi68MRv8yzkYSapBnFA6L3U2VSc02ciDzoAJhJg==",
+      "engines": {
+        "node": ">=6.9.0"
+      }
     },
-    "node_modules/array-buffer-byte-length": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/array-buffer-byte-length/-/array-buffer-byte-length-1.0.2.tgz",
-      "integrity": "sha512-LHE+8BuR7RYGDKvnrmcuSq3tDcKv9OFEXQt/HpbZhY7V6h0zlUXutnAD82GiFx9rdieCMjkvtcsPqBwgUl1Iiw==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/core": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.29.0.tgz",
+      "integrity": "sha512-CGOfOJqWjg2qW/Mb6zNsDm+u5vFQ8DxXfbM09z69p5Z6+mE1ikP2jUXw+j42Pf1XTYED2Rni5f95npYeuwMDQA==",
+      "peer": true,
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "is-array-buffer": "^3.0.5"
+        "@babel/code-frame": "^7.29.0",
+        "@babel/generator": "^7.29.0",
+        "@babel/helper-compilation-targets": "^7.28.6",
+        "@babel/helper-module-transforms": "^7.28.6",
+        "@babel/helpers": "^7.28.6",
+        "@babel/parser": "^7.29.0",
+        "@babel/template": "^7.28.6",
+        "@babel/traverse": "^7.29.0",
+        "@babel/types": "^7.29.0",
+        "@jridgewell/remapping": "^2.3.5",
+        "convert-source-map": "^2.0.0",
+        "debug": "^4.1.0",
+        "gensync": "^1.0.0-beta.2",
+        "json5": "^2.2.3",
+        "semver": "^6.3.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/babel"
       }
     },
-    "node_modules/array-includes": {
-      "version": "3.1.9",
-      "resolved": "https://registry.npmjs.org/array-includes/-/array-includes-3.1.9.tgz",
-      "integrity": "sha512-FmeCCAenzH0KH381SPT5FZmiA/TmpndpcaShhfgEN9eCVjnFBqq3l1xrI42y8+PPLI6hypzou4GXw00WHmPBLQ==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/core/node_modules/semver": {
+      "version": "6.3.1",
+      "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz",
+      "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==",
+      "bin": {
+        "semver": "bin/semver.js"
+      }
+    },
+    "node_modules/@babel/generator": {
+      "version": "7.29.1",
+      "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.29.1.tgz",
+      "integrity": "sha512-qsaF+9Qcm2Qv8SRIMMscAvG4O3lJ0F1GuMo5HR/Bp02LopNgnZBC/EkbevHFeGs4ls/oPz9v+Bsmzbkbe+0dUw==",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.4",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.24.0",
-        "es-object-atoms": "^1.1.1",
-        "get-intrinsic": "^1.3.0",
-        "is-string": "^1.1.1",
-        "math-intrinsics": "^1.1.0"
+        "@babel/parser": "^7.29.0",
+        "@babel/types": "^7.29.0",
+        "@jridgewell/gen-mapping": "^0.3.12",
+        "@jridgewell/trace-mapping": "^0.3.28",
+        "jsesc": "^3.0.2"
       },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/array.prototype.findlastindex": {
-      "version": "1.2.6",
-      "resolved": "https://registry.npmjs.org/array.prototype.findlastindex/-/array.prototype.findlastindex-1.2.6.tgz",
-      "integrity": "sha512-F/TKATkzseUExPlfvmwQKGITM3DGTK+vkAsCZoDc5daVygbJBnjEUCbgkAvVFsgfXfX4YIqZ/27G3k3tdXrTxQ==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/helper-compilation-targets": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/helper-compilation-targets/-/helper-compilation-targets-7.28.6.tgz",
+      "integrity": "sha512-JYtls3hqi15fcx5GaSNL7SCTJ2MNmjrkHXg4FSpOA/grxK8KwyZ5bubHsCq8FXCkua6xhuaaBit+3b7+VZRfcA==",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.4",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.9",
-        "es-errors": "^1.3.0",
-        "es-object-atoms": "^1.1.1",
-        "es-shim-unscopables": "^1.1.0"
+        "@babel/compat-data": "^7.28.6",
+        "@babel/helper-validator-option": "^7.27.1",
+        "browserslist": "^4.24.0",
+        "lru-cache": "^5.1.1",
+        "semver": "^6.3.1"
       },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/array.prototype.flat": {
-      "version": "1.3.3",
-      "resolved": "https://registry.npmjs.org/array.prototype.flat/-/array.prototype.flat-1.3.3.tgz",
-      "integrity": "sha512-rwG/ja1neyLqCuGZ5YYrznA62D4mZXg0i1cIskIUKSiqF3Cje9/wXAls9B9s1Wa2fomMsIv8czB8jZcPmxCXFg==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/helper-compilation-targets/node_modules/lru-cache": {
+      "version": "5.1.1",
+      "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-5.1.1.tgz",
+      "integrity": "sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.5",
-        "es-shim-unscopables": "^1.0.2"
-      },
+        "yallist": "^3.0.2"
+      }
+    },
+    "node_modules/@babel/helper-compilation-targets/node_modules/semver": {
+      "version": "6.3.1",
+      "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz",
+      "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==",
+      "bin": {
+        "semver": "bin/semver.js"
+      }
+    },
+    "node_modules/@babel/helper-compilation-targets/node_modules/yallist": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz",
+      "integrity": "sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g=="
+    },
+    "node_modules/@babel/helper-globals": {
+      "version": "7.28.0",
+      "resolved": "https://registry.npmjs.org/@babel/helper-globals/-/helper-globals-7.28.0.tgz",
+      "integrity": "sha512-+W6cISkXFa1jXsDEdYA8HeevQT/FULhxzR99pxphltZcVaugps53THCeiWA8SguxxpSp3gKPiuYfSWopkLQ4hw==",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
+      }
+    },
+    "node_modules/@babel/helper-module-imports": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/helper-module-imports/-/helper-module-imports-7.28.6.tgz",
+      "integrity": "sha512-l5XkZK7r7wa9LucGw9LwZyyCUscb4x37JWTPz7swwFE/0FMQAGpiWUZn8u9DzkSBWEcK25jmvubfpw2dnAMdbw==",
+      "dependencies": {
+        "@babel/traverse": "^7.28.6",
+        "@babel/types": "^7.28.6"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "engines": {
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/array.prototype.flatmap": {
-      "version": "1.3.3",
-      "resolved": "https://registry.npmjs.org/array.prototype.flatmap/-/array.prototype.flatmap-1.3.3.tgz",
-      "integrity": "sha512-Y7Wt51eKJSyi80hFrJCePGGNo5ktJCslFuboqJsbf57CCPcm5zztluPlc4/aD8sWsKvlwatezpV4U1efk8kpjg==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/helper-module-transforms": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.28.6.tgz",
+      "integrity": "sha512-67oXFAYr2cDLDVGLXTEABjdBJZ6drElUSI7WKp70NrpyISso3plG9SAGEF6y7zbha/wOzUByWWTJvEDVNIUGcA==",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.5",
-        "es-shim-unscopables": "^1.0.2"
+        "@babel/helper-module-imports": "^7.28.6",
+        "@babel/helper-validator-identifier": "^7.28.5",
+        "@babel/traverse": "^7.28.6"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "peerDependencies": {
+        "@babel/core": "^7.0.0"
       }
     },
-    "node_modules/arraybuffer.prototype.slice": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/arraybuffer.prototype.slice/-/arraybuffer.prototype.slice-1.0.4.tgz",
-      "integrity": "sha512-BNoCY6SXXPQ7gF2opIP4GBE+Xw7U+pHMYKuzjgCN3GwiaIR09UUeKfheyIry77QtrCBlC0KK0q5/TER/tYh3PQ==",
-      "dev": true,
+    "node_modules/@babel/helper-plugin-utils": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/helper-plugin-utils/-/helper-plugin-utils-7.28.6.tgz",
+      "integrity": "sha512-S9gzZ/bz83GRysI7gAD4wPT/AI3uCnY+9xn+Mx/KPs2JwHJIz1W8PZkg2cqyt3RNOBM8ejcXhV6y8Og7ly/Dug==",
       "license": "MIT",
-      "dependencies": {
-        "array-buffer-byte-length": "^1.0.1",
-        "call-bind": "^1.0.8",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.5",
-        "es-errors": "^1.3.0",
-        "get-intrinsic": "^1.2.6",
-        "is-array-buffer": "^3.0.4"
-      },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/async-function": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/async-function/-/async-function-1.0.0.tgz",
-      "integrity": "sha512-hsU18Ae8CDTR6Kgu9DYf0EbCr/a5iGL0rytQDobUcdpYOKokk8LEjVphnXkDkgpi0wYVsqrXuP0bZxJaTqdgoA==",
-      "dev": true,
+    "node_modules/@babel/helper-string-parser": {
+      "version": "7.27.1",
+      "resolved": "https://registry.npmjs.org/@babel/helper-string-parser/-/helper-string-parser-7.27.1.tgz",
+      "integrity": "sha512-qMlSxKbpRlAridDExk92nSobyDdpPijUq2DW6oDnUqd0iOGxmQjyqhMIihI9+zv4LPyZdRje2cavWPbCbWm3eA==",
       "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/available-typed-arrays": {
-      "version": "1.0.7",
-      "resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.7.tgz",
-      "integrity": "sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==",
-      "dev": true,
+    "node_modules/@babel/helper-validator-identifier": {
+      "version": "7.28.5",
+      "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.28.5.tgz",
+      "integrity": "sha512-qSs4ifwzKJSV39ucNjsvc6WVHs6b7S03sOh2OcHF9UHfVPqWWALUsNUVzhSBiItjRZoLHx7nIarVjqKVusUZ1Q==",
       "license": "MIT",
-      "dependencies": {
-        "possible-typed-array-names": "^1.0.0"
-      },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/balanced-match": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
-      "integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/brace-expansion": {
-      "version": "1.1.11",
-      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz",
-      "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "balanced-match": "^1.0.0",
-        "concat-map": "0.0.1"
+    "node_modules/@babel/helper-validator-option": {
+      "version": "7.27.1",
+      "resolved": "https://registry.npmjs.org/@babel/helper-validator-option/-/helper-validator-option-7.27.1.tgz",
+      "integrity": "sha512-YvjJow9FxbhFFKDSuFnVCe2WxXk1zWc22fFePVNEaWJEu8IrZVlda6N0uHwzZrUM1il7NC9Mlp4MaJYbYd9JSg==",
+      "engines": {
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/builtins": {
-      "version": "5.1.0",
-      "resolved": "https://registry.npmjs.org/builtins/-/builtins-5.1.0.tgz",
-      "integrity": "sha512-SW9lzGTLvWTP1AY8xeAMZimqDrIaSdLQUcVr9DMef51niJ022Ri87SwRRKYm4A6iHfkPaiVUu/Duw2Wc4J7kKg==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/helpers": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/helpers/-/helpers-7.28.6.tgz",
+      "integrity": "sha512-xOBvwq86HHdB7WUDTfKfT/Vuxh7gElQ+Sfti2Cy6yIWNW05P8iUslOVcZ4/sKbE+/jQaukQAdz/gf3724kYdqw==",
       "dependencies": {
-        "semver": "^7.0.0"
+        "@babel/template": "^7.28.6",
+        "@babel/types": "^7.28.6"
+      },
+      "engines": {
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/builtins/node_modules/semver": {
-      "version": "7.6.2",
-      "resolved": "https://registry.npmjs.org/semver/-/semver-7.6.2.tgz",
-      "integrity": "sha512-FNAIBWCx9qcRhoHcgcJ0gvU7SN1lYU2ZXuSfl04bSC5OpvDHFyJCjdNHomPXxjQlCBU67YW64PzY7/VIEH7F2w==",
-      "dev": true,
-      "license": "ISC",
+    "node_modules/@babel/parser": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.29.0.tgz",
+      "integrity": "sha512-IyDgFV5GeDUVX4YdF/3CPULtVGSXXMLh1xVIgdCgxApktqnQV0r7/8Nqthg+8YLGaAtdyIlo2qIdZrbCv4+7ww==",
+      "dependencies": {
+        "@babel/types": "^7.29.0"
+      },
       "bin": {
-        "semver": "bin/semver.js"
+        "parser": "bin/babel-parser.js"
       },
       "engines": {
-        "node": ">=10"
+        "node": ">=6.0.0"
       }
     },
-    "node_modules/call-bind": {
-      "version": "1.0.8",
-      "resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.8.tgz",
-      "integrity": "sha512-oKlSFMcMwpUg2ednkhQ454wfWiU/ul3CkJe/PEHcTKuiX6RpbehUiFMXu13HalGZxfUwCQzZG747YXBn1im9ww==",
-      "dev": true,
+    "node_modules/@babel/plugin-transform-react-jsx-self": {
+      "version": "7.27.1",
+      "resolved": "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-self/-/plugin-transform-react-jsx-self-7.27.1.tgz",
+      "integrity": "sha512-6UzkCs+ejGdZ5mFFC/OCUrv028ab2fp1znZmCZjAOBKiBK2jXD1O+BPSfX8X2qjJ75fZBMSnQn3Rq2mrBJK2mw==",
       "license": "MIT",
       "dependencies": {
-        "call-bind-apply-helpers": "^1.0.0",
-        "es-define-property": "^1.0.0",
-        "get-intrinsic": "^1.2.4",
-        "set-function-length": "^1.2.2"
+        "@babel/helper-plugin-utils": "^7.27.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
       }
     },
-    "node_modules/call-bind-apply-helpers": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/call-bind-apply-helpers/-/call-bind-apply-helpers-1.0.2.tgz",
-      "integrity": "sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==",
-      "dev": true,
+    "node_modules/@babel/plugin-transform-react-jsx-source": {
+      "version": "7.27.1",
+      "resolved": "https://registry.npmjs.org/@babel/plugin-transform-react-jsx-source/-/plugin-transform-react-jsx-source-7.27.1.tgz",
+      "integrity": "sha512-zbwoTsBruTeKB9hSq73ha66iFeJHuaFkUbwvqElnygoNbj/jHRsSeokowZFN3CZ64IvEqcmmkVe89OPXc7ldAw==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "function-bind": "^1.1.2"
+        "@babel/helper-plugin-utils": "^7.27.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
       }
     },
-    "node_modules/call-bound": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/call-bound/-/call-bound-1.0.4.tgz",
-      "integrity": "sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/template": {
+      "version": "7.28.6",
+      "resolved": "https://registry.npmjs.org/@babel/template/-/template-7.28.6.tgz",
+      "integrity": "sha512-YA6Ma2KsCdGb+WC6UpBVFJGXL58MDA6oyONbjyF/+5sBgxY/dwkhLogbMT2GXXyU84/IhRw/2D1Os1B/giz+BQ==",
       "dependencies": {
-        "call-bind-apply-helpers": "^1.0.2",
-        "get-intrinsic": "^1.3.0"
+        "@babel/code-frame": "^7.28.6",
+        "@babel/parser": "^7.28.6",
+        "@babel/types": "^7.28.6"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=6.9.0"
+      }
+    },
+    "node_modules/@babel/traverse": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/traverse/-/traverse-7.29.0.tgz",
+      "integrity": "sha512-4HPiQr0X7+waHfyXPZpWPfWL/J7dcN1mx9gL6WdQVMbPnF3+ZhSMs8tCxN7oHddJE9fhNE7+lxdnlyemKfJRuA==",
+      "dependencies": {
+        "@babel/code-frame": "^7.29.0",
+        "@babel/generator": "^7.29.0",
+        "@babel/helper-globals": "^7.28.0",
+        "@babel/parser": "^7.29.0",
+        "@babel/template": "^7.28.6",
+        "@babel/types": "^7.29.0",
+        "debug": "^4.3.1"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "engines": {
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/callsites": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
-      "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/@babel/types": {
+      "version": "7.29.0",
+      "resolved": "https://registry.npmjs.org/@babel/types/-/types-7.29.0.tgz",
+      "integrity": "sha512-LwdZHpScM4Qz8Xw2iKSzS+cfglZzJGvofQICy7W7v4caru4EaAmyUuO6BGrbyQ2mYV11W0U8j5mBhd14dd3B0A==",
+      "dependencies": {
+        "@babel/helper-string-parser": "^7.27.1",
+        "@babel/helper-validator-identifier": "^7.28.5"
+      },
       "engines": {
-        "node": ">=6"
+        "node": ">=6.9.0"
       }
     },
-    "node_modules/chalk": {
-      "version": "4.1.2",
-      "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
-      "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
-      "dev": true,
+    "node_modules/@capsizecss/unpack": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/@capsizecss/unpack/-/unpack-4.0.0.tgz",
+      "integrity": "sha512-VERIM64vtTP1C4mxQ5thVT9fK0apjPFobqybMtA1UdUujWka24ERHbRHFGmpbbhp73MhV+KSsHQH9C6uOTdEQA==",
       "license": "MIT",
       "dependencies": {
-        "ansi-styles": "^4.1.0",
-        "supports-color": "^7.1.0"
+        "fontkitten": "^1.0.0"
       },
       "engines": {
-        "node": ">=10"
-      },
-      "funding": {
-        "url": "https://github.com/chalk/chalk?sponsor=1"
+        "node": ">=18"
       }
     },
-    "node_modules/character-entities": {
-      "version": "1.2.4",
-      "resolved": "https://registry.npmjs.org/character-entities/-/character-entities-1.2.4.tgz",
-      "integrity": "sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw==",
-      "dev": true,
+    "node_modules/@clack/core": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@clack/core/-/core-1.1.0.tgz",
+      "integrity": "sha512-SVcm4Dqm2ukn64/8Gub2wnlA5nS2iWJyCkdNHcvNHPIeBTGojpdJ+9cZKwLfmqy7irD4N5qLteSilJlE0WLAtA==",
       "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+      "dependencies": {
+        "sisteransi": "^1.0.5"
       }
     },
-    "node_modules/character-entities-legacy": {
-      "version": "1.1.4",
-      "resolved": "https://registry.npmjs.org/character-entities-legacy/-/character-entities-legacy-1.1.4.tgz",
-      "integrity": "sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA==",
-      "dev": true,
+    "node_modules/@clack/prompts": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@clack/prompts/-/prompts-1.1.0.tgz",
+      "integrity": "sha512-pkqbPGtohJAvm4Dphs2M8xE29ggupihHdy1x84HNojZuMtFsHiUlRvqD24tM2+XmI+61LlfNceM3Wr7U5QES5g==",
       "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+      "dependencies": {
+        "@clack/core": "1.1.0",
+        "sisteransi": "^1.0.5"
       }
     },
-    "node_modules/character-reference-invalid": {
-      "version": "1.1.4",
-      "resolved": "https://registry.npmjs.org/character-reference-invalid/-/character-reference-invalid-1.1.4.tgz",
-      "integrity": "sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg==",
+    "node_modules/@csstools/cascade-layer-name-parser": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/@csstools/cascade-layer-name-parser/-/cascade-layer-name-parser-3.0.0.tgz",
+      "integrity": "sha512-/3iksyevwRfSJx5yH0RkcrcYXwuhMQx3Juqf40t97PeEy2/Mz2TItZ/z/216qpe4GgOyFBP8MKIwVvytzHmfIQ==",
       "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
+      "engines": {
+        "node": ">=20.19.0"
+      },
+      "peerDependencies": {
+        "@csstools/css-parser-algorithms": "^4.0.0",
+        "@csstools/css-tokenizer": "^4.0.0"
       }
     },
-    "node_modules/color-convert": {
-      "version": "2.0.1",
-      "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
-      "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
+    "node_modules/@csstools/css-parser-algorithms": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/@csstools/css-parser-algorithms/-/css-parser-algorithms-4.0.0.tgz",
+      "integrity": "sha512-+B87qS7fIG3L5h3qwJ/IFbjoVoOe/bpOdh9hAjXbvx0o8ImEmUsGXN0inFOnk2ChCFgqkkGFQ+TpM5rbhkKe4w==",
       "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "color-name": "~1.1.4"
-      },
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
+      "peer": true,
       "engines": {
-        "node": ">=7.0.0"
+        "node": ">=20.19.0"
+      },
+      "peerDependencies": {
+        "@csstools/css-tokenizer": "^4.0.0"
       }
     },
-    "node_modules/color-name": {
-      "version": "1.1.4",
-      "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
-      "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
+    "node_modules/@csstools/css-tokenizer": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/@csstools/css-tokenizer/-/css-tokenizer-4.0.0.tgz",
+      "integrity": "sha512-QxULHAm7cNu72w97JUNCBFODFaXpbDg+dP8b/oWFAZ2MTRppA3U00Y2L1HqaS4J6yBqxwa/Y3nMBaxVKbB/NsA==",
       "dev": true,
-      "license": "MIT"
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
+      "peer": true,
+      "engines": {
+        "node": ">=20.19.0"
+      }
     },
-    "node_modules/concat-map": {
-      "version": "0.0.1",
-      "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
-      "integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==",
+    "node_modules/@csstools/media-query-list-parser": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/@csstools/media-query-list-parser/-/media-query-list-parser-5.0.0.tgz",
+      "integrity": "sha512-T9lXmZOfnam3eMERPsszjY5NK0jX8RmThmmm99FZ8b7z8yMaFZWKwLWGZuTwdO3ddRY5fy13GmmEYZXB4I98Eg==",
       "dev": true,
-      "license": "MIT"
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
+      "engines": {
+        "node": ">=20.19.0"
+      },
+      "peerDependencies": {
+        "@csstools/css-parser-algorithms": "^4.0.0",
+        "@csstools/css-tokenizer": "^4.0.0"
+      }
     },
-    "node_modules/cross-spawn": {
-      "version": "7.0.3",
-      "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.3.tgz",
-      "integrity": "sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==",
+    "node_modules/@csstools/postcss-global-data": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/@csstools/postcss-global-data/-/postcss-global-data-4.0.0.tgz",
+      "integrity": "sha512-mPKrL3Tzt8k1V+hTkU8XTH6JKRekB97oKHv/MekC9nfmRa+gMf1swlHRt8YK722sYN4xOipl17FZst99jsScLA==",
       "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "path-key": "^3.1.0",
-        "shebang-command": "^2.0.0",
-        "which": "^2.0.1"
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
+      "license": "MIT-0",
+      "engines": {
+        "node": ">=20.19.0"
       },
+      "peerDependencies": {
+        "postcss": "^8.4"
+      }
+    },
+    "node_modules/@ctrl/tinycolor": {
+      "version": "4.2.0",
+      "resolved": "https://registry.npmjs.org/@ctrl/tinycolor/-/tinycolor-4.2.0.tgz",
+      "integrity": "sha512-kzyuwOAQnXJNLS9PSyrk0CWk35nWJW/zl/6KvnTBMFK65gm7U1/Z5BqjxeapjZCIhQcM/DsrEmcbRwDyXyXK4A==",
       "engines": {
-        "node": ">= 8"
+        "node": ">=14"
       }
     },
-    "node_modules/data-view-buffer": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/data-view-buffer/-/data-view-buffer-1.0.2.tgz",
-      "integrity": "sha512-EmKO5V3OLXh1rtK2wgXRansaK1/mtVdTUEiEI0W8RkvgT05kfxaH29PliLnpLP73yYO6142Q72QNa8Wx/A5CqQ==",
-      "dev": true,
+    "node_modules/@emnapi/runtime": {
+      "version": "1.9.1",
+      "resolved": "https://registry.npmjs.org/@emnapi/runtime/-/runtime-1.9.1.tgz",
+      "integrity": "sha512-VYi5+ZVLhpgK4hQ0TAjiQiZ6ol0oe4mBx7mVv7IflsiEp0OWoVsp/+f9Vc1hOhE0TtkORVrI1GvzyreqpgWtkA==",
       "license": "MIT",
+      "optional": true,
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "es-errors": "^1.3.0",
-        "is-data-view": "^1.0.2"
-      },
+        "tslib": "^2.4.0"
+      }
+    },
+    "node_modules/@esbuild/aix-ppc64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.27.4.tgz",
+      "integrity": "sha512-cQPwL2mp2nSmHHJlCyoXgHGhbEPMrEEU5xhkcy3Hs/O7nGZqEpZ2sUtLaL9MORLtDfRvVl2/3PAuEkYZH0Ty8Q==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "aix"
+      ],
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=18"
       }
     },
-    "node_modules/data-view-byte-length": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/data-view-byte-length/-/data-view-byte-length-1.0.2.tgz",
-      "integrity": "sha512-tuhGbE6CfTM9+5ANGf+oQb72Ky/0+s3xKUpHvShfiz2RxMFgFPjsXuRLBVMtvMs15awe45SRb83D6wH4ew6wlQ==",
-      "dev": true,
+    "node_modules/@esbuild/android-arm": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.27.4.tgz",
+      "integrity": "sha512-X9bUgvxiC8CHAGKYufLIHGXPJWnr0OCdR0anD2e21vdvgCI8lIfqFbnoeOz7lBjdrAGUhqLZLcQo6MLhTO2DKQ==",
+      "cpu": [
+        "arm"
+      ],
       "license": "MIT",
-      "dependencies": {
-        "call-bound": "^1.0.3",
-        "es-errors": "^1.3.0",
-        "is-data-view": "^1.0.2"
-      },
+      "optional": true,
+      "os": [
+        "android"
+      ],
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/inspect-js"
+        "node": ">=18"
       }
     },
-    "node_modules/data-view-byte-offset": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/data-view-byte-offset/-/data-view-byte-offset-1.0.1.tgz",
-      "integrity": "sha512-BS8PfmtDGnrgYdOonGZQdLZslWIeCGFP9tpan0hi1Co2Zr2NKADsvGYA8XxuG/4UWgJ6Cjtv+YJnB6MM69QGlQ==",
+    "node_modules/@esbuild/android-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/android-arm64/-/android-arm64-0.27.4.tgz",
+      "integrity": "sha512-gdLscB7v75wRfu7QSm/zg6Rx29VLdy9eTr2t44sfTW7CxwAtQghZ4ZnqHk3/ogz7xao0QAgrkradbBzcqFPasw==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "android"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/android-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/android-x64/-/android-x64-0.27.4.tgz",
+      "integrity": "sha512-PzPFnBNVF292sfpfhiyiXCGSn9HZg5BcAz+ivBuSsl6Rk4ga1oEXAamhOXRFyMcjwr2DVtm40G65N3GLeH1Lvw==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "android"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/darwin-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/darwin-arm64/-/darwin-arm64-0.27.4.tgz",
+      "integrity": "sha512-b7xaGIwdJlht8ZFCvMkpDN6uiSmnxxK56N2GDTMYPr2/gzvfdQN8rTfBsvVKmIVY/X7EM+/hJKEIbbHs9oA4tQ==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/darwin-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/darwin-x64/-/darwin-x64-0.27.4.tgz",
+      "integrity": "sha512-sR+OiKLwd15nmCdqpXMnuJ9W2kpy0KigzqScqHI3Hqwr7IXxBp3Yva+yJwoqh7rE8V77tdoheRYataNKL4QrPw==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/freebsd-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/freebsd-arm64/-/freebsd-arm64-0.27.4.tgz",
+      "integrity": "sha512-jnfpKe+p79tCnm4GVav68A7tUFeKQwQyLgESwEAUzyxk/TJr4QdGog9sqWNcUbr/bZt/O/HXouspuQDd9JxFSw==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "freebsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/freebsd-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/freebsd-x64/-/freebsd-x64-0.27.4.tgz",
+      "integrity": "sha512-2kb4ceA/CpfUrIcTUl1wrP/9ad9Atrp5J94Lq69w7UwOMolPIGrfLSvAKJp0RTvkPPyn6CIWrNy13kyLikZRZQ==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "freebsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-arm": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-arm/-/linux-arm-0.27.4.tgz",
+      "integrity": "sha512-aBYgcIxX/wd5n2ys0yESGeYMGF+pv6g0DhZr3G1ZG4jMfruU9Tl1i2Z+Wnj9/KjGz1lTLCcorqE2viePZqj4Eg==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-arm64/-/linux-arm64-0.27.4.tgz",
+      "integrity": "sha512-7nQOttdzVGth1iz57kxg9uCz57dxQLHWxopL6mYuYthohPKEK0vU0C3O21CcBK6KDlkYVcnDXY099HcCDXd9dA==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-ia32": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-ia32/-/linux-ia32-0.27.4.tgz",
+      "integrity": "sha512-oPtixtAIzgvzYcKBQM/qZ3R+9TEUd1aNJQu0HhGyqtx6oS7qTpvjheIWBbes4+qu1bNlo2V4cbkISr8q6gRBFA==",
+      "cpu": [
+        "ia32"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-loong64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-loong64/-/linux-loong64-0.27.4.tgz",
+      "integrity": "sha512-8mL/vh8qeCoRcFH2nM8wm5uJP+ZcVYGGayMavi8GmRJjuI3g1v6Z7Ni0JJKAJW+m0EtUuARb6Lmp4hMjzCBWzA==",
+      "cpu": [
+        "loong64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-mips64el": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-mips64el/-/linux-mips64el-0.27.4.tgz",
+      "integrity": "sha512-1RdrWFFiiLIW7LQq9Q2NES+HiD4NyT8Itj9AUeCl0IVCA459WnPhREKgwrpaIfTOe+/2rdntisegiPWn/r/aAw==",
+      "cpu": [
+        "mips64el"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-ppc64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-ppc64/-/linux-ppc64-0.27.4.tgz",
+      "integrity": "sha512-tLCwNG47l3sd9lpfyx9LAGEGItCUeRCWeAx6x2Jmbav65nAwoPXfewtAdtbtit/pJFLUWOhpv0FpS6GQAmPrHA==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-riscv64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-riscv64/-/linux-riscv64-0.27.4.tgz",
+      "integrity": "sha512-BnASypppbUWyqjd1KIpU4AUBiIhVr6YlHx/cnPgqEkNoVOhHg+YiSVxM1RLfiy4t9cAulbRGTNCKOcqHrEQLIw==",
+      "cpu": [
+        "riscv64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-s390x": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-s390x/-/linux-s390x-0.27.4.tgz",
+      "integrity": "sha512-+eUqgb/Z7vxVLezG8bVB9SfBie89gMueS+I0xYh2tJdw3vqA/0ImZJ2ROeWwVJN59ihBeZ7Tu92dF/5dy5FttA==",
+      "cpu": [
+        "s390x"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/linux-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/linux-x64/-/linux-x64-0.27.4.tgz",
+      "integrity": "sha512-S5qOXrKV8BQEzJPVxAwnryi2+Iq5pB40gTEIT69BQONqR7JH1EPIcQ/Uiv9mCnn05jff9umq/5nqzxlqTOg9NA==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/netbsd-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/netbsd-arm64/-/netbsd-arm64-0.27.4.tgz",
+      "integrity": "sha512-xHT8X4sb0GS8qTqiwzHqpY00C95DPAq7nAwX35Ie/s+LO9830hrMd3oX0ZMKLvy7vsonee73x0lmcdOVXFzd6Q==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "netbsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/netbsd-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/netbsd-x64/-/netbsd-x64-0.27.4.tgz",
+      "integrity": "sha512-RugOvOdXfdyi5Tyv40kgQnI0byv66BFgAqjdgtAKqHoZTbTF2QqfQrFwa7cHEORJf6X2ht+l9ABLMP0dnKYsgg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "netbsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/openbsd-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/openbsd-arm64/-/openbsd-arm64-0.27.4.tgz",
+      "integrity": "sha512-2MyL3IAaTX+1/qP0O1SwskwcwCoOI4kV2IBX1xYnDDqthmq5ArrW94qSIKCAuRraMgPOmG0RDTA74mzYNQA9ow==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "openbsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/openbsd-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/openbsd-x64/-/openbsd-x64-0.27.4.tgz",
+      "integrity": "sha512-u8fg/jQ5aQDfsnIV6+KwLOf1CmJnfu1ShpwqdwC0uA7ZPwFws55Ngc12vBdeUdnuWoQYx/SOQLGDcdlfXhYmXQ==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "openbsd"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/openharmony-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/openharmony-arm64/-/openharmony-arm64-0.27.4.tgz",
+      "integrity": "sha512-JkTZrl6VbyO8lDQO3yv26nNr2RM2yZzNrNHEsj9bm6dOwwu9OYN28CjzZkH57bh4w0I2F7IodpQvUAEd1mbWXg==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "openharmony"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/sunos-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/sunos-x64/-/sunos-x64-0.27.4.tgz",
+      "integrity": "sha512-/gOzgaewZJfeJTlsWhvUEmUG4tWEY2Spp5M20INYRg2ZKl9QPO3QEEgPeRtLjEWSW8FilRNacPOg8R1uaYkA6g==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "sunos"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/win32-arm64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/win32-arm64/-/win32-arm64-0.27.4.tgz",
+      "integrity": "sha512-Z9SExBg2y32smoDQdf1HRwHRt6vAHLXcxD2uGgO/v2jK7Y718Ix4ndsbNMU/+1Qiem9OiOdaqitioZwxivhXYg==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/win32-ia32": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/win32-ia32/-/win32-ia32-0.27.4.tgz",
+      "integrity": "sha512-DAyGLS0Jz5G5iixEbMHi5KdiApqHBWMGzTtMiJ72ZOLhbu/bzxgAe8Ue8CTS3n3HbIUHQz/L51yMdGMeoxXNJw==",
+      "cpu": [
+        "ia32"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@esbuild/win32-x64": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/@esbuild/win32-x64/-/win32-x64-0.27.4.tgz",
+      "integrity": "sha512-+knoa0BDoeXgkNvvV1vvbZX4+hizelrkwmGJBdT17t8FNPwG2lKemmuMZlmaNQ3ws3DKKCxpb4zRZEIp3UxFCg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@eslint-community/eslint-utils": {
+      "version": "4.9.1",
+      "resolved": "https://registry.npmjs.org/@eslint-community/eslint-utils/-/eslint-utils-4.9.1.tgz",
+      "integrity": "sha512-phrYmNiYppR7znFEdqgfWHXR6NCkZEK7hwWDHZUjit/2/U0r6XvkDl0SYnoM51Hq7FhCGdLDT6zxCCOY1hexsQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "es-errors": "^1.3.0",
-        "is-data-view": "^1.0.1"
+        "eslint-visitor-keys": "^3.4.3"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://opencollective.com/eslint"
+      },
+      "peerDependencies": {
+        "eslint": "^6.0.0 || ^7.0.0 || >=8.0.0"
       }
     },
-    "node_modules/debug": {
-      "version": "4.3.5",
-      "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.5.tgz",
-      "integrity": "sha512-pt0bNEmneDIvdL1Xsd9oDQ/wrQRkXDT4AUWlNZNPKvW5x/jyO9VFXkJUP07vQ2upmw5PlaITaPKc31jK13V+jg==",
+    "node_modules/@eslint-community/eslint-utils/node_modules/eslint-visitor-keys": {
+      "version": "3.4.3",
+      "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz",
+      "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/eslint"
+      }
+    },
+    "node_modules/@eslint-community/regexpp": {
+      "version": "4.12.2",
+      "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.12.2.tgz",
+      "integrity": "sha512-EriSTlt5OC9/7SXkRSCAhfSxxoSUgBm33OH+IkwbdpgoqsSsUg7y3uh+IICI/Qg4BBWr3U2i39RpmycbxMq4ew==",
       "dev": true,
       "license": "MIT",
+      "engines": {
+        "node": "^12.0.0 || ^14.0.0 || >=16.0.0"
+      }
+    },
+    "node_modules/@eslint/config-array": {
+      "version": "0.21.1",
+      "resolved": "https://registry.npmjs.org/@eslint/config-array/-/config-array-0.21.1.tgz",
+      "integrity": "sha512-aw1gNayWpdI/jSYVgzN5pL0cfzU02GT3NBpeT/DXbx1/1x7ZKxFPd9bwrzygx/qiwIQiJ1sw/zD8qY/kRvlGHA==",
+      "dev": true,
+      "license": "Apache-2.0",
       "dependencies": {
-        "ms": "2.1.2"
+        "@eslint/object-schema": "^2.1.7",
+        "debug": "^4.3.1",
+        "minimatch": "^3.1.2"
       },
       "engines": {
-        "node": ">=6.0"
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      }
+    },
+    "node_modules/@eslint/config-helpers": {
+      "version": "0.4.2",
+      "resolved": "https://registry.npmjs.org/@eslint/config-helpers/-/config-helpers-0.4.2.tgz",
+      "integrity": "sha512-gBrxN88gOIf3R7ja5K9slwNayVcZgK6SOUORm2uBzTeIEfeVaIhOpCtTox3P6R7o2jLFwLFTLnC7kU/RGcYEgw==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@eslint/core": "^0.17.0"
       },
-      "peerDependenciesMeta": {
-        "supports-color": {
-          "optional": true
-        }
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
       }
     },
-    "node_modules/deep-is": {
-      "version": "0.1.4",
-      "resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz",
-      "integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==",
+    "node_modules/@eslint/core": {
+      "version": "0.17.0",
+      "resolved": "https://registry.npmjs.org/@eslint/core/-/core-0.17.0.tgz",
+      "integrity": "sha512-yL/sLrpmtDaFEiUj1osRP4TI2MDz1AddJL+jZ7KSqvBuliN4xqYY54IfdN8qD8Toa6g1iloph1fxQNkjOxrrpQ==",
       "dev": true,
-      "license": "MIT"
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@types/json-schema": "^7.0.15"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      }
     },
-    "node_modules/define-data-property": {
-      "version": "1.1.4",
-      "resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.4.tgz",
-      "integrity": "sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==",
+    "node_modules/@eslint/eslintrc": {
+      "version": "3.3.3",
+      "resolved": "https://registry.npmjs.org/@eslint/eslintrc/-/eslintrc-3.3.3.tgz",
+      "integrity": "sha512-Kr+LPIUVKz2qkx1HAMH8q1q6azbqBAsXJUxBl/ODDuVPX45Z9DfwB8tPjTi6nNZ8BuM3nbJxC5zCAg5elnBUTQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "es-define-property": "^1.0.0",
-        "es-errors": "^1.3.0",
-        "gopd": "^1.0.1"
+        "ajv": "^6.12.4",
+        "debug": "^4.3.2",
+        "espree": "^10.0.1",
+        "globals": "^14.0.0",
+        "ignore": "^5.2.0",
+        "import-fresh": "^3.2.1",
+        "js-yaml": "^4.1.1",
+        "minimatch": "^3.1.2",
+        "strip-json-comments": "^3.1.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://opencollective.com/eslint"
       }
     },
-    "node_modules/define-properties": {
-      "version": "1.2.1",
-      "resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.2.1.tgz",
-      "integrity": "sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==",
+    "node_modules/@eslint/eslintrc/node_modules/globals": {
+      "version": "14.0.0",
+      "resolved": "https://registry.npmjs.org/globals/-/globals-14.0.0.tgz",
+      "integrity": "sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/@eslint/js": {
+      "version": "9.39.2",
+      "resolved": "https://registry.npmjs.org/@eslint/js/-/js-9.39.2.tgz",
+      "integrity": "sha512-q1mjIoW1VX4IvSocvM/vbTiveKC4k9eLrajNEuSsmjymSDEbpGddtpfOoN7YGAqBK3NG+uqo8ia4PDTt8buCYA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://eslint.org/donate"
+      }
+    },
+    "node_modules/@eslint/object-schema": {
+      "version": "2.1.7",
+      "resolved": "https://registry.npmjs.org/@eslint/object-schema/-/object-schema-2.1.7.tgz",
+      "integrity": "sha512-VtAOaymWVfZcmZbp6E2mympDIHvyjXs/12LqWYjVw6qjrfF+VK+fyG33kChz3nnK+SU5/NeHOqrTEHS8sXO3OA==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      }
+    },
+    "node_modules/@eslint/plugin-kit": {
+      "version": "0.4.1",
+      "resolved": "https://registry.npmjs.org/@eslint/plugin-kit/-/plugin-kit-0.4.1.tgz",
+      "integrity": "sha512-43/qtrDUokr7LJqoF2c3+RInu/t4zfrpYdoSDfYyhg52rwLV6TnOvdG4fXm7IkSB3wErkcmJS9iEhjVtOSEjjA==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@eslint/core": "^0.17.0",
+        "levn": "^0.4.1"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      }
+    },
+    "node_modules/@expressive-code/core": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/@expressive-code/core/-/core-0.41.7.tgz",
+      "integrity": "sha512-ck92uZYZ9Wba2zxkiZLsZGi9N54pMSAVdrI9uW3Oo9AtLglD5RmrdTwbYPCT2S/jC36JGB2i+pnQtBm/Ib2+dg==",
+      "dependencies": {
+        "@ctrl/tinycolor": "^4.0.4",
+        "hast-util-select": "^6.0.2",
+        "hast-util-to-html": "^9.0.1",
+        "hast-util-to-text": "^4.0.1",
+        "hastscript": "^9.0.0",
+        "postcss": "^8.4.38",
+        "postcss-nested": "^6.0.1",
+        "unist-util-visit": "^5.0.0",
+        "unist-util-visit-parents": "^6.0.1"
+      }
+    },
+    "node_modules/@expressive-code/core/node_modules/postcss-nested": {
+      "version": "6.2.0",
+      "resolved": "https://registry.npmjs.org/postcss-nested/-/postcss-nested-6.2.0.tgz",
+      "integrity": "sha512-HQbt28KulC5AJzG+cZtj9kvKB93CFCdLvog1WFLf1D+xmMvPGlBstkpTEZfK5+AN9hfJocyBFCNiqyS48bpgzQ==",
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "dependencies": {
+        "postcss-selector-parser": "^6.1.1"
+      },
+      "engines": {
+        "node": ">=12.0"
+      },
+      "peerDependencies": {
+        "postcss": "^8.2.14"
+      }
+    },
+    "node_modules/@expressive-code/core/node_modules/postcss-selector-parser": {
+      "version": "6.1.2",
+      "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.1.2.tgz",
+      "integrity": "sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==",
+      "dependencies": {
+        "cssesc": "^3.0.0",
+        "util-deprecate": "^1.0.2"
+      },
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/@expressive-code/plugin-frames": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/@expressive-code/plugin-frames/-/plugin-frames-0.41.7.tgz",
+      "integrity": "sha512-diKtxjQw/979cTglRFaMCY/sR6hWF0kSMg8jsKLXaZBSfGS0I/Hoe7Qds3vVEgeoW+GHHQzMcwvgx/MOIXhrTA==",
+      "dependencies": {
+        "@expressive-code/core": "^0.41.7"
+      }
+    },
+    "node_modules/@expressive-code/plugin-shiki": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/@expressive-code/plugin-shiki/-/plugin-shiki-0.41.7.tgz",
+      "integrity": "sha512-DL605bLrUOgqTdZ0Ot5MlTaWzppRkzzqzeGEu7ODnHF39IkEBbFdsC7pbl3LbUQ1DFtnfx6rD54k/cdofbW6KQ==",
+      "dependencies": {
+        "@expressive-code/core": "^0.41.7",
+        "shiki": "^3.2.2"
+      }
+    },
+    "node_modules/@expressive-code/plugin-text-markers": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/@expressive-code/plugin-text-markers/-/plugin-text-markers-0.41.7.tgz",
+      "integrity": "sha512-Ewpwuc5t6eFdZmWlFyeuy3e1PTQC0jFvw2Q+2bpcWXbOZhPLsT7+h8lsSIJxb5mS7wZko7cKyQ2RLYDyK6Fpmw==",
+      "dependencies": {
+        "@expressive-code/core": "^0.41.7"
+      }
+    },
+    "node_modules/@humanfs/core": {
+      "version": "0.19.1",
+      "resolved": "https://registry.npmjs.org/@humanfs/core/-/core-0.19.1.tgz",
+      "integrity": "sha512-5DyQ4+1JEUzejeK1JGICcideyfUbGixgS9jNgex5nqkW+cY7WZhxBigmieN5Qnw9ZosSNVC9KQKyb+GUaGyKUA==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">=18.18.0"
+      }
+    },
+    "node_modules/@humanfs/node": {
+      "version": "0.16.7",
+      "resolved": "https://registry.npmjs.org/@humanfs/node/-/node-0.16.7.tgz",
+      "integrity": "sha512-/zUx+yOsIrG4Y43Eh2peDeKCxlRt/gET6aHfaKpuq267qXdYDFViVHfMaLyygZOnl0kGWxFIgsBy8QFuTLUXEQ==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@humanfs/core": "^0.19.1",
+        "@humanwhocodes/retry": "^0.4.0"
+      },
+      "engines": {
+        "node": ">=18.18.0"
+      }
+    },
+    "node_modules/@humanwhocodes/module-importer": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/@humanwhocodes/module-importer/-/module-importer-1.0.1.tgz",
+      "integrity": "sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">=12.22"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/nzakas"
+      }
+    },
+    "node_modules/@humanwhocodes/retry": {
+      "version": "0.4.3",
+      "resolved": "https://registry.npmjs.org/@humanwhocodes/retry/-/retry-0.4.3.tgz",
+      "integrity": "sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">=18.18"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/nzakas"
+      }
+    },
+    "node_modules/@iconify-json/fluent": {
+      "version": "1.2.41",
+      "resolved": "https://registry.npmjs.org/@iconify-json/fluent/-/fluent-1.2.41.tgz",
+      "integrity": "sha512-UbUFCJm7gICJuiDVZdo259L05TxAKbECJ/NBax/+N5CejWXJ0q/y++HNWLdJBkSfsZVYH9KtFZgwox36PC0/Wg==",
+      "dev": true,
+      "dependencies": {
+        "@iconify/types": "*"
+      }
+    },
+    "node_modules/@iconify/tools": {
+      "version": "4.2.0",
+      "resolved": "https://registry.npmjs.org/@iconify/tools/-/tools-4.2.0.tgz",
+      "integrity": "sha512-WRxPva/ipxYkqZd1+CkEAQmd86dQmrwH0vwK89gmp2Kh2WyyVw57XbPng0NehP3x4V1LzLsXUneP1uMfTMZmUA==",
+      "license": "MIT",
+      "dependencies": {
+        "@iconify/types": "^2.0.0",
+        "@iconify/utils": "^2.3.0",
+        "cheerio": "^1.1.2",
+        "domhandler": "^5.0.3",
+        "extract-zip": "^2.0.1",
+        "local-pkg": "^1.1.2",
+        "pathe": "^2.0.3",
+        "svgo": "^3.3.2",
+        "tar": "^7.5.2"
+      }
+    },
+    "node_modules/@iconify/tools/node_modules/commander": {
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz",
+      "integrity": "sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==",
+      "license": "MIT",
+      "engines": {
+        "node": ">= 10"
+      }
+    },
+    "node_modules/@iconify/tools/node_modules/css-tree": {
+      "version": "2.3.1",
+      "resolved": "https://registry.npmjs.org/css-tree/-/css-tree-2.3.1.tgz",
+      "integrity": "sha512-6Fv1DV/TYw//QF5IzQdqsNDjx/wc8TrMBZsqjL9eW01tWb7R7k/mq+/VXfJCl7SoD5emsJop9cOByJZfs8hYIw==",
+      "license": "MIT",
+      "dependencies": {
+        "mdn-data": "2.0.30",
+        "source-map-js": "^1.0.1"
+      },
+      "engines": {
+        "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0"
+      }
+    },
+    "node_modules/@iconify/tools/node_modules/mdn-data": {
+      "version": "2.0.30",
+      "resolved": "https://registry.npmjs.org/mdn-data/-/mdn-data-2.0.30.tgz",
+      "integrity": "sha512-GaqWWShW4kv/G9IEucWScBx9G1/vsFZZJUO+tD26M8J8z3Kw5RDQjaoZe03YAClgeS/SWPOcb4nkFBTEi5DUEA==",
+      "license": "CC0-1.0"
+    },
+    "node_modules/@iconify/tools/node_modules/svgo": {
+      "version": "3.3.3",
+      "resolved": "https://registry.npmjs.org/svgo/-/svgo-3.3.3.tgz",
+      "integrity": "sha512-+wn7I4p7YgJhHs38k2TNjy1vCfPIfLIJWR5MnCStsN8WuuTcBnRKcMHQLMM2ijxGZmDoZwNv8ipl5aTTen62ng==",
+      "license": "MIT",
+      "dependencies": {
+        "commander": "^7.2.0",
+        "css-select": "^5.1.0",
+        "css-tree": "^2.3.1",
+        "css-what": "^6.1.0",
+        "csso": "^5.0.5",
+        "picocolors": "^1.0.0",
+        "sax": "^1.5.0"
+      },
+      "bin": {
+        "svgo": "bin/svgo"
+      },
+      "engines": {
+        "node": ">=14.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/svgo"
+      }
+    },
+    "node_modules/@iconify/types": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/@iconify/types/-/types-2.0.0.tgz",
+      "integrity": "sha512-+wluvCrRhXrhyOmRDJ3q8mux9JkKy5SJ/v8ol2tu4FVjyYvtEzkc/3pK15ET6RKg4b4w4BmTk1+gsCUhf21Ykg==",
+      "license": "MIT"
+    },
+    "node_modules/@iconify/utils": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/@iconify/utils/-/utils-2.3.0.tgz",
+      "integrity": "sha512-GmQ78prtwYW6EtzXRU1rY+KwOKfz32PD7iJh6Iyqw68GiKuoZ2A6pRtzWONz5VQJbp50mEjXh/7NkumtrAgRKA==",
+      "license": "MIT",
+      "dependencies": {
+        "@antfu/install-pkg": "^1.0.0",
+        "@antfu/utils": "^8.1.0",
+        "@iconify/types": "^2.0.0",
+        "debug": "^4.4.0",
+        "globals": "^15.14.0",
+        "kolorist": "^1.8.0",
+        "local-pkg": "^1.0.0",
+        "mlly": "^1.7.4"
+      }
+    },
+    "node_modules/@iconify/utils/node_modules/globals": {
+      "version": "15.15.0",
+      "resolved": "https://registry.npmjs.org/globals/-/globals-15.15.0.tgz",
+      "integrity": "sha512-7ACyT3wmyp3I61S4fG682L0VA2RGD9otkqGJIwNUMF1SWUombIIk+af1unuDYgMm082aHYwD+mzJvv9Iu8dsgg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/@img/colour": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/@img/colour/-/colour-1.0.0.tgz",
+      "integrity": "sha512-A5P/LfWGFSl6nsckYtjw9da+19jB8hkJ6ACTGcDfEJ0aE+l2n2El7dsVM7UVHZQ9s2lmYMWlrS21YLy2IR1LUw==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@img/sharp-darwin-arm64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-darwin-arm64/-/sharp-darwin-arm64-0.34.5.tgz",
+      "integrity": "sha512-imtQ3WMJXbMY4fxb/Ndp6HBTNVtWCUI0WdobyheGf5+ad6xX8VIDO8u2xE4qc/fr08CKG/7dDseFtn6M6g/r3w==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-darwin-arm64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-darwin-x64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-darwin-x64/-/sharp-darwin-x64-0.34.5.tgz",
+      "integrity": "sha512-YNEFAF/4KQ/PeW0N+r+aVVsoIY0/qxxikF2SWdp+NRkmMB7y9LBZAVqQ4yhGCm/H3H270OSykqmQMKLBhBJDEw==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-darwin-x64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-libvips-darwin-arm64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-arm64/-/sharp-libvips-darwin-arm64-1.2.4.tgz",
+      "integrity": "sha512-zqjjo7RatFfFoP0MkQ51jfuFZBnVE2pRiaydKJ1G/rHZvnsrHAOcQALIi9sA5co5xenQdTugCvtb1cuf78Vf4g==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-darwin-x64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-darwin-x64/-/sharp-libvips-darwin-x64-1.2.4.tgz",
+      "integrity": "sha512-1IOd5xfVhlGwX+zXv2N93k0yMONvUlANylbJw1eTah8K/Jtpi15KC+WSiaX/nBmbm2HxRM1gZ0nSdjSsrZbGKg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-arm": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm/-/sharp-libvips-linux-arm-1.2.4.tgz",
+      "integrity": "sha512-bFI7xcKFELdiNCVov8e44Ia4u2byA+l3XtsAj+Q8tfCwO6BQ8iDojYdvoPMqsKDkuoOo+X6HZA0s0q11ANMQ8A==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-arm64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-arm64/-/sharp-libvips-linux-arm64-1.2.4.tgz",
+      "integrity": "sha512-excjX8DfsIcJ10x1Kzr4RcWe1edC9PquDRRPx3YVCvQv+U5p7Yin2s32ftzikXojb1PIFc/9Mt28/y+iRklkrw==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-ppc64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-ppc64/-/sharp-libvips-linux-ppc64-1.2.4.tgz",
+      "integrity": "sha512-FMuvGijLDYG6lW+b/UvyilUWu5Ayu+3r2d1S8notiGCIyYU/76eig1UfMmkZ7vwgOrzKzlQbFSuQfgm7GYUPpA==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-riscv64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-riscv64/-/sharp-libvips-linux-riscv64-1.2.4.tgz",
+      "integrity": "sha512-oVDbcR4zUC0ce82teubSm+x6ETixtKZBh/qbREIOcI3cULzDyb18Sr/Wcyx7NRQeQzOiHTNbZFF1UwPS2scyGA==",
+      "cpu": [
+        "riscv64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-s390x": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-s390x/-/sharp-libvips-linux-s390x-1.2.4.tgz",
+      "integrity": "sha512-qmp9VrzgPgMoGZyPvrQHqk02uyjA0/QrTO26Tqk6l4ZV0MPWIW6LTkqOIov+J1yEu7MbFQaDpwdwJKhbJvuRxQ==",
+      "cpu": [
+        "s390x"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linux-x64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-x64/-/sharp-libvips-linux-x64-1.2.4.tgz",
+      "integrity": "sha512-tJxiiLsmHc9Ax1bz3oaOYBURTXGIRDODBqhveVHonrHJ9/+k89qbLl0bcJns+e4t4rvaNBxaEZsFtSfAdquPrw==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linuxmusl-arm64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-arm64/-/sharp-libvips-linuxmusl-arm64-1.2.4.tgz",
+      "integrity": "sha512-FVQHuwx1IIuNow9QAbYUzJ+En8KcVm9Lk5+uGUQJHaZmMECZmOlix9HnH7n1TRkXMS0pGxIJokIVB9SuqZGGXw==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-libvips-linuxmusl-x64": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/@img/sharp-libvips-linuxmusl-x64/-/sharp-libvips-linuxmusl-x64-1.2.4.tgz",
+      "integrity": "sha512-+LpyBk7L44ZIXwz/VYfglaX/okxezESc6UxDSoyo2Ks6Jxc4Y7sGjpgU9s4PMgqgjj1gZCylTieNamqA1MF7Dg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-linux-arm": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm/-/sharp-linux-arm-0.34.5.tgz",
+      "integrity": "sha512-9dLqsvwtg1uuXBGZKsxem9595+ujv0sJ6Vi8wcTANSFpwV/GONat5eCkzQo/1O6zRIkh0m/8+5BjrRr7jDUSZw==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-arm": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linux-arm64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-arm64/-/sharp-linux-arm64-0.34.5.tgz",
+      "integrity": "sha512-bKQzaJRY/bkPOXyKx5EVup7qkaojECG6NLYswgktOZjaXecSAeCWiZwwiFf3/Y+O1HrauiE3FVsGxFg8c24rZg==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-arm64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linux-ppc64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-ppc64/-/sharp-linux-ppc64-0.34.5.tgz",
+      "integrity": "sha512-7zznwNaqW6YtsfrGGDA6BRkISKAAE1Jo0QdpNYXNMHu2+0dTrPflTLNkpc8l7MUP5M16ZJcUvysVWWrMefZquA==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-ppc64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linux-riscv64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-riscv64/-/sharp-linux-riscv64-0.34.5.tgz",
+      "integrity": "sha512-51gJuLPTKa7piYPaVs8GmByo7/U7/7TZOq+cnXJIHZKavIRHAP77e3N2HEl3dgiqdD/w0yUfiJnII77PuDDFdw==",
+      "cpu": [
+        "riscv64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-riscv64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linux-s390x": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-s390x/-/sharp-linux-s390x-0.34.5.tgz",
+      "integrity": "sha512-nQtCk0PdKfho3eC5MrbQoigJ2gd1CgddUMkabUj+rBevs8tZ2cULOx46E7oyX+04WGfABgIwmMC0VqieTiR4jg==",
+      "cpu": [
+        "s390x"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-s390x": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linux-x64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linux-x64/-/sharp-linux-x64-0.34.5.tgz",
+      "integrity": "sha512-MEzd8HPKxVxVenwAa+JRPwEC7QFjoPWuS5NZnBt6B3pu7EG2Ge0id1oLHZpPJdn3OQK+BQDiw9zStiHBTJQQQQ==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linux-x64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linuxmusl-arm64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-arm64/-/sharp-linuxmusl-arm64-0.34.5.tgz",
+      "integrity": "sha512-fprJR6GtRsMt6Kyfq44IsChVZeGN97gTD331weR1ex1c1rypDEABN6Tm2xa1wE6lYb5DdEnk03NZPqA7Id21yg==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linuxmusl-arm64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-linuxmusl-x64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-linuxmusl-x64/-/sharp-linuxmusl-x64-0.34.5.tgz",
+      "integrity": "sha512-Jg8wNT1MUzIvhBFxViqrEhWDGzqymo3sV7z7ZsaWbZNDLXRJZoRGrjulp60YYtV4wfY8VIKcWidjojlLcWrd8Q==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "Apache-2.0",
+      "optional": true,
+      "os": [
+        "linux"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-libvips-linuxmusl-x64": "1.2.4"
+      }
+    },
+    "node_modules/@img/sharp-wasm32": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-wasm32/-/sharp-wasm32-0.34.5.tgz",
+      "integrity": "sha512-OdWTEiVkY2PHwqkbBI8frFxQQFekHaSSkUIJkwzclWZe64O1X4UlUjqqqLaPbUpMOQk6FBu/HtlGXNblIs0huw==",
+      "cpu": [
+        "wasm32"
+      ],
+      "license": "Apache-2.0 AND LGPL-3.0-or-later AND MIT",
+      "optional": true,
+      "dependencies": {
+        "@emnapi/runtime": "^1.7.0"
+      },
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-win32-arm64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-win32-arm64/-/sharp-win32-arm64-0.34.5.tgz",
+      "integrity": "sha512-WQ3AgWCWYSb2yt+IG8mnC6Jdk9Whs7O0gxphblsLvdhSpSTtmu69ZG1Gkb6NuvxsNACwiPV6cNSZNzt0KPsw7g==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "Apache-2.0 AND LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-win32-ia32": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-win32-ia32/-/sharp-win32-ia32-0.34.5.tgz",
+      "integrity": "sha512-FV9m/7NmeCmSHDD5j4+4pNI8Cp3aW+JvLoXcTUo0IqyjSfAZJ8dIUmijx1qaJsIiU+Hosw6xM5KijAWRJCSgNg==",
+      "cpu": [
+        "ia32"
+      ],
+      "license": "Apache-2.0 AND LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@img/sharp-win32-x64": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/@img/sharp-win32-x64/-/sharp-win32-x64-0.34.5.tgz",
+      "integrity": "sha512-+29YMsqY2/9eFEiW93eqWnuLcWcufowXewwSNIT6UwZdUUCrM3oFjMWH/Z6/TMmb4hlFenmfAVbpWeup2jryCw==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "Apache-2.0 AND LGPL-3.0-or-later",
+      "optional": true,
+      "os": [
+        "win32"
+      ],
+      "engines": {
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/libvips"
+      }
+    },
+    "node_modules/@isaacs/fs-minipass": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/@isaacs/fs-minipass/-/fs-minipass-4.0.1.tgz",
+      "integrity": "sha512-wgm9Ehl2jpeqP3zw/7mo3kRHFp5MEDhqAdwy1fTGkHAwnkGOVsgpvQhL8B5n1qlb01jV3n/bI0ZfZp5lWA1k4w==",
+      "license": "ISC",
+      "dependencies": {
+        "minipass": "^7.0.4"
+      },
+      "engines": {
+        "node": ">=18.0.0"
+      }
+    },
+    "node_modules/@jridgewell/gen-mapping": {
+      "version": "0.3.13",
+      "resolved": "https://registry.npmjs.org/@jridgewell/gen-mapping/-/gen-mapping-0.3.13.tgz",
+      "integrity": "sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA==",
+      "dependencies": {
+        "@jridgewell/sourcemap-codec": "^1.5.0",
+        "@jridgewell/trace-mapping": "^0.3.24"
+      }
+    },
+    "node_modules/@jridgewell/remapping": {
+      "version": "2.3.5",
+      "resolved": "https://registry.npmjs.org/@jridgewell/remapping/-/remapping-2.3.5.tgz",
+      "integrity": "sha512-LI9u/+laYG4Ds1TDKSJW2YPrIlcVYOwi2fUC6xB43lueCjgxV4lffOCZCtYFiH6TNOX+tQKXx97T4IKHbhyHEQ==",
+      "dependencies": {
+        "@jridgewell/gen-mapping": "^0.3.5",
+        "@jridgewell/trace-mapping": "^0.3.24"
+      }
+    },
+    "node_modules/@jridgewell/resolve-uri": {
+      "version": "3.1.2",
+      "resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.1.2.tgz",
+      "integrity": "sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==",
+      "engines": {
+        "node": ">=6.0.0"
+      }
+    },
+    "node_modules/@jridgewell/sourcemap-codec": {
+      "version": "1.5.5",
+      "resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.5.5.tgz",
+      "integrity": "sha512-cYQ9310grqxueWbl+WuIUIaiUaDcj7WOq5fVhEljNVgRfOUhY9fy2zTvfoqWsnebh8Sl70VScFbICvJnLKB0Og==",
+      "license": "MIT"
+    },
+    "node_modules/@jridgewell/trace-mapping": {
+      "version": "0.3.31",
+      "resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.31.tgz",
+      "integrity": "sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw==",
+      "dependencies": {
+        "@jridgewell/resolve-uri": "^3.1.0",
+        "@jridgewell/sourcemap-codec": "^1.4.14"
+      }
+    },
+    "node_modules/@mdx-js/mdx": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/@mdx-js/mdx/-/mdx-3.1.1.tgz",
+      "integrity": "sha512-f6ZO2ifpwAQIpzGWaBQT2TXxPv6z3RBzQKpVftEWN78Vl/YweF1uwussDx8ECAXVtr3Rs89fKyG9YlzUs9DyGQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "@types/estree-jsx": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "@types/mdx": "^2.0.0",
+        "acorn": "^8.0.0",
+        "collapse-white-space": "^2.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-is-identifier-name": "^3.0.0",
+        "estree-util-scope": "^1.0.0",
+        "estree-walker": "^3.0.0",
+        "hast-util-to-jsx-runtime": "^2.0.0",
+        "markdown-extensions": "^2.0.0",
+        "recma-build-jsx": "^1.0.0",
+        "recma-jsx": "^1.0.0",
+        "recma-stringify": "^1.0.0",
+        "rehype-recma": "^1.0.0",
+        "remark-mdx": "^3.0.0",
+        "remark-parse": "^11.0.0",
+        "remark-rehype": "^11.0.0",
+        "source-map": "^0.7.0",
+        "unified": "^11.0.0",
+        "unist-util-position-from-estree": "^2.0.0",
+        "unist-util-stringify-position": "^4.0.0",
+        "unist-util-visit": "^5.0.0",
+        "vfile": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/@noble/hashes": {
+      "version": "1.8.0",
+      "resolved": "https://registry.npmjs.org/@noble/hashes/-/hashes-1.8.0.tgz",
+      "integrity": "sha512-jCs9ldd7NwzpgXDIf6P3+NrHh9/sD6CQdxHyjQI+h/6rDNo88ypBxxz45UDuZHz9r3tNz7N/VInSVoVdtXEI4A==",
+      "license": "MIT",
+      "engines": {
+        "node": "^14.21.3 || >=16"
+      },
+      "funding": {
+        "url": "https://paulmillr.com/funding/"
+      }
+    },
+    "node_modules/@nodelib/fs.scandir": {
+      "version": "2.1.5",
+      "resolved": "https://registry.npmjs.org/@nodelib/fs.scandir/-/fs.scandir-2.1.5.tgz",
+      "integrity": "sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@nodelib/fs.stat": "2.0.5",
+        "run-parallel": "^1.1.9"
+      },
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/@nodelib/fs.stat": {
+      "version": "2.0.5",
+      "resolved": "https://registry.npmjs.org/@nodelib/fs.stat/-/fs.stat-2.0.5.tgz",
+      "integrity": "sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/@nodelib/fs.walk": {
+      "version": "1.2.8",
+      "resolved": "https://registry.npmjs.org/@nodelib/fs.walk/-/fs.walk-1.2.8.tgz",
+      "integrity": "sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@nodelib/fs.scandir": "2.1.5",
+        "fastq": "^1.6.0"
+      },
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/@orama/core": {
+      "version": "1.2.19",
+      "resolved": "https://registry.npmjs.org/@orama/core/-/core-1.2.19.tgz",
+      "integrity": "sha512-AVEI0eG/a1RUQK+tBloRMppQf46Ky4kIYKEVjo0V0VfIGZHdLOE2PJR4v949kFwiTnfSJCUaxgwM74FCA1uHUA==",
+      "license": "AGPL-3.0",
+      "peer": true,
+      "dependencies": {
+        "@orama/cuid2": "2.2.3",
+        "@orama/oramacore-events-parser": "0.0.5"
+      }
+    },
+    "node_modules/@orama/cuid2": {
+      "version": "2.2.3",
+      "resolved": "https://registry.npmjs.org/@orama/cuid2/-/cuid2-2.2.3.tgz",
+      "integrity": "sha512-Lcak3chblMejdlSHgYU2lS2cdOhDpU6vkfIJH4m+YKvqQyLqs1bB8+w6NT1MG5bO12NUK2GFc34Mn2xshMIQ1g==",
+      "license": "MIT",
+      "dependencies": {
+        "@noble/hashes": "^1.1.5"
+      }
+    },
+    "node_modules/@orama/oramacore-events-parser": {
+      "version": "0.0.5",
+      "resolved": "https://registry.npmjs.org/@orama/oramacore-events-parser/-/oramacore-events-parser-0.0.5.tgz",
+      "integrity": "sha512-yAuSwog+HQBAXgZ60TNKEwu04y81/09mpbYBCmz1RCxnr4ObNY2JnPZI7HmALbjAhLJ8t5p+wc2JHRK93ubO4w==",
+      "license": "AGPL-3.0"
+    },
+    "node_modules/@orama/stopwords": {
+      "version": "3.1.18",
+      "resolved": "https://registry.npmjs.org/@orama/stopwords/-/stopwords-3.1.18.tgz",
+      "integrity": "sha512-W8V7m7RnCme+99OmKl/xs5rf6OUhFpr0aPGVmPrXzTLSg4ZqSbRY2euS2S/lgjjYi/0NhEWqwoq8nDY6Ihx4EA==",
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">= 20.0.0"
+      }
+    },
+    "node_modules/@orama/ui": {
+      "version": "1.5.4",
+      "resolved": "https://registry.npmjs.org/@orama/ui/-/ui-1.5.4.tgz",
+      "integrity": "sha512-lljPUpyYQ2aOWXDyfIOyI6DROHcCPfGT44I+Ji3W0EEnv4RZQEQchMDJp+8Mhxwy+qW7nJKRr5GA0rmgzQVVPg==",
+      "license": "MIT",
+      "dependencies": {
+        "@orama/stopwords": "^3.1.16",
+        "prism-react-renderer": "^1.3.5",
+        "react-markdown": "^10.1.0",
+        "remark-gfm": "^4.0.1",
+        "throttleit": "^2.1.0"
+      },
+      "peerDependencies": {
+        "@orama/core": "^1.2.13"
+      }
+    },
+    "node_modules/@oslojs/encoding": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/@oslojs/encoding/-/encoding-1.1.0.tgz",
+      "integrity": "sha512-70wQhgYmndg4GCPxPPxPGevRKqTIJ2Nh4OkiMWmDAVYsTQ+Ta7Sq+rPevXyXGdzr30/qZBnyOalCszoMxlyldQ==",
+      "license": "MIT"
+    },
+    "node_modules/@pkgr/core": {
+      "version": "0.2.9",
+      "resolved": "https://registry.npmjs.org/@pkgr/core/-/core-0.2.9.tgz",
+      "integrity": "sha512-QNqXyfVS2wm9hweSYD2O7F0G06uurj9kZ96TRQE5Y9hU7+tgdZwIkbAKc5Ocy1HxEY2kuDQa6cQ1WRs/O5LFKA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "^12.20.0 || ^14.18.0 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/pkgr"
+      }
+    },
+    "node_modules/@playwright/test": {
+      "version": "1.59.1",
+      "resolved": "https://registry.npmjs.org/@playwright/test/-/test-1.59.1.tgz",
+      "integrity": "sha512-PG6q63nQg5c9rIi4/Z5lR5IVF7yU5MqmKaPOe0HSc0O2cX1fPi96sUQu5j7eo4gKCkB2AnNGoWt7y4/Xx3Kcqg==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "playwright": "1.59.1"
+      },
+      "bin": {
+        "playwright": "cli.js"
+      },
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/@rolldown/pluginutils": {
+      "version": "1.0.0-rc.3",
+      "resolved": "https://registry.npmjs.org/@rolldown/pluginutils/-/pluginutils-1.0.0-rc.3.tgz",
+      "integrity": "sha512-eybk3TjzzzV97Dlj5c+XrBFW57eTNhzod66y9HrBlzJ6NsCrWCp/2kaPS3K9wJmurBC0Tdw4yPjXKZqlznim3Q==",
+      "license": "MIT"
+    },
+    "node_modules/@rollup/pluginutils": {
+      "version": "5.3.0",
+      "resolved": "https://registry.npmjs.org/@rollup/pluginutils/-/pluginutils-5.3.0.tgz",
+      "integrity": "sha512-5EdhGZtnu3V88ces7s53hhfK5KSASnJZv8Lulpc04cWO3REESroJXg73DFsOmgbU2BhwV0E20bu2IDZb3VKW4Q==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "estree-walker": "^2.0.2",
+        "picomatch": "^4.0.2"
+      },
+      "engines": {
+        "node": ">=14.0.0"
+      },
+      "peerDependencies": {
+        "rollup": "^1.20.0||^2.0.0||^3.0.0||^4.0.0"
+      },
+      "peerDependenciesMeta": {
+        "rollup": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/@rollup/pluginutils/node_modules/estree-walker": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/estree-walker/-/estree-walker-2.0.2.tgz",
+      "integrity": "sha512-Rfkk/Mp/DL7JVje3u18FxFujQlTNR2q6QfMSMB7AvCBx91NGj/ba3kCfza0f6dVDbw7YlRf/nDrn7pQrCCyQ/w==",
+      "license": "MIT"
+    },
+    "node_modules/@rollup/rollup-android-arm-eabi": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm-eabi/-/rollup-android-arm-eabi-4.59.0.tgz",
+      "integrity": "sha512-upnNBkA6ZH2VKGcBj9Fyl9IGNPULcjXRlg0LLeaioQWueH30p6IXtJEbKAgvyv+mJaMxSm1l6xwDXYjpEMiLMg==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "android"
+      ]
+    },
+    "node_modules/@rollup/rollup-android-arm64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-android-arm64/-/rollup-android-arm64-4.59.0.tgz",
+      "integrity": "sha512-hZ+Zxj3SySm4A/DylsDKZAeVg0mvi++0PYVceVyX7hemkw7OreKdCvW2oQ3T1FMZvCaQXqOTHb8qmBShoqk69Q==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "android"
+      ]
+    },
+    "node_modules/@rollup/rollup-darwin-arm64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-arm64/-/rollup-darwin-arm64-4.59.0.tgz",
+      "integrity": "sha512-W2Psnbh1J8ZJw0xKAd8zdNgF9HRLkdWwwdWqubSVk0pUuQkoHnv7rx4GiF9rT4t5DIZGAsConRE3AxCdJ4m8rg==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ]
+    },
+    "node_modules/@rollup/rollup-darwin-x64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-darwin-x64/-/rollup-darwin-x64-4.59.0.tgz",
+      "integrity": "sha512-ZW2KkwlS4lwTv7ZVsYDiARfFCnSGhzYPdiOU4IM2fDbL+QGlyAbjgSFuqNRbSthybLbIJ915UtZBtmuLrQAT/w==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ]
+    },
+    "node_modules/@rollup/rollup-freebsd-arm64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-freebsd-arm64/-/rollup-freebsd-arm64-4.59.0.tgz",
+      "integrity": "sha512-EsKaJ5ytAu9jI3lonzn3BgG8iRBjV4LxZexygcQbpiU0wU0ATxhNVEpXKfUa0pS05gTcSDMKpn3Sx+QB9RlTTA==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "freebsd"
+      ]
+    },
+    "node_modules/@rollup/rollup-freebsd-x64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-freebsd-x64/-/rollup-freebsd-x64-4.59.0.tgz",
+      "integrity": "sha512-d3DuZi2KzTMjImrxoHIAODUZYoUUMsuUiY4SRRcJy6NJoZ6iIqWnJu9IScV9jXysyGMVuW+KNzZvBLOcpdl3Vg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "freebsd"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-arm-gnueabihf": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-gnueabihf/-/rollup-linux-arm-gnueabihf-4.59.0.tgz",
+      "integrity": "sha512-t4ONHboXi/3E0rT6OZl1pKbl2Vgxf9vJfWgmUoCEVQVxhW6Cw/c8I6hbbu7DAvgp82RKiH7TpLwxnJeKv2pbsw==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-arm-musleabihf": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm-musleabihf/-/rollup-linux-arm-musleabihf-4.59.0.tgz",
+      "integrity": "sha512-CikFT7aYPA2ufMD086cVORBYGHffBo4K8MQ4uPS/ZnY54GKj36i196u8U+aDVT2LX4eSMbyHtyOh7D7Zvk2VvA==",
+      "cpu": [
+        "arm"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-arm64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-gnu/-/rollup-linux-arm64-gnu-4.59.0.tgz",
+      "integrity": "sha512-jYgUGk5aLd1nUb1CtQ8E+t5JhLc9x5WdBKew9ZgAXg7DBk0ZHErLHdXM24rfX+bKrFe+Xp5YuJo54I5HFjGDAA==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-arm64-musl": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-arm64-musl/-/rollup-linux-arm64-musl-4.59.0.tgz",
+      "integrity": "sha512-peZRVEdnFWZ5Bh2KeumKG9ty7aCXzzEsHShOZEFiCQlDEepP1dpUl/SrUNXNg13UmZl+gzVDPsiCwnV1uI0RUA==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-loong64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-loong64-gnu/-/rollup-linux-loong64-gnu-4.59.0.tgz",
+      "integrity": "sha512-gbUSW/97f7+r4gHy3Jlup8zDG190AuodsWnNiXErp9mT90iCy9NKKU0Xwx5k8VlRAIV2uU9CsMnEFg/xXaOfXg==",
+      "cpu": [
+        "loong64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-loong64-musl": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-loong64-musl/-/rollup-linux-loong64-musl-4.59.0.tgz",
+      "integrity": "sha512-yTRONe79E+o0FWFijasoTjtzG9EBedFXJMl888NBEDCDV9I2wGbFFfJQQe63OijbFCUZqxpHz1GzpbtSFikJ4Q==",
+      "cpu": [
+        "loong64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-ppc64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-ppc64-gnu/-/rollup-linux-ppc64-gnu-4.59.0.tgz",
+      "integrity": "sha512-sw1o3tfyk12k3OEpRddF68a1unZ5VCN7zoTNtSn2KndUE+ea3m3ROOKRCZxEpmT9nsGnogpFP9x6mnLTCaoLkA==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-ppc64-musl": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-ppc64-musl/-/rollup-linux-ppc64-musl-4.59.0.tgz",
+      "integrity": "sha512-+2kLtQ4xT3AiIxkzFVFXfsmlZiG5FXYW7ZyIIvGA7Bdeuh9Z0aN4hVyXS/G1E9bTP/vqszNIN/pUKCk/BTHsKA==",
+      "cpu": [
+        "ppc64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-riscv64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-riscv64-gnu/-/rollup-linux-riscv64-gnu-4.59.0.tgz",
+      "integrity": "sha512-NDYMpsXYJJaj+I7UdwIuHHNxXZ/b/N2hR15NyH3m2qAtb/hHPA4g4SuuvrdxetTdndfj9b1WOmy73kcPRoERUg==",
+      "cpu": [
+        "riscv64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-riscv64-musl": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-riscv64-musl/-/rollup-linux-riscv64-musl-4.59.0.tgz",
+      "integrity": "sha512-nLckB8WOqHIf1bhymk+oHxvM9D3tyPndZH8i8+35p/1YiVoVswPid2yLzgX7ZJP0KQvnkhM4H6QZ5m0LzbyIAg==",
+      "cpu": [
+        "riscv64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-s390x-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-s390x-gnu/-/rollup-linux-s390x-gnu-4.59.0.tgz",
+      "integrity": "sha512-oF87Ie3uAIvORFBpwnCvUzdeYUqi2wY6jRFWJAy1qus/udHFYIkplYRW+wo+GRUP4sKzYdmE1Y3+rY5Gc4ZO+w==",
+      "cpu": [
+        "s390x"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-x64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-gnu/-/rollup-linux-x64-gnu-4.59.0.tgz",
+      "integrity": "sha512-3AHmtQq/ppNuUspKAlvA8HtLybkDflkMuLK4DPo77DfthRb71V84/c4MlWJXixZz4uruIH4uaa07IqoAkG64fg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-linux-x64-musl": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-linux-x64-musl/-/rollup-linux-x64-musl-4.59.0.tgz",
+      "integrity": "sha512-2UdiwS/9cTAx7qIUZB/fWtToJwvt0Vbo0zmnYt7ED35KPg13Q0ym1g442THLC7VyI6JfYTP4PiSOWyoMdV2/xg==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "linux"
+      ]
+    },
+    "node_modules/@rollup/rollup-openbsd-x64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-openbsd-x64/-/rollup-openbsd-x64-4.59.0.tgz",
+      "integrity": "sha512-M3bLRAVk6GOwFlPTIxVBSYKUaqfLrn8l0psKinkCFxl4lQvOSz8ZrKDz2gxcBwHFpci0B6rttydI4IpS4IS/jQ==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "openbsd"
+      ]
+    },
+    "node_modules/@rollup/rollup-openharmony-arm64": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-openharmony-arm64/-/rollup-openharmony-arm64-4.59.0.tgz",
+      "integrity": "sha512-tt9KBJqaqp5i5HUZzoafHZX8b5Q2Fe7UjYERADll83O4fGqJ49O1FsL6LpdzVFQcpwvnyd0i+K/VSwu/o/nWlA==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "openharmony"
+      ]
+    },
+    "node_modules/@rollup/rollup-win32-arm64-msvc": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-arm64-msvc/-/rollup-win32-arm64-msvc-4.59.0.tgz",
+      "integrity": "sha512-V5B6mG7OrGTwnxaNUzZTDTjDS7F75PO1ae6MJYdiMu60sq0CqN5CVeVsbhPxalupvTX8gXVSU9gq+Rx1/hvu6A==",
+      "cpu": [
+        "arm64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ]
+    },
+    "node_modules/@rollup/rollup-win32-ia32-msvc": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-ia32-msvc/-/rollup-win32-ia32-msvc-4.59.0.tgz",
+      "integrity": "sha512-UKFMHPuM9R0iBegwzKF4y0C4J9u8C6MEJgFuXTBerMk7EJ92GFVFYBfOZaSGLu6COf7FxpQNqhNS4c4icUPqxA==",
+      "cpu": [
+        "ia32"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ]
+    },
+    "node_modules/@rollup/rollup-win32-x64-gnu": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-x64-gnu/-/rollup-win32-x64-gnu-4.59.0.tgz",
+      "integrity": "sha512-laBkYlSS1n2L8fSo1thDNGrCTQMmxjYY5G0WFWjFFYZkKPjsMBsgJfGf4TLxXrF6RyhI60L8TMOjBMvXiTcxeA==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ]
+    },
+    "node_modules/@rollup/rollup-win32-x64-msvc": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/@rollup/rollup-win32-x64-msvc/-/rollup-win32-x64-msvc-4.59.0.tgz",
+      "integrity": "sha512-2HRCml6OztYXyJXAvdDXPKcawukWY2GpR5/nxKp4iBgiO3wcoEGkAaqctIbZcNB6KlUQBIqt8VYkNSj2397EfA==",
+      "cpu": [
+        "x64"
+      ],
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "win32"
+      ]
+    },
+    "node_modules/@shikijs/core": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/core/-/core-3.21.0.tgz",
+      "integrity": "sha512-AXSQu/2n1UIQekY8euBJlvFYZIw0PHY63jUzGbrOma4wPxzznJXTXkri+QcHeBNaFxiiOljKxxJkVSoB3PjbyA==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "3.21.0",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4",
+        "hast-util-to-html": "^9.0.5"
+      }
+    },
+    "node_modules/@shikijs/engine-javascript": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-javascript/-/engine-javascript-3.21.0.tgz",
+      "integrity": "sha512-ATwv86xlbmfD9n9gKRiwuPpWgPENAWCLwYCGz9ugTJlsO2kOzhOkvoyV/UD+tJ0uT7YRyD530x6ugNSffmvIiQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "3.21.0",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "oniguruma-to-es": "^4.3.4"
+      }
+    },
+    "node_modules/@shikijs/engine-oniguruma": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-oniguruma/-/engine-oniguruma-3.21.0.tgz",
+      "integrity": "sha512-OYknTCct6qiwpQDqDdf3iedRdzj6hFlOPv5hMvI+hkWfCKs5mlJ4TXziBG9nyabLwGulrUjHiCq3xCspSzErYQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "3.21.0",
+        "@shikijs/vscode-textmate": "^10.0.2"
+      }
+    },
+    "node_modules/@shikijs/langs": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/langs/-/langs-3.21.0.tgz",
+      "integrity": "sha512-g6mn5m+Y6GBJ4wxmBYqalK9Sp0CFkUqfNzUy2pJglUginz6ZpWbaWjDB4fbQ/8SHzFjYbtU6Ddlp1pc+PPNDVA==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "3.21.0"
+      }
+    },
+    "node_modules/@shikijs/primitive": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/primitive/-/primitive-4.0.2.tgz",
+      "integrity": "sha512-M6UMPrSa3fN5ayeJwFVl9qWofl273wtK1VG8ySDZ1mQBfhCpdd8nEx7nPZ/tk7k+TYcpqBZzj/AnwxT9lO+HJw==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/@shikijs/primitive/node_modules/@shikijs/types": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/types/-/types-4.0.2.tgz",
+      "integrity": "sha512-qzbeRooUTPnLE+sHD/Z8DStmaDgnbbc/pMrU203950aRqjX/6AFHeDYT+j00y2lPdz0ywJKx7o/7qnqTivtlXg==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/@shikijs/themes": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/themes/-/themes-3.21.0.tgz",
+      "integrity": "sha512-BAE4cr9EDiZyYzwIHEk7JTBJ9CzlPuM4PchfcA5ao1dWXb25nv6hYsoDiBq2aZK9E3dlt3WB78uI96UESD+8Mw==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "3.21.0"
+      }
+    },
+    "node_modules/@shikijs/types": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/@shikijs/types/-/types-3.21.0.tgz",
+      "integrity": "sha512-zGrWOxZ0/+0ovPY7PvBU2gIS9tmhSUUt30jAcNV0Bq0gb2S98gwfjIs1vxlmH5zM7/4YxLamT6ChlqqAJmPPjA==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      }
+    },
+    "node_modules/@shikijs/vscode-textmate": {
+      "version": "10.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/vscode-textmate/-/vscode-textmate-10.0.2.tgz",
+      "integrity": "sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==",
+      "license": "MIT"
+    },
+    "node_modules/@shuding/opentype.js": {
+      "version": "1.4.0-beta.0",
+      "resolved": "https://registry.npmjs.org/@shuding/opentype.js/-/opentype.js-1.4.0-beta.0.tgz",
+      "integrity": "sha512-3NgmNyH3l/Hv6EvsWJbsvpcpUba6R8IREQ83nH83cyakCw7uM1arZKNfHwv1Wz6jgqrF/j4x5ELvR6PnK9nTcA==",
+      "license": "MIT",
+      "dependencies": {
+        "fflate": "^0.7.3",
+        "string.prototype.codepointat": "^0.2.1"
+      },
+      "bin": {
+        "ot": "bin/ot"
+      },
+      "engines": {
+        "node": ">= 8.0.0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-add-jsx-attribute": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-add-jsx-attribute/-/babel-plugin-add-jsx-attribute-8.0.0.tgz",
+      "integrity": "sha512-b9MIk7yhdS1pMCZM8VeNfUlSKVRhsHZNMl5O9SfaX0l0t5wjdgu4IDzGB8bpnGBBOjGST3rRFVsaaEtI4W6f7g==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-remove-jsx-attribute": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-remove-jsx-attribute/-/babel-plugin-remove-jsx-attribute-8.0.0.tgz",
+      "integrity": "sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-remove-jsx-empty-expression": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-remove-jsx-empty-expression/-/babel-plugin-remove-jsx-empty-expression-8.0.0.tgz",
+      "integrity": "sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-replace-jsx-attribute-value": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-replace-jsx-attribute-value/-/babel-plugin-replace-jsx-attribute-value-8.0.0.tgz",
+      "integrity": "sha512-KVQ+PtIjb1BuYT3ht8M5KbzWBhdAjjUPdlMtpuw/VjT8coTrItWX6Qafl9+ji831JaJcu6PJNKCV0bp01lBNzQ==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-svg-dynamic-title": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-svg-dynamic-title/-/babel-plugin-svg-dynamic-title-8.0.0.tgz",
+      "integrity": "sha512-omNiKqwjNmOQJ2v6ge4SErBbkooV2aAWwaPFs2vUY7p7GhVkzRkJ00kILXQvRhA6miHnNpXv7MRnnSjdRjK8og==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-svg-em-dimensions": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-svg-em-dimensions/-/babel-plugin-svg-em-dimensions-8.0.0.tgz",
+      "integrity": "sha512-mURHYnu6Iw3UBTbhGwE/vsngtCIbHE43xCRK7kCw4t01xyGqb2Pd+WXekRRoFOBIY29ZoOhUCTEweDMdrjfi9g==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-transform-react-native-svg": {
+      "version": "8.1.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-transform-react-native-svg/-/babel-plugin-transform-react-native-svg-8.1.0.tgz",
+      "integrity": "sha512-Tx8T58CHo+7nwJ+EhUwx3LfdNSG9R2OKfaIXXs5soiy5HtgoAEkDay9LIimLOcG8dJQH1wPZp/cnAv6S9CrR1Q==",
+      "dev": true,
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-plugin-transform-svg-component": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-plugin-transform-svg-component/-/babel-plugin-transform-svg-component-8.0.0.tgz",
+      "integrity": "sha512-DFx8xa3cZXTdb/k3kfPeaixecQLgKh5NVBMwD0AQxOzcZawK4oo1Jh9LbrcACUivsCA7TLG8eeWgrDXjTMhRmw==",
+      "dev": true,
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/babel-preset": {
+      "version": "8.1.0",
+      "resolved": "https://registry.npmjs.org/@svgr/babel-preset/-/babel-preset-8.1.0.tgz",
+      "integrity": "sha512-7EYDbHE7MxHpv4sxvnVPngw5fuR6pw79SkcrILHJ/iMpuKySNCl5W1qcwPEpU+LgyRXOaAFgH0KhwD18wwg6ug==",
+      "dev": true,
+      "dependencies": {
+        "@svgr/babel-plugin-add-jsx-attribute": "8.0.0",
+        "@svgr/babel-plugin-remove-jsx-attribute": "8.0.0",
+        "@svgr/babel-plugin-remove-jsx-empty-expression": "8.0.0",
+        "@svgr/babel-plugin-replace-jsx-attribute-value": "8.0.0",
+        "@svgr/babel-plugin-svg-dynamic-title": "8.0.0",
+        "@svgr/babel-plugin-svg-em-dimensions": "8.0.0",
+        "@svgr/babel-plugin-transform-react-native-svg": "8.1.0",
+        "@svgr/babel-plugin-transform-svg-component": "8.0.0"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@babel/core": "^7.0.0-0"
+      }
+    },
+    "node_modules/@svgr/core": {
+      "version": "8.1.0",
+      "resolved": "https://registry.npmjs.org/@svgr/core/-/core-8.1.0.tgz",
+      "integrity": "sha512-8QqtOQT5ACVlmsvKOJNEaWmRPmcojMOzCz4Hs2BGG/toAp/K38LcsMRyLp349glq5AzJbCEeimEoxaX6v/fLrA==",
+      "dev": true,
+      "peer": true,
+      "dependencies": {
+        "@babel/core": "^7.21.3",
+        "@svgr/babel-preset": "8.1.0",
+        "camelcase": "^6.2.0",
+        "cosmiconfig": "^8.1.3",
+        "snake-case": "^3.0.4"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      }
+    },
+    "node_modules/@svgr/core/node_modules/camelcase": {
+      "version": "6.3.0",
+      "resolved": "https://registry.npmjs.org/camelcase/-/camelcase-6.3.0.tgz",
+      "integrity": "sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==",
+      "dev": true,
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/@svgr/hast-util-to-babel-ast": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/@svgr/hast-util-to-babel-ast/-/hast-util-to-babel-ast-8.0.0.tgz",
+      "integrity": "sha512-EbDKwO9GpfWP4jN9sGdYwPBU0kdomaPIL2Eu4YwmgP+sJeXT+L7bMwJUBnhzfH8Q2qMBqZ4fJwpCyYsAN3mt2Q==",
+      "dev": true,
+      "dependencies": {
+        "@babel/types": "^7.21.3",
+        "entities": "^4.4.0"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      }
+    },
+    "node_modules/@svgr/hast-util-to-babel-ast/node_modules/entities": {
+      "version": "4.5.0",
+      "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz",
+      "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==",
+      "dev": true,
+      "engines": {
+        "node": ">=0.12"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/entities?sponsor=1"
+      }
+    },
+    "node_modules/@svgr/plugin-jsx": {
+      "version": "8.1.0",
+      "resolved": "https://registry.npmjs.org/@svgr/plugin-jsx/-/plugin-jsx-8.1.0.tgz",
+      "integrity": "sha512-0xiIyBsLlr8quN+WyuxooNW9RJ0Dpr8uOnH/xrCVO8GLUcwHISwj1AG0k+LFzteTkAA0GbX0kj9q6Dk70PTiPA==",
+      "dev": true,
+      "dependencies": {
+        "@babel/core": "^7.21.3",
+        "@svgr/babel-preset": "8.1.0",
+        "@svgr/hast-util-to-babel-ast": "8.0.0",
+        "svg-parser": "^2.0.4"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/gregberge"
+      },
+      "peerDependencies": {
+        "@svgr/core": "*"
+      }
+    },
+    "node_modules/@types/babel__core": {
+      "version": "7.20.5",
+      "resolved": "https://registry.npmjs.org/@types/babel__core/-/babel__core-7.20.5.tgz",
+      "integrity": "sha512-qoQprZvz5wQFJwMDqeseRXWv3rqMvhgpbXFfVyWhbx9X47POIA6i/+dXefEmZKoAgOaTdaIgNSMqMIU61yRyzA==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/parser": "^7.20.7",
+        "@babel/types": "^7.20.7",
+        "@types/babel__generator": "*",
+        "@types/babel__template": "*",
+        "@types/babel__traverse": "*"
+      }
+    },
+    "node_modules/@types/babel__generator": {
+      "version": "7.27.0",
+      "resolved": "https://registry.npmjs.org/@types/babel__generator/-/babel__generator-7.27.0.tgz",
+      "integrity": "sha512-ufFd2Xi92OAVPYsy+P4n7/U7e68fex0+Ee8gSG9KX7eo084CWiQ4sdxktvdl0bOPupXtVJPY19zk6EwWqUQ8lg==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/types": "^7.0.0"
+      }
+    },
+    "node_modules/@types/babel__template": {
+      "version": "7.4.4",
+      "resolved": "https://registry.npmjs.org/@types/babel__template/-/babel__template-7.4.4.tgz",
+      "integrity": "sha512-h/NUaSyG5EyxBIp8YRxo4RMe2/qQgvyowRwVMzhYhBCONbW8PUsg4lkFMrhgZhUe5z3L3MiLDuvyJ/CaPa2A8A==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/parser": "^7.1.0",
+        "@babel/types": "^7.0.0"
+      }
+    },
+    "node_modules/@types/babel__traverse": {
+      "version": "7.28.0",
+      "resolved": "https://registry.npmjs.org/@types/babel__traverse/-/babel__traverse-7.28.0.tgz",
+      "integrity": "sha512-8PvcXf70gTDZBgt9ptxJ8elBeBjcLOAcOtoO/mPJjtji1+CdGbHgm77om1GrsPxsiE+uXIpNSK64UYaIwQXd4Q==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/types": "^7.28.2"
+      }
+    },
+    "node_modules/@types/debug": {
+      "version": "4.1.12",
+      "resolved": "https://registry.npmjs.org/@types/debug/-/debug-4.1.12.tgz",
+      "integrity": "sha512-vIChWdVG3LG1SMxEvI/AK+FWJthlrqlTu7fbrlywTkkaONwk/UAGaULXRlf8vkzFBLVm0zkMdCquhL5aOjhXPQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/ms": "*"
+      }
+    },
+    "node_modules/@types/estree": {
+      "version": "1.0.8",
+      "resolved": "https://registry.npmjs.org/@types/estree/-/estree-1.0.8.tgz",
+      "integrity": "sha512-dWHzHa2WqEXI/O1E9OjrocMTKJl2mSrEolh1Iomrv6U+JuNwaHXsXx9bLu5gG7BUWFIN0skIQJQ/L1rIex4X6w==",
+      "license": "MIT"
+    },
+    "node_modules/@types/estree-jsx": {
+      "version": "1.0.5",
+      "resolved": "https://registry.npmjs.org/@types/estree-jsx/-/estree-jsx-1.0.5.tgz",
+      "integrity": "sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "*"
+      }
+    },
+    "node_modules/@types/hast": {
+      "version": "3.0.4",
+      "resolved": "https://registry.npmjs.org/@types/hast/-/hast-3.0.4.tgz",
+      "integrity": "sha512-WPs+bbQw5aCj+x6laNGWLH3wviHtoCv/P3+otBhbOhJgG8qtpdAMlTCxLtsTWA7LH1Oh/bFCHsBn0TPS5m30EQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "*"
+      }
+    },
+    "node_modules/@types/json-schema": {
+      "version": "7.0.15",
+      "resolved": "https://registry.npmjs.org/@types/json-schema/-/json-schema-7.0.15.tgz",
+      "integrity": "sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/@types/mdast": {
+      "version": "4.0.4",
+      "resolved": "https://registry.npmjs.org/@types/mdast/-/mdast-4.0.4.tgz",
+      "integrity": "sha512-kGaNbPh1k7AFzgpud/gMdvIm5xuECykRR+JnWKQno9TAXVa6WIVCGTPvYGekIDL4uwCZQSYbUxNBSb1aUo79oA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "*"
+      }
+    },
+    "node_modules/@types/mdx": {
+      "version": "2.0.13",
+      "resolved": "https://registry.npmjs.org/@types/mdx/-/mdx-2.0.13.tgz",
+      "integrity": "sha512-+OWZQfAYyio6YkJb3HLxDrvnx6SWWDbC0zVPfBRzUk0/nqoDyf6dNxQi3eArPe8rJ473nobTMQ/8Zk+LxJ+Yuw==",
+      "license": "MIT"
+    },
+    "node_modules/@types/ms": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/@types/ms/-/ms-2.1.0.tgz",
+      "integrity": "sha512-GsCCIZDE/p3i96vtEqx+7dBUGXrc7zeSK3wwPHIaRThS+9OhWIXRqzs4d6k1SVU8g91DrNRWxWUGhp5KXQb2VA==",
+      "license": "MIT"
+    },
+    "node_modules/@types/nlcst": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/@types/nlcst/-/nlcst-2.0.3.tgz",
+      "integrity": "sha512-vSYNSDe6Ix3q+6Z7ri9lyWqgGhJTmzRjZRqyq15N0Z/1/UnVsno9G/N40NBijoYx2seFDIl0+B2mgAb9mezUCA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "*"
+      }
+    },
+    "node_modules/@types/node": {
+      "version": "25.3.2",
+      "resolved": "https://registry.npmjs.org/@types/node/-/node-25.3.2.tgz",
+      "integrity": "sha512-RpV6r/ij22zRRdyBPcxDeKAzH43phWVKEjL2iksqo1Vz3CuBUrgmPpPhALKiRfU7OMCmeeO9vECBMsV0hMTG8Q==",
+      "license": "MIT",
+      "dependencies": {
+        "undici-types": "~7.18.0"
+      }
+    },
+    "node_modules/@types/react": {
+      "version": "19.2.14",
+      "resolved": "https://registry.npmjs.org/@types/react/-/react-19.2.14.tgz",
+      "integrity": "sha512-ilcTH/UniCkMdtexkoCN0bI7pMcJDvmQFPvuPvmEaYA/NSfFTAgdUSLAoVjaRJm7+6PvcM+q1zYOwS4wTYMF9w==",
+      "peer": true,
+      "dependencies": {
+        "csstype": "^3.2.2"
+      }
+    },
+    "node_modules/@types/react-dom": {
+      "version": "19.2.3",
+      "resolved": "https://registry.npmjs.org/@types/react-dom/-/react-dom-19.2.3.tgz",
+      "integrity": "sha512-jp2L/eY6fn+KgVVQAOqYItbF0VY/YApe5Mz2F0aykSO8gx31bYCZyvSeYxCHKvzHG5eZjc+zyaS5BrBWya2+kQ==",
+      "peer": true,
+      "peerDependencies": {
+        "@types/react": "^19.2.0"
+      }
+    },
+    "node_modules/@types/sax": {
+      "version": "1.2.7",
+      "resolved": "https://registry.npmjs.org/@types/sax/-/sax-1.2.7.tgz",
+      "integrity": "sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/node": "*"
+      }
+    },
+    "node_modules/@types/unist": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/@types/unist/-/unist-3.0.3.tgz",
+      "integrity": "sha512-ko/gIFJRv177XgZsZcBwnqJN5x/Gien8qNOn0D5bQU/zAzVf9Zt3BlcUiLqhV9y4ARk0GbT3tnUiPNgnTXzc/Q==",
+      "license": "MIT"
+    },
+    "node_modules/@types/yauzl": {
+      "version": "2.10.3",
+      "resolved": "https://registry.npmjs.org/@types/yauzl/-/yauzl-2.10.3.tgz",
+      "integrity": "sha512-oJoftv0LSuaDZE3Le4DbKX+KS9G36NzOeSap90UIK0yMA/NhKJhqlSGtNDORNRaIbQfzjXDrQa0ytJ6mNRGz/Q==",
+      "license": "MIT",
+      "optional": true,
+      "dependencies": {
+        "@types/node": "*"
+      }
+    },
+    "node_modules/@typescript-eslint/eslint-plugin": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/eslint-plugin/-/eslint-plugin-8.53.1.tgz",
+      "integrity": "sha512-cFYYFZ+oQFi6hUnBTbLRXfTJiaQtYE3t4O692agbBl+2Zy+eqSKWtPjhPXJu1G7j4RLjKgeJPDdq3EqOwmX5Ag==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@eslint-community/regexpp": "^4.12.2",
+        "@typescript-eslint/scope-manager": "8.53.1",
+        "@typescript-eslint/type-utils": "8.53.1",
+        "@typescript-eslint/utils": "8.53.1",
+        "@typescript-eslint/visitor-keys": "8.53.1",
+        "ignore": "^7.0.5",
+        "natural-compare": "^1.4.0",
+        "ts-api-utils": "^2.4.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "@typescript-eslint/parser": "^8.53.1",
+        "eslint": "^8.57.0 || ^9.0.0",
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/eslint-plugin/node_modules/ignore": {
+      "version": "7.0.5",
+      "resolved": "https://registry.npmjs.org/ignore/-/ignore-7.0.5.tgz",
+      "integrity": "sha512-Hs59xBNfUIunMFgWAbGX5cq6893IbWg4KnrjbYwX3tx0ztorVgTDA6B2sxf8ejHJ4wz8BqGUMYlnzNBer5NvGg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 4"
+      }
+    },
+    "node_modules/@typescript-eslint/parser": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/parser/-/parser-8.53.1.tgz",
+      "integrity": "sha512-nm3cvFN9SqZGXjmw5bZ6cGmvJSyJPn0wU9gHAZZHDnZl2wF9PhHv78Xf06E0MaNk4zLVHL8hb2/c32XvyJOLQg==",
+      "dev": true,
+      "license": "MIT",
+      "peer": true,
+      "dependencies": {
+        "@typescript-eslint/scope-manager": "8.53.1",
+        "@typescript-eslint/types": "8.53.1",
+        "@typescript-eslint/typescript-estree": "8.53.1",
+        "@typescript-eslint/visitor-keys": "8.53.1",
+        "debug": "^4.4.3"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "eslint": "^8.57.0 || ^9.0.0",
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/project-service": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/project-service/-/project-service-8.53.1.tgz",
+      "integrity": "sha512-WYC4FB5Ra0xidsmlPb+1SsnaSKPmS3gsjIARwbEkHkoWloQmuzcfypljaJcR78uyLA1h8sHdWWPHSLDI+MtNog==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@typescript-eslint/tsconfig-utils": "^8.53.1",
+        "@typescript-eslint/types": "^8.53.1",
+        "debug": "^4.4.3"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/scope-manager": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/scope-manager/-/scope-manager-8.53.1.tgz",
+      "integrity": "sha512-Lu23yw1uJMFY8cUeq7JlrizAgeQvWugNQzJp8C3x8Eo5Jw5Q2ykMdiiTB9vBVOOUBysMzmRRmUfwFrZuI2C4SQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@typescript-eslint/types": "8.53.1",
+        "@typescript-eslint/visitor-keys": "8.53.1"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      }
+    },
+    "node_modules/@typescript-eslint/tsconfig-utils": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/tsconfig-utils/-/tsconfig-utils-8.53.1.tgz",
+      "integrity": "sha512-qfvLXS6F6b1y43pnf0pPbXJ+YoXIC7HKg0UGZ27uMIemKMKA6XH2DTxsEDdpdN29D+vHV07x/pnlPNVLhdhWiA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/type-utils": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/type-utils/-/type-utils-8.53.1.tgz",
+      "integrity": "sha512-MOrdtNvyhy0rHyv0ENzub1d4wQYKb2NmIqG7qEqPWFW7Mpy2jzFC3pQ2yKDvirZB7jypm5uGjF2Qqs6OIqu47w==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@typescript-eslint/types": "8.53.1",
+        "@typescript-eslint/typescript-estree": "8.53.1",
+        "@typescript-eslint/utils": "8.53.1",
+        "debug": "^4.4.3",
+        "ts-api-utils": "^2.4.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "eslint": "^8.57.0 || ^9.0.0",
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/types": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/types/-/types-8.53.1.tgz",
+      "integrity": "sha512-jr/swrr2aRmUAUjW5/zQHbMaui//vQlsZcJKijZf3M26bnmLj8LyZUpj8/Rd6uzaek06OWsqdofN/Thenm5O8A==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      }
+    },
+    "node_modules/@typescript-eslint/typescript-estree": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/typescript-estree/-/typescript-estree-8.53.1.tgz",
+      "integrity": "sha512-RGlVipGhQAG4GxV1s34O91cxQ/vWiHJTDHbXRr0li2q/BGg3RR/7NM8QDWgkEgrwQYCvmJV9ichIwyoKCQ+DTg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@typescript-eslint/project-service": "8.53.1",
+        "@typescript-eslint/tsconfig-utils": "8.53.1",
+        "@typescript-eslint/types": "8.53.1",
+        "@typescript-eslint/visitor-keys": "8.53.1",
+        "debug": "^4.4.3",
+        "minimatch": "^9.0.5",
+        "semver": "^7.7.3",
+        "tinyglobby": "^0.2.15",
+        "ts-api-utils": "^2.4.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansion": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-2.0.2.tgz",
+      "integrity": "sha512-Jt0vHyM+jmUBqojB7E1NIYadt0vI0Qxjxd2TErW94wDz+E2LAm5vKMXXwg6ZZBTHPuUlDgQHKXvjGBdfcF1ZDQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "balanced-match": "^1.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/typescript-estree/node_modules/minimatch": {
+      "version": "9.0.9",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-9.0.9.tgz",
+      "integrity": "sha512-OBwBN9AL4dqmETlpS2zasx+vTeWclWzkblfZk7KTA5j3jeOONz/tRCnZomUyvNg83wL5Zv9Ss6HMJXAgL8R2Yg==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "brace-expansion": "^2.0.2"
+      },
+      "engines": {
+        "node": ">=16 || 14 >=14.17"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
+      }
+    },
+    "node_modules/@typescript-eslint/utils": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/utils/-/utils-8.53.1.tgz",
+      "integrity": "sha512-c4bMvGVWW4hv6JmDUEG7fSYlWOl3II2I4ylt0NM+seinYQlZMQIaKaXIIVJWt9Ofh6whrpM+EdDQXKXjNovvrg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@eslint-community/eslint-utils": "^4.9.1",
+        "@typescript-eslint/scope-manager": "8.53.1",
+        "@typescript-eslint/types": "8.53.1",
+        "@typescript-eslint/typescript-estree": "8.53.1"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "eslint": "^8.57.0 || ^9.0.0",
+        "typescript": ">=4.8.4 <6.0.0"
+      }
+    },
+    "node_modules/@typescript-eslint/visitor-keys": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/@typescript-eslint/visitor-keys/-/visitor-keys-8.53.1.tgz",
+      "integrity": "sha512-oy+wV7xDKFPRyNggmXuZQSBzvoLnpmJs+GhzRhPjrxl2b/jIlyjVokzm47CZCDUdXKr2zd7ZLodPfOBpOPyPlg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@typescript-eslint/types": "8.53.1",
+        "eslint-visitor-keys": "^4.2.1"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      }
+    },
+    "node_modules/@ungap/structured-clone": {
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/@ungap/structured-clone/-/structured-clone-1.3.0.tgz",
+      "integrity": "sha512-WmoN8qaIAo7WTYWbAZuG8PYEhn5fkz7dZrqTBZ7dtt//lL2Gwms1IcnQ5yHqjDfX8Ft5j4YzDM23f87zBfDe9g==",
+      "license": "ISC"
+    },
+    "node_modules/@vitejs/plugin-react": {
+      "version": "5.2.0",
+      "resolved": "https://registry.npmjs.org/@vitejs/plugin-react/-/plugin-react-5.2.0.tgz",
+      "integrity": "sha512-YmKkfhOAi3wsB1PhJq5Scj3GXMn3WvtQ/JC0xoopuHoXSdmtdStOpFrYaT1kie2YgFBcIe64ROzMYRjCrYOdYw==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/core": "^7.29.0",
+        "@babel/plugin-transform-react-jsx-self": "^7.27.1",
+        "@babel/plugin-transform-react-jsx-source": "^7.27.1",
+        "@rolldown/pluginutils": "1.0.0-rc.3",
+        "@types/babel__core": "^7.20.5",
+        "react-refresh": "^0.18.0"
+      },
+      "engines": {
+        "node": "^20.19.0 || >=22.12.0"
+      },
+      "peerDependencies": {
+        "vite": "^4.2.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0"
+      }
+    },
+    "node_modules/acorn": {
+      "version": "8.16.0",
+      "resolved": "https://registry.npmjs.org/acorn/-/acorn-8.16.0.tgz",
+      "integrity": "sha512-UVJyE9MttOsBQIDKw1skb9nAwQuR5wuGD3+82K6JgJlm/Y+KI92oNsMNGZCYdDsVtRHSak0pcV5Dno5+4jh9sw==",
+      "license": "MIT",
+      "peer": true,
+      "bin": {
+        "acorn": "bin/acorn"
+      },
+      "engines": {
+        "node": ">=0.4.0"
+      }
+    },
+    "node_modules/acorn-jsx": {
+      "version": "5.3.2",
+      "resolved": "https://registry.npmjs.org/acorn-jsx/-/acorn-jsx-5.3.2.tgz",
+      "integrity": "sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==",
+      "license": "MIT",
+      "peerDependencies": {
+        "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
+      }
+    },
+    "node_modules/ajv": {
+      "version": "6.14.0",
+      "resolved": "https://registry.npmjs.org/ajv/-/ajv-6.14.0.tgz",
+      "integrity": "sha512-IWrosm/yrn43eiKqkfkHis7QioDleaXQHdDVPKg0FSwwd/DuvyX79TZnFOnYpB7dcsFAMmtFztZuXPDvSePkFw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "fast-deep-equal": "^3.1.1",
+        "fast-json-stable-stringify": "^2.0.0",
+        "json-schema-traverse": "^0.4.1",
+        "uri-js": "^4.2.2"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/epoberezkin"
+      }
+    },
+    "node_modules/ansi-escapes": {
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-7.2.0.tgz",
+      "integrity": "sha512-g6LhBsl+GBPRWGWsBtutpzBYuIIdBkLEvad5C/va/74Db018+5TZiyA26cZJAr3Rft5lprVqOIPxf5Vid6tqAw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "environment": "^1.0.0"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/ansi-regex": {
+      "version": "6.2.2",
+      "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-6.2.2.tgz",
+      "integrity": "sha512-Bq3SmSpyFHaWjPk8If9yc6svM8c56dB5BAtW4Qbw5jHTwwXXcTLoRMkpDJp6VL0XzlWaCHTXrkFURMYmD0sLqg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/ansi-regex?sponsor=1"
+      }
+    },
+    "node_modules/ansi-styles": {
+      "version": "6.2.3",
+      "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-6.2.3.tgz",
+      "integrity": "sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/ansi-styles?sponsor=1"
+      }
+    },
+    "node_modules/anymatch": {
+      "version": "3.1.3",
+      "resolved": "https://registry.npmjs.org/anymatch/-/anymatch-3.1.3.tgz",
+      "integrity": "sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==",
+      "license": "ISC",
+      "dependencies": {
+        "normalize-path": "^3.0.0",
+        "picomatch": "^2.0.4"
+      },
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/anymatch/node_modules/picomatch": {
+      "version": "2.3.1",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
+      "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=8.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/jonschlinkert"
+      }
+    },
+    "node_modules/arg": {
+      "version": "5.0.2",
+      "resolved": "https://registry.npmjs.org/arg/-/arg-5.0.2.tgz",
+      "integrity": "sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==",
+      "license": "MIT"
+    },
+    "node_modules/argparse": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/argparse/-/argparse-2.0.1.tgz",
+      "integrity": "sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==",
+      "license": "Python-2.0"
+    },
+    "node_modules/aria-query": {
+      "version": "5.3.2",
+      "resolved": "https://registry.npmjs.org/aria-query/-/aria-query-5.3.2.tgz",
+      "integrity": "sha512-COROpnaoap1E2F000S62r6A60uHZnmlvomhfyT2DlTcrY1OrBKn2UhH7qn5wTC9zMvD0AY7csdPSNwKP+7WiQw==",
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/array-buffer-byte-length": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/array-buffer-byte-length/-/array-buffer-byte-length-1.0.2.tgz",
+      "integrity": "sha512-LHE+8BuR7RYGDKvnrmcuSq3tDcKv9OFEXQt/HpbZhY7V6h0zlUXutnAD82GiFx9rdieCMjkvtcsPqBwgUl1Iiw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "is-array-buffer": "^3.0.5"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/array-includes": {
+      "version": "3.1.9",
+      "resolved": "https://registry.npmjs.org/array-includes/-/array-includes-3.1.9.tgz",
+      "integrity": "sha512-FmeCCAenzH0KH381SPT5FZmiA/TmpndpcaShhfgEN9eCVjnFBqq3l1xrI42y8+PPLI6hypzou4GXw00WHmPBLQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.4",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.24.0",
+        "es-object-atoms": "^1.1.1",
+        "get-intrinsic": "^1.3.0",
+        "is-string": "^1.1.1",
+        "math-intrinsics": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/array-iterate": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/array-iterate/-/array-iterate-2.0.1.tgz",
+      "integrity": "sha512-I1jXZMjAgCMmxT4qxXfPXa6SthSoE8h6gkSI9BGGNv8mP8G/v0blc+qFnZu6K42vTOiuME596QaLO0TP3Lk0xg==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/array.prototype.flat": {
+      "version": "1.3.3",
+      "resolved": "https://registry.npmjs.org/array.prototype.flat/-/array.prototype.flat-1.3.3.tgz",
+      "integrity": "sha512-rwG/ja1neyLqCuGZ5YYrznA62D4mZXg0i1cIskIUKSiqF3Cje9/wXAls9B9s1Wa2fomMsIv8czB8jZcPmxCXFg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.5",
+        "es-shim-unscopables": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/array.prototype.flatmap": {
+      "version": "1.3.3",
+      "resolved": "https://registry.npmjs.org/array.prototype.flatmap/-/array.prototype.flatmap-1.3.3.tgz",
+      "integrity": "sha512-Y7Wt51eKJSyi80hFrJCePGGNo5ktJCslFuboqJsbf57CCPcm5zztluPlc4/aD8sWsKvlwatezpV4U1efk8kpjg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.5",
+        "es-shim-unscopables": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/arraybuffer.prototype.slice": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/arraybuffer.prototype.slice/-/arraybuffer.prototype.slice-1.0.4.tgz",
+      "integrity": "sha512-BNoCY6SXXPQ7gF2opIP4GBE+Xw7U+pHMYKuzjgCN3GwiaIR09UUeKfheyIry77QtrCBlC0KK0q5/TER/tYh3PQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "array-buffer-byte-length": "^1.0.1",
+        "call-bind": "^1.0.8",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.5",
+        "es-errors": "^1.3.0",
+        "get-intrinsic": "^1.2.6",
+        "is-array-buffer": "^3.0.4"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/ast-types-flow": {
+      "version": "0.0.8",
+      "resolved": "https://registry.npmjs.org/ast-types-flow/-/ast-types-flow-0.0.8.tgz",
+      "integrity": "sha512-OH/2E5Fg20h2aPrbe+QL8JZQFko0YZaF+j4mnQ7BGhfavO7OpSLa8a0y9sBwomHdSbkhTS8TQNayBfnW5DwbvQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/astring": {
+      "version": "1.9.0",
+      "resolved": "https://registry.npmjs.org/astring/-/astring-1.9.0.tgz",
+      "integrity": "sha512-LElXdjswlqjWrPpJFg1Fx4wpkOCxj1TDHlSV4PlaRxHGWko024xICaa97ZkMfs6DRKlCguiAI+rbXv5GWwXIkg==",
+      "license": "MIT",
+      "bin": {
+        "astring": "bin/astring"
+      }
+    },
+    "node_modules/astro": {
+      "version": "6.1.2",
+      "resolved": "https://registry.npmjs.org/astro/-/astro-6.1.2.tgz",
+      "integrity": "sha512-r3iIvmB6JvQxsdJLvapybKKq7Bojd1iQK6CCx5P55eRnXJIyUpHx/1UB/GdMm+em/lwaCUasxHCmIO0lCLV2uA==",
+      "license": "MIT",
+      "peer": true,
+      "dependencies": {
+        "@astrojs/compiler": "^3.0.1",
+        "@astrojs/internal-helpers": "0.8.0",
+        "@astrojs/markdown-remark": "7.1.0",
+        "@astrojs/telemetry": "3.3.0",
+        "@capsizecss/unpack": "^4.0.0",
+        "@clack/prompts": "^1.1.0",
+        "@oslojs/encoding": "^1.1.0",
+        "@rollup/pluginutils": "^5.3.0",
+        "aria-query": "^5.3.2",
+        "axobject-query": "^4.1.0",
+        "ci-info": "^4.4.0",
+        "clsx": "^2.1.1",
+        "common-ancestor-path": "^2.0.0",
+        "cookie": "^1.1.1",
+        "devalue": "^5.6.3",
+        "diff": "^8.0.3",
+        "dlv": "^1.1.3",
+        "dset": "^3.1.4",
+        "es-module-lexer": "^2.0.0",
+        "esbuild": "^0.27.3",
+        "flattie": "^1.1.1",
+        "fontace": "~0.4.1",
+        "github-slugger": "^2.0.0",
+        "html-escaper": "3.0.3",
+        "http-cache-semantics": "^4.2.0",
+        "js-yaml": "^4.1.1",
+        "magic-string": "^0.30.21",
+        "magicast": "^0.5.2",
+        "mrmime": "^2.0.1",
+        "neotraverse": "^0.6.18",
+        "obug": "^2.1.1",
+        "p-limit": "^7.3.0",
+        "p-queue": "^9.1.0",
+        "package-manager-detector": "^1.6.0",
+        "piccolore": "^0.1.3",
+        "picomatch": "^4.0.3",
+        "rehype": "^13.0.2",
+        "semver": "^7.7.4",
+        "shiki": "^4.0.2",
+        "smol-toml": "^1.6.0",
+        "svgo": "^4.0.1",
+        "tinyclip": "^0.1.12",
+        "tinyexec": "^1.0.4",
+        "tinyglobby": "^0.2.15",
+        "tsconfck": "^3.1.6",
+        "ultrahtml": "^1.6.0",
+        "unifont": "~0.7.4",
+        "unist-util-visit": "^5.1.0",
+        "unstorage": "^1.17.4",
+        "vfile": "^6.0.3",
+        "vite": "^7.3.1",
+        "vitefu": "^1.1.2",
+        "xxhash-wasm": "^1.1.0",
+        "yargs-parser": "^22.0.0",
+        "zod": "^4.3.6"
+      },
+      "bin": {
+        "astro": "bin/astro.mjs"
+      },
+      "engines": {
+        "node": ">=22.12.0",
+        "npm": ">=9.6.5",
+        "pnpm": ">=7.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/astrodotbuild"
+      },
+      "optionalDependencies": {
+        "sharp": "^0.34.0"
+      }
+    },
+    "node_modules/astro-eslint-parser": {
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/astro-eslint-parser/-/astro-eslint-parser-1.2.2.tgz",
+      "integrity": "sha512-JepyLROIad6f44uyqMF6HKE2QbunNzp3mYKRcPoDGt0QkxXmH222FAFC64WTyQu2Kg8NNEXHTN/sWuUId9sSxw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@astrojs/compiler": "^2.0.0",
+        "@typescript-eslint/scope-manager": "^7.0.0 || ^8.0.0",
+        "@typescript-eslint/types": "^7.0.0 || ^8.0.0",
+        "astrojs-compiler-sync": "^1.0.0",
+        "debug": "^4.3.4",
+        "entities": "^6.0.0",
+        "eslint-scope": "^8.0.1",
+        "eslint-visitor-keys": "^4.0.0",
+        "espree": "^10.0.0",
+        "fast-glob": "^3.3.3",
+        "is-glob": "^4.0.3",
+        "semver": "^7.3.8"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ota-meshi"
+      }
+    },
+    "node_modules/astro-expressive-code": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/astro-expressive-code/-/astro-expressive-code-0.41.7.tgz",
+      "integrity": "sha512-hUpogGc6DdAd+I7pPXsctyYPRBJDK7Q7d06s4cyP0Vz3OcbziP3FNzN0jZci1BpCvLn9675DvS7B9ctKKX64JQ==",
+      "dependencies": {
+        "rehype-expressive-code": "^0.41.7"
+      },
+      "peerDependencies": {
+        "astro": "^4.0.0-beta || ^5.0.0-beta || ^3.3.0 || ^6.0.0-beta"
+      }
+    },
+    "node_modules/astro-icon": {
+      "version": "1.1.5",
+      "resolved": "https://registry.npmjs.org/astro-icon/-/astro-icon-1.1.5.tgz",
+      "integrity": "sha512-CJYS5nWOw9jz4RpGWmzNQY7D0y2ZZacH7atL2K9DeJXJVaz7/5WrxeyIxO8KASk1jCM96Q4LjRx/F3R+InjJrw==",
+      "license": "MIT",
+      "dependencies": {
+        "@iconify/tools": "^4.0.5",
+        "@iconify/types": "^2.0.0",
+        "@iconify/utils": "^2.1.30"
+      }
+    },
+    "node_modules/astro/node_modules/@astrojs/compiler": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/@astrojs/compiler/-/compiler-3.0.1.tgz",
+      "integrity": "sha512-z97oYbdebO5aoWzuJ/8q5hLK232+17KcLZ7cJ8BCWk6+qNzVxn/gftC0KzMBUTD8WAaBkPpNSQK6PXLnNrZ0CA==",
+      "license": "MIT"
+    },
+    "node_modules/astro/node_modules/@shikijs/core": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/core/-/core-4.0.2.tgz",
+      "integrity": "sha512-hxT0YF4ExEqB8G/qFdtJvpmHXBYJ2lWW7qTHDarVkIudPFE6iCIrqdgWxGn5s+ppkGXI0aEGlibI0PAyzP3zlw==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/primitive": "4.0.2",
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4",
+        "hast-util-to-html": "^9.0.5"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/@shikijs/engine-javascript": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-javascript/-/engine-javascript-4.0.2.tgz",
+      "integrity": "sha512-7PW0Nm49DcoUIQEXlJhNNBHyoGMjalRETTCcjMqEaMoJRLljy1Bi/EGV3/qLBgLKQejdspiiYuHGQW6dX94Nag==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "oniguruma-to-es": "^4.3.4"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/@shikijs/engine-oniguruma": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/engine-oniguruma/-/engine-oniguruma-4.0.2.tgz",
+      "integrity": "sha512-UpCB9Y2sUKlS9z8juFSKz7ZtysmeXCgnRF0dlhXBkmQnek7lAToPte8DkxmEYGNTMii72zU/lyXiCB6StuZeJg==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/@shikijs/langs": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/langs/-/langs-4.0.2.tgz",
+      "integrity": "sha512-KaXby5dvoeuZzN0rYQiPMjFoUrz4hgwIE+D6Du9owcHcl6/g16/yT5BQxSW5cGt2MZBz6Hl0YuRqf12omRfUUg==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/@shikijs/themes": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/themes/-/themes-4.0.2.tgz",
+      "integrity": "sha512-mjCafwt8lJJaVSsQvNVrJumbnnj1RI8jbUKrPKgE6E3OvQKxnuRoBaYC51H4IGHePsGN/QtALglWBU7DoKDFnA==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/types": "4.0.2"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/@shikijs/types": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/@shikijs/types/-/types-4.0.2.tgz",
+      "integrity": "sha512-qzbeRooUTPnLE+sHD/Z8DStmaDgnbbc/pMrU203950aRqjX/6AFHeDYT+j00y2lPdz0ywJKx7o/7qnqTivtlXg==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astro/node_modules/shiki": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/shiki/-/shiki-4.0.2.tgz",
+      "integrity": "sha512-eAVKTMedR5ckPo4xne/PjYQYrU3qx78gtJZ+sHlXEg5IHhhoQhMfZVzetTYuaJS0L2Ef3AcCRzCHV8T0WI6nIQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@shikijs/core": "4.0.2",
+        "@shikijs/engine-javascript": "4.0.2",
+        "@shikijs/engine-oniguruma": "4.0.2",
+        "@shikijs/langs": "4.0.2",
+        "@shikijs/themes": "4.0.2",
+        "@shikijs/types": "4.0.2",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/astrojs-compiler-sync": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/astrojs-compiler-sync/-/astrojs-compiler-sync-1.1.1.tgz",
+      "integrity": "sha512-0mKvB9sDQRIZPsEJadw6OaFbGJ92cJPPR++ICca9XEyiUAZqgVuk25jNmzHPT0KF80rI94trSZrUR5iHFXGGOQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "synckit": "^0.11.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || >=20.9.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ota-meshi"
+      },
+      "peerDependencies": {
+        "@astrojs/compiler": ">=0.27.0"
+      }
+    },
+    "node_modules/async-function": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/async-function/-/async-function-1.0.0.tgz",
+      "integrity": "sha512-hsU18Ae8CDTR6Kgu9DYf0EbCr/a5iGL0rytQDobUcdpYOKokk8LEjVphnXkDkgpi0wYVsqrXuP0bZxJaTqdgoA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/available-typed-arrays": {
+      "version": "1.0.7",
+      "resolved": "https://registry.npmjs.org/available-typed-arrays/-/available-typed-arrays-1.0.7.tgz",
+      "integrity": "sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "possible-typed-array-names": "^1.0.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/axe-core": {
+      "version": "4.11.1",
+      "resolved": "https://registry.npmjs.org/axe-core/-/axe-core-4.11.1.tgz",
+      "integrity": "sha512-BASOg+YwO2C+346x3LZOeoovTIoTrRqEsqMa6fmfAV0P+U9mFr9NsyOEpiYvFjbc64NMrSswhV50WdXzdb/Z5A==",
+      "dev": true,
+      "license": "MPL-2.0",
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/axobject-query": {
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/axobject-query/-/axobject-query-4.1.0.tgz",
+      "integrity": "sha512-qIj0G9wZbMGNLjLmg1PT6v2mE9AH2zlnADJD/2tC6E00hgmhUOfEB6greHPAfLRSufHqROIUTkw6E+M3lH0PTQ==",
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/bail": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/bail/-/bail-2.0.2.tgz",
+      "integrity": "sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/balanced-match": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/balanced-match/-/balanced-match-1.0.2.tgz",
+      "integrity": "sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/base64-js": {
+      "version": "0.0.8",
+      "resolved": "https://registry.npmjs.org/base64-js/-/base64-js-0.0.8.tgz",
+      "integrity": "sha512-3XSA2cR/h/73EzlXXdU6YNycmYI7+kicTxks4eJg2g39biHR84slg2+des+p7iHYhbRg/udIS4TD53WabcOUkw==",
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/baseline-browser-mapping": {
+      "version": "2.10.0",
+      "resolved": "https://registry.npmjs.org/baseline-browser-mapping/-/baseline-browser-mapping-2.10.0.tgz",
+      "integrity": "sha512-lIyg0szRfYbiy67j9KN8IyeD7q7hcmqnJ1ddWmNt19ItGpNN64mnllmxUNFIOdOm6by97jlL6wfpTTJrmnjWAA==",
+      "bin": {
+        "baseline-browser-mapping": "dist/cli.cjs"
+      },
+      "engines": {
+        "node": ">=6.0.0"
+      }
+    },
+    "node_modules/bcp-47-match": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/bcp-47-match/-/bcp-47-match-2.0.3.tgz",
+      "integrity": "sha512-JtTezzbAibu8G0R9op9zb3vcWZd9JF6M0xOYGPn0fNCd7wOpRB1mU2mH9T8gaBGbAAyIIVgB2G7xG0GP98zMAQ==",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/boolbase": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/boolbase/-/boolbase-1.0.0.tgz",
+      "integrity": "sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==",
+      "license": "ISC"
+    },
+    "node_modules/brace-expansion": {
+      "version": "1.1.12",
+      "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.12.tgz",
+      "integrity": "sha512-9T9UjW3r0UW5c1Q7GTwllptXwhvYmEzFhzMfZ9H7FQWt+uZePjZPjBP/W1ZEyZ1twGWom5/56TF4lPcqjnDHcg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "balanced-match": "^1.0.0",
+        "concat-map": "0.0.1"
+      }
+    },
+    "node_modules/braces": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/braces/-/braces-3.0.3.tgz",
+      "integrity": "sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "fill-range": "^7.1.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/browserslist": {
+      "version": "4.28.1",
+      "resolved": "https://registry.npmjs.org/browserslist/-/browserslist-4.28.1.tgz",
+      "integrity": "sha512-ZC5Bd0LgJXgwGqUknZY/vkUQ04r8NXnJZ3yYi4vDmSiZmC/pdSN0NbNRPxZpbtO4uAfDUAFffO8IZoM3Gj8IkA==",
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/browserslist"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "peer": true,
+      "dependencies": {
+        "baseline-browser-mapping": "^2.9.0",
+        "caniuse-lite": "^1.0.30001759",
+        "electron-to-chromium": "^1.5.263",
+        "node-releases": "^2.0.27",
+        "update-browserslist-db": "^1.2.0"
+      },
+      "bin": {
+        "browserslist": "cli.js"
+      },
+      "engines": {
+        "node": "^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7"
+      }
+    },
+    "node_modules/buffer-crc32": {
+      "version": "0.2.13",
+      "resolved": "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz",
+      "integrity": "sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==",
+      "license": "MIT",
+      "engines": {
+        "node": "*"
+      }
+    },
+    "node_modules/call-bind": {
+      "version": "1.0.8",
+      "resolved": "https://registry.npmjs.org/call-bind/-/call-bind-1.0.8.tgz",
+      "integrity": "sha512-oKlSFMcMwpUg2ednkhQ454wfWiU/ul3CkJe/PEHcTKuiX6RpbehUiFMXu13HalGZxfUwCQzZG747YXBn1im9ww==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind-apply-helpers": "^1.0.0",
+        "es-define-property": "^1.0.0",
+        "get-intrinsic": "^1.2.4",
+        "set-function-length": "^1.2.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/call-bind-apply-helpers": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/call-bind-apply-helpers/-/call-bind-apply-helpers-1.0.2.tgz",
+      "integrity": "sha512-Sp1ablJ0ivDkSzjcaJdxEunN5/XvksFJ2sMBFfq6x0ryhQV/2b/KwFe21cMpmHtPOSij8K99/wSfoEuTObmuMQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0",
+        "function-bind": "^1.1.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/call-bound": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/call-bound/-/call-bound-1.0.4.tgz",
+      "integrity": "sha512-+ys997U96po4Kx/ABpBCqhA9EuxJaQWDQg7295H4hBphv3IZg0boBKuwYpt4YXp6MZ5AmZQnU/tyMTlRpaSejg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind-apply-helpers": "^1.0.2",
+        "get-intrinsic": "^1.3.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/callsites": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz",
+      "integrity": "sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/camelize": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/camelize/-/camelize-1.0.1.tgz",
+      "integrity": "sha512-dU+Tx2fsypxTgtLoE36npi3UqcjSSMNYfkqgmoEhtZrraP5VWq0K7FkWVTYa8eMPtnU/G2txVsfdCJTn9uzpuQ==",
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/caniuse-lite": {
+      "version": "1.0.30001777",
+      "resolved": "https://registry.npmjs.org/caniuse-lite/-/caniuse-lite-1.0.30001777.tgz",
+      "integrity": "sha512-tmN+fJxroPndC74efCdp12j+0rk0RHwV5Jwa1zWaFVyw2ZxAuPeG8ZgWC3Wz7uSjT3qMRQ5XHZ4COgQmsCMJAQ==",
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/caniuse-lite"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ]
+    },
+    "node_modules/ccount": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/ccount/-/ccount-2.0.1.tgz",
+      "integrity": "sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/character-entities": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/character-entities/-/character-entities-2.0.2.tgz",
+      "integrity": "sha512-shx7oQ0Awen/BRIdkjkvz54PnEEI/EjwXDSIZp86/KKdbafHh1Df/RYGBhn4hbe2+uKC9FnT5UCEdyPz3ai9hQ==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/character-entities-html4": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/character-entities-html4/-/character-entities-html4-2.1.0.tgz",
+      "integrity": "sha512-1v7fgQRj6hnSwFpq1Eu0ynr/CDEw0rXo2B61qXrLNdHZmPKgb7fqS1a2JwF0rISo9q77jDI8VMEHoApn8qDoZA==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/character-entities-legacy": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/character-entities-legacy/-/character-entities-legacy-3.0.0.tgz",
+      "integrity": "sha512-RpPp0asT/6ufRm//AJVwpViZbGM/MkjQFxJccQRHmISF/22NBtsHqAWmL+/pmkPWoIUJdWyeVleTl1wydHATVQ==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/character-reference-invalid": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/character-reference-invalid/-/character-reference-invalid-2.0.1.tgz",
+      "integrity": "sha512-iBZ4F4wRbyORVsu0jPV7gXkOsGYjGHPmAyv+HiHG8gi5PtC9KI2j1+v8/tlibRvjoWX027ypmG/n0HtO5t7unw==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/cheerio": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/cheerio/-/cheerio-1.2.0.tgz",
+      "integrity": "sha512-WDrybc/gKFpTYQutKIK6UvfcuxijIZfMfXaYm8NMsPQxSYvf+13fXUJ4rztGGbJcBQ/GF55gvrZ0Bc0bj/mqvg==",
+      "license": "MIT",
+      "dependencies": {
+        "cheerio-select": "^2.1.0",
+        "dom-serializer": "^2.0.0",
+        "domhandler": "^5.0.3",
+        "domutils": "^3.2.2",
+        "encoding-sniffer": "^0.2.1",
+        "htmlparser2": "^10.1.0",
+        "parse5": "^7.3.0",
+        "parse5-htmlparser2-tree-adapter": "^7.1.0",
+        "parse5-parser-stream": "^7.1.2",
+        "undici": "^7.19.0",
+        "whatwg-mimetype": "^4.0.0"
+      },
+      "engines": {
+        "node": ">=20.18.1"
+      },
+      "funding": {
+        "url": "https://github.com/cheeriojs/cheerio?sponsor=1"
+      }
+    },
+    "node_modules/cheerio-select": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/cheerio-select/-/cheerio-select-2.1.0.tgz",
+      "integrity": "sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==",
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "boolbase": "^1.0.0",
+        "css-select": "^5.1.0",
+        "css-what": "^6.1.0",
+        "domelementtype": "^2.3.0",
+        "domhandler": "^5.0.3",
+        "domutils": "^3.0.1"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/fb55"
+      }
+    },
+    "node_modules/chokidar": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/chokidar/-/chokidar-5.0.0.tgz",
+      "integrity": "sha512-TQMmc3w+5AxjpL8iIiwebF73dRDF4fBIieAqGn9RGCWaEVwQ6Fb2cGe31Yns0RRIzii5goJ1Y7xbMwo1TxMplw==",
+      "license": "MIT",
+      "dependencies": {
+        "readdirp": "^5.0.0"
+      },
+      "engines": {
+        "node": ">= 20.19.0"
+      },
+      "funding": {
+        "url": "https://paulmillr.com/funding/"
+      }
+    },
+    "node_modules/chownr": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/chownr/-/chownr-3.0.0.tgz",
+      "integrity": "sha512-+IxzY9BZOQd/XuYPRmrvEVjF/nqj5kgT4kEq7VofrDoM1MxoRjEWkrCC3EtLi59TVawxTAn+orJwFQcrqEN1+g==",
+      "license": "BlueOak-1.0.0",
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/ci-info": {
+      "version": "4.4.0",
+      "resolved": "https://registry.npmjs.org/ci-info/-/ci-info-4.4.0.tgz",
+      "integrity": "sha512-77PSwercCZU2Fc4sX94eF8k8Pxte6JAwL4/ICZLFjJLqegs7kCuAsqqj/70NQF6TvDpgFjkubQB2FW2ZZddvQg==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/sibiraj-s"
+        }
+      ],
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/cli-cursor": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/cli-cursor/-/cli-cursor-5.0.0.tgz",
+      "integrity": "sha512-aCj4O5wKyszjMmDT4tZj93kxyydN/K5zPWSCe6/0AV/AA1pqe5ZBIw0a2ZfPQV7lL5/yb5HsUreJ6UFAF1tEQw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "restore-cursor": "^5.0.0"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/cli-truncate": {
+      "version": "5.1.1",
+      "resolved": "https://registry.npmjs.org/cli-truncate/-/cli-truncate-5.1.1.tgz",
+      "integrity": "sha512-SroPvNHxUnk+vIW/dOSfNqdy1sPEFkrTk6TUtqLCnBlo3N7TNYYkzzN7uSD6+jVjrdO4+p8nH7JzH6cIvUem6A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "slice-ansi": "^7.1.0",
+        "string-width": "^8.0.0"
+      },
+      "engines": {
+        "node": ">=20"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/cli-truncate/node_modules/string-width": {
+      "version": "8.1.0",
+      "resolved": "https://registry.npmjs.org/string-width/-/string-width-8.1.0.tgz",
+      "integrity": "sha512-Kxl3KJGb/gxkaUMOjRsQ8IrXiGW75O4E3RPjFIINOVH8AMl2SQ/yWdTzWwF3FevIX9LcMAjJW+GRwAlAbTSXdg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "get-east-asian-width": "^1.3.0",
+        "strip-ansi": "^7.1.0"
+      },
+      "engines": {
+        "node": ">=20"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/clsx": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/clsx/-/clsx-2.1.1.tgz",
+      "integrity": "sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/collapse-white-space": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/collapse-white-space/-/collapse-white-space-2.1.0.tgz",
+      "integrity": "sha512-loKTxY1zCOuG4j9f6EPnuyyYkf58RnhhWTvRoZEokgB+WbdXehfjFviyOVYkqzEWz1Q5kRiZdBYS5SwxbQYwzw==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/color-convert": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/color-convert/-/color-convert-2.0.1.tgz",
+      "integrity": "sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "color-name": "~1.1.4"
+      },
+      "engines": {
+        "node": ">=7.0.0"
+      }
+    },
+    "node_modules/color-name": {
+      "version": "1.1.4",
+      "resolved": "https://registry.npmjs.org/color-name/-/color-name-1.1.4.tgz",
+      "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==",
+      "license": "MIT"
+    },
+    "node_modules/colorette": {
+      "version": "2.0.20",
+      "resolved": "https://registry.npmjs.org/colorette/-/colorette-2.0.20.tgz",
+      "integrity": "sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/comma-separated-tokens": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/comma-separated-tokens/-/comma-separated-tokens-2.0.3.tgz",
+      "integrity": "sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/commander": {
+      "version": "11.1.0",
+      "resolved": "https://registry.npmjs.org/commander/-/commander-11.1.0.tgz",
+      "integrity": "sha512-yPVavfyCcRhmorC7rWlkHn15b4wDVgVmBA7kV4QVBsF7kv/9TKJAbAXVTxvTnwP8HHKjRCJDClKbciiYS7p0DQ==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=16"
+      }
+    },
+    "node_modules/common-ancestor-path": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/common-ancestor-path/-/common-ancestor-path-2.0.0.tgz",
+      "integrity": "sha512-dnN3ibLeoRf2HNC+OlCiNc5d2zxbLJXOtiZUudNFSXZrNSydxcCsSpRzXwfu7BBWCIfHPw+xTayeBvJCP/D8Ng==",
+      "license": "BlueOak-1.0.0",
+      "engines": {
+        "node": ">= 18"
+      }
+    },
+    "node_modules/concat-map": {
+      "version": "0.0.1",
+      "resolved": "https://registry.npmjs.org/concat-map/-/concat-map-0.0.1.tgz",
+      "integrity": "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/confbox": {
+      "version": "0.2.2",
+      "resolved": "https://registry.npmjs.org/confbox/-/confbox-0.2.2.tgz",
+      "integrity": "sha512-1NB+BKqhtNipMsov4xI/NnhCKp9XG9NamYp5PVm9klAT0fsrNPjaFICsCFhNhwZJKNh7zB/3q8qXz0E9oaMNtQ==",
+      "license": "MIT"
+    },
+    "node_modules/convert-source-map": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/convert-source-map/-/convert-source-map-2.0.0.tgz",
+      "integrity": "sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg=="
+    },
+    "node_modules/cookie": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/cookie/-/cookie-1.1.1.tgz",
+      "integrity": "sha512-ei8Aos7ja0weRpFzJnEA9UHJ/7XQmqglbRwnf2ATjcB9Wq874VKH9kfjjirM6UhU2/E5fFYadylyhFldcqSidQ==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/express"
+      }
+    },
+    "node_modules/cookie-es": {
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/cookie-es/-/cookie-es-1.2.2.tgz",
+      "integrity": "sha512-+W7VmiVINB+ywl1HGXJXmrqkOhpKrIiVZV6tQuV54ZyQC7MMuBt81Vc336GMLoHBq5hV/F9eXgt5Mnx0Rha5Fg==",
+      "license": "MIT"
+    },
+    "node_modules/cosmiconfig": {
+      "version": "8.3.6",
+      "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-8.3.6.tgz",
+      "integrity": "sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA==",
+      "dev": true,
+      "dependencies": {
+        "import-fresh": "^3.3.0",
+        "js-yaml": "^4.1.0",
+        "parse-json": "^5.2.0",
+        "path-type": "^4.0.0"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/d-fischer"
+      },
+      "peerDependencies": {
+        "typescript": ">=4.9.5"
+      },
+      "peerDependenciesMeta": {
+        "typescript": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/cross-spawn": {
+      "version": "7.0.6",
+      "resolved": "https://registry.npmjs.org/cross-spawn/-/cross-spawn-7.0.6.tgz",
+      "integrity": "sha512-uV2QOWP2nWzsy2aMp8aRibhi9dlzF5Hgh5SHaB9OiTGEyDTiJJyx0uy51QXdyWbtAHNua4XJzUKca3OzKUd3vA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "path-key": "^3.1.0",
+        "shebang-command": "^2.0.0",
+        "which": "^2.0.1"
+      },
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/crossws": {
+      "version": "0.3.5",
+      "resolved": "https://registry.npmjs.org/crossws/-/crossws-0.3.5.tgz",
+      "integrity": "sha512-ojKiDvcmByhwa8YYqbQI/hg7MEU0NC03+pSdEq4ZUnZR9xXpwk7E43SMNGkn+JxJGPFtNvQ48+vV2p+P1ml5PA==",
+      "license": "MIT",
+      "dependencies": {
+        "uncrypto": "^0.1.3"
+      }
+    },
+    "node_modules/css-background-parser": {
+      "version": "0.1.0",
+      "resolved": "https://registry.npmjs.org/css-background-parser/-/css-background-parser-0.1.0.tgz",
+      "integrity": "sha512-2EZLisiZQ+7m4wwur/qiYJRniHX4K5Tc9w93MT3AS0WS1u5kaZ4FKXlOTBhOjc+CgEgPiGY+fX1yWD8UwpEqUA==",
+      "license": "MIT"
+    },
+    "node_modules/css-box-shadow": {
+      "version": "1.0.0-3",
+      "resolved": "https://registry.npmjs.org/css-box-shadow/-/css-box-shadow-1.0.0-3.tgz",
+      "integrity": "sha512-9jaqR6e7Ohds+aWwmhe6wILJ99xYQbfmK9QQB9CcMjDbTxPZjwEmUQpU91OG05Xgm8BahT5fW+svbsQGjS/zPg==",
+      "license": "MIT"
+    },
+    "node_modules/css-color-keywords": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/css-color-keywords/-/css-color-keywords-1.0.0.tgz",
+      "integrity": "sha512-FyyrDHZKEjXDpNJYvVsV960FiqQyXc/LlYmsxl2BcdMb2WPx0OGRVgTg55rPSyLSNMqP52R9r8geSp7apN3Ofg==",
+      "license": "ISC",
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/css-gradient-parser": {
+      "version": "0.0.17",
+      "resolved": "https://registry.npmjs.org/css-gradient-parser/-/css-gradient-parser-0.0.17.tgz",
+      "integrity": "sha512-w2Xy9UMMwlKtou0vlRnXvWglPAceXCTtcmVSo8ZBUvqCV5aXEFP/PC6d+I464810I9FT++UACwTD5511bmGPUg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=16"
+      }
+    },
+    "node_modules/css-select": {
+      "version": "5.2.2",
+      "resolved": "https://registry.npmjs.org/css-select/-/css-select-5.2.2.tgz",
+      "integrity": "sha512-TizTzUddG/xYLA3NXodFM0fSbNizXjOKhqiQQwvhlspadZokn1KDy0NZFS0wuEubIYAV5/c1/lAr0TaaFXEXzw==",
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "boolbase": "^1.0.0",
+        "css-what": "^6.1.0",
+        "domhandler": "^5.0.2",
+        "domutils": "^3.0.1",
+        "nth-check": "^2.0.1"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/fb55"
+      }
+    },
+    "node_modules/css-selector-parser": {
+      "version": "3.3.0",
+      "resolved": "https://registry.npmjs.org/css-selector-parser/-/css-selector-parser-3.3.0.tgz",
+      "integrity": "sha512-Y2asgMGFqJKF4fq4xHDSlFYIkeVfRsm69lQC1q9kbEsH5XtnINTMrweLkjYMeaUgiXBy/uvKeO/a1JHTNnmB2g==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/mdevils"
+        },
+        {
+          "type": "patreon",
+          "url": "https://patreon.com/mdevils"
+        }
+      ]
+    },
+    "node_modules/css-to-react-native": {
+      "version": "3.2.0",
+      "resolved": "https://registry.npmjs.org/css-to-react-native/-/css-to-react-native-3.2.0.tgz",
+      "integrity": "sha512-e8RKaLXMOFii+02mOlqwjbD00KSEKqblnpO9e++1aXS1fPQOpS1YoqdVHBqPjHNoxeF2mimzVqawm2KCbEdtHQ==",
+      "license": "MIT",
+      "dependencies": {
+        "camelize": "^1.0.0",
+        "css-color-keywords": "^1.0.0",
+        "postcss-value-parser": "^4.0.2"
+      }
+    },
+    "node_modules/css-tree": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/css-tree/-/css-tree-3.1.0.tgz",
+      "integrity": "sha512-0eW44TGN5SQXU1mWSkKwFstI/22X2bG1nYzZTYMAWjylYURhse752YgbE4Cx46AC+bAvI+/dYTPRk1LqSUnu6w==",
+      "license": "MIT",
+      "dependencies": {
+        "mdn-data": "2.12.2",
+        "source-map-js": "^1.0.1"
+      },
+      "engines": {
+        "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0"
+      }
+    },
+    "node_modules/css-what": {
+      "version": "6.2.2",
+      "resolved": "https://registry.npmjs.org/css-what/-/css-what-6.2.2.tgz",
+      "integrity": "sha512-u/O3vwbptzhMs3L1fQE82ZSLHQQfto5gyZzwteVIEyeaY5Fc7R4dapF/BvRoSYFeqfBk4m0V1Vafq5Pjv25wvA==",
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">= 6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/fb55"
+      }
+    },
+    "node_modules/cssesc": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/cssesc/-/cssesc-3.0.0.tgz",
+      "integrity": "sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==",
+      "license": "MIT",
+      "bin": {
+        "cssesc": "bin/cssesc"
+      },
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/csso": {
+      "version": "5.0.5",
+      "resolved": "https://registry.npmjs.org/csso/-/csso-5.0.5.tgz",
+      "integrity": "sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==",
+      "license": "MIT",
+      "dependencies": {
+        "css-tree": "~2.2.0"
+      },
+      "engines": {
+        "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0",
+        "npm": ">=7.0.0"
+      }
+    },
+    "node_modules/csso/node_modules/css-tree": {
+      "version": "2.2.1",
+      "resolved": "https://registry.npmjs.org/css-tree/-/css-tree-2.2.1.tgz",
+      "integrity": "sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==",
+      "license": "MIT",
+      "dependencies": {
+        "mdn-data": "2.0.28",
+        "source-map-js": "^1.0.1"
+      },
+      "engines": {
+        "node": "^10 || ^12.20.0 || ^14.13.0 || >=15.0.0",
+        "npm": ">=7.0.0"
+      }
+    },
+    "node_modules/csso/node_modules/mdn-data": {
+      "version": "2.0.28",
+      "resolved": "https://registry.npmjs.org/mdn-data/-/mdn-data-2.0.28.tgz",
+      "integrity": "sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==",
+      "license": "CC0-1.0"
+    },
+    "node_modules/csstype": {
+      "version": "3.2.3",
+      "resolved": "https://registry.npmjs.org/csstype/-/csstype-3.2.3.tgz",
+      "integrity": "sha512-z1HGKcYy2xA8AGQfwrn0PAy+PB7X/GSj3UVJW9qKyn43xWa+gl5nXmU4qqLMRzWVLFC8KusUX8T/0kCiOYpAIQ=="
+    },
+    "node_modules/damerau-levenshtein": {
+      "version": "1.0.8",
+      "resolved": "https://registry.npmjs.org/damerau-levenshtein/-/damerau-levenshtein-1.0.8.tgz",
+      "integrity": "sha512-sdQSFB7+llfUcQHUQO3+B8ERRj0Oa4w9POWMI/puGtuf7gFywGmkaLCElnudfTiKZV+NvHqL0ifzdrI8Ro7ESA==",
+      "dev": true,
+      "license": "BSD-2-Clause"
+    },
+    "node_modules/data-view-buffer": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/data-view-buffer/-/data-view-buffer-1.0.2.tgz",
+      "integrity": "sha512-EmKO5V3OLXh1rtK2wgXRansaK1/mtVdTUEiEI0W8RkvgT05kfxaH29PliLnpLP73yYO6142Q72QNa8Wx/A5CqQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "es-errors": "^1.3.0",
+        "is-data-view": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/data-view-byte-length": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/data-view-byte-length/-/data-view-byte-length-1.0.2.tgz",
+      "integrity": "sha512-tuhGbE6CfTM9+5ANGf+oQb72Ky/0+s3xKUpHvShfiz2RxMFgFPjsXuRLBVMtvMs15awe45SRb83D6wH4ew6wlQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "es-errors": "^1.3.0",
+        "is-data-view": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/inspect-js"
+      }
+    },
+    "node_modules/data-view-byte-offset": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/data-view-byte-offset/-/data-view-byte-offset-1.0.1.tgz",
+      "integrity": "sha512-BS8PfmtDGnrgYdOonGZQdLZslWIeCGFP9tpan0hi1Co2Zr2NKADsvGYA8XxuG/4UWgJ6Cjtv+YJnB6MM69QGlQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.2",
+        "es-errors": "^1.3.0",
+        "is-data-view": "^1.0.1"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/debug": {
+      "version": "4.4.3",
+      "resolved": "https://registry.npmjs.org/debug/-/debug-4.4.3.tgz",
+      "integrity": "sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==",
+      "license": "MIT",
+      "dependencies": {
+        "ms": "^2.1.3"
+      },
+      "engines": {
+        "node": ">=6.0"
+      },
+      "peerDependenciesMeta": {
+        "supports-color": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/decode-named-character-reference": {
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/decode-named-character-reference/-/decode-named-character-reference-1.3.0.tgz",
+      "integrity": "sha512-GtpQYB283KrPp6nRw50q3U9/VfOutZOe103qlN7BPP6Ad27xYnOIWv4lPzo8HCAL+mMZofJ9KEy30fq6MfaK6Q==",
+      "license": "MIT",
+      "dependencies": {
+        "character-entities": "^2.0.0"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/deep-is": {
+      "version": "0.1.4",
+      "resolved": "https://registry.npmjs.org/deep-is/-/deep-is-0.1.4.tgz",
+      "integrity": "sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/define-data-property": {
+      "version": "1.1.4",
+      "resolved": "https://registry.npmjs.org/define-data-property/-/define-data-property-1.1.4.tgz",
+      "integrity": "sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-define-property": "^1.0.0",
+        "es-errors": "^1.3.0",
+        "gopd": "^1.0.1"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/define-properties": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/define-properties/-/define-properties-1.2.1.tgz",
+      "integrity": "sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "define-data-property": "^1.0.1",
+        "has-property-descriptors": "^1.0.0",
+        "object-keys": "^1.1.1"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/defu": {
+      "version": "6.1.4",
+      "resolved": "https://registry.npmjs.org/defu/-/defu-6.1.4.tgz",
+      "integrity": "sha512-mEQCMmwJu317oSz8CwdIOdwf3xMif1ttiM8LTufzc3g6kR+9Pe236twL8j3IYT1F7GfRgGcW6MWxzZjLIkuHIg==",
+      "license": "MIT"
+    },
+    "node_modules/dequal": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/dequal/-/dequal-2.0.3.tgz",
+      "integrity": "sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/destr": {
+      "version": "2.0.5",
+      "resolved": "https://registry.npmjs.org/destr/-/destr-2.0.5.tgz",
+      "integrity": "sha512-ugFTXCtDZunbzasqBxrK93Ik/DRYsO6S/fedkWEMKqt04xZ4csmnmwGDBAb07QWNaGMAmnTIemsYZCksjATwsA==",
+      "license": "MIT"
+    },
+    "node_modules/detect-libc": {
+      "version": "2.1.2",
+      "resolved": "https://registry.npmjs.org/detect-libc/-/detect-libc-2.1.2.tgz",
+      "integrity": "sha512-Btj2BOOO83o3WyH59e8MgXsxEQVcarkUOpEYrubB0urwnN10yQ364rsiByU11nZlqWYZm05i/of7io4mzihBtQ==",
+      "license": "Apache-2.0",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/devalue": {
+      "version": "5.6.4",
+      "resolved": "https://registry.npmjs.org/devalue/-/devalue-5.6.4.tgz",
+      "integrity": "sha512-Gp6rDldRsFh/7XuouDbxMH3Mx8GMCcgzIb1pDTvNyn8pZGQ22u+Wa+lGV9dQCltFQ7uVw0MhRyb8XDskNFOReA==",
+      "license": "MIT"
+    },
+    "node_modules/devlop": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/devlop/-/devlop-1.1.0.tgz",
+      "integrity": "sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==",
+      "license": "MIT",
+      "dependencies": {
+        "dequal": "^2.0.0"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/diff": {
+      "version": "8.0.3",
+      "resolved": "https://registry.npmjs.org/diff/-/diff-8.0.3.tgz",
+      "integrity": "sha512-qejHi7bcSD4hQAZE0tNAawRK1ZtafHDmMTMkrrIGgSLl7hTnQHmKCeB45xAcbfTqK2zowkM3j3bHt/4b/ARbYQ==",
+      "license": "BSD-3-Clause",
+      "engines": {
+        "node": ">=0.3.1"
+      }
+    },
+    "node_modules/direction": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/direction/-/direction-2.0.1.tgz",
+      "integrity": "sha512-9S6m9Sukh1cZNknO1CWAr2QAWsbKLafQiyM5gZ7VgXHeuaoUwffKN4q6NC4A/Mf9iiPlOXQEKW/Mv/mh9/3YFA==",
+      "bin": {
+        "direction": "cli.js"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/dlv": {
+      "version": "1.1.3",
+      "resolved": "https://registry.npmjs.org/dlv/-/dlv-1.1.3.tgz",
+      "integrity": "sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==",
+      "license": "MIT"
+    },
+    "node_modules/dom-serializer": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-2.0.0.tgz",
+      "integrity": "sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==",
+      "license": "MIT",
+      "dependencies": {
+        "domelementtype": "^2.3.0",
+        "domhandler": "^5.0.2",
+        "entities": "^4.2.0"
+      },
+      "funding": {
+        "url": "https://github.com/cheeriojs/dom-serializer?sponsor=1"
+      }
+    },
+    "node_modules/dom-serializer/node_modules/entities": {
+      "version": "4.5.0",
+      "resolved": "https://registry.npmjs.org/entities/-/entities-4.5.0.tgz",
+      "integrity": "sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==",
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">=0.12"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/entities?sponsor=1"
+      }
+    },
+    "node_modules/domelementtype": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.3.0.tgz",
+      "integrity": "sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/fb55"
+        }
+      ],
+      "license": "BSD-2-Clause"
+    },
+    "node_modules/domhandler": {
+      "version": "5.0.3",
+      "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-5.0.3.tgz",
+      "integrity": "sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==",
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "domelementtype": "^2.3.0"
+      },
+      "engines": {
+        "node": ">= 4"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/domhandler?sponsor=1"
+      }
+    },
+    "node_modules/domutils": {
+      "version": "3.2.2",
+      "resolved": "https://registry.npmjs.org/domutils/-/domutils-3.2.2.tgz",
+      "integrity": "sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==",
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "dom-serializer": "^2.0.0",
+        "domelementtype": "^2.3.0",
+        "domhandler": "^5.0.3"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/domutils?sponsor=1"
+      }
+    },
+    "node_modules/dot-case": {
+      "version": "3.0.4",
+      "resolved": "https://registry.npmjs.org/dot-case/-/dot-case-3.0.4.tgz",
+      "integrity": "sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==",
+      "dev": true,
+      "dependencies": {
+        "no-case": "^3.0.4",
+        "tslib": "^2.0.3"
+      }
+    },
+    "node_modules/dset": {
+      "version": "3.1.4",
+      "resolved": "https://registry.npmjs.org/dset/-/dset-3.1.4.tgz",
+      "integrity": "sha512-2QF/g9/zTaPDc3BjNcVTGoBbXBgYfMTTceLaYcFJ/W9kggFUkhxD/hMEeuLKbugyef9SqAx8cpgwlIP/jinUTA==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/dunder-proto": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/dunder-proto/-/dunder-proto-1.0.1.tgz",
+      "integrity": "sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind-apply-helpers": "^1.0.1",
+        "es-errors": "^1.3.0",
+        "gopd": "^1.2.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/electron-to-chromium": {
+      "version": "1.5.307",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.307.tgz",
+      "integrity": "sha512-5z3uFKBWjiNR44nFcYdkcXjKMbg5KXNdciu7mhTPo9tB7NbqSNP2sSnGR+fqknZSCwKkBN+oxiiajWs4dT6ORg=="
+    },
+    "node_modules/emoji-regex": {
+      "version": "10.6.0",
+      "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-10.6.0.tgz",
+      "integrity": "sha512-toUI84YS5YmxW219erniWD0CIVOo46xGKColeNQRgOzDorgBi1v4D71/OFzgD9GO2UGKIv1C3Sp8DAn0+j5w7A==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/emoji-regex-xs": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/emoji-regex-xs/-/emoji-regex-xs-2.0.1.tgz",
+      "integrity": "sha512-1QFuh8l7LqUcKe24LsPUNzjrzJQ7pgRwp1QMcZ5MX6mFplk2zQ08NVCM84++1cveaUUYtcCYHmeFEuNg16sU4g==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=10.0.0"
+      }
+    },
+    "node_modules/encoding-sniffer": {
+      "version": "0.2.1",
+      "resolved": "https://registry.npmjs.org/encoding-sniffer/-/encoding-sniffer-0.2.1.tgz",
+      "integrity": "sha512-5gvq20T6vfpekVtqrYQsSCFZ1wEg5+wW0/QaZMWkFr6BqD3NfKs0rLCx4rrVlSWJeZb5NBJgVLswK/w2MWU+Gw==",
+      "license": "MIT",
+      "dependencies": {
+        "iconv-lite": "^0.6.3",
+        "whatwg-encoding": "^3.1.1"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/encoding-sniffer?sponsor=1"
+      }
+    },
+    "node_modules/end-of-stream": {
+      "version": "1.4.5",
+      "resolved": "https://registry.npmjs.org/end-of-stream/-/end-of-stream-1.4.5.tgz",
+      "integrity": "sha512-ooEGc6HP26xXq/N+GCGOT0JKCLDGrq2bQUZrQ7gyrJiZANJ/8YDTxTpQBXGMn+WbIQXNVpyWymm7KYVICQnyOg==",
+      "license": "MIT",
+      "dependencies": {
+        "once": "^1.4.0"
+      }
+    },
+    "node_modules/entities": {
+      "version": "6.0.1",
+      "resolved": "https://registry.npmjs.org/entities/-/entities-6.0.1.tgz",
+      "integrity": "sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==",
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">=0.12"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/entities?sponsor=1"
+      }
+    },
+    "node_modules/environment": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/environment/-/environment-1.1.0.tgz",
+      "integrity": "sha512-xUtoPkMggbz0MPyPiIWr1Kp4aeWJjDZ6SMvURhimjdZgsRuDplF5/s9hcgGhyXMhs+6vpnuoiZ2kFiu3FMnS8Q==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/error-ex": {
+      "version": "1.3.4",
+      "resolved": "https://registry.npmjs.org/error-ex/-/error-ex-1.3.4.tgz",
+      "integrity": "sha512-sqQamAnR14VgCr1A618A3sGrygcpK+HEbenA/HiEAkkUwcZIIB/tgWqHFxWgOyDh4nB4JCRimh79dR5Ywc9MDQ==",
+      "dev": true,
+      "dependencies": {
+        "is-arrayish": "^0.2.1"
+      }
+    },
+    "node_modules/es-abstract": {
+      "version": "1.24.1",
+      "resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.24.1.tgz",
+      "integrity": "sha512-zHXBLhP+QehSSbsS9Pt23Gg964240DPd6QCf8WpkqEXxQ7fhdZzYsocOr5u7apWonsS5EjZDmTF+/slGMyasvw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "array-buffer-byte-length": "^1.0.2",
+        "arraybuffer.prototype.slice": "^1.0.4",
+        "available-typed-arrays": "^1.0.7",
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.4",
+        "data-view-buffer": "^1.0.2",
+        "data-view-byte-length": "^1.0.2",
+        "data-view-byte-offset": "^1.0.1",
+        "es-define-property": "^1.0.1",
+        "es-errors": "^1.3.0",
+        "es-object-atoms": "^1.1.1",
+        "es-set-tostringtag": "^2.1.0",
+        "es-to-primitive": "^1.3.0",
+        "function.prototype.name": "^1.1.8",
+        "get-intrinsic": "^1.3.0",
+        "get-proto": "^1.0.1",
+        "get-symbol-description": "^1.1.0",
+        "globalthis": "^1.0.4",
+        "gopd": "^1.2.0",
+        "has-property-descriptors": "^1.0.2",
+        "has-proto": "^1.2.0",
+        "has-symbols": "^1.1.0",
+        "hasown": "^2.0.2",
+        "internal-slot": "^1.1.0",
+        "is-array-buffer": "^3.0.5",
+        "is-callable": "^1.2.7",
+        "is-data-view": "^1.0.2",
+        "is-negative-zero": "^2.0.3",
+        "is-regex": "^1.2.1",
+        "is-set": "^2.0.3",
+        "is-shared-array-buffer": "^1.0.4",
+        "is-string": "^1.1.1",
+        "is-typed-array": "^1.1.15",
+        "is-weakref": "^1.1.1",
+        "math-intrinsics": "^1.1.0",
+        "object-inspect": "^1.13.4",
+        "object-keys": "^1.1.1",
+        "object.assign": "^4.1.7",
+        "own-keys": "^1.0.1",
+        "regexp.prototype.flags": "^1.5.4",
+        "safe-array-concat": "^1.1.3",
+        "safe-push-apply": "^1.0.0",
+        "safe-regex-test": "^1.1.0",
+        "set-proto": "^1.0.0",
+        "stop-iteration-iterator": "^1.1.0",
+        "string.prototype.trim": "^1.2.10",
+        "string.prototype.trimend": "^1.0.9",
+        "string.prototype.trimstart": "^1.0.8",
+        "typed-array-buffer": "^1.0.3",
+        "typed-array-byte-length": "^1.0.3",
+        "typed-array-byte-offset": "^1.0.4",
+        "typed-array-length": "^1.0.7",
+        "unbox-primitive": "^1.1.0",
+        "which-typed-array": "^1.1.19"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/es-define-property": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/es-define-property/-/es-define-property-1.0.1.tgz",
+      "integrity": "sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/es-errors": {
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz",
+      "integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/es-module-lexer": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/es-module-lexer/-/es-module-lexer-2.0.0.tgz",
+      "integrity": "sha512-5POEcUuZybH7IdmGsD8wlf0AI55wMecM9rVBTI/qEAy2c1kTOm3DjFYjrBdI2K3BaJjJYfYFeRtM0t9ssnRuxw==",
+      "license": "MIT"
+    },
+    "node_modules/es-object-atoms": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/es-object-atoms/-/es-object-atoms-1.1.1.tgz",
+      "integrity": "sha512-FGgH2h8zKNim9ljj7dankFPcICIK9Cp5bm+c2gQSYePhpaG5+esrLODihIorn+Pe6FGJzWhXQotPv73jTaldXA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/es-set-tostringtag": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/es-set-tostringtag/-/es-set-tostringtag-2.1.0.tgz",
+      "integrity": "sha512-j6vWzfrGVfyXxge+O0x5sh6cvxAog0a/4Rdd2K36zCMV5eJ+/+tOAngRO8cODMNWbVRdVlmGZQL2YS3yR8bIUA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0",
+        "get-intrinsic": "^1.2.6",
+        "has-tostringtag": "^1.0.2",
+        "hasown": "^2.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/es-shim-unscopables": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/es-shim-unscopables/-/es-shim-unscopables-1.1.0.tgz",
+      "integrity": "sha512-d9T8ucsEhh8Bi1woXCf+TIKDIROLG5WCkxg8geBCbvk22kzwC5G2OnXVMO6FUsvQlgUUXQ2itephWDLqDzbeCw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "hasown": "^2.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/es-to-primitive": {
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/es-to-primitive/-/es-to-primitive-1.3.0.tgz",
+      "integrity": "sha512-w+5mJ3GuFL+NjVtJlvydShqE1eN3h3PbI7/5LAsYJP/2qtuMXjfL2LpHSRqo4b4eSF5K/DH1JXKUAHSB2UW50g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "is-callable": "^1.2.7",
+        "is-date-object": "^1.0.5",
+        "is-symbol": "^1.0.4"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/esast-util-from-estree": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/esast-util-from-estree/-/esast-util-from-estree-2.0.0.tgz",
+      "integrity": "sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-visit": "^2.0.0",
+        "unist-util-position-from-estree": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/esast-util-from-js": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/esast-util-from-js/-/esast-util-from-js-2.0.1.tgz",
+      "integrity": "sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "acorn": "^8.0.0",
+        "esast-util-from-estree": "^2.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/esbuild": {
+      "version": "0.27.4",
+      "resolved": "https://registry.npmjs.org/esbuild/-/esbuild-0.27.4.tgz",
+      "integrity": "sha512-Rq4vbHnYkK5fws5NF7MYTU68FPRE1ajX7heQ/8QXXWqNgqqJ/GkmmyxIzUnf2Sr/bakf8l54716CcMGHYhMrrQ==",
+      "hasInstallScript": true,
+      "license": "MIT",
+      "bin": {
+        "esbuild": "bin/esbuild"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "optionalDependencies": {
+        "@esbuild/aix-ppc64": "0.27.4",
+        "@esbuild/android-arm": "0.27.4",
+        "@esbuild/android-arm64": "0.27.4",
+        "@esbuild/android-x64": "0.27.4",
+        "@esbuild/darwin-arm64": "0.27.4",
+        "@esbuild/darwin-x64": "0.27.4",
+        "@esbuild/freebsd-arm64": "0.27.4",
+        "@esbuild/freebsd-x64": "0.27.4",
+        "@esbuild/linux-arm": "0.27.4",
+        "@esbuild/linux-arm64": "0.27.4",
+        "@esbuild/linux-ia32": "0.27.4",
+        "@esbuild/linux-loong64": "0.27.4",
+        "@esbuild/linux-mips64el": "0.27.4",
+        "@esbuild/linux-ppc64": "0.27.4",
+        "@esbuild/linux-riscv64": "0.27.4",
+        "@esbuild/linux-s390x": "0.27.4",
+        "@esbuild/linux-x64": "0.27.4",
+        "@esbuild/netbsd-arm64": "0.27.4",
+        "@esbuild/netbsd-x64": "0.27.4",
+        "@esbuild/openbsd-arm64": "0.27.4",
+        "@esbuild/openbsd-x64": "0.27.4",
+        "@esbuild/openharmony-arm64": "0.27.4",
+        "@esbuild/sunos-x64": "0.27.4",
+        "@esbuild/win32-arm64": "0.27.4",
+        "@esbuild/win32-ia32": "0.27.4",
+        "@esbuild/win32-x64": "0.27.4"
+      }
+    },
+    "node_modules/escalade": {
+      "version": "3.2.0",
+      "resolved": "https://registry.npmjs.org/escalade/-/escalade-3.2.0.tgz",
+      "integrity": "sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==",
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/escape-html": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/escape-html/-/escape-html-1.0.3.tgz",
+      "integrity": "sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==",
+      "license": "MIT"
+    },
+    "node_modules/escape-string-regexp": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-5.0.0.tgz",
+      "integrity": "sha512-/veY75JbMK4j1yjvuUxuVsiS/hr/4iHs9FTT6cgTexxdE0Ly/glccBAkloH/DofkjRbZU3bnoj38mOmhkZ0lHw==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/eslint": {
+      "version": "9.39.2",
+      "resolved": "https://registry.npmjs.org/eslint/-/eslint-9.39.2.tgz",
+      "integrity": "sha512-LEyamqS7W5HB3ujJyvi0HQK/dtVINZvd5mAAp9eT5S/ujByGjiZLCzPcHVzuXbpJDJF/cxwHlfceVUDZ2lnSTw==",
+      "dev": true,
+      "license": "MIT",
+      "peer": true,
+      "dependencies": {
+        "@eslint-community/eslint-utils": "^4.8.0",
+        "@eslint-community/regexpp": "^4.12.1",
+        "@eslint/config-array": "^0.21.1",
+        "@eslint/config-helpers": "^0.4.2",
+        "@eslint/core": "^0.17.0",
+        "@eslint/eslintrc": "^3.3.1",
+        "@eslint/js": "9.39.2",
+        "@eslint/plugin-kit": "^0.4.1",
+        "@humanfs/node": "^0.16.6",
+        "@humanwhocodes/module-importer": "^1.0.1",
+        "@humanwhocodes/retry": "^0.4.2",
+        "@types/estree": "^1.0.6",
+        "ajv": "^6.12.4",
+        "chalk": "^4.0.0",
+        "cross-spawn": "^7.0.6",
+        "debug": "^4.3.2",
+        "escape-string-regexp": "^4.0.0",
+        "eslint-scope": "^8.4.0",
+        "eslint-visitor-keys": "^4.2.1",
+        "espree": "^10.4.0",
+        "esquery": "^1.5.0",
+        "esutils": "^2.0.2",
+        "fast-deep-equal": "^3.1.3",
+        "file-entry-cache": "^8.0.0",
+        "find-up": "^5.0.0",
+        "glob-parent": "^6.0.2",
+        "ignore": "^5.2.0",
+        "imurmurhash": "^0.1.4",
+        "is-glob": "^4.0.0",
+        "json-stable-stringify-without-jsonify": "^1.0.1",
+        "lodash.merge": "^4.6.2",
+        "minimatch": "^3.1.2",
+        "natural-compare": "^1.4.0",
+        "optionator": "^0.9.3"
+      },
+      "bin": {
+        "eslint": "bin/eslint.js"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://eslint.org/donate"
+      },
+      "peerDependencies": {
+        "jiti": "*"
+      },
+      "peerDependenciesMeta": {
+        "jiti": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/eslint-compat-utils": {
+      "version": "0.6.5",
+      "resolved": "https://registry.npmjs.org/eslint-compat-utils/-/eslint-compat-utils-0.6.5.tgz",
+      "integrity": "sha512-vAUHYzue4YAa2hNACjB8HvUQj5yehAZgiClyFVVom9cP8z5NSFq3PwB/TtJslN2zAMgRX6FCFCjYBbQh71g5RQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "semver": "^7.5.4"
+      },
+      "engines": {
+        "node": ">=12"
+      },
+      "peerDependencies": {
+        "eslint": ">=6.0.0"
+      }
+    },
+    "node_modules/eslint-config-prettier": {
+      "version": "10.1.8",
+      "resolved": "https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-10.1.8.tgz",
+      "integrity": "sha512-82GZUjRS0p/jganf6q1rEO25VSoHH0hKPCTrgillPjdI/3bgBhAE1QzHrHTizjpRvy6pGAvKjDJtk2pF9NDq8w==",
+      "dev": true,
+      "bin": {
+        "eslint-config-prettier": "bin/cli.js"
+      },
+      "funding": {
+        "url": "https://opencollective.com/eslint-config-prettier"
+      },
+      "peerDependencies": {
+        "eslint": ">=7.0.0"
+      }
+    },
+    "node_modules/eslint-plugin-astro": {
+      "version": "1.5.0",
+      "resolved": "https://registry.npmjs.org/eslint-plugin-astro/-/eslint-plugin-astro-1.5.0.tgz",
+      "integrity": "sha512-IWy4kY3DKTJxd7g652zIWpBGFuxw7NIIt16kyqc8BlhnIKvI8yGJj+Maua0DiNYED3F/D8AmzoTTTA6A95WX9g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@eslint-community/eslint-utils": "^4.2.0",
+        "@jridgewell/sourcemap-codec": "^1.4.14",
+        "@typescript-eslint/types": "^7.7.1 || ^8",
+        "astro-eslint-parser": "^1.0.2",
+        "eslint-compat-utils": "^0.6.0",
+        "globals": "^16.0.0",
+        "postcss": "^8.4.14",
+        "postcss-selector-parser": "^7.0.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ota-meshi"
+      },
+      "peerDependencies": {
+        "eslint": ">=8.57.0"
+      }
+    },
+    "node_modules/eslint-plugin-astro/node_modules/globals": {
+      "version": "16.5.0",
+      "resolved": "https://registry.npmjs.org/globals/-/globals-16.5.0.tgz",
+      "integrity": "sha512-c/c15i26VrJ4IRt5Z89DnIzCGDn9EcebibhAOjw5ibqEHsE1wLUgkPn9RDmNcUKyU87GeaL633nyJ+pplFR2ZQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/eslint-plugin-jsx-a11y": {
+      "version": "6.10.2",
+      "resolved": "https://registry.npmjs.org/eslint-plugin-jsx-a11y/-/eslint-plugin-jsx-a11y-6.10.2.tgz",
+      "integrity": "sha512-scB3nz4WmG75pV8+3eRUQOHZlNSUhFNq37xnpgRkCCELU3XMvXAxLk1eqWWyE22Ki4Q01Fnsw9BA3cJHDPgn2Q==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "aria-query": "^5.3.2",
+        "array-includes": "^3.1.8",
+        "array.prototype.flatmap": "^1.3.2",
+        "ast-types-flow": "^0.0.8",
+        "axe-core": "^4.10.0",
+        "axobject-query": "^4.1.0",
+        "damerau-levenshtein": "^1.0.8",
+        "emoji-regex": "^9.2.2",
+        "hasown": "^2.0.2",
+        "jsx-ast-utils": "^3.3.5",
+        "language-tags": "^1.0.9",
+        "minimatch": "^3.1.2",
+        "object.fromentries": "^2.0.8",
+        "safe-regex-test": "^1.0.3",
+        "string.prototype.includes": "^2.0.1"
+      },
+      "engines": {
+        "node": ">=4.0"
+      },
+      "peerDependencies": {
+        "eslint": "^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9"
+      }
+    },
+    "node_modules/eslint-plugin-jsx-a11y/node_modules/emoji-regex": {
+      "version": "9.2.2",
+      "resolved": "https://registry.npmjs.org/emoji-regex/-/emoji-regex-9.2.2.tgz",
+      "integrity": "sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/eslint-scope": {
+      "version": "8.4.0",
+      "resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-8.4.0.tgz",
+      "integrity": "sha512-sNXOfKCn74rt8RICKMvJS7XKV/Xk9kA7DyJr8mJik3S7Cwgy3qlkkmyS2uQB3jiJg6VNdZd/pDBJu0nvG2NlTg==",
+      "dev": true,
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "esrecurse": "^4.3.0",
+        "estraverse": "^5.2.0"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/eslint"
+      }
+    },
+    "node_modules/eslint-visitor-keys": {
+      "version": "4.2.1",
+      "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-4.2.1.tgz",
+      "integrity": "sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==",
+      "dev": true,
+      "license": "Apache-2.0",
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/eslint"
+      }
+    },
+    "node_modules/eslint/node_modules/ansi-styles": {
+      "version": "4.3.0",
+      "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-4.3.0.tgz",
+      "integrity": "sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "color-convert": "^2.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/ansi-styles?sponsor=1"
+      }
+    },
+    "node_modules/eslint/node_modules/chalk": {
+      "version": "4.1.2",
+      "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
+      "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "ansi-styles": "^4.1.0",
+        "supports-color": "^7.1.0"
+      },
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/chalk?sponsor=1"
+      }
+    },
+    "node_modules/eslint/node_modules/escape-string-regexp": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
+      "integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/espree": {
+      "version": "10.4.0",
+      "resolved": "https://registry.npmjs.org/espree/-/espree-10.4.0.tgz",
+      "integrity": "sha512-j6PAQ2uUr79PZhBjP5C5fhl8e39FmRnOjsD5lGnWrFU8i2G776tBK7+nP8KuQUTTyAZUwfQqXAgrVH5MbH9CYQ==",
+      "dev": true,
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "acorn": "^8.15.0",
+        "acorn-jsx": "^5.3.2",
+        "eslint-visitor-keys": "^4.2.1"
+      },
+      "engines": {
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/eslint"
+      }
+    },
+    "node_modules/esprima": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz",
+      "integrity": "sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==",
+      "bin": {
+        "esparse": "bin/esparse.js",
+        "esvalidate": "bin/esvalidate.js"
+      },
+      "engines": {
+        "node": ">=4"
+      }
+    },
+    "node_modules/esquery": {
+      "version": "1.7.0",
+      "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.7.0.tgz",
+      "integrity": "sha512-Ap6G0WQwcU/LHsvLwON1fAQX9Zp0A2Y6Y/cJBl9r/JbW90Zyg4/zbG6zzKa2OTALELarYHmKu0GhpM5EO+7T0g==",
+      "dev": true,
+      "license": "BSD-3-Clause",
+      "dependencies": {
+        "estraverse": "^5.1.0"
+      },
+      "engines": {
+        "node": ">=0.10"
+      }
+    },
+    "node_modules/esrecurse": {
+      "version": "4.3.0",
+      "resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
+      "integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
+      "dev": true,
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "estraverse": "^5.2.0"
+      },
+      "engines": {
+        "node": ">=4.0"
+      }
+    },
+    "node_modules/estraverse": {
+      "version": "5.3.0",
+      "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
+      "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
+      "dev": true,
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">=4.0"
+      }
+    },
+    "node_modules/estree-util-attach-comments": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/estree-util-attach-comments/-/estree-util-attach-comments-3.0.0.tgz",
+      "integrity": "sha512-cKUwm/HUcTDsYh/9FgnuFqpfquUbwIqwKM26BVCGDPVgvaCl/nDCCjUfiLlx6lsEZ3Z4RFxNbOQ60pkaEwFxGw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-util-build-jsx": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/estree-util-build-jsx/-/estree-util-build-jsx-3.0.1.tgz",
+      "integrity": "sha512-8U5eiL6BTrPxp/CHbs2yMgP8ftMhR5ww1eIKoWRMlqvltHF8fZn5LRDvTKuxD3DUn+shRbLGqXemcP51oFCsGQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-is-identifier-name": "^3.0.0",
+        "estree-walker": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-util-is-identifier-name": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/estree-util-is-identifier-name/-/estree-util-is-identifier-name-3.0.0.tgz",
+      "integrity": "sha512-hFtqIDZTIUZ9BXLb8y4pYGyk6+wekIivNVTcmvk8NoOh+VeRn5y6cEHzbURrWbfp1fIqdVipilzj+lfaadNZmg==",
+      "license": "MIT",
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-util-scope": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/estree-util-scope/-/estree-util-scope-1.0.0.tgz",
+      "integrity": "sha512-2CAASclonf+JFWBNJPndcOpA8EMJwa0Q8LUFJEKqXLW6+qBvbFZuF5gItbQOs/umBUkjviCSDCbBwU2cXbmrhQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "devlop": "^1.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-util-to-js": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/estree-util-to-js/-/estree-util-to-js-2.0.0.tgz",
+      "integrity": "sha512-WDF+xj5rRWmD5tj6bIqRi6CkLIXbbNQUcxQHzGysQzvHmdYG2G7p/Tf0J0gpxGgkeMZNTIjT/AoSvC9Xehcgdg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "astring": "^1.8.0",
+        "source-map": "^0.7.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-util-visit": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/estree-util-visit/-/estree-util-visit-2.0.0.tgz",
+      "integrity": "sha512-m5KgiH85xAhhW8Wta0vShLcUvOsh3LLPI2YVwcbio1l7E09NTLL1EyMZFM1OyWowoH0skScNbhOPl4kcBgzTww==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "@types/unist": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/estree-walker": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/estree-walker/-/estree-walker-3.0.3.tgz",
+      "integrity": "sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0"
+      }
+    },
+    "node_modules/esutils": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz",
+      "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==",
+      "dev": true,
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/eventemitter3": {
+      "version": "5.0.4",
+      "resolved": "https://registry.npmjs.org/eventemitter3/-/eventemitter3-5.0.4.tgz",
+      "integrity": "sha512-mlsTRyGaPBjPedk6Bvw+aqbsXDtoAyAzm5MO7JgU+yVRyMQ5O8bD4Kcci7BS85f93veegeCPkL8R4GLClnjLFw==",
+      "license": "MIT"
+    },
+    "node_modules/expressive-code": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/expressive-code/-/expressive-code-0.41.7.tgz",
+      "integrity": "sha512-2wZjC8OQ3TaVEMcBtYY4Va3lo6J+Ai9jf3d4dbhURMJcU4Pbqe6EcHe424MIZI0VHUA1bR6xdpoHYi3yxokWqA==",
+      "dependencies": {
+        "@expressive-code/core": "^0.41.7",
+        "@expressive-code/plugin-frames": "^0.41.7",
+        "@expressive-code/plugin-shiki": "^0.41.7",
+        "@expressive-code/plugin-text-markers": "^0.41.7"
+      }
+    },
+    "node_modules/exsolve": {
+      "version": "1.0.8",
+      "resolved": "https://registry.npmjs.org/exsolve/-/exsolve-1.0.8.tgz",
+      "integrity": "sha512-LmDxfWXwcTArk8fUEnOfSZpHOJ6zOMUJKOtFLFqJLoKJetuQG874Uc7/Kki7zFLzYybmZhp1M7+98pfMqeX8yA==",
+      "license": "MIT"
+    },
+    "node_modules/extend": {
+      "version": "3.0.2",
+      "resolved": "https://registry.npmjs.org/extend/-/extend-3.0.2.tgz",
+      "integrity": "sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==",
+      "license": "MIT"
+    },
+    "node_modules/extend-shallow": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/extend-shallow/-/extend-shallow-2.0.1.tgz",
+      "integrity": "sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==",
+      "dependencies": {
+        "is-extendable": "^0.1.0"
+      },
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/extract-zip": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/extract-zip/-/extract-zip-2.0.1.tgz",
+      "integrity": "sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==",
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "debug": "^4.1.1",
+        "get-stream": "^5.1.0",
+        "yauzl": "^2.10.0"
+      },
+      "bin": {
+        "extract-zip": "cli.js"
+      },
+      "engines": {
+        "node": ">= 10.17.0"
+      },
+      "optionalDependencies": {
+        "@types/yauzl": "^2.9.1"
+      }
+    },
+    "node_modules/fast-deep-equal": {
+      "version": "3.1.3",
+      "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
+      "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/fast-glob": {
+      "version": "3.3.3",
+      "resolved": "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.3.tgz",
+      "integrity": "sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "@nodelib/fs.stat": "^2.0.2",
+        "@nodelib/fs.walk": "^1.2.3",
+        "glob-parent": "^5.1.2",
+        "merge2": "^1.3.0",
+        "micromatch": "^4.0.8"
+      },
+      "engines": {
+        "node": ">=8.6.0"
+      }
+    },
+    "node_modules/fast-glob/node_modules/glob-parent": {
+      "version": "5.1.2",
+      "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz",
+      "integrity": "sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "is-glob": "^4.0.1"
+      },
+      "engines": {
+        "node": ">= 6"
+      }
+    },
+    "node_modules/fast-json-stable-stringify": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
+      "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/fast-levenshtein": {
+      "version": "2.0.6",
+      "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
+      "integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/fast-xml-builder": {
+      "version": "1.1.4",
+      "resolved": "https://registry.npmjs.org/fast-xml-builder/-/fast-xml-builder-1.1.4.tgz",
+      "integrity": "sha512-f2jhpN4Eccy0/Uz9csxh3Nu6q4ErKxf0XIsasomfOihuSUa3/xw6w8dnOtCDgEItQFJG8KyXPzQXzcODDrrbOg==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/NaturalIntelligence"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "path-expression-matcher": "^1.1.3"
+      }
+    },
+    "node_modules/fast-xml-parser": {
+      "version": "5.5.9",
+      "resolved": "https://registry.npmjs.org/fast-xml-parser/-/fast-xml-parser-5.5.9.tgz",
+      "integrity": "sha512-jldvxr1MC6rtiZKgrFnDSvT8xuH+eJqxqOBThUVjYrxssYTo1avZLGql5l0a0BAERR01CadYzZ83kVEkbyDg+g==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/NaturalIntelligence"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "fast-xml-builder": "^1.1.4",
+        "path-expression-matcher": "^1.2.0",
+        "strnum": "^2.2.2"
+      },
+      "bin": {
+        "fxparser": "src/cli/cli.js"
+      }
+    },
+    "node_modules/fastq": {
+      "version": "1.20.1",
+      "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.20.1.tgz",
+      "integrity": "sha512-GGToxJ/w1x32s/D2EKND7kTil4n8OVk/9mycTc4VDza13lOvpUZTGX3mFSCtV9ksdGBVzvsyAVLM6mHFThxXxw==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "reusify": "^1.0.4"
+      }
+    },
+    "node_modules/fd-slicer": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/fd-slicer/-/fd-slicer-1.1.0.tgz",
+      "integrity": "sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==",
+      "license": "MIT",
+      "dependencies": {
+        "pend": "~1.2.0"
+      }
+    },
+    "node_modules/fdir": {
+      "version": "6.5.0",
+      "resolved": "https://registry.npmjs.org/fdir/-/fdir-6.5.0.tgz",
+      "integrity": "sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=12.0.0"
+      },
+      "peerDependencies": {
+        "picomatch": "^3 || ^4"
+      },
+      "peerDependenciesMeta": {
+        "picomatch": {
+          "optional": true
+        }
+      }
+    },
+    "node_modules/fflate": {
+      "version": "0.7.4",
+      "resolved": "https://registry.npmjs.org/fflate/-/fflate-0.7.4.tgz",
+      "integrity": "sha512-5u2V/CDW15QM1XbbgS+0DfPxVB+jUKhWEKuuFuHncbk3tEEqzmoXL+2KyOFuKGqOnmdIy0/davWF1CkuwtibCw==",
+      "license": "MIT"
+    },
+    "node_modules/file-entry-cache": {
+      "version": "8.0.0",
+      "resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-8.0.0.tgz",
+      "integrity": "sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "flat-cache": "^4.0.0"
+      },
+      "engines": {
+        "node": ">=16.0.0"
+      }
+    },
+    "node_modules/fill-range": {
+      "version": "7.1.1",
+      "resolved": "https://registry.npmjs.org/fill-range/-/fill-range-7.1.1.tgz",
+      "integrity": "sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "to-regex-range": "^5.0.1"
+      },
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/find-up": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
+      "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "locate-path": "^6.0.0",
+        "path-exists": "^4.0.0"
+      },
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/flat-cache": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-4.0.1.tgz",
+      "integrity": "sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "flatted": "^3.2.9",
+        "keyv": "^4.5.4"
+      },
+      "engines": {
+        "node": ">=16"
+      }
+    },
+    "node_modules/flatted": {
+      "version": "3.4.2",
+      "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.4.2.tgz",
+      "integrity": "sha512-PjDse7RzhcPkIJwy5t7KPWQSZ9cAbzQXcafsetQoD7sOJRQlGikNbx7yZp2OotDnJyrDcbyRq3Ttb18iYOqkxA==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/flattie": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/flattie/-/flattie-1.1.1.tgz",
+      "integrity": "sha512-9UbaD6XdAL97+k/n+N7JwX46K/M6Zc6KcFYskrYL8wbBV/Uyk0CTAMY0VT+qiK5PM7AIc9aTWYtq65U7T+aCNQ==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/fontace": {
+      "version": "0.4.1",
+      "resolved": "https://registry.npmjs.org/fontace/-/fontace-0.4.1.tgz",
+      "integrity": "sha512-lDMvbAzSnHmbYMTEld5qdtvNH2/pWpICOqpean9IgC7vUbUJc3k+k5Dokp85CegamqQpFbXf0rAVkbzpyTA8aw==",
+      "license": "MIT",
+      "dependencies": {
+        "fontkitten": "^1.0.2"
+      }
+    },
+    "node_modules/fontkitten": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/fontkitten/-/fontkitten-1.0.2.tgz",
+      "integrity": "sha512-piJxbLnkD9Xcyi7dWJRnqszEURixe7CrF/efBfbffe2DPyabmuIuqraruY8cXTs19QoM8VJzx47BDRVNXETM7Q==",
+      "license": "MIT",
+      "dependencies": {
+        "tiny-inflate": "^1.0.3"
+      },
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/for-each": {
+      "version": "0.3.5",
+      "resolved": "https://registry.npmjs.org/for-each/-/for-each-0.3.5.tgz",
+      "integrity": "sha512-dKx12eRCVIzqCxFGplyFKJMPvLEWgmNtUrpTiJIR5u97zEhRG8ySrtboPHZXx7daLxQVrl643cTzbab2tkQjxg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "is-callable": "^1.2.7"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/fsevents": {
+      "version": "2.3.3",
+      "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.3.tgz",
+      "integrity": "sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==",
+      "hasInstallScript": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
+      "engines": {
+        "node": "^8.16.0 || ^10.6.0 || >=11.0.0"
+      }
+    },
+    "node_modules/function-bind": {
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz",
+      "integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==",
+      "dev": true,
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/function.prototype.name": {
+      "version": "1.1.8",
+      "resolved": "https://registry.npmjs.org/function.prototype.name/-/function.prototype.name-1.1.8.tgz",
+      "integrity": "sha512-e5iwyodOHhbMr/yNrc7fDYG4qlbIvI5gajyzPnb5TCwyhjApznQh1BMFou9b30SevY43gCJKXycoCBjMbsuW0Q==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.3",
+        "define-properties": "^1.2.1",
+        "functions-have-names": "^1.2.3",
+        "hasown": "^2.0.2",
+        "is-callable": "^1.2.7"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/functions-have-names": {
+      "version": "1.2.3",
+      "resolved": "https://registry.npmjs.org/functions-have-names/-/functions-have-names-1.2.3.tgz",
+      "integrity": "sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==",
+      "dev": true,
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/generator-function": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/generator-function/-/generator-function-2.0.1.tgz",
+      "integrity": "sha512-SFdFmIJi+ybC0vjlHN0ZGVGHc3lgE0DxPAT0djjVg+kjOnSqclqmj0KQ7ykTOLP6YxoqOvuAODGdcHJn+43q3g==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/gensync": {
+      "version": "1.0.0-beta.2",
+      "resolved": "https://registry.npmjs.org/gensync/-/gensync-1.0.0-beta.2.tgz",
+      "integrity": "sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==",
+      "engines": {
+        "node": ">=6.9.0"
+      }
+    },
+    "node_modules/get-east-asian-width": {
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/get-east-asian-width/-/get-east-asian-width-1.4.0.tgz",
+      "integrity": "sha512-QZjmEOC+IT1uk6Rx0sX22V6uHWVwbdbxf1faPqJ1QhLdGgsRGCZoyaQBm/piRdJy/D2um6hM1UP7ZEeQ4EkP+Q==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/get-intrinsic": {
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.3.0.tgz",
+      "integrity": "sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind-apply-helpers": "^1.0.2",
+        "es-define-property": "^1.0.1",
+        "es-errors": "^1.3.0",
+        "es-object-atoms": "^1.1.1",
+        "function-bind": "^1.1.2",
+        "get-proto": "^1.0.1",
+        "gopd": "^1.2.0",
+        "has-symbols": "^1.1.0",
+        "hasown": "^2.0.2",
+        "math-intrinsics": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/get-proto": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/get-proto/-/get-proto-1.0.1.tgz",
+      "integrity": "sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "dunder-proto": "^1.0.1",
+        "es-object-atoms": "^1.0.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/get-stream": {
+      "version": "5.2.0",
+      "resolved": "https://registry.npmjs.org/get-stream/-/get-stream-5.2.0.tgz",
+      "integrity": "sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==",
+      "license": "MIT",
+      "dependencies": {
+        "pump": "^3.0.0"
+      },
+      "engines": {
+        "node": ">=8"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/get-symbol-description": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/get-symbol-description/-/get-symbol-description-1.1.0.tgz",
+      "integrity": "sha512-w9UMqWwJxHNOvoNzSJ2oPF5wvYcvP7jUvYzhp67yEhTi17ZDBBC1z9pTdGuzjD+EFIqLSYRweZjqfiPzQ06Ebg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "es-errors": "^1.3.0",
+        "get-intrinsic": "^1.2.6"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/github-slugger": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/github-slugger/-/github-slugger-2.0.0.tgz",
+      "integrity": "sha512-IaOQ9puYtjrkq7Y0Ygl9KDZnrf/aiUJYUpVf89y8kyaxbRG7Y1SrX/jaumrv81vc61+kiMempujsM3Yw7w5qcw==",
+      "license": "ISC"
+    },
+    "node_modules/glob-parent": {
+      "version": "6.0.2",
+      "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
+      "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
+      "dev": true,
+      "license": "ISC",
+      "dependencies": {
+        "is-glob": "^4.0.3"
+      },
+      "engines": {
+        "node": ">=10.13.0"
+      }
+    },
+    "node_modules/globals": {
+      "version": "17.4.0",
+      "resolved": "https://registry.npmjs.org/globals/-/globals-17.4.0.tgz",
+      "integrity": "sha512-hjrNztw/VajQwOLsMNT1cbJiH2muO3OROCHnbehc8eY5JyD2gqz4AcMHPqgaOR59DjgUjYAYLeH699g/eWi2jw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/globalthis": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/globalthis/-/globalthis-1.0.4.tgz",
+      "integrity": "sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "define-properties": "^1.2.1",
+        "gopd": "^1.0.1"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/gopd": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/gopd/-/gopd-1.2.0.tgz",
+      "integrity": "sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/gray-matter": {
+      "version": "4.0.3",
+      "resolved": "https://registry.npmjs.org/gray-matter/-/gray-matter-4.0.3.tgz",
+      "integrity": "sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==",
+      "dependencies": {
+        "js-yaml": "^3.13.1",
+        "kind-of": "^6.0.2",
+        "section-matter": "^1.0.0",
+        "strip-bom-string": "^1.0.0"
+      },
+      "engines": {
+        "node": ">=6.0"
+      }
+    },
+    "node_modules/gray-matter/node_modules/argparse": {
+      "version": "1.0.10",
+      "resolved": "https://registry.npmjs.org/argparse/-/argparse-1.0.10.tgz",
+      "integrity": "sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==",
+      "dependencies": {
+        "sprintf-js": "~1.0.2"
+      }
+    },
+    "node_modules/gray-matter/node_modules/js-yaml": {
+      "version": "3.14.2",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.14.2.tgz",
+      "integrity": "sha512-PMSmkqxr106Xa156c2M265Z+FTrPl+oxd/rgOQy2tijQeK5TxQ43psO1ZCwhVOSdnn+RzkzlRz/eY4BgJBYVpg==",
+      "dependencies": {
+        "argparse": "^1.0.7",
+        "esprima": "^4.0.0"
+      },
+      "bin": {
+        "js-yaml": "bin/js-yaml.js"
+      }
+    },
+    "node_modules/h3": {
+      "version": "1.15.10",
+      "resolved": "https://registry.npmjs.org/h3/-/h3-1.15.10.tgz",
+      "integrity": "sha512-YzJeWSkDZxAhvmp8dexjRK5hxziRO7I9m0N53WhvYL5NiWfkUkzssVzY9jvGu0HBoLFW6+duYmNSn6MaZBCCtg==",
+      "license": "MIT",
+      "dependencies": {
+        "cookie-es": "^1.2.2",
+        "crossws": "^0.3.5",
+        "defu": "^6.1.4",
+        "destr": "^2.0.5",
+        "iron-webcrypto": "^1.2.1",
+        "node-mock-http": "^1.0.4",
+        "radix3": "^1.1.2",
+        "ufo": "^1.6.3",
+        "uncrypto": "^0.1.3"
+      }
+    },
+    "node_modules/has-bigints": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.1.0.tgz",
+      "integrity": "sha512-R3pbpkcIqv2Pm3dUwgjclDRVmWpTJW2DcMzcIhEXEx1oh/CEMObMm3KLmRJOdvhM7o4uQBnwr8pzRK2sJWIqfg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/has-flag": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
+      "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8"
+      }
+    },
+    "node_modules/has-property-descriptors": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.2.tgz",
+      "integrity": "sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-define-property": "^1.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/has-proto": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/has-proto/-/has-proto-1.2.0.tgz",
+      "integrity": "sha512-KIL7eQPfHQRC8+XluaIw7BHUwwqL19bQn4hzNgdr+1wXoU0KKj6rufu47lhY7KbJR2C6T6+PfyN0Ea7wkSS+qQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "dunder-proto": "^1.0.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/has-symbols": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.1.0.tgz",
+      "integrity": "sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/has-tostringtag": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.2.tgz",
+      "integrity": "sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "has-symbols": "^1.0.3"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/hasown": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.2.tgz",
+      "integrity": "sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "function-bind": "^1.1.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/hast-util-from-html": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/hast-util-from-html/-/hast-util-from-html-2.0.3.tgz",
+      "integrity": "sha512-CUSRHXyKjzHov8yKsQjGOElXy/3EKpyX56ELnkHH34vDVw1N1XSQ1ZcAvTyAPtGqLTuKP/uxM+aLkSPqF/EtMw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "devlop": "^1.1.0",
+        "hast-util-from-parse5": "^8.0.0",
+        "parse5": "^7.0.0",
+        "vfile": "^6.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-from-parse5": {
+      "version": "8.0.3",
+      "resolved": "https://registry.npmjs.org/hast-util-from-parse5/-/hast-util-from-parse5-8.0.3.tgz",
+      "integrity": "sha512-3kxEVkEKt0zvcZ3hCRYI8rqrgwtlIOFMWkbclACvjlDw8Li9S2hk/d51OI0nr/gIpdMHNepwgOKqZ/sy0Clpyg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "devlop": "^1.0.0",
+        "hastscript": "^9.0.0",
+        "property-information": "^7.0.0",
+        "vfile": "^6.0.0",
+        "vfile-location": "^5.0.0",
+        "web-namespaces": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-has-property": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/hast-util-has-property/-/hast-util-has-property-3.0.0.tgz",
+      "integrity": "sha512-MNilsvEKLFpV604hwfhVStK0usFY/QmM5zX16bo7EjnAEGofr5YyI37kzopBlZJkHD4t887i+q/C8/tr5Q94cA==",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-heading-rank": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/hast-util-heading-rank/-/hast-util-heading-rank-3.0.0.tgz",
+      "integrity": "sha512-EJKb8oMUXVHcWZTDepnr+WNbfnXKFNf9duMesmr4S8SXTJBJ9M4Yok08pu9vxdJwdlGRhVumk9mEhkEvKGifwA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-is-element": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/hast-util-is-element/-/hast-util-is-element-3.0.0.tgz",
+      "integrity": "sha512-Val9mnv2IWpLbNPqc/pUem+a7Ipj2aHacCwgNfTiK0vJKl0LF+4Ba4+v1oPHFpf3bLYmreq0/l3Gud9S5OH42g==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-parse-selector": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/hast-util-parse-selector/-/hast-util-parse-selector-4.0.0.tgz",
+      "integrity": "sha512-wkQCkSYoOGCRKERFWcxMVMOcYE2K1AaNLU8DXS9arxnLOUEWbOXKXiJUNzEpqZ3JOKpnha3jkFrumEjVliDe7A==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-raw": {
+      "version": "9.1.0",
+      "resolved": "https://registry.npmjs.org/hast-util-raw/-/hast-util-raw-9.1.0.tgz",
+      "integrity": "sha512-Y8/SBAHkZGoNkpzqqfCldijcuUKh7/su31kEBp67cFY09Wy0mTRgtsLYsiIxMJxlu0f6AA5SUTbDR8K0rxnbUw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "@ungap/structured-clone": "^1.0.0",
+        "hast-util-from-parse5": "^8.0.0",
+        "hast-util-to-parse5": "^8.0.0",
+        "html-void-elements": "^3.0.0",
+        "mdast-util-to-hast": "^13.0.0",
+        "parse5": "^7.0.0",
+        "unist-util-position": "^5.0.0",
+        "unist-util-visit": "^5.0.0",
+        "vfile": "^6.0.0",
+        "web-namespaces": "^2.0.0",
+        "zwitch": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-select": {
+      "version": "6.0.4",
+      "resolved": "https://registry.npmjs.org/hast-util-select/-/hast-util-select-6.0.4.tgz",
+      "integrity": "sha512-RqGS1ZgI0MwxLaKLDxjprynNzINEkRHY2i8ln4DDjgv9ZhcYVIHN9rlpiYsqtFwrgpYU361SyWDQcGNIBVu3lw==",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "bcp-47-match": "^2.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "css-selector-parser": "^3.0.0",
+        "devlop": "^1.0.0",
+        "direction": "^2.0.0",
+        "hast-util-has-property": "^3.0.0",
+        "hast-util-to-string": "^3.0.0",
+        "hast-util-whitespace": "^3.0.0",
+        "nth-check": "^2.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0",
+        "unist-util-visit": "^5.0.0",
+        "zwitch": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-estree": {
+      "version": "3.1.3",
+      "resolved": "https://registry.npmjs.org/hast-util-to-estree/-/hast-util-to-estree-3.1.3.tgz",
+      "integrity": "sha512-48+B/rJWAp0jamNbAAf9M7Uf//UVqAoMmgXhBdxTDJLGKY+LRnZ99qcG+Qjl5HfMpYNzS5v4EAwVEF34LeAj7w==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "@types/estree-jsx": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-attach-comments": "^3.0.0",
+        "estree-util-is-identifier-name": "^3.0.0",
+        "hast-util-whitespace": "^3.0.0",
+        "mdast-util-mdx-expression": "^2.0.0",
+        "mdast-util-mdx-jsx": "^3.0.0",
+        "mdast-util-mdxjs-esm": "^2.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0",
+        "style-to-js": "^1.0.0",
+        "unist-util-position": "^5.0.0",
+        "zwitch": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-html": {
+      "version": "9.0.5",
+      "resolved": "https://registry.npmjs.org/hast-util-to-html/-/hast-util-to-html-9.0.5.tgz",
+      "integrity": "sha512-OguPdidb+fbHQSU4Q4ZiLKnzWo8Wwsf5bZfbvu7//a9oTYoqD/fWpe96NuHkoS9h0ccGOTe0C4NGXdtS0iObOw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "ccount": "^2.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "hast-util-whitespace": "^3.0.0",
+        "html-void-elements": "^3.0.0",
+        "mdast-util-to-hast": "^13.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0",
+        "stringify-entities": "^4.0.0",
+        "zwitch": "^2.0.4"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-jsx-runtime": {
+      "version": "2.3.6",
+      "resolved": "https://registry.npmjs.org/hast-util-to-jsx-runtime/-/hast-util-to-jsx-runtime-2.3.6.tgz",
+      "integrity": "sha512-zl6s8LwNyo1P9uw+XJGvZtdFF1GdAkOg8ujOw+4Pyb76874fLps4ueHXDhXWdk6YHQ6OgUtinliG7RsYvCbbBg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-is-identifier-name": "^3.0.0",
+        "hast-util-whitespace": "^3.0.0",
+        "mdast-util-mdx-expression": "^2.0.0",
+        "mdast-util-mdx-jsx": "^3.0.0",
+        "mdast-util-mdxjs-esm": "^2.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0",
+        "style-to-js": "^1.0.0",
+        "unist-util-position": "^5.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-parse5": {
+      "version": "8.0.1",
+      "resolved": "https://registry.npmjs.org/hast-util-to-parse5/-/hast-util-to-parse5-8.0.1.tgz",
+      "integrity": "sha512-MlWT6Pjt4CG9lFCjiz4BH7l9wmrMkfkJYCxFwKQic8+RTZgWPuWxwAfjJElsXkex7DJjfSJsQIt931ilUgmwdA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "devlop": "^1.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0",
+        "web-namespaces": "^2.0.0",
+        "zwitch": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-string": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/hast-util-to-string/-/hast-util-to-string-3.0.1.tgz",
+      "integrity": "sha512-XelQVTDWvqcl3axRfI0xSeoVKzyIFPwsAGSLIsKdJKQMXDYJS4WYrBNF/8J7RdhIcFI2BOHgAifggsvsxp/3+A==",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-to-text": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/hast-util-to-text/-/hast-util-to-text-4.0.2.tgz",
+      "integrity": "sha512-KK6y/BN8lbaq654j7JgBydev7wuNMcID54lkRav1P0CaE1e47P72AWWPiGKXTJU271ooYzcvTAn/Zt0REnvc7A==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/unist": "^3.0.0",
+        "hast-util-is-element": "^3.0.0",
+        "unist-util-find-after": "^5.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hast-util-whitespace": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/hast-util-whitespace/-/hast-util-whitespace-3.0.0.tgz",
+      "integrity": "sha512-88JUN06ipLwsnv+dVn+OIYOvAuvBMy/Qoi6O7mQHxdPXpjy+Cd6xRkWwux7DKO+4sYILtLBRIKgsdpS2gQc7qw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hastscript": {
+      "version": "9.0.1",
+      "resolved": "https://registry.npmjs.org/hastscript/-/hastscript-9.0.1.tgz",
+      "integrity": "sha512-g7df9rMFX/SPi34tyGCyUBREQoKkapwdY/T04Qn9TDWfHhAYt4/I0gMVirzK5wEzeUqIjEB+LXC/ypb7Aqno5w==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "comma-separated-tokens": "^2.0.0",
+        "hast-util-parse-selector": "^4.0.0",
+        "property-information": "^7.0.0",
+        "space-separated-tokens": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/hex-rgb": {
+      "version": "4.3.0",
+      "resolved": "https://registry.npmjs.org/hex-rgb/-/hex-rgb-4.3.0.tgz",
+      "integrity": "sha512-Ox1pJVrDCyGHMG9CFg1tmrRUMRPRsAWYc/PinY0XzJU4K7y7vjNoLKIQ7BR5UJMCxNN8EM1MNDmHWA/B3aZUuw==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/html-escaper": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/html-escaper/-/html-escaper-3.0.3.tgz",
+      "integrity": "sha512-RuMffC89BOWQoY0WKGpIhn5gX3iI54O6nRA0yC124NYVtzjmFWBIiFd8M0x+ZdX0P9R4lADg1mgP8C7PxGOWuQ==",
+      "license": "MIT"
+    },
+    "node_modules/html-url-attributes": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/html-url-attributes/-/html-url-attributes-3.0.1.tgz",
+      "integrity": "sha512-ol6UPyBWqsrO6EJySPz2O7ZSr856WDrEzM5zMqp+FJJLGMW35cLYmmZnl0vztAZxRUoNZJFTCohfjuIJ8I4QBQ==",
+      "license": "MIT",
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/html-void-elements": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/html-void-elements/-/html-void-elements-3.0.0.tgz",
+      "integrity": "sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/htmlparser2": {
+      "version": "10.1.0",
+      "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-10.1.0.tgz",
+      "integrity": "sha512-VTZkM9GWRAtEpveh7MSF6SjjrpNVNNVJfFup7xTY3UpFtm67foy9HDVXneLtFVt4pMz5kZtgNcvCniNFb1hlEQ==",
+      "funding": [
+        "https://github.com/fb55/htmlparser2?sponsor=1",
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/fb55"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "domelementtype": "^2.3.0",
+        "domhandler": "^5.0.3",
+        "domutils": "^3.2.2",
+        "entities": "^7.0.1"
+      }
+    },
+    "node_modules/htmlparser2/node_modules/entities": {
+      "version": "7.0.1",
+      "resolved": "https://registry.npmjs.org/entities/-/entities-7.0.1.tgz",
+      "integrity": "sha512-TWrgLOFUQTH994YUyl1yT4uyavY5nNB5muff+RtWaqNVCAK408b5ZnnbNAUEWLTCpum9w6arT70i1XdQ4UeOPA==",
+      "license": "BSD-2-Clause",
+      "engines": {
+        "node": ">=0.12"
+      },
+      "funding": {
+        "url": "https://github.com/fb55/entities?sponsor=1"
+      }
+    },
+    "node_modules/http-cache-semantics": {
+      "version": "4.2.0",
+      "resolved": "https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.2.0.tgz",
+      "integrity": "sha512-dTxcvPXqPvXBQpq5dUr6mEMJX4oIEFv6bwom3FDwKRDsuIjjJGANqhBuoAn9c1RQJIdAKav33ED65E2ys+87QQ==",
+      "license": "BSD-2-Clause"
+    },
+    "node_modules/husky": {
+      "version": "9.1.7",
+      "resolved": "https://registry.npmjs.org/husky/-/husky-9.1.7.tgz",
+      "integrity": "sha512-5gs5ytaNjBrh5Ow3zrvdUUY+0VxIuWVL4i9irt6friV+BqdCfmV11CQTWMiBYWHbXhco+J1kHfTOUkePhCDvMA==",
+      "dev": true,
+      "license": "MIT",
+      "bin": {
+        "husky": "bin.js"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/typicode"
+      }
+    },
+    "node_modules/iconv-lite": {
+      "version": "0.6.3",
+      "resolved": "https://registry.npmjs.org/iconv-lite/-/iconv-lite-0.6.3.tgz",
+      "integrity": "sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==",
+      "license": "MIT",
+      "dependencies": {
+        "safer-buffer": ">= 2.1.2 < 3.0.0"
+      },
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/ignore": {
+      "version": "5.3.2",
+      "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.2.tgz",
+      "integrity": "sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 4"
+      }
+    },
+    "node_modules/import-fresh": {
+      "version": "3.3.1",
+      "resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.1.tgz",
+      "integrity": "sha512-TR3KfrTZTYLPB6jUjfx6MF9WcWrHL9su5TObK4ZkYgBdWKPOFoSoQIdEuTuR82pmtxH2spWG9h6etwfr1pLBqQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "parent-module": "^1.0.0",
+        "resolve-from": "^4.0.0"
+      },
+      "engines": {
+        "node": ">=6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/imurmurhash": {
+      "version": "0.1.4",
+      "resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
+      "integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.8.19"
+      }
+    },
+    "node_modules/inline-style-parser": {
+      "version": "0.2.7",
+      "resolved": "https://registry.npmjs.org/inline-style-parser/-/inline-style-parser-0.2.7.tgz",
+      "integrity": "sha512-Nb2ctOyNR8DqQoR0OwRG95uNWIC0C1lCgf5Naz5H6Ji72KZ8OcFZLz2P5sNgwlyoJ8Yif11oMuYs5pBQa86csA==",
+      "license": "MIT"
+    },
+    "node_modules/internal-slot": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.1.0.tgz",
+      "integrity": "sha512-4gd7VpWNQNB4UKKCFFVcp1AVv+FMOgs9NKzjHKusc8jTMhd5eL1NqQqOpE0KzMds804/yHlglp3uxgluOqAPLw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0",
+        "hasown": "^2.0.2",
+        "side-channel": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/iron-webcrypto": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/iron-webcrypto/-/iron-webcrypto-1.2.1.tgz",
+      "integrity": "sha512-feOM6FaSr6rEABp/eDfVseKyTMDt+KGpeB35SkVn9Tyn0CqvVsY3EwI0v5i8nMHyJnzCIQf7nsy3p41TPkJZhg==",
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/brc-dd"
+      }
+    },
+    "node_modules/is-alphabetical": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/is-alphabetical/-/is-alphabetical-2.0.1.tgz",
+      "integrity": "sha512-FWyyY60MeTNyeSRpkM2Iry0G9hpr7/9kD40mD/cGQEuilcZYS4okz8SN2Q6rLCJ8gbCt6fN+rC+6tMGS99LaxQ==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/is-alphanumerical": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-2.0.1.tgz",
+      "integrity": "sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==",
+      "license": "MIT",
+      "dependencies": {
+        "is-alphabetical": "^2.0.0",
+        "is-decimal": "^2.0.0"
+      },
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/is-array-buffer": {
+      "version": "3.0.5",
+      "resolved": "https://registry.npmjs.org/is-array-buffer/-/is-array-buffer-3.0.5.tgz",
+      "integrity": "sha512-DDfANUiiG2wC1qawP66qlTugJeL5HyzMpfr8lLK+jMQirGzNod0B12cFB/9q838Ru27sBwfw78/rdoU7RERz6A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.3",
+        "get-intrinsic": "^1.2.6"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-arrayish": {
+      "version": "0.2.1",
+      "resolved": "https://registry.npmjs.org/is-arrayish/-/is-arrayish-0.2.1.tgz",
+      "integrity": "sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==",
+      "dev": true
+    },
+    "node_modules/is-async-function": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/is-async-function/-/is-async-function-2.1.1.tgz",
+      "integrity": "sha512-9dgM/cZBnNvjzaMYHVoxxfPj2QXt22Ev7SuuPrs+xav0ukGB0S6d4ydZdEiM48kLx5kDV+QBPrpVnFyefL8kkQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "async-function": "^1.0.0",
+        "call-bound": "^1.0.3",
+        "get-proto": "^1.0.1",
+        "has-tostringtag": "^1.0.2",
+        "safe-regex-test": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-bigint": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/is-bigint/-/is-bigint-1.1.0.tgz",
+      "integrity": "sha512-n4ZT37wG78iz03xPRKJrHTdZbe3IicyucEtdRsV5yglwc3GyUfbAfpSeD0FJ41NbUNSt5wbhqfp1fS+BgnvDFQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "has-bigints": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-boolean-object": {
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/is-boolean-object/-/is-boolean-object-1.2.2.tgz",
+      "integrity": "sha512-wa56o2/ElJMYqjCjGkXri7it5FbebW5usLw/nPmCMs5DeZ7eziSYZhSmPRn0txqeW4LnAmQQU7FgqLpsEFKM4A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "has-tostringtag": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-callable": {
+      "version": "1.2.7",
+      "resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.7.tgz",
+      "integrity": "sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-data-view": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/is-data-view/-/is-data-view-1.0.2.tgz",
+      "integrity": "sha512-RKtWF8pGmS87i2D6gqQu/l7EYRlVdfzemCJN/P3UOs//x1QE7mfhvzHIApBTRf7axvT6DMGwSwBXYCT0nfB9xw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.2",
+        "get-intrinsic": "^1.2.6",
+        "is-typed-array": "^1.1.13"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-date-object": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/is-date-object/-/is-date-object-1.1.0.tgz",
+      "integrity": "sha512-PwwhEakHVKTdRNVOw+/Gyh0+MzlCl4R6qKvkhuvLtPMggI1WAHt9sOwZxQLSGpUaDnrdyDsomoRgNnCfKNSXXg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.2",
+        "has-tostringtag": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-decimal": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/is-decimal/-/is-decimal-2.0.1.tgz",
+      "integrity": "sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/is-docker": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/is-docker/-/is-docker-3.0.0.tgz",
+      "integrity": "sha512-eljcgEDlEns/7AXFosB5K/2nCM4P7FQPkGc/DWLy5rmFEWvZayGrik1d9/QIY5nJ4f9YsVvBkA6kJpHn9rISdQ==",
+      "license": "MIT",
+      "bin": {
+        "is-docker": "cli.js"
+      },
+      "engines": {
+        "node": "^12.20.0 || ^14.13.1 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/is-extendable": {
+      "version": "0.1.1",
+      "resolved": "https://registry.npmjs.org/is-extendable/-/is-extendable-0.1.1.tgz",
+      "integrity": "sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/is-extglob": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
+      "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/is-finalizationregistry": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/is-finalizationregistry/-/is-finalizationregistry-1.1.1.tgz",
+      "integrity": "sha512-1pC6N8qWJbWoPtEjgcL2xyhQOP491EQjeUo3qTKcmV8YSDDJrOepfG8pcC7h/QgnQHYSv0mJ3Z/ZWxmatVrysg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-generator-function": {
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/is-generator-function/-/is-generator-function-1.1.2.tgz",
+      "integrity": "sha512-upqt1SkGkODW9tsGNG5mtXTXtECizwtS2kA161M+gJPc1xdb/Ax629af6YrTwcOeQHbewrPNlE5Dx7kzvXTizA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.4",
+        "generator-function": "^2.0.0",
+        "get-proto": "^1.0.1",
+        "has-tostringtag": "^1.0.2",
+        "safe-regex-test": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-glob": {
+      "version": "4.0.3",
+      "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
+      "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "is-extglob": "^2.1.1"
+      },
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/is-hexadecimal": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/is-hexadecimal/-/is-hexadecimal-2.0.1.tgz",
+      "integrity": "sha512-DgZQp241c8oO6cA1SbTEWiXeoxV42vlcJxgH+B3hi1AiqqKruZR3ZGF8In3fj4+/y/7rHvlOZLZtgJ/4ttYGZg==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/is-inside-container": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/is-inside-container/-/is-inside-container-1.0.0.tgz",
+      "integrity": "sha512-KIYLCCJghfHZxqjYBE7rEy0OBuTd5xCHS7tHVgvCLkx7StIoaxwNW3hCALgEUjFfeRk+MG/Qxmp/vtETEF3tRA==",
+      "license": "MIT",
+      "dependencies": {
+        "is-docker": "^3.0.0"
+      },
+      "bin": {
+        "is-inside-container": "cli.js"
+      },
+      "engines": {
+        "node": ">=14.16"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/is-map": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/is-map/-/is-map-2.0.3.tgz",
+      "integrity": "sha512-1Qed0/Hr2m+YqxnM09CjA2d/i6YZNfF6R2oRAOj36eUdS6qIV/huPJNSEpKbupewFs+ZsJlxsjjPbc0/afW6Lw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-negative-zero": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/is-negative-zero/-/is-negative-zero-2.0.3.tgz",
+      "integrity": "sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-number": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz",
+      "integrity": "sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.12.0"
+      }
+    },
+    "node_modules/is-number-object": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.1.1.tgz",
+      "integrity": "sha512-lZhclumE1G6VYD8VHe35wFaIif+CTy5SJIi5+3y4psDgWu4wPDoBhF8NxUOinEc7pHgiTsT6MaBb92rKhhD+Xw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "has-tostringtag": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-plain-obj": {
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/is-plain-obj/-/is-plain-obj-4.1.0.tgz",
+      "integrity": "sha512-+Pgi+vMuUNkJyExiMBt5IlFoMyKnr5zhJ4Uspz58WOhBF5QoIZkFyNHIbBAtHwzVAgk5RtndVNsDRN61/mmDqg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/is-regex": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.2.1.tgz",
+      "integrity": "sha512-MjYsKHO5O7mCsmRGxWcLWheFqN9DJ/2TmngvjKXihe6efViPqc274+Fx/4fYj/r03+ESvBdTXK0V6tA3rgez1g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.2",
+        "gopd": "^1.2.0",
+        "has-tostringtag": "^1.0.2",
+        "hasown": "^2.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-set": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/is-set/-/is-set-2.0.3.tgz",
+      "integrity": "sha512-iPAjerrse27/ygGLxw+EBR9agv9Y6uLeYVJMu+QNCoouJ1/1ri0mGrcWpfCqFZuzzx3WjtwxG098X+n4OuRkPg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-shared-array-buffer": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.4.tgz",
+      "integrity": "sha512-ISWac8drv4ZGfwKl5slpHG9OwPNty4jOWPRIhBpxOoD+hqITiwuipOQ2bNthAzwA3B4fIjO4Nln74N0S9byq8A==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-string": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/is-string/-/is-string-1.1.1.tgz",
+      "integrity": "sha512-BtEeSsoaQjlSPBemMQIrY1MY0uM6vnS1g5fmufYOtnxLGUZM2178PKbhsk7Ffv58IX+ZtcvoGwccYsh0PglkAA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "has-tostringtag": "^1.0.2"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-symbol": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/is-symbol/-/is-symbol-1.1.1.tgz",
+      "integrity": "sha512-9gGx6GTtCQM73BgmHQXfDmLtfjjTUDSyoxTCbp5WtoixAhfgsDirWIcVQ/IHpvI5Vgd5i/J5F7B9cN/WlVbC/w==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.2",
+        "has-symbols": "^1.1.0",
+        "safe-regex-test": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-typed-array": {
+      "version": "1.1.15",
+      "resolved": "https://registry.npmjs.org/is-typed-array/-/is-typed-array-1.1.15.tgz",
+      "integrity": "sha512-p3EcsicXjit7SaskXHs1hA91QxgTw46Fv6EFKKGS5DRFLD8yKnohjF3hxoju94b/OcMZoQukzpPpBE9uLVKzgQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "which-typed-array": "^1.1.16"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-weakmap": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/is-weakmap/-/is-weakmap-2.0.2.tgz",
+      "integrity": "sha512-K5pXYOm9wqY1RgjpL3YTkF39tni1XajUIkawTLUo9EZEVUFga5gSQJF8nNS7ZwJQ02y+1YCNYcMh+HIf1ZqE+w==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-weakref": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/is-weakref/-/is-weakref-1.1.1.tgz",
+      "integrity": "sha512-6i9mGWSlqzNMEqpCp93KwRS1uUOodk2OJ6b+sq7ZPDSy2WuI5NFIxp/254TytR8ftefexkWn5xNiHUNpPOfSew==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-weakset": {
+      "version": "2.0.4",
+      "resolved": "https://registry.npmjs.org/is-weakset/-/is-weakset-2.0.4.tgz",
+      "integrity": "sha512-mfcwb6IzQyOKTs84CQMrOwW4gQcaTOAWJ0zzJCl2WSPDrWk/OzDaImWFH3djXhb24g4eudZfLRozAvPGw4d9hQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bound": "^1.0.3",
+        "get-intrinsic": "^1.2.6"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
+      }
+    },
+    "node_modules/is-wsl": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/is-wsl/-/is-wsl-3.1.0.tgz",
+      "integrity": "sha512-UcVfVfaK4Sc4m7X3dUSoHoozQGBEFeDC+zVo06t98xe8CzHSZZBekNXH+tu0NalHolcJ/QAGqS46Hef7QXBIMw==",
+      "license": "MIT",
+      "dependencies": {
+        "is-inside-container": "^1.0.0"
+      },
+      "engines": {
+        "node": ">=16"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/isarray": {
+      "version": "2.0.5",
+      "resolved": "https://registry.npmjs.org/isarray/-/isarray-2.0.5.tgz",
+      "integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/isexe": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
+      "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
+      "dev": true,
+      "license": "ISC"
+    },
+    "node_modules/js-tokens": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/js-tokens/-/js-tokens-4.0.0.tgz",
+      "integrity": "sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ=="
+    },
+    "node_modules/js-yaml": {
+      "version": "4.1.1",
+      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz",
+      "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==",
+      "license": "MIT",
+      "dependencies": {
+        "argparse": "^2.0.1"
+      },
+      "bin": {
+        "js-yaml": "bin/js-yaml.js"
+      }
+    },
+    "node_modules/jsesc": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/jsesc/-/jsesc-3.1.0.tgz",
+      "integrity": "sha512-/sM3dO2FOzXjKQhJuo0Q173wf2KOo8t4I8vHy6lF9poUp7bKT0/NHE8fPX23PwfhnykfqnC2xRxOnVw5XuGIaA==",
+      "bin": {
+        "jsesc": "bin/jsesc"
+      },
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/json-buffer": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz",
+      "integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/json-parse-even-better-errors": {
+      "version": "2.3.1",
+      "resolved": "https://registry.npmjs.org/json-parse-even-better-errors/-/json-parse-even-better-errors-2.3.1.tgz",
+      "integrity": "sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==",
+      "dev": true
+    },
+    "node_modules/json-schema-traverse": {
+      "version": "0.4.1",
+      "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
+      "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/json-stable-stringify-without-jsonify": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
+      "integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/json5": {
+      "version": "2.2.3",
+      "resolved": "https://registry.npmjs.org/json5/-/json5-2.2.3.tgz",
+      "integrity": "sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==",
+      "bin": {
+        "json5": "lib/cli.js"
+      },
+      "engines": {
+        "node": ">=6"
+      }
+    },
+    "node_modules/jsx-ast-utils": {
+      "version": "3.3.5",
+      "resolved": "https://registry.npmjs.org/jsx-ast-utils/-/jsx-ast-utils-3.3.5.tgz",
+      "integrity": "sha512-ZZow9HBI5O6EPgSJLUb8n2NKgmVWTwCvHGwFuJlMjvLFqlGG6pjirPhtdsseaLZjSibD8eegzmYpUZwoIlj2cQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "array-includes": "^3.1.6",
+        "array.prototype.flat": "^1.3.1",
+        "object.assign": "^4.1.4",
+        "object.values": "^1.1.6"
+      },
+      "engines": {
+        "node": ">=4.0"
+      }
+    },
+    "node_modules/keyv": {
+      "version": "4.5.4",
+      "resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz",
+      "integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "json-buffer": "3.0.1"
+      }
+    },
+    "node_modules/kind-of": {
+      "version": "6.0.3",
+      "resolved": "https://registry.npmjs.org/kind-of/-/kind-of-6.0.3.tgz",
+      "integrity": "sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/kolorist": {
+      "version": "1.8.0",
+      "resolved": "https://registry.npmjs.org/kolorist/-/kolorist-1.8.0.tgz",
+      "integrity": "sha512-Y+60/zizpJ3HRH8DCss+q95yr6145JXZo46OTpFvDZWLfRCE4qChOyk1b26nMaNpfHHgxagk9dXT5OP0Tfe+dQ==",
+      "license": "MIT"
+    },
+    "node_modules/language-subtag-registry": {
+      "version": "0.3.23",
+      "resolved": "https://registry.npmjs.org/language-subtag-registry/-/language-subtag-registry-0.3.23.tgz",
+      "integrity": "sha512-0K65Lea881pHotoGEa5gDlMxt3pctLi2RplBb7Ezh4rRdLEOtgi7n4EwK9lamnUCkKBqaeKRVebTq6BAxSkpXQ==",
+      "dev": true,
+      "license": "CC0-1.0"
+    },
+    "node_modules/language-tags": {
+      "version": "1.0.9",
+      "resolved": "https://registry.npmjs.org/language-tags/-/language-tags-1.0.9.tgz",
+      "integrity": "sha512-MbjN408fEndfiQXbFQ1vnd+1NoLDsnQW41410oQBXiyXDMYH5z505juWa4KUE1LqxRC7DgOgZDbKLxHIwm27hA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "language-subtag-registry": "^0.3.20"
+      },
+      "engines": {
+        "node": ">=0.10"
+      }
+    },
+    "node_modules/levn": {
+      "version": "0.4.1",
+      "resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz",
+      "integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "prelude-ls": "^1.2.1",
+        "type-check": "~0.4.0"
+      },
+      "engines": {
+        "node": ">= 0.8.0"
+      }
+    },
+    "node_modules/linebreak": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/linebreak/-/linebreak-1.1.0.tgz",
+      "integrity": "sha512-MHp03UImeVhB7XZtjd0E4n6+3xr5Dq/9xI/5FptGk5FrbDR3zagPa2DS6U8ks/3HjbKWG9Q1M2ufOzxV2qLYSQ==",
+      "license": "MIT",
+      "dependencies": {
+        "base64-js": "0.0.8",
+        "unicode-trie": "^2.0.0"
+      }
+    },
+    "node_modules/lines-and-columns": {
+      "version": "1.2.4",
+      "resolved": "https://registry.npmjs.org/lines-and-columns/-/lines-and-columns-1.2.4.tgz",
+      "integrity": "sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==",
+      "dev": true
+    },
+    "node_modules/lint-staged": {
+      "version": "16.2.7",
+      "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-16.2.7.tgz",
+      "integrity": "sha512-lDIj4RnYmK7/kXMya+qJsmkRFkGolciXjrsZ6PC25GdTfWOAWetR0ZbsNXRAj1EHHImRSalc+whZFg56F5DVow==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "commander": "^14.0.2",
+        "listr2": "^9.0.5",
+        "micromatch": "^4.0.8",
+        "nano-spawn": "^2.0.0",
+        "pidtree": "^0.6.0",
+        "string-argv": "^0.3.2",
+        "yaml": "^2.8.1"
+      },
+      "bin": {
+        "lint-staged": "bin/lint-staged.js"
+      },
+      "engines": {
+        "node": ">=20.17"
+      },
+      "funding": {
+        "url": "https://opencollective.com/lint-staged"
+      }
+    },
+    "node_modules/lint-staged/node_modules/commander": {
+      "version": "14.0.2",
+      "resolved": "https://registry.npmjs.org/commander/-/commander-14.0.2.tgz",
+      "integrity": "sha512-TywoWNNRbhoD0BXs1P3ZEScW8W5iKrnbithIl0YH+uCmBd0QpPOA8yc82DS3BIE5Ma6FnBVUsJ7wVUDz4dvOWQ==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=20"
+      }
+    },
+    "node_modules/listr2": {
+      "version": "9.0.5",
+      "resolved": "https://registry.npmjs.org/listr2/-/listr2-9.0.5.tgz",
+      "integrity": "sha512-ME4Fb83LgEgwNw96RKNvKV4VTLuXfoKudAmm2lP8Kk87KaMK0/Xrx/aAkMWmT8mDb+3MlFDspfbCs7adjRxA2g==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "cli-truncate": "^5.0.0",
+        "colorette": "^2.0.20",
+        "eventemitter3": "^5.0.1",
+        "log-update": "^6.1.0",
+        "rfdc": "^1.4.1",
+        "wrap-ansi": "^9.0.0"
+      },
+      "engines": {
+        "node": ">=20.0.0"
+      }
+    },
+    "node_modules/local-pkg": {
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/local-pkg/-/local-pkg-1.1.2.tgz",
+      "integrity": "sha512-arhlxbFRmoQHl33a0Zkle/YWlmNwoyt6QNZEIJcqNbdrsix5Lvc4HyyI3EnwxTYlZYc32EbYrQ8SzEZ7dqgg9A==",
+      "license": "MIT",
+      "dependencies": {
+        "mlly": "^1.7.4",
+        "pkg-types": "^2.3.0",
+        "quansync": "^0.2.11"
+      },
+      "engines": {
+        "node": ">=14"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/antfu"
+      }
+    },
+    "node_modules/locate-path": {
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
+      "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "p-locate": "^5.0.0"
+      },
+      "engines": {
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/lodash.merge": {
+      "version": "4.6.2",
+      "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
+      "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/log-update": {
+      "version": "6.1.0",
+      "resolved": "https://registry.npmjs.org/log-update/-/log-update-6.1.0.tgz",
+      "integrity": "sha512-9ie8ItPR6tjY5uYJh8K/Zrv/RMZ5VOlOWvtZdEHYSTFKZfIBPQa9tOAEeAWhd+AnIneLJ22w5fjOYtoutpWq5w==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "ansi-escapes": "^7.0.0",
+        "cli-cursor": "^5.0.0",
+        "slice-ansi": "^7.1.0",
+        "strip-ansi": "^7.1.0",
+        "wrap-ansi": "^9.0.0"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/longest-streak": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/longest-streak/-/longest-streak-3.1.0.tgz",
+      "integrity": "sha512-9Ri+o0JYgehTaVBBDoMqIl8GXtbWg711O3srftcHhZ0dqnETqLaoIK0x17fUw9rFSlK/0NlsKe0Ahhyl5pXE2g==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/lower-case": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/lower-case/-/lower-case-2.0.2.tgz",
+      "integrity": "sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==",
+      "dev": true,
+      "dependencies": {
+        "tslib": "^2.0.3"
+      }
+    },
+    "node_modules/lru-cache": {
+      "version": "11.2.4",
+      "resolved": "https://registry.npmjs.org/lru-cache/-/lru-cache-11.2.4.tgz",
+      "integrity": "sha512-B5Y16Jr9LB9dHVkh6ZevG+vAbOsNOYCX+sXvFWFu7B3Iz5mijW3zdbMyhsh8ANd2mSWBYdJgnqi+mL7/LrOPYg==",
+      "license": "BlueOak-1.0.0",
+      "engines": {
+        "node": "20 || >=22"
+      }
+    },
+    "node_modules/magic-string": {
+      "version": "0.30.21",
+      "resolved": "https://registry.npmjs.org/magic-string/-/magic-string-0.30.21.tgz",
+      "integrity": "sha512-vd2F4YUyEXKGcLHoq+TEyCjxueSeHnFxyyjNp80yg0XV4vUhnDer/lvvlqM/arB5bXQN5K2/3oinyCRyx8T2CQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@jridgewell/sourcemap-codec": "^1.5.5"
+      }
+    },
+    "node_modules/magicast": {
+      "version": "0.5.2",
+      "resolved": "https://registry.npmjs.org/magicast/-/magicast-0.5.2.tgz",
+      "integrity": "sha512-E3ZJh4J3S9KfwdjZhe2afj6R9lGIN5Pher1pF39UGrXRqq/VDaGVIGN13BjHd2u8B61hArAGOnso7nBOouW3TQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@babel/parser": "^7.29.0",
+        "@babel/types": "^7.29.0",
+        "source-map-js": "^1.2.1"
+      }
+    },
+    "node_modules/markdown-extensions": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/markdown-extensions/-/markdown-extensions-2.0.0.tgz",
+      "integrity": "sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=16"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
+      }
+    },
+    "node_modules/markdown-table": {
+      "version": "3.0.4",
+      "resolved": "https://registry.npmjs.org/markdown-table/-/markdown-table-3.0.4.tgz",
+      "integrity": "sha512-wiYz4+JrLyb/DqW2hkFJxP7Vd7JuTDm77fvbM8VfEQdmSMqcImWeeRbHwZjBjIFki/VaMK2BhFi7oUUZeM5bqw==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
+    },
+    "node_modules/math-intrinsics": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/math-intrinsics/-/math-intrinsics-1.1.0.tgz",
+      "integrity": "sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/mdast-util-definitions": {
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-definitions/-/mdast-util-definitions-6.0.0.tgz",
+      "integrity": "sha512-scTllyX6pnYNZH/AIp/0ePz6s4cZtARxImwoPJ7kS42n+MnVsI4XbnG6d4ibehRIldYMWM2LD7ImQblVhUejVQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "@types/unist": "^3.0.0",
+        "unist-util-visit": "^5.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-find-and-replace": {
+      "version": "3.0.2",
+      "resolved": "https://registry.npmjs.org/mdast-util-find-and-replace/-/mdast-util-find-and-replace-3.0.2.tgz",
+      "integrity": "sha512-Tmd1Vg/m3Xz43afeNxDIhWRtFZgM2VLyaf4vSTYwudTyeuTneoL3qtWMA5jeLyz/O1vDJmmV4QuScFCA2tBPwg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "escape-string-regexp": "^5.0.0",
+        "unist-util-is": "^6.0.0",
+        "unist-util-visit-parents": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-from-markdown": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-2.0.3.tgz",
+      "integrity": "sha512-W4mAWTvSlKvf8L6J+VN9yLSqQ9AOAAvHuoDAmPkz4dHf553m5gVj2ejadHJhoJmcmxEnOv6Pa8XJhpxE93kb8Q==",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "@types/unist": "^3.0.0",
+        "decode-named-character-reference": "^1.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-to-string": "^4.0.0",
+        "micromark": "^4.0.0",
+        "micromark-util-decode-numeric-character-reference": "^2.0.0",
+        "micromark-util-decode-string": "^2.0.0",
+        "micromark-util-normalize-identifier": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "unist-util-stringify-position": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm/-/mdast-util-gfm-3.1.0.tgz",
+      "integrity": "sha512-0ulfdQOM3ysHhCJ1p06l0b0VKlhU0wuQs3thxZQagjcjPrlFRqY215uZGHHJan9GEAXd9MbfPjFJz+qMkVR6zQ==",
+      "license": "MIT",
+      "dependencies": {
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-gfm-autolink-literal": "^2.0.0",
+        "mdast-util-gfm-footnote": "^2.0.0",
+        "mdast-util-gfm-strikethrough": "^2.0.0",
+        "mdast-util-gfm-table": "^2.0.0",
+        "mdast-util-gfm-task-list-item": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm-autolink-literal": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm-autolink-literal/-/mdast-util-gfm-autolink-literal-2.0.1.tgz",
+      "integrity": "sha512-5HVP2MKaP6L+G6YaxPNjuL0BPrq9orG3TsrZ9YXbA3vDw/ACI4MEsnoDpn6ZNm7GnZgtAcONJyPhOP8tNJQavQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "ccount": "^2.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-find-and-replace": "^3.0.0",
+        "micromark-util-character": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm-footnote": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm-footnote/-/mdast-util-gfm-footnote-2.1.0.tgz",
+      "integrity": "sha512-sqpDWlsHn7Ac9GNZQMeUzPQSMzR6Wv0WKRNvQRg0KqHh02fpTz69Qc1QSseNX29bhz1ROIyNyxExfawVKTm1GQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.1.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0",
+        "micromark-util-normalize-identifier": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm-strikethrough": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm-strikethrough/-/mdast-util-gfm-strikethrough-2.0.0.tgz",
+      "integrity": "sha512-mKKb915TF+OC5ptj5bJ7WFRPdYtuHv0yTRxK2tJvi+BDqbkiG7h7u/9SI89nRAYcmap2xHQL9D+QG/6wSrTtXg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm-table": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm-table/-/mdast-util-gfm-table-2.0.0.tgz",
+      "integrity": "sha512-78UEvebzz/rJIxLvE7ZtDd/vIQ0RHv+3Mh5DR96p7cS7HsBhYIICDBCu8csTNWNO6tBWfqXPWekRuj2FNOGOZg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.0.0",
+        "markdown-table": "^3.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-gfm-task-list-item": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-gfm-task-list-item/-/mdast-util-gfm-task-list-item-2.0.0.tgz",
+      "integrity": "sha512-IrtvNvjxC1o06taBAVJznEnkiHxLFTzgonUdy8hzFVeDun0uTjxxrRGVaNFqkU1wJR3RBPEfsxmU6jDWPofrTQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-mdx": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-mdx/-/mdast-util-mdx-3.0.0.tgz",
+      "integrity": "sha512-JfbYLAW7XnYTTbUsmpu0kdBUVe+yKVJZBItEjwyYJiDJuZ9w4eeaqks4HQO+R7objWgS2ymV60GYpI14Ug554w==",
+      "license": "MIT",
+      "dependencies": {
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-mdx-expression": "^2.0.0",
+        "mdast-util-mdx-jsx": "^3.0.0",
+        "mdast-util-mdxjs-esm": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-mdx-expression": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/mdast-util-mdx-expression/-/mdast-util-mdx-expression-2.0.1.tgz",
+      "integrity": "sha512-J6f+9hUp+ldTZqKRSg7Vw5V6MqjATc+3E4gf3CFNcuZNWD8XdyI6zQ8GqH7f8169MM6P7hMBRDVGnn7oHB9kXQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-mdx-jsx": {
+      "version": "3.2.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-mdx-jsx/-/mdast-util-mdx-jsx-3.2.0.tgz",
+      "integrity": "sha512-lj/z8v0r6ZtsN/cGNNtemmmfoLAFZnjMbNyLzBafjzikOM+glrjNHPlf6lQDOTccj9n5b0PPihEBbhneMyGs1Q==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "@types/unist": "^3.0.0",
+        "ccount": "^2.0.0",
+        "devlop": "^1.1.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0",
+        "parse-entities": "^4.0.0",
+        "stringify-entities": "^4.0.0",
+        "unist-util-stringify-position": "^4.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-mdxjs-esm": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/mdast-util-mdxjs-esm/-/mdast-util-mdxjs-esm-2.0.1.tgz",
+      "integrity": "sha512-EcmOpxsZ96CvlP03NghtH1EsLtr0n9Tm4lPUJUBccV9RwUOneqSycg19n5HGzCf+10LozMRSObtVr3ee1WoHtg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree-jsx": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "mdast-util-to-markdown": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-phrasing": {
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-phrasing/-/mdast-util-phrasing-4.1.0.tgz",
+      "integrity": "sha512-TqICwyvJJpBwvGAMZjj4J2n0X8QWp21b9l0o7eXyVJ25YNWYbJDVIyD1bZXE6WtV6RmKJVYmQAKWa0zWOABz2w==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "unist-util-is": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-to-hast": {
+      "version": "13.2.1",
+      "resolved": "https://registry.npmjs.org/mdast-util-to-hast/-/mdast-util-to-hast-13.2.1.tgz",
+      "integrity": "sha512-cctsq2wp5vTsLIcaymblUriiTcZd0CwWtCbLvrOzYCDZoWyMNV8sZ7krj09FSnsiJi3WVsHLM4k6Dq/yaPyCXA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "@ungap/structured-clone": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-util-sanitize-uri": "^2.0.0",
+        "trim-lines": "^3.0.0",
+        "unist-util-position": "^5.0.0",
+        "unist-util-visit": "^5.0.0",
+        "vfile": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-to-markdown": {
+      "version": "2.1.2",
+      "resolved": "https://registry.npmjs.org/mdast-util-to-markdown/-/mdast-util-to-markdown-2.1.2.tgz",
+      "integrity": "sha512-xj68wMTvGXVOKonmog6LwyJKrYXZPvlwabaryTjLh9LuvovB/KAH+kvi8Gjj+7rJjsFi23nkUxRQv1KqSroMqA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "@types/unist": "^3.0.0",
+        "longest-streak": "^3.0.0",
+        "mdast-util-phrasing": "^4.0.0",
+        "mdast-util-to-string": "^4.0.0",
+        "micromark-util-classify-character": "^2.0.0",
+        "micromark-util-decode-string": "^2.0.0",
+        "unist-util-visit": "^5.0.0",
+        "zwitch": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdast-util-to-string": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/mdast-util-to-string/-/mdast-util-to-string-4.0.0.tgz",
+      "integrity": "sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==",
+      "dependencies": {
+        "@types/mdast": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/mdn-data": {
+      "version": "2.12.2",
+      "resolved": "https://registry.npmjs.org/mdn-data/-/mdn-data-2.12.2.tgz",
+      "integrity": "sha512-IEn+pegP1aManZuckezWCO+XZQDplx1366JoVhTpMpBB1sPey/SbveZQUosKiKiGYjg1wH4pMlNgXbCiYgihQA==",
+      "license": "CC0-1.0"
+    },
+    "node_modules/merge2": {
+      "version": "1.4.1",
+      "resolved": "https://registry.npmjs.org/merge2/-/merge2-1.4.1.tgz",
+      "integrity": "sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">= 8"
+      }
+    },
+    "node_modules/micromark": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/micromark/-/micromark-4.0.2.tgz",
+      "integrity": "sha512-zpe98Q6kvavpCr1NPVSCMebCKfD7CA2NqZ+rykeNhONIJBpc1tFKt9hucLGwha3jNTNI8lHpctWJWoimVF4PfA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "@types/debug": "^4.0.0",
+        "debug": "^4.0.0",
+        "decode-named-character-reference": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-core-commonmark": "^2.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-chunked": "^2.0.0",
+        "micromark-util-combine-extensions": "^2.0.0",
+        "micromark-util-decode-numeric-character-reference": "^2.0.0",
+        "micromark-util-encode": "^2.0.0",
+        "micromark-util-normalize-identifier": "^2.0.0",
+        "micromark-util-resolve-all": "^2.0.0",
+        "micromark-util-sanitize-uri": "^2.0.0",
+        "micromark-util-subtokenize": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-core-commonmark": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/micromark-core-commonmark/-/micromark-core-commonmark-2.0.3.tgz",
+      "integrity": "sha512-RDBrHEMSxVFLg6xvnXmb1Ayr2WzLAWjeSATAoxwKYJV94TeNavgoIdA0a9ytzDSVzBy2YKFK+emCPOEibLeCrg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "decode-named-character-reference": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-factory-destination": "^2.0.0",
+        "micromark-factory-label": "^2.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-factory-title": "^2.0.0",
+        "micromark-factory-whitespace": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-chunked": "^2.0.0",
+        "micromark-util-classify-character": "^2.0.0",
+        "micromark-util-html-tag-name": "^2.0.0",
+        "micromark-util-normalize-identifier": "^2.0.0",
+        "micromark-util-resolve-all": "^2.0.0",
+        "micromark-util-subtokenize": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-extension-gfm": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm/-/micromark-extension-gfm-3.0.0.tgz",
+      "integrity": "sha512-vsKArQsicm7t0z2GugkCKtZehqUm31oeGBV/KVSorWSy8ZlNAv7ytjFhvaryUiCUJYqs+NoE6AFhpQvBTM6Q4w==",
+      "license": "MIT",
+      "dependencies": {
+        "micromark-extension-gfm-autolink-literal": "^2.0.0",
+        "micromark-extension-gfm-footnote": "^2.0.0",
+        "micromark-extension-gfm-strikethrough": "^2.0.0",
+        "micromark-extension-gfm-table": "^2.0.0",
+        "micromark-extension-gfm-tagfilter": "^2.0.0",
+        "micromark-extension-gfm-task-list-item": "^2.0.0",
+        "micromark-util-combine-extensions": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-autolink-literal": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-autolink-literal/-/micromark-extension-gfm-autolink-literal-2.1.0.tgz",
+      "integrity": "sha512-oOg7knzhicgQ3t4QCjCWgTmfNhvQbDDnJeVu9v81r7NltNCVmhPy1fJRX27pISafdjL+SVc4d3l48Gb6pbRypw==",
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-sanitize-uri": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-footnote": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-footnote/-/micromark-extension-gfm-footnote-2.1.0.tgz",
+      "integrity": "sha512-/yPhxI1ntnDNsiHtzLKYnE3vf9JZ6cAisqVDauhp4CEHxlb4uoOTxOCJ+9s51bIB8U1N1FJ1RXOKTIlD5B/gqw==",
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-core-commonmark": "^2.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-normalize-identifier": "^2.0.0",
+        "micromark-util-sanitize-uri": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-strikethrough": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-strikethrough/-/micromark-extension-gfm-strikethrough-2.1.0.tgz",
+      "integrity": "sha512-ADVjpOOkjz1hhkZLlBiYA9cR2Anf8F4HqZUO6e5eDcPQd0Txw5fxLzzxnEkSkfnD0wziSGiv7sYhk/ktvbf1uw==",
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-util-chunked": "^2.0.0",
+        "micromark-util-classify-character": "^2.0.0",
+        "micromark-util-resolve-all": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-table": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-table/-/micromark-extension-gfm-table-2.1.1.tgz",
+      "integrity": "sha512-t2OU/dXXioARrC6yWfJ4hqB7rct14e8f7m0cbI5hUmDyyIlwv5vEtooptH8INkbLzOatzKuVbQmAYcbWoyz6Dg==",
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-tagfilter": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-tagfilter/-/micromark-extension-gfm-tagfilter-2.0.0.tgz",
+      "integrity": "sha512-xHlTOmuCSotIA8TW1mDIM6X2O1SiX5P9IuDtqGonFhEK0qgRI4yeC6vMxEV2dgyr2TiD+2PQ10o+cOhdVAcwfg==",
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-gfm-task-list-item": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-gfm-task-list-item/-/micromark-extension-gfm-task-list-item-2.1.0.tgz",
+      "integrity": "sha512-qIBZhqxqI6fjLDYFTBIa4eivDMnP+OZqsNwmQ3xNLE4Cxwc+zfQEfbs6tzAo2Hjq+bh6q5F+Z8/cksrLFYWQQw==",
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-mdx-expression": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-extension-mdx-expression/-/micromark-extension-mdx-expression-3.0.1.tgz",
+      "integrity": "sha512-dD/ADLJ1AeMvSAKBwO22zG22N4ybhe7kFIZ3LsDI0GlsNr2A3KYxb0LdC1u5rj4Nw+CHKY0RVdnHX8vj8ejm4Q==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-factory-mdx-expression": "^2.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-events-to-acorn": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-extension-mdx-jsx": {
+      "version": "3.0.2",
+      "resolved": "https://registry.npmjs.org/micromark-extension-mdx-jsx/-/micromark-extension-mdx-jsx-3.0.2.tgz",
+      "integrity": "sha512-e5+q1DjMh62LZAJOnDraSSbDMvGJ8x3cbjygy2qFEi7HCeUT4BDKCvMozPozcD6WmOt6sVvYDNBKhFSz3kjOVQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-is-identifier-name": "^3.0.0",
+        "micromark-factory-mdx-expression": "^2.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-events-to-acorn": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-mdx-md": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-mdx-md/-/micromark-extension-mdx-md-2.0.0.tgz",
+      "integrity": "sha512-EpAiszsB3blw4Rpba7xTOUptcFeBFi+6PY8VnJ2hhimH+vCQDirWgsMpz7w1XcZE7LVrSAUGb9VJpG9ghlYvYQ==",
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-mdxjs": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-mdxjs/-/micromark-extension-mdxjs-3.0.0.tgz",
+      "integrity": "sha512-A873fJfhnJ2siZyUrJ31l34Uqwy4xIFmvPY1oj+Ean5PHcPBYzEsvqvWGaWcfEIr11O5Dlw3p2y0tZWpKHDejQ==",
+      "license": "MIT",
+      "dependencies": {
+        "acorn": "^8.0.0",
+        "acorn-jsx": "^5.0.0",
+        "micromark-extension-mdx-expression": "^3.0.0",
+        "micromark-extension-mdx-jsx": "^3.0.0",
+        "micromark-extension-mdx-md": "^2.0.0",
+        "micromark-extension-mdxjs-esm": "^3.0.0",
+        "micromark-util-combine-extensions": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-extension-mdxjs-esm": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/micromark-extension-mdxjs-esm/-/micromark-extension-mdxjs-esm-3.0.0.tgz",
+      "integrity": "sha512-DJFl4ZqkErRpq/dAPyeWp15tGrcrrJho1hKK5uBS70BCtfrIFg81sqcTVu3Ta+KD1Tk5vAtBNElWxtAa+m8K9A==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-core-commonmark": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-events-to-acorn": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "unist-util-position-from-estree": "^2.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/micromark-factory-destination": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-factory-destination/-/micromark-factory-destination-2.0.1.tgz",
+      "integrity": "sha512-Xe6rDdJlkmbFRExpTOmRj9N3MaWmbAgdpSrBQvCFqhezUn4AHqJHbaEnfbVYYiexVSs//tqOdY/DxhjdCiJnIA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-factory-label": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-factory-label/-/micromark-factory-label-2.0.1.tgz",
+      "integrity": "sha512-VFMekyQExqIW7xIChcXn4ok29YE3rnuyveW3wZQWWqF4Nv9Wk5rgJ99KzPvHjkmPXF93FXIbBp6YdW3t71/7Vg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-factory-mdx-expression": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/micromark-factory-mdx-expression/-/micromark-factory-mdx-expression-2.0.3.tgz",
+      "integrity": "sha512-kQnEtA3vzucU2BkrIa8/VaSAsP+EJ3CKOvhMuJgOEGg9KDC6OAY6nSnNDVRiVNRqj7Y4SlSzcStaH/5jge8JdQ==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "devlop": "^1.0.0",
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-events-to-acorn": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "unist-util-position-from-estree": "^2.0.0",
+        "vfile-message": "^4.0.0"
+      }
+    },
+    "node_modules/micromark-factory-space": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-factory-space/-/micromark-factory-space-2.0.1.tgz",
+      "integrity": "sha512-zRkxjtBxxLd2Sc0d+fbnEunsTj46SWXgXciZmHq0kDYGnck/ZSGj9/wULTV95uoeYiK5hRXP2mJ98Uo4cq/LQg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-factory-title": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-factory-title/-/micromark-factory-title-2.0.1.tgz",
+      "integrity": "sha512-5bZ+3CjhAd9eChYTHsjy6TGxpOFSKgKKJPJxr293jTbfry2KDoWkhBb6TcPVB4NmzaPhMs1Frm9AZH7OD4Cjzw==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-factory-whitespace": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-factory-whitespace/-/micromark-factory-whitespace-2.0.1.tgz",
+      "integrity": "sha512-Ob0nuZ3PKt/n0hORHyvoD9uZhr+Za8sFoP+OnMcnWK5lngSzALgQYKMr9RJVOWLqQYuyn6ulqGWSXdwf6F80lQ==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-factory-space": "^2.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-character": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-character/-/micromark-util-character-2.1.1.tgz",
+      "integrity": "sha512-wv8tdUTJ3thSFFFJKtpYKOYiGP2+v96Hvk4Tu8KpCAsTMs6yi+nVmGh1syvSCsaxz45J6Jbw+9DD6g97+NV67Q==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-chunked": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-chunked/-/micromark-util-chunked-2.0.1.tgz",
+      "integrity": "sha512-QUNFEOPELfmvv+4xiNg2sRYeS/P84pTW0TCgP5zc9FpXetHY0ab7SxKyAQCNCc1eK0459uoLI1y5oO5Vc1dbhA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-symbol": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-classify-character": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-classify-character/-/micromark-util-classify-character-2.0.1.tgz",
+      "integrity": "sha512-K0kHzM6afW/MbeWYWLjoHQv1sgg2Q9EccHEDzSkxiP/EaagNzCm7T/WMKZ3rjMbvIpvBiZgwR3dKMygtA4mG1Q==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-combine-extensions": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-combine-extensions/-/micromark-util-combine-extensions-2.0.1.tgz",
+      "integrity": "sha512-OnAnH8Ujmy59JcyZw8JSbK9cGpdVY44NKgSM7E9Eh7DiLS2E9RNQf0dONaGDzEG9yjEl5hcqeIsj4hfRkLH/Bg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-chunked": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-decode-numeric-character-reference": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/micromark-util-decode-numeric-character-reference/-/micromark-util-decode-numeric-character-reference-2.0.2.tgz",
+      "integrity": "sha512-ccUbYk6CwVdkmCQMyr64dXz42EfHGkPQlBj5p7YVGzq8I7CtjXZJrubAYezf7Rp+bjPseiROqe7G6foFd+lEuw==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-symbol": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-decode-string": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-decode-string/-/micromark-util-decode-string-2.0.1.tgz",
+      "integrity": "sha512-nDV/77Fj6eH1ynwscYTOsbK7rR//Uj0bZXBwJZRfaLEJ1iGBR6kIfNmlNqaqJf649EP0F3NWNdeJi03elllNUQ==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "decode-named-character-reference": "^1.0.0",
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-decode-numeric-character-reference": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-encode": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-encode/-/micromark-util-encode-2.0.1.tgz",
+      "integrity": "sha512-c3cVx2y4KqUnwopcO9b/SCdo2O67LwJJ/UyqGfbigahfegL9myoEFoDYZgkT7f36T0bLrM9hZTAaAyH+PCAXjw==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/micromark-util-events-to-acorn": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/micromark-util-events-to-acorn/-/micromark-util-events-to-acorn-2.0.3.tgz",
+      "integrity": "sha512-jmsiEIiZ1n7X1Rr5k8wVExBQCg5jy4UXVADItHmNk1zkwEVhBuIUKRu3fqv+hs4nxLISi2DQGlqIOGiFxgbfHg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "@types/unist": "^3.0.0",
+        "devlop": "^1.0.0",
+        "estree-util-visit": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "vfile-message": "^4.0.0"
+      }
+    },
+    "node_modules/micromark-util-html-tag-name": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-html-tag-name/-/micromark-util-html-tag-name-2.0.1.tgz",
+      "integrity": "sha512-2cNEiYDhCWKI+Gs9T0Tiysk136SnR13hhO8yW6BGNyhOC4qYFnwF1nKfD3HFAIXA5c45RrIG1ub11GiXeYd1xA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/micromark-util-normalize-identifier": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-normalize-identifier/-/micromark-util-normalize-identifier-2.0.1.tgz",
+      "integrity": "sha512-sxPqmo70LyARJs0w2UclACPUUEqltCkJ6PhKdMIDuJ3gSf/Q+/GIe3WKl0Ijb/GyH9lOpUkRAO2wp0GVkLvS9Q==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-symbol": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-resolve-all": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-resolve-all/-/micromark-util-resolve-all-2.0.1.tgz",
+      "integrity": "sha512-VdQyxFWFT2/FGJgwQnJYbe1jjQoNTS4RjglmSjTUlpUMa95Htx9NHeYW4rGDJzbjvCsl9eLjMQwGeElsqmzcHg==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-sanitize-uri": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-sanitize-uri/-/micromark-util-sanitize-uri-2.0.1.tgz",
+      "integrity": "sha512-9N9IomZ/YuGGZZmQec1MbgxtlgougxTodVwDzzEouPKo3qFWvymFHWcnDi2vzV1ff6kas9ucW+o3yzJK9YB1AQ==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "micromark-util-character": "^2.0.0",
+        "micromark-util-encode": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-subtokenize": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/micromark-util-subtokenize/-/micromark-util-subtokenize-2.1.0.tgz",
+      "integrity": "sha512-XQLu552iSctvnEcgXw6+Sx75GflAPNED1qx7eBJ+wydBb2KCbRZe+NwvIEEMM83uml1+2WSXpBAcp9IUCgCYWA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT",
+      "dependencies": {
+        "devlop": "^1.0.0",
+        "micromark-util-chunked": "^2.0.0",
+        "micromark-util-symbol": "^2.0.0",
+        "micromark-util-types": "^2.0.0"
+      }
+    },
+    "node_modules/micromark-util-symbol": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/micromark-util-symbol/-/micromark-util-symbol-2.0.1.tgz",
+      "integrity": "sha512-vs5t8Apaud9N28kgCrRUdEed4UJ+wWNvicHLPxCa9ENlYuAY31M0ETy5y1vA33YoNPDFTghEbnh6efaE8h4x0Q==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/micromark-util-types": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/micromark-util-types/-/micromark-util-types-2.0.2.tgz",
+      "integrity": "sha512-Yw0ECSpJoViF1qTU4DC6NwtC4aWGt1EkzaQB8KPPyCRR8z9TWeV0HbEFGTO+ZY1wB22zmxnJqhPyTpOVCpeHTA==",
+      "funding": [
+        {
+          "type": "GitHub Sponsors",
+          "url": "https://github.com/sponsors/unifiedjs"
+        },
+        {
+          "type": "OpenCollective",
+          "url": "https://opencollective.com/unified"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/micromatch": {
+      "version": "4.0.8",
+      "resolved": "https://registry.npmjs.org/micromatch/-/micromatch-4.0.8.tgz",
+      "integrity": "sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "braces": "^3.0.3",
+        "picomatch": "^2.3.1"
+      },
+      "engines": {
+        "node": ">=8.6"
+      }
+    },
+    "node_modules/micromatch/node_modules/picomatch": {
+      "version": "2.3.1",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz",
+      "integrity": "sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=8.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/jonschlinkert"
+      }
+    },
+    "node_modules/mimic-function": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/mimic-function/-/mimic-function-5.0.1.tgz",
+      "integrity": "sha512-VP79XUPxV2CigYP3jWwAUFSku2aKqBH7uTAapFWCBqutsbmDo96KY5o8uh6U+/YSIn5OxJnXp73beVkpqMIGhA==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "define-data-property": "^1.0.1",
-        "has-property-descriptors": "^1.0.0",
-        "object-keys": "^1.1.1"
-      },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=18"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/doctrine": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/doctrine/-/doctrine-3.0.0.tgz",
-      "integrity": "sha512-yS+Q5i3hBf7GBkd4KG8a7eBNNWNGLTaEwwYWUijIYM7zrlYDM0BFXHjjPWlWZ1Rg7UaddZeIDmi9jF3HmqiQ2w==",
+    "node_modules/minimatch": {
+      "version": "3.1.5",
+      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.5.tgz",
+      "integrity": "sha512-VgjWUsnnT6n+NUk6eZq77zeFdpW2LWDzP6zFGrCbHXiYNul5Dzqk2HHQ5uFH2DNW5Xbp8+jVzaeNt94ssEEl4w==",
       "dev": true,
-      "license": "Apache-2.0",
+      "license": "ISC",
       "dependencies": {
-        "esutils": "^2.0.2"
+        "brace-expansion": "^1.1.7"
       },
       "engines": {
-        "node": ">=6.0.0"
+        "node": "*"
       }
     },
-    "node_modules/dunder-proto": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/dunder-proto/-/dunder-proto-1.0.1.tgz",
-      "integrity": "sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==",
-      "dev": true,
+    "node_modules/minipass": {
+      "version": "7.1.2",
+      "resolved": "https://registry.npmjs.org/minipass/-/minipass-7.1.2.tgz",
+      "integrity": "sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==",
+      "license": "ISC",
+      "engines": {
+        "node": ">=16 || 14 >=14.17"
+      }
+    },
+    "node_modules/minizlib": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/minizlib/-/minizlib-3.1.0.tgz",
+      "integrity": "sha512-KZxYo1BUkWD2TVFLr0MQoM8vUUigWD3LlD83a/75BqC+4qE0Hb1Vo5v1FgcfaNXvfXzr+5EhQ6ing/CaBijTlw==",
       "license": "MIT",
       "dependencies": {
-        "call-bind-apply-helpers": "^1.0.1",
-        "es-errors": "^1.3.0",
-        "gopd": "^1.2.0"
+        "minipass": "^7.1.2"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">= 18"
       }
     },
-    "node_modules/es-abstract": {
-      "version": "1.24.0",
-      "resolved": "https://registry.npmjs.org/es-abstract/-/es-abstract-1.24.0.tgz",
-      "integrity": "sha512-WSzPgsdLtTcQwm4CROfS5ju2Wa1QQcVeT37jFjYzdFz1r9ahadC8B8/a4qxJxM+09F18iumCdRmlr96ZYkQvEg==",
-      "dev": true,
+    "node_modules/mlly": {
+      "version": "1.8.0",
+      "resolved": "https://registry.npmjs.org/mlly/-/mlly-1.8.0.tgz",
+      "integrity": "sha512-l8D9ODSRWLe2KHJSifWGwBqpTZXIXTeo8mlKjY+E2HAakaTeNpqAyBZ8GSqLzHgw4XmHmC8whvpjJNMbFZN7/g==",
       "license": "MIT",
       "dependencies": {
-        "array-buffer-byte-length": "^1.0.2",
-        "arraybuffer.prototype.slice": "^1.0.4",
-        "available-typed-arrays": "^1.0.7",
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.4",
-        "data-view-buffer": "^1.0.2",
-        "data-view-byte-length": "^1.0.2",
-        "data-view-byte-offset": "^1.0.1",
-        "es-define-property": "^1.0.1",
-        "es-errors": "^1.3.0",
-        "es-object-atoms": "^1.1.1",
-        "es-set-tostringtag": "^2.1.0",
-        "es-to-primitive": "^1.3.0",
-        "function.prototype.name": "^1.1.8",
-        "get-intrinsic": "^1.3.0",
-        "get-proto": "^1.0.1",
-        "get-symbol-description": "^1.1.0",
-        "globalthis": "^1.0.4",
-        "gopd": "^1.2.0",
-        "has-property-descriptors": "^1.0.2",
-        "has-proto": "^1.2.0",
-        "has-symbols": "^1.1.0",
-        "hasown": "^2.0.2",
-        "internal-slot": "^1.1.0",
-        "is-array-buffer": "^3.0.5",
-        "is-callable": "^1.2.7",
-        "is-data-view": "^1.0.2",
-        "is-negative-zero": "^2.0.3",
-        "is-regex": "^1.2.1",
-        "is-set": "^2.0.3",
-        "is-shared-array-buffer": "^1.0.4",
-        "is-string": "^1.1.1",
-        "is-typed-array": "^1.1.15",
-        "is-weakref": "^1.1.1",
-        "math-intrinsics": "^1.1.0",
-        "object-inspect": "^1.13.4",
-        "object-keys": "^1.1.1",
-        "object.assign": "^4.1.7",
-        "own-keys": "^1.0.1",
-        "regexp.prototype.flags": "^1.5.4",
-        "safe-array-concat": "^1.1.3",
-        "safe-push-apply": "^1.0.0",
-        "safe-regex-test": "^1.1.0",
-        "set-proto": "^1.0.0",
-        "stop-iteration-iterator": "^1.1.0",
-        "string.prototype.trim": "^1.2.10",
-        "string.prototype.trimend": "^1.0.9",
-        "string.prototype.trimstart": "^1.0.8",
-        "typed-array-buffer": "^1.0.3",
-        "typed-array-byte-length": "^1.0.3",
-        "typed-array-byte-offset": "^1.0.4",
-        "typed-array-length": "^1.0.7",
-        "unbox-primitive": "^1.1.0",
-        "which-typed-array": "^1.1.19"
-      },
+        "acorn": "^8.15.0",
+        "pathe": "^2.0.3",
+        "pkg-types": "^1.3.1",
+        "ufo": "^1.6.1"
+      }
+    },
+    "node_modules/mlly/node_modules/confbox": {
+      "version": "0.1.8",
+      "resolved": "https://registry.npmjs.org/confbox/-/confbox-0.1.8.tgz",
+      "integrity": "sha512-RMtmw0iFkeR4YV+fUOSucriAQNb9g8zFR52MWCtl+cCZOFRNL6zeB395vPzFhEjjn4fMxXudmELnl/KF/WrK6w==",
+      "license": "MIT"
+    },
+    "node_modules/mlly/node_modules/pkg-types": {
+      "version": "1.3.1",
+      "resolved": "https://registry.npmjs.org/pkg-types/-/pkg-types-1.3.1.tgz",
+      "integrity": "sha512-/Jm5M4RvtBFVkKWRu2BLUTNP8/M2a+UwuAX+ae4770q1qVGtfjG+WTCupoZixokjmHiry8uI+dlY8KXYV5HVVQ==",
+      "license": "MIT",
+      "dependencies": {
+        "confbox": "^0.1.8",
+        "mlly": "^1.7.4",
+        "pathe": "^2.0.1"
+      }
+    },
+    "node_modules/mrmime": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/mrmime/-/mrmime-2.0.1.tgz",
+      "integrity": "sha512-Y3wQdFg2Va6etvQ5I82yUhGdsKrcYox6p7FfL1LbK2J4V01F9TGlepTIhnK24t7koZibmg82KGglhA1XK5IsLQ==",
+      "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=10"
+      }
+    },
+    "node_modules/ms": {
+      "version": "2.1.3",
+      "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.3.tgz",
+      "integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==",
+      "license": "MIT"
+    },
+    "node_modules/nano-spawn": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/nano-spawn/-/nano-spawn-2.0.0.tgz",
+      "integrity": "sha512-tacvGzUY5o2D8CBh2rrwxyNojUsZNU2zjNTzKQrkgGJQTbGAfArVWXSKMBokBeeg6C7OLRGUEyoFlYbfeWQIqw==",
+      "dev": true,
+      "license": "MIT",
+      "engines": {
+        "node": ">=20.17"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/sindresorhus/nano-spawn?sponsor=1"
       }
     },
-    "node_modules/es-define-property": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/es-define-property/-/es-define-property-1.0.1.tgz",
-      "integrity": "sha512-e3nRfgfUZ4rNGL232gUgX06QNyyez04KdjFrF+LTRoOXmrOgFKDg4BCdsjW8EnT69eqdYGmRpJwiPVYNrCaW3g==",
-      "dev": true,
+    "node_modules/nanoid": {
+      "version": "3.3.11",
+      "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.11.tgz",
+      "integrity": "sha512-N8SpfPUnUp1bK+PMYW8qSWdl9U+wwNWI4QKxOYDy9JAro3WMX7p2OeVRF9v+347pnakNevPmiHhNmZ2HbFA76w==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
       "license": "MIT",
+      "bin": {
+        "nanoid": "bin/nanoid.cjs"
+      },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^10 || ^12 || ^13.7 || ^14 || >=15.0.1"
       }
     },
-    "node_modules/es-errors": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/es-errors/-/es-errors-1.3.0.tgz",
-      "integrity": "sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==",
+    "node_modules/natural-compare": {
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
+      "integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==",
       "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/neotraverse": {
+      "version": "0.6.18",
+      "resolved": "https://registry.npmjs.org/neotraverse/-/neotraverse-0.6.18.tgz",
+      "integrity": "sha512-Z4SmBUweYa09+o6pG+eASabEpP6QkQ70yHj351pQoEXIs8uHbaU2DWVmzBANKgflPa47A50PtB2+NgRpQvr7vA==",
       "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">= 10"
       }
     },
-    "node_modules/es-object-atoms": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/es-object-atoms/-/es-object-atoms-1.1.1.tgz",
-      "integrity": "sha512-FGgH2h8zKNim9ljj7dankFPcICIK9Cp5bm+c2gQSYePhpaG5+esrLODihIorn+Pe6FGJzWhXQotPv73jTaldXA==",
-      "dev": true,
+    "node_modules/nlcst-to-string": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/nlcst-to-string/-/nlcst-to-string-4.0.0.tgz",
+      "integrity": "sha512-YKLBCcUYKAg0FNlOBT6aI91qFmSiFKiluk655WzPF+DDMA02qIyy8uiRqI8QXtcFpEvll12LpL5MXqEmAZ+dcA==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0"
+        "@types/nlcst": "^2.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/es-set-tostringtag": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/es-set-tostringtag/-/es-set-tostringtag-2.1.0.tgz",
-      "integrity": "sha512-j6vWzfrGVfyXxge+O0x5sh6cvxAog0a/4Rdd2K36zCMV5eJ+/+tOAngRO8cODMNWbVRdVlmGZQL2YS3yR8bIUA==",
+    "node_modules/no-case": {
+      "version": "3.0.4",
+      "resolved": "https://registry.npmjs.org/no-case/-/no-case-3.0.4.tgz",
+      "integrity": "sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==",
       "dev": true,
+      "dependencies": {
+        "lower-case": "^2.0.2",
+        "tslib": "^2.0.3"
+      }
+    },
+    "node_modules/node-fetch-native": {
+      "version": "1.6.7",
+      "resolved": "https://registry.npmjs.org/node-fetch-native/-/node-fetch-native-1.6.7.tgz",
+      "integrity": "sha512-g9yhqoedzIUm0nTnTqAQvueMPVOuIY16bqgAJJC8XOOubYFNwz6IER9qs0Gq2Xd0+CecCKFjtdDTMA4u4xG06Q==",
+      "license": "MIT"
+    },
+    "node_modules/node-mock-http": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/node-mock-http/-/node-mock-http-1.0.4.tgz",
+      "integrity": "sha512-8DY+kFsDkNXy1sJglUfuODx1/opAGJGyrTuFqEoN90oRc2Vk0ZbD4K2qmKXBBEhZQzdKHIVfEJpDU8Ak2NJEvQ==",
+      "license": "MIT"
+    },
+    "node_modules/node-releases": {
+      "version": "2.0.36",
+      "resolved": "https://registry.npmjs.org/node-releases/-/node-releases-2.0.36.tgz",
+      "integrity": "sha512-TdC8FSgHz8Mwtw9g5L4gR/Sh9XhSP/0DEkQxfEFXOpiul5IiHgHan2VhYYb6agDSfp4KuvltmGApc8HMgUrIkA=="
+    },
+    "node_modules/normalize-path": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/normalize-path/-/normalize-path-3.0.0.tgz",
+      "integrity": "sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==",
       "license": "MIT",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/nth-check": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.1.1.tgz",
+      "integrity": "sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==",
+      "license": "BSD-2-Clause",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "get-intrinsic": "^1.2.6",
-        "has-tostringtag": "^1.0.2",
-        "hasown": "^2.0.2"
+        "boolbase": "^1.0.0"
       },
+      "funding": {
+        "url": "https://github.com/fb55/nth-check?sponsor=1"
+      }
+    },
+    "node_modules/object-inspect": {
+      "version": "1.13.4",
+      "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.4.tgz",
+      "integrity": "sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==",
+      "dev": true,
+      "license": "MIT",
       "engines": {
         "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/es-shim-unscopables": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/es-shim-unscopables/-/es-shim-unscopables-1.1.0.tgz",
-      "integrity": "sha512-d9T8ucsEhh8Bi1woXCf+TIKDIROLG5WCkxg8geBCbvk22kzwC5G2OnXVMO6FUsvQlgUUXQ2itephWDLqDzbeCw==",
+    "node_modules/object-keys": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
+      "integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "hasown": "^2.0.2"
-      },
       "engines": {
         "node": ">= 0.4"
       }
     },
-    "node_modules/es-to-primitive": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/es-to-primitive/-/es-to-primitive-1.3.0.tgz",
-      "integrity": "sha512-w+5mJ3GuFL+NjVtJlvydShqE1eN3h3PbI7/5LAsYJP/2qtuMXjfL2LpHSRqo4b4eSF5K/DH1JXKUAHSB2UW50g==",
+    "node_modules/object.assign": {
+      "version": "4.1.7",
+      "resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.7.tgz",
+      "integrity": "sha512-nK28WOo+QIjBkDduTINE4JkF/UJJKyf2EJxvJKfblDpyg0Q+pkOHNTL0Qwy6NP6FhE/EnzV73BxxqcJaXY9anw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "is-callable": "^1.2.7",
-        "is-date-object": "^1.0.5",
-        "is-symbol": "^1.0.4"
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.3",
+        "define-properties": "^1.2.1",
+        "es-object-atoms": "^1.0.0",
+        "has-symbols": "^1.1.0",
+        "object-keys": "^1.1.1"
       },
       "engines": {
         "node": ">= 0.4"
@@ -896,716 +9005,917 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/escape-string-regexp": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/escape-string-regexp/-/escape-string-regexp-4.0.0.tgz",
-      "integrity": "sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==",
+    "node_modules/object.fromentries": {
+      "version": "2.0.8",
+      "resolved": "https://registry.npmjs.org/object.fromentries/-/object.fromentries-2.0.8.tgz",
+      "integrity": "sha512-k6E21FzySsSK5a21KRADBd/NGneRegFO5pLHfdQLpRDETUNJueLXs3WCzyQ3tFRDYgbq3KHGXfTbi2bs8WQ6rQ==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.7",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.2",
+        "es-object-atoms": "^1.0.0"
+      },
       "engines": {
-        "node": ">=10"
+        "node": ">= 0.4"
       },
       "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/eslint": {
-      "version": "8.57.0",
-      "resolved": "https://registry.npmjs.org/eslint/-/eslint-8.57.0.tgz",
-      "integrity": "sha512-dZ6+mexnaTIbSBZWgou51U6OmzIhYM2VcNdtiTtI7qPNZm35Akpr0f6vtw3w1Kmn5PYo+tZVfh13WrhpS6oLqQ==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "@eslint-community/eslint-utils": "^4.2.0",
-        "@eslint-community/regexpp": "^4.6.1",
-        "@eslint/eslintrc": "^2.1.4",
-        "@eslint/js": "8.57.0",
-        "@humanwhocodes/config-array": "^0.11.14",
-        "@humanwhocodes/module-importer": "^1.0.1",
-        "@nodelib/fs.walk": "^1.2.8",
-        "@ungap/structured-clone": "^1.2.0",
-        "ajv": "^6.12.4",
-        "chalk": "^4.0.0",
-        "cross-spawn": "^7.0.2",
-        "debug": "^4.3.2",
-        "doctrine": "^3.0.0",
-        "escape-string-regexp": "^4.0.0",
-        "eslint-scope": "^7.2.2",
-        "eslint-visitor-keys": "^3.4.3",
-        "espree": "^9.6.1",
-        "esquery": "^1.4.2",
-        "esutils": "^2.0.2",
-        "fast-deep-equal": "^3.1.3",
-        "file-entry-cache": "^6.0.1",
-        "find-up": "^5.0.0",
-        "glob-parent": "^6.0.2",
-        "globals": "^13.19.0",
-        "graphemer": "^1.4.0",
-        "ignore": "^5.2.0",
-        "imurmurhash": "^0.1.4",
-        "is-glob": "^4.0.0",
-        "is-path-inside": "^3.0.3",
-        "js-yaml": "^4.1.0",
-        "json-stable-stringify-without-jsonify": "^1.0.1",
-        "levn": "^0.4.1",
-        "lodash.merge": "^4.6.2",
-        "minimatch": "^3.1.2",
-        "natural-compare": "^1.4.0",
-        "optionator": "^0.9.3",
-        "strip-ansi": "^6.0.1",
-        "text-table": "^0.2.0"
-      },
-      "bin": {
-        "eslint": "bin/eslint.js"
+    "node_modules/object.values": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/object.values/-/object.values-1.2.1.tgz",
+      "integrity": "sha512-gXah6aZrcUxjWg2zR2MwouP2eHlCBzdV4pygudehaKXSGW4v2AsRQUK+lwwXhii6KFZcunEnmSUoYp5CXibxtA==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.3",
+        "define-properties": "^1.2.1",
+        "es-object-atoms": "^1.0.0"
       },
       "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+        "node": ">= 0.4"
       },
       "funding": {
-        "url": "https://opencollective.com/eslint"
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/eslint-config-standard": {
-      "version": "17.1.0",
-      "resolved": "https://registry.npmjs.org/eslint-config-standard/-/eslint-config-standard-17.1.0.tgz",
-      "integrity": "sha512-IwHwmaBNtDK4zDHQukFDW5u/aTb8+meQWZvNFWkiGmbWjD6bqyuSSBxxXKkCftCUzc1zwCH2m/baCNDLGmuO5Q==",
-      "dev": true,
+    "node_modules/obug": {
+      "version": "2.1.1",
+      "resolved": "https://registry.npmjs.org/obug/-/obug-2.1.1.tgz",
+      "integrity": "sha512-uTqF9MuPraAQ+IsnPf366RG4cP9RtUi7MLO1N3KEc+wb0a6yKpeL0lmk2IB1jY5KHPAlTc6T/JRdC/YqxHNwkQ==",
       "funding": [
-        {
-          "type": "github",
-          "url": "https://github.com/sponsors/feross"
-        },
-        {
-          "type": "patreon",
-          "url": "https://www.patreon.com/feross"
-        },
-        {
-          "type": "consulting",
-          "url": "https://feross.org/support"
-        }
-      ],
+        "https://github.com/sponsors/sxzz",
+        "https://opencollective.com/debug"
+      ]
+    },
+    "node_modules/ofetch": {
+      "version": "1.5.1",
+      "resolved": "https://registry.npmjs.org/ofetch/-/ofetch-1.5.1.tgz",
+      "integrity": "sha512-2W4oUZlVaqAPAil6FUg/difl6YhqhUR7x2eZY4bQCko22UXg3hptq9KLQdqFClV+Wu85UX7hNtdGTngi/1BxcA==",
+      "license": "MIT",
+      "dependencies": {
+        "destr": "^2.0.5",
+        "node-fetch-native": "^1.6.7",
+        "ufo": "^1.6.1"
+      }
+    },
+    "node_modules/ohash": {
+      "version": "2.0.11",
+      "resolved": "https://registry.npmjs.org/ohash/-/ohash-2.0.11.tgz",
+      "integrity": "sha512-RdR9FQrFwNBNXAr4GixM8YaRZRJ5PUWbKYbE5eOsrwAjJW0q2REGcf79oYPsLyskQCZG1PLN+S/K1V00joZAoQ==",
+      "license": "MIT"
+    },
+    "node_modules/once": {
+      "version": "1.4.0",
+      "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
+      "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
+      "license": "ISC",
+      "dependencies": {
+        "wrappy": "1"
+      }
+    },
+    "node_modules/onetime": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/onetime/-/onetime-7.0.0.tgz",
+      "integrity": "sha512-VXJjc87FScF88uafS3JllDgvAm+c/Slfz06lorj2uAY34rlUu0Nt+v8wreiImcrgAjjIHp1rXpTDlLOGw29WwQ==",
+      "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "mimic-function": "^5.0.0"
+      },
       "engines": {
-        "node": ">=12.0.0"
+        "node": ">=18"
       },
-      "peerDependencies": {
-        "eslint": "^8.0.1",
-        "eslint-plugin-import": "^2.25.2",
-        "eslint-plugin-n": "^15.0.0 || ^16.0.0 ",
-        "eslint-plugin-promise": "^6.0.0"
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-import-resolver-node": {
-      "version": "0.3.9",
-      "resolved": "https://registry.npmjs.org/eslint-import-resolver-node/-/eslint-import-resolver-node-0.3.9.tgz",
-      "integrity": "sha512-WFj2isz22JahUv+B788TlO3N6zL3nNJGU8CcZbPZvVEkBPaJdCV4vy5wyghty5ROFbCRnm132v8BScu5/1BQ8g==",
-      "dev": true,
+    "node_modules/oniguruma-parser": {
+      "version": "0.12.1",
+      "resolved": "https://registry.npmjs.org/oniguruma-parser/-/oniguruma-parser-0.12.1.tgz",
+      "integrity": "sha512-8Unqkvk1RYc6yq2WBYRj4hdnsAxVze8i7iPfQr8e4uSP3tRv0rpZcbGUDvxfQQcdwHt/e9PrMvGCsa8OqG9X3w==",
+      "license": "MIT"
+    },
+    "node_modules/oniguruma-to-es": {
+      "version": "4.3.4",
+      "resolved": "https://registry.npmjs.org/oniguruma-to-es/-/oniguruma-to-es-4.3.4.tgz",
+      "integrity": "sha512-3VhUGN3w2eYxnTzHn+ikMI+fp/96KoRSVK9/kMTcFqj1NRDh2IhQCKvYxDnWePKRXY/AqH+Fuiyb7VHSzBjHfA==",
       "license": "MIT",
       "dependencies": {
-        "debug": "^3.2.7",
-        "is-core-module": "^2.13.0",
-        "resolve": "^1.22.4"
+        "oniguruma-parser": "^0.12.1",
+        "regex": "^6.0.1",
+        "regex-recursion": "^6.0.2"
       }
     },
-    "node_modules/eslint-import-resolver-node/node_modules/debug": {
-      "version": "3.2.7",
-      "resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
-      "integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
+    "node_modules/optionator": {
+      "version": "0.9.4",
+      "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.4.tgz",
+      "integrity": "sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "ms": "^2.1.1"
+        "deep-is": "^0.1.3",
+        "fast-levenshtein": "^2.0.6",
+        "levn": "^0.4.1",
+        "prelude-ls": "^1.2.1",
+        "type-check": "^0.4.0",
+        "word-wrap": "^1.2.5"
+      },
+      "engines": {
+        "node": ">= 0.8.0"
       }
     },
-    "node_modules/eslint-module-utils": {
-      "version": "2.12.1",
-      "resolved": "https://registry.npmjs.org/eslint-module-utils/-/eslint-module-utils-2.12.1.tgz",
-      "integrity": "sha512-L8jSWTze7K2mTg0vos/RuLRS5soomksDPoJLXIslC7c8Wmut3bx7CPpJijDcBZtxQ5lrbUdM+s0OlNbz0DCDNw==",
+    "node_modules/own-keys": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/own-keys/-/own-keys-1.0.1.tgz",
+      "integrity": "sha512-qFOyK5PjiWZd+QQIh+1jhdb9LpxTF0qs7Pm8o5QHYZ0M3vKqSqzsZaEB6oWlxZ+q2sJBMI/Ktgd2N5ZwQoRHfg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "debug": "^3.2.7"
+        "get-intrinsic": "^1.2.6",
+        "object-keys": "^1.1.1",
+        "safe-push-apply": "^1.0.0"
       },
       "engines": {
-        "node": ">=4"
+        "node": ">= 0.4"
       },
-      "peerDependenciesMeta": {
-        "eslint": {
-          "optional": true
-        }
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/eslint-module-utils/node_modules/debug": {
-      "version": "3.2.7",
-      "resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
-      "integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
-      "dev": true,
+    "node_modules/p-limit": {
+      "version": "7.3.0",
+      "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-7.3.0.tgz",
+      "integrity": "sha512-7cIXg/Z0M5WZRblrsOla88S4wAK+zOQQWeBYfV3qJuJXMr+LnbYjaadrFaS0JILfEDPVqHyKnZ1Z/1d6J9VVUw==",
       "license": "MIT",
       "dependencies": {
-        "ms": "^2.1.1"
+        "yocto-queue": "^1.2.1"
+      },
+      "engines": {
+        "node": ">=20"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-es": {
-      "version": "4.1.0",
-      "resolved": "https://registry.npmjs.org/eslint-plugin-es/-/eslint-plugin-es-4.1.0.tgz",
-      "integrity": "sha512-GILhQTnjYE2WorX5Jyi5i4dz5ALWxBIdQECVQavL6s7cI76IZTDWleTHkxz/QT3kvcs2QlGHvKLYsSlPOlPXnQ==",
+    "node_modules/p-locate": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
+      "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "eslint-utils": "^2.0.0",
-        "regexpp": "^3.0.0"
+        "p-limit": "^3.0.2"
       },
       "engines": {
-        "node": ">=8.10.0"
+        "node": ">=10"
       },
       "funding": {
-        "url": "https://github.com/sponsors/mysticatea"
-      },
-      "peerDependencies": {
-        "eslint": ">=4.19.1"
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-es/node_modules/eslint-utils": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-2.1.0.tgz",
-      "integrity": "sha512-w94dQYoauyvlDc43XnGB8lU3Zt713vNChgt4EWwhXAP2XkBvndfxF0AgIqKOOasjPIPzj9JqgwkwbCYD0/V3Zg==",
+    "node_modules/p-locate/node_modules/p-limit": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
+      "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "eslint-visitor-keys": "^1.1.0"
+        "yocto-queue": "^0.1.0"
       },
       "engines": {
-        "node": ">=6"
+        "node": ">=10"
       },
       "funding": {
-        "url": "https://github.com/sponsors/mysticatea"
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-es/node_modules/eslint-visitor-keys": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-1.3.0.tgz",
-      "integrity": "sha512-6J72N8UNa462wa/KFODt/PJ3IU60SDpC3QXC1Hjc1BXXpfL2C9R5+AU7jhe0F6GREqVMh4Juu+NY7xn+6dipUQ==",
+    "node_modules/p-locate/node_modules/yocto-queue": {
+      "version": "0.1.0",
+      "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
+      "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==",
       "dev": true,
-      "license": "Apache-2.0",
+      "license": "MIT",
       "engines": {
-        "node": ">=4"
+        "node": ">=10"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-import": {
-      "version": "2.32.0",
-      "resolved": "https://registry.npmjs.org/eslint-plugin-import/-/eslint-plugin-import-2.32.0.tgz",
-      "integrity": "sha512-whOE1HFo/qJDyX4SnXzP4N6zOWn79WhnCUY/iDR0mPfQZO8wcYE4JClzI2oZrhBnnMUCBCHZhO6VQyoBU95mZA==",
-      "dev": true,
+    "node_modules/p-queue": {
+      "version": "9.1.0",
+      "resolved": "https://registry.npmjs.org/p-queue/-/p-queue-9.1.0.tgz",
+      "integrity": "sha512-O/ZPaXuQV29uSLbxWBGGZO1mCQXV2BLIwUr59JUU9SoH76mnYvtms7aafH/isNSNGwuEfP6W/4xD0/TJXxrizw==",
       "license": "MIT",
       "dependencies": {
-        "@rtsao/scc": "^1.1.0",
-        "array-includes": "^3.1.9",
-        "array.prototype.findlastindex": "^1.2.6",
-        "array.prototype.flat": "^1.3.3",
-        "array.prototype.flatmap": "^1.3.3",
-        "debug": "^3.2.7",
-        "doctrine": "^2.1.0",
-        "eslint-import-resolver-node": "^0.3.9",
-        "eslint-module-utils": "^2.12.1",
-        "hasown": "^2.0.2",
-        "is-core-module": "^2.16.1",
-        "is-glob": "^4.0.3",
-        "minimatch": "^3.1.2",
-        "object.fromentries": "^2.0.8",
-        "object.groupby": "^1.0.3",
-        "object.values": "^1.2.1",
-        "semver": "^6.3.1",
-        "string.prototype.trimend": "^1.0.9",
-        "tsconfig-paths": "^3.15.0"
+        "eventemitter3": "^5.0.1",
+        "p-timeout": "^7.0.0"
       },
       "engines": {
-        "node": ">=4"
+        "node": ">=20"
       },
-      "peerDependencies": {
-        "eslint": "^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9"
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-import/node_modules/debug": {
-      "version": "3.2.7",
-      "resolved": "https://registry.npmjs.org/debug/-/debug-3.2.7.tgz",
-      "integrity": "sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==",
-      "dev": true,
+    "node_modules/p-timeout": {
+      "version": "7.0.1",
+      "resolved": "https://registry.npmjs.org/p-timeout/-/p-timeout-7.0.1.tgz",
+      "integrity": "sha512-AxTM2wDGORHGEkPCt8yqxOTMgpfbEHqF51f/5fJCmwFC3C/zNcGT63SymH2ttOAaiIws2zVg4+izQCjrakcwHg==",
       "license": "MIT",
-      "dependencies": {
-        "ms": "^2.1.1"
+      "engines": {
+        "node": ">=20"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-import/node_modules/doctrine": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/doctrine/-/doctrine-2.1.0.tgz",
-      "integrity": "sha512-35mSku4ZXK0vfCuHEDAwt55dg2jNajHZ1odvF+8SSr82EsZY4QmXfuWso8oEd8zRhVObSN18aM0CjSdoBX7zIw==",
+    "node_modules/package-manager-detector": {
+      "version": "1.6.0",
+      "resolved": "https://registry.npmjs.org/package-manager-detector/-/package-manager-detector-1.6.0.tgz",
+      "integrity": "sha512-61A5ThoTiDG/C8s8UMZwSorAGwMJ0ERVGj2OjoW5pAalsNOg15+iQiPzrLJ4jhZ1HJzmC2PIHT2oEiH3R5fzNA==",
+      "license": "MIT"
+    },
+    "node_modules/pako": {
+      "version": "0.2.9",
+      "resolved": "https://registry.npmjs.org/pako/-/pako-0.2.9.tgz",
+      "integrity": "sha512-NUcwaKxUxWrZLpDG+z/xZaCgQITkA/Dv4V/T6bw7VON6l1Xz/VnrBqrYjZQ12TamKHzITTfOEIYUj48y2KXImA==",
+      "license": "MIT"
+    },
+    "node_modules/parent-module": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
+      "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
       "dev": true,
-      "license": "Apache-2.0",
+      "license": "MIT",
       "dependencies": {
-        "esutils": "^2.0.2"
+        "callsites": "^3.0.0"
       },
       "engines": {
-        "node": ">=0.10.0"
+        "node": ">=6"
       }
     },
-    "node_modules/eslint-plugin-markdown": {
-      "version": "2.2.1",
-      "resolved": "https://registry.npmjs.org/eslint-plugin-markdown/-/eslint-plugin-markdown-2.2.1.tgz",
-      "integrity": "sha512-FgWp4iyYvTFxPwfbxofTvXxgzPsDuSKHQy2S+a8Ve6savbujey+lgrFFbXQA0HPygISpRYWYBjooPzhYSF81iA==",
-      "dev": true,
+    "node_modules/parse-css-color": {
+      "version": "0.2.1",
+      "resolved": "https://registry.npmjs.org/parse-css-color/-/parse-css-color-0.2.1.tgz",
+      "integrity": "sha512-bwS/GGIFV3b6KS4uwpzCFj4w297Yl3uqnSgIPsoQkx7GMLROXfMnWvxfNkL0oh8HVhZA4hvJoEoEIqonfJ3BWg==",
       "license": "MIT",
       "dependencies": {
-        "mdast-util-from-markdown": "^0.8.5"
-      },
-      "engines": {
-        "node": "^8.10.0 || ^10.12.0 || >= 12.0.0"
-      },
-      "peerDependencies": {
-        "eslint": ">=6.0.0"
+        "color-name": "^1.1.4",
+        "hex-rgb": "^4.1.0"
       }
     },
-    "node_modules/eslint-plugin-n": {
-      "version": "15.7.0",
-      "resolved": "https://registry.npmjs.org/eslint-plugin-n/-/eslint-plugin-n-15.7.0.tgz",
-      "integrity": "sha512-jDex9s7D/Qial8AGVIHq4W7NswpUD5DPDL2RH8Lzd9EloWUuvUkHfv4FRLMipH5q2UtyurorBkPeNi1wVWNh3Q==",
-      "dev": true,
+    "node_modules/parse-entities": {
+      "version": "4.0.2",
+      "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-4.0.2.tgz",
+      "integrity": "sha512-GG2AQYWoLgL877gQIKeRPGO1xF9+eG1ujIb5soS5gPvLQ1y2o8FL90w2QWNdf9I361Mpp7726c+lj3U0qK1uGw==",
       "license": "MIT",
       "dependencies": {
-        "builtins": "^5.0.1",
-        "eslint-plugin-es": "^4.1.0",
-        "eslint-utils": "^3.0.0",
-        "ignore": "^5.1.1",
-        "is-core-module": "^2.11.0",
-        "minimatch": "^3.1.2",
-        "resolve": "^1.22.1",
-        "semver": "^7.3.8"
-      },
-      "engines": {
-        "node": ">=12.22.0"
+        "@types/unist": "^2.0.0",
+        "character-entities-legacy": "^3.0.0",
+        "character-reference-invalid": "^2.0.0",
+        "decode-named-character-reference": "^1.0.0",
+        "is-alphanumerical": "^2.0.0",
+        "is-decimal": "^2.0.0",
+        "is-hexadecimal": "^2.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/mysticatea"
-      },
-      "peerDependencies": {
-        "eslint": ">=7.0.0"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/eslint-plugin-n/node_modules/semver": {
-      "version": "7.6.2",
-      "resolved": "https://registry.npmjs.org/semver/-/semver-7.6.2.tgz",
-      "integrity": "sha512-FNAIBWCx9qcRhoHcgcJ0gvU7SN1lYU2ZXuSfl04bSC5OpvDHFyJCjdNHomPXxjQlCBU67YW64PzY7/VIEH7F2w==",
+    "node_modules/parse-entities/node_modules/@types/unist": {
+      "version": "2.0.11",
+      "resolved": "https://registry.npmjs.org/@types/unist/-/unist-2.0.11.tgz",
+      "integrity": "sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==",
+      "license": "MIT"
+    },
+    "node_modules/parse-json": {
+      "version": "5.2.0",
+      "resolved": "https://registry.npmjs.org/parse-json/-/parse-json-5.2.0.tgz",
+      "integrity": "sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==",
       "dev": true,
-      "license": "ISC",
-      "bin": {
-        "semver": "bin/semver.js"
+      "dependencies": {
+        "@babel/code-frame": "^7.0.0",
+        "error-ex": "^1.3.1",
+        "json-parse-even-better-errors": "^2.3.0",
+        "lines-and-columns": "^1.1.6"
       },
       "engines": {
-        "node": ">=10"
+        "node": ">=8"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/eslint-plugin-promise": {
-      "version": "6.6.0",
-      "resolved": "https://registry.npmjs.org/eslint-plugin-promise/-/eslint-plugin-promise-6.6.0.tgz",
-      "integrity": "sha512-57Zzfw8G6+Gq7axm2Pdo3gW/Rx3h9Yywgn61uE/3elTCOePEHVrn2i5CdfBwA1BLK0Q0WqctICIUSqXZW/VprQ==",
-      "dev": true,
-      "license": "ISC",
-      "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+    "node_modules/parse-latin": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/parse-latin/-/parse-latin-7.0.0.tgz",
+      "integrity": "sha512-mhHgobPPua5kZ98EF4HWiH167JWBfl4pvAIXXdbaVohtK7a6YBOy56kvhCqduqyo/f3yrHFWmqmiMg/BkBkYYQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/nlcst": "^2.0.0",
+        "@types/unist": "^3.0.0",
+        "nlcst-to-string": "^4.0.0",
+        "unist-util-modify-children": "^4.0.0",
+        "unist-util-visit-children": "^3.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "url": "https://opencollective.com/eslint"
-      },
-      "peerDependencies": {
-        "eslint": "^7.0.0 || ^8.0.0 || ^9.0.0"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/eslint-scope": {
-      "version": "7.2.2",
-      "resolved": "https://registry.npmjs.org/eslint-scope/-/eslint-scope-7.2.2.tgz",
-      "integrity": "sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==",
-      "dev": true,
-      "license": "BSD-2-Clause",
+    "node_modules/parse5": {
+      "version": "7.3.0",
+      "resolved": "https://registry.npmjs.org/parse5/-/parse5-7.3.0.tgz",
+      "integrity": "sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==",
+      "license": "MIT",
       "dependencies": {
-        "esrecurse": "^4.3.0",
-        "estraverse": "^5.2.0"
-      },
-      "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+        "entities": "^6.0.0"
       },
       "funding": {
-        "url": "https://opencollective.com/eslint"
+        "url": "https://github.com/inikulin/parse5?sponsor=1"
       }
     },
-    "node_modules/eslint-utils": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz",
-      "integrity": "sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==",
-      "dev": true,
+    "node_modules/parse5-htmlparser2-tree-adapter": {
+      "version": "7.1.0",
+      "resolved": "https://registry.npmjs.org/parse5-htmlparser2-tree-adapter/-/parse5-htmlparser2-tree-adapter-7.1.0.tgz",
+      "integrity": "sha512-ruw5xyKs6lrpo9x9rCZqZZnIUntICjQAd0Wsmp396Ul9lN/h+ifgVV1x1gZHi8euej6wTfpqX8j+BFQxF0NS/g==",
       "license": "MIT",
       "dependencies": {
-        "eslint-visitor-keys": "^2.0.0"
-      },
-      "engines": {
-        "node": "^10.0.0 || ^12.0.0 || >= 14.0.0"
+        "domhandler": "^5.0.3",
+        "parse5": "^7.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/mysticatea"
+        "url": "https://github.com/inikulin/parse5?sponsor=1"
+      }
+    },
+    "node_modules/parse5-parser-stream": {
+      "version": "7.1.2",
+      "resolved": "https://registry.npmjs.org/parse5-parser-stream/-/parse5-parser-stream-7.1.2.tgz",
+      "integrity": "sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow==",
+      "license": "MIT",
+      "dependencies": {
+        "parse5": "^7.0.0"
       },
-      "peerDependencies": {
-        "eslint": ">=5"
+      "funding": {
+        "url": "https://github.com/inikulin/parse5?sponsor=1"
       }
     },
-    "node_modules/eslint-utils/node_modules/eslint-visitor-keys": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-2.1.0.tgz",
-      "integrity": "sha512-0rSmRBzXgDzIsD6mGdJgevzgezI534Cer5L/vyMX0kHzT/jiB43jRhd9YUlMGYLQy2zprNmoT8qasCGtY+QaKw==",
+    "node_modules/path-exists": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
+      "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
       "dev": true,
-      "license": "Apache-2.0",
+      "license": "MIT",
       "engines": {
-        "node": ">=10"
+        "node": ">=8"
       }
     },
-    "node_modules/eslint-visitor-keys": {
-      "version": "3.4.3",
-      "resolved": "https://registry.npmjs.org/eslint-visitor-keys/-/eslint-visitor-keys-3.4.3.tgz",
-      "integrity": "sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==",
+    "node_modules/path-expression-matcher": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/path-expression-matcher/-/path-expression-matcher-1.2.0.tgz",
+      "integrity": "sha512-DwmPWeFn+tq7TiyJ2CxezCAirXjFxvaiD03npak3cRjlP9+OjTmSy1EpIrEbh+l6JgUundniloMLDQ/6VTdhLQ==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/NaturalIntelligence"
+        }
+      ],
+      "license": "MIT",
+      "engines": {
+        "node": ">=14.0.0"
+      }
+    },
+    "node_modules/path-key": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
+      "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
       "dev": true,
-      "license": "Apache-2.0",
+      "license": "MIT",
       "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
-      },
-      "funding": {
-        "url": "https://opencollective.com/eslint"
+        "node": ">=8"
       }
     },
-    "node_modules/espree": {
-      "version": "9.6.1",
-      "resolved": "https://registry.npmjs.org/espree/-/espree-9.6.1.tgz",
-      "integrity": "sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==",
+    "node_modules/path-type": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/path-type/-/path-type-4.0.0.tgz",
+      "integrity": "sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==",
       "dev": true,
-      "license": "BSD-2-Clause",
-      "dependencies": {
-        "acorn": "^8.9.0",
-        "acorn-jsx": "^5.3.2",
-        "eslint-visitor-keys": "^3.4.1"
-      },
       "engines": {
-        "node": "^12.22.0 || ^14.17.0 || >=16.0.0"
+        "node": ">=8"
+      }
+    },
+    "node_modules/pathe": {
+      "version": "2.0.3",
+      "resolved": "https://registry.npmjs.org/pathe/-/pathe-2.0.3.tgz",
+      "integrity": "sha512-WUjGcAqP1gQacoQe+OBJsFA7Ld4DyXuUIjZ5cc75cLHvJ7dtNsTugphxIADwspS+AraAUePCKrSVtPLFj/F88w==",
+      "license": "MIT"
+    },
+    "node_modules/pend": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz",
+      "integrity": "sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==",
+      "license": "MIT"
+    },
+    "node_modules/piccolore": {
+      "version": "0.1.3",
+      "resolved": "https://registry.npmjs.org/piccolore/-/piccolore-0.1.3.tgz",
+      "integrity": "sha512-o8bTeDWjE086iwKrROaDf31K0qC/BENdm15/uH9usSC/uZjJOKb2YGiVHfLY4GhwsERiPI1jmwI2XrA7ACOxVw==",
+      "license": "ISC"
+    },
+    "node_modules/picocolors": {
+      "version": "1.1.1",
+      "resolved": "https://registry.npmjs.org/picocolors/-/picocolors-1.1.1.tgz",
+      "integrity": "sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==",
+      "license": "ISC"
+    },
+    "node_modules/picomatch": {
+      "version": "4.0.3",
+      "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz",
+      "integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=12"
       },
       "funding": {
-        "url": "https://opencollective.com/eslint"
+        "url": "https://github.com/sponsors/jonschlinkert"
       }
     },
-    "node_modules/esquery": {
-      "version": "1.5.0",
-      "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.5.0.tgz",
-      "integrity": "sha512-YQLXUplAwJgCydQ78IMJywZCceoqk1oH01OERdSAJc/7U2AylwjhSCLDEtqwg811idIS/9fIU5GjG73IgjKMVg==",
+    "node_modules/pidtree": {
+      "version": "0.6.0",
+      "resolved": "https://registry.npmjs.org/pidtree/-/pidtree-0.6.0.tgz",
+      "integrity": "sha512-eG2dWTVw5bzqGRztnHExczNxt5VGsE6OwTeCG3fdUf9KBsZzO3R5OIIIzWR+iZA0NtZ+RDVdaoE2dK1cn6jH4g==",
       "dev": true,
-      "license": "BSD-3-Clause",
-      "dependencies": {
-        "estraverse": "^5.1.0"
+      "license": "MIT",
+      "bin": {
+        "pidtree": "bin/pidtree.js"
       },
       "engines": {
         "node": ">=0.10"
       }
     },
-    "node_modules/esrecurse": {
-      "version": "4.3.0",
-      "resolved": "https://registry.npmjs.org/esrecurse/-/esrecurse-4.3.0.tgz",
-      "integrity": "sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==",
+    "node_modules/pkg-types": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/pkg-types/-/pkg-types-2.3.0.tgz",
+      "integrity": "sha512-SIqCzDRg0s9npO5XQ3tNZioRY1uK06lA41ynBC1YmFTmnY6FjUjVt6s4LoADmwoig1qqD0oK8h1p/8mlMx8Oig==",
+      "license": "MIT",
+      "dependencies": {
+        "confbox": "^0.2.2",
+        "exsolve": "^1.0.7",
+        "pathe": "^2.0.3"
+      }
+    },
+    "node_modules/playwright": {
+      "version": "1.59.1",
+      "resolved": "https://registry.npmjs.org/playwright/-/playwright-1.59.1.tgz",
+      "integrity": "sha512-C8oWjPR3F81yljW9o5OxcWzfh6avkVwDD2VYdwIGqTkl+OGFISgypqzfu7dOe4QNLL2aqcWBmI3PMtLIK233lw==",
       "dev": true,
-      "license": "BSD-2-Clause",
+      "license": "Apache-2.0",
       "dependencies": {
-        "estraverse": "^5.2.0"
+        "playwright-core": "1.59.1"
+      },
+      "bin": {
+        "playwright": "cli.js"
       },
       "engines": {
-        "node": ">=4.0"
+        "node": ">=18"
+      },
+      "optionalDependencies": {
+        "fsevents": "2.3.2"
       }
     },
-    "node_modules/estraverse": {
-      "version": "5.3.0",
-      "resolved": "https://registry.npmjs.org/estraverse/-/estraverse-5.3.0.tgz",
-      "integrity": "sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==",
+    "node_modules/playwright-core": {
+      "version": "1.59.1",
+      "resolved": "https://registry.npmjs.org/playwright-core/-/playwright-core-1.59.1.tgz",
+      "integrity": "sha512-HBV/RJg81z5BiiZ9yPzIiClYV/QMsDCKUyogwH9p3MCP6IYjUFu/MActgYAvK0oWyV9NlwM3GLBjADyWgydVyg==",
       "dev": true,
-      "license": "BSD-2-Clause",
+      "license": "Apache-2.0",
+      "bin": {
+        "playwright-core": "cli.js"
+      },
       "engines": {
-        "node": ">=4.0"
+        "node": ">=18"
       }
     },
-    "node_modules/esutils": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/esutils/-/esutils-2.0.3.tgz",
-      "integrity": "sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==",
+    "node_modules/playwright/node_modules/fsevents": {
+      "version": "2.3.2",
+      "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz",
+      "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==",
       "dev": true,
-      "license": "BSD-2-Clause",
+      "hasInstallScript": true,
+      "license": "MIT",
+      "optional": true,
+      "os": [
+        "darwin"
+      ],
       "engines": {
-        "node": ">=0.10.0"
+        "node": "^8.16.0 || ^10.6.0 || >=11.0.0"
       }
     },
-    "node_modules/fast-deep-equal": {
-      "version": "3.1.3",
-      "resolved": "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz",
-      "integrity": "sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/fast-json-stable-stringify": {
-      "version": "2.1.0",
-      "resolved": "https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.1.0.tgz",
-      "integrity": "sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/fast-levenshtein": {
-      "version": "2.0.6",
-      "resolved": "https://registry.npmjs.org/fast-levenshtein/-/fast-levenshtein-2.0.6.tgz",
-      "integrity": "sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==",
+    "node_modules/possible-typed-array-names": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/possible-typed-array-names/-/possible-typed-array-names-1.1.0.tgz",
+      "integrity": "sha512-/+5VFTchJDoVj3bhoqi6UeymcD00DAwb1nJwamzPvHEszJ4FpF6SNNbUbOS8yI56qHzdV8eK0qEfOSiodkTdxg==",
       "dev": true,
-      "license": "MIT"
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.4"
+      }
     },
-    "node_modules/fastq": {
-      "version": "1.17.1",
-      "resolved": "https://registry.npmjs.org/fastq/-/fastq-1.17.1.tgz",
-      "integrity": "sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==",
-      "dev": true,
-      "license": "ISC",
+    "node_modules/postcss": {
+      "version": "8.5.6",
+      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.6.tgz",
+      "integrity": "sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg==",
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/postcss"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
+      "license": "MIT",
+      "peer": true,
       "dependencies": {
-        "reusify": "^1.0.4"
+        "nanoid": "^3.3.11",
+        "picocolors": "^1.1.1",
+        "source-map-js": "^1.2.1"
+      },
+      "engines": {
+        "node": "^10 || ^12 || >=14"
       }
     },
-    "node_modules/file-entry-cache": {
-      "version": "6.0.1",
-      "resolved": "https://registry.npmjs.org/file-entry-cache/-/file-entry-cache-6.0.1.tgz",
-      "integrity": "sha512-7Gps/XWymbLk2QLYK4NzpMOrYjMhdIxXuIvy2QBsLE6ljuodKvdkWs/cpyJJ3CVIVpH0Oi1Hvg1ovbMzLdFBBg==",
+    "node_modules/postcss-custom-media": {
+      "version": "12.0.0",
+      "resolved": "https://registry.npmjs.org/postcss-custom-media/-/postcss-custom-media-12.0.0.tgz",
+      "integrity": "sha512-jIgEvqceN6ru2uQ0f75W1g+JDi0UyECFeJKjPG7UcSkW3+03LDKH2c6h+9C0XuDTV4y2pEHmD5AJtVBq1OGnZA==",
       "dev": true,
-      "license": "MIT",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/csstools"
+        },
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/csstools"
+        }
+      ],
       "dependencies": {
-        "flat-cache": "^3.0.4"
+        "@csstools/cascade-layer-name-parser": "^3.0.0",
+        "@csstools/css-parser-algorithms": "^4.0.0",
+        "@csstools/css-tokenizer": "^4.0.0",
+        "@csstools/media-query-list-parser": "^5.0.0"
       },
       "engines": {
-        "node": "^10.12.0 || >=12.0.0"
+        "node": ">=20.19.0"
+      },
+      "peerDependencies": {
+        "postcss": "^8.4"
       }
     },
-    "node_modules/find-up": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/find-up/-/find-up-5.0.0.tgz",
-      "integrity": "sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==",
+    "node_modules/postcss-nested": {
+      "version": "7.0.2",
+      "resolved": "https://registry.npmjs.org/postcss-nested/-/postcss-nested-7.0.2.tgz",
+      "integrity": "sha512-5osppouFc0VR9/VYzYxO03VaDa3e8F23Kfd6/9qcZTUI8P58GIYlArOET2Wq0ywSl2o2PjELhYOFI4W7l5QHKw==",
       "dev": true,
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/postcss/"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
       "license": "MIT",
       "dependencies": {
-        "locate-path": "^6.0.0",
-        "path-exists": "^4.0.0"
+        "postcss-selector-parser": "^7.0.0"
       },
       "engines": {
-        "node": ">=10"
+        "node": ">=18.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+      "peerDependencies": {
+        "postcss": "^8.2.14"
       }
     },
-    "node_modules/flat-cache": {
-      "version": "3.2.0",
-      "resolved": "https://registry.npmjs.org/flat-cache/-/flat-cache-3.2.0.tgz",
-      "integrity": "sha512-CYcENa+FtcUKLmhhqyctpclsq7QF38pKjZHsGNiSQF5r4FtoKDWabFDl3hzaEQMvT1LHEysw5twgLvpYYb4vbw==",
+    "node_modules/postcss-selector-parser": {
+      "version": "7.1.1",
+      "resolved": "https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-7.1.1.tgz",
+      "integrity": "sha512-orRsuYpJVw8LdAwqqLykBj9ecS5/cRHlI5+nvTo8LcCKmzDmqVORXtOIYEEQuL9D4BxtA1lm5isAqzQZCoQ6Eg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "flatted": "^3.2.9",
-        "keyv": "^4.5.3",
-        "rimraf": "^3.0.2"
+        "cssesc": "^3.0.0",
+        "util-deprecate": "^1.0.2"
       },
       "engines": {
-        "node": "^10.12.0 || >=12.0.0"
+        "node": ">=4"
       }
     },
-    "node_modules/flatted": {
-      "version": "3.3.1",
-      "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.3.1.tgz",
-      "integrity": "sha512-X8cqMLLie7KsNUDSdzeN8FYK9rEt4Dt67OsG/DNGnYTSDBG4uFAJFBnUeiV+zCVAvwFy56IjM9sH51jVaEhNxw==",
+    "node_modules/postcss-value-parser": {
+      "version": "4.2.0",
+      "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.2.0.tgz",
+      "integrity": "sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==",
+      "license": "MIT"
+    },
+    "node_modules/prelude-ls": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
+      "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
       "dev": true,
-      "license": "ISC"
+      "license": "MIT",
+      "engines": {
+        "node": ">= 0.8.0"
+      }
     },
-    "node_modules/for-each": {
-      "version": "0.3.5",
-      "resolved": "https://registry.npmjs.org/for-each/-/for-each-0.3.5.tgz",
-      "integrity": "sha512-dKx12eRCVIzqCxFGplyFKJMPvLEWgmNtUrpTiJIR5u97zEhRG8ySrtboPHZXx7daLxQVrl643cTzbab2tkQjxg==",
+    "node_modules/prettier": {
+      "version": "3.8.1",
+      "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.8.1.tgz",
+      "integrity": "sha512-UOnG6LftzbdaHZcKoPFtOcCKztrQ57WkHDeRD9t/PTQtmT0NHSeWWepj6pS0z/N7+08BHFDQVUrfmfMRcZwbMg==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "is-callable": "^1.2.7"
+      "bin": {
+        "prettier": "bin/prettier.cjs"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=14"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/prettier/prettier?sponsor=1"
       }
     },
-    "node_modules/fs.realpath": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz",
-      "integrity": "sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==",
+    "node_modules/prettier-plugin-astro": {
+      "version": "0.14.1",
+      "resolved": "https://registry.npmjs.org/prettier-plugin-astro/-/prettier-plugin-astro-0.14.1.tgz",
+      "integrity": "sha512-RiBETaaP9veVstE4vUwSIcdATj6dKmXljouXc/DDNwBSPTp8FRkLGDSGFClKsAFeeg+13SB0Z1JZvbD76bigJw==",
       "dev": true,
-      "license": "ISC"
+      "license": "MIT",
+      "dependencies": {
+        "@astrojs/compiler": "^2.9.1",
+        "prettier": "^3.0.0",
+        "sass-formatter": "^0.7.6"
+      },
+      "engines": {
+        "node": "^14.15.0 || >=16.0.0"
+      }
     },
-    "node_modules/function-bind": {
-      "version": "1.1.2",
-      "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.2.tgz",
-      "integrity": "sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==",
-      "dev": true,
+    "node_modules/prism-react-renderer": {
+      "version": "1.3.5",
+      "resolved": "https://registry.npmjs.org/prism-react-renderer/-/prism-react-renderer-1.3.5.tgz",
+      "integrity": "sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg==",
       "license": "MIT",
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "peerDependencies": {
+        "react": ">=0.14.9"
       }
     },
-    "node_modules/function.prototype.name": {
-      "version": "1.1.8",
-      "resolved": "https://registry.npmjs.org/function.prototype.name/-/function.prototype.name-1.1.8.tgz",
-      "integrity": "sha512-e5iwyodOHhbMr/yNrc7fDYG4qlbIvI5gajyzPnb5TCwyhjApznQh1BMFou9b30SevY43gCJKXycoCBjMbsuW0Q==",
-      "dev": true,
+    "node_modules/prismjs": {
+      "version": "1.30.0",
+      "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.30.0.tgz",
+      "integrity": "sha512-DEvV2ZF2r2/63V+tK8hQvrR2ZGn10srHbXviTlcv7Kpzw8jWiNTqbVgjO3IY8RxrrOUF8VPMQQFysYYYv0YZxw==",
       "license": "MIT",
-      "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.3",
-        "define-properties": "^1.2.1",
-        "functions-have-names": "^1.2.3",
-        "hasown": "^2.0.2",
-        "is-callable": "^1.2.7"
-      },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6"
       }
     },
-    "node_modules/functions-have-names": {
-      "version": "1.2.3",
-      "resolved": "https://registry.npmjs.org/functions-have-names/-/functions-have-names-1.2.3.tgz",
-      "integrity": "sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==",
-      "dev": true,
+    "node_modules/property-information": {
+      "version": "7.1.0",
+      "resolved": "https://registry.npmjs.org/property-information/-/property-information-7.1.0.tgz",
+      "integrity": "sha512-TwEZ+X+yCJmYfL7TPUOcvBZ4QfoT5YenQiJuX//0th53DE6w0xxLEtfK3iyryQFddXuvkIk51EEgrJQ0WJkOmQ==",
       "license": "MIT",
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/get-intrinsic": {
-      "version": "1.3.0",
-      "resolved": "https://registry.npmjs.org/get-intrinsic/-/get-intrinsic-1.3.0.tgz",
-      "integrity": "sha512-9fSjSaos/fRIVIp+xSJlE6lfwhES7LNtKaCBIamHsjr2na1BiABJPo0mOjjz8GJDURarmCPGqaiVg5mfjb98CQ==",
-      "dev": true,
+    "node_modules/pump": {
+      "version": "3.0.3",
+      "resolved": "https://registry.npmjs.org/pump/-/pump-3.0.3.tgz",
+      "integrity": "sha512-todwxLMY7/heScKmntwQG8CXVkWUOdYxIvY2s0VWAAMh/nd8SoYiRaKjlr7+iCs984f2P8zvrfWcDDYVb73NfA==",
       "license": "MIT",
       "dependencies": {
-        "call-bind-apply-helpers": "^1.0.2",
-        "es-define-property": "^1.0.1",
-        "es-errors": "^1.3.0",
-        "es-object-atoms": "^1.1.1",
-        "function-bind": "^1.1.2",
-        "get-proto": "^1.0.1",
-        "gopd": "^1.2.0",
-        "has-symbols": "^1.1.0",
-        "hasown": "^2.0.2",
-        "math-intrinsics": "^1.1.0"
-      },
+        "end-of-stream": "^1.1.0",
+        "once": "^1.3.1"
+      }
+    },
+    "node_modules/punycode": {
+      "version": "2.3.1",
+      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz",
+      "integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==",
+      "dev": true,
+      "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=6"
+      }
+    },
+    "node_modules/quansync": {
+      "version": "0.2.11",
+      "resolved": "https://registry.npmjs.org/quansync/-/quansync-0.2.11.tgz",
+      "integrity": "sha512-AifT7QEbW9Nri4tAwR5M/uzpBuqfZf+zwaEM/QkzEjj7NBuFD2rBuy0K3dE+8wltbezDV7JMA0WfnCPYRSYbXA==",
+      "funding": [
+        {
+          "type": "individual",
+          "url": "https://github.com/sponsors/antfu"
+        },
+        {
+          "type": "individual",
+          "url": "https://github.com/sponsors/sxzz"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/queue-microtask": {
+      "version": "1.2.3",
+      "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
+      "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
+      "dev": true,
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/feross"
+        },
+        {
+          "type": "patreon",
+          "url": "https://www.patreon.com/feross"
+        },
+        {
+          "type": "consulting",
+          "url": "https://feross.org/support"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/radix3": {
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/radix3/-/radix3-1.1.2.tgz",
+      "integrity": "sha512-b484I/7b8rDEdSDKckSSBA8knMpcdsXudlE/LNL639wFoHKwLbEkQFZHWEYwDC0wa0FKUcCY+GAF73Z7wxNVFA==",
+      "license": "MIT"
+    },
+    "node_modules/react": {
+      "version": "19.2.4",
+      "resolved": "https://registry.npmjs.org/react/-/react-19.2.4.tgz",
+      "integrity": "sha512-9nfp2hYpCwOjAN+8TZFGhtWEwgvWHXqESH8qT89AT/lWklpLON22Lc8pEtnpsZz7VmawabSU0gCjnj8aC0euHQ==",
+      "peer": true,
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/react-dom": {
+      "version": "19.2.4",
+      "resolved": "https://registry.npmjs.org/react-dom/-/react-dom-19.2.4.tgz",
+      "integrity": "sha512-AXJdLo8kgMbimY95O2aKQqsz2iWi9jMgKJhRBAxECE4IFxfcazB2LmzloIoibJI3C12IlY20+KFaLv+71bUJeQ==",
+      "peer": true,
+      "dependencies": {
+        "scheduler": "^0.27.0"
+      },
+      "peerDependencies": {
+        "react": "^19.2.4"
       }
     },
-    "node_modules/get-proto": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/get-proto/-/get-proto-1.0.1.tgz",
-      "integrity": "sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==",
-      "dev": true,
+    "node_modules/react-markdown": {
+      "version": "10.1.0",
+      "resolved": "https://registry.npmjs.org/react-markdown/-/react-markdown-10.1.0.tgz",
+      "integrity": "sha512-qKxVopLT/TyA6BX3Ue5NwabOsAzm0Q7kAPwq6L+wWDwisYs7R8vZ0nRXqq6rkueboxpkjvLGU9fWifiX/ZZFxQ==",
       "license": "MIT",
       "dependencies": {
-        "dunder-proto": "^1.0.1",
-        "es-object-atoms": "^1.0.0"
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "devlop": "^1.0.0",
+        "hast-util-to-jsx-runtime": "^2.0.0",
+        "html-url-attributes": "^3.0.0",
+        "mdast-util-to-hast": "^13.0.0",
+        "remark-parse": "^11.0.0",
+        "remark-rehype": "^11.0.0",
+        "unified": "^11.0.0",
+        "unist-util-visit": "^5.0.0",
+        "vfile": "^6.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       },
+      "peerDependencies": {
+        "@types/react": ">=18",
+        "react": ">=18"
+      }
+    },
+    "node_modules/react-refresh": {
+      "version": "0.18.0",
+      "resolved": "https://registry.npmjs.org/react-refresh/-/react-refresh-0.18.0.tgz",
+      "integrity": "sha512-QgT5//D3jfjJb6Gsjxv0Slpj23ip+HtOpnNgnb2S5zU3CB26G/IDPGoy4RJB42wzFE46DRsstbW6tKHoKbhAxw==",
+      "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=0.10.0"
       }
     },
-    "node_modules/get-symbol-description": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/get-symbol-description/-/get-symbol-description-1.1.0.tgz",
-      "integrity": "sha512-w9UMqWwJxHNOvoNzSJ2oPF5wvYcvP7jUvYzhp67yEhTi17ZDBBC1z9pTdGuzjD+EFIqLSYRweZjqfiPzQ06Ebg==",
-      "dev": true,
+    "node_modules/readdirp": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/readdirp/-/readdirp-5.0.0.tgz",
+      "integrity": "sha512-9u/XQ1pvrQtYyMpZe7DXKv2p5CNvyVwzUB6uhLAnQwHMSgKMBR62lc7AHljaeteeHXn11XTAaLLUVZYVZyuRBQ==",
       "license": "MIT",
-      "dependencies": {
-        "call-bound": "^1.0.3",
-        "es-errors": "^1.3.0",
-        "get-intrinsic": "^1.2.6"
-      },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">= 20.19.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "individual",
+        "url": "https://paulmillr.com/funding/"
       }
     },
-    "node_modules/glob": {
-      "version": "7.2.3",
-      "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.3.tgz",
-      "integrity": "sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==",
-      "deprecated": "Glob versions prior to v9 are no longer supported",
-      "dev": true,
-      "license": "ISC",
+    "node_modules/recma-build-jsx": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/recma-build-jsx/-/recma-build-jsx-1.0.0.tgz",
+      "integrity": "sha512-8GtdyqaBcDfva+GUKDr3nev3VpKAhup1+RvkMvUxURHpW7QyIvk9F5wz7Vzo06CEMSilw6uArgRqhpiUcWp8ew==",
+      "license": "MIT",
       "dependencies": {
-        "fs.realpath": "^1.0.0",
-        "inflight": "^1.0.4",
-        "inherits": "2",
-        "minimatch": "^3.1.1",
-        "once": "^1.3.0",
-        "path-is-absolute": "^1.0.0"
-      },
-      "engines": {
-        "node": "*"
+        "@types/estree": "^1.0.0",
+        "estree-util-build-jsx": "^3.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/isaacs"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/glob-parent": {
-      "version": "6.0.2",
-      "resolved": "https://registry.npmjs.org/glob-parent/-/glob-parent-6.0.2.tgz",
-      "integrity": "sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==",
-      "dev": true,
-      "license": "ISC",
+    "node_modules/recma-jsx": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/recma-jsx/-/recma-jsx-1.0.1.tgz",
+      "integrity": "sha512-huSIy7VU2Z5OLv6oFLosQGGDqPqdO1iq6bWNAdhzMxSJP7RAso4fCZ1cKu8j9YHCZf3TPrq4dw3okhrylgcd7w==",
+      "license": "MIT",
       "dependencies": {
-        "is-glob": "^4.0.3"
+        "acorn-jsx": "^5.0.0",
+        "estree-util-to-js": "^2.0.0",
+        "recma-parse": "^1.0.0",
+        "recma-stringify": "^1.0.0",
+        "unified": "^11.0.0"
       },
-      "engines": {
-        "node": ">=10.13.0"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      },
+      "peerDependencies": {
+        "acorn": "^6.0.0 || ^7.0.0 || ^8.0.0"
       }
     },
-    "node_modules/globals": {
-      "version": "13.24.0",
-      "resolved": "https://registry.npmjs.org/globals/-/globals-13.24.0.tgz",
-      "integrity": "sha512-AhO5QUcj8llrbG09iWhPU2B204J1xnPeL8kQmVorSsy+Sjj1sk8gIyh6cUocGmH4L0UuhAJy+hJMRA4mgA4mFQ==",
-      "dev": true,
+    "node_modules/recma-parse": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/recma-parse/-/recma-parse-1.0.0.tgz",
+      "integrity": "sha512-OYLsIGBB5Y5wjnSnQW6t3Xg7q3fQ7FWbw/vcXtORTnyaSFscOtABg+7Pnz6YZ6c27fG1/aN8CjfwoUEUIdwqWQ==",
       "license": "MIT",
       "dependencies": {
-        "type-fest": "^0.20.2"
+        "@types/estree": "^1.0.0",
+        "esast-util-from-js": "^2.0.0",
+        "unified": "^11.0.0",
+        "vfile": "^6.0.0"
       },
-      "engines": {
-        "node": ">=8"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/recma-stringify": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/recma-stringify/-/recma-stringify-1.0.0.tgz",
+      "integrity": "sha512-cjwII1MdIIVloKvC9ErQ+OgAtwHBmcZ0Bg4ciz78FtbT8In39aAYbaA7zvxQ61xVMSPE8WxhLwLbhif4Js2C+g==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "^1.0.0",
+        "estree-util-to-js": "^2.0.0",
+        "unified": "^11.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/globalthis": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/globalthis/-/globalthis-1.0.4.tgz",
-      "integrity": "sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==",
+    "node_modules/reflect.getprototypeof": {
+      "version": "1.0.10",
+      "resolved": "https://registry.npmjs.org/reflect.getprototypeof/-/reflect.getprototypeof-1.0.10.tgz",
+      "integrity": "sha512-00o4I+DVrefhv+nX0ulyi3biSHCPDe+yLv5o/p6d/UVlirijB8E16FtfwSAi4g3tcqrQ4lRAqQSoFEZJehYEcw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
+        "call-bind": "^1.0.8",
         "define-properties": "^1.2.1",
-        "gopd": "^1.0.1"
+        "es-abstract": "^1.23.9",
+        "es-errors": "^1.3.0",
+        "es-object-atoms": "^1.0.0",
+        "get-intrinsic": "^1.2.7",
+        "get-proto": "^1.0.1",
+        "which-builtin-type": "^1.2.1"
       },
       "engines": {
         "node": ">= 0.4"
@@ -1614,32 +9924,44 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/gopd": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/gopd/-/gopd-1.2.0.tgz",
-      "integrity": "sha512-ZUKRh6/kUFoAiTAtTYPZJ3hw9wNxx+BIBOijnlG9PnrJsCcSjs1wyyD6vJpaYtgnzDrKYRSqf3OO6Rfa93xsRg==",
-      "dev": true,
+    "node_modules/regex": {
+      "version": "6.1.0",
+      "resolved": "https://registry.npmjs.org/regex/-/regex-6.1.0.tgz",
+      "integrity": "sha512-6VwtthbV4o/7+OaAF9I5L5V3llLEsoPyq9P1JVXkedTP33c7MfCG0/5NOPcSJn0TzXcG9YUrR0gQSWioew3LDg==",
       "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "dependencies": {
+        "regex-utilities": "^2.3.0"
       }
     },
-    "node_modules/graphemer": {
-      "version": "1.4.0",
-      "resolved": "https://registry.npmjs.org/graphemer/-/graphemer-1.4.0.tgz",
-      "integrity": "sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==",
-      "dev": true,
+    "node_modules/regex-recursion": {
+      "version": "6.0.2",
+      "resolved": "https://registry.npmjs.org/regex-recursion/-/regex-recursion-6.0.2.tgz",
+      "integrity": "sha512-0YCaSCq2VRIebiaUviZNs0cBz1kg5kVS2UKUfNIx8YVs1cN3AV7NTctO5FOKBA+UT2BPJIWZauYHPqJODG50cg==",
+      "license": "MIT",
+      "dependencies": {
+        "regex-utilities": "^2.3.0"
+      }
+    },
+    "node_modules/regex-utilities": {
+      "version": "2.3.0",
+      "resolved": "https://registry.npmjs.org/regex-utilities/-/regex-utilities-2.3.0.tgz",
+      "integrity": "sha512-8VhliFJAWRaUiVvREIiW2NXXTmHs4vMNnSzuJVhscgmGav3g9VDxLrQndI3dZZVVdp0ZO/5v0xmX516/7M9cng==",
       "license": "MIT"
     },
-    "node_modules/has-bigints": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/has-bigints/-/has-bigints-1.1.0.tgz",
-      "integrity": "sha512-R3pbpkcIqv2Pm3dUwgjclDRVmWpTJW2DcMzcIhEXEx1oh/CEMObMm3KLmRJOdvhM7o4uQBnwr8pzRK2sJWIqfg==",
+    "node_modules/regexp.prototype.flags": {
+      "version": "1.5.4",
+      "resolved": "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.5.4.tgz",
+      "integrity": "sha512-dYqgNSZbDwkaJ2ceRd9ojCGjBq+mOm9LmtXnAnEGyHhN/5R7iDW2TRw3h+o/jCFxus3P2LfWIIiwowAjANm7IA==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "define-properties": "^1.2.1",
+        "es-errors": "^1.3.0",
+        "get-proto": "^1.0.1",
+        "gopd": "^1.2.0",
+        "set-function-name": "^2.0.2"
+      },
       "engines": {
         "node": ">= 0.4"
       },
@@ -1647,348 +9969,430 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/has-flag": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz",
-      "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      }
-    },
-    "node_modules/has-property-descriptors": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/has-property-descriptors/-/has-property-descriptors-1.0.2.tgz",
-      "integrity": "sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==",
-      "dev": true,
+    "node_modules/rehype": {
+      "version": "13.0.2",
+      "resolved": "https://registry.npmjs.org/rehype/-/rehype-13.0.2.tgz",
+      "integrity": "sha512-j31mdaRFrwFRUIlxGeuPXXKWQxet52RBQRvCmzl5eCefn/KGbomK5GMHNMsOJf55fgo3qw5tST5neDuarDYR2A==",
       "license": "MIT",
       "dependencies": {
-        "es-define-property": "^1.0.0"
+        "@types/hast": "^3.0.0",
+        "rehype-parse": "^9.0.0",
+        "rehype-stringify": "^10.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/has-proto": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/has-proto/-/has-proto-1.2.0.tgz",
-      "integrity": "sha512-KIL7eQPfHQRC8+XluaIw7BHUwwqL19bQn4hzNgdr+1wXoU0KKj6rufu47lhY7KbJR2C6T6+PfyN0Ea7wkSS+qQ==",
-      "dev": true,
+    "node_modules/rehype-autolink-headings": {
+      "version": "7.1.0",
+      "resolved": "https://registry.npmjs.org/rehype-autolink-headings/-/rehype-autolink-headings-7.1.0.tgz",
+      "integrity": "sha512-rItO/pSdvnvsP4QRB1pmPiNHUskikqtPojZKJPPPAVx9Hj8i8TwMBhofrrAYRhYOOBZH9tgmG5lPqDLuIWPWmw==",
       "license": "MIT",
       "dependencies": {
-        "dunder-proto": "^1.0.0"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/hast": "^3.0.0",
+        "@ungap/structured-clone": "^1.0.0",
+        "hast-util-heading-rank": "^3.0.0",
+        "hast-util-is-element": "^3.0.0",
+        "unified": "^11.0.0",
+        "unist-util-visit": "^5.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/has-symbols": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/has-symbols/-/has-symbols-1.1.0.tgz",
-      "integrity": "sha512-1cDNdwJ2Jaohmb3sg4OmKaMBwuC48sYni5HUw2DvsC8LjGTLK9h+eb1X6RyuOHe4hT0ULCW68iomhjUoKUqlPQ==",
-      "dev": true,
+    "node_modules/rehype-expressive-code": {
+      "version": "0.41.7",
+      "resolved": "https://registry.npmjs.org/rehype-expressive-code/-/rehype-expressive-code-0.41.7.tgz",
+      "integrity": "sha512-25f8ZMSF1d9CMscX7Cft0TSQIqdwjce2gDOvQ+d/w0FovsMwrSt3ODP4P3Z7wO1jsIJ4eYyaDRnIR/27bd/EMQ==",
+      "dependencies": {
+        "expressive-code": "^0.41.7"
+      }
+    },
+    "node_modules/rehype-parse": {
+      "version": "9.0.1",
+      "resolved": "https://registry.npmjs.org/rehype-parse/-/rehype-parse-9.0.1.tgz",
+      "integrity": "sha512-ksCzCD0Fgfh7trPDxr2rSylbwq9iYDkSn8TCDmEJ49ljEUBxDVCzCHv7QNzZOfODanX4+bWQ4WZqLCRWYLfhag==",
       "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "hast-util-from-html": "^2.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/has-tostringtag": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/has-tostringtag/-/has-tostringtag-1.0.2.tgz",
-      "integrity": "sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==",
-      "dev": true,
+    "node_modules/rehype-raw": {
+      "version": "7.0.0",
+      "resolved": "https://registry.npmjs.org/rehype-raw/-/rehype-raw-7.0.0.tgz",
+      "integrity": "sha512-/aE8hCfKlQeA8LmyeyQvQF3eBiLRGNlfBJEvWH7ivp9sBqs7TNqBL5X3v157rM4IFETqDnIOO+z5M/biZbo9Ww==",
       "license": "MIT",
       "dependencies": {
-        "has-symbols": "^1.0.3"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/hast": "^3.0.0",
+        "hast-util-raw": "^9.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/hasown": {
-      "version": "2.0.2",
-      "resolved": "https://registry.npmjs.org/hasown/-/hasown-2.0.2.tgz",
-      "integrity": "sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==",
-      "dev": true,
+    "node_modules/rehype-recma": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/rehype-recma/-/rehype-recma-1.0.0.tgz",
+      "integrity": "sha512-lqA4rGUf1JmacCNWWZx0Wv1dHqMwxzsDWYMTowuplHF3xH0N/MmrZ/G3BDZnzAkRmxDadujCjaKM2hqYdCBOGw==",
       "license": "MIT",
       "dependencies": {
-        "function-bind": "^1.1.2"
+        "@types/estree": "^1.0.0",
+        "@types/hast": "^3.0.0",
+        "hast-util-to-estree": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/ignore": {
-      "version": "5.3.1",
-      "resolved": "https://registry.npmjs.org/ignore/-/ignore-5.3.1.tgz",
-      "integrity": "sha512-5Fytz/IraMjqpwfd34ke28PTVMjZjJG2MPn5t7OE4eUCUNf8BAa7b5WUS9/Qvr6mwOQS7Mk6vdsMno5he+T8Xw==",
-      "dev": true,
+    "node_modules/rehype-slug": {
+      "version": "6.0.0",
+      "resolved": "https://registry.npmjs.org/rehype-slug/-/rehype-slug-6.0.0.tgz",
+      "integrity": "sha512-lWyvf/jwu+oS5+hL5eClVd3hNdmwM1kAC0BUvEGD19pajQMIzcNUd/k9GsfQ+FfECvX+JE+e9/btsKH0EjJT6A==",
       "license": "MIT",
-      "engines": {
-        "node": ">= 4"
+      "dependencies": {
+        "@types/hast": "^3.0.0",
+        "github-slugger": "^2.0.0",
+        "hast-util-heading-rank": "^3.0.0",
+        "hast-util-to-string": "^3.0.0",
+        "unist-util-visit": "^5.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/import-fresh": {
-      "version": "3.3.0",
-      "resolved": "https://registry.npmjs.org/import-fresh/-/import-fresh-3.3.0.tgz",
-      "integrity": "sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==",
-      "dev": true,
+    "node_modules/rehype-stringify": {
+      "version": "10.0.1",
+      "resolved": "https://registry.npmjs.org/rehype-stringify/-/rehype-stringify-10.0.1.tgz",
+      "integrity": "sha512-k9ecfXHmIPuFVI61B9DeLPN0qFHfawM6RsuX48hoqlaKSF61RskNjSm1lI8PhBEM0MRdLxVVm4WmTqJQccH9mA==",
       "license": "MIT",
       "dependencies": {
-        "parent-module": "^1.0.0",
-        "resolve-from": "^4.0.0"
-      },
-      "engines": {
-        "node": ">=6"
+        "@types/hast": "^3.0.0",
+        "hast-util-to-html": "^9.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/imurmurhash": {
-      "version": "0.1.4",
-      "resolved": "https://registry.npmjs.org/imurmurhash/-/imurmurhash-0.1.4.tgz",
-      "integrity": "sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==",
-      "dev": true,
+    "node_modules/remark-gfm": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/remark-gfm/-/remark-gfm-4.0.1.tgz",
+      "integrity": "sha512-1quofZ2RQ9EWdeN34S79+KExV1764+wCUGop5CPL1WGdD0ocPpu91lzPGbwWMECpEpd42kJGQwzRfyov9j4yNg==",
       "license": "MIT",
-      "engines": {
-        "node": ">=0.8.19"
-      }
-    },
-    "node_modules/inflight": {
-      "version": "1.0.6",
-      "resolved": "https://registry.npmjs.org/inflight/-/inflight-1.0.6.tgz",
-      "integrity": "sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==",
-      "deprecated": "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.",
-      "dev": true,
-      "license": "ISC",
       "dependencies": {
-        "once": "^1.3.0",
-        "wrappy": "1"
+        "@types/mdast": "^4.0.0",
+        "mdast-util-gfm": "^3.0.0",
+        "micromark-extension-gfm": "^3.0.0",
+        "remark-parse": "^11.0.0",
+        "remark-stringify": "^11.0.0",
+        "unified": "^11.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/inherits": {
-      "version": "2.0.4",
-      "resolved": "https://registry.npmjs.org/inherits/-/inherits-2.0.4.tgz",
-      "integrity": "sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==",
-      "dev": true,
-      "license": "ISC"
-    },
-    "node_modules/internal-slot": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/internal-slot/-/internal-slot-1.1.0.tgz",
-      "integrity": "sha512-4gd7VpWNQNB4UKKCFFVcp1AVv+FMOgs9NKzjHKusc8jTMhd5eL1NqQqOpE0KzMds804/yHlglp3uxgluOqAPLw==",
-      "dev": true,
+    "node_modules/remark-mdx": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/remark-mdx/-/remark-mdx-3.1.1.tgz",
+      "integrity": "sha512-Pjj2IYlUY3+D8x00UJsIOg5BEvfMyeI+2uLPn9VO9Wg4MEtN/VTIq2NEJQfde9PnX15KgtHyl9S0BcTnWrIuWg==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "hasown": "^2.0.2",
-        "side-channel": "^1.1.0"
+        "mdast-util-mdx": "^3.0.0",
+        "micromark-extension-mdxjs": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-alphabetical": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/is-alphabetical/-/is-alphabetical-1.0.4.tgz",
-      "integrity": "sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg==",
-      "dev": true,
+    "node_modules/remark-parse": {
+      "version": "11.0.0",
+      "resolved": "https://registry.npmjs.org/remark-parse/-/remark-parse-11.0.0.tgz",
+      "integrity": "sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==",
       "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "mdast-util-from-markdown": "^2.0.0",
+        "micromark-util-types": "^2.0.0",
+        "unified": "^11.0.0"
+      },
       "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-alphanumerical": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/is-alphanumerical/-/is-alphanumerical-1.0.4.tgz",
-      "integrity": "sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A==",
-      "dev": true,
+    "node_modules/remark-rehype": {
+      "version": "11.1.2",
+      "resolved": "https://registry.npmjs.org/remark-rehype/-/remark-rehype-11.1.2.tgz",
+      "integrity": "sha512-Dh7l57ianaEoIpzbp0PC9UKAdCSVklD8E5Rpw7ETfbTl3FqcOOgq5q2LVDhgGCkaBv7p24JXikPdvhhmHvKMsw==",
       "license": "MIT",
       "dependencies": {
-        "is-alphabetical": "^1.0.0",
-        "is-decimal": "^1.0.0"
+        "@types/hast": "^3.0.0",
+        "@types/mdast": "^4.0.0",
+        "mdast-util-to-hast": "^13.0.0",
+        "unified": "^11.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-array-buffer": {
-      "version": "3.0.5",
-      "resolved": "https://registry.npmjs.org/is-array-buffer/-/is-array-buffer-3.0.5.tgz",
-      "integrity": "sha512-DDfANUiiG2wC1qawP66qlTugJeL5HyzMpfr8lLK+jMQirGzNod0B12cFB/9q838Ru27sBwfw78/rdoU7RERz6A==",
-      "dev": true,
+    "node_modules/remark-smartypants": {
+      "version": "3.0.2",
+      "resolved": "https://registry.npmjs.org/remark-smartypants/-/remark-smartypants-3.0.2.tgz",
+      "integrity": "sha512-ILTWeOriIluwEvPjv67v7Blgrcx+LZOkAUVtKI3putuhlZm84FnqDORNXPPm+HY3NdZOMhyDwZ1E+eZB/Df5dA==",
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.3",
-        "get-intrinsic": "^1.2.6"
+        "retext": "^9.0.0",
+        "retext-smartypants": "^6.0.0",
+        "unified": "^11.0.4",
+        "unist-util-visit": "^5.0.0"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=16.0.0"
+      }
+    },
+    "node_modules/remark-stringify": {
+      "version": "11.0.0",
+      "resolved": "https://registry.npmjs.org/remark-stringify/-/remark-stringify-11.0.0.tgz",
+      "integrity": "sha512-1OSmLd3awB/t8qdoEOMazZkNsfVTeY4fTsgzcQFdXNq8ToTN4ZGwrMnlda4K6smTFKD+GRV6O48i6Z4iKgPPpw==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/mdast": "^4.0.0",
+        "mdast-util-to-markdown": "^2.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-async-function": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/is-async-function/-/is-async-function-2.1.1.tgz",
-      "integrity": "sha512-9dgM/cZBnNvjzaMYHVoxxfPj2QXt22Ev7SuuPrs+xav0ukGB0S6d4ydZdEiM48kLx5kDV+QBPrpVnFyefL8kkQ==",
+    "node_modules/resolve-from": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
+      "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "async-function": "^1.0.0",
-        "call-bound": "^1.0.3",
-        "get-proto": "^1.0.1",
-        "has-tostringtag": "^1.0.2",
-        "safe-regex-test": "^1.1.0"
-      },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=4"
       }
     },
-    "node_modules/is-bigint": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/is-bigint/-/is-bigint-1.1.0.tgz",
-      "integrity": "sha512-n4ZT37wG78iz03xPRKJrHTdZbe3IicyucEtdRsV5yglwc3GyUfbAfpSeD0FJ41NbUNSt5wbhqfp1fS+BgnvDFQ==",
+    "node_modules/restore-cursor": {
+      "version": "5.1.0",
+      "resolved": "https://registry.npmjs.org/restore-cursor/-/restore-cursor-5.1.0.tgz",
+      "integrity": "sha512-oMA2dcrw6u0YfxJQXm342bFKX/E4sG9rbTzO9ptUcR/e8A33cHuvStiYOwH7fszkZlZ1z/ta9AAoPk2F4qIOHA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "has-bigints": "^1.0.2"
+        "onetime": "^7.0.0",
+        "signal-exit": "^4.1.0"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=18"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/is-boolean-object": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/is-boolean-object/-/is-boolean-object-1.2.2.tgz",
-      "integrity": "sha512-wa56o2/ElJMYqjCjGkXri7it5FbebW5usLw/nPmCMs5DeZ7eziSYZhSmPRn0txqeW4LnAmQQU7FgqLpsEFKM4A==",
-      "dev": true,
+    "node_modules/retext": {
+      "version": "9.0.0",
+      "resolved": "https://registry.npmjs.org/retext/-/retext-9.0.0.tgz",
+      "integrity": "sha512-sbMDcpHCNjvlheSgMfEcVrZko3cDzdbe1x/e7G66dFp0Ff7Mldvi2uv6JkJQzdRcvLYE8CA8Oe8siQx8ZOgTcA==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "has-tostringtag": "^1.0.2"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/nlcst": "^2.0.0",
+        "retext-latin": "^4.0.0",
+        "retext-stringify": "^4.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-callable": {
-      "version": "1.2.7",
-      "resolved": "https://registry.npmjs.org/is-callable/-/is-callable-1.2.7.tgz",
-      "integrity": "sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==",
-      "dev": true,
+    "node_modules/retext-latin": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/retext-latin/-/retext-latin-4.0.0.tgz",
+      "integrity": "sha512-hv9woG7Fy0M9IlRQloq/N6atV82NxLGveq+3H2WOi79dtIYWN8OaxogDm77f8YnVXJL2VD3bbqowu5E3EMhBYA==",
       "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
+      "dependencies": {
+        "@types/nlcst": "^2.0.0",
+        "parse-latin": "^7.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-core-module": {
-      "version": "2.16.1",
-      "resolved": "https://registry.npmjs.org/is-core-module/-/is-core-module-2.16.1.tgz",
-      "integrity": "sha512-UfoeMA6fIJ8wTYFEUjelnaGI67v6+N7qXJEvQuIGa99l4xsCruSYOVSQ0uPANn4dAzm8lkYPaKLrrijLq7x23w==",
-      "dev": true,
+    "node_modules/retext-smartypants": {
+      "version": "6.2.0",
+      "resolved": "https://registry.npmjs.org/retext-smartypants/-/retext-smartypants-6.2.0.tgz",
+      "integrity": "sha512-kk0jOU7+zGv//kfjXEBjdIryL1Acl4i9XNkHxtM7Tm5lFiCog576fjNC9hjoR7LTKQ0DsPWy09JummSsH1uqfQ==",
       "license": "MIT",
       "dependencies": {
-        "hasown": "^2.0.2"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/nlcst": "^2.0.0",
+        "nlcst-to-string": "^4.0.0",
+        "unist-util-visit": "^5.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-data-view": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/is-data-view/-/is-data-view-1.0.2.tgz",
-      "integrity": "sha512-RKtWF8pGmS87i2D6gqQu/l7EYRlVdfzemCJN/P3UOs//x1QE7mfhvzHIApBTRf7axvT6DMGwSwBXYCT0nfB9xw==",
-      "dev": true,
+    "node_modules/retext-stringify": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/retext-stringify/-/retext-stringify-4.0.0.tgz",
+      "integrity": "sha512-rtfN/0o8kL1e+78+uxPTqu1Klt0yPzKuQ2BfWwwfgIUSayyzxpM1PJzkKt4V8803uB9qSy32MvI7Xep9khTpiA==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "get-intrinsic": "^1.2.6",
-        "is-typed-array": "^1.1.13"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/nlcst": "^2.0.0",
+        "nlcst-to-string": "^4.0.0",
+        "unified": "^11.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/is-date-object": {
+    "node_modules/reusify": {
       "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/is-date-object/-/is-date-object-1.1.0.tgz",
-      "integrity": "sha512-PwwhEakHVKTdRNVOw+/Gyh0+MzlCl4R6qKvkhuvLtPMggI1WAHt9sOwZxQLSGpUaDnrdyDsomoRgNnCfKNSXXg==",
+      "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.1.0.tgz",
+      "integrity": "sha512-g6QUff04oZpHs0eG5p83rFLhHeV00ug/Yf9nZM6fLeUrPguBTkTQOdpAWWspMh55TZfVQDPaN3NQJfbVRAxdIw==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "call-bound": "^1.0.2",
-        "has-tostringtag": "^1.0.2"
-      },
       "engines": {
-        "node": ">= 0.4"
+        "iojs": ">=1.0.0",
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/rfdc": {
+      "version": "1.4.1",
+      "resolved": "https://registry.npmjs.org/rfdc/-/rfdc-1.4.1.tgz",
+      "integrity": "sha512-q1b3N5QkRUWUl7iyylaaj3kOpIT0N2i9MqIEQXP73GVsN9cw3fdx8X63cEmWhJGi2PPCF23Ijp7ktmd39rawIA==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/rollup": {
+      "version": "4.59.0",
+      "resolved": "https://registry.npmjs.org/rollup/-/rollup-4.59.0.tgz",
+      "integrity": "sha512-2oMpl67a3zCH9H79LeMcbDhXW/UmWG/y2zuqnF2jQq5uq9TbM9TVyXvA4+t+ne2IIkBdrLpAaRQAvo7YI/Yyeg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/estree": "1.0.8"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "bin": {
+        "rollup": "dist/bin/rollup"
+      },
+      "engines": {
+        "node": ">=18.0.0",
+        "npm": ">=8.0.0"
+      },
+      "optionalDependencies": {
+        "@rollup/rollup-android-arm-eabi": "4.59.0",
+        "@rollup/rollup-android-arm64": "4.59.0",
+        "@rollup/rollup-darwin-arm64": "4.59.0",
+        "@rollup/rollup-darwin-x64": "4.59.0",
+        "@rollup/rollup-freebsd-arm64": "4.59.0",
+        "@rollup/rollup-freebsd-x64": "4.59.0",
+        "@rollup/rollup-linux-arm-gnueabihf": "4.59.0",
+        "@rollup/rollup-linux-arm-musleabihf": "4.59.0",
+        "@rollup/rollup-linux-arm64-gnu": "4.59.0",
+        "@rollup/rollup-linux-arm64-musl": "4.59.0",
+        "@rollup/rollup-linux-loong64-gnu": "4.59.0",
+        "@rollup/rollup-linux-loong64-musl": "4.59.0",
+        "@rollup/rollup-linux-ppc64-gnu": "4.59.0",
+        "@rollup/rollup-linux-ppc64-musl": "4.59.0",
+        "@rollup/rollup-linux-riscv64-gnu": "4.59.0",
+        "@rollup/rollup-linux-riscv64-musl": "4.59.0",
+        "@rollup/rollup-linux-s390x-gnu": "4.59.0",
+        "@rollup/rollup-linux-x64-gnu": "4.59.0",
+        "@rollup/rollup-linux-x64-musl": "4.59.0",
+        "@rollup/rollup-openbsd-x64": "4.59.0",
+        "@rollup/rollup-openharmony-arm64": "4.59.0",
+        "@rollup/rollup-win32-arm64-msvc": "4.59.0",
+        "@rollup/rollup-win32-ia32-msvc": "4.59.0",
+        "@rollup/rollup-win32-x64-gnu": "4.59.0",
+        "@rollup/rollup-win32-x64-msvc": "4.59.0",
+        "fsevents": "~2.3.2"
       }
     },
-    "node_modules/is-decimal": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/is-decimal/-/is-decimal-1.0.4.tgz",
-      "integrity": "sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw==",
+    "node_modules/run-parallel": {
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
+      "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
       "dev": true,
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/feross"
+        },
+        {
+          "type": "patreon",
+          "url": "https://www.patreon.com/feross"
+        },
+        {
+          "type": "consulting",
+          "url": "https://feross.org/support"
+        }
+      ],
       "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+      "dependencies": {
+        "queue-microtask": "^1.2.2"
       }
     },
-    "node_modules/is-extglob": {
-      "version": "2.1.1",
-      "resolved": "https://registry.npmjs.org/is-extglob/-/is-extglob-2.1.1.tgz",
-      "integrity": "sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==",
+    "node_modules/s.color": {
+      "version": "0.0.15",
+      "resolved": "https://registry.npmjs.org/s.color/-/s.color-0.0.15.tgz",
+      "integrity": "sha512-AUNrbEUHeKY8XsYr/DYpl+qk5+aM+DChopnWOPEzn8YKzOhv4l2zH6LzZms3tOZP3wwdOyc0RmTciyi46HLIuA==",
+      "dev": true,
+      "license": "MIT"
+    },
+    "node_modules/safe-array-concat": {
+      "version": "1.1.3",
+      "resolved": "https://registry.npmjs.org/safe-array-concat/-/safe-array-concat-1.1.3.tgz",
+      "integrity": "sha512-AURm5f0jYEOydBj7VQlVvDrjeFgthDdEF5H1dP+6mNpoXOMo1quQqJ4wvJDyRZ9+pO3kGWoOdmV08cSv2aJV6Q==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.2",
+        "get-intrinsic": "^1.2.6",
+        "has-symbols": "^1.1.0",
+        "isarray": "^2.0.5"
+      },
       "engines": {
-        "node": ">=0.10.0"
+        "node": ">=0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-finalizationregistry": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/is-finalizationregistry/-/is-finalizationregistry-1.1.1.tgz",
-      "integrity": "sha512-1pC6N8qWJbWoPtEjgcL2xyhQOP491EQjeUo3qTKcmV8YSDDJrOepfG8pcC7h/QgnQHYSv0mJ3Z/ZWxmatVrysg==",
+    "node_modules/safe-push-apply": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/safe-push-apply/-/safe-push-apply-1.0.0.tgz",
+      "integrity": "sha512-iKE9w/Z7xCzUMIZqdBsp6pEQvwuEebH4vdpjcDWnyzaI6yl6O9FHvVpmGelvEHNsoY6wGblkxR6Zty/h00WiSA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3"
+        "es-errors": "^1.3.0",
+        "isarray": "^2.0.5"
       },
       "engines": {
         "node": ">= 0.4"
@@ -1997,17 +10401,16 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-generator-function": {
+    "node_modules/safe-regex-test": {
       "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/is-generator-function/-/is-generator-function-1.1.0.tgz",
-      "integrity": "sha512-nPUB5km40q9e8UfN/Zc24eLlzdSf9OfKByBw9CIdw4H1giPMeA0OIJvbchsCu4npfI2QcMVBsGEBHKZ7wLTWmQ==",
+      "resolved": "https://registry.npmjs.org/safe-regex-test/-/safe-regex-test-1.1.0.tgz",
+      "integrity": "sha512-x/+Cz4YrimQxQccJf5mKEbIa1NzeCRNI5Ecl/ekmlYaampdNLPalVyIcCZNNH3MvmqBugV5TMYZXv0ljslUlaw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "get-proto": "^1.0.0",
-        "has-tostringtag": "^1.0.2",
-        "safe-regex-test": "^1.1.0"
+        "call-bound": "^1.0.2",
+        "es-errors": "^1.3.0",
+        "is-regex": "^1.2.1"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2016,174 +10419,226 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-glob": {
-      "version": "4.0.3",
-      "resolved": "https://registry.npmjs.org/is-glob/-/is-glob-4.0.3.tgz",
-      "integrity": "sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==",
+    "node_modules/safer-buffer": {
+      "version": "2.1.2",
+      "resolved": "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz",
+      "integrity": "sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==",
+      "license": "MIT"
+    },
+    "node_modules/sass-formatter": {
+      "version": "0.7.9",
+      "resolved": "https://registry.npmjs.org/sass-formatter/-/sass-formatter-0.7.9.tgz",
+      "integrity": "sha512-CWZ8XiSim+fJVG0cFLStwDvft1VI7uvXdCNJYXhDvowiv+DsbD1nXLiQ4zrE5UBvj5DWZJ93cwN0NX5PMsr1Pw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "is-extglob": "^2.1.1"
+        "suf-log": "^2.5.3"
+      }
+    },
+    "node_modules/satori": {
+      "version": "0.26.0",
+      "resolved": "https://registry.npmjs.org/satori/-/satori-0.26.0.tgz",
+      "integrity": "sha512-tkMFrfIs3l2mQ2JEcyW0ADTy3zGggFRFzi6Ef8YozQSFsFKEqaSO1Y8F9wJg4//PJGQauMalHGTUEkPrFwhVPA==",
+      "license": "MPL-2.0",
+      "dependencies": {
+        "@shuding/opentype.js": "1.4.0-beta.0",
+        "css-background-parser": "^0.1.0",
+        "css-box-shadow": "1.0.0-3",
+        "css-gradient-parser": "^0.0.17",
+        "css-to-react-native": "^3.0.0",
+        "emoji-regex-xs": "^2.0.1",
+        "escape-html": "^1.0.3",
+        "linebreak": "^1.1.0",
+        "parse-css-color": "^0.2.1",
+        "postcss-value-parser": "^4.2.0",
+        "yoga-layout": "^3.2.1"
       },
       "engines": {
-        "node": ">=0.10.0"
+        "node": ">=16"
       }
     },
-    "node_modules/is-hexadecimal": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/is-hexadecimal/-/is-hexadecimal-1.0.4.tgz",
-      "integrity": "sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+    "node_modules/sax": {
+      "version": "1.6.0",
+      "resolved": "https://registry.npmjs.org/sax/-/sax-1.6.0.tgz",
+      "integrity": "sha512-6R3J5M4AcbtLUdZmRv2SygeVaM7IhrLXu9BmnOGmmACak8fiUtOsYNWUS4uK7upbmHIBbLBeFeI//477BKLBzA==",
+      "license": "BlueOak-1.0.0",
+      "engines": {
+        "node": ">=11.0.0"
       }
     },
-    "node_modules/is-map": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/is-map/-/is-map-2.0.3.tgz",
-      "integrity": "sha512-1Qed0/Hr2m+YqxnM09CjA2d/i6YZNfF6R2oRAOj36eUdS6qIV/huPJNSEpKbupewFs+ZsJlxsjjPbc0/afW6Lw==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
+    "node_modules/scheduler": {
+      "version": "0.27.0",
+      "resolved": "https://registry.npmjs.org/scheduler/-/scheduler-0.27.0.tgz",
+      "integrity": "sha512-eNv+WrVbKu1f3vbYJT/xtiF5syA5HPIMtf9IgY/nKg0sWqzAUEvqY/xm7OcZc/qafLx/iO9FgOmeSAp4v5ti/Q=="
+    },
+    "node_modules/section-matter": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/section-matter/-/section-matter-1.0.0.tgz",
+      "integrity": "sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==",
+      "dependencies": {
+        "extend-shallow": "^2.0.1",
+        "kind-of": "^6.0.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "engines": {
+        "node": ">=4"
       }
     },
-    "node_modules/is-negative-zero": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/is-negative-zero/-/is-negative-zero-2.0.3.tgz",
-      "integrity": "sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==",
-      "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
+    "node_modules/semver": {
+      "version": "7.7.4",
+      "resolved": "https://registry.npmjs.org/semver/-/semver-7.7.4.tgz",
+      "integrity": "sha512-vFKC2IEtQnVhpT78h1Yp8wzwrf8CM+MzKMHGJZfBtzhZNycRFnXsHk6E5TxIkkMsgNS7mdX3AGB7x2QM2di4lA==",
+      "license": "ISC",
+      "bin": {
+        "semver": "bin/semver.js"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "engines": {
+        "node": ">=10"
       }
     },
-    "node_modules/is-number-object": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/is-number-object/-/is-number-object-1.1.1.tgz",
-      "integrity": "sha512-lZhclumE1G6VYD8VHe35wFaIif+CTy5SJIi5+3y4psDgWu4wPDoBhF8NxUOinEc7pHgiTsT6MaBb92rKhhD+Xw==",
+    "node_modules/set-function-length": {
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/set-function-length/-/set-function-length-1.2.2.tgz",
+      "integrity": "sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "has-tostringtag": "^1.0.2"
+        "define-data-property": "^1.1.4",
+        "es-errors": "^1.3.0",
+        "function-bind": "^1.1.2",
+        "get-intrinsic": "^1.2.4",
+        "gopd": "^1.0.1",
+        "has-property-descriptors": "^1.0.2"
       },
       "engines": {
         "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-path-inside": {
-      "version": "3.0.3",
-      "resolved": "https://registry.npmjs.org/is-path-inside/-/is-path-inside-3.0.3.tgz",
-      "integrity": "sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==",
+    "node_modules/set-function-name": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/set-function-name/-/set-function-name-2.0.2.tgz",
+      "integrity": "sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "define-data-property": "^1.1.4",
+        "es-errors": "^1.3.0",
+        "functions-have-names": "^1.2.3",
+        "has-property-descriptors": "^1.0.2"
+      },
       "engines": {
-        "node": ">=8"
+        "node": ">= 0.4"
       }
     },
-    "node_modules/is-regex": {
-      "version": "1.2.1",
-      "resolved": "https://registry.npmjs.org/is-regex/-/is-regex-1.2.1.tgz",
-      "integrity": "sha512-MjYsKHO5O7mCsmRGxWcLWheFqN9DJ/2TmngvjKXihe6efViPqc274+Fx/4fYj/r03+ESvBdTXK0V6tA3rgez1g==",
+    "node_modules/set-proto": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/set-proto/-/set-proto-1.0.0.tgz",
+      "integrity": "sha512-RJRdvCo6IAnPdsvP/7m6bsQqNnn1FCBX5ZNtFL98MmFF/4xAIJTIg1YbHW5DC2W5SKZanrC6i4HsJqlajw/dZw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "gopd": "^1.2.0",
-        "has-tostringtag": "^1.0.2",
-        "hasown": "^2.0.2"
+        "dunder-proto": "^1.0.1",
+        "es-errors": "^1.3.0",
+        "es-object-atoms": "^1.0.0"
       },
       "engines": {
         "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-set": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/is-set/-/is-set-2.0.3.tgz",
-      "integrity": "sha512-iPAjerrse27/ygGLxw+EBR9agv9Y6uLeYVJMu+QNCoouJ1/1ri0mGrcWpfCqFZuzzx3WjtwxG098X+n4OuRkPg==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/sharp": {
+      "version": "0.34.5",
+      "resolved": "https://registry.npmjs.org/sharp/-/sharp-0.34.5.tgz",
+      "integrity": "sha512-Ou9I5Ft9WNcCbXrU9cMgPBcCK8LiwLqcbywW3t4oDV37n1pzpuNLsYiAV8eODnjbtQlSDwZ2cUEeQz4E54Hltg==",
+      "hasInstallScript": true,
+      "license": "Apache-2.0",
+      "dependencies": {
+        "@img/colour": "^1.0.0",
+        "detect-libc": "^2.1.2",
+        "semver": "^7.7.3"
+      },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^18.17.0 || ^20.3.0 || >=21.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://opencollective.com/libvips"
+      },
+      "optionalDependencies": {
+        "@img/sharp-darwin-arm64": "0.34.5",
+        "@img/sharp-darwin-x64": "0.34.5",
+        "@img/sharp-libvips-darwin-arm64": "1.2.4",
+        "@img/sharp-libvips-darwin-x64": "1.2.4",
+        "@img/sharp-libvips-linux-arm": "1.2.4",
+        "@img/sharp-libvips-linux-arm64": "1.2.4",
+        "@img/sharp-libvips-linux-ppc64": "1.2.4",
+        "@img/sharp-libvips-linux-riscv64": "1.2.4",
+        "@img/sharp-libvips-linux-s390x": "1.2.4",
+        "@img/sharp-libvips-linux-x64": "1.2.4",
+        "@img/sharp-libvips-linuxmusl-arm64": "1.2.4",
+        "@img/sharp-libvips-linuxmusl-x64": "1.2.4",
+        "@img/sharp-linux-arm": "0.34.5",
+        "@img/sharp-linux-arm64": "0.34.5",
+        "@img/sharp-linux-ppc64": "0.34.5",
+        "@img/sharp-linux-riscv64": "0.34.5",
+        "@img/sharp-linux-s390x": "0.34.5",
+        "@img/sharp-linux-x64": "0.34.5",
+        "@img/sharp-linuxmusl-arm64": "0.34.5",
+        "@img/sharp-linuxmusl-x64": "0.34.5",
+        "@img/sharp-wasm32": "0.34.5",
+        "@img/sharp-win32-arm64": "0.34.5",
+        "@img/sharp-win32-ia32": "0.34.5",
+        "@img/sharp-win32-x64": "0.34.5"
       }
     },
-    "node_modules/is-shared-array-buffer": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/is-shared-array-buffer/-/is-shared-array-buffer-1.0.4.tgz",
-      "integrity": "sha512-ISWac8drv4ZGfwKl5slpHG9OwPNty4jOWPRIhBpxOoD+hqITiwuipOQ2bNthAzwA3B4fIjO4Nln74N0S9byq8A==",
+    "node_modules/shebang-command": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
+      "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3"
+        "shebang-regex": "^3.0.0"
       },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=8"
       }
     },
-    "node_modules/is-string": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/is-string/-/is-string-1.1.1.tgz",
-      "integrity": "sha512-BtEeSsoaQjlSPBemMQIrY1MY0uM6vnS1g5fmufYOtnxLGUZM2178PKbhsk7Ffv58IX+ZtcvoGwccYsh0PglkAA==",
+    "node_modules/shebang-regex": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
+      "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "call-bound": "^1.0.3",
-        "has-tostringtag": "^1.0.2"
-      },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=8"
       }
     },
-    "node_modules/is-symbol": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/is-symbol/-/is-symbol-1.1.1.tgz",
-      "integrity": "sha512-9gGx6GTtCQM73BgmHQXfDmLtfjjTUDSyoxTCbp5WtoixAhfgsDirWIcVQ/IHpvI5Vgd5i/J5F7B9cN/WlVbC/w==",
-      "dev": true,
+    "node_modules/shiki": {
+      "version": "3.21.0",
+      "resolved": "https://registry.npmjs.org/shiki/-/shiki-3.21.0.tgz",
+      "integrity": "sha512-N65B/3bqL/TI2crrXr+4UivctrAGEjmsib5rPMMPpFp1xAx/w03v8WZ9RDDFYteXoEgY7qZ4HGgl5KBIu1153w==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "has-symbols": "^1.1.0",
-        "safe-regex-test": "^1.1.0"
-      },
-      "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "@shikijs/core": "3.21.0",
+        "@shikijs/engine-javascript": "3.21.0",
+        "@shikijs/engine-oniguruma": "3.21.0",
+        "@shikijs/langs": "3.21.0",
+        "@shikijs/themes": "3.21.0",
+        "@shikijs/types": "3.21.0",
+        "@shikijs/vscode-textmate": "^10.0.2",
+        "@types/hast": "^3.0.4"
       }
     },
-    "node_modules/is-typed-array": {
-      "version": "1.1.15",
-      "resolved": "https://registry.npmjs.org/is-typed-array/-/is-typed-array-1.1.15.tgz",
-      "integrity": "sha512-p3EcsicXjit7SaskXHs1hA91QxgTw46Fv6EFKKGS5DRFLD8yKnohjF3hxoju94b/OcMZoQukzpPpBE9uLVKzgQ==",
+    "node_modules/side-channel": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.1.0.tgz",
+      "integrity": "sha512-ZX99e6tRweoUXqR+VBrslhda51Nh5MTQwou5tnUDgbtyM0dBgmhEDtWGP/xbKn6hqfPRHujUNwz5fy/wbbhnpw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "which-typed-array": "^1.1.16"
+        "es-errors": "^1.3.0",
+        "object-inspect": "^1.13.3",
+        "side-channel-list": "^1.0.0",
+        "side-channel-map": "^1.0.1",
+        "side-channel-weakmap": "^1.0.2"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2192,12 +10647,16 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-weakmap": {
-      "version": "2.0.2",
-      "resolved": "https://registry.npmjs.org/is-weakmap/-/is-weakmap-2.0.2.tgz",
-      "integrity": "sha512-K5pXYOm9wqY1RgjpL3YTkF39tni1XajUIkawTLUo9EZEVUFga5gSQJF8nNS7ZwJQ02y+1YCNYcMh+HIf1ZqE+w==",
+    "node_modules/side-channel-list": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/side-channel-list/-/side-channel-list-1.0.0.tgz",
+      "integrity": "sha512-FCLHtRD/gnpCiCHEiJLOwdmFP+wzCmDEkc9y7NsYxeF4u7Btsn1ZuwgwJGxImImHicJArLP4R0yX4c2KCrMrTA==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0",
+        "object-inspect": "^1.13.3"
+      },
       "engines": {
         "node": ">= 0.4"
       },
@@ -2205,14 +10664,17 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-weakref": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/is-weakref/-/is-weakref-1.1.1.tgz",
-      "integrity": "sha512-6i9mGWSlqzNMEqpCp93KwRS1uUOodk2OJ6b+sq7ZPDSy2WuI5NFIxp/254TytR8ftefexkWn5xNiHUNpPOfSew==",
+    "node_modules/side-channel-map": {
+      "version": "1.0.1",
+      "resolved": "https://registry.npmjs.org/side-channel-map/-/side-channel-map-1.0.1.tgz",
+      "integrity": "sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3"
+        "call-bound": "^1.0.2",
+        "es-errors": "^1.3.0",
+        "get-intrinsic": "^1.2.5",
+        "object-inspect": "^1.13.3"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2221,15 +10683,18 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/is-weakset": {
-      "version": "2.0.4",
-      "resolved": "https://registry.npmjs.org/is-weakset/-/is-weakset-2.0.4.tgz",
-      "integrity": "sha512-mfcwb6IzQyOKTs84CQMrOwW4gQcaTOAWJ0zzJCl2WSPDrWk/OzDaImWFH3djXhb24g4eudZfLRozAvPGw4d9hQ==",
+    "node_modules/side-channel-weakmap": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/side-channel-weakmap/-/side-channel-weakmap-1.0.2.tgz",
+      "integrity": "sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "get-intrinsic": "^1.2.6"
+        "call-bound": "^1.0.2",
+        "es-errors": "^1.3.0",
+        "get-intrinsic": "^1.2.5",
+        "object-inspect": "^1.13.3",
+        "side-channel-map": "^1.0.1"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2238,247 +10703,230 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/isarray": {
-      "version": "2.0.5",
-      "resolved": "https://registry.npmjs.org/isarray/-/isarray-2.0.5.tgz",
-      "integrity": "sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/isexe": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/isexe/-/isexe-2.0.0.tgz",
-      "integrity": "sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==",
-      "dev": true,
-      "license": "ISC"
-    },
-    "node_modules/js-yaml": {
-      "version": "4.1.1",
-      "resolved": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.1.1.tgz",
-      "integrity": "sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==",
+    "node_modules/signal-exit": {
+      "version": "4.1.0",
+      "resolved": "https://registry.npmjs.org/signal-exit/-/signal-exit-4.1.0.tgz",
+      "integrity": "sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==",
       "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "argparse": "^2.0.1"
+      "license": "ISC",
+      "engines": {
+        "node": ">=14"
       },
-      "bin": {
-        "js-yaml": "bin/js-yaml.js"
+      "funding": {
+        "url": "https://github.com/sponsors/isaacs"
       }
     },
-    "node_modules/json-buffer": {
-      "version": "3.0.1",
-      "resolved": "https://registry.npmjs.org/json-buffer/-/json-buffer-3.0.1.tgz",
-      "integrity": "sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/json-schema-traverse": {
-      "version": "0.4.1",
-      "resolved": "https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.4.1.tgz",
-      "integrity": "sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/json-stable-stringify-without-jsonify": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/json-stable-stringify-without-jsonify/-/json-stable-stringify-without-jsonify-1.0.1.tgz",
-      "integrity": "sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==",
-      "dev": true,
+    "node_modules/sisteransi": {
+      "version": "1.0.5",
+      "resolved": "https://registry.npmjs.org/sisteransi/-/sisteransi-1.0.5.tgz",
+      "integrity": "sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==",
       "license": "MIT"
     },
-    "node_modules/json5": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/json5/-/json5-1.0.2.tgz",
-      "integrity": "sha512-g1MWMLBiz8FKi1e4w0UyVL3w+iJceWAFBAaBnnGKOpNa5f8TLktkbre1+s6oICydWAm+HRUGTmI+//xv2hvXYA==",
-      "dev": true,
+    "node_modules/sitemap": {
+      "version": "9.0.1",
+      "resolved": "https://registry.npmjs.org/sitemap/-/sitemap-9.0.1.tgz",
+      "integrity": "sha512-S6hzjGJSG3d6if0YoF5kTyeRJvia6FSTBroE5fQ0bu1QNxyJqhhinfUsXi9fH3MgtXODWvwo2BDyQSnhPQ88uQ==",
       "license": "MIT",
       "dependencies": {
-        "minimist": "^1.2.0"
+        "@types/node": "^24.9.2",
+        "@types/sax": "^1.2.1",
+        "arg": "^5.0.0",
+        "sax": "^1.4.1"
       },
       "bin": {
-        "json5": "lib/cli.js"
+        "sitemap": "dist/esm/cli.js"
+      },
+      "engines": {
+        "node": ">=20.19.5",
+        "npm": ">=10.8.2"
       }
     },
-    "node_modules/keyv": {
-      "version": "4.5.4",
-      "resolved": "https://registry.npmjs.org/keyv/-/keyv-4.5.4.tgz",
-      "integrity": "sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==",
-      "dev": true,
+    "node_modules/sitemap/node_modules/@types/node": {
+      "version": "24.12.0",
+      "resolved": "https://registry.npmjs.org/@types/node/-/node-24.12.0.tgz",
+      "integrity": "sha512-GYDxsZi3ChgmckRT9HPU0WEhKLP08ev/Yfcq2AstjrDASOYCSXeyjDsHg4v5t4jOj7cyDX3vmprafKlWIG9MXQ==",
       "license": "MIT",
       "dependencies": {
-        "json-buffer": "3.0.1"
+        "undici-types": "~7.16.0"
       }
     },
-    "node_modules/levn": {
-      "version": "0.4.1",
-      "resolved": "https://registry.npmjs.org/levn/-/levn-0.4.1.tgz",
-      "integrity": "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==",
+    "node_modules/sitemap/node_modules/undici-types": {
+      "version": "7.16.0",
+      "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-7.16.0.tgz",
+      "integrity": "sha512-Zz+aZWSj8LE6zoxD+xrjh4VfkIG8Ya6LvYkZqtUQGJPZjYl53ypCaUwWqo7eI0x66KBGeRo+mlBEkMSeSZ38Nw==",
+      "license": "MIT"
+    },
+    "node_modules/slice-ansi": {
+      "version": "7.1.2",
+      "resolved": "https://registry.npmjs.org/slice-ansi/-/slice-ansi-7.1.2.tgz",
+      "integrity": "sha512-iOBWFgUX7caIZiuutICxVgX1SdxwAVFFKwt1EvMYYec/NWO5meOJ6K5uQxhrYBdQJne4KxiqZc+KptFOWFSI9w==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "prelude-ls": "^1.2.1",
-        "type-check": "~0.4.0"
+        "ansi-styles": "^6.2.1",
+        "is-fullwidth-code-point": "^5.0.0"
       },
       "engines": {
-        "node": ">= 0.8.0"
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/slice-ansi?sponsor=1"
       }
     },
-    "node_modules/locate-path": {
-      "version": "6.0.0",
-      "resolved": "https://registry.npmjs.org/locate-path/-/locate-path-6.0.0.tgz",
-      "integrity": "sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==",
+    "node_modules/slice-ansi/node_modules/is-fullwidth-code-point": {
+      "version": "5.1.0",
+      "resolved": "https://registry.npmjs.org/is-fullwidth-code-point/-/is-fullwidth-code-point-5.1.0.tgz",
+      "integrity": "sha512-5XHYaSyiqADb4RnZ1Bdad6cPp8Toise4TzEjcOYDHZkTCbKgiUl7WTUCpNWHuxmDt91wnsZBc9xinNzopv3JMQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "p-locate": "^5.0.0"
+        "get-east-asian-width": "^1.3.1"
       },
       "engines": {
-        "node": ">=10"
+        "node": ">=18"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/lodash.merge": {
-      "version": "4.6.2",
-      "resolved": "https://registry.npmjs.org/lodash.merge/-/lodash.merge-4.6.2.tgz",
-      "integrity": "sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==",
-      "dev": true,
-      "license": "MIT"
-    },
-    "node_modules/math-intrinsics": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/math-intrinsics/-/math-intrinsics-1.1.0.tgz",
-      "integrity": "sha512-/IXtbwEk5HTPyEwyKX6hGkYXxM9nbj64B+ilVJnC/R6B0pH5G4V3b0pVbL7DBj4tkhBAppbQUlf6F6Xl9LHu1g==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/smol-toml": {
+      "version": "1.6.1",
+      "resolved": "https://registry.npmjs.org/smol-toml/-/smol-toml-1.6.1.tgz",
+      "integrity": "sha512-dWUG8F5sIIARXih1DTaQAX4SsiTXhInKf1buxdY9DIg4ZYPZK5nGM1VRIYmEbDbsHt7USo99xSLFu5Q1IqTmsg==",
+      "license": "BSD-3-Clause",
       "engines": {
-        "node": ">= 0.4"
-      }
-    },
-    "node_modules/mdast-util-from-markdown": {
-      "version": "0.8.5",
-      "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-0.8.5.tgz",
-      "integrity": "sha512-2hkTXtYYnr+NubD/g6KGBS/0mFmBcifAsI0yIWRiRo0PjVs6SSOSOdtzbp6kSGnShDN6G5aWZpKQ2lWRy27mWQ==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "@types/mdast": "^3.0.0",
-        "mdast-util-to-string": "^2.0.0",
-        "micromark": "~2.11.0",
-        "parse-entities": "^2.0.0",
-        "unist-util-stringify-position": "^2.0.0"
+        "node": ">= 18"
       },
       "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
-      }
-    },
-    "node_modules/mdast-util-to-string": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/mdast-util-to-string/-/mdast-util-to-string-2.0.0.tgz",
-      "integrity": "sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w==",
-      "dev": true,
-      "license": "MIT",
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
+        "url": "https://github.com/sponsors/cyyynthia"
       }
     },
-    "node_modules/micromark": {
-      "version": "2.11.4",
-      "resolved": "https://registry.npmjs.org/micromark/-/micromark-2.11.4.tgz",
-      "integrity": "sha512-+WoovN/ppKolQOFIAajxi7Lu9kInbPxFuTBVEavFcL8eAfVstoc5MocPmqBeAdBOJV00uaVjegzH4+MA0DN/uA==",
+    "node_modules/snake-case": {
+      "version": "3.0.4",
+      "resolved": "https://registry.npmjs.org/snake-case/-/snake-case-3.0.4.tgz",
+      "integrity": "sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==",
       "dev": true,
-      "funding": [
-        {
-          "type": "GitHub Sponsors",
-          "url": "https://github.com/sponsors/unifiedjs"
-        },
-        {
-          "type": "OpenCollective",
-          "url": "https://opencollective.com/unified"
-        }
-      ],
-      "license": "MIT",
       "dependencies": {
-        "debug": "^4.0.0",
-        "parse-entities": "^2.0.0"
+        "dot-case": "^3.0.4",
+        "tslib": "^2.0.3"
       }
     },
-    "node_modules/minimatch": {
-      "version": "3.1.2",
-      "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz",
-      "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==",
-      "dev": true,
-      "license": "ISC",
-      "dependencies": {
-        "brace-expansion": "^1.1.7"
-      },
+    "node_modules/source-map": {
+      "version": "0.7.6",
+      "resolved": "https://registry.npmjs.org/source-map/-/source-map-0.7.6.tgz",
+      "integrity": "sha512-i5uvt8C3ikiWeNZSVZNWcfZPItFQOsYTUAOkcUPGd8DqDy1uOUikjt5dG+uRlwyvR108Fb9DOd4GvXfT0N2/uQ==",
+      "license": "BSD-3-Clause",
       "engines": {
-        "node": "*"
+        "node": ">= 12"
       }
     },
-    "node_modules/minimist": {
-      "version": "1.2.8",
-      "resolved": "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz",
-      "integrity": "sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==",
-      "dev": true,
+    "node_modules/source-map-js": {
+      "version": "1.2.1",
+      "resolved": "https://registry.npmjs.org/source-map-js/-/source-map-js-1.2.1.tgz",
+      "integrity": "sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==",
+      "license": "BSD-3-Clause",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/space-separated-tokens": {
+      "version": "2.0.2",
+      "resolved": "https://registry.npmjs.org/space-separated-tokens/-/space-separated-tokens-2.0.2.tgz",
+      "integrity": "sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==",
       "license": "MIT",
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/ms": {
-      "version": "2.1.2",
-      "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz",
-      "integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==",
+    "node_modules/sprintf-js": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/sprintf-js/-/sprintf-js-1.0.3.tgz",
+      "integrity": "sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g=="
+    },
+    "node_modules/stop-iteration-iterator": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/stop-iteration-iterator/-/stop-iteration-iterator-1.1.0.tgz",
+      "integrity": "sha512-eLoXW/DHyl62zxY4SCaIgnRhuMr6ri4juEYARS8E6sCEqzKpOiE521Ucofdx+KnDZl5xmvGYaaKCk5FEOxJCoQ==",
       "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "es-errors": "^1.3.0",
+        "internal-slot": "^1.1.0"
+      },
+      "engines": {
+        "node": ">= 0.4"
+      }
+    },
+    "node_modules/stream-replace-string": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/stream-replace-string/-/stream-replace-string-2.0.0.tgz",
+      "integrity": "sha512-TlnjJ1C0QrmxRNrON00JvaFFlNh5TTG00APw23j74ET7gkQpTASi6/L2fuiav8pzK715HXtUeClpBTw2NPSn6w==",
       "license": "MIT"
     },
-    "node_modules/natural-compare": {
-      "version": "1.4.0",
-      "resolved": "https://registry.npmjs.org/natural-compare/-/natural-compare-1.4.0.tgz",
-      "integrity": "sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==",
+    "node_modules/string-argv": {
+      "version": "0.3.2",
+      "resolved": "https://registry.npmjs.org/string-argv/-/string-argv-0.3.2.tgz",
+      "integrity": "sha512-aqD2Q0144Z+/RqG52NeHEkZauTAUWJO8c6yTftGJKO3Tja5tUgIfmIl6kExvhtxSDP7fXB6DvzkfMpCd/F3G+Q==",
       "dev": true,
-      "license": "MIT"
+      "license": "MIT",
+      "engines": {
+        "node": ">=0.6.19"
+      }
     },
-    "node_modules/object-inspect": {
-      "version": "1.13.4",
-      "resolved": "https://registry.npmjs.org/object-inspect/-/object-inspect-1.13.4.tgz",
-      "integrity": "sha512-W67iLl4J2EXEGTbfeHCffrjDfitvLANg0UlX3wFUUSTx92KXRFegMHUVgSqE+wvhAbi4WqjGg9czysTV2Epbew==",
+    "node_modules/string-width": {
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/string-width/-/string-width-7.2.0.tgz",
+      "integrity": "sha512-tsaTIkKW9b4N+AEj+SVA+WhJzV7/zMhcSu78mLKWSk7cXMOSHsBKFWUs0fWwq8QyK3MgJBQRX6Gbi4kYbdvGkQ==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "emoji-regex": "^10.3.0",
+        "get-east-asian-width": "^1.0.0",
+        "strip-ansi": "^7.1.0"
+      },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=18"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/object-keys": {
-      "version": "1.1.1",
-      "resolved": "https://registry.npmjs.org/object-keys/-/object-keys-1.1.1.tgz",
-      "integrity": "sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==",
+    "node_modules/string.prototype.codepointat": {
+      "version": "0.2.1",
+      "resolved": "https://registry.npmjs.org/string.prototype.codepointat/-/string.prototype.codepointat-0.2.1.tgz",
+      "integrity": "sha512-2cBVCj6I4IOvEnjgO/hWqXjqBGsY+zwPmHl12Srk9IXSZ56Jwwmy+66XO5Iut/oQVR7t5ihYdLB0GMa4alEUcg==",
+      "license": "MIT"
+    },
+    "node_modules/string.prototype.includes": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/string.prototype.includes/-/string.prototype.includes-2.0.1.tgz",
+      "integrity": "sha512-o7+c9bW6zpAdJHTtujeePODAhkuicdAryFsfVKwA+wGw89wJ4GTY484WTucM9hLtDEOpOvI+aHnzqnC5lHp4Rg==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "call-bind": "^1.0.7",
+        "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.3"
+      },
       "engines": {
         "node": ">= 0.4"
       }
     },
-    "node_modules/object.assign": {
-      "version": "4.1.7",
-      "resolved": "https://registry.npmjs.org/object.assign/-/object.assign-4.1.7.tgz",
-      "integrity": "sha512-nK28WOo+QIjBkDduTINE4JkF/UJJKyf2EJxvJKfblDpyg0Q+pkOHNTL0Qwy6NP6FhE/EnzV73BxxqcJaXY9anw==",
+    "node_modules/string.prototype.trim": {
+      "version": "1.2.10",
+      "resolved": "https://registry.npmjs.org/string.prototype.trim/-/string.prototype.trim-1.2.10.tgz",
+      "integrity": "sha512-Rs66F0P/1kedk5lyYyH9uBzuiI/kNRmwJAR9quK6VOtIpZ2G+hMZd+HQbbv25MgCA6gEffoMZYxlTod4WcdrKA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
         "call-bind": "^1.0.8",
-        "call-bound": "^1.0.3",
+        "call-bound": "^1.0.2",
+        "define-data-property": "^1.1.4",
         "define-properties": "^1.2.1",
+        "es-abstract": "^1.23.5",
         "es-object-atoms": "^1.0.0",
-        "has-symbols": "^1.1.0",
-        "object-keys": "^1.1.1"
+        "has-property-descriptors": "^1.0.2"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2487,16 +10935,16 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/object.fromentries": {
-      "version": "2.0.8",
-      "resolved": "https://registry.npmjs.org/object.fromentries/-/object.fromentries-2.0.8.tgz",
-      "integrity": "sha512-k6E21FzySsSK5a21KRADBd/NGneRegFO5pLHfdQLpRDETUNJueLXs3WCzyQ3tFRDYgbq3KHGXfTbi2bs8WQ6rQ==",
+    "node_modules/string.prototype.trimend": {
+      "version": "1.0.9",
+      "resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.9.tgz",
+      "integrity": "sha512-G7Ok5C6E/j4SGfyLCloXTrngQIQU3PWtXGst3yM7Bea9FRURf1S42ZHlZZtsNque2FN2PoUhfZXYLNWwEr4dLQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.7",
+        "call-bind": "^1.0.8",
+        "call-bound": "^1.0.2",
         "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.2",
         "es-object-atoms": "^1.0.0"
       },
       "engines": {
@@ -2506,31 +10954,15 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/object.groupby": {
-      "version": "1.0.3",
-      "resolved": "https://registry.npmjs.org/object.groupby/-/object.groupby-1.0.3.tgz",
-      "integrity": "sha512-+Lhy3TQTuzXI5hevh8sBGqbmurHbbIjAi0Z4S63nthVLmLxfbj4T54a4CfZrXIrt9iP4mVAPYMo/v99taj3wjQ==",
+    "node_modules/string.prototype.trimstart": {
+      "version": "1.0.8",
+      "resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.8.tgz",
+      "integrity": "sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
         "call-bind": "^1.0.7",
         "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.2"
-      },
-      "engines": {
-        "node": ">= 0.4"
-      }
-    },
-    "node_modules/object.values": {
-      "version": "1.2.1",
-      "resolved": "https://registry.npmjs.org/object.values/-/object.values-1.2.1.tgz",
-      "integrity": "sha512-gXah6aZrcUxjWg2zR2MwouP2eHlCBzdV4pygudehaKXSGW4v2AsRQUK+lwwXhii6KFZcunEnmSUoYp5CXibxtA==",
-      "dev": true,
-      "license": "MIT",
-      "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.3",
-        "define-properties": "^1.2.1",
         "es-object-atoms": "^1.0.0"
       },
       "engines": {
@@ -2540,370 +10972,360 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/once": {
-      "version": "1.4.0",
-      "resolved": "https://registry.npmjs.org/once/-/once-1.4.0.tgz",
-      "integrity": "sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==",
-      "dev": true,
-      "license": "ISC",
-      "dependencies": {
-        "wrappy": "1"
-      }
-    },
-    "node_modules/optionator": {
-      "version": "0.9.4",
-      "resolved": "https://registry.npmjs.org/optionator/-/optionator-0.9.4.tgz",
-      "integrity": "sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==",
-      "dev": true,
+    "node_modules/stringify-entities": {
+      "version": "4.0.4",
+      "resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-4.0.4.tgz",
+      "integrity": "sha512-IwfBptatlO+QCJUo19AqvrPNqlVMpW9YEL2LIVY+Rpv2qsjCGxaDLNRgeGsQWJhfItebuJhsGSLjaBbNSQ+ieg==",
       "license": "MIT",
       "dependencies": {
-        "deep-is": "^0.1.3",
-        "fast-levenshtein": "^2.0.6",
-        "levn": "^0.4.1",
-        "prelude-ls": "^1.2.1",
-        "type-check": "^0.4.0",
-        "word-wrap": "^1.2.5"
+        "character-entities-html4": "^2.0.0",
+        "character-entities-legacy": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.8.0"
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/own-keys": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/own-keys/-/own-keys-1.0.1.tgz",
-      "integrity": "sha512-qFOyK5PjiWZd+QQIh+1jhdb9LpxTF0qs7Pm8o5QHYZ0M3vKqSqzsZaEB6oWlxZ+q2sJBMI/Ktgd2N5ZwQoRHfg==",
+    "node_modules/strip-ansi": {
+      "version": "7.1.2",
+      "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-7.1.2.tgz",
+      "integrity": "sha512-gmBGslpoQJtgnMAvOVqGZpEz9dyoKTCzy2nfz/n8aIFhN/jCE/rCmcxabB6jOOHV+0WNnylOxaxBQPSvcWklhA==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "get-intrinsic": "^1.2.6",
-        "object-keys": "^1.1.1",
-        "safe-push-apply": "^1.0.0"
+        "ansi-regex": "^6.0.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=12"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/chalk/strip-ansi?sponsor=1"
       }
     },
-    "node_modules/p-limit": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz",
-      "integrity": "sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==",
+    "node_modules/strip-bom-string": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/strip-bom-string/-/strip-bom-string-1.0.0.tgz",
+      "integrity": "sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==",
+      "engines": {
+        "node": ">=0.10.0"
+      }
+    },
+    "node_modules/strip-json-comments": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz",
+      "integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==",
       "dev": true,
       "license": "MIT",
-      "dependencies": {
-        "yocto-queue": "^0.1.0"
-      },
       "engines": {
-        "node": ">=10"
+        "node": ">=8"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/p-locate": {
-      "version": "5.0.0",
-      "resolved": "https://registry.npmjs.org/p-locate/-/p-locate-5.0.0.tgz",
-      "integrity": "sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==",
-      "dev": true,
+    "node_modules/strnum": {
+      "version": "2.2.2",
+      "resolved": "https://registry.npmjs.org/strnum/-/strnum-2.2.2.tgz",
+      "integrity": "sha512-DnR90I+jtXNSTXWdwrEy9FakW7UX+qUZg28gj5fk2vxxl7uS/3bpI4fjFYVmdK9etptYBPNkpahuQnEwhwECqA==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/NaturalIntelligence"
+        }
+      ],
+      "license": "MIT"
+    },
+    "node_modules/style-to-js": {
+      "version": "1.1.21",
+      "resolved": "https://registry.npmjs.org/style-to-js/-/style-to-js-1.1.21.tgz",
+      "integrity": "sha512-RjQetxJrrUJLQPHbLku6U/ocGtzyjbJMP9lCNK7Ag0CNh690nSH8woqWH9u16nMjYBAok+i7JO1NP2pOy8IsPQ==",
       "license": "MIT",
       "dependencies": {
-        "p-limit": "^3.0.2"
-      },
-      "engines": {
-        "node": ">=10"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+        "style-to-object": "1.0.14"
       }
     },
-    "node_modules/parent-module": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/parent-module/-/parent-module-1.0.1.tgz",
-      "integrity": "sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==",
-      "dev": true,
+    "node_modules/style-to-object": {
+      "version": "1.0.14",
+      "resolved": "https://registry.npmjs.org/style-to-object/-/style-to-object-1.0.14.tgz",
+      "integrity": "sha512-LIN7rULI0jBscWQYaSswptyderlarFkjQ+t79nzty8tcIAceVomEVlLzH5VP4Cmsv6MtKhs7qaAiwlcp+Mgaxw==",
       "license": "MIT",
       "dependencies": {
-        "callsites": "^3.0.0"
-      },
-      "engines": {
-        "node": ">=6"
+        "inline-style-parser": "0.2.7"
       }
     },
-    "node_modules/parse-entities": {
-      "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/parse-entities/-/parse-entities-2.0.0.tgz",
-      "integrity": "sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==",
+    "node_modules/suf-log": {
+      "version": "2.5.3",
+      "resolved": "https://registry.npmjs.org/suf-log/-/suf-log-2.5.3.tgz",
+      "integrity": "sha512-KvC8OPjzdNOe+xQ4XWJV2whQA0aM1kGVczMQ8+dStAO6KfEB140JEVQ9dE76ONZ0/Ylf67ni4tILPJB41U0eow==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "character-entities": "^1.0.0",
-        "character-entities-legacy": "^1.0.0",
-        "character-reference-invalid": "^1.0.0",
-        "is-alphanumerical": "^1.0.0",
-        "is-decimal": "^1.0.0",
-        "is-hexadecimal": "^1.0.0"
-      },
-      "funding": {
-        "type": "github",
-        "url": "https://github.com/sponsors/wooorm"
+        "s.color": "0.0.15"
       }
     },
-    "node_modules/path-exists": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/path-exists/-/path-exists-4.0.0.tgz",
-      "integrity": "sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==",
+    "node_modules/supports-color": {
+      "version": "7.2.0",
+      "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
+      "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "has-flag": "^4.0.0"
+      },
       "engines": {
         "node": ">=8"
       }
     },
-    "node_modules/path-is-absolute": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/path-is-absolute/-/path-is-absolute-1.0.1.tgz",
-      "integrity": "sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==",
-      "dev": true,
+    "node_modules/svg-parser": {
+      "version": "2.0.4",
+      "resolved": "https://registry.npmjs.org/svg-parser/-/svg-parser-2.0.4.tgz",
+      "integrity": "sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ==",
+      "dev": true
+    },
+    "node_modules/svgo": {
+      "version": "4.0.1",
+      "resolved": "https://registry.npmjs.org/svgo/-/svgo-4.0.1.tgz",
+      "integrity": "sha512-XDpWUOPC6FEibaLzjfe0ucaV0YrOjYotGJO1WpF0Zd+n6ZGEQUsSugaoLq9QkEZtAfQIxT42UChcssDVPP3+/w==",
       "license": "MIT",
+      "dependencies": {
+        "commander": "^11.1.0",
+        "css-select": "^5.1.0",
+        "css-tree": "^3.0.1",
+        "css-what": "^6.1.0",
+        "csso": "^5.0.5",
+        "picocolors": "^1.1.1",
+        "sax": "^1.5.0"
+      },
+      "bin": {
+        "svgo": "bin/svgo.js"
+      },
       "engines": {
-        "node": ">=0.10.0"
+        "node": ">=16"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/svgo"
       }
     },
-    "node_modules/path-key": {
-      "version": "3.1.1",
-      "resolved": "https://registry.npmjs.org/path-key/-/path-key-3.1.1.tgz",
-      "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==",
+    "node_modules/synckit": {
+      "version": "0.11.12",
+      "resolved": "https://registry.npmjs.org/synckit/-/synckit-0.11.12.tgz",
+      "integrity": "sha512-Bh7QjT8/SuKUIfObSXNHNSK6WHo6J1tHCqJsuaFDP7gP0fkzSfTxI8y85JrppZ0h8l0maIgc2tfuZQ6/t3GtnQ==",
       "dev": true,
       "license": "MIT",
+      "dependencies": {
+        "@pkgr/core": "^0.2.9"
+      },
       "engines": {
-        "node": ">=8"
+        "node": "^14.18.0 || >=16.0.0"
+      },
+      "funding": {
+        "url": "https://opencollective.com/synckit"
       }
     },
-    "node_modules/path-parse": {
-      "version": "1.0.7",
-      "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz",
-      "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==",
-      "dev": true,
-      "license": "MIT"
+    "node_modules/tar": {
+      "version": "7.5.12",
+      "resolved": "https://registry.npmjs.org/tar/-/tar-7.5.12.tgz",
+      "integrity": "sha512-9TsuLcdhOn4XztcQqhNyq1KOwOOED/3k58JAvtULiYqbO8B/0IBAAIE1hj0Svmm58k27TmcigyDI0deMlgG3uw==",
+      "license": "BlueOak-1.0.0",
+      "dependencies": {
+        "@isaacs/fs-minipass": "^4.0.0",
+        "chownr": "^3.0.0",
+        "minipass": "^7.1.2",
+        "minizlib": "^3.1.0",
+        "yallist": "^5.0.0"
+      },
+      "engines": {
+        "node": ">=18"
+      }
     },
-    "node_modules/possible-typed-array-names": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/possible-typed-array-names/-/possible-typed-array-names-1.1.0.tgz",
-      "integrity": "sha512-/+5VFTchJDoVj3bhoqi6UeymcD00DAwb1nJwamzPvHEszJ4FpF6SNNbUbOS8yI56qHzdV8eK0qEfOSiodkTdxg==",
-      "dev": true,
+    "node_modules/throttleit": {
+      "version": "2.1.0",
+      "resolved": "https://registry.npmjs.org/throttleit/-/throttleit-2.1.0.tgz",
+      "integrity": "sha512-nt6AMGKW1p/70DF/hGBdJB57B8Tspmbp5gfJ8ilhLnt7kkr2ye7hzD6NVG8GGErk2HWF34igrL2CXmNIkzKqKw==",
       "license": "MIT",
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/sindresorhus"
       }
     },
-    "node_modules/prelude-ls": {
-      "version": "1.2.1",
-      "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.2.1.tgz",
-      "integrity": "sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==",
-      "dev": true,
+    "node_modules/tiny-inflate": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/tiny-inflate/-/tiny-inflate-1.0.3.tgz",
+      "integrity": "sha512-pkY1fj1cKHb2seWDy0B16HeWyczlJA9/WW3u3c4z/NiWDsO3DOU5D7nhTLE9CF0yXv/QZFY7sEJmj24dK+Rrqw==",
+      "license": "MIT"
+    },
+    "node_modules/tinyclip": {
+      "version": "0.1.12",
+      "resolved": "https://registry.npmjs.org/tinyclip/-/tinyclip-0.1.12.tgz",
+      "integrity": "sha512-Ae3OVUqifDw0wBriIBS7yVaW44Dp6eSHQcyq4Igc7eN2TJH/2YsicswaW+J/OuMvhpDPOKEgpAZCjkb4hpoyeA==",
       "license": "MIT",
       "engines": {
-        "node": ">= 0.8.0"
+        "node": "^16.14.0 || >= 17.3.0"
       }
     },
-    "node_modules/punycode": {
-      "version": "2.3.1",
-      "resolved": "https://registry.npmjs.org/punycode/-/punycode-2.3.1.tgz",
-      "integrity": "sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==",
-      "dev": true,
+    "node_modules/tinyexec": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/tinyexec/-/tinyexec-1.0.4.tgz",
+      "integrity": "sha512-u9r3uZC0bdpGOXtlxUIdwf9pkmvhqJdrVCH9fapQtgy/OeTTMZ1nqH7agtvEfmGui6e1XxjcdrlxvxJvc3sMqw==",
       "license": "MIT",
       "engines": {
-        "node": ">=6"
+        "node": ">=18"
       }
     },
-    "node_modules/queue-microtask": {
-      "version": "1.2.3",
-      "resolved": "https://registry.npmjs.org/queue-microtask/-/queue-microtask-1.2.3.tgz",
-      "integrity": "sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==",
-      "dev": true,
-      "funding": [
-        {
-          "type": "github",
-          "url": "https://github.com/sponsors/feross"
-        },
-        {
-          "type": "patreon",
-          "url": "https://www.patreon.com/feross"
-        },
-        {
-          "type": "consulting",
-          "url": "https://feross.org/support"
-        }
-      ],
-      "license": "MIT"
-    },
-    "node_modules/reflect.getprototypeof": {
-      "version": "1.0.10",
-      "resolved": "https://registry.npmjs.org/reflect.getprototypeof/-/reflect.getprototypeof-1.0.10.tgz",
-      "integrity": "sha512-00o4I+DVrefhv+nX0ulyi3biSHCPDe+yLv5o/p6d/UVlirijB8E16FtfwSAi4g3tcqrQ4lRAqQSoFEZJehYEcw==",
-      "dev": true,
+    "node_modules/tinyglobby": {
+      "version": "0.2.15",
+      "resolved": "https://registry.npmjs.org/tinyglobby/-/tinyglobby-0.2.15.tgz",
+      "integrity": "sha512-j2Zq4NyQYG5XMST4cbs02Ak8iJUdxRM0XI5QyxXuZOzKOINmWurp3smXu3y5wDcJrptwpSjgXHzIQxR0omXljQ==",
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.9",
-        "es-errors": "^1.3.0",
-        "es-object-atoms": "^1.0.0",
-        "get-intrinsic": "^1.2.7",
-        "get-proto": "^1.0.1",
-        "which-builtin-type": "^1.2.1"
+        "fdir": "^6.5.0",
+        "picomatch": "^4.0.3"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=12.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/sponsors/SuperchupuDev"
       }
     },
-    "node_modules/regexp.prototype.flags": {
-      "version": "1.5.4",
-      "resolved": "https://registry.npmjs.org/regexp.prototype.flags/-/regexp.prototype.flags-1.5.4.tgz",
-      "integrity": "sha512-dYqgNSZbDwkaJ2ceRd9ojCGjBq+mOm9LmtXnAnEGyHhN/5R7iDW2TRw3h+o/jCFxus3P2LfWIIiwowAjANm7IA==",
+    "node_modules/to-regex-range": {
+      "version": "5.0.1",
+      "resolved": "https://registry.npmjs.org/to-regex-range/-/to-regex-range-5.0.1.tgz",
+      "integrity": "sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "define-properties": "^1.2.1",
-        "es-errors": "^1.3.0",
-        "get-proto": "^1.0.1",
-        "gopd": "^1.2.0",
-        "set-function-name": "^2.0.2"
+        "is-number": "^7.0.0"
       },
       "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "node": ">=8.0"
       }
     },
-    "node_modules/regexpp": {
-      "version": "3.2.0",
-      "resolved": "https://registry.npmjs.org/regexpp/-/regexpp-3.2.0.tgz",
-      "integrity": "sha512-pq2bWo9mVD43nbts2wGv17XLiNLya+GklZ8kaDLV2Z08gDCsGpnKn9BFMepvWuHCbyVvY7J5o5+BVvoQbmlJLg==",
-      "dev": true,
+    "node_modules/trim-lines": {
+      "version": "3.0.1",
+      "resolved": "https://registry.npmjs.org/trim-lines/-/trim-lines-3.0.1.tgz",
+      "integrity": "sha512-kRj8B+YHZCc9kQYdWfJB2/oUl9rA99qbowYYBtr4ui4mZyAQ2JpvVBd/6U2YloATfqBhBTSMhTpgBHtU0Mf3Rg==",
       "license": "MIT",
-      "engines": {
-        "node": ">=8"
-      },
       "funding": {
-        "url": "https://github.com/sponsors/mysticatea"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/resolve": {
-      "version": "1.22.8",
-      "resolved": "https://registry.npmjs.org/resolve/-/resolve-1.22.8.tgz",
-      "integrity": "sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==",
-      "dev": true,
+    "node_modules/trough": {
+      "version": "2.2.0",
+      "resolved": "https://registry.npmjs.org/trough/-/trough-2.2.0.tgz",
+      "integrity": "sha512-tmMpK00BjZiUyVyvrBK7knerNgmgvcV/KLVyuma/SC+TQN167GrMRciANTz09+k3zW8L8t60jWO1GpfkZdjTaw==",
       "license": "MIT",
-      "dependencies": {
-        "is-core-module": "^2.13.0",
-        "path-parse": "^1.0.7",
-        "supports-preserve-symlinks-flag": "^1.0.0"
-      },
-      "bin": {
-        "resolve": "bin/resolve"
-      },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/resolve-from": {
-      "version": "4.0.0",
-      "resolved": "https://registry.npmjs.org/resolve-from/-/resolve-from-4.0.0.tgz",
-      "integrity": "sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==",
+    "node_modules/ts-api-utils": {
+      "version": "2.4.0",
+      "resolved": "https://registry.npmjs.org/ts-api-utils/-/ts-api-utils-2.4.0.tgz",
+      "integrity": "sha512-3TaVTaAv2gTiMB35i3FiGJaRfwb3Pyn/j3m/bfAvGe8FB7CF6u+LMYqYlDh7reQf7UNvoTvdfAqHGmPGOSsPmA==",
       "dev": true,
       "license": "MIT",
       "engines": {
-        "node": ">=4"
+        "node": ">=18.12"
+      },
+      "peerDependencies": {
+        "typescript": ">=4.8.4"
       }
     },
-    "node_modules/reusify": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/reusify/-/reusify-1.0.4.tgz",
-      "integrity": "sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==",
-      "dev": true,
+    "node_modules/tsconfck": {
+      "version": "3.1.6",
+      "resolved": "https://registry.npmjs.org/tsconfck/-/tsconfck-3.1.6.tgz",
+      "integrity": "sha512-ks6Vjr/jEw0P1gmOVwutM3B7fWxoWBL2KRDb1JfqGVawBmO5UsvmWOQFGHBPl5yxYz4eERr19E6L7NMv+Fej4w==",
       "license": "MIT",
+      "bin": {
+        "tsconfck": "bin/tsconfck.js"
+      },
       "engines": {
-        "iojs": ">=1.0.0",
-        "node": ">=0.10.0"
+        "node": "^18 || >=20"
+      },
+      "peerDependencies": {
+        "typescript": "^5.0.0"
+      },
+      "peerDependenciesMeta": {
+        "typescript": {
+          "optional": true
+        }
       }
     },
-    "node_modules/rimraf": {
-      "version": "3.0.2",
-      "resolved": "https://registry.npmjs.org/rimraf/-/rimraf-3.0.2.tgz",
-      "integrity": "sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==",
-      "deprecated": "Rimraf versions prior to v4 are no longer supported",
+    "node_modules/tslib": {
+      "version": "2.8.1",
+      "resolved": "https://registry.npmjs.org/tslib/-/tslib-2.8.1.tgz",
+      "integrity": "sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==",
+      "devOptional": true,
+      "license": "0BSD"
+    },
+    "node_modules/type-check": {
+      "version": "0.4.0",
+      "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
+      "integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
       "dev": true,
-      "license": "ISC",
+      "license": "MIT",
       "dependencies": {
-        "glob": "^7.1.3"
-      },
-      "bin": {
-        "rimraf": "bin.js"
+        "prelude-ls": "^1.2.1"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/isaacs"
+      "engines": {
+        "node": ">= 0.8.0"
       }
     },
-    "node_modules/run-parallel": {
-      "version": "1.2.0",
-      "resolved": "https://registry.npmjs.org/run-parallel/-/run-parallel-1.2.0.tgz",
-      "integrity": "sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==",
+    "node_modules/typed-array-buffer": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/typed-array-buffer/-/typed-array-buffer-1.0.3.tgz",
+      "integrity": "sha512-nAYYwfY3qnzX30IkA6AQZjVbtK6duGontcQm1WSG1MD94YLqK0515GNApXkoxKOWMusVssAHWLh9SeaoefYFGw==",
       "dev": true,
-      "funding": [
-        {
-          "type": "github",
-          "url": "https://github.com/sponsors/feross"
-        },
-        {
-          "type": "patreon",
-          "url": "https://www.patreon.com/feross"
-        },
-        {
-          "type": "consulting",
-          "url": "https://feross.org/support"
-        }
-      ],
       "license": "MIT",
       "dependencies": {
-        "queue-microtask": "^1.2.2"
+        "call-bound": "^1.0.3",
+        "es-errors": "^1.3.0",
+        "is-typed-array": "^1.1.14"
+      },
+      "engines": {
+        "node": ">= 0.4"
       }
     },
-    "node_modules/safe-array-concat": {
-      "version": "1.1.3",
-      "resolved": "https://registry.npmjs.org/safe-array-concat/-/safe-array-concat-1.1.3.tgz",
-      "integrity": "sha512-AURm5f0jYEOydBj7VQlVvDrjeFgthDdEF5H1dP+6mNpoXOMo1quQqJ4wvJDyRZ9+pO3kGWoOdmV08cSv2aJV6Q==",
+    "node_modules/typed-array-byte-length": {
+      "version": "1.0.3",
+      "resolved": "https://registry.npmjs.org/typed-array-byte-length/-/typed-array-byte-length-1.0.3.tgz",
+      "integrity": "sha512-BaXgOuIxz8n8pIq3e7Atg/7s+DpiYrxn4vdot3w9KbnBhcRQq6o3xemQdIfynqSeXeDrF32x+WvfzmOjPiY9lg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
         "call-bind": "^1.0.8",
-        "call-bound": "^1.0.2",
-        "get-intrinsic": "^1.2.6",
-        "has-symbols": "^1.1.0",
-        "isarray": "^2.0.5"
+        "for-each": "^0.3.3",
+        "gopd": "^1.2.0",
+        "has-proto": "^1.2.0",
+        "is-typed-array": "^1.1.14"
       },
       "engines": {
-        "node": ">=0.4"
+        "node": ">= 0.4"
       },
       "funding": {
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/safe-push-apply": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/safe-push-apply/-/safe-push-apply-1.0.0.tgz",
-      "integrity": "sha512-iKE9w/Z7xCzUMIZqdBsp6pEQvwuEebH4vdpjcDWnyzaI6yl6O9FHvVpmGelvEHNsoY6wGblkxR6Zty/h00WiSA==",
+    "node_modules/typed-array-byte-offset": {
+      "version": "1.0.4",
+      "resolved": "https://registry.npmjs.org/typed-array-byte-offset/-/typed-array-byte-offset-1.0.4.tgz",
+      "integrity": "sha512-bTlAFB/FBYMcuX81gbL4OcpH5PmlFHqlCCpAl8AlEzMz5k53oNDvN8p1PNOWLEmI2x4orp3raOFB51tv9X+MFQ==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "isarray": "^2.0.5"
+        "available-typed-arrays": "^1.0.7",
+        "call-bind": "^1.0.8",
+        "for-each": "^0.3.3",
+        "gopd": "^1.2.0",
+        "has-proto": "^1.2.0",
+        "is-typed-array": "^1.1.15",
+        "reflect.getprototypeof": "^1.0.9"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2912,16 +11334,19 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/safe-regex-test": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/safe-regex-test/-/safe-regex-test-1.1.0.tgz",
-      "integrity": "sha512-x/+Cz4YrimQxQccJf5mKEbIa1NzeCRNI5Ecl/ekmlYaampdNLPalVyIcCZNNH3MvmqBugV5TMYZXv0ljslUlaw==",
+    "node_modules/typed-array-length": {
+      "version": "1.0.7",
+      "resolved": "https://registry.npmjs.org/typed-array-length/-/typed-array-length-1.0.7.tgz",
+      "integrity": "sha512-3KS2b+kL7fsuk/eJZ7EQdnEmQoaho/r6KUef7hxvltNA5DR8NAUM+8wJMbJyZ4G9/7i3v5zPBIMN5aybAh2/Jg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "es-errors": "^1.3.0",
-        "is-regex": "^1.2.1"
+        "call-bind": "^1.0.7",
+        "for-each": "^0.3.3",
+        "gopd": "^1.0.1",
+        "is-typed-array": "^1.1.13",
+        "possible-typed-array-names": "^1.0.0",
+        "reflect.getprototypeof": "^1.0.6"
       },
       "engines": {
         "node": ">= 0.4"
@@ -2930,464 +11355,662 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/semver": {
-      "version": "6.3.1",
-      "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.1.tgz",
-      "integrity": "sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==",
-      "dev": true,
-      "license": "ISC",
+    "node_modules/typescript": {
+      "version": "5.9.3",
+      "resolved": "https://registry.npmjs.org/typescript/-/typescript-5.9.3.tgz",
+      "integrity": "sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==",
+      "devOptional": true,
+      "license": "Apache-2.0",
+      "peer": true,
       "bin": {
-        "semver": "bin/semver.js"
+        "tsc": "bin/tsc",
+        "tsserver": "bin/tsserver"
+      },
+      "engines": {
+        "node": ">=14.17"
       }
     },
-    "node_modules/set-function-length": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/set-function-length/-/set-function-length-1.2.2.tgz",
-      "integrity": "sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==",
+    "node_modules/typescript-eslint": {
+      "version": "8.53.1",
+      "resolved": "https://registry.npmjs.org/typescript-eslint/-/typescript-eslint-8.53.1.tgz",
+      "integrity": "sha512-gB+EVQfP5RDElh9ittfXlhZJdjSU4jUSTyE2+ia8CYyNvet4ElfaLlAIqDvQV9JPknKx0jQH1racTYe/4LaLSg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "define-data-property": "^1.1.4",
-        "es-errors": "^1.3.0",
-        "function-bind": "^1.1.2",
-        "get-intrinsic": "^1.2.4",
-        "gopd": "^1.0.1",
-        "has-property-descriptors": "^1.0.2"
+        "@typescript-eslint/eslint-plugin": "8.53.1",
+        "@typescript-eslint/parser": "8.53.1",
+        "@typescript-eslint/typescript-estree": "8.53.1",
+        "@typescript-eslint/utils": "8.53.1"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^18.18.0 || ^20.9.0 || >=21.1.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/typescript-eslint"
+      },
+      "peerDependencies": {
+        "eslint": "^8.57.0 || ^9.0.0",
+        "typescript": ">=4.8.4 <6.0.0"
       }
     },
-    "node_modules/set-function-name": {
-      "version": "2.0.2",
-      "resolved": "https://registry.npmjs.org/set-function-name/-/set-function-name-2.0.2.tgz",
-      "integrity": "sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==",
+    "node_modules/ufo": {
+      "version": "1.6.3",
+      "resolved": "https://registry.npmjs.org/ufo/-/ufo-1.6.3.tgz",
+      "integrity": "sha512-yDJTmhydvl5lJzBmy/hyOAA0d+aqCBuwl818haVdYCRrWV84o7YyeVm4QlVHStqNrrJSTb6jKuFAVqAFsr+K3Q==",
+      "license": "MIT"
+    },
+    "node_modules/ultrahtml": {
+      "version": "1.6.0",
+      "resolved": "https://registry.npmjs.org/ultrahtml/-/ultrahtml-1.6.0.tgz",
+      "integrity": "sha512-R9fBn90VTJrqqLDwyMph+HGne8eqY1iPfYhPzZrvKpIfwkWZbcYlfpsb8B9dTvBfpy1/hqAD7Wi8EKfP9e8zdw==",
+      "license": "MIT"
+    },
+    "node_modules/unbox-primitive": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/unbox-primitive/-/unbox-primitive-1.1.0.tgz",
+      "integrity": "sha512-nWJ91DjeOkej/TA8pXQ3myruKpKEYgqvpw9lz4OPHj/NWFNluYrjbz9j01CJ8yKQd2g4jFoOkINCTW2I5LEEyw==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
-        "define-data-property": "^1.1.4",
-        "es-errors": "^1.3.0",
-        "functions-have-names": "^1.2.3",
-        "has-property-descriptors": "^1.0.2"
+        "call-bound": "^1.0.3",
+        "has-bigints": "^1.0.2",
+        "has-symbols": "^1.1.0",
+        "which-boxed-primitive": "^1.1.1"
       },
       "engines": {
         "node": ">= 0.4"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/set-proto": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/set-proto/-/set-proto-1.0.0.tgz",
-      "integrity": "sha512-RJRdvCo6IAnPdsvP/7m6bsQqNnn1FCBX5ZNtFL98MmFF/4xAIJTIg1YbHW5DC2W5SKZanrC6i4HsJqlajw/dZw==",
-      "dev": true,
+    "node_modules/uncrypto": {
+      "version": "0.1.3",
+      "resolved": "https://registry.npmjs.org/uncrypto/-/uncrypto-0.1.3.tgz",
+      "integrity": "sha512-Ql87qFHB3s/De2ClA9e0gsnS6zXG27SkTiSJwjCc9MebbfapQfuPzumMIUMi38ezPZVNFcHI9sUIepeQfw8J8Q==",
+      "license": "MIT"
+    },
+    "node_modules/undici": {
+      "version": "7.24.5",
+      "resolved": "https://registry.npmjs.org/undici/-/undici-7.24.5.tgz",
+      "integrity": "sha512-3IWdCpjgxp15CbJnsi/Y9TCDE7HWVN19j1hmzVhoAkY/+CJx449tVxT5wZc1Gwg8J+P0LWvzlBzxYRnHJ+1i7Q==",
       "license": "MIT",
-      "dependencies": {
-        "dunder-proto": "^1.0.1",
-        "es-errors": "^1.3.0",
-        "es-object-atoms": "^1.0.0"
-      },
       "engines": {
-        "node": ">= 0.4"
+        "node": ">=20.18.1"
       }
     },
-    "node_modules/shebang-command": {
+    "node_modules/undici-types": {
+      "version": "7.18.2",
+      "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-7.18.2.tgz",
+      "integrity": "sha512-AsuCzffGHJybSaRrmr5eHr81mwJU3kjw6M+uprWvCXiNeN9SOGwQ3Jn8jb8m3Z6izVgknn1R0FTCEAP2QrLY/w==",
+      "license": "MIT"
+    },
+    "node_modules/unicode-trie": {
       "version": "2.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-command/-/shebang-command-2.0.0.tgz",
-      "integrity": "sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==",
-      "dev": true,
+      "resolved": "https://registry.npmjs.org/unicode-trie/-/unicode-trie-2.0.0.tgz",
+      "integrity": "sha512-x7bc76x0bm4prf1VLg79uhAzKw8DVboClSN5VxJuQ+LKDOVEW9CdH+VY7SP+vX7xCYQqzzgQpFqz15zeLvAtZQ==",
       "license": "MIT",
       "dependencies": {
-        "shebang-regex": "^3.0.0"
+        "pako": "^0.2.5",
+        "tiny-inflate": "^1.0.0"
+      }
+    },
+    "node_modules/unified": {
+      "version": "11.0.5",
+      "resolved": "https://registry.npmjs.org/unified/-/unified-11.0.5.tgz",
+      "integrity": "sha512-xKvGhPWw3k84Qjh8bI3ZeJjqnyadK+GEFtazSfZv/rKeTkTjOJho6mFqh2SM96iIcZokxiOpg78GazTSg8+KHA==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "^3.0.0",
+        "bail": "^2.0.0",
+        "devlop": "^1.0.0",
+        "extend": "^3.0.0",
+        "is-plain-obj": "^4.0.0",
+        "trough": "^2.0.0",
+        "vfile": "^6.0.0"
       },
-      "engines": {
-        "node": ">=8"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/shebang-regex": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/shebang-regex/-/shebang-regex-3.0.0.tgz",
-      "integrity": "sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==",
-      "dev": true,
+    "node_modules/unifont": {
+      "version": "0.7.4",
+      "resolved": "https://registry.npmjs.org/unifont/-/unifont-0.7.4.tgz",
+      "integrity": "sha512-oHeis4/xl42HUIeHuNZRGEvxj5AaIKR+bHPNegRq5LV1gdc3jundpONbjglKpihmJf+dswygdMJn3eftGIMemg==",
       "license": "MIT",
-      "engines": {
-        "node": ">=8"
+      "dependencies": {
+        "css-tree": "^3.1.0",
+        "ofetch": "^1.5.1",
+        "ohash": "^2.0.11"
       }
     },
-    "node_modules/side-channel": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/side-channel/-/side-channel-1.1.0.tgz",
-      "integrity": "sha512-ZX99e6tRweoUXqR+VBrslhda51Nh5MTQwou5tnUDgbtyM0dBgmhEDtWGP/xbKn6hqfPRHujUNwz5fy/wbbhnpw==",
-      "dev": true,
+    "node_modules/unist-util-find-after": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-find-after/-/unist-util-find-after-5.0.0.tgz",
+      "integrity": "sha512-amQa0Ep2m6hE2g72AugUItjbuM8X8cGQnFoHk0pGfrFeT9GZhzN5SW8nRsiGKK7Aif4CrACPENkA6P/Lw6fHGQ==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "object-inspect": "^1.13.3",
-        "side-channel-list": "^1.0.0",
-        "side-channel-map": "^1.0.1",
-        "side-channel-weakmap": "^1.0.2"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/unist": "^3.0.0",
+        "unist-util-is": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/side-channel-list": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/side-channel-list/-/side-channel-list-1.0.0.tgz",
-      "integrity": "sha512-FCLHtRD/gnpCiCHEiJLOwdmFP+wzCmDEkc9y7NsYxeF4u7Btsn1ZuwgwJGxImImHicJArLP4R0yX4c2KCrMrTA==",
-      "dev": true,
+    "node_modules/unist-util-is": {
+      "version": "6.0.1",
+      "resolved": "https://registry.npmjs.org/unist-util-is/-/unist-util-is-6.0.1.tgz",
+      "integrity": "sha512-LsiILbtBETkDz8I9p1dQ0uyRUWuaQzd/cuEeS1hoRSyW5E5XGmTzlwY1OrNzzakGowI9Dr/I8HVaw4hTtnxy8g==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "object-inspect": "^1.13.3"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/unist": "^3.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/side-channel-map": {
-      "version": "1.0.1",
-      "resolved": "https://registry.npmjs.org/side-channel-map/-/side-channel-map-1.0.1.tgz",
-      "integrity": "sha512-VCjCNfgMsby3tTdo02nbjtM/ewra6jPHmpThenkTYh8pG9ucZ/1P8So4u4FGBek/BjpOVsDCMoLA/iuBKIFXRA==",
-      "dev": true,
+    "node_modules/unist-util-modify-children": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-modify-children/-/unist-util-modify-children-4.0.0.tgz",
+      "integrity": "sha512-+tdN5fGNddvsQdIzUF3Xx82CU9sMM+fA0dLgR9vOmT0oPT2jH+P1nd5lSqfCfXAw+93NhcXNY2qqvTUtE4cQkw==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "es-errors": "^1.3.0",
-        "get-intrinsic": "^1.2.5",
-        "object-inspect": "^1.13.3"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/unist": "^3.0.0",
+        "array-iterate": "^2.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/side-channel-weakmap": {
-      "version": "1.0.2",
-      "resolved": "https://registry.npmjs.org/side-channel-weakmap/-/side-channel-weakmap-1.0.2.tgz",
-      "integrity": "sha512-WPS/HvHQTYnHisLo9McqBHOJk2FkHO/tlpvldyrnem4aeQp4hai3gythswg6p01oSoTl58rcpiFAjF2br2Ak2A==",
-      "dev": true,
+    "node_modules/unist-util-position": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-position/-/unist-util-position-5.0.0.tgz",
+      "integrity": "sha512-fucsC7HjXvkB5R3kTCO7kUjRdrS0BJt3M/FPxmHMBOm8JQi2BsHAHFsy27E0EolP8rp0NzXsJ+jNPyDWvOJZPA==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.2",
-        "es-errors": "^1.3.0",
-        "get-intrinsic": "^1.2.5",
-        "object-inspect": "^1.13.3",
-        "side-channel-map": "^1.0.1"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/unist": "^3.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/stop-iteration-iterator": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/stop-iteration-iterator/-/stop-iteration-iterator-1.1.0.tgz",
-      "integrity": "sha512-eLoXW/DHyl62zxY4SCaIgnRhuMr6ri4juEYARS8E6sCEqzKpOiE521Ucofdx+KnDZl5xmvGYaaKCk5FEOxJCoQ==",
-      "dev": true,
+    "node_modules/unist-util-position-from-estree": {
+      "version": "2.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-position-from-estree/-/unist-util-position-from-estree-2.0.0.tgz",
+      "integrity": "sha512-KaFVRjoqLyF6YXCbVLNad/eS4+OfPQQn2yOd7zF/h5T/CSL2v8NpN6a5TPvtbXthAGw5nG+PuTtq+DdIZr+cRQ==",
       "license": "MIT",
       "dependencies": {
-        "es-errors": "^1.3.0",
-        "internal-slot": "^1.1.0"
+        "@types/unist": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/string.prototype.trim": {
-      "version": "1.2.10",
-      "resolved": "https://registry.npmjs.org/string.prototype.trim/-/string.prototype.trim-1.2.10.tgz",
-      "integrity": "sha512-Rs66F0P/1kedk5lyYyH9uBzuiI/kNRmwJAR9quK6VOtIpZ2G+hMZd+HQbbv25MgCA6gEffoMZYxlTod4WcdrKA==",
-      "dev": true,
+    "node_modules/unist-util-remove-position": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-remove-position/-/unist-util-remove-position-5.0.0.tgz",
+      "integrity": "sha512-Hp5Kh3wLxv0PHj9m2yZhhLt58KzPtEYKQQ4yxfYFEO7EvHwzyDYnduhHnY1mDxoqr7VUwVuHXk9RXKIiYS1N8Q==",
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.2",
-        "define-data-property": "^1.1.4",
-        "define-properties": "^1.2.1",
-        "es-abstract": "^1.23.5",
-        "es-object-atoms": "^1.0.0",
-        "has-property-descriptors": "^1.0.2"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@types/unist": "^3.0.0",
+        "unist-util-visit": "^5.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/string.prototype.trimend": {
-      "version": "1.0.9",
-      "resolved": "https://registry.npmjs.org/string.prototype.trimend/-/string.prototype.trimend-1.0.9.tgz",
-      "integrity": "sha512-G7Ok5C6E/j4SGfyLCloXTrngQIQU3PWtXGst3yM7Bea9FRURf1S42ZHlZZtsNque2FN2PoUhfZXYLNWwEr4dLQ==",
-      "dev": true,
+    "node_modules/unist-util-stringify-position": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-stringify-position/-/unist-util-stringify-position-4.0.0.tgz",
+      "integrity": "sha512-0ASV06AAoKCDkS2+xw5RXJywruurpbC4JZSm7nr7MOt1ojAzvyyaO+UxZf18j8FCF6kmzCZKcAgN/yu2gm2XgQ==",
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "call-bound": "^1.0.2",
-        "define-properties": "^1.2.1",
-        "es-object-atoms": "^1.0.0"
+        "@types/unist": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/unist-util-visit": {
+      "version": "5.1.0",
+      "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-5.1.0.tgz",
+      "integrity": "sha512-m+vIdyeCOpdr/QeQCu2EzxX/ohgS8KbnPDgFni4dQsfSCtpz8UqDyY5GjRru8PDKuYn7Fq19j1CQ+nJSsGKOzg==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "^3.0.0",
+        "unist-util-is": "^6.0.0",
+        "unist-util-visit-parents": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/string.prototype.trimstart": {
-      "version": "1.0.8",
-      "resolved": "https://registry.npmjs.org/string.prototype.trimstart/-/string.prototype.trimstart-1.0.8.tgz",
-      "integrity": "sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==",
-      "dev": true,
+    "node_modules/unist-util-visit-children": {
+      "version": "3.0.0",
+      "resolved": "https://registry.npmjs.org/unist-util-visit-children/-/unist-util-visit-children-3.0.0.tgz",
+      "integrity": "sha512-RgmdTfSBOg04sdPcpTSD1jzoNBjt9a80/ZCzp5cI9n1qPzLZWF9YdvWGN2zmTumP1HWhXKdUWexjy/Wy/lJ7tA==",
       "license": "MIT",
       "dependencies": {
-        "call-bind": "^1.0.7",
-        "define-properties": "^1.2.1",
-        "es-object-atoms": "^1.0.0"
+        "@types/unist": "^3.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
+      }
+    },
+    "node_modules/unist-util-visit-parents": {
+      "version": "6.0.2",
+      "resolved": "https://registry.npmjs.org/unist-util-visit-parents/-/unist-util-visit-parents-6.0.2.tgz",
+      "integrity": "sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==",
+      "license": "MIT",
+      "dependencies": {
+        "@types/unist": "^3.0.0",
+        "unist-util-is": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/strip-ansi": {
-      "version": "6.0.1",
-      "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz",
-      "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==",
+    "node_modules/unplugin": {
+      "version": "2.3.11",
+      "resolved": "https://registry.npmjs.org/unplugin/-/unplugin-2.3.11.tgz",
+      "integrity": "sha512-5uKD0nqiYVzlmCRs01Fhs2BdkEgBS3SAVP6ndrBsuK42iC2+JHyxM05Rm9G8+5mkmRtzMZGY8Ct5+mliZxU/Ww==",
       "dev": true,
-      "license": "MIT",
       "dependencies": {
-        "ansi-regex": "^5.0.1"
+        "@jridgewell/remapping": "^2.3.5",
+        "acorn": "^8.15.0",
+        "picomatch": "^4.0.3",
+        "webpack-virtual-modules": "^0.6.2"
       },
       "engines": {
-        "node": ">=8"
+        "node": ">=18.12.0"
       }
     },
-    "node_modules/strip-bom": {
-      "version": "3.0.0",
-      "resolved": "https://registry.npmjs.org/strip-bom/-/strip-bom-3.0.0.tgz",
-      "integrity": "sha512-vavAMRXOgBVNF6nyEEmL3DBK19iRpDcoIwW+swQ+CbGiu7lju6t+JklA1MHweoWtadgt4ISVUsXLyDq34ddcwA==",
+    "node_modules/unplugin-icons": {
+      "version": "23.0.1",
+      "resolved": "https://registry.npmjs.org/unplugin-icons/-/unplugin-icons-23.0.1.tgz",
+      "integrity": "sha512-rv0XEJepajKzDLvRUWASM8K+8+/CCfZn2jtogXqg6RIp7kpatRc/aFrVJn8ANQA09e++lPEEv9yX8cC9enc+QQ==",
       "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">=4"
+      "dependencies": {
+        "@antfu/install-pkg": "^1.1.0",
+        "@iconify/utils": "^3.1.0",
+        "local-pkg": "^1.1.2",
+        "obug": "^2.1.1",
+        "unplugin": "^2.3.11"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/antfu"
+      },
+      "peerDependencies": {
+        "@svgr/core": ">=7.0.0",
+        "@svgx/core": "^1.0.1",
+        "@vue/compiler-sfc": "^3.0.2",
+        "svelte": "^3.0.0 || ^4.0.0 || ^5.0.0"
+      },
+      "peerDependenciesMeta": {
+        "@svgr/core": {
+          "optional": true
+        },
+        "@svgx/core": {
+          "optional": true
+        },
+        "@vue/compiler-sfc": {
+          "optional": true
+        },
+        "svelte": {
+          "optional": true
+        }
       }
     },
-    "node_modules/strip-json-comments": {
-      "version": "3.1.1",
-      "resolved": "https://registry.npmjs.org/strip-json-comments/-/strip-json-comments-3.1.1.tgz",
-      "integrity": "sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==",
+    "node_modules/unplugin-icons/node_modules/@iconify/utils": {
+      "version": "3.1.0",
+      "resolved": "https://registry.npmjs.org/@iconify/utils/-/utils-3.1.0.tgz",
+      "integrity": "sha512-Zlzem1ZXhI1iHeeERabLNzBHdOa4VhQbqAcOQaMKuTuyZCpwKbC2R4Dd0Zo3g9EAc+Y4fiarO8HIHRAth7+skw==",
       "dev": true,
+      "dependencies": {
+        "@antfu/install-pkg": "^1.1.0",
+        "@iconify/types": "^2.0.0",
+        "mlly": "^1.8.0"
+      }
+    },
+    "node_modules/unstorage": {
+      "version": "1.17.4",
+      "resolved": "https://registry.npmjs.org/unstorage/-/unstorage-1.17.4.tgz",
+      "integrity": "sha512-fHK0yNg38tBiJKp/Vgsq4j0JEsCmgqH58HAn707S7zGkArbZsVr/CwINoi+nh3h98BRCwKvx1K3Xg9u3VV83sw==",
       "license": "MIT",
-      "engines": {
-        "node": ">=8"
+      "dependencies": {
+        "anymatch": "^3.1.3",
+        "chokidar": "^5.0.0",
+        "destr": "^2.0.5",
+        "h3": "^1.15.5",
+        "lru-cache": "^11.2.0",
+        "node-fetch-native": "^1.6.7",
+        "ofetch": "^1.5.1",
+        "ufo": "^1.6.3"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+      "peerDependencies": {
+        "@azure/app-configuration": "^1.8.0",
+        "@azure/cosmos": "^4.2.0",
+        "@azure/data-tables": "^13.3.0",
+        "@azure/identity": "^4.6.0",
+        "@azure/keyvault-secrets": "^4.9.0",
+        "@azure/storage-blob": "^12.26.0",
+        "@capacitor/preferences": "^6 || ^7 || ^8",
+        "@deno/kv": ">=0.9.0",
+        "@netlify/blobs": "^6.5.0 || ^7.0.0 || ^8.1.0 || ^9.0.0 || ^10.0.0",
+        "@planetscale/database": "^1.19.0",
+        "@upstash/redis": "^1.34.3",
+        "@vercel/blob": ">=0.27.1",
+        "@vercel/functions": "^2.2.12 || ^3.0.0",
+        "@vercel/kv": "^1 || ^2 || ^3",
+        "aws4fetch": "^1.0.20",
+        "db0": ">=0.2.1",
+        "idb-keyval": "^6.2.1",
+        "ioredis": "^5.4.2",
+        "uploadthing": "^7.4.4"
+      },
+      "peerDependenciesMeta": {
+        "@azure/app-configuration": {
+          "optional": true
+        },
+        "@azure/cosmos": {
+          "optional": true
+        },
+        "@azure/data-tables": {
+          "optional": true
+        },
+        "@azure/identity": {
+          "optional": true
+        },
+        "@azure/keyvault-secrets": {
+          "optional": true
+        },
+        "@azure/storage-blob": {
+          "optional": true
+        },
+        "@capacitor/preferences": {
+          "optional": true
+        },
+        "@deno/kv": {
+          "optional": true
+        },
+        "@netlify/blobs": {
+          "optional": true
+        },
+        "@planetscale/database": {
+          "optional": true
+        },
+        "@upstash/redis": {
+          "optional": true
+        },
+        "@vercel/blob": {
+          "optional": true
+        },
+        "@vercel/functions": {
+          "optional": true
+        },
+        "@vercel/kv": {
+          "optional": true
+        },
+        "aws4fetch": {
+          "optional": true
+        },
+        "db0": {
+          "optional": true
+        },
+        "idb-keyval": {
+          "optional": true
+        },
+        "ioredis": {
+          "optional": true
+        },
+        "uploadthing": {
+          "optional": true
+        }
       }
     },
-    "node_modules/supports-color": {
-      "version": "7.2.0",
-      "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-7.2.0.tgz",
-      "integrity": "sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==",
-      "dev": true,
-      "license": "MIT",
+    "node_modules/update-browserslist-db": {
+      "version": "1.2.3",
+      "resolved": "https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.2.3.tgz",
+      "integrity": "sha512-Js0m9cx+qOgDxo0eMiFGEueWztz+d4+M3rGlmKPT+T4IS/jP4ylw3Nwpu6cpTTP8R1MAC1kF4VbdLt3ARf209w==",
+      "funding": [
+        {
+          "type": "opencollective",
+          "url": "https://opencollective.com/browserslist"
+        },
+        {
+          "type": "tidelift",
+          "url": "https://tidelift.com/funding/github/npm/browserslist"
+        },
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/ai"
+        }
+      ],
       "dependencies": {
-        "has-flag": "^4.0.0"
+        "escalade": "^3.2.0",
+        "picocolors": "^1.1.1"
       },
-      "engines": {
-        "node": ">=8"
+      "bin": {
+        "update-browserslist-db": "cli.js"
+      },
+      "peerDependencies": {
+        "browserslist": ">= 4.21.0"
       }
     },
-    "node_modules/supports-preserve-symlinks-flag": {
-      "version": "1.0.0",
-      "resolved": "https://registry.npmjs.org/supports-preserve-symlinks-flag/-/supports-preserve-symlinks-flag-1.0.0.tgz",
-      "integrity": "sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==",
+    "node_modules/uri-js": {
+      "version": "4.4.1",
+      "resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz",
+      "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
       "dev": true,
-      "license": "MIT",
-      "engines": {
-        "node": ">= 0.4"
-      },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "license": "BSD-2-Clause",
+      "dependencies": {
+        "punycode": "^2.1.0"
       }
     },
-    "node_modules/text-table": {
-      "version": "0.2.0",
-      "resolved": "https://registry.npmjs.org/text-table/-/text-table-0.2.0.tgz",
-      "integrity": "sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==",
-      "dev": true,
+    "node_modules/util-deprecate": {
+      "version": "1.0.2",
+      "resolved": "https://registry.npmjs.org/util-deprecate/-/util-deprecate-1.0.2.tgz",
+      "integrity": "sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==",
       "license": "MIT"
     },
-    "node_modules/tsconfig-paths": {
-      "version": "3.15.0",
-      "resolved": "https://registry.npmjs.org/tsconfig-paths/-/tsconfig-paths-3.15.0.tgz",
-      "integrity": "sha512-2Ac2RgzDe/cn48GvOe3M+o82pEFewD3UPbyoUHHdKasHwJKjds4fLXWf/Ux5kATBKN20oaFGu+jbElp1pos0mg==",
-      "dev": true,
+    "node_modules/vfile": {
+      "version": "6.0.3",
+      "resolved": "https://registry.npmjs.org/vfile/-/vfile-6.0.3.tgz",
+      "integrity": "sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==",
       "license": "MIT",
       "dependencies": {
-        "@types/json5": "^0.0.29",
-        "json5": "^1.0.2",
-        "minimist": "^1.2.6",
-        "strip-bom": "^3.0.0"
+        "@types/unist": "^3.0.0",
+        "vfile-message": "^4.0.0"
+      },
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/type-check": {
-      "version": "0.4.0",
-      "resolved": "https://registry.npmjs.org/type-check/-/type-check-0.4.0.tgz",
-      "integrity": "sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==",
-      "dev": true,
+    "node_modules/vfile-location": {
+      "version": "5.0.3",
+      "resolved": "https://registry.npmjs.org/vfile-location/-/vfile-location-5.0.3.tgz",
+      "integrity": "sha512-5yXvWDEgqeiYiBe1lbxYF7UMAIm/IcopxMHrMQDq3nvKcjPKIhZklUKL+AE7J7uApI4kwe2snsK+eI6UTj9EHg==",
       "license": "MIT",
       "dependencies": {
-        "prelude-ls": "^1.2.1"
-      },
-      "engines": {
-        "node": ">= 0.8.0"
-      }
-    },
-    "node_modules/type-fest": {
-      "version": "0.20.2",
-      "resolved": "https://registry.npmjs.org/type-fest/-/type-fest-0.20.2.tgz",
-      "integrity": "sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==",
-      "dev": true,
-      "license": "(MIT OR CC0-1.0)",
-      "engines": {
-        "node": ">=10"
+        "@types/unist": "^3.0.0",
+        "vfile": "^6.0.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/sindresorhus"
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/typed-array-buffer": {
-      "version": "1.0.3",
-      "resolved": "https://registry.npmjs.org/typed-array-buffer/-/typed-array-buffer-1.0.3.tgz",
-      "integrity": "sha512-nAYYwfY3qnzX30IkA6AQZjVbtK6duGontcQm1WSG1MD94YLqK0515GNApXkoxKOWMusVssAHWLh9SeaoefYFGw==",
-      "dev": true,
+    "node_modules/vfile-message": {
+      "version": "4.0.3",
+      "resolved": "https://registry.npmjs.org/vfile-message/-/vfile-message-4.0.3.tgz",
+      "integrity": "sha512-QTHzsGd1EhbZs4AsQ20JX1rC3cOlt/IWJruk893DfLRr57lcnOeMaWG4K0JrRta4mIJZKth2Au3mM3u03/JWKw==",
       "license": "MIT",
       "dependencies": {
-        "call-bound": "^1.0.3",
-        "es-errors": "^1.3.0",
-        "is-typed-array": "^1.1.14"
+        "@types/unist": "^3.0.0",
+        "unist-util-stringify-position": "^4.0.0"
       },
-      "engines": {
-        "node": ">= 0.4"
+      "funding": {
+        "type": "opencollective",
+        "url": "https://opencollective.com/unified"
       }
     },
-    "node_modules/typed-array-byte-length": {
-      "version": "1.0.3",
-      "resolved": "https://registry.npmjs.org/typed-array-byte-length/-/typed-array-byte-length-1.0.3.tgz",
-      "integrity": "sha512-BaXgOuIxz8n8pIq3e7Atg/7s+DpiYrxn4vdot3w9KbnBhcRQq6o3xemQdIfynqSeXeDrF32x+WvfzmOjPiY9lg==",
-      "dev": true,
+    "node_modules/vite": {
+      "version": "7.3.1",
+      "resolved": "https://registry.npmjs.org/vite/-/vite-7.3.1.tgz",
+      "integrity": "sha512-w+N7Hifpc3gRjZ63vYBXA56dvvRlNWRczTdmCBBa+CotUzAPf5b7YMdMR/8CQoeYE5LX3W4wj6RYTgonm1b9DA==",
       "license": "MIT",
+      "peer": true,
       "dependencies": {
-        "call-bind": "^1.0.8",
-        "for-each": "^0.3.3",
-        "gopd": "^1.2.0",
-        "has-proto": "^1.2.0",
-        "is-typed-array": "^1.1.14"
+        "esbuild": "^0.27.0",
+        "fdir": "^6.5.0",
+        "picomatch": "^4.0.3",
+        "postcss": "^8.5.6",
+        "rollup": "^4.43.0",
+        "tinyglobby": "^0.2.15"
+      },
+      "bin": {
+        "vite": "bin/vite.js"
       },
       "engines": {
-        "node": ">= 0.4"
+        "node": "^20.19.0 || >=22.12.0"
       },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "url": "https://github.com/vitejs/vite?sponsor=1"
+      },
+      "optionalDependencies": {
+        "fsevents": "~2.3.3"
+      },
+      "peerDependencies": {
+        "@types/node": "^20.19.0 || >=22.12.0",
+        "jiti": ">=1.21.0",
+        "less": "^4.0.0",
+        "lightningcss": "^1.21.0",
+        "sass": "^1.70.0",
+        "sass-embedded": "^1.70.0",
+        "stylus": ">=0.54.8",
+        "sugarss": "^5.0.0",
+        "terser": "^5.16.0",
+        "tsx": "^4.8.1",
+        "yaml": "^2.4.2"
+      },
+      "peerDependenciesMeta": {
+        "@types/node": {
+          "optional": true
+        },
+        "jiti": {
+          "optional": true
+        },
+        "less": {
+          "optional": true
+        },
+        "lightningcss": {
+          "optional": true
+        },
+        "sass": {
+          "optional": true
+        },
+        "sass-embedded": {
+          "optional": true
+        },
+        "stylus": {
+          "optional": true
+        },
+        "sugarss": {
+          "optional": true
+        },
+        "terser": {
+          "optional": true
+        },
+        "tsx": {
+          "optional": true
+        },
+        "yaml": {
+          "optional": true
+        }
       }
     },
-    "node_modules/typed-array-byte-offset": {
-      "version": "1.0.4",
-      "resolved": "https://registry.npmjs.org/typed-array-byte-offset/-/typed-array-byte-offset-1.0.4.tgz",
-      "integrity": "sha512-bTlAFB/FBYMcuX81gbL4OcpH5PmlFHqlCCpAl8AlEzMz5k53oNDvN8p1PNOWLEmI2x4orp3raOFB51tv9X+MFQ==",
+    "node_modules/vite-plugin-svgr": {
+      "version": "4.5.0",
+      "resolved": "https://registry.npmjs.org/vite-plugin-svgr/-/vite-plugin-svgr-4.5.0.tgz",
+      "integrity": "sha512-W+uoSpmVkSmNOGPSsDCWVW/DDAyv+9fap9AZXBvWiQqrboJ08j2vh0tFxTD/LjwqwAd3yYSVJgm54S/1GhbdnA==",
       "dev": true,
-      "license": "MIT",
       "dependencies": {
-        "available-typed-arrays": "^1.0.7",
-        "call-bind": "^1.0.8",
-        "for-each": "^0.3.3",
-        "gopd": "^1.2.0",
-        "has-proto": "^1.2.0",
-        "is-typed-array": "^1.1.15",
-        "reflect.getprototypeof": "^1.0.9"
-      },
-      "engines": {
-        "node": ">= 0.4"
+        "@rollup/pluginutils": "^5.2.0",
+        "@svgr/core": "^8.1.0",
+        "@svgr/plugin-jsx": "^8.1.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "peerDependencies": {
+        "vite": ">=2.6.0"
       }
     },
-    "node_modules/typed-array-length": {
-      "version": "1.0.7",
-      "resolved": "https://registry.npmjs.org/typed-array-length/-/typed-array-length-1.0.7.tgz",
-      "integrity": "sha512-3KS2b+kL7fsuk/eJZ7EQdnEmQoaho/r6KUef7hxvltNA5DR8NAUM+8wJMbJyZ4G9/7i3v5zPBIMN5aybAh2/Jg==",
-      "dev": true,
+    "node_modules/vitefu": {
+      "version": "1.1.2",
+      "resolved": "https://registry.npmjs.org/vitefu/-/vitefu-1.1.2.tgz",
+      "integrity": "sha512-zpKATdUbzbsycPFBN71nS2uzBUQiVnFoOrr2rvqv34S1lcAgMKKkjWleLGeiJlZ8lwCXvtWaRn7R3ZC16SYRuw==",
       "license": "MIT",
-      "dependencies": {
-        "call-bind": "^1.0.7",
-        "for-each": "^0.3.3",
-        "gopd": "^1.0.1",
-        "is-typed-array": "^1.1.13",
-        "possible-typed-array-names": "^1.0.0",
-        "reflect.getprototypeof": "^1.0.6"
-      },
-      "engines": {
-        "node": ">= 0.4"
+      "workspaces": [
+        "tests/deps/*",
+        "tests/projects/*",
+        "tests/projects/workspace/packages/*"
+      ],
+      "peerDependencies": {
+        "vite": "^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-beta.0"
       },
-      "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+      "peerDependenciesMeta": {
+        "vite": {
+          "optional": true
+        }
       }
     },
-    "node_modules/unbox-primitive": {
-      "version": "1.1.0",
-      "resolved": "https://registry.npmjs.org/unbox-primitive/-/unbox-primitive-1.1.0.tgz",
-      "integrity": "sha512-nWJ91DjeOkej/TA8pXQ3myruKpKEYgqvpw9lz4OPHj/NWFNluYrjbz9j01CJ8yKQd2g4jFoOkINCTW2I5LEEyw==",
-      "dev": true,
+    "node_modules/web-namespaces": {
+      "version": "2.0.1",
+      "resolved": "https://registry.npmjs.org/web-namespaces/-/web-namespaces-2.0.1.tgz",
+      "integrity": "sha512-bKr1DkiNa2krS7qxNtdrtHAmzuYGFQLiQ13TsorsdT6ULTkPLKuu5+GsFpDlg6JFjUTwX2DyhMPG2be8uPrqsQ==",
       "license": "MIT",
-      "dependencies": {
-        "call-bound": "^1.0.3",
-        "has-bigints": "^1.0.2",
-        "has-symbols": "^1.1.0",
-        "which-boxed-primitive": "^1.1.1"
-      },
-      "engines": {
-        "node": ">= 0.4"
-      },
       "funding": {
-        "url": "https://github.com/sponsors/ljharb"
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
       }
     },
-    "node_modules/unist-util-stringify-position": {
-      "version": "2.0.3",
-      "resolved": "https://registry.npmjs.org/unist-util-stringify-position/-/unist-util-stringify-position-2.0.3.tgz",
-      "integrity": "sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g==",
-      "dev": true,
+    "node_modules/webpack-virtual-modules": {
+      "version": "0.6.2",
+      "resolved": "https://registry.npmjs.org/webpack-virtual-modules/-/webpack-virtual-modules-0.6.2.tgz",
+      "integrity": "sha512-66/V2i5hQanC51vBQKPH4aI8NMAcBW59FVBs+rC7eGHupMyfn34q7rZIE+ETlJ+XTevqfUhVVBgSUNSW2flEUQ==",
+      "dev": true
+    },
+    "node_modules/whatwg-encoding": {
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/whatwg-encoding/-/whatwg-encoding-3.1.1.tgz",
+      "integrity": "sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==",
+      "deprecated": "Use @exodus/bytes instead for a more spec-conformant and faster implementation",
       "license": "MIT",
       "dependencies": {
-        "@types/unist": "^2.0.2"
+        "iconv-lite": "0.6.3"
       },
-      "funding": {
-        "type": "opencollective",
-        "url": "https://opencollective.com/unified"
+      "engines": {
+        "node": ">=18"
       }
     },
-    "node_modules/uri-js": {
-      "version": "4.4.1",
-      "resolved": "https://registry.npmjs.org/uri-js/-/uri-js-4.4.1.tgz",
-      "integrity": "sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==",
-      "dev": true,
-      "license": "BSD-2-Clause",
-      "dependencies": {
-        "punycode": "^2.1.0"
+    "node_modules/whatwg-mimetype": {
+      "version": "4.0.0",
+      "resolved": "https://registry.npmjs.org/whatwg-mimetype/-/whatwg-mimetype-4.0.0.tgz",
+      "integrity": "sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=18"
       }
     },
     "node_modules/which": {
@@ -3473,10 +12096,19 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
+    "node_modules/which-pm-runs": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/which-pm-runs/-/which-pm-runs-1.1.0.tgz",
+      "integrity": "sha512-n1brCuqClxfFfq/Rb0ICg9giSZqCS+pLtccdag6C2HyufBrh3fBOiy9nb6ggRMvWOVH5GrdJskj5iGTZNxd7SA==",
+      "license": "MIT",
+      "engines": {
+        "node": ">=4"
+      }
+    },
     "node_modules/which-typed-array": {
-      "version": "1.1.19",
-      "resolved": "https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.19.tgz",
-      "integrity": "sha512-rEvr90Bck4WZt9HHFC4DJMsjvu7x+r6bImz0/BrbWb7A2djJ8hnZMrWnHo9F8ssv0OMErasDhftrfROTyqSDrw==",
+      "version": "1.1.20",
+      "resolved": "https://registry.npmjs.org/which-typed-array/-/which-typed-array-1.1.20.tgz",
+      "integrity": "sha512-LYfpUkmqwl0h9A2HL09Mms427Q1RZWuOHsukfVcKRq9q95iQxdw0ix1JQrqbcDR9PH1QDwf5Qo8OZb5lksZ8Xg==",
       "dev": true,
       "license": "MIT",
       "dependencies": {
@@ -3505,25 +12137,116 @@
         "node": ">=0.10.0"
       }
     },
+    "node_modules/wrap-ansi": {
+      "version": "9.0.2",
+      "resolved": "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-9.0.2.tgz",
+      "integrity": "sha512-42AtmgqjV+X1VpdOfyTGOYRi0/zsoLqtXQckTmqTeybT+BDIbM/Guxo7x3pE2vtpr1ok6xRqM9OpBe+Jyoqyww==",
+      "dev": true,
+      "license": "MIT",
+      "dependencies": {
+        "ansi-styles": "^6.2.1",
+        "string-width": "^7.0.0",
+        "strip-ansi": "^7.1.0"
+      },
+      "engines": {
+        "node": ">=18"
+      },
+      "funding": {
+        "url": "https://github.com/chalk/wrap-ansi?sponsor=1"
+      }
+    },
     "node_modules/wrappy": {
       "version": "1.0.2",
       "resolved": "https://registry.npmjs.org/wrappy/-/wrappy-1.0.2.tgz",
       "integrity": "sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==",
-      "dev": true,
       "license": "ISC"
     },
+    "node_modules/xxhash-wasm": {
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/xxhash-wasm/-/xxhash-wasm-1.1.0.tgz",
+      "integrity": "sha512-147y/6YNh+tlp6nd/2pWq38i9h6mz/EuQ6njIrmW8D1BS5nCqs0P6DG+m6zTGnNz5I+uhZ0SHxBs9BsPrwcKDA==",
+      "license": "MIT"
+    },
+    "node_modules/yallist": {
+      "version": "5.0.0",
+      "resolved": "https://registry.npmjs.org/yallist/-/yallist-5.0.0.tgz",
+      "integrity": "sha512-YgvUTfwqyc7UXVMrB+SImsVYSmTS8X/tSrtdNZMImM+n7+QTriRXyXim0mBrTXNeqzVF0KWGgHPeiyViFFrNDw==",
+      "license": "BlueOak-1.0.0",
+      "engines": {
+        "node": ">=18"
+      }
+    },
+    "node_modules/yaml": {
+      "version": "2.8.2",
+      "resolved": "https://registry.npmjs.org/yaml/-/yaml-2.8.2.tgz",
+      "integrity": "sha512-mplynKqc1C2hTVYxd0PU2xQAc22TI1vShAYGksCCfxbn/dFwnHTNi1bvYsBTkhdUNtGIf5xNOg938rrSSYvS9A==",
+      "devOptional": true,
+      "license": "ISC",
+      "bin": {
+        "yaml": "bin.mjs"
+      },
+      "engines": {
+        "node": ">= 14.6"
+      },
+      "funding": {
+        "url": "https://github.com/sponsors/eemeli"
+      }
+    },
+    "node_modules/yargs-parser": {
+      "version": "22.0.0",
+      "resolved": "https://registry.npmjs.org/yargs-parser/-/yargs-parser-22.0.0.tgz",
+      "integrity": "sha512-rwu/ClNdSMpkSrUb+d6BRsSkLUq1fmfsY6TOpYzTwvwkg1/NRG85KBy3kq++A8LKQwX6lsu+aWad+2khvuXrqw==",
+      "license": "ISC",
+      "engines": {
+        "node": "^20.19.0 || ^22.12.0 || >=23"
+      }
+    },
+    "node_modules/yauzl": {
+      "version": "2.10.0",
+      "resolved": "https://registry.npmjs.org/yauzl/-/yauzl-2.10.0.tgz",
+      "integrity": "sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==",
+      "license": "MIT",
+      "dependencies": {
+        "buffer-crc32": "~0.2.3",
+        "fd-slicer": "~1.1.0"
+      }
+    },
     "node_modules/yocto-queue": {
-      "version": "0.1.0",
-      "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz",
-      "integrity": "sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==",
-      "dev": true,
+      "version": "1.2.2",
+      "resolved": "https://registry.npmjs.org/yocto-queue/-/yocto-queue-1.2.2.tgz",
+      "integrity": "sha512-4LCcse/U2MHZ63HAJVE+v71o7yOdIe4cZ70Wpf8D/IyjDKYQLV5GD46B+hSTjJsvV5PztjvHoU580EftxjDZFQ==",
       "license": "MIT",
       "engines": {
-        "node": ">=10"
+        "node": ">=12.20"
       },
       "funding": {
         "url": "https://github.com/sponsors/sindresorhus"
       }
+    },
+    "node_modules/yoga-layout": {
+      "version": "3.2.1",
+      "resolved": "https://registry.npmjs.org/yoga-layout/-/yoga-layout-3.2.1.tgz",
+      "integrity": "sha512-0LPOt3AxKqMdFBZA3HBAt/t/8vIKq7VaQYbuA8WxCgung+p9TVyKRYdpvCb80HcdTN2NkbIKbhNwKUfm3tQywQ==",
+      "license": "MIT"
+    },
+    "node_modules/zod": {
+      "version": "4.3.6",
+      "resolved": "https://registry.npmjs.org/zod/-/zod-4.3.6.tgz",
+      "integrity": "sha512-rftlrkhHZOcjDwkGlnUtZZkvaPHCsDATp4pGpuOOMDaTdDDXF91wuVDJoWoPsKX/3YPQ5fHuF3STjcYyKr+Qhg==",
+      "license": "MIT",
+      "funding": {
+        "url": "https://github.com/sponsors/colinhacks"
+      }
+    },
+    "node_modules/zwitch": {
+      "version": "2.0.4",
+      "resolved": "https://registry.npmjs.org/zwitch/-/zwitch-2.0.4.tgz",
+      "integrity": "sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==",
+      "license": "MIT",
+      "funding": {
+        "type": "github",
+        "url": "https://github.com/sponsors/wooorm"
+      }
     }
   }
 }
diff --git a/package.json b/package.json
index eebc645804..8fad85df05 100644
--- a/package.json
+++ b/package.json
@@ -1,55 +1,95 @@
 {
-  "name": "expressjs.com",
-  "version": "0.0.0",
+  "name": "expressjs-website",
+  "type": "module",
   "private": true,
+  "description": "Express.js Website",
+  "author": {
+    "name": "Express.js Documentation Team and Contributors"
+  },
+  "license": "CC-BY-SA-4.0",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/expressjs/expressjs.com.git"
+  },
   "scripts": {
-    "test": "eslint --ignore-path .gitignore --ignore-pattern _includes/readmes/ \"**/*.md\""
+    "dev": "astro dev",
+    "build": "astro build",
+    "preview": "astro preview",
+    "astro": "astro",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "check": "npm run format:check && npm run lint",
+    "fix": "npm run format && npm run lint:fix",
+    "prepare": "husky",
+    "lint-staged": "lint-staged",
+    "test:e2e": "playwright test"
+  },
+  "dependencies": {
+    "@astrojs/mdx": "^5.0.3",
+    "@astrojs/react": "^5.0.2",
+    "@astrojs/rss": "^4.0.18",
+    "@astrojs/sitemap": "^3.7.2",
+    "@orama/core": "^1.2.19",
+    "@orama/ui": "^1.5.4",
+    "astro": "^6.1.2",
+    "astro-expressive-code": "^0.41.7",
+    "astro-icon": "^1.1.5",
+    "gray-matter": "^4.0.3",
+    "mdast-util-from-markdown": "^2.0.3",
+    "mdast-util-to-string": "^4.0.0",
+    "react": "^19.2.4",
+    "react-dom": "^19.2.4",
+    "rehype-autolink-headings": "^7.1.0",
+    "rehype-slug": "^6.0.0",
+    "satori": "^0.26.0",
+    "sharp": "^0.34.5",
+    "unist-util-visit": "^5.1.0"
+  },
+  "devEngines": {
+    "runtime": {
+      "name": "node",
+      "version": ">=24.13.0",
+      "onFail": "error"
+    },
+    "packageManager": {
+      "name": "npm",
+      "version": ">=11.0.0",
+      "onFail": "error"
+    }
   },
   "devDependencies": {
-    "eslint": "^8.54.0",
-    "eslint-config-standard": "^17.1.0",
-    "eslint-plugin-import": "^2.32.0",
-    "eslint-plugin-markdown": "^2.2.1",
-    "eslint-plugin-n": "^15.0.0",
-    "eslint-plugin-promise": "^6.6.0"
+    "@csstools/postcss-global-data": "^4.0.0",
+    "@eslint/js": "^9.39.2",
+    "@iconify-json/fluent": "^1.2.41",
+    "@playwright/test": "^1.59.1",
+    "@types/node": "^25.3.2",
+    "@types/react": "^19.2.14",
+    "@types/react-dom": "^19.2.3",
+    "eslint": "^9.39.2",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-astro": "^1.5.0",
+    "eslint-plugin-jsx-a11y": "^6.10.2",
+    "globals": "^17.4.0",
+    "husky": "^9.1.7",
+    "lint-staged": "^16.2.7",
+    "postcss-custom-media": "^12.0.0",
+    "postcss-nested": "^7.0.2",
+    "prettier": "^3.8.1",
+    "prettier-plugin-astro": "^0.14.1",
+    "typescript": "^5.9.3",
+    "typescript-eslint": "^8.53.1",
+    "unplugin-icons": "^23.0.1",
+    "vite-plugin-svgr": "^4.5.0"
   },
-  "eslintConfig": {
-    "extends": [
-      "standard",
-      "plugin:markdown/recommended"
-    ],
-    "plugins": [
-      "markdown"
+  "lint-staged": {
+    "*.{js,jsx,ts,tsx,astro}": [
+      "eslint --fix",
+      "prettier --write"
     ],
-    "overrides": [
-      {
-        "files": "**/*.md",
-        "processor": "markdown/markdown"
-      },
-      {
-        "files": "**/*.md/*.js",
-        "rules": {
-          "array-callback-return": "off",
-          "no-var": "error",
-          "n/handle-callback-err": "off",
-          "object-shorthand": "error",
-          "prefer-arrow-callback": "error",
-          "prefer-template": "error"
-        }
-      },
-      {
-        "files": [
-          "**/3x/*.md/*.js",
-          "**/4x/*.md/*.js",
-          "**/guide/migrating-4.md/*.js"
-        ],
-        "rules": {
-          "no-var": "off",
-          "object-shorthand": "off",
-          "prefer-arrow-callback": "off",
-          "prefer-template": "off"
-        }
-      }
+    "*.{json,md,css}": [
+      "prettier --write"
     ]
   }
 }
diff --git a/playwright.config.ts b/playwright.config.ts
new file mode 100644
index 0000000000..82db311633
--- /dev/null
+++ b/playwright.config.ts
@@ -0,0 +1,34 @@
+import { defineConfig, devices } from '@playwright/test';
+
+const isCI = !!process.env.CI;
+
+/**
+ * See https://playwright.dev/docs/test-configuration.
+ */
+export default defineConfig({
+  testDir: './tests/e2e',
+  fullyParallel: true,
+  forbidOnly: isCI,
+  retries: isCI ? 2 : 0,
+  workers: isCI ? 1 : undefined,
+  reporter: isCI ? [['html'], ['github']] : [['html']],
+
+  use: {
+    baseURL: process.env.PLAYWRIGHT_BASE_URL || 'http://localhost:4321',
+    trace: 'on-first-retry',
+  },
+  projects: [
+    {
+      name: 'chromium',
+      use: { ...devices['Desktop Chrome'] },
+    },
+    {
+      name: 'firefox',
+      use: { ...devices['Desktop Firefox'] },
+    },
+    {
+      name: 'webkit',
+      use: { ...devices['Desktop Safari'] },
+    },
+  ],
+});
diff --git a/postcss.config.mjs b/postcss.config.mjs
new file mode 100644
index 0000000000..febcf2f575
--- /dev/null
+++ b/postcss.config.mjs
@@ -0,0 +1,13 @@
+import postcssGlobalData from '@csstools/postcss-global-data';
+import postcssCustomMedia from 'postcss-custom-media';
+import postcssNested from 'postcss-nested';
+
+export default {
+  plugins: [
+    postcssGlobalData({
+      files: ['./src/styles/tokens/_breakpoints.css'],
+    }),
+    postcssCustomMedia(),
+    postcssNested(),
+  ],
+};
diff --git a/pt-br/3x/api.md b/pt-br/3x/api.md
deleted file mode 100644
index 51e2c55373..0000000000
--- a/pt-br/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - Referência de API
-description: Acesso à referência da API do Express.js versão 3.x, observando que esta versão é final de vida e não mais mantida - inclui detalhes sobre módulos e métodos.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x support is ending soon**
-
-This series will continue to receive only security updates and bug fixes until July 2015. It is highly recommended to upgrade to Express 4.x.
-
-Se você não puder atualizar as últimas 3.x, por favor considere as [Opções de Suporte Comercial](/{{ page.lang }}/support#comercial-support-options).
-
-  </div>
-
-  <h1>3.x API</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/pt-br/4x/api.md b/pt-br/4x/api.md
deleted file mode 100644
index 1c107a346d..0000000000
--- a/pt-br/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - Referência de API
-description: Acesse a referência da API para Express.js 4.x, detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>API 4.x</h1>
-
-{% capture node-version %}
-
-Express 4.0 requer Node.js 0.10 ou superior.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/pt-br/5x/api.md b/pt-br/5x/api.md
deleted file mode 100644
index 9513d8ae03..0000000000
--- a/pt-br/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Referência da API
-description: Acesse a referência da API para Express.js 5.x, detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão mais recente.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requer Node.js 18 ou superior.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/pt-br/advanced/best-practice-performance.md b/pt-br/advanced/best-practice-performance.md
deleted file mode 100644
index e769362adc..0000000000
--- a/pt-br/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,429 +0,0 @@
----
-layout: page
-title: Melhores Práticas de Desempenho Usando o Express em Produção
-description: Descubra desempenho e confiabilidade melhores práticas para aplicativos Express na produção, cobrindo otimizações de código e configurações de ambiente para um desempenho ideal.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# Melhores Práticas de Produção: desempenho e confiabilidade
-
-Este artigo discute as melhores práticas de desempenho e de confiabilidade
-para aplicativos Express implementados para produção.
-
-Este tópico se enquadra claramente no mundo de "devops", abordando o desenvolvimento tradicional e as operações. Assim, as informações são divididas em duas partes:
-
-- [Itens a fazer no seu código](#code) (a parte do dev).
-  - Use a compactação gzip
-  - Não use funções síncronas
-  - Faça o registro de logs corretamente
-  - [Tratar exceções corretamente](#handle-exceptions-properly)
-- [Itens a fazer no seu ambiente / configuração](#env) (a parte de ops).
-  - Configure o NODE_ENV para "produção"
-  - Executar o seu aplicativo (e Node) diretamente com o sistema
-    de inicialização. Isto é de certa forma mais simples, mas você não
-    obtém as vantagens adicionais do uso de um gerenciador de processos.
-  - Execute seu aplicativo em um cluster
-  - <a name="try-catch"></a>
-  - Use um balanceador de carga
-  - Use um proxy reverso
-
-## Itens a fazer no seu código
-
-A seguir serão apresentados alguns itens que podem ser feitos no seu código
-para melhorar o desempenho dos aplicativos:
-
-- Use a compactação gzip
-- Não use funções síncronas
-- Faça o registro de logs corretamente
-- [Tratar exceções corretamente](#handle-exceptions-properly)
-
-### Use a compactação gzip
-
-A compactação Gzip pode diminuir bastante o tamanho do corpo de resposta e assim aumentar a velocidade de um aplicativo da web. Use o middleware [compression](https://www.npmjs.com/package/compression) para fazer a compactação gzip no seu aplicativo do Express. Por exemplo:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-Para um website com tráfego intenso na produção, a melhor maneira de colocar a compactação em prática, é implementá-la em um
-nível de proxy reverso (consulte [Use um proxy reverso](#proxy)). Neste caso, não é necessário usar o middleware de compactação. Para obter detalhes sobre a ativação da compactação gzip no Nginx, consulte o Módulo
-ngx_http_gzip_module na documentação do Nginx.
-
-### Não use funções síncronas
-
-Funções e métodos síncronos impedem o avanço da execução do processo até que eles retornem. Uma
-única chamada a uma função síncrona pode retornar em poucos microssegundos ou milissegundos, entretanto, em websites com tráfego
-intenso, essas chamadas se somam e reduzem o desempenho do
-aplicativo. Evite o uso delas na produção.
-
-Apesar de o Node e muitos módulos fornecerem versões síncronas e assíncronas de suas funções, sempre use as versões assíncronas na produção. O único momento em que o uso de uma função síncrona pode ser justificado é na primeira inicialização.
-
-Se estiver usando o Node.js + ou o  .+, é possível usar a sinalização `--trace-sync-io` da linha de comandos para imprimir um aviso e um rastreio de pilha sempre que o seu aplicativo usar uma API síncrona. Obviamente, não seria desejado usar isto na produção, mas sim antes, para garantir que seu código está pronto para produção. Consulte a Atualização
-semanal para o io.js 2.1.0 para obter mais informações.
-
-### Lide com exceções adequadamente
-
-Em geral, existem duas razões para registrar logs em seu aplicativo: Para depuração e para registro de logs de atividade do aplicativo (essencialmente, todo o resto). Usar
-o `console.log()` ou o `console.err()` para imprimir mensagens de log no
-terminal é uma prática comum em desenvolvimento. Mas essas
-funções são síncronas quando o destino é um terminal ou um arquivo, portanto elas não são adequadas para produção, a não ser que
-a saída seja canalizada para outro programa.
-
-#### Para depuração
-
-Se estiver registrando logs com o propósito de depuração, então ao invés de usar o `console.log()`, use um módulo
-especial para depuração como o [debug](https://www.npmjs.com/package/debug). Este
-módulo permite que seja usada a variável de ambiente DEBUG para controlar quais mensagens de depuração são enviadas para o
-`console.err()`, se houver. Para manter o seu aplicativo puramente assíncrono, você deverá canalizar o
-`console.err()` para outro programa. Mas nesse ponto, você não fará a depuração na produção, não é?
-
-#### Para atividade do aplicativo
-
-Se estiver registrando logs de atividade do aplicativo (por
-exemplo, rastreamento de tráfico ou chamadas de API), ao invés de
-usar o `console.log()`, use uma biblioteca de
-registro de logs como [Winston](https://www.npmjs.com/package/pino) ou Bunyan.
-
-### Lide com exceções adequadamente
-
-Aplicativos do Node caem ao encontrarem uma exceção não
-capturada. O não tratamento de exceções e a não tomada das ações
-apropriadas irão fazer com que o seu aplicativo do Express caia e
-fique off-line. Se seguir os conselhos em [Assegurando que o seu aplicativo reinicie automaticamente](#restart)
-abaixo, então seu aplicativo se recuperará de uma queda. Felizmente, aplicativos Express tipicamente possuem um tempo curto de inicialização. Contudo,
-é desejável evitar quedas em primeiro lugar e, para fazer isso, é
-necessário tratar exceções adequadamente.
-
-Para garantir que está tratando todas as exceções, use as seguintes técnicas:
-
-- [Use try-catch](#try-catch)
-- [Use promessas](#promises)
-
-Antes de se aprofundar nestes tópicos, você deveria ter um
-entendimento básico de manipulação de erros do Node/Express: usando
-retornos de chamada erros-first, e propagação de erros no
-middleware. O Node usa uma convenção "retorno de chamada erros-first" para retorno de erros de funções assíncronas, onde o
-primeiro parâmetro para a função de retorno de chamada é o objeto de erro, seguido dos dados de resultado nos parâmetros subsequentes. Para indicar que não ocorreram erros, passe null como o primeiro parâmetro. A função de retorno de chamada deve correspondentemente seguir a
-convenção de retorno de chamada erros-first para tratar o erro de forma significativa. E no Express, a melhor prática é usar a função next() para propagar erros pela cadeia de middlewares.
-
-Para obter mais informações sobre os fundamentos de manipulação de erros, consulte:
-
-- [Manipulação de Erros no Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### Usar try-catch
-
-Try-catch é uma construção da linguagem JavaScript que pode ser usada para capturar exceções em um código síncrono. Use try-catch, por exemplo, para tratar erros de análise sintática de JSON como mostrado abaixo.
-
-Aqui está um exemplo de uso de try-catch para tratar uma
-potencial exceção causadora de queda de processo.
-Esta função middleware aceita um parâmetro de campo de consulta chamado "params" que é um objeto JSON.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-Entretanto, o try-catch funciona apenas para códigos síncronos. Como
-a plataforma Node é a princípio assíncrona (particularmente em um ambiente de produção), o try-catch deixará de capturar muitas
-exceções.
-
-#### Use promessas
-
-Quando um erro é lançado em uma função `async` ou uma promessa rejeitada é aguardada dentro de uma função `async`, esses erros serão passados para o manipulador de erros como se chamando `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Além disso, você pode usar funções assíncronas para o seu middleware, e o roteador irá lidar com erros se a promessa falhar, por exemplo:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-A melhor prática é lidar com os erros o mais próximo possível do site. Então enquanto isso é manipulado no roteador, É melhor encontrar o erro no middleware e lidar com ele sem depender de um middleware separado para manipular erros.
-
-#### O que não fazer
-
-Uma coisa que _não_ deveria fazer é escutar a eventos `uncaughtException`, emitidos quando uma exceção
-emerge regressando ao loop de eventos. Incluir um listener de eventos para `uncaughtException` irá mudar o comportamento
-padrão do processo que está encontrando uma exceção; o processo irá continuar a execução apesar da exceção. Essa pode parecer como uma boa maneira de prevenir que o seu
-aplicativo caia, mas continuar a execução do aplicativo após uma
-exceção não capturada é uma prática perigosa e não é recomendada, porque o estado do processo se torna não confiável e imprevisível.
-
-Adicionalmente, usar o `uncaughtException` é oficialmente reconhecido como [grosseiro](https://nodejs.org/api/process.html#process_event_uncaughtexception)
-e existe uma [proposta](https://github.com/nodejs/node-v0.x-archive/issues/2582)
-de removê-lo do núcleo. Portando escutar por um `uncaughtException` é simplesmente uma má ideia. É
-por isso que recomendamos coisas como múltiplos processos e
-supervisores: o processo de queda e reinicialização é frequentemente a
-forma mais confiável de se recuperar de um erro.
-
-Também não recomendamos o uso de [domínios](https://nodejs.org/api/domain.html). Ele
-geralmente não resolve o problema e é um módulo descontinuado.
-
-## Coisa a se fazer no seu ambiente / configuração
-
-A seguir serão apresentados alguns itens que podem ser feitos no seu ambiente de sistema para melhorar o desempenho dos seus aplicativos:
-
-- Configure o NODE_ENV para "produção"
-- Executar o seu aplicativo (e Node) diretamente com o sistema
-  de inicialização. Isto é de certa forma mais simples, mas você não
-  obtém as vantagens adicionais do uso de um gerenciador de processos.
-- Execute seu aplicativo em um cluster
-- <a name="try-catch"></a>
-- Use um balanceador de carga
-- Use um proxy reverso
-
-### Configure o NODE_ENV para "produção"
-
-A variável de ambiente NODE_ENV especifica o ambiente no qual um aplicativo está executando (geralmente, desenvolvimento ou
-produção). Uma das coisas mais simples que podem ser feitas para
-melhorar o desempenho é configurar NODE_ENV para "production".
-
-Configurando NODE_ENV para "produção" faz com que o Express:
-
-- Armazene em Cache os modelos de visualização.
-- Armazene em Cache arquivos CSS gerados a partir de extensões CSS.
-- Gere menos mensagens de erro detalhadas
-
-Testes
-indicam que apenas fazendo isso pode melhorar o desempenho por um fator de três!
-
-Se precisar escrever código específico por ambiente, é possível verificar o valor de NODE_ENV com `process.env.NODE_ENV`. Esteja
-ciente de que verificar o valor de qualquer variável de ambiente incorre em perda de desempenho, e por isso deve ser feito raramente.
-
-Em desenvolvimento, você tipicamente configura variáveis de ambiente no seu shell interativo, por exemplo, usando o
-`export` ou o seu arquivo `.bash_profile`. Mas
-em geral você não deveria fazer isto em um servidor de produção; ao invés disso, use o sistema de inicialização do seu sistema
-operacional (systemd). A próxima seção fornece mais detalhes sobre a utilização do seu sistema de inicialização em geral,
-mas configurando NODE_ENV é tão importante para o desempenho (e fácil de fazer), que está destacado aqui.
-
-Com o systemd, use a diretiva `Environment` no seu arquivo de unidade. Por exemplo:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-Para obter mais informações, consulte Usando
-Variáveis de Ambiente em Unidades systemd.
-
-### Assegure que o seu aplicativo reinicie automaticamente
-
-Em produção, não é desejado que seu aplicativo fique off-line,
-nunca. Isto significa que é necessário certificar-se de que ele
-reinicie tanto se o aplicativo cair quanto se o próprio servidor
-cair. Apesar de se esperar que nenhum desses eventos ocorram,
-realisticamente você deve considerar ambas as eventualidades:
-
-- Usando um gerenciador de processos para reiniciar o aplicativo (e o Node) quando ele cair.
-- Usando o sistema de inicialização fornecido pelo seu sistema operacional para reiniciar o gerenciador de processos quando o
-  sistema operacional cair. Também é possível usar o sistema de inicialização sem um gerenciador de processos.
-
-Aplicativos do Node caem se encontrarem uma exceção não
-capturada. A principal coisa que precisa ser feita é assegurar que o
-seu aplicativo esteja bem testado e trate todas as exceções (consulte
-[tratar exceções adequadamente](#exceptions) para
-obter detalhes). Mas por segurança, posicione um mecanismo para
-assegurar que se e quando o seu aplicativo cair, ele irá
-automaticamente reiniciar.
-
-#### Use um gerenciador de processos
-
-Em desenvolvimento, você iniciou o seu aplicativo de forma simples a partir da linha de comandos com  o `node server.js` ou
-algo similar. Mas fazer isso na produção é uma receita para o desastre. Se o aplicativo cair, ele ficará off-line até ser reiniciado. Para
-assegurar que o seu aplicativo reinicie se ele cair, use um gerenciador de processos. Um
-gerenciador de processos é um "contêiner" para aplicativos que facilita a implementação, fornece alta disponibilidade, e permite o
-gerenciamento do aplicativo em tempo real.
-
-Em adição à reinicialização do seu aplicativo quando cai, um
-gerenciador de processos pode permitir que você:
-
-- Ganhe insights sobre o desempenho em tempo de execução e o consumo de recursos.
-- Modifique configurações dinamicamente para melhorar o desempenho.
-- Controle de agrupamento (pm2).
-
-Historicamente, foi popular usar um gerente de processo Node.js, como [PM2](https://github.com/Unitech/pm2). Veja a documentação deles, se você quiser fazer isso. No entanto, recomendamos a utilização de seu sistema de inicio para gerenciamento de processos.
-
-#### Use um sistema de inicialização
-
-A próxima camada de confiabilidade é para assegurar que o seu
-aplicativo reinicie quando o servidor reiniciar. Os sistemas podem
-ainda assim cair por uma variedade de razões. Para assegurar que o
-seu aplicativo reinicie se o servidor cair, use o sistema de
-inicialização integrado no seu sistema operacional. O sistema principal de iniciação em uso hoje é [systemd](https://wiki.debian.org/systemd).
-
-Existem duas formas de usar sistemas de inicialização com o seu aplicativo Express:
-
-- Executar o seu aplicativo em um gerenciador de processos, e instalar o gerenciador de processos com o sistema de inicialização. O gerenciador de processos irá reiniciar seu aplicativo quando o
-  aplicativo cair, e o sistema de inicialização irá reiniciar o
-  gerenciador de processos quando o sistema operacional reiniciar. Esta é a abordagem recomendada.
-- Execute seu aplicativo (e Node) diretamente com o sistema iniciação. Isto é um pouco mais simples, mas você não obtém as vantagens adicionais de usar um gerente de processo.
-
-##### Systemd
-
-O Systemd é um sistema Linux e gerenciador de serviço. A
-maioria das distribuições principais do Linux adotaram o systemd como
-sistema de inicialização padrão.
-
-Um arquivo de configuração de serviço do systemd é chamado
-de _arquivo de unidade_, com um nome de arquivo
-terminando em .service. Aqui está um exemplo de arquivo de unidade
-para gerenciar um aplicativo Node diretamente (substitua o texto em
-negrito com valores para o seu sistema e aplicativo): Substitua os valores colocados em `<angle brackets>` do seu sistema e aplicativo:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-Para obter mais informações sobre o systemd, consulte a
-referência
-do systemd (página do manual).
-
-### Execute seu aplicativo em um cluster
-
-Em um sistema com múltiplos núcleos, é possível aumentar o
-desempenho de um aplicativo Node em muitas vezes ativando um cluster
-de processos. Um cluster executa múltiplas instâncias do aplicativo,
-idealmente uma instância em cada núcleo da CPU, assim distribuindo a carga e as
-tarefas entre as instâncias.
-
-![Balanceamento entre instâncias de aplicação usando a API de cluster](/images/clustering.png)
-
-IMPORTANTE: Como as instâncias do aplicativo são executadas em processos separados, elas não compartilham o mesmo espaço de memória. Isto é, os objetos são locais para cada instância do aplicativo. Portanto, não é possível manter o estado no código do aplicativo. Entretanto, é possível usar um armazenamento de dados em memória como o [Redis](http://redis.io/) para armazenar dados
-relativos à sessão e ao estado. Este alerta aplica-se a essencialmente todas as formas de escalonamento horizontal, seja a
-clusterização com múltiplos processos ou múltiplos servidores físicos.
-
-Em aplicativos clusterizados, processos de trabalho podem cair individualmente sem afetar o restante dos processos. Fora as vantagens de desempenho, o isolamento de falhas é outra razão para executar um cluster de processos de aplicativos. Sempre que processo de trabalho cair, certifique-se de registrar os logs do evento e spawn um novo processo usando cluster.fork().
-
-#### Usando o módulo de cluster do Node
-
-É possível agrupar com o [módulo cluster do Node](https://nodejs.org/api/cluster.html). Isto permite que um processo principal faça o
-spawn de processos de trabalho e distribua conexões recebidas entre
-os trabalhadores.
-
-#### Usando PM2
-
-Se você publicar sua aplicação com PM2, então você pode aproveitar o clustering _without_ para modificar o código da sua aplicação. Você deve garantir sua [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) primeiro, significando que nenhum dado local é armazenado no processo (como sessões, conexões de websocket e coisas parecidas).
-
-Ao executar um aplicativo com PM2, você pode habilitar o **cluster mode** para executá-lo em um cluster com várias instâncias de sua escolha, como o número de CPUs disponíveis na máquina. Você pode alterar manualmente o número de processos no cluster usando a ferramenta de linha de comando `pm2` sem parar o aplicativo.
-
-Para ativar o modo de agrupamento, inicie seu aplicativo assim:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-Isto também pode ser configurado dentro de um arquivo de processo PM2 (`ecosystem.config.js` ou similar) configurando `exec_mode` para `cluster` e `instances` para o número de workers para começar.
-
-Quando em execução, o aplicativo pode ser alterado assim:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-Para obter mais informações sobre clustering com PM2, consulte [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) na documentação PM2.
-
-### Armazene em cache os resultados das solicitações
-
-Outra estratégia para melhorar o desempenho na produção é
-armazenar em cache o resultado de solicitações, para que o seu
-aplicativo não repita a operação para entregar a mesma solicitação
-repetidamente.
-
-Use um servidor de cache como [Varnish](https://www.varnish-cache.org/) ou [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (veja também [Nginx Caching](https://serversforhackers.com/nginx-caching/)) para melhorar muito a velocidade e o desempenho de sua aplicação.
-
-### Use um balanceador de carga
-
-Não importa o quão otimizado um aplicativo é, uma única
-instância pode manipular apenas uma quantidade limitada de carga e
-tráfego. Uma maneira de escalar um aplicativo é executar múltiplas
-instâncias do mesmo e distribuir o tráfego através de um balanceador
-de carga. Configurar um balanceador de carga pode melhorar o
-desempenho e velocidade do aplicativo, e permiti-lo escalar mais do
-que é possível com uma instância única.
-
-Um balanceador de carga é geralmente um proxy reverso que
-orquestra o tráfego para e de múltiplas instâncias de aplicativo e
-servidores. Você pode facilmente configurar um balanceador de carga 'load balancer' para o seu aplicativo usando [Nginx](https://nginx.org/en/docs/http/load_balancing.html) ou [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-Com o balanceamento de carga, você pode ter que garantir que
-solicitações que estão associadas com um ID de sessão em particular
-conectam ao processo que as originou. Isto é conhecido como
-_afinidade de sessão_, ou _sessões
-pegajosas_, e podem ser endereçadas pela sugestão acima para
-usar um armazenamento de dados como o Redis para os dados da sessão
-(dependendo do seu aplicativo). Para uma discussão, consulte por
-[Usando múltiplos nós](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### Use um proxy reverso
-
-Um proxy reverso fica em frente a um aplicativo web e executa
-operações de suporte nas solicitações, fora o direcionamento de
-solicitações para o aplicativo. Ele pode lidar com páginas de erro,
-compactação, armazenamento em cache, entrega de arquivos, e
-balanceamento de carga entre outras coisas.
-
-Entregar tarefas que não requerem conhecimento do estado do
-aplicativo para um proxy reverso libera o Express para executar
-tarefas especializadas de aplicativos. Por este motivo, é recomendado executar Express atrás de um proxy reverso como [Nginx](https://www.nginx.org/) ou [HAProxy](https://www.haproxy.org/) em produção.
diff --git a/pt-br/advanced/best-practice-security.md b/pt-br/advanced/best-practice-security.md
deleted file mode 100644
index f82781b78f..0000000000
--- a/pt-br/advanced/best-practice-security.md
+++ /dev/null
@@ -1,351 +0,0 @@
----
-layout: page
-title: Melhores Práticas de Segurança para o Express em Produção
-description: Descubra as melhores práticas de segurança cruciais para aplicativos Express em produção, incluindo o uso de TLS, validação de entrada, cookies seguros e prevenção de vulnerabilidades.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# Melhores Práticas em Produção: Segurança
-
-## Visão Geral
-
-O termo _"produção"_ refere-se ao estágio no ciclo de vida do software onde um aplicativo ou API está geralmente
-disponível para os seus usuários finais ou consumidores. Em contrapartida, no estágio de _"desenvolvimento"_,
-você ainda está ativamente escrevendo e testando o código, e o aplicativo não está aberto para acesso externo. Os ambiente de sistema correspondentes são conhecidos como ambientes de _produção_ e _desenvolvimento_,
-respectivamente.
-
-Os ambientes de desenvolvimento e produção são geralmente
-configurados de forma diferente e possuem requisitos completamente
-diferentes. O que é bom em desenvolvimento pode não ser aceitável na produção. Por exemplo, em um ambiente de desenvolvimento você pode
-desejar registros detalhados de erros para depuração, enquanto o
-mesmo comportamento pode se tornar um risco de segurança em um
-ambiente de produção. E em desenvolvimento, você não precisa se
-preocupar com a escalabilidade, confiabilidade, e desempenho,
-enquanto estas preocupações se tornam críticas na produção.
-
-{% capture security-note %}
-
-Se acredita que descobriu uma vulnerabilidade de segurança em Express, consulte
-[Políticas de Segurança e Procedimentos](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-Este artigo discute algumas melhores práticas de segurança para
-aplicativos do Express implementadas na produção.
-
-- [Práticas recomendadas: Segurança](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Não usar versões descontinuadas ou vulneráveis do Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [Use TLS](#use-tls)
-  - [Não confie na entrada do usuário](#do-not-trust-user-input)
-    - [Impedir redirecionamentos abertos](#prevent-open-redirects)
-  - [Use Helmet](#use-helmet)
-  - [Reduzir impressão digital](#reduce-fingerprinting)
-  - A [hsts](https://github.com/helmetjs/hsts) configura o cabeçalho `Strict-Transport-Security`
-    que impinge conexões seguras (HTTP sobre SSL/TLS) com o servidor.
-    - A principal diferença entre esses dois módulos é como eles salvam os dados de cookies de sessão.  O middleware [express-session](https://www.npmjs.com/package/express-session)
-      armazena os dados da sessão no servidor; ele salva apenas o ID da
-      sessão no cookie, não os dados da sessão.  Por padrão, ele usa
-      armazenamento em memória e não é projetado para um ambiente de
-      produção.  Em produção, será necessário configurar um armazenamento de
-      sessão escalável; consulte a lista de armazenamentos
-      de sessão compatíveis.
-    - A [ieNoOpen](https://github.com/helmetjs/ienoopen) configura o `X-Download-Options` para o IE8+.
-  - [Impedir ataques brute-force contra a autorização](#prevent-brute-force-attacks-against-authorization)
-  - [Garanta que suas dependências sejam seguras](#ensure-your-dependencies-are-secure)
-    - A [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) remove o cabeçalho `X-Powered-By`.
-  - [Considerações adicionais](#additional-considerations)
-
-## Não use versões descontinuadas ou vulneráveis do Express
-
-Os Express 2.x e 3.x não são mais mantidos. Problemas de
-segurança e desempenho nestas versões não serão corrigidos. Não use-as! Se
-não tiver migrado para a versão 4, siga o [guia de migração](/{{ page.lang }}/guide/migrating-4.html).
-
-Assegure-se também de que não esteja usando nenhuma das versões
-vulneráveis do Express listadas na [Página de
-atualizações de segurança](/{{ page.lang }}/advanced/security-updates.html). Se estiver, atualize para uma das
-liberações estáveis, preferivelmente a mais recente.
-
-## Use TLS
-
-Se o seu aplicativo negocia com ou transmite dados sensíveis,
-use a Segurança
-da Camada de Transporte (TLS) para proteger a conexão e os
-dados. Esta tecnologia criptografa os dados antes deles serem
-enviados do cliente para o servidor, assim evitando alguns ataques
-comuns (e fáceis). Apesar de solicitações Ajax e POST não parecerem
-visivelmente óbvias e parecerem "ocultas" em navegadores, o seu
-tráfego de rede é vulnerável a [sniffing de pacotes](https://en.wikipedia.org/wiki/Packet_analyzer) e
-[ataques man-in-the-middle ](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-Você pode estar familiarizado com a criptografia Secure Sockets Layer(SSL). O
-TLS é simplesmente a próxima progressão do. Em outras palavras, se você estava usando o SSL antes, considere fazer o
-upgrade para o TLS. Em geral, recomendamos o Nginx para lidar com o TLS. Para
-obter uma boa referência para configurar o TLS no Nginx (e outros servidores), consulte
-Configurações
-Recomendadas de Servidores (Mozilla Wiki).
-
-Além disso, uma ferramenta útil para obter um certificado TLS
-gratuito é a Let's
-Encrypt, uma autoridade de certificação (CA) gratuita,
-automatizada, e aberta fornecida pelo
-Grupo de Pesquisas de
-Segurança da Internet (ISRG).
-
-## Não confiar em entrada do usuário
-
-Para aplicativos web, um dos requisitos de segurança mais críticos é a validação e tratamento adequado dos dados de entrada do usuário. Isto tem muitas formas e não as cobriremos todas aqui.
-Em última análise, a responsabilidade de validar e manipular corretamente os tipos de entrada de usuário que seu aplicativo aceita é sua.
-
-### Impedir redirecionamentos abertos
-
-Um exemplo de entrada de usuário potencialmente perigosa é um _open redirect_, onde um aplicativo aceita uma URL como entrada de usuário (muitas vezes na consulta de URL, por exemplo `? rl=https://exemplo.com`) e usa `res.redirect` para definir o cabeçalho `location` e
-return um status de 3xx.
-
-Uma aplicação deve validar que suporta redirecionamento para a URL de entrada, para evitar enviar usuários para links maliciosos, como sites de phishing, entre outros riscos.
-
-Aqui está um exemplo de verificar URLs antes de usar `res.redirect` ou `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## Use Helmet
-
-O [Helmet](https://www.npmjs.com/package/helmet) pode
-ajudar a proteger o seu aplicativo de algumas vulnerabilidades da web
-bastante conhecidas configurando os cabeçalhos HTTP adequadamente.
-
-Helmet é uma função middleware que define cabeçalhos de resposta HTTP relacionados à segurança. Helmet define os seguintes cabeçalhos por padrão:
-
-- `Content-Security-Policy`: Uma poderosa lista de permissões do que pode acontecer na sua página, que mitiga muitos ataques
-- `Cross-Origin-Opener-Policy`: Ajuda a isolar sua página
-- `Cross-Origin-Resource-Policy`: Bloqueia outros de carregar seus recursos entre origens
-- `Origin-Agent-Cluster`: Altera o isolamento do processo para ser baseado na origem
-- `Referrer-Policy`: controla o cabeçalho [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer)
-- `Strict-Transport-Security`: Diz aos navegadores para preferir HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controla o pré-carregamento de DNS
-- `X-Download-Options`: Força os downloads a serem salvos (apenas no Internet Explore)
-- `X-Frame-Options`: Cabeçalho de legado que mitiga ataques [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking)
-- `X-Perting-Cross-Domain-Policies`: Controla o comportamento entre domínios para produtos Adobe, como a Acrobat
-- `X-Powered-By`: Informações sobre o servidor web. Removido porque poderia ser utilizado em ataques simples
-- `X-XSS-Protection`: Cabeçalho de legado que tenta mitigar [ataques XSS](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), mas piora as coisas, então o Helmet desabilita isso
-
-Cada cabeçalho pode ser configurado ou desativado. Para ler mais sobre isso, por favor, vá para [a documentação do site][helmet].
-
-Instale o Helmet como qualquer outro módulo:
-
-```bash
-$ npm install helmet
-```
-
-Em seguida use-o no seu código:
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduzir impressão digital
-
-Ele pode ajudar a fornecer uma camada extra de segurança para reduzir a capacidade dos invasores de determinar
-o software que um servidor usa, conhecido como "impressão digital." Embora não seja um problema de segurança em si,
-reduzir a capacidade de imprimir impressão digital a um aplicativo melhora sua posição geral de segurança.
-O software do servidor pode ser impresso por peculiares em como ele responde a solicitações específicas, por exemplo em
-os cabeçalhos de resposta HTTP.
-
-Por padrão, o Express envia o cabeçalho de resposta `X-Powered-By` que você pode
-desabilitar usando o método `app.disable()`:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Desativar o cabeçalho `X-Powered-By` não impede que um atacante sofisticado determine que um aplicativo está executando o Express. Isso pode
-desencorajar uma exploração casual, mas existem outras maneiras de determinar se um aplicativo está executando Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express também envia suas próprias mensagens formatadas "404 Not Found" e erro de formatação
-mensagens de resposta. Elas podem ser alteradas por
-[adicionando seu próprio manipulador para 404](/en/starter/faq.html#how-do-i-handle-404-responses)
-e
-[escrevendo seu próprio manipulador de erro](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## Use cookies de maneira segura
-
-Para assegurar que os cookies não deixem o seu aplicativo
-aberto a ataques, não use o cookie de sessão padrão e configure as
-opções de segurança de cookies adequadamente.
-
-Existem dois módulos de middleware principais para sessão de
-cookies:
-
-- [express-session](https://www.npmjs.com/package/express-session)
-  que substitui o middleware `express.session`
-  integrado no Express 3.x.
-- [cookie-session](https://www.npmjs.com/package/cookie-session)
-  que substitui o middleware `express.cookieSession` integrado no Express 3.x.
-
-A principal diferença entre estes dois módulos é como eles salvam os dados da sessão de cookie. O [express-session](https://www.npmjs.com/package/express-session) middleware armazena os dados de sessão no servidor; apenas salva o ID da sessão no próprio cookie, não nos dados da sessão. Por padrão, ele usa armazenamento de memória e não é projetado para um ambiente de produção. Na produção, você precisará configurar uma loja de sessão escalável; ver a lista de [lojas de sessões compatíveis](https://github.com/expressjs/session#compatible-session-stores).
-
-Em contrapartida, o middleware [cookie-session](https://www.npmjs.com/package/cookie-session)
-implementa um armazenamento apoiado em cookies: ele serializa a sessão inteira para o cookie, ao invés de apenas a chave da sessão.  Use apenas quando os dados da sessão são relativamente pequenos e facilmente codificados como números primitivos(ao invés de objetos). Use isso apenas quando os dados da sessão são relativamente pequenos e facilmente codificados como valores primitivos (em vez de objetos). Apesar de navegadores supostamente suportarem pelo menos 4096 bytes por cookie, para assegurar que você não exceda o limite, não exceda
-um tamanho de  4093 bytes por domínio. Além disso, esteja ciente de que os dados do cookie serão visíveis para o cliente, portanto se
-houver razão para mantê-los seguros ou obscuros, então o express-session pode ser uma escolha melhor.
-
-### Não use o nome do cookie da sessão padrão
-
-Usando o nome do cookie da sessão padrão pode deixar o seu
-aplicativo aberto a ataques. O problema de segurança levantado é
-parecido ao do `X-Powered-By`: um invasor em
-potencial poderia usá-lo para identificar o servidor e direcionar
-ataques de acordo com ele.
-
-Para evitar este problema, use nomes de cookie genéricos; por
-exemplo usando o middleware [express-session](https://www.npmjs.com/package/express-session):
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### Configure as opções de segurança de cookie
-
-Configure as seguintes opções de cookie para aprimorar a
-segurança:
-
-- `secure` - Assegura que o navegador só envie o cookie por HTTPS.
-- `httpOnly` - Assegura que o cookie seja enviado apenas por HTTP(S), não por cliente JavaScript, ajudando
-  assim a se proteger contra ataques de cross-site scripting.
-- `domain` - indica o domínio do cookie; use-o para comparação contra o domínio do servidor em que a URL está
-  sendo solicitada. Se elas corresponderem, verifique o atributo de caminho em seguida.
-- `path` - indica o caminho do cookie; use-o para comparação contra o caminho da solicitação. Se este e o domínio corresponderem, então envie o cookie na solicitação.
-- `expires` - use para configurar uma data de
-  expiração para cookies persistentes.
-
-Aqui está um exemplo usando o middleware [cookie-session](https://www.npmjs.com/package/cookie-session):
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Evite ataques brutos contra autorização
-
-Certifique-se de que os endpoints de login estejam protegidos para tornar os dados privados mais seguros.
-
-Uma técnica simples e poderosa é bloquear tentativas de autorização usando duas métricas:
-
-1. O número de tentativas consecutivas com o mesmo nome de usuário e endereço IP.
-2. O número de tentativas falhadas de um endereço IP por um longo período de tempo. Por exemplo, bloqueie um endereço IP se fizer 100 tentativas falhadas em um dia.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) pacote fornece ferramentas para tornar essa técnica fácil e rápida. Você pode encontrar [um exemplo de proteção brute-force na documentação](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Certifique-se de que suas dependências estejam seguras
-
-Usar o npm para gerenciar as dependências do seu aplicativo é poderoso e conveniente. Mas os pacotes que você usa podem conter vulnerabilidades de segurança críticas que também podem afetar sua aplicação. A segurança do seu aplicativo só é forte como o link "mais fraco" em suas dependências.
-
-Desde npm@6, npm revisa automaticamente toda requisição de instalação. Além disso, você pode usar o `npm audit` para analisar sua árvore de dependências.
-
-```bash
-$ npm audit
-```
-
-Se você deseja ficar mais seguro, considere [Snyk](https://snyk.io/).
-
-Snyk oferece tanto uma [ferramenta de linha de comando](https://www.npmjs.com/package/snyk) quanto uma [integração com um Github](https://snyk.io/docs/github) que verifica a sua aplicação no [banco de dados de vulnerabilidades de fonte aberta do Snyk](https://snyk.io/vuln/) para quaisquer vulnerabilidades conhecidas em suas dependências. Instalar CLI da seguinte forma:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use este comando para testar suas vulnerabilidades:
-
-```bash
-$ snyk test
-```
-
-### Evitar outras vulnerabilidades conhecidas
-
-Fique atento às recomendações do
-Node Security
-Project que podem afetar o Express ou outros módulos usados
-pelo seu aplicativo. Em geral, o Node Security Project é um excelente
-recurso para conhecimento e ferramentas sobre segurança do Node.
-
-Finalmente, os aplicativos do Express - como outros aplicativos web - podem estar vulneráveis a uma variedade de ataques baseados na
-web. Familiarize-se com [vulnerabilidades web](https://www.owasp.org/www-project-top-ten/) conhecidas e tome precauções para evitá-las.
-
-## Considerações adicionais
-
-Aqui estão algumas recomendações adicionais da excelente Lista
-de Verificação de Segurança do Node.js. Refira-se a esta postagem do blog para obter todos os detalhes destas recomendações:
-
-- Sempre filtrar e limpar a entrada do usuário para se proteger de ataques de cross-site scripting (XSS) e injeção de comando.
-- Proteja-se contra ataques de injeção de SQLs usando consultas parametrizadas ou instruções preparadas.
-- Use a ferramenta de software livre [sqlmap](http://sqlmap.org/) para detectar
-  vulnerabilidades de injeção de SQL no seu aplicativo.
-- Use as ferramentas [nmap](https://nmap.org/) e [sslyze](https://github.com/nabla-c0d3/sslyze) para
-  testar a configuração das suas cifras SSL, chaves, e renegociação, bem como a validade do seu certificado.
-- Use o [safe-regex](https://www.npmjs.com/package/safe-regex) para assegurar que suas expressões regulares não estejam suscetíveis
-  a ataques [negação de serviço de expressões regulares](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
-
-[helmet]: https://helmetjs.github.io/
\ No newline at end of file
diff --git a/pt-br/advanced/developing-template-engines.md b/pt-br/advanced/developing-template-engines.md
deleted file mode 100644
index f4b47c4ea9..0000000000
--- a/pt-br/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-layout: page
-title: Desenvolvendo mecanismos de modelo para o Express
-description: Aprenda a desenvolver motores de modelos personalizados para Express.js usando app.engine(), com exemplos sobre como criar e integrar sua própria lógica de renderização de templates.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# Desenvolvendo mecanismos de modelo para o Express
-
-Use o método `app.engine(ext, callback)`
-para criar seu próprio mecanismo de modelo. `ext`
-refere-se à extensão do arquivo, e  `callback` é a
-função de mecanismo de modelo, que aceita os seguintes itens como
-parâmetros: a localização do arquivo, o objeto de opções, e a função
-de retorno de chamada.
-
-O código a seguir é um exemplo de implementação de um mecanismo
-de modelo muito simples para renderização de arquivos `.ntl`.
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Seu aplicativo estará agora habilitado a renderizar arquivos `.ntl`. Crie
-um arquivo chamado `index.ntl` no diretório
-`views` com o seguinte conteúdo.
-
-```pug
-#title#
-#message#
-```
-
-Em seguida, crie a seguinte rota no seu aplicativo.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Ao fazer uma solicitação à página inicial, o `index.ntl` será renderizado como HTML.
\ No newline at end of file
diff --git a/pt-br/advanced/healthcheck-graceful-shutdown.md b/pt-br/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 5b3257d30b..0000000000
--- a/pt-br/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Verificação de integridade e Desligamento Gracioso
-description: Aprenda como implementar verificações de integridade e encerramentos graciosos em aplicativos Express, para melhorar a confiabilidade, gerenciar implantações e integrar com balanceadores de carga como Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Verificação de integridade e Desligamento Gracioso
-
-## Desligamento Gracioso
-
-Quando você publica uma nova versão do seu aplicativo, você deve substituir a versão anterior. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### Exemplo
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Verificações de integridade
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. Por exemplo, [Kubernetes tem dois exames de saúde](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/pt-br/advanced/security-updates.md b/pt-br/advanced/security-updates.md
deleted file mode 100644
index 854a685bd2..0000000000
--- a/pt-br/advanced/security-updates.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-layout: page
-title: Atualizações de segurança do Express
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# Atualizações de segurança
-
-<div class="doc-box doc-notice" markdown="1">
-As vulnerabilidades do Node.js afetam diretamente o Express. Portanto
-[fique atento às
-vulnerabilidades do Node.js](https://nodejs.org
-/en/blog/vulnerability/) e certifique-se de que você está
-usando a versão estável mais recente do Node.js.
-</div>
-
-A lista abaixo enumera as vulnerabilidades do Express que foram
-corrigidas na versão da atualização especificadas.
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - Corrigida a vulnerabilidade de divulgação do caminho
-    raiz no `express.static`, `res.sendfile`, e `res.sendFile`
-- 4.10.7
-  - Corrigida a vulnerabilidade de redirecionamento aberto no `express.static` ([recomendação](https://npmjs.com/advisories/35),
-    [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 4.8.8
-  - Corrigida a vulnerabilidade de travessia de diretório no `express.static` ([recomendação](http://npmjs.com/advisories/32), [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
-- 4.8.4
-  - O Node.js 0.10 pode vazar os `fd`s em certas situações que afetam o `express.static` e o
-    `res.sendfile`. Solicitações maliciosas podem causar os `fd`s a vazar e eventualmente levar a erros de
-    `EMFILE` e servidores sem capacidade de resposta.
-- 4.8.0
-  - Matrizes esparsas que possuem índices extremamente altos na sequência de consulta podem fazer com que o processo sofra um
-    esgotamento de memória e derrubar o servidor.
-  - Objetos de sequência de consulta extremamente aninhados podem fazer com que o processo fique bloqueado e o servidor
-    temporariamente não responsivo.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x support is ending soon**
-
-This series will continue to receive only security updates and bug fixes until July 2015. It is highly recommended to upgrade to Express 4.x.
-
-Se você não puder atualizar as últimas 3.x, por favor considere as [Opções de Suporte Comercial](/{{ page.lang }}/support#comercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - Corrigida a vulnerabilidade de divulgação do caminho
-    raiz no `express.static`, `res.sendfile`, e `res.sendFile`
-- 3.19.0
-  - Corrigida a vulnerabilidade de redirecionamento aberto no `express.static` ([recomendação](https://npmjs.com/advisories/35),
-    [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
-- 3.16.10
-  - Corrigida a vulnerabilidade de travessia de diretório no `express.static`.
-- 3.16.6
-  - O Node.js 0.10 pode vazar os `fd`s em certas situações que afetam o `express.static` e o
-    `res.sendfile`. Solicitações maliciosas podem causar os `fd`s a vazar e eventualmente levar a erros de
-    `EMFILE` e servidores sem capacidade de resposta.
-- 3.16.0
-  - Matrizes esparsas que possuem índices extremamente altos na sequência de consulta podem fazer com que o processo sofra um
-    esgotamento de memória e derrubar o servidor.
-  - Objetos de sequência de consulta extremamente aninhados podem fazer com que o processo fique bloqueado e o servidor
-    temporariamente não responsivo.
-- 3.3.0
-  - A resposta 404 de uma tentativa de substituição de um método não suportado era suscetível a ataques de cross-site scripting.
\ No newline at end of file
diff --git a/pt-br/api.md b/pt-br/api.md
deleted file mode 100644
index 821025c6e0..0000000000
--- a/pt-br/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - Referência da API
-description: Acesse a referência da API para Express.js , detalhando todos os módulos, métodos e propriedades para construir aplicações web com esta versão.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/pt-br/changelog/index.md b/pt-br/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/pt-br/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/pt-br/guide/behind-proxies.md b/pt-br/guide/behind-proxies.md
deleted file mode 100644
index 4a9af0f11e..0000000000
--- a/pt-br/guide/behind-proxies.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-layout: page
-title: Express atrás de proxies
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# Express atrás de proxies
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-Ao executar um aplicativo do Express atrás de um proxy,
-configure (usando [app.set()](/{{ page.lang }}/4x/api.html#app.set)) a variável do
-aplicativo `trust proxy` para um dos valores
-listados na seguinte tabela.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>Tipo</th><th>Valor</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>Booleano</td>
-<td markdown="1">
-Se `true`, o endereço de IP do cliente será
-compreendido como a entrada mais a esquerda no cabeçalho `X-Forwarded-*`.
-
-Se `false`, o aplicativo é compreendido como
-exposto diretamente à Internet e o endereço de IP do cliente é
-derivado a partir do `req.connection.remoteAddress`. Esta
-é a configuração padrão.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-É possível configurar endereços de IP de qualquer uma das
-formas a seguir:
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-Quando especificados, os endereços de IP ou sub-redes são
-excluídos do processo de determinação de endereço, e o endereço de
-IP não confiável mais próximos do servidor de aplicativos é
-determinado como o endereço de IP do cliente. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>Número</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">O valor de [req.hostname](/{{ page.lang }}/api.html#req.hostname) é
-derivado do valor configurado no cabeçalho
-`X-Forwarded-Host`, que pode ser configurado pelo
-cliente ou pelo proxy.
-  </li>
-  <li markdown="1">`X-Forwarded-Proto` pode ser
-configurado pelo proxy reverso para dizer ao aplicativo se ele é
-`https` ou `http` ou até um nome
-inválido. Este valor é refletido pelo [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">Os valores [req.ip](/{{ page.lang }}/api.html#req.ip) e
-[req.ips](/{{ page.lang }}/api.html#req.ips) são populados com a lista de
-endereços do `X-Forwarded-For`.
-  </li>
-</ul>
-
-A configuração do `trust proxy` é
-implementada usando o pacote
-[proxy-addr](https://www.npmjs.com/package/proxy-addr). Para
-obter mais informações, consulte a documentação.
diff --git a/pt-br/guide/database-integration.md b/pt-br/guide/database-integration.md
deleted file mode 100644
index b7d6393934..0000000000
--- a/pt-br/guide/database-integration.md
+++ /dev/null
@@ -1,511 +0,0 @@
----
-layout: page
-title: Integração de banco de dados do Express
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# Integração de Banco de dados
-
-A inclusão da capacidade de se conectar à banco de dados em aplicativos do Express é apenas uma questão de se carregar um driver
-Node.js apropriado para o banco de dados no seu aplicativo. Este documento explica brevemente como incluir e utilizar alguns dos mais
-populares módulos do Node.js para sistemas de bancos de dados no seu aplicativo do Express:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-Estes drivers de banco de dados estão entre os muitos que estão
-disponíveis. Para obter outras opções, procure no site [npm](https://www.npmjs.com/).
-</div>
-
-## Cassandra
-
-**Módulo**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install cassandra-driver
-```
-
-### Exemplo
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### Installation
-
-```bash
-$ npm install couchbase
-```
-
-### Exemplo
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**Módulo**: [nano](https://github.com/dscape/nano)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install nano
-```
-
-### Exemplo
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**Módulo**: [levelup](https://github.com/rvagg/node-levelup)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### Exemplo
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**Módulo**: [mysql](https://github.com/felixge/node-mysql/)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install mysql
-```
-
-### Exemplo
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**Módulo**: [mongodb](https://github.com/mongodb/node-mongodb-native)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install mongodb
-```
-
-### Exemplos.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Exemplos (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-Se desejar um driver de modelo de objeto para o MongoDB,
-consulte em [Mongoose](https://github.com/LearnBoost/mongoose).
-
-## Neo4j
-
-**Módulo**: [apoc](https://github.com/hacksparrow/apoc)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install neo4j-driver
-```
-
-### Exemplo
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Módulo**: [pg](https://github.com/brianc/node-postgres)
-**Instalação**
-
-### Installation
-
-NOTA: [Ver pré-requisitos de instalação](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### Exemplo
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Módulo**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-
-### Installation
-
-```bash
-$ npm install pg-promise
-```
-
-### Exemplo
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**Módulo**: [redis](https://github.com/mranney/node_redis)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install redis
-```
-
-### Exemplo
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Módulo**: [redis](https://github.com/tediousjs/tedious)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install tedious
-```
-
-### Exemplo
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**Módulo**: [sqlite3](https://github.com/mapbox/node-sqlite3)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install sqlite3
-```
-
-### Exemplo
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**Módulo**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
-**Instalação**
-
-### Installation
-
-```bash
-$ npm install elasticsearch
-```
-
-### Exemplo
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/pt-br/guide/debugging.md b/pt-br/guide/debugging.md
deleted file mode 100644
index e19d81b765..0000000000
--- a/pt-br/guide/debugging.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-layout: page
-title: Depurando o Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# Depurando o Express
-
-Para ver todos os logs interno usados no Express, configure a
-variável de ambiente `DEBUG` para
-`express:*` ao ativar seu aplicativo.
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-No Windows, use o comando correspondente.
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-Executar este comando no aplicativo padrão gerado pelo
-[express generator](/{{ page.lang }}/starter/generator.html) imprime a seguinte saída:
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-Quando uma solicitação é feita em seguida para o aplicativo,
-você verá os logs especificados no código do Express:
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-Para ver os logs apenas da implementação do roteador configure
-o valor de `DEBUG` para
-`express:router`. Do mesmo modo, para ver os logs
-apenas da implementação do aplicativo configure o valor de
-`DEBUG` para `express:application`,
-e assim por diante.
-
-## Aplicativos gerados pelo `express`
-
-Um aplicativo gerado pelo comando `express`
-também usa o módulo de `debug` e o seu namespace de
-depuração está com o escopo definido para o nome do aplicativo.
-
-Por exemplo, se você gerou o aplicativo com o `$ express
-sample-app`, é possível ativar as instruções de depuração
-com o seguinte comando:
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-É possível especificar mais do que um namespace de depuração
-designando uma lista de nomes separados por vírgulas:
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Opções avançadas
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Nome                | Objetivo                                                          |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-Veja a documentação do Node.js para
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-para a lista completa.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/pt-br/guide/error-handling.md b/pt-br/guide/error-handling.md
deleted file mode 100644
index b58be964c3..0000000000
--- a/pt-br/guide/error-handling.md
+++ /dev/null
@@ -1,326 +0,0 @@
----
-layout: page
-title: Manipulação de erros do Express
-description: Entenda como o Express.js lida com erros em código síncrono e assíncrono e aprenda a implementar erro personalizado de manipulação de intermediários para seus aplicativos.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# Manipulação de erros
-
-_Manipulação de erros_ refere-se a como as capturas Expressas e processa erros que
-ocorrem de forma sincronizada e assíncrona. Express vem com um manipulador de erro padrão
-para que você não precise escrever o seu próprio para começar.
-
-## Captura de Erros
-
-É importante garantir que Express capture os erros que ocorrem enquanto
-está rodando manipuladores de rotas e intermediários.
-
-Erros que ocorrem no código síncrono dentro dos manipuladores de rota e middleware
-não exigem trabalho extra. Se o código síncrono lançar um erro, então o Express irá
-capturá-lo e processá-lo. Por exemplo:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-Para erros retornados de funções assíncronas, invocados pelos manipuladores de rota
-e intermediário, você deve passá-los para a função `next()`, onde o Express irá capturá-los a
-e processá-los.  Por exemplo:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Se você tiver um manipulador de rota com as funções de retorno
-de chamada é possível usar o parâmetro `route`
-para ignorar o próximo manipulador de rota.
-Por exemplo:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-Se `getUserById` lança um erro ou rejeita, `next` será chamado com
-o erro lançado ou o valor rejeitado. Se nenhum valor rejeitado for fornecido, `next`
-será chamado com um objeto de erro padrão fornecido pelo roteador Express.
-
-Se passar qualquer coisa para a função `next()`
-(exceto a sequência de caracteres `'route'`),
-o Express considera a solicitação atual como estando em erro e irá
-ignorar quaisquer funções restantes de roteamento e middleware que
-não sejam de manipulação de erros.
-
-Se o callback em uma sequência não fornecer dados, somente erros, você pode simplificar
-este código da seguinte forma:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-No exemplo acima, `next` é fornecido como o callback para `fs.writeFile`,
-que é chamado com ou sem erros. Se não houver erro, o segundo manipulador
-é executado, caso contrário as capturas e processam o erro.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. Por exemplo:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  Por exemplo:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. Por exemplo:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## O Manipulador de Erros Padrão
-
-O Express vem com um manipulador de erros integrado, que cuida
-de qualquer erro que possa ser encontrado no aplicativo. Essa função
-de middleware de manipulação de erros padrão é incluída no final da
-pilha de funções de middleware.
-
-se você passar um erro para o `next()` e você
-não manipulá-lo com um manipulador de erros, ele irá ser manipulado
-por um manipulador de erros integrado; o erro será escrito no cliente
-com o rastreio de pilha. O rastreio de pilha não será incluído no
-ambiente de produção.
-
-<div class="doc-box doc-info" markdown="1">
-Configura a variável de ambiente `NODE_ENV` para
-`production`, para executar o aplicativo em modo de
-produção.
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- A 'res.statusMessage' é definida de acordo com o código de status.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-Se você chamar o `next()` com um erro após ter
-inicializado escrevendo a resposta (por exemplo, se encontrar um erro
-enquanto passa a resposta ao cliente) o manipulador de erros padrão do
-Express fecha a conexão e falha a solicitação.
-
-Portanto ao incluir um manipulador de erro customizado, você
-desejará delegar para o mecanismo de manipulação de erros padrão no
-Express, quando os cabeçalhos já tiverem sido enviados para o cliente:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-Define error-handling middleware functions in the same way as other middleware functions,
-except error-handling functions have four arguments instead of three:
-`(err, req, res, next)`. Por exemplo:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Você define os middlewares de manipulação de erros por
-último, após outros `app.use()` e chamads de rota; por
-exemplo:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Repostas de dentro de uma função de middleware podem estar em
-qualquer formato que preferir, como uma página HTML de erros, uma
-mensagem simples, ou uma sequência de caracteres JSON.
-
-Para propósitos organizacionais (e estrutura de alto nível), é
-possível definir várias funções de middleware de manipulação de
-erros, de forma muito parecida como você faria com funções de
-middleware comuns. Por exemplo, se desejar definir um manipulador de
-erros para solicitações feitas usando o `XHR`, e
-aqueles sem, você pode usar os seguintes comandos:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-Neste exemplo, o `logErrors` genérico pode
-escrever informações de solicitações e erros no
-`stderr`, por exemplo:
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-Também neste exemplo, o `clientErrorHandler` é
-definido como segue; neste caso, o erro é explicitamente passado para
-o próximo:
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-A função "catch-all" `errorHandler` pode ser implementada como segue:
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. Por exemplo:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-Neste exemplo, o manipulador `getPaidContent`
-será ignorado mas qualquer manipulador remanescente no
-`app` para
-`/a_route_behind_paywall` continuariam sendo
-executados.
-
-<div class="doc-box doc-info" markdown="1">
-Chamadas para `next()` e `next(err)`
-indicam que o manipulador atual está completo e em qual estado.  `next(err)` irá ignorar todos os manipuladores
-remanescentes na cadeia exceto por aqueles que estão configurados
-para manipular erros como descrito acima.
-</div>
diff --git a/pt-br/guide/migrating-4.md b/pt-br/guide/migrating-4.md
deleted file mode 100644
index 859f184f59..0000000000
--- a/pt-br/guide/migrating-4.md
+++ /dev/null
@@ -1,654 +0,0 @@
----
-layout: page
-title: Migrando para o Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# Migrando para o Express 4
-
-<h2 id="overview">Visão Geral</h2>
-
-Express 4 é uma alteração de ruptura do Express 3. Isso significa que um aplicativo Express 3 existente não irá funcionar
-se você atualizar a versão do Express nas suas dependências.
-
-Este artigo cobre:
-
-<ul class="doclist">
-  <li><a href="#changes">Mudanças no Express 4.</a></li>
-  <li><a href="#example-migration">Um exemplo</a> de migração de um aplicativo do Express 3 para o Express 4.</li>
-  <li><a href="#app-gen">Fazendo o upgrade para o gerador de aplicativos do Express 4.</a></li>
-</ul>
-
-<h2 id="changes">Mudanças no Express 4</h2>
-
-Existem várias mudanças significativas no Express 4:
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">Mudanças no sistema de roteamento.</a></li>
-  <li><a href="#other-changes">Várias outras mudanças.</a></li>
-</ul>
-
-Consulte também:
-
-- [Novos recursos no 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migrando do 3.x para o 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Mudanças no núcleo e sistemas middleware do Express
-</h3>
-
-O Express 4 não depende mais do Connect, e remove todos os
-middlewares integrados do seu núcleo, exceto pela função
-`express.static`. Isso significa que o
-Express é agora um framework web de middleware e roteamento
-independente, e que o versionamento e as liberações do Express não
-são mais afetadas por atualizações nos middlewares.
-
-Sem os middlewares integrados, você deve incluir explicitamente todos os middlewares necessários para a execução do seu aplicativo. Simplesmente siga esses passos:
-
-1. Instale o módulo: `npm install --save <module-name>`
-2. No seu aplicativo, solicite o módulo: `require('module-name')`
-3. Use o módulo de acordo com sua documentação: `app.use( ... )`
-
-A tabela a seguir lista os middlewares do Express 3 e suas contrapartes no Express 4.
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-Aqui está a [lista completa](https://github.com/senchalabs/connect#middleware) de middlewares do Express 4.
-
-Na maioria dos casos, é possível simplesmente substituir a antiga versão 3 do middleware pela sua contraparte do Express4. Para obter detalhes, consulte a documentação do módulo no GitHub.
-
-<h4 id="app-use">O <code>app.use</code> aceita parâmetros</h4>
-
-Na versão 4 é possível utilizar uma variável de parâmetro para
-definir o caminho onde as funções do middleware estão carregadas, e
-em seguida ler o valor do parâmetro a partir do manipulador de rota.
-Por exemplo:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-O sistema de roteamento
-</h3>
-
-Os aplicativos agora carregam implicitamente middlewares de
-roteamento, para que não seja mais necessário se preocupar com a
-ordem em que os middlewares são carregados no que diz respeito ao
-middleware `router`.
-
-A forma como as rotas são definidas são as mesmas, mas  o
-sistema de roteamento possui dois novos recursos para ajudá-lo a
-organizar suas rotas:
-
-{: .doclist }
-
-- Um novo método, `app.route()`, para criar
-  manipuladores de rotas encadeáveis para um caminho de rota.
-- Uma nova classe, `express.Router`, para
-  criar manipuladores de rotas modulares montáveis
-
-<h4 id="app-route">O método <code>app.route()</code></h4>
-
-O novo método `app.route()` permite que sejam
-criados manipuladores de rotas encadeáveis para um caminho de rota. Como o caminho é especificado em uma localização única, criar rotas
-modulares é útil, já que reduz redundâncias e erros tipográficos. Para
-obter mais informações sobre rotas, consulte a [`documentação do Router()` ](/{{ page.lang }}/4x/api.html#router).
-
-Aqui está um exemplo de manipuladores de rotas encadeáveis que
-são definidos usando a função `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router">classe <code>express.Router</code></h4>
-
-O outro recurso que ajuda na organização das rotas é uma nova
-classe, `express.Router`, que pode ser usada para
-criar manipuladores de rotas modulares montáveis. Uma instância de `Router` é um middleware e sistema
-de roteamento completo; por essa razão ela é frequentemente referida
-como um "mini-aplicativo"
-
-O seguinte exemplo cria um roteador como um módulo, carrega o
-middleware nele, define algumas rotas, e monta-o em um caminho no
-aplicativo principal.
-
-Por exemplo, cria um arquivo roteador chamado
-`birds.js` no diretório do aplicativo, com o
-conteúdo a seguir:
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Em seguida, carregue o módulo roteador no aplicativo:
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-O aplicativo será agora capaz de manipular solicitações aos
-caminhos `/birds` e `/birds/about`,
-e irá chamar o middleware `timeLog`
-que é específico para a rota.
-
-<h3 id="other-changes">
-Outras mudanças
-</h3>
-
-A seguinte tabela lista outras pequenas, porém importantes, mudanças no Express 4:
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Objeto</th>
-<th>Descrição</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>O Express 4 requer o Node.js 0.10.x ou posterior e descartou o
-suporte ao Node.js 0.8.x.</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-O módulo `http` não é mais necessário, a não ser
-que você precise trabalhar diretamente com ele (socket.io/SPDY/HTTPS). O
-aplicativo pode ser iniciado usando a função `app.listen()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-A função `app.configure()` foi removida.  Use a função `process.env.NODE_ENV` ou
-`app.get('env')` para detectar o ambiente e
-configurar o aplicativo de acordo com ele.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-A propriedade de aplicativo `json spaces` está
-desativada por padrão no Express 4.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-Use `req.accepts()`, `req.acceptsEncodings()`,
-`req.acceptsCharsets()`, e `req.acceptsLanguages()`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-Não resolve mais URLs relativas.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Era uma matriz; agora é um objeto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Era uma função; agora é um objeto.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-Mudado para `res.headersSent`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-Agora disponível como `app.mountpath`.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-Removido.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-Removido.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-A funcionalidade é agora limitada a configurar o valor básico do
-cookie. Use `res.cookie()` para funcionalidades
-adicionais.
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">Exemplo de migração de aplicativo</h2>
-
-Aqui está um eemplo de migração de um aplicativo Express 3 para
-o Express 4.
-Os arquivos de interesse são `app.js` e `package.json`.
-
-<h3 id="">
-Aplicativo da Versão 3
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-Considere um aplicativo do Express v.3 com o seguinte arquivo `app.js`:
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-O arquivo `package.json` que acompanha a
-versão 3 pode parecer com algo assim:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-Processo
-</h3>
-
-Comece o processo de migração instalando os middlewares
-necessários para o aplicativo Express 4 e atualizando o Express e o
-Pug para as suas respectivas versões mais recentes com o seguinte
-comando:
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-Faça as seguintes alterações no `app.js`:
-
-1. As funções de middleware integradas do Express `express.favicon`,
-   `express.logger`, `express.methodOverride`,
-   `express.session`, `express.bodyParser` e
-   `express.errorHandler` não estão mais disponíveis no objeto `express`. É
-   preciso instalar manualmente as alternativas e carregá-las no aplicativo.
-
-2. Não é mais necessário carregar a função `app.router`.
-   Ela não é um objeto válido para aplicativos Express 4, portanto
-   remova o código do `app.use(app.router);`.
-
-3. Certifique-se deque as funções de middleware sejam carregadas na ordem correta - carregar a
-   `errorHandler` após carregar as rotas de aplicativo.
-
-<h3 id="">Aplicativo da Versão 4</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-A execução do comando `npm` acima irá
-atualizar o `package.json` como a seguir:
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Em seguida, remova o código inválido, carregue o middleware
-necessário e faça outras alterações conforme necessárias. O arquivo `app.js` irá parecer com isso:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-A não ser que precise trabalhar diretamente com
-o módulo `http` (socket.io/SPDY/HTTPS),
-carregá-lo não é necessário, e o aplicativo pode ser iniciado
-simplesmente desta forma:
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Execute o aplicativo</h3>
-
-O processo de migração está concluído, e o aplicativo é agora
-um aplicativo Express 4. Para confirmar, inicie o aplicativo usando o
-seguinte comando:
-
-```bash
-$ node .
-```
-
-Carregue [http://localhost:3000](http://localhost:3000)
-e veja a página inicial sendo renderizada pelo Express 4.
-
-<h2 id="app-gen">Fazendo o upgrade para o gerador de aplicativos do
-Express 4</h2>
-
-A ferramenta de linha de comandos para gerar um aplicativo
-Express ainda é a `express`, mas para fazer o
-upgrade para a nova versão , é preciso desinstalar o gerador de
-aplicativos Express 3 e, em seguida, instalar o novo `express-generator`.
-
-<h3 id="">Instalação </h3>
-
-Se já tiver o gerador de aplicativos do Express 3 instalado no
-seu sistema, é preciso desinstalá-lo:
-
-```bash
-$ npm uninstall -g express
-```
-
-Dependendo de como os seus privilégios de arquivos e diretórios estão
-configurados, pode ser necessário executar este comando com `sudo`.
-
-Agora instale o novo gerador:
-
-```bash
-$ npm install -g express-generator
-```
-
-Dependendo de como os seus privilégios de arquivos e diretórios estão
-configurados, pode ser necessário executar este comando com `sudo`.
-
-Agora o comando `express` no seu sistema está
-atualizado para o gerador do Express 4.
-
-<h3 id="">Mudanças no gerador de aplicativos </h3>
-
-As opções e o uso do comando permanecem em grande parte as
-mesmas, com as seguintes exceções:
-
-{: .doclist }
-
-- Foi removida a opção `--sessions`.
-- Foi removida a opção `--jshtml`.
-- Foi incluída a opção `--hogan` para
-  suportar o [Hogan.js](http://twitter.github.io/hogan.js/).
-
-<h3 id="">Exemplo</h3>
-
-Execute o seguinte comando para criar um aplicativo do Express 4:
-
-```bash
-$ express app4
-```
-
-Se olhar o conteúdo do arquivo `app4/app.js`,
-você verá que todas as funções de middleware (exceto
-`express.static`) que são requeridas pelo aplicativo
-estão a carregadas como módulos independentes, e o middleware de
-`router` não está mais explicitamente carregado no
-aplicativo.
-
-Você irá também notar que o arquivo `app.js` é
-agora um módulo do Node.js, ao invés do aplicativo independente
-gerado pelo antigo gerador.
-
-Após instalar as dependências, inicie o aplicativo usando o
-seguinte comando:
-
-```bash
-$ npm start
-```
-
-Se olhar o script de inicialização npm no arquivo
-`package.json`, você irá notar que o comando real
-que inicia o aplicativo é o `node ./bin/www`, que
-antes era `node app.js` no Express 3.
-
-Como o arquivo `app.js` que foi gerado pelo
-gerador do Express 4 é agora um módulo do Node.js, ele não pode mais
-ser iniciado independentemente como um aplicativo
-(a não ser que modifique o código). O módulo deve ser carregado em um
-arquivo Node.js e iniciado através do arquivo Node.js. O arquivo
-Node.js é `./bin/www`
-neste caso.
-
-Nem o diretório `bin` e nem o arquivo sem
-extensão `www` são obrigatórios para a criação ou
-inicialização de um aplicativo Express. Eles são apenas sugestões
-feitas pelo gerador, portanto fique a vontade para modificá-los para
-adequá-los às suas necessidades.
-
-Se livre do diretório `www` e mantenha as
-coisas "da maneira do Express 3", exclua a linha que diz
-`module.exports = app;` no final do arquivo
-`app.js`, em seguida cole o seguinte código em seu
-lugar:
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-Assegure-se de carregar o módulo `debug` em
-cima do arquivo `app.js` usando o seguinte código:
-
-```js
-var debug = require('debug')('app4')
-```
-
-Em seguida, mude o `"start": "node ./bin/www"`
-no arquivo `package.json` para `"start": "node
-app.js"`.
-
-Você agora moveu a funcionalidade do
-`./bin/www` de volta para o
-`app.js`. Esta mudança não é recomendada, mas o
-exercício ajuda você a entender como o arquivo
-`./bin/www` funciona, e porque o arquivo
-`app.js` não é mais iniciado por conta própria.
diff --git a/pt-br/guide/migrating-5.md b/pt-br/guide/migrating-5.md
deleted file mode 100644
index c9a18847bf..0000000000
--- a/pt-br/guide/migrating-5.md
+++ /dev/null
@@ -1,670 +0,0 @@
----
-layout: page
-title: Migrando para o Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# Migrando para o Express 5
-
-<h2 id="overview">Visão Geral</h2>
-
-O Express 5 não é muito diferente do Express 4: As mudanças na
-API não são tão significantes quanto as do 3.0 para o 4.0. Apesar de
-a API básica permanecer a mesma, ainda existem mudanças disruptivas;
-em outras palavras um programa do Express 4 existente pode não
-funcionar se você atualizá-lo para usar o Express 5.
-
-Para instalar esta versão, você precisa ter uma versão 18 ou superior de Node.js. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-É possível em seguida executar seus testes automatizados para
-verificar o que falha, e corrigir os problemas de acordo com as
-atualizações abaixo. Após endereçar as falhas nos testes, execute o
-seu aplicativo para verificar quais erros ocorrem. Você descobrirá
-imediatamente se o aplicativo utiliza quaisquer métodos ou
-propriedades que não são suportados.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Mudanças no Express 5</h2>
-
-**Métodos e propriedades removidas**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">Nomes de métodos pluralizados</a></li>
-  <li><a href="#leading">Vírgula no início no argumento nome para o  app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**Melhorias**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Rota correspondente à sintaxe</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**Mudadas**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## Métodos e propriedades removidas
-
-Se estiver usando qualquer um desses métodos ou propriedades
-no seu aplicativo, ele irá quebrar. Portanto, será necessário alterar
-o seu aplicativo após fazer a atualização para a versão 5.
-
-<h3 id="app.del">app.del()</h3>
-
-O Express 5 não suporta mais a função `app.del()`. Se
-você usas esta função um erro será lançado. Para registrar rotas HTTP DELETE, use a função `app.delete()` ao invés disso.
-
-Inicialmente `del` era usada ao invés de
-`delete`, porque `delete` é uma
-palavra-chave reservada no JavaScript. Entretanto, a partir do ECMAScript 6,
-`delete` e outras palavras-chave reservadas podem
-legalmente ser usadas como nomes de propriedades.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-A assinatura `app.param(fn)` foi usada para
-modificar o comportamento da função `app.param(name, fn)`. Ela
-foi descontinuada desde a v4.11.0, e o Express 5 não a suporta mais de nenhuma forma.
-
-<h3 id="plural">Nomes de métodos pluralizados</h3>
-
-Os seguintes nomes de métodos podem ser pluralizados. No
-Express 4, o uso dos métodos antigos resultava em um aviso de
-descontinuação.  O Express 5 não os suporta mais de forma nenhuma: Express 5 não os suporta mais:
-
-`req.acceptsLanguage()` é substituído por `req.acceptsLanguages()`.
-
-`req.acceptsCharset()` é substituído por `req.acceptsCharsets()`.
-
-`req.acceptsEncoding()` é substituído por `req.acceptsEncodings()`.
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">Dois pontos no começo (:) do nome do app.param(name, fn)</h3>
-
-Um caractere de dois pontos (:) no início do nome para a função
-`app.param(name, fn)` é um remanescente do Express
-3, e para fins de compatibilidade com versões anteriores, o Express 4
-suportava-o com um aviso de descontinuação. O Express 5 irá
-silenciosamente ignorá-lo e usar o nome do parâmetro sem prefixá-lo
-com os dois pontos.
-
-Isso não deve afetar o seu código se você seguiu a documentação
-do Express 4 do [app.param](/{{ page.lang }}/4x/api.html#app.param), já que ela não
-menciona os dois pontos no início.
-
-<h3 id="req.param">req.param(name)</h3>
-
-Este é um método potencialmente confuso e perigoso de recuperação de dados de formulário foi removido. Você precisará agora especificamente olhar para o nome do parâmetro enviado no objeto `req.params`,
-`req.body`, ou `req.query`.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-O Express 5 não suporta mais a assinatura `res.json(obj, status)`. Ao
-invés disso, configure o status e então encadeie-o ao método `res.json()` assim:
-`res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-O Express 5 não suporta mais a assinatura `res.jsonp(obj, status)`. Ao invés disso, configure o status e então encadeie-o ao método
-`res.jsonp()` assim: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-O Express 5 não suporta mais a assinatura `res.send(obj, status)`. Ao invés disso, configure o status e então encadeie-o ao método
-`res.send()` assim: `res.status(status).send(obj)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-O Express 5 não suporta mais a assinatura <code>res.send(<em>status</em>)</code>, onde _`status`_
-é um número. Ao invés disso, use a função
-`res.sendStatus(statusCode)`, que configura o código
-do status do cabeçalho de resposta HTTP  e envia a versão de texto do
-código: "Não Encontrado", "Erro Interno de Servidor", e assim por
-diante.
-Se precisar enviar um número usando a função
-`res.send()`, coloque o número entre aspas para
-converte-lo para um sequência de caracteres, para que o Express não o
-interprete como uma tentativa de usar a assinatura antiga não
-suportada.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-A função `res.sendfile()` foi substituída pela
-versão em formato camel-case `res.sendFile()` no
-Express 5.
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- Arquivos JavaScript (.js): agora "text/javascript" ao invés de "application/javascript"
-- Arquivos JSON (.json): agora "application/json" em vez de "text/json"
-- Arquivos CSS (.css): agora "text/css" em vez de "text/plain"
-- Arquivos XML (.xml): agora "application/xml" em vez de "text/xml"
-- Arquivos de fonte (.woff): agora "font/woff" em vez de "application/font-woff"
-- Arquivos SVG (.svg): agora "image/svg+xml" em vez de "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-Você pode substituir as assinaturas obsoletas pelo seguinte comando:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. Ela
-foi descontinuada desde a v4.11.0, e o Express 5 não a suporta mais de nenhuma forma.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## Mudadas
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. Por exemplo:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-Por exemplo:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-O objeto `app.router`, que foi removido no
-Express 4, está de volta no Express 5. Na nove versão, este objeto é
-apenas uma referência para o roteador Express base, diferentemente do
-Express 3, onde um aplicativo tinha que carregá-lo explicitamente.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-No Express 4, a função `req.host`
-incorretamente removia o número da porta caso estivesse presente. No
-Express 5 o número da porta é mantido.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## Melhorias
-
-<h3 id="res.render">res.render()</h3>
-
-Este método agora impinge comportamento assíncrono  para todos
-os mecanismos de visualização, evitando erros causados pelos
-mecanismos de visualização que tinham uma implementação síncrona e
-que violavam a interface recomendada.
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/pt-br/guide/overriding-express-api.md b/pt-br/guide/overriding-express-api.md
deleted file mode 100644
index 039cb593ad..0000000000
--- a/pt-br/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Sobrescrevendo a API Express
-description: Descubra como personalizar e estender a API do Express.js substituindo métodos e propriedades nos objetos de solicitação e resposta usando protótipos.
-menu: guide
-order: 4
----
-
-# Sobrescrevendo a API Express
-
-A API do Express consiste de vários métodos e propriedades nos objetos de solicitação e resposta. Estas são herdadas pelo protótipo. Há dois pontos de extensão para a API Express:
-
-1. Os protótipos globais em `express.request` e `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Métodos
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-A seguir é um exemplo de substituição do comportamento de [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-O método sobrescrito agora pode ser usado dessa maneira:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Propriedades
-
-As propriedades da API Express também são:
-
-1. Propriedades atribuídas (ex: `req.baseUrl`, `req.originalUrl`)
-2. Definido como getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/pt-br/guide/routing.md b/pt-br/guide/routing.md
deleted file mode 100644
index 9454be8146..0000000000
--- a/pt-br/guide/routing.md
+++ /dev/null
@@ -1,454 +0,0 @@
----
-layout: page
-title: Roteamento no Express
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# Roteamento
-
-O _Roteamento_ refere-se a como os _endpoints_ de uma aplicação (URIs) respondem às requisições do cliente.
-Para uma introdução ao roteamento, consulte [Roteamento básico](/{{ page.lang }}/starter/basic-routing.html).
-
-Rotas são definidas utilizando métodos do objeto `app` do Express que correspondem aos métodos HTTP;
-por exemplo, `app.get()` para lidar com requisições GET e `app.post()` para requisições POST. Para a lista completa, veja [app.METHOD](/{{ page.lang }}/4x/api.html#app.METHOD). Você também pode utilizar [app.all()](/{{ page.lang }}/4x/api.html#app.all) para lidar com todos os métodos HTTP
-e [app.use()](/{{ page.lang }}/4x/api.html#app.use) para especificar middleware como funções _callback_
-(Veja [Usando middlewares](/{{ page.lang }}/guide/using-middleware.html) para mais detalhes).
-
-Esses métodos de roteamento especificam uma função _callback_ a ser chamada quando a aplicação
-recebe uma requisição à rota e método HTTP especificados. Em outras palavras, a aplicação "escuta"
-requisições que se encaixam nas rotas e métodos especificados e, quando há alguma correspondência,
-chama a função _callback_ especificada.
-
-Na realidade, métodos de roteamento podem possuir mais de uma função _callback_ como argumento.
-Com múltiplas funções, é importante passar `next` como argumento da função e chamar `next()` para passar o controle para a próxima.
-
-O código a seguir é um exemplo de uma rota muito básica.
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">Métodos de roteamento</h2>
-
-Um método de roteamento é derivado a partir de um dos métodos
-HTTP, e é anexado a uma instância da classe `express`.
-
-o código a seguir é um exemplo de rotas para a raiz do
-aplicativo que estão definidas para os
-métodos GET e POST.
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-O Express suporta métodos que correspondem a todos os métodos de requisição HTTP: `get`, `post`, etc.
-Pra uma lista completa, veja [app.METHOD](/{{ page.lang }}/4x/api.html#app.METHOD).
-
-Existe um método de roteamento especial,
-`app.all()`, que não é derivado de nenhum método
-HTTP. Este método é usado para carregar funções de middleware em um
-caminho para todos os métodos de solicitação. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">Caminhos de rota</h2>
-
-Caminhos de rota, em combinação com os métodos de solicitação,
-definem os terminais em que as solicitações podem ser feitas. Caminhos
-de rota podem ser sequências de caracteres, padrões de sequência, ou
-expressões regulares.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. O Express
-Route Tester é uma ferramenta útil para testar rotas básicas do Express, apesar de não suportar a correspondência de padrões.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Aqui estão alguns exemplos de caminhos de rota baseados em sequências de caracteres
-
-Este caminho de rota irá corresponder a solicitações ao `/qualquer.texto`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-Este caminho de rota irá corresponder a solicitações ao `/ajuda`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-Este caminho de rota corresponde a solicitações à rota raiz, `/`.
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Aqui estão alguns exemplos de caminhos de rota baseados em padrões de sequência
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-Este caminho de rota irá corresponder ao `/abe` e `/abcde`.
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-Este caminho de rota irá corresponder ao `abcd`, `abbcd`, `abbbcd`, e assim por diante.
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-Este caminho de rota irá corresponder ao `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, e assim por diante.
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-Este caminho de rota irá corresponder ao `acd` e `abcd`.
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### Exemplos de caminhos de rota baseados em expressões regulares:
-
-Este caminho de rota irá corresponder a qualquer coisa com um
-"a" no nome.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-Este caminho de rota irá corresponder a `butterfly` e
-`dragonfly`, mas não a `butterflyman`,
-`dragonfly man`, e assim por diante.
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">
-Sequências de consulta não fazem parte dos caminhos de rota.
-</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Manipuladores de rota</h2>
-
-É possível fornecer várias funções _callback_
-que se comportam como [middleware](/{{ page.lang }}/guide/using-middleware.html) para
-manipular uma solicitação. A única exceção é que estes _callbacks_ podem chamar `next('route')` para efetuar um
-bypass nos _callbacks_ restantes. É possível usar
-este mecanismo para impor pré-condições em uma rota, e em seguida
-passar o controle para rotas subsequentes se não houveram razões para
-continuar com a rota atual.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Manipuladores de rota podem estar na forma de uma função, uma
-matriz de funções, ou combinações de ambas, como mostrado nos
-seguintes exemplos.
-
-Uma única função _callback_ pode manipular uma rota. Por exemplo:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-Mais de uma função _callback_ pode manipular uma
-rota (certifique-se de especificar o objeto `next`). Por exemplo:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-Uma matriz de funções _callback_ podem manipular uma
-rota. Por exemplo:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-Uma combinação de funções independentes e matrizes de funções
-podem manipular uma rota. Por exemplo:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">Métodos de resposta</h2>
-
-Os métodos do objeto de resposta (`res`) na
-seguinte tabela  podem enviar uma resposta ao cliente, e finalizar o
-ciclo solicitação-resposta. Se nenhum destes métodos forem chamados a
-partir de um manipulador de rota, a solicitação do cliente será
-deixada em suspenso.
-
-| Método                                                                                                                                                                                                                    | Descrição                                                                                                                                 |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | Solicita que seja efetuado o download de um arquivo                                                                                       |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | Termina o processo de resposta.                                                                                           |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | Envia uma resposta JSON.                                                                                                  |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | Envia uma resposta JSON com suporta ao JSONP.                                                                             |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | Redireciona uma solicitação.                                                                                              |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Renderiza um modelo de visualização.                                                                                      |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | Envia uma resposta de vários tipos.                                                                                       |
-| [res.sendFile](/{{ page.lang }}/4x/api.html#res.sendFile)                          | Envia um arquivo como um fluxo de octeto.                                                                                 |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Configura o código do status de resposta e envia a sua representação em sequência de caracteres como o corpo de resposta. |
-
-<h2 id="app-route">app.route()</h2>
-
-É possível criar manipuladores de rota encadeáveis para um caminho de rota usando o `app.route()`.
-Como o caminho é especificado em uma localização única, criar rotas modulares é útil, já que reduz redundâncias e erros tipográficos. Para obter mais informações sobre rotas, consulte: [documentação do Router()](/{{ page.lang }}/4x/api.html#router).
-
-Aqui está um exemplo de manipuladores de rotas encadeáveis que são definidos usando `app.route()`.
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Use a classe `express.Router` para criar
-manipuladores de rota modulares e montáveis. Uma instância de
-`Router` é um middleware e sistema de roteamento
-completo; por essa razão, ela é frequentemente referida como um
-"mini-aplicativo"
-
-O seguinte exemplo cria um roteador como um módulo, carrega uma
-função de middleware nele, define algumas rotas, e monta o módulo
-router em um caminho no aplicativo principal.
-
-Crie um arquivo de roteador com um arquivo chamado
-`passaros.js` no diretório do aplicativo, com o
-seguinte conteúdo:
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-Em seguida, carregue o módulo roteador no aplicativo:
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-O aplicativo será agora capaz de manipular solicitações aos
-caminhos `/passaros` e `/passaros/ajuda`,
-assim como chamar a função de middleware `timeLog` que
-é específica para a rota.
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/pt-br/guide/using-middleware.md b/pt-br/guide/using-middleware.md
deleted file mode 100644
index a7459f124f..0000000000
--- a/pt-br/guide/using-middleware.md
+++ /dev/null
@@ -1,318 +0,0 @@
----
-layout: page
-title: Usando middlewares do Express
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# Usando middlewares
-
-O Express é uma estrutura web de roteamento e middlewares que
-tem uma funcionalidade mínima por si só: Um aplicativo do Express é
-essencialmente uma série de chamadas de funções de middleware.
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. A próxima função middleware é
-comumente denotada por uma variável chamada `next`.
-
-Funções de middleware podem executar as seguintes tarefas:
-
-- Executar qualquer código.
-- Fazer mudanças nos objetos de solicitação e resposta.
-- Encerrar o ciclo de solicitação-resposta.
-- Chamar a próxima função de middleware na pilha.
-
-Se a atual função de middleware não terminar o ciclo de
-solicitação-resposta, ela precisa chamar `next()`
-para passar o controle para a próxima função de middleware. Caso
-contrário, a solicitação ficará suspensa.
-
-Um aplicativo Express pode usar os seguintes tipos de middleware:
-
-- [Middleware de nível do aplicativo](#middleware.application)
-- [Middleware de nível de roteador](#middleware.router)
-- [Middleware de manipulação de erros](#middleware.error-handling)
-- [Middleware integrado](#middleware.built-in)
-- [Middleware de Terceiros](#middleware.third-party)
-
-É possível carregar middlewares de nível de roteador e de nível do aplicativo com um caminho de montagem opcional.
-É possível também carregar uma série de funções de middleware juntas, o que cria uma sub-pilha do sistema de middleware em um ponto de montagem.
-
-<h2 id='middleware.application'>Middleware de nível do aplicativo</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-Este exemplo mostra uma função de middleware sem um caminho de
-montagem. A função é executada sempre que o aplicativo receber uma
-solicitação.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-Este exemplo mostra uma função de middleware montada no caminho
-`/user/:id`. A função é executada para qualquer tipo
-de solicitação HTTP no caminho `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Este exemplo mostra uma rota e sua função
-manipuladora (sistema de middleware). A função manipula solicitações
-GET ao caminho `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Aqui está um exemplo de carregamento de um série de funções de
-middleware em um ponto de montagem, com um caminho de montagem.
-Ele
-ilustra uma sub-pilha de middleware que imprime informações de
-solicitação para qualquer tipo de solicitação HTTP no caminho `/user/:id`.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Manipuladores de rota permitem a você definir várias rotas para
-um caminho. O exemplo abaixo define duas rotas para solicitações GET
-no caminho `/user/:id`. A segunda rota não irá
-causar nenhum problema, mas ela nunca será chamada pois a primeira
-rota termina o ciclo solicitação-resposta.
-
-Este exemplo mostra uma sub-pilha de middleware que manipula
-solicitações GET no caminho `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-`redirect`
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-Este exemplo mostra uma sub-pilha de middleware que manipula
-solicitações GET no caminho `/user/:id`.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-É possível ter mais do que um diretório estático por aplicativo:
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>Middleware de nível de roteador</h2>
-
-Middlewares de nível de roteador funcionam da mesma forma que
-os middlewares de nível do aplicativo, mas estão vinculados a uma
-instância do `express.Router()`.
-
-```js
-const router = express.Router()
-```
-
-Carregue os middlewares de nível de roteador usando as funções `router.use()` e `router.METHOD()`.
-
-O seguinte código de exemplo replica o sistema de middleware
-que é mostrado acima para o middleware de nível do aplicativo, usando
-um middleware de nível de roteador:
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-Para obter mais detalhes sobre a função `serve-static` e suas opções, consulte: documentação do[serve-static](https://github.com/expressjs/serve-static).
-
-Este exemplo mostra uma sub-pilha de middleware que manipula
-solicitações GET no caminho `/user/:id`.
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Middleware de manipulação de erros</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Middlewares de manipulação de erros sempre levam *quatro* argumentos. Você deve fornecer quatro argumentos para identificá-lo como uma
-função de middleware de manipulação de erros. Mesmo se você não
-precisar usar o objeto `next`, você deve
-especificá-lo para manter a assinatura. Caso contrário, o objeto
-`next` será interpretado como um middleware comum e
-a manipulação de erros falhará.
-</div>
-
-Defina funções de middleware de manipulação de
-erros da mesma forma que outras funções de middleware, exceto que com
-quatro argumentos ao invés de três, especificamente com a assinatura
-`(err, req, res, next)`):
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Para obter detalhes sobre middleware de manipulação de erros,
-consulte [Manipulação de erros](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Middleware integrado</h2>
-
-Desde a versão 4.x, o Express não depende mais do [Connect](https://github.com/senchalabs/connect). Com
-exceção da `express.static`, todas as funções de
-middleware que eram previamente incluídas com o Express estão agora
-em módulos separados. Visualize  a lista
-de funções de middleware.
-
-Aqui está um exemplo de uso da função de middleware `express.static` com um objeto options elaborado:
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Middleware de Terceiros</h2>
-
-Use middlewares de terceiros para incluir funcionalidades aos aplicativos do Express
-
-Instale o módulo Node.js para a funcionalidade requerida, em seguida carregue-a no seu aplicativo no nível do aplicativo ou no nível de roteador.
-
-O exemplo a seguir ilustra a instalação e carregamento da
-função de middleware para análise sintática de cookies `cookie-parser`.
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-Para obter uma lista parcial de funções de middleware de
-terceiros que são comumente utilizadas com o Express, consulte:
-[Middleware de Terceiros](../resources/middleware.html).
diff --git a/pt-br/guide/using-template-engines.md b/pt-br/guide/using-template-engines.md
deleted file mode 100644
index 65e84a34f4..0000000000
--- a/pt-br/guide/using-template-engines.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-layout: page
-title: Usando mecanismos de modelo com o Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# Usando mecanismos de modelo com o Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, é o diretório onde os arquivos de
-  modelo estão localizados. Por exemplo: `app.set('views',
-  './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, o mecanismo de modelo a ser
-  usado. Por Exemplo: `app.set('view engine', 'pug')`
-
-Em seguida instale o pacote npm correspondente ao mecanismo de modelo:
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Mecanismos de modelo compatíveis com o Express como o Pug exportam
-uma função chamada `__express(filePath, options,
-callback)`, que é chamada pela função
-`res.render()` para renderizar o código de modelo.
-
-Alguns mecanismos de modelo não seguem esta convenção. A
-biblioteca [Consolidate.js](https://www.npmjs.org/package/consolidate)
-segue esta convenção mapeando todos os mecanismos de modelo populares
-do Node.js, e portanto funciona de forma harmoniosa com o Express.
-
-</div>
-
-Após o mecanismo de visualização estar configurado, você não
-precisa especificar o mecanismo ou carregar o módulo do mecanismo de
-modelo no seu aplicativo; o Express carrega o módulo internamente,
-como mostrado abaixo (para o exemplo acima).
-
-```js
-app.set('view engine', 'pug')
-```
-
-Crie um arquivo de modelo do Pug
-chamado `index.pug` no diretório
-`views`, com o seguinte conteúdo:
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Em seguida crie uma rota para renderizar o arquivo
-`index.pug`. Se a propriedade `view
-engine` não estiver configurada, é preciso especificar a
-extensão do arquivo `view`. Caso contrário, é
-possível omití-la.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-Ao fazer uma solicitação à página inicial, o arquivo `index.pug` será renderizado como HTML.
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/pt-br/guide/writing-middleware.md b/pt-br/guide/writing-middleware.md
deleted file mode 100644
index 0d69935835..0000000000
--- a/pt-br/guide/writing-middleware.md
+++ /dev/null
@@ -1,248 +0,0 @@
----
-layout: page
-title: Escrevendo middlewares para uso em aplicativos do Express
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# Escrevendo middlewares para uso em aplicativos do Express
-
-<h2>Visão Geral</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. A próxima função middleware é
-comumente denotada por uma variável chamada `next`.
-
-Funções de middleware podem executar as seguintes tarefas:
-
-- Executar qualquer código.
-- Fazer mudanças nos objetos de solicitação e resposta.
-- Encerrar o ciclo de solicitação-resposta.
-- Chamar o próximo middleware na pilha.
-
-Se a atual função de middleware não terminar o ciclo de
-solicitação-resposta, ela precisa chamar `next()`
-para passar o controle para a próxima função de middleware. Caso
-contrário, a solicitação ficará suspensa.
-
-O exemplo a seguir mostra os elementos de uma chamada de função de middleware:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">O método HTTP para o qual a função de middleware é aplicada.</div></tbody>
-
-<div class="callout" id="callout2">Caminho (rota) para o qual a função de middleware é aplicada.</div>
-
-<div class="callout" id="callout3">A função de middleware.</div>
-
-<div class="callout" id="callout4">Argumento de retorno de chamada para a função de middleware, chamado de "next" por convenção.</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>Exemplo</h2>
-
-Aqui está um exemplo de um simples aplicativo "Hello World" do
-Express, para o qual serão definidas duas funções de middleware:
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Aqui está um exemplo simples de uma função de middleware chamada "myLogger". Esta
-função apenas imprime "LOGGED" quando uma solicitação para o aplicativo passa por ela. A
-função de middleware é designada para uma variável chamada `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Observe a chamada acima para `next()`. A chamada
-desta função chama a próxima função de middleware no aplicativo.
-A função `next()` não faz parte do Node.js
-ou da API Express, mas é o terceiro argumento que é passado para a
-função de middleware. A função `next()` poderia ter
-qualquer nome, mas por convenção ela é sempre chamada de "next".
-Para
-evitar confusão, sempre use esta convenção.
-</div>
-
-Para carregar a função de middleware, chame `app.use()`, especificando a função de middleware.
-Por exemplo, o código a seguir carrega a função de middleware do `myLogger` antes da rota para o caminho raiz (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-Sempre que o aplicativo recebe uma chamada, ele imprime a mensagem "LOGGED" no terminal.
-
-A ordem de carregamento do middleware é importante: funções de middleware que são carregadas primeiro também são executadas primeiro.
-
-Se `myLogger` é carregada após a rota para o
-caminho raiz, a chamada nunca chegará a ela e o aplicativo não
-imprimirá "LOGGED", pois o manipulador de rota do caminho raiz
-encerra o ciclo de solicitação-resposta.
-
-A função de middleware `myLogger` simplesmente imprime uma mensagem, e em seguida passa a solicitação para a próxima
-função de middleware na pilha chamando a função `next()`.
-
-<h3>Middleware function requestTime</h3>
-
-O próximo exemplo inclui uma propriedade chamada
-`requestTime` ao objeto da solicitação. Iremos
-chamar esta função de middleware de "requestTime".
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-O aplicativo agora usa a função de middleware `requestTime`. Além
-disso, a função de retorno de chamada do caminho raiz usa a
-propriedade que a função de middleware inclui no
-`req` (o objeto da solicitação).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-Ao fazer uma solicitação para a raiz do aplicativo, o
-aplicativo agora exibe o registro de data e hora da sua solicitação
-no navegador.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Como você tem acesso ao objeto da solicitação, ao objeto de
-resposta, à próxima função de middleware na pilha, e à API completa do
-Node.js, as possibilidades com as funções de middleware são ilimitadas.
-
-Para obter mais informações sobre middlewares no Express,
-consulte: [Usando
-middlewares no Express](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/pt-br/index.md b/pt-br/index.md
deleted file mode 100644
index 720fada107..0000000000
--- a/pt-br/index.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-layout: home
-title: Express - Node.js framework para aplicações web
-description: "Express é  rápido, sem opinião e minimalista para Node.js, fornecendo um conjunto robusto de recursos para aplicativos web e móveis."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Uma estrutura web rápida, flexível e minimalista para aplicativos Node.js</h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Aplicações Web</h2> Express é um framework para aplicativos web Node.js, mínimo e flexível que fornece um conjunto robusto de recursos para aplicativos web e móveis.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2>Com uma infinidade de métodos utilitários HTTP e middleware à sua disposição, criar uma API robusta é rápido e fácil.</div>
-    <div id="performance">
-      <h2>Desempenho</h2> Express fornece uma fina camada de recursos fundamentais de aplicativos web, sem obscurecer recursos de Node.js que você conhece e ama.
-    </div>
-    <div id="middleware">
-      <h2>Middleware</h2> 
-      Express é uma framework de roteamento leve e flexível com recursos centrais mínimos 
-      destinados a ser aumentada através do uso de módulos Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> . 
-    </div>
-  </div>
-</section>
diff --git a/pt-br/resources/community.md b/pt-br/resources/community.md
deleted file mode 100644
index 568e5cf131..0000000000
--- a/pt-br/resources/community.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-layout: page
-title: Comunidade do Express
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# Comunidade
-
-## Comitê técnico
-
-O comitê técnico do Express se reúne on-line a cada duas semanas (conforme necessário) para discutir o desenvolvimento e a manutenção do Express,
-e outras questões relevantes para o projeto Express. Cada reunião é normalmente anunciada em um
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) com um link para participar ou visualizar a reunião, que é
-aberto a todos os observadores.
-
-As reuniões são gravadas; para obter uma lista das gravações, consulte o [ canal no YouTube do Express.js](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Os membros do comitê técnico do Express são:
-
-**Ativo:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inativo:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express é feito de vários módulos
-
-Nossa vibrante comunidade criou uma grande variedade de extensões,
-[middleware módulos](/{{ page.lang }}/resources/middleware.html) e frameworks de alto nível.
-
-Além disso, a comunidade Express mantém módulos nestes duas organizações no GitHub:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-Para acompanhar o que está acontecendo em toda a comunidade, Confira a [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## Questões
-
-Se você se deparou com o que acha que é um bug ou apenas deseja fazer
-uma solicitação de recurso abre um ticket no [issue queue](https://github.com/expressjs/express/issues).
-
-## Exemplos
-
-Veja dezenas de aplicativos Express [exemplos](https://github.com/expressjs/express/tree/master/examples)
-no repositório temos de tudo, desde design de API e autenticação até integração de mecanismo de template.
-
-## Discussões no GitHub
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Marca do Expres.js
-
-## Logo Express.js
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotipo</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomarca</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/pt-br/resources/contributing.md b/pt-br/resources/contributing.md
deleted file mode 100644
index 90b6e8f8e1..0000000000
--- a/pt-br/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Comitê técnico
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/pt-br/resources/glossary.md b/pt-br/resources/glossary.md
deleted file mode 100644
index 3648c103ba..0000000000
--- a/pt-br/resources/glossary.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: page
-title: Glossário do Express
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# Glossário
-
-### aplicativo
-
-Em geral, um ou mais programas que são designados a executar
-operações com um propósito específico.  No contexto do Express, um
-programa que usa a API do Express executando na plataforma.  Pode
-também se referir a um [objeto app](/{{ page.lang }}/api.html#express).
-
-### API
-
-Interface de programação de aplicativos. Especifique o significado da abreviação no seu primeiro uso.
-
-### Express
-
-Uma estrutura web rápida, flexível e minimalista para aplicativos Node.js. Em
-geral, "Express" é preferido a "Express.js," apesar de que o último ser aceitável.
-
-### libuv
-
-Uma biblioteca de suporte multiplataforma que foca em E/S
-assíncrona, primeiramente desenvolvida para uso pelo Node.js.
-
-### middleware
-
-Uma função que é chamada pela camada de roteamento do Express
-antes do manipulador final da solicitação, e assim ficando no meio,
-entre uma solicitação bruta a rota final desejada. Alguns poucos
-pontos de refinamento da terminologia envolvendo middleware:
-
-- `var foo = require('middleware')` é
-  chamado _requerendo_ ou _usando_ um módulo
-  do Node.js. Então a instrução `var mw = foo()`
-  tipicamente retorna o middleware.
-- `app.use(mw)` é chamado _incluindo
-  o middleware na pilha global de processamento_.
-- `app.get('/foo', mw, function (req, res) { ... })`
-  é chamado \*incluindo o  middleware para a pilha de
-  processamento do "GET /foo" \*.
-
-### Node.js
-
-Uma plataforma de software que é usada para construir aplicativos de rede escaláveis. O Node.js usa o JavaScript como
-linguagem de script, e alcança rendimentos altos através de E/S não
-bloqueante e um loop de eventos de thread única. Consulte [nodejs.org](http://nodejs.org/). **Nota
-de uso**: Inicialmente, "Node.js," posteriormente "Node".
-
-### código aberto, código aberto
-
-Quando usado como adjetivo, colocar o hífen; por exemplo "Este
-é um software open-source". Consulte
-Software
-Open-source na Wikipedia.
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### solicitação
-
-Uma solicitação HTTP. Um cliente envia uma mensagem HTTP para
-um servidor, que retorna uma resposta.  A solicitação deve usar um dos
-vários
-métodos
-de solicitação como GET, POST, e assim por diante.
-
-### resposta
-
-Uma resposta HTTP. Um servidor retorna uma mensagem de resposta
-HTTP para o cliente. A resposta contém informações do status de
-conclusão sobre a solicitação e pode também conter conteúdo da
-solicitação no corpo da mensagem.
-
-### rota
-
-Parte de uma URL que identifica um recurso. Por exemplo, em
-`http://foo.com/products/id`, "/products/id" é a
-rota.
-
-### roteador
-
-Consulte [roteador](/{{ page.lang }}/4x/api.html#router) na referência da API.
diff --git a/pt-br/resources/middleware.md b/pt-br/resources/middleware.md
deleted file mode 100644
index 115c46942b..0000000000
--- a/pt-br/resources/middleware.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-layout: middleware
-title: Middleware do Express
-description: Explore uma lista de módulos de middleware Express.js mantidos pela equipe Express e pela comunidade, incluindo módulos de intermediários e de terceiros populares.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Middleware do Express
-
-Aqui estão alguns módulos middleware do Express:
-
-| Módulo de Middleware                                                        | Descrição                                                                                                                                     |
-| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Analisar corpo da requisição HTTP.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Comprimir respostas HTTP.                                                                                                     |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Gerar ID único de requisição.                                                                                                 |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Analisar cabeçalho de cookie e preencher `req.cookies`. Ver também [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Estabelecer sessões baseadas em cookies.                                                                                      |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Ativa o compartilhamento de recursos entre origens (CORS) com várias opções.                               |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Processamento/depuração do desenvolvimento.                                                                                   |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Substituir métodos HTTP utilizando header.                                                                                    |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | Log de requisições HTTP.                                                                                                      |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Manipule dados de formulários multi-part.                                                                                     |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                                    |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Sirva um favicon.                                                                                                             |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                                     |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Servir arquivos estáticos.                                                                                                    |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                                        |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                                   |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Criar domínios virtuais.                                                                                                      |
-
-## Para obter mais módulos middleware, consulte:
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Módulo de Middleware                                | Descrição                                                                                                                                                                                             |
-| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [st](https://github.com/isaacs/st)                  | [helmet](https://github.com/helmetjs/helmet): módulo para ajudar a proteger seus aplicativos configurando vários cabeçalhos HTTP.                                     |
-| [passport](https://github.com/jaredhanson/passport) | Authentication using "strategies" such as OAuth, OpenID and many others.  Veja [passportjs.org](https://passportjs.org/) para obter mais informações. |
diff --git a/pt-br/resources/middleware/body-parser.md b/pt-br/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/pt-br/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/pt-br/resources/middleware/compression.md b/pt-br/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/pt-br/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/pt-br/resources/middleware/connect-rid.md b/pt-br/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/pt-br/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/pt-br/resources/middleware/cookie-parser.md b/pt-br/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/pt-br/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/pt-br/resources/middleware/cookie-session.md b/pt-br/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/pt-br/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/pt-br/resources/middleware/cors.md b/pt-br/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/pt-br/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/pt-br/resources/middleware/errorhandler.md b/pt-br/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/pt-br/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/pt-br/resources/middleware/method-override.md b/pt-br/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/pt-br/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/pt-br/resources/middleware/morgan.md b/pt-br/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/pt-br/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/pt-br/resources/middleware/multer.md b/pt-br/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/pt-br/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/pt-br/resources/middleware/response-time.md b/pt-br/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/pt-br/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/pt-br/resources/middleware/serve-favicon.md b/pt-br/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/pt-br/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/pt-br/resources/middleware/serve-index.md b/pt-br/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/pt-br/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/pt-br/resources/middleware/serve-static.md b/pt-br/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/pt-br/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/pt-br/resources/middleware/session.md b/pt-br/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/pt-br/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/pt-br/resources/middleware/timeout.md b/pt-br/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/pt-br/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/pt-br/resources/middleware/vhost.md b/pt-br/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/pt-br/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/pt-br/resources/utils.md b/pt-br/resources/utils.md
deleted file mode 100644
index de7799f8d6..0000000000
--- a/pt-br/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilidades
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express funções utilitárias
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Módulos utilitários                                            | Descrição                                                                                                                                                                                                                  |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/pt-br/starter/basic-routing.md b/pt-br/starter/basic-routing.md
deleted file mode 100644
index d464fdd3eb..0000000000
--- a/pt-br/starter/basic-routing.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-layout: page
-title: Roteamento básico no Express
-description: Aprenda os fundamentos do roteamento em aplicações Express.js, incluindo como definir rotas, lidar com métodos HTTP e criar manipuladores de rotas para seu servidor web.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# Roteamento Básico
-
-O _Roteamento_ refere-se à determinação de como um
-aplicativo responde a uma solicitação do cliente por um endpoint
-específico, que é uma URI (ou caminho) e um método de solicitação HTTP
-específico (GET, POST, e assim por diante).
-
-Cada rota pode ter uma ou mais funções de manipulação, que são
-executadas quando a rota é correspondida.
-
-A definição de rotas aceita a seguinte estrutura:
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Onde:
-
-- `app` é uma instância do `express`.
-- `METHOD` é um [método de solicitação HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), em minúsculas.
-- `PATH` é um caminho no servidor.
-- `HANDLER` é a função executada quando a rota é correspondida.
-
-<div class="doc-box doc-notice" markdown="1">
-Este tutorial assume que uma instância de `express`
-chamada `app` está criada e o servidor está em
-execução. Caso não tenha familiaridade com a criação e inicialização
-de um aplicativo, consulte o [exemplo Hello world](/{{ page.lang }}/starter/hello-world.html).
-</div>
-
-Os seguintes exemplos ilustram a definição de rotas simples.
-
-Responda com `Hello World!` na página inicial:
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Responder a uma solicitação POST na rota raiz (`/`) com a página inicial do aplicativo:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-Responder a uma solicitação PUT para a rota `/user`:
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-Responder a uma solicitação DELETE para a rota `/user`:
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-Para obter mais detalhes sobre roteamento, consulte o [guia de roteamento](/{{ page.lang }}/guide/routing.html).
-
diff --git a/pt-br/starter/examples.md b/pt-br/starter/examples.md
deleted file mode 100644
index 8f180fd8f7..0000000000
--- a/pt-br/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Exemplos do Express
-description: Explore uma coleção de exemplos de aplicações em Express.js cobrindo diversos casos de uso, integrações e configurações avançadas para te ajudar a aprender e construir seus projetos.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Exemplos adicionais
-
-Estes são alguns exemplos adicionais com integrações mais extensas.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Aplicativo Fullstack com Express e Next.js utilizando [Prisma](https://www.npmjs.com/package/prisma) como ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - API REST com Express em TypeScript utilizando [Prisma](https://www.npmjs.com/package/prisma) como ORM
\ No newline at end of file
diff --git a/pt-br/starter/faq.md b/pt-br/starter/faq.md
deleted file mode 100644
index 41f8017989..0000000000
--- a/pt-br/starter/faq.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-layout: page
-title: Pergunta mais Frequentes do Express
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# Perguntas mais frequentes
-
-## Como eu devo estruturar meu aplicativo?
-
-Não existe uma resposta definitiva para esta questão. A
-resposta depende da escala do seu aplicativo e o time que está
-envolvido. Para ser o mais flexível possível, o Express não faz
-suposições em termos de estrutura.
-
-Rotas e outras lógicas específicas do aplicativo podem ficar em
-quantos arquivos quiser, em qualquer estrutura de diretórios que
-preferir. Visualize os seguintes exemplos para obter inspiração:
-
-- [Listagens de rota](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [Mapa de rota](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [Controladores com estilo MVC](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-Além disso, existem extensões de terceiros para o Express, que
-simplificam alguns desses padrões:
-
-- [Roteamento de recursos](https://github.com/expressjs/express-resource)
-
-## Como eu defino modelos?
-
-O Express não tem noção de banco de dados. Este conceito é
-deixado para módulos do Node de terceiros, permitindo que você faça
-a interface com praticamente qualquer banco de dados.
-
-Consulte [LoopBack](http://loopback.io) para
-uma estrutura baseada no Express que é centrada em modelos.
-
-## Como posso autenticar usuários?
-
-Autenticação é outra área muito opinada que o Express não
-se arrisca a entrar. Você pode usar qualquer esquema que desejar.
-Para um esquema simples com nome de usuário / senha, consulte
-este
-exemplo.
-
-## Quais mecanismos de modelo o Express suporta?
-
-O Express suporta qualquer mecanismo de modelo que esteja em
-conformidade com a assinatura `(path, locals,
-callback)`.
-Para normalizar interfaces e o armazenamento em
-cache de mecanismo de modelo, consulte o projeto
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-para obter suporte. Mecanismos de modelo não listados podem ainda
-assim suportar a assinatura do Express.
-
-[Roteamento engenhoso](https://github.com/expressjs/express-resource)
-
-## Como manipulo respostas 404?
-
-No Express, respostas 404 não são o resultado de um erro,
-portanto o middleware manipulador de erros não irá capturá-las. Este comportamento é porque uma resposta 404 simplesmente indicam a
-ausência de trabalho adicional para fazer; em outras palavras, o
-Express executou todas as funções de middleware e rotas, e descobriu
-que nenhuma delas respondeu. Tudo que você precisa fazer é incluir
-uma função de middleware no final da pilha (abaixo de todas as outras
-funções) para manipular uma resposta 404:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## Como configuro um manipulador de erros?
-
-Você define middlewares de manipulação de erros da mesma forma
-que outros middlewares, exceto que com quatro argumentos ao invés de
-três; especificamente com a assinatura `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-Para obter mais informações, consulte [Manipulação de erros](/{{ page.lang }}/guide/error-handling.html).
-
-## Como renderizar um HTML simples?
-
-Você não faz! Não há necessidade de se "renderizar" HTML com a
-função `res.render()`.
-se você tiver um arquivo
-específico, use a função `res.sendFile()`.
-Se estiver entregando muitos ativos a partir de um diretório, use a
-função de middleware `express.static()`.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requer Node.js 0.10 ou superior.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requer Node.js 18 ou superior.
\ No newline at end of file
diff --git a/pt-br/starter/generator.md b/pt-br/starter/generator.md
deleted file mode 100644
index 48aca7f32e..0000000000
--- a/pt-br/starter/generator.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-layout: page
-title: Gerador de aplicativos do Express
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Gerador de aplicativos do Express
-
-Use a ferramenta geradora de aplicativos, `express`,
-para rapidamente criar uma estrutura básica de aplicativo.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-Exiba as opções de comando com a opção `-h`:
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-Por exemplo, o seguinte cria um aplicativo do Express chamado _myapp_
-no diretório atualmente em funcionamento: The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-Em seguida instale as dependências:
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-No MacOS ou Linux, execute o aplicativo com este comando:
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-No Windows, use este comando:
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-Instale o `express` com o comando a seguir:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-Em seguida carregue `http://localhost:3000/` no seu navegador para acessar o aplicativo.
-
-O aplicativo gerado possui a seguinte estrutura de diretórios:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-A estrutura de aplicativo criada pelo gerador é apenas uma das várias maneiras de estruturar aplicativos do Express. É possível utilizar esta estrutura ou modificá-la para melhor se adequar às suas necessidades.
-</div>
\ No newline at end of file
diff --git a/pt-br/starter/hello-world.md b/pt-br/starter/hello-world.md
deleted file mode 100644
index f8a569748f..0000000000
--- a/pt-br/starter/hello-world.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: page
-title: Exemplo "Hello World" do Express
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Exemplo Hello World
-
-<div class="doc-box doc-info" markdown="1">
-Este é essencialmente o aplicativo mais simples do Express que é possível criar. Ele
-é um aplicativo de arquivo único &mdash; *não* é o que você iria obter usando o [Gerador Express](/{{ page.lang }}/starter/generator.html),
-que cria a estrutura para um aplicativo completo com inúmeros arquivos JavaScript, modelos Jade, e subdiretórios para vários
-propósitos.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-O aplicativo inicia um servidor e escuta a porta 3000 por
-conexões. O aplicativo responde com "Hello World!" à solicitações
-para a URL raiz (`/`) ou _rota_. Para
-todos os outros caminhos, ele irá responder com um **404 Não Encontrado**.
-
-### Executando localmente
-
-Primeiro crie um diretório chamado `myapp`,
-mude para ele e execute o `npm init`. Em seguida
-instale o `express` como uma dependência, de acordo com o [guia de instalação](/{{ page.lang }}/starter/installing.html).
-
-No diretório `myapp`, crie um arquivo chamado `app.js` e inclua o seguinte código:
-
-<div class="doc-box doc-notice" markdown="1">
-O `req` (solicitação) e `res`
-(resposta) são os mesmos objetos que o Node fornece, para que seja
-possível chamar o `req.pipe()`,
-`req.on('data', callback)`, e qualquer outra coisa
-que desejaria fazer sem o envolvimento do Express.
-</div>
-
-Execute o aplicativo com o seguinte comando:
-
-```bash
-$ node app.js
-```
-
-Em seguida, carregue [http://localhost:3000/](http://localhost:3000/) em
-um navegador para visualizar a saída
\ No newline at end of file
diff --git a/pt-br/starter/installing.md b/pt-br/starter/installing.md
deleted file mode 100644
index 402851e089..0000000000
--- a/pt-br/starter/installing.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: page
-title: Instalando o Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# Instalação
-
-Assumindo que já tenha instalado o [Node.js](https://nodejs.org/), crie um diretório
-para conter o seu aplicativo, e torne-o seu diretório ativo.
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requer Node.js 0.10 ou superior.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requer Node.js 18 ou superior.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Use o comando `npm init` para criar um arquivo `package.json` para o seu aplicativo.
-Para obter mais informações sobre como o `package.json` funciona,
-consulte [Detalhes do tratamento de package.json do npm](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-Este comando solicita por várias coisas, como o nome e versão do seu aplicativo.
-Por enquanto, é possível simplesmente pressionar RETURN para aceitar
-os padrões para a maioria deles, com as seguintes exceções:
-
-```
-entry point: (index.js)
-```
-
-Insira `app.js`, ou qualquer nome que deseje
-para o arquivo principal. Se desejar que seja `index.js`, pressione RETURN para aceitar o nome de
-arquivo padrão sugerido.
-
-Agora instale o Express no diretório `myapp`
-e salve-o na lista de dependências. Por exemplo:
-
-```bash
-$ npm install express
-```
-
-Para instalar o Express temporariamente não o inclua na lista
-de dependências, omita a opção `--save`:
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-Módulos do Node instalados com a opção `--save`
-são incluídas na lista `dependencies` no arquivo
-`package.json`. Posteriormente, executando `npm install` no diretório
-`app` irá automaticamente instalar os módulos na
-lista de dependências.
-</div>
\ No newline at end of file
diff --git a/pt-br/starter/static-files.md b/pt-br/starter/static-files.md
deleted file mode 100644
index a9d80ce50c..0000000000
--- a/pt-br/starter/static-files.md
+++ /dev/null
@@ -1,94 +0,0 @@
----
-layout: page
-title: Entregando arquivos estáticos no Express
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# Entregando arquivos estáticos no Express
-
-Para entregar arquivos estáticos como imagens, arquivos CSS, e
-arquivos JavaScript, use a função de middleware `express.static`
-integrada no Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-Por exemplo, use o código a seguir
-para entregar imagens, arquivos CSS, e arquivos JavaScript em um
-diretório chamado `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-Agora, é possível carregar os arquivos que estão no diretório `public`:
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-O Express consulta os arquivos em relação ao diretório estático, para
-que o nome do diretório estático não faça parte da URL.
-</div>
-
-Para usar vários diretórios de ativos estáticos, chame a função
-de middleware `express.static` várias vezes:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-O Express consulta os arquivos na ordem em que você configurar
-os diretórios estáticos com a função de middleware
-`express.static`.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-Agora, é possível carregar os arquivos que estão no diretório
-`public` a partir do prefixo do caminho `/static`.
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-Entretanto, o caminho fornecido para a função
-`express.static` é relativa ao diretório a partir do
-qual você inicia o seu `node` de processo. Se você
-executar o aplicativo express a partir de outro diretório, é mais
-seguro utilizar o caminho absoluto do diretório para o qual deseja
-entregar.
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/pt-br/support/index.md b/pt-br/support/index.md
deleted file mode 100644
index 8179fe2991..0000000000
--- a/pt-br/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Suporte à Versão
-description: Encontre informações sobre o cronograma de suporte para diferentes versões do Express.js, incluindo quais versões são atualmente mantidas e antigas políticas.
-menu: support
----
-
-# Suporte à Versão
-
-Somente a última versão de qualquer linha de lançamento é suportada.
-
-Versões que são EOL (fim de vida) podem receber atualizações de vulnerabilidades de segurança críticas, mas a equipe Express não oferece garantia e não planeja endereçar ou liberar correções para quaisquer problemas encontrados.
-
-| Versão Principal                                                                                                                                           | Versão mínima do Node.js | Início Suporte   | Término Suporte                                            |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ---------------- | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                       | Setembro de 2024 | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0   | Abril de 2014    | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0    | Outubro de 2012  | Julho de 2015                                              |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1    | Março de 2011    | Julho de 2012                                              |
-| **v1.x**{: .eol }                                                                                          | 0.2.0    | Dezembro de 2010 | Março de 2011                                              |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98   | Dezembro de 2010 | Dezembro de 2010                                           |
-
-## Opções de Suporte Comercial
-
-Se você não puder atualizar para uma versão suportada do Express, entre em contato com um de nossos parceiros para receber atualizações de segurança:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/.well-known/security.txt b/public/.well-known/security.txt
similarity index 85%
rename from .well-known/security.txt
rename to public/.well-known/security.txt
index 85fcd7780a..55e7ad779d 100644
--- a/.well-known/security.txt
+++ b/public/.well-known/security.txt
@@ -3,4 +3,4 @@ Contact: mailto:express-security@lists.openjsf.org
 # Our security policy
 Policy: https://github.com/expressjs/express/security/policy
 # Expires this policy
-Expires: 2026-07-20T00:00:00Z
\ No newline at end of file
+Expires: 2026-07-20T00:00:00Z
diff --git a/public/apple-touch-icon.png b/public/apple-touch-icon.png
new file mode 100644
index 0000000000..1246e42e69
Binary files /dev/null and b/public/apple-touch-icon.png differ
diff --git a/public/favicon.ico b/public/favicon.ico
new file mode 100644
index 0000000000..45865d9e17
Binary files /dev/null and b/public/favicon.ico differ
diff --git a/public/favicon.svg b/public/favicon.svg
new file mode 100644
index 0000000000..a026d6f3ed
--- /dev/null
+++ b/public/favicon.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" width="1000" height="1000"><g clip-path="url(#SvgjsClipPath1335)"><rect width="1000" height="1000" fill="#1a1a1a"></rect><g transform="matrix(27.77777777777778,0,0,27.77777777777778,0,0)"><svg xmlns="http://www.w3.org/2000/svg" version="1.1" xmlns:xlink="http://www.w3.org/1999/xlink" width="36" height="36"><svg xmlns="http://www.w3.org/2000/svg" width="36" height="36" fill="none"><g fill="#fff" clip-path="url(#a)"><path d="M18.306 23.444h1.336l8.138-10.879h-1.356l-8.118 10.879Z"></path><path d="M29.713 25.125v.004l-5.056-6.657-.65.863 5.685 7.796H5.102V8.869h11.09l5.863 7.816.67-.901-5.103-6.915h.003l-.838-1.103H4v20.468h28l-2.287-3.109ZM9.41 17.245v-.009.009Z"></path><path d="M16.737 14.156a4.445 4.445 0 0 0-1.508-1.38c-.619-.351-1.365-.526-2.235-.526-.87 0-1.598.165-2.224.495a4.386 4.386 0 0 0-1.528 1.307 5.704 5.704 0 0 0-.876 1.845 7.92 7.92 0 0 0-.284 2.109c0 .773.095 1.508.284 2.203a5.4 5.4 0 0 0 .876 1.835 4.07 4.07 0 0 0 1.528 1.243c.626.303 1.366.454 2.224.454 1.377 0 2.442-.337 3.195-1.012.751-.674 1.269-1.631 1.55-2.867H16.41c-.211.843-.592 1.517-1.14 2.023-.547.507-1.306.759-2.277.759-.633 0-1.173-.133-1.624-.4a3.655 3.655 0 0 1-1.117-1.013 4.08 4.08 0 0 1-.643-1.38 6 6 0 0 1-.198-1.321 10.323 10.323 0 0 0-.017-.334 5.24 5.24 0 0 1 .017-.967 5.92 5.92 0 0 1 .345-1.427c.175-.47.411-.885.707-1.244a3.402 3.402 0 0 1 1.076-.865c.421-.218.906-.326 1.454-.326.548 0 1.013.108 1.434.326.422.218.78.507 1.076.865.296.359.523.77.685 1.233.162.463.249.95.263 1.454h-5.889l.005 1.117h7.212a8.542 8.542 0 0 0-.21-2.245 5.765 5.765 0 0 0-.833-1.96Zm-7.324 3.073v.007-.007Z"></path></g><defs><clipPath id="a"><path fill="#fff" d="M4 7.766h28v20.468H4z"></path></clipPath><clipPath id="SvgjsClipPath1335"><rect width="1000" height="1000" x="0" y="0" rx="0" ry="0"></rect></clipPath></defs></svg></svg></g></g></svg>
\ No newline at end of file
diff --git a/public/fonts/JetBrainsMono-Light.woff2 b/public/fonts/JetBrainsMono-Light.woff2
new file mode 100644
index 0000000000..6538498736
Binary files /dev/null and b/public/fonts/JetBrainsMono-Light.woff2 differ
diff --git a/public/fonts/JetBrainsMono-LightItalic.woff2 b/public/fonts/JetBrainsMono-LightItalic.woff2
new file mode 100644
index 0000000000..66ca3d2b99
Binary files /dev/null and b/public/fonts/JetBrainsMono-LightItalic.woff2 differ
diff --git a/public/fonts/inter-bold.woff b/public/fonts/inter-bold.woff
new file mode 100644
index 0000000000..161b01e821
Binary files /dev/null and b/public/fonts/inter-bold.woff differ
diff --git a/public/hero-poster-light.webp b/public/hero-poster-light.webp
new file mode 100644
index 0000000000..87fba410ec
Binary files /dev/null and b/public/hero-poster-light.webp differ
diff --git a/public/hero-poster.webp b/public/hero-poster.webp
new file mode 100644
index 0000000000..a83205db68
Binary files /dev/null and b/public/hero-poster.webp differ
diff --git a/images/clustering.png b/public/images/clustering.png
similarity index 100%
rename from images/clustering.png
rename to public/images/clustering.png
diff --git a/public/images/express-mw.png b/public/images/express-mw.png
new file mode 100644
index 0000000000..d7e78f3157
Binary files /dev/null and b/public/images/express-mw.png differ
diff --git a/public/images/logos/express-kawaii.webp b/public/images/logos/express-kawaii.webp
new file mode 100644
index 0000000000..116d5663cc
Binary files /dev/null and b/public/images/logos/express-kawaii.webp differ
diff --git a/public/images/logos/logo-dark.svg b/public/images/logos/logo-dark.svg
new file mode 100644
index 0000000000..8a60d60a79
--- /dev/null
+++ b/public/images/logos/logo-dark.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="353" height="258" fill="none" viewBox="0 0 353 258"><g fill="#fff" clip-path="url(#a)"><path d="M180.477 197.464h20.699l102.5-137.0211h-20.972z"/><path d="M323.863 218.64v.045l-59.307-79.008-10.918 14.231 65.413 89.993H13.8905V13.8905H149.028l74.355 98.8675 10.849-14.1398-62.666-84.7277h.046L161.058 0H0v257.792h352.665z"/><path d="M160.424 80.4821c-4.88-7.1722-11.19-12.9599-18.998-17.3858-7.785-4.4259-17.181-6.6275-28.144-6.6275s-20.1322 2.0881-28.008 6.2416-14.2991 9.6462-19.247 16.4553-8.6249 14.5714-11.0307 23.2413c-2.3832 8.671-3.5861 17.522-3.5861 26.556 0 9.737 1.2029 18.997 3.5861 27.758s6.0601 16.455 11.0307 23.106c4.9479 6.65 11.3712 11.87 19.247 15.661 7.8758 3.813 17.204 5.719 28.008 5.719 17.34 0 30.754-4.244 40.242-12.756 9.464-8.488 15.978-20.54 19.519-36.11h-16.728c-2.655 10.622-7.444 19.11-14.344 25.488s-16.455 9.556-28.689 9.556c-7.967 0-14.7757-1.68-20.4499-5.039-5.6743-3.359-10.3498-7.603-14.0721-12.756-3.7223-5.129-6.4233-10.94-8.1028-17.386-1.498-5.719-2.3151-11.257-2.4967-16.636-.0454-1.408-.1135-2.792-.2043-4.199-.295-4.154-.2496-8.217.2043-12.189q1.0554-9.192 4.3578-17.976c2.2016-5.9235 5.1749-11.1438 8.8972-15.6605q5.58345-6.77505 13.5501-10.8945c5.3114-2.7463 11.4164-4.1081 18.3164-4.1081s12.756 1.3618 18.067 4.1081 9.828 6.3778 13.55 10.8945 6.582 9.6916 8.625 15.5245c2.042 5.833 3.132 11.962 3.313 18.317H82.6638l.0681 14.072h90.8331c.363-9.556-.522-18.998-2.655-28.281-2.134-9.2827-5.629-17.5217-10.486-24.6939"/></g><defs><clipPath id="a"><path fill="#fff" d="M0 0h352.665v257.792H0z"/></clipPath></defs></svg>
diff --git a/public/images/logos/logo-express-black.svg b/public/images/logos/logo-express-black.svg
new file mode 100644
index 0000000000..268c1b5495
--- /dev/null
+++ b/public/images/logos/logo-express-black.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="599" height="159" fill="none" viewBox="0 0 599 159"><g fill="#000" clip-path="url(#a)"><path d="M110.82 121.236h12.709l62.932-84.1271h-12.876z"/><path d="M198.851 134.239v.028l-36.413-48.5091-6.703 8.7374 40.161 55.2537H8.53622V8.52841H91.5071L137.159 69.2306l6.661-8.6817-38.475-52.02049h.028L98.8928 0H.00781v158.277H216.535zm39.778-10.716c6.41 0 11.984-1.171 16.708-3.512 4.725-2.341 8.668-5.546 11.818-9.615 3.149-4.069 5.49-8.807 7.009-14.1865 1.519-5.379 2.286-11.0646 2.286-17.0429 0-5.9782-.767-11.6638-2.286-17.0429-1.519-5.379-3.86-10.1031-7.009-14.1861-3.15-4.0691-7.093-7.3021-11.818-9.699-4.724-2.3829-10.298-3.5814-16.708-3.5814-6.842 0-12.96 1.6026-18.339 4.8077s-9.267 7.748-11.664 13.6148h-.32V37.0959h-9.462v76.9091l10.27 13.963V105.24h.321c1.087 3.037 2.633 5.713 4.64 7.985 2.007 2.285 4.32 4.18 6.926 5.713 2.606 1.519 5.435 2.662 8.473 3.428 3.037.753 6.089 1.143 9.127 1.143zm-22.91-19.886c-2.341-3.372-4.027-7.2045-5.058-11.4966s-1.547-8.612-1.547-12.9599c0-4.7798.46-9.3505 1.38-13.6984.919-4.3478 2.522-8.1521 4.807-11.413 2.286-3.2608 5.324-5.8668 9.128-7.8316 3.804-1.951 8.528-2.9404 14.186-2.9404 4.891 0 9.072 1.0591 12.556 3.1773 3.484 2.1181 6.326 4.8634 8.556 8.2357 2.23 3.3724 3.86 7.2046 4.891 11.4967 1.032 4.292 1.547 8.612 1.547 12.9598s-.515 8.6678-1.547 12.9598c-1.031 4.2921-2.661 8.1246-4.891 11.4966s-5.086 6.118-8.556 8.236c-3.484 2.118-7.665 3.177-12.556 3.177-5.435 0-10.033-1.059-13.782-3.177s-6.8-4.864-9.128-8.236z"/><path d="m113.754 0 6.48 8.52841h470.219V149.749H225.125l6.271 8.528h367.585V0zM98.4977 49.414c-2.9961-4.4036-6.8701-7.9571-11.6638-10.6745-4.7799-2.7174-10.5491-4.0691-17.2798-4.0691-6.7308 0-12.3607 1.2821-17.1962 3.8322-4.8356 2.5502-8.7793 5.9225-11.8172 10.1031-3.0378 4.1806-5.2954 8.9465-6.7725 14.2698-1.4632 5.3233-2.2018 10.758-2.2018 16.3043 0 5.9782.7386 11.6639 2.2018 17.0429 1.4632 5.3793 3.7207 10.1033 6.7725 14.1863 3.0379 4.083 6.9816 7.288 11.8172 9.615 4.8355 2.341 10.563 3.512 17.1962 3.512 10.6465 0 18.8823-2.606 24.7073-7.832 5.8106-5.212 9.8106-12.611 11.9846-22.1708H95.9754c-1.6304 6.5218-4.5708 11.7338-8.8071 15.6498-4.2363 3.915-10.1031 5.866-17.6142 5.866-4.8913 0-9.0719-1.031-12.5557-3.093-3.4839-2.063-6.3545-4.669-8.6399-7.832-2.2854-3.149-3.9437-6.7168-4.9749-10.6744-.9198-3.5117-1.4214-6.912-1.5329-10.2146-.0279-.864-.0697-1.7141-.1254-2.5781-.1812-2.5501-.1533-5.0445.1254-7.4832.432-3.7626 1.3238-7.4415 2.6755-11.0368 1.3518-3.6371 3.1773-6.8422 5.4627-9.6154 2.2854-2.7731 5.0585-5.0027 8.3194-6.6889 3.2608-1.6862 7.0094-2.5223 11.2458-2.5223 4.2363 0 7.8316.8361 11.0925 2.5223 3.2608 1.6862 6.034 3.9158 8.3194 6.6889 2.2854 2.7732 4.0412 5.9504 5.2954 9.5318 1.2541 3.5814 1.923 7.3439 2.0345 11.2458H50.7553l.0418 8.6399h55.7689c.223-5.8668-.32-11.6639-1.63-17.3634-1.31-5.6996-3.456-10.7581-6.4383-15.1616"/><path d="M292.434 37.1093v84.1277h10.27V76.393c0-4.4593.752-8.5563 2.285-12.3049q2.2785-5.6229 6.438-9.699c2.774-2.7174 6.062-4.8077 9.867-6.2709 3.804-1.4632 8.04-2.0903 12.723-1.8813V35.9666c-7.609-.3205-14.159 1.3657-19.649 5.0585-5.491 3.6929-9.532 8.9604-12.152 15.8166h-.32V37.1093zm117.56 27.4663c-1.31-5.6996-3.456-10.7581-6.438-15.1616-2.996-4.4036-6.87-7.9571-11.664-10.6745-4.779-2.7174-10.549-4.0691-17.279-4.0691-6.731 0-12.361 1.2821-17.196 3.8322-4.836 2.5502-8.78 5.9225-11.818 10.1031s-5.295 8.9465-6.772 14.2698c-1.463 5.3233-2.202 10.758-2.202 16.3043 0 5.9782.739 11.6639 2.202 17.0429 1.463 5.3793 3.721 10.1033 6.772 14.1863 3.038 4.083 6.982 7.288 11.818 9.615 4.835 2.341 10.562 3.512 17.196 3.512 10.646 0 18.882-2.606 24.707-7.832 5.811-5.212 9.81-12.611 11.984-22.1708h-10.27c-1.63 6.5218-4.571 11.7338-8.807 15.6498-4.236 3.915-10.103 5.866-17.614 5.866-4.892 0-9.072-1.031-12.556-3.093-3.484-2.063-6.355-4.669-8.64-7.832-2.285-3.149-3.944-6.7168-4.975-10.6744-1.031-3.9716-1.547-7.8038-1.547-11.4967h64.73c.223-5.8667-.321-11.6638-1.631-17.3634zm-63.099 8.7235c.432-3.8043 1.324-7.5251 2.69-11.1622 1.352-3.6371 3.177-6.8422 5.462-9.6154 2.286-2.7731 5.059-5.0027 8.32-6.6889s7.009-2.5223 11.246-2.5223c4.236 0 7.831.8361 11.092 2.5223s6.034 3.9158 8.32 6.6889c2.285 2.7732 4.041 5.9504 5.295 9.5318s1.923 7.3439 2.035 11.2458zm124.076 38.1559c-2.286 1.31-4.752 2.23-7.414 2.773-2.662.544-5.24.808-7.748.808-6.842 0-12.584-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.119-9.6154-1.407-2.7173-3.233-5.0027-5.462-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.699-3.0936c-1.741-.432-3.637-1.0034-5.713-1.7141-2.062-.7107-3.972-1.6025-5.7-2.6895-1.741-1.0869-3.177-2.4108-4.319-3.9994-1.143-1.5747-1.715-3.5117-1.715-5.7832 0-2.7173.6-5.0027 1.798-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.341-.4877 4.641-.7386 6.926-.7386 2.94 0 5.714.3484 8.32 1.0591 2.605.7107 4.919 1.8256 6.925 3.3445 2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.853 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.616-5.0585-3.637-1.087-7.58-1.6304-11.817-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.187 4.083-3.037 1.8534-5.518 4.2921-7.413 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.152 4.2364c1.032 1.6861 1.547 3.7764 1.547 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975zm78.414 0c-2.286 1.31-4.752 2.23-7.414 2.773-2.661.544-5.24.808-7.748.808-6.842 0-12.583-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.118-9.6154-1.408-2.7173-3.233-5.0027-5.463-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.698-3.0936c-1.742-.432-3.638-1.0034-5.714-1.7141-2.062-.7107-3.971-1.6025-5.699-2.6895-1.742-1.0869-3.178-2.4108-4.32-3.9994-1.143-1.5747-1.714-3.5117-1.714-5.7832 0-2.7173.599-5.0027 1.797-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.342-.4877 4.641-.7386 6.926-.7386 2.941 0 5.714.3484 8.32 1.0591s4.919 1.8256 6.925 3.3445c2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.854 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.615-5.0585-3.638-1.087-7.581-1.6304-11.818-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.186 4.083-3.038 1.8534-5.519 4.2921-7.414 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.153 4.2364c1.031 1.6861 1.546 3.7764 1.546 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975z"/></g><defs><clipPath id="a"><path fill="#000" d="M0 0h598.982v158.277H0z"/></clipPath></defs></svg>
diff --git a/public/images/logos/logo-express-white.svg b/public/images/logos/logo-express-white.svg
new file mode 100644
index 0000000000..f35c4beccc
--- /dev/null
+++ b/public/images/logos/logo-express-white.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="599" height="159" fill="none" viewBox="0 0 599 159"><g fill="#fff" clip-path="url(#a)"><path d="M110.82 121.236h12.709l62.932-84.1271h-12.876z"/><path d="M198.851 134.239v.028l-36.413-48.5091-6.703 8.7374 40.161 55.2537H8.53622V8.52841H91.5071L137.159 69.2306l6.661-8.6817-38.475-52.02049h.028L98.8928 0H.00781v158.277H216.535zM238.629 123.523c6.41 0 11.984-1.171 16.708-3.512 4.725-2.341 8.668-5.546 11.818-9.615 3.149-4.069 5.49-8.807 7.009-14.1865 1.519-5.379 2.286-11.0646 2.286-17.0429 0-5.9782-.767-11.6638-2.286-17.0429-1.519-5.379-3.86-10.1031-7.009-14.1861-3.15-4.0691-7.093-7.3021-11.818-9.699-4.724-2.3829-10.298-3.5814-16.708-3.5814-6.842 0-12.96 1.6026-18.339 4.8077s-9.267 7.748-11.664 13.6148h-.32V37.0959h-9.462v76.9091l10.27 13.963V105.24h.321c1.087 3.037 2.633 5.713 4.64 7.985 2.007 2.285 4.32 4.18 6.926 5.713 2.606 1.519 5.435 2.662 8.473 3.428 3.037.753 6.089 1.143 9.127 1.143zm-22.91-19.886c-2.341-3.372-4.027-7.2045-5.058-11.4966s-1.547-8.612-1.547-12.9599c0-4.7798.46-9.3505 1.38-13.6984.919-4.3478 2.522-8.1521 4.807-11.413 2.286-3.2608 5.324-5.8668 9.128-7.8316 3.804-1.951 8.528-2.9404 14.186-2.9404 4.891 0 9.072 1.0591 12.556 3.1773 3.484 2.1181 6.326 4.8634 8.556 8.2357 2.23 3.3724 3.86 7.2046 4.891 11.4967 1.032 4.292 1.547 8.612 1.547 12.9598s-.515 8.6678-1.547 12.9598c-1.031 4.2921-2.661 8.1246-4.891 11.4966s-5.086 6.118-8.556 8.236c-3.484 2.118-7.665 3.177-12.556 3.177-5.435 0-10.033-1.059-13.782-3.177s-6.8-4.864-9.128-8.236z"/><path d="m113.754 0 6.48 8.52841h470.219V149.749H225.125l6.271 8.528h367.585V0zM98.4977 49.414c-2.9961-4.4036-6.8701-7.9571-11.6638-10.6745-4.7799-2.7174-10.5491-4.0691-17.2798-4.0691-6.7308 0-12.3607 1.2821-17.1962 3.8322-4.8356 2.5502-8.7793 5.9225-11.8172 10.1031-3.0378 4.1806-5.2954 8.9465-6.7725 14.2698-1.4632 5.3233-2.2018 10.758-2.2018 16.3043 0 5.9782.7386 11.6639 2.2018 17.0429 1.4632 5.3793 3.7207 10.1033 6.7725 14.1863 3.0379 4.083 6.9816 7.288 11.8172 9.615 4.8355 2.341 10.563 3.512 17.1962 3.512 10.6465 0 18.8823-2.606 24.7073-7.832 5.8106-5.212 9.8106-12.611 11.9846-22.1708H95.9754c-1.6304 6.5218-4.5708 11.7338-8.8071 15.6498-4.2363 3.915-10.1031 5.866-17.6142 5.866-4.8913 0-9.0719-1.031-12.5557-3.093-3.4839-2.063-6.3545-4.669-8.6399-7.832-2.2854-3.149-3.9437-6.7168-4.9749-10.6744-.9198-3.5117-1.4214-6.912-1.5329-10.2146-.0279-.864-.0697-1.7141-.1254-2.5781-.1812-2.5501-.1533-5.0445.1254-7.4832.432-3.7626 1.3238-7.4415 2.6755-11.0368 1.3518-3.6371 3.1773-6.8422 5.4627-9.6154 2.2854-2.7731 5.0585-5.0027 8.3194-6.6889 3.2608-1.6862 7.0094-2.5223 11.2458-2.5223 4.2363 0 7.8316.8361 11.0925 2.5223 3.2608 1.6862 6.034 3.9158 8.3194 6.6889 2.2854 2.7732 4.0412 5.9504 5.2954 9.5318 1.2541 3.5814 1.923 7.3439 2.0345 11.2458H50.7553l.0418 8.6399h55.7689c.223-5.8668-.32-11.6639-1.63-17.3634-1.31-5.6996-3.456-10.7581-6.4383-15.1616"/><path d="M292.434 37.1093v84.1277h10.27V76.393c0-4.4593.752-8.5563 2.285-12.3049q2.2785-5.6229 6.438-9.699c2.774-2.7174 6.062-4.8077 9.867-6.2709 3.804-1.4632 8.04-2.0903 12.723-1.8813V35.9666c-7.609-.3205-14.159 1.3657-19.649 5.0585-5.491 3.6929-9.532 8.9604-12.152 15.8166h-.32V37.1093zM409.994 64.5756c-1.31-5.6996-3.456-10.7581-6.438-15.1616-2.996-4.4036-6.87-7.9571-11.664-10.6745-4.779-2.7174-10.549-4.0691-17.279-4.0691-6.731 0-12.361 1.2821-17.196 3.8322-4.836 2.5502-8.78 5.9225-11.818 10.1031s-5.295 8.9465-6.772 14.2698c-1.463 5.3233-2.202 10.758-2.202 16.3043 0 5.9782.739 11.6639 2.202 17.0429 1.463 5.3793 3.721 10.1033 6.772 14.1863 3.038 4.083 6.982 7.288 11.818 9.615 4.835 2.341 10.562 3.512 17.196 3.512 10.646 0 18.882-2.606 24.707-7.832 5.811-5.212 9.81-12.611 11.984-22.1708h-10.27c-1.63 6.5218-4.571 11.7338-8.807 15.6498-4.236 3.915-10.103 5.866-17.614 5.866-4.892 0-9.072-1.031-12.556-3.093-3.484-2.063-6.355-4.669-8.64-7.832-2.285-3.149-3.944-6.7168-4.975-10.6744-1.031-3.9716-1.547-7.8038-1.547-11.4967h64.73c.223-5.8667-.321-11.6638-1.631-17.3634zm-63.099 8.7235c.432-3.8043 1.324-7.5251 2.69-11.1622 1.352-3.6371 3.177-6.8422 5.462-9.6154 2.286-2.7731 5.059-5.0027 8.32-6.6889s7.009-2.5223 11.246-2.5223c4.236 0 7.831.8361 11.092 2.5223s6.034 3.9158 8.32 6.6889c2.285 2.7732 4.041 5.9504 5.295 9.5318s1.923 7.3439 2.035 11.2458zM470.971 111.455c-2.286 1.31-4.752 2.23-7.414 2.773-2.662.544-5.24.808-7.748.808-6.842 0-12.584-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.119-9.6154-1.407-2.7173-3.233-5.0027-5.462-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.699-3.0936c-1.741-.432-3.637-1.0034-5.713-1.7141-2.062-.7107-3.972-1.6025-5.7-2.6895-1.741-1.0869-3.177-2.4108-4.319-3.9994-1.143-1.5747-1.715-3.5117-1.715-5.7832 0-2.7173.6-5.0027 1.798-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.341-.4877 4.641-.7386 6.926-.7386 2.94 0 5.714.3484 8.32 1.0591 2.605.7107 4.919 1.8256 6.925 3.3445 2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.853 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.616-5.0585-3.637-1.087-7.58-1.6304-11.817-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.187 4.083-3.037 1.8534-5.518 4.2921-7.413 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.152 4.2364c1.032 1.6861 1.547 3.7764 1.547 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975zM549.385 111.455c-2.286 1.31-4.752 2.23-7.414 2.773-2.661.544-5.24.808-7.748.808-6.842 0-12.583-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.118-9.6154-1.408-2.7173-3.233-5.0027-5.463-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.698-3.0936c-1.742-.432-3.638-1.0034-5.714-1.7141-2.062-.7107-3.971-1.6025-5.699-2.6895-1.742-1.0869-3.178-2.4108-4.32-3.9994-1.143-1.5747-1.714-3.5117-1.714-5.7832 0-2.7173.599-5.0027 1.797-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.342-.4877 4.641-.7386 6.926-.7386 2.941 0 5.714.3484 8.32 1.0591s4.919 1.8256 6.925 3.3445c2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.854 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.615-5.0585-3.638-1.087-7.581-1.6304-11.818-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.186 4.083-3.038 1.8534-5.519 4.2921-7.414 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.153 4.2364c1.031 1.6861 1.546 3.7764 1.546 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975z"/></g><defs><clipPath id="a"><path fill="#fff" d="M0 0h598.982v158.277H0z"/></clipPath></defs></svg>
diff --git a/public/images/logos/logo-white.svg b/public/images/logos/logo-white.svg
new file mode 100644
index 0000000000..087ca19ac7
--- /dev/null
+++ b/public/images/logos/logo-white.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="353" height="258" fill="none" viewBox="0 0 353 258"><g fill="#000" clip-path="url(#a)"><path d="M180.477 197.464h20.699l102.5-137.0211h-20.972z"/><path d="M323.863 218.64v.045l-59.307-79.008-10.918 14.231 65.413 89.993H13.8905V13.8905H149.028l74.355 98.8675 10.849-14.1398-62.666-84.7277h.046L161.058 0H0v257.792h352.665z"/><path d="M160.424 80.4821c-4.88-7.1722-11.19-12.9599-18.998-17.3858-7.785-4.4259-17.181-6.6275-28.144-6.6275s-20.1322 2.0881-28.008 6.2416-14.2991 9.6462-19.247 16.4553-8.6249 14.5714-11.0307 23.2413c-2.3832 8.671-3.5861 17.522-3.5861 26.556 0 9.737 1.2029 18.997 3.5861 27.758s6.0601 16.455 11.0307 23.106c4.9479 6.65 11.3712 11.87 19.247 15.661 7.8758 3.813 17.204 5.719 28.008 5.719 17.34 0 30.754-4.244 40.242-12.756 9.464-8.488 15.978-20.54 19.519-36.11h-16.728c-2.655 10.622-7.444 19.11-14.344 25.488s-16.455 9.556-28.689 9.556c-7.967 0-14.7757-1.68-20.4499-5.039-5.6743-3.359-10.3498-7.603-14.0721-12.756-3.7223-5.129-6.4233-10.94-8.1028-17.386-1.498-5.719-2.3151-11.257-2.4967-16.636-.0454-1.408-.1135-2.792-.2043-4.199-.295-4.154-.2496-8.217.2043-12.189q1.0554-9.192 4.3578-17.976c2.2016-5.9235 5.1749-11.1438 8.8972-15.6605q5.58345-6.77505 13.5501-10.8945c5.3114-2.7463 11.4164-4.1081 18.3164-4.1081s12.756 1.3618 18.067 4.1081 9.828 6.3778 13.55 10.8945 6.582 9.6916 8.625 15.5245c2.042 5.833 3.132 11.962 3.313 18.317H82.6638l.0681 14.072h90.8331c.363-9.556-.522-18.998-2.655-28.281-2.134-9.2827-5.629-17.5217-10.486-24.6939"/></g><defs><clipPath id="a"><path fill="#000" d="M0 0h352.665v257.792H0z"/></clipPath></defs></svg>
diff --git a/public/netlify-logo.svg b/public/netlify-logo.svg
new file mode 100644
index 0000000000..2edda22502
--- /dev/null
+++ b/public/netlify-logo.svg
@@ -0,0 +1 @@
+<svg width="114" height="50" viewBox="0 0 114 50" fill="none" xmlns="http://www.w3.org/2000/svg"><g clip-path="url(#a)"><path fill="#0C2A2A" d="M0 0h114v51H0z"/><g clip-path="url(#b)"><path d="M44.445 40.302v-7.695l.153-.16h1.853l.154.16v7.695l-.154.16h-1.853l-.153-.16ZM44.445 17.855v-7.696l.153-.159h1.853l.154.16v7.695l-.154.16h-1.853l-.153-.16ZM38.068 34.892h-.254l-1.275-1.323v-.264l2.388-2.482 1.349.002.18.185v1.4l-2.388 2.482ZM36.54 17.227v-.267l1.274-1.32h.254l2.388 2.479v1.398l-.18.19h-1.349l-2.388-2.48ZM28.154 24.107h10.5l.153.16v1.926l-.153.16h-10.5l-.154-.16v-1.927l.154-.16ZM99.844 24.11l.154.159v1.924l-.154.16H89.19l-.153-.16.77-1.924.154-.16h9.883Z" fill="#32E6E2"/><path d="M49 29.24h-1.853l-.153-.16v-4.502c0-.802-.303-1.423-1.234-1.443a24.2 24.2 0 0 0-1.613.025l-.089.092v5.826l-.153.16h-1.853l-.154-.16v-7.695l.154-.16h4.169c1.62 0 2.933 1.364 2.933 3.046v4.81l-.154.159v.002ZM57.974 25.871l-.154.16h-4.79l-.154.16c0 .32.31 1.283 1.546 1.283.463 0 .926-.16 1.082-.481l.154-.16h1.852l.154.16c-.154.962-.926 2.407-3.245 2.407-2.625 0-3.861-1.924-3.861-4.172 0-2.248 1.236-4.171 3.708-4.171 2.472 0 3.708 1.924 3.708 4.171v.643Zm-2.319-1.605c0-.16-.153-1.283-1.39-1.283-1.235 0-1.389 1.124-1.389 1.283l.154.16h2.472l.153-.16ZM62.298 26.833c0 .322.154.481.464.481h1.39l.153.16v1.604l-.154.16h-1.39c-1.389 0-2.625-.643-2.625-2.407v-3.529l-.154-.16H58.9l-.154-.159v-1.605l.154-.16h1.082l.154-.159v-1.443l.154-.16h1.852l.154.16v1.443l.154.16h1.699l.153.16v1.604l-.153.16h-1.7l-.153.159v3.529l.002.002ZM68.015 29.24h-1.853l-.153-.16V18.172l.153-.16h1.853l.154.16v10.907l-.154.16v.002ZM72.186 19.935h-1.852l-.154-.16v-1.604l.154-.16h1.852l.154.16v1.605l-.154.16Zm0 9.305h-1.852l-.154-.16v-7.7l.154-.159h1.852l.154.16v7.7l-.154.16ZM79.449 18.171v1.605l-.154.16h-1.39c-.309 0-.463.159-.463.48v.643l.154.16h1.546l.153.16v1.604l-.153.16h-1.546l-.154.159v5.774l-.153.16h-1.853l-.154-.16v-5.774l-.153-.16h-1.083l-.153-.159v-1.605l.153-.16h1.083l.153-.159v-.643c0-1.764 1.236-2.407 2.626-2.407h1.39l.153.16-.002.002ZM85.163 29.4c-.619 1.605-1.236 2.567-3.398 2.567h-.773l-.154-.16v-1.605l.154-.16h.773c.773 0 .926-.159 1.082-.64v-.16l-2.472-6.257v-1.604l.154-.16h1.39l.153.16 1.853 5.455h.153l1.853-5.455.154-.16h1.39l.153.16v1.604l-2.472 6.417.007-.002Z" fill="#fff"/></g><path fill="#32E6E2" d="M0 0v51h15V0z"/><path d="M5.518 45.367v-.774H10v.774H5.518Zm0-1.746c0-.44.098-.784.294-1.032.196-.248.474-.372.834-.372.348 0 .622.13.822.39.2.26.3.628.3 1.104l-.336.018c.004-.608.114-1.062.33-1.362.212-.3.524-.45.936-.45.424 0 .748.146.972.438.22.288.33.686.33 1.194v1.242h-.738v-1.152c0-.268-.05-.488-.15-.66a.498.498 0 0 0-.462-.258c-.224 0-.39.088-.498.264-.108.172-.162.39-.162.654v1.146h-.738V43.68c0-.192-.04-.36-.12-.504a.426.426 0 0 0-.396-.216c-.192 0-.33.068-.414.204a.955.955 0 0 0-.126.51v1.116h-.678v-1.17Zm0-2.925v-.774H8.17c.256 0 .472-.04.648-.12a.88.88 0 0 0 .39-.336.926.926 0 0 0 .126-.486.926.926 0 0 0-.126-.486.845.845 0 0 0-.39-.33 1.497 1.497 0 0 0-.648-.126H5.518v-.75h2.664c.604 0 1.068.146 1.392.438.324.288.486.71.486 1.266 0 .56-.162.984-.486 1.272-.324.288-.788.432-1.392.432H5.518Zm0-5.048v-.774H10v.774H5.518Zm0-2.475V32.4H10v.774H5.518Zm3.75-.546v-2.412H10v2.412h-.732Zm-3.69-3.903v-.773H10v.773H5.578Zm-.06 1.41v-3.6h.732v3.6h-.732Zm0-6.98v-.827l3.684-1.056v.318L5.518 20.43v-.888l3.684-1.122v.318L5.518 17.64v-.798L10 18.18v.81l-4.086 1.254v-.438L10 21.097v.756l-4.482 1.302Zm0-7.385v-.774H10v.774H5.518Zm.06-3.283v-.774H10v.774H5.578Zm-.06 1.41v-3.6h.732v3.6h-.732Zm0-4.7v-.773H10v.774H5.518Zm1.572-.545V6.179h.732V8.65H7.09ZM5.518 6.407v-.774H10v.774H5.518Z" fill="#0C2A2A"/></g><rect x="1" y="1" width="112" height="48" rx="3" stroke="#32E6E2" stroke-width="2"/><defs><clipPath id="a"><rect width="114" height="50" rx="4" fill="#fff"/></clipPath><clipPath id="b"><path fill="#fff" d="M28 10h72v30.462H28z"/></clipPath></defs></svg>
\ No newline at end of file
diff --git a/public/openjs-logo-black.svg b/public/openjs-logo-black.svg
new file mode 100644
index 0000000000..2c30e009a4
--- /dev/null
+++ b/public/openjs-logo-black.svg
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 23.0.2, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="ARTWORK" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 1000 314.4" style="enable-background:new 0 0 1000 314.4;" xml:space="preserve">
+<g>
+	<path d="M271.4,78.1L137,0.5L136.1,0l-0.9,0.5L1.6,77.7l-0.7,0.4L0,78.6v157.2l0.9,0.5l134.4,77.6l0.9,0.5l0.9-0.5l132.6-76.5
+		l1.8-1l0.9-0.5V78.6L271.4,78.1z M122.7,20.1L89.8,77H24.1L122.7,20.1z M84.4,86.4L69,113.1L22.8,86.4H84.4z M72.4,125.8l54.3,31.4
+		l-54.3,31.4l-18.1-31.4L72.4,125.8z M64.4,121.2l-15.4,26.7L18.1,94.5L64.4,121.2z M10.7,100.3l32.9,56.9l-32.9,56.9V100.3z
+		 M48.9,166.6l15.4,26.7l-46.2,26.7L48.9,166.6z M69,201.3L84.4,228H22.8L69,201.3z M24.1,237.4h65.7l32.9,56.9L24.1,237.4z
+		 M131.5,290.8l-30.8-53.4h30.8V290.8z M131.5,228H95.2l-18.1-31.4l54.3-31.4V228z M131.5,149.1l-54.3-31.4l18.1-31.4h36.2V149.1z
+		 M131.5,77h-30.8l30.8-53.4V77z M207.9,121.2l46.2-26.7l-30.8,53.4L207.9,121.2z M217.9,157.2l-18.1,31.4l-54.3-31.4l54.3-31.4
+		L217.9,157.2z M203.2,113.1l-15.4-26.7h61.6L203.2,113.1z M248.1,77h-65.7l-32.8-56.9L248.1,77z M140.8,23.6L171.6,77h-30.8V23.6z
+		 M140.8,86.4H177l18.1,31.4l-54.3,31.4V86.4z M140.8,165.3l54.3,31.4L177,228h-36.2V165.3z M140.8,237.4h30.8l-30.8,53.4V237.4z
+		 M149.6,294.3l32.8-56.9h65.7L149.6,294.3z M187.8,228l15.4-26.7l46.2,26.7H187.8z M207.9,193.2l15.4-26.7l30.8,53.4L207.9,193.2z
+		 M261.6,214.1l-32.9-56.9l32.9-56.9V214.1z"/>
+	<polygon points="308.4,202.7 372.6,202.7 372.6,208.5 315,208.5 315,257 367.2,257 367.2,263 315,263 315,312.9 308.4,312.9 	"/>
+	<path d="M383.8,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
+		C399,314.2,383.8,298.7,383.8,279.7 M446,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
+		C434.8,308.6,446,296.1,446,279.7"/>
+	<path d="M469.9,288.5v-41.7h6.3v40.7c0,13.5,6.3,21.1,19,21.1c14.3,0,24.3-9.6,24.3-24.8v-37h6.3v66.2h-6.3l0.2-14.6
+		c-4.4,9.9-13.5,16-25.1,16C479.8,314.4,469.9,304.7,469.9,288.5"/>
+	<path d="M543,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
+		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37H543V246.8z"/>
+	<path d="M616.3,279.7c0-19.5,13.8-34.4,32.8-34.4c13.5,0,23.2,7.3,28,17.2v-66.6h6.3v117.1h-6.3l0.3-16.5
+		c-4.7,10.2-15.6,17.8-28.4,17.8C630.1,314.2,616.3,299.2,616.3,279.7 M677.6,279.7c0-16.4-11-28.7-27.7-28.7
+		c-16.4,0-26.9,12.3-26.9,28.7c0,16.4,10.5,28.9,26.9,28.9C666.6,308.6,677.6,296.1,677.6,279.7"/>
+	<path d="M748,271.4c0-14.9-6.8-20.6-17.7-20.6c-10.1,0-16.9,4.2-21.6,11.4l-4.5-3.2c5.5-8.6,14.9-13.6,26.3-13.6
+		c13.6,0,23.8,8.3,23.8,25.5v42.2H748l0.3-10.2c-4.2,6.3-11.5,11.5-22.9,11.5c-15.1,0-25-7-25-20.3c0-13.1,11.5-19.3,24.2-19.3H748
+		V271.4z M725.4,279.9c-10.1,0-18.6,3.9-18.6,13.9c0,10.1,6.6,14.8,19.3,14.8c11,0,21.9-6.5,21.9-16.7v-12H725.4z"/>
+	<path d="M782.5,295.4v-43.3h-10.4v-5.4h10.4v-23.2h6.3v23.2h19.1v5.4h-19.1v43.1c0,9.7,3.4,13.3,8.9,13.3c5.8,0,8.1-2.3,10.5-4.9
+		l4.1,3.9c-3.2,3.7-7.1,6.6-14.6,6.6C789.3,314.2,782.5,308.9,782.5,295.4"/>
+	<path d="M829.5,218.2c0-3.1,2.6-5.4,5.4-5.4c2.8,0,5.4,2.3,5.4,5.4c0,3.2-2.6,5.3-5.4,5.3C832.1,223.6,829.5,221.5,829.5,218.2
+		 M831.8,246.8h6.3v66.2h-6.3V246.8z"/>
+	<path d="M857.1,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
+		C872.4,314.2,857.1,298.7,857.1,279.7 M919.4,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
+		C908.2,308.6,919.4,296.1,919.4,279.7"/>
+	<path d="M943.9,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
+		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37h-6.3V246.8z"/>
+	<path d="M308.4,73.1c0-41.4,31.8-71.3,71.7-71.3c39.6,0,71.5,29.8,71.5,71.3c0,41.4-31.9,71.3-71.5,71.3
+		C340.2,144.3,308.4,114.5,308.4,73.1 M429.4,73.1c0-29.6-20.4-51.9-49.4-51.9c-29,0-49.6,22.3-49.6,51.9
+		c0,29.6,20.6,51.9,49.6,51.9C409,124.9,429.4,102.7,429.4,73.1"/>
+	<path d="M473.9,56.8h20.8l-0.6,15.9c5.5-10.6,15.7-17.8,30.4-17.8c22,0,39.8,18.6,39.8,44.5c0,25.9-18,44.9-40.2,44.9
+		c-14.3,0-24.5-6.9-29.4-16.5v58h-20.8V56.8z M543.1,99.4c0-15.5-9.4-26.1-24.3-26.1c-15.1,0-24.9,10.6-24.9,26.1
+		c0,16.1,9.8,26.7,24.9,26.7C533.8,126.2,543.1,115.6,543.1,99.4"/>
+	<path d="M635,127c11.2,0,19.4-4.5,24.3-9.2l12,12.7c-8,8-19,13.9-36.1,13.9c-29.4,0-48.4-19-48.4-44.7c0-25.5,20-44.7,45.7-44.7
+		c29.2,0,45.7,21.6,44.3,51.7h-69C610.3,119,619.3,127,635,127 M656.1,92.3c-1.8-11.6-9-20.2-23.3-20.2c-13.3,0-22.5,7.3-24.9,20.2
+		H656.1z"/>
+	<path d="M699.7,56.8h20.6l-0.4,15.9c5.3-11.2,16.1-17.8,29-17.8c19,0,32.1,13.5,32.1,36.7v50.8h-20.6V93.3
+		c0-12.3-5.7-19.4-17.8-19.4c-13.5,0-22.3,8.2-22.3,22v46.5h-20.6V56.8z"/>
+	<path d="M803.5,120.9l17.6-10.8c4.9,8.8,10.6,14.9,20.8,14.9c11.6,0,19.2-5.5,19.2-21.6V3.7h21.6v100c0,27.6-16.5,40.6-39.8,40.6
+		C822.3,144.3,810.1,133.7,803.5,120.9"/>
+	<path d="M904.9,115.6l17.8-9.8c6.5,10.8,14.9,19.4,31.8,19.4c14.1,0,24.1-7.6,24.1-19c0-12-8.2-17.4-23.3-24.1l-9.2-4.1
+		c-20.2-9-32.5-19.2-32.5-40.6c0-20.6,15.9-35.3,39-35.3C971,2,983.5,9,991.8,23.9l-16.9,10.4c-5.3-9.2-11.4-13.5-22.3-13.5
+		c-11,0-18,6.7-18,16.1c0,10.4,5.9,15.1,20,21.2l9,4.1c23.7,10.4,36.3,21.4,36.3,43.7c0,24.3-19,38.4-45.1,38.4
+		C928.5,144.3,912.6,131.3,904.9,115.6"/>
+</g>
+</svg>
diff --git a/public/openjs-logo-white.svg b/public/openjs-logo-white.svg
new file mode 100644
index 0000000000..1a4436d3ea
--- /dev/null
+++ b/public/openjs-logo-white.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Generator: Adobe Illustrator 23.0.2, SVG Export Plug-In . SVG Version: 6.00 Build 0)  -->
+<svg version="1.1" id="ARTWORK" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px"
+	 viewBox="0 0 1000 314.4" style="enable-background:new 0 0 1000 314.4;" xml:space="preserve">
+<style type="text/css">
+	.st0{fill:#FFFFFF;}
+</style>
+<g>
+	<path class="st0" d="M271.4,78.1L137,0.5L136.1,0l-0.9,0.5L1.6,77.7l-0.7,0.4L0,78.6v157.2l0.9,0.5l134.4,77.6l0.9,0.5l0.9-0.5
+		l132.6-76.5l1.8-1l0.9-0.5V78.6L271.4,78.1z M122.7,20.1L89.8,77H24.1L122.7,20.1z M84.4,86.4L69,113.1L22.8,86.4H84.4z
+		 M72.4,125.8l54.3,31.4l-54.3,31.4l-18.1-31.4L72.4,125.8z M64.4,121.2l-15.4,26.7L18.1,94.5L64.4,121.2z M10.7,100.3l32.9,56.9
+		l-32.9,56.9V100.3z M48.9,166.6l15.4,26.7l-46.2,26.7L48.9,166.6z M69,201.3L84.4,228H22.8L69,201.3z M24.1,237.4h65.7l32.9,56.9
+		L24.1,237.4z M131.5,290.8l-30.8-53.4h30.8V290.8z M131.5,228H95.2l-18.1-31.4l54.3-31.4V228z M131.5,149.1l-54.3-31.4l18.1-31.4
+		h36.2V149.1z M131.5,77h-30.8l30.8-53.4V77z M207.9,121.2l46.2-26.7l-30.8,53.4L207.9,121.2z M217.9,157.2l-18.1,31.4l-54.3-31.4
+		l54.3-31.4L217.9,157.2z M203.2,113.1l-15.4-26.7h61.6L203.2,113.1z M248.1,77h-65.7l-32.8-56.9L248.1,77z M140.8,23.6L171.6,77
+		h-30.8V23.6z M140.8,86.4H177l18.1,31.4l-54.3,31.4V86.4z M140.8,165.3l54.3,31.4L177,228h-36.2V165.3z M140.8,237.4h30.8
+		l-30.8,53.4V237.4z M149.6,294.3l32.8-56.9h65.7L149.6,294.3z M187.8,228l15.4-26.7l46.2,26.7H187.8z M207.9,193.2l15.4-26.7
+		l30.8,53.4L207.9,193.2z M261.6,214.1l-32.9-56.9l32.9-56.9V214.1z"/>
+	<polygon class="st0" points="308.4,202.7 372.6,202.7 372.6,208.5 315,208.5 315,257 367.2,257 367.2,263 315,263 315,312.9 
+		308.4,312.9 	"/>
+	<path class="st0" d="M383.8,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
+		C399,314.2,383.8,298.7,383.8,279.7 M446,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
+		C434.8,308.6,446,296.1,446,279.7"/>
+	<path class="st0" d="M469.9,288.5v-41.7h6.3v40.7c0,13.5,6.3,21.1,19,21.1c14.3,0,24.3-9.6,24.3-24.8v-37h6.3v66.2h-6.3l0.2-14.6
+		c-4.4,9.9-13.5,16-25.1,16C479.8,314.4,469.9,304.7,469.9,288.5"/>
+	<path class="st0" d="M543,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
+		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37H543V246.8z"/>
+	<path class="st0" d="M616.3,279.7c0-19.5,13.8-34.4,32.8-34.4c13.5,0,23.2,7.3,28,17.2v-66.6h6.3v117.1h-6.3l0.3-16.5
+		c-4.7,10.2-15.6,17.8-28.4,17.8C630.1,314.2,616.3,299.2,616.3,279.7 M677.6,279.7c0-16.4-11-28.7-27.7-28.7
+		c-16.4,0-26.9,12.3-26.9,28.7c0,16.4,10.5,28.9,26.9,28.9C666.6,308.6,677.6,296.1,677.6,279.7"/>
+	<path class="st0" d="M748,271.4c0-14.9-6.8-20.6-17.7-20.6c-10.1,0-16.9,4.2-21.6,11.4l-4.5-3.2c5.5-8.6,14.9-13.6,26.3-13.6
+		c13.6,0,23.8,8.3,23.8,25.5v42.2H748l0.3-10.2c-4.2,6.3-11.5,11.5-22.9,11.5c-15.1,0-25-7-25-20.3c0-13.1,11.5-19.3,24.2-19.3H748
+		V271.4z M725.4,279.9c-10.1,0-18.6,3.9-18.6,13.9c0,10.1,6.6,14.8,19.3,14.8c11,0,21.9-6.5,21.9-16.7v-12H725.4z"/>
+	<path class="st0" d="M782.5,295.4v-43.3h-10.4v-5.4h10.4v-23.2h6.3v23.2h19.1v5.4h-19.1v43.1c0,9.7,3.4,13.3,8.9,13.3
+		c5.8,0,8.1-2.3,10.5-4.9l4.1,3.9c-3.2,3.7-7.1,6.6-14.6,6.6C789.3,314.2,782.5,308.9,782.5,295.4"/>
+	<path class="st0" d="M829.5,218.2c0-3.1,2.6-5.4,5.4-5.4c2.8,0,5.4,2.3,5.4,5.4c0,3.2-2.6,5.3-5.4,5.3
+		C832.1,223.6,829.5,221.5,829.5,218.2 M831.8,246.8h6.3v66.2h-6.3V246.8z"/>
+	<path class="st0" d="M857.1,279.7c0-19,15.2-34.4,34.5-34.4c19.3,0,34.2,15.4,34.2,34.4c0,19-14.9,34.5-34.2,34.5
+		C872.4,314.2,857.1,298.7,857.1,279.7 M919.4,279.7c0-16.4-11.2-28.7-27.7-28.7c-16.5,0-28,12.3-28,28.7c0,16.4,11.5,28.9,28,28.9
+		C908.2,308.6,919.4,296.1,919.4,279.7"/>
+	<path class="st0" d="M943.9,246.8h6.3l-0.2,14.8c4.4-10,13.6-16.2,25.3-16.2c14.8,0,24.6,9.9,24.6,26.3v41.3h-6.3v-40.2
+		c0-13.6-6.3-21.6-19.1-21.6c-14.3,0-24.3,9.4-24.3,24.8v37h-6.3V246.8z"/>
+	<path class="st0" d="M308.4,73.1c0-41.4,31.8-71.3,71.7-71.3c39.6,0,71.5,29.8,71.5,71.3c0,41.4-31.9,71.3-71.5,71.3
+		C340.2,144.3,308.4,114.5,308.4,73.1 M429.4,73.1c0-29.6-20.4-51.9-49.4-51.9c-29,0-49.6,22.3-49.6,51.9
+		c0,29.6,20.6,51.9,49.6,51.9C409,124.9,429.4,102.7,429.4,73.1"/>
+	<path class="st0" d="M473.9,56.8h20.8l-0.6,15.9c5.5-10.6,15.7-17.8,30.4-17.8c22,0,39.8,18.6,39.8,44.5c0,25.9-18,44.9-40.2,44.9
+		c-14.3,0-24.5-6.9-29.4-16.5v58h-20.8V56.8z M543.1,99.4c0-15.5-9.4-26.1-24.3-26.1c-15.1,0-24.9,10.6-24.9,26.1
+		c0,16.1,9.8,26.7,24.9,26.7C533.8,126.2,543.1,115.6,543.1,99.4"/>
+	<path class="st0" d="M635,127c11.2,0,19.4-4.5,24.3-9.2l12,12.7c-8,8-19,13.9-36.1,13.9c-29.4,0-48.4-19-48.4-44.7
+		c0-25.5,20-44.7,45.7-44.7c29.2,0,45.7,21.6,44.3,51.7h-69C610.3,119,619.3,127,635,127 M656.1,92.3c-1.8-11.6-9-20.2-23.3-20.2
+		c-13.3,0-22.5,7.3-24.9,20.2H656.1z"/>
+	<path class="st0" d="M699.7,56.8h20.6l-0.4,15.9c5.3-11.2,16.1-17.8,29-17.8c19,0,32.1,13.5,32.1,36.7v50.8h-20.6V93.3
+		c0-12.3-5.7-19.4-17.8-19.4c-13.5,0-22.3,8.2-22.3,22v46.5h-20.6V56.8z"/>
+	<path class="st0" d="M803.5,120.9l17.6-10.8c4.9,8.8,10.6,14.9,20.8,14.9c11.6,0,19.2-5.5,19.2-21.6V3.7h21.6v100
+		c0,27.6-16.5,40.6-39.8,40.6C822.3,144.3,810.1,133.7,803.5,120.9"/>
+	<path class="st0" d="M904.9,115.6l17.8-9.8c6.5,10.8,14.9,19.4,31.8,19.4c14.1,0,24.1-7.6,24.1-19c0-12-8.2-17.4-23.3-24.1
+		l-9.2-4.1c-20.2-9-32.5-19.2-32.5-40.6c0-20.6,15.9-35.3,39-35.3C971,2,983.5,9,991.8,23.9l-16.9,10.4
+		c-5.3-9.2-11.4-13.5-22.3-13.5c-11,0-18,6.7-18,16.1c0,10.4,5.9,15.1,20,21.2l9,4.1c23.7,10.4,36.3,21.4,36.3,43.7
+		c0,24.3-19,38.4-45.1,38.4C928.5,144.3,912.6,131.3,904.9,115.6"/>
+</g>
+</svg>
diff --git a/public/site.webmanifest b/public/site.webmanifest
new file mode 100644
index 0000000000..3fbbdf62be
--- /dev/null
+++ b/public/site.webmanifest
@@ -0,0 +1,21 @@
+{
+  "name": "Express.js",
+  "short_name": "Express.js",
+  "icons": [
+    {
+      "src": "/web-app-manifest-192x192.png",
+      "sizes": "192x192",
+      "type": "image/png",
+      "purpose": "maskable"
+    },
+    {
+      "src": "/web-app-manifest-512x512.png",
+      "sizes": "512x512",
+      "type": "image/png",
+      "purpose": "maskable"
+    }
+  ],
+  "theme_color": "#ffffff",
+  "background_color": "#1a1a1a",
+  "display": "standalone"
+}
diff --git a/public/videos/hero-background-light.webm b/public/videos/hero-background-light.webm
new file mode 100644
index 0000000000..ff8e6e6b5b
Binary files /dev/null and b/public/videos/hero-background-light.webm differ
diff --git a/public/videos/hero-background.webm b/public/videos/hero-background.webm
new file mode 100644
index 0000000000..6cf492dbcc
Binary files /dev/null and b/public/videos/hero-background.webm differ
diff --git a/scripts/orama-documents.mjs b/scripts/orama-documents.mjs
new file mode 100644
index 0000000000..0b9a9668b1
--- /dev/null
+++ b/scripts/orama-documents.mjs
@@ -0,0 +1,135 @@
+import { readFile, readdir, stat } from 'node:fs/promises';
+import { join, relative, extname, basename } from 'node:path';
+import { fileURLToPath, URL } from 'node:url';
+import matter from 'gray-matter';
+import { fromMarkdown } from 'mdast-util-from-markdown';
+import { toString } from 'mdast-util-to-string';
+
+const CONTENT_DIR = fileURLToPath(new URL('../src/content', import.meta.url));
+
+const stripMdxImports = (content) => content.replace(/^import\s+.*$/gm, '');
+
+const mdToText = (content) =>
+  toString(fromMarkdown(stripMdxImports(content))).replace(/<[^>]*>/g, '');
+
+const collectMdFiles = async (dir, base = dir) => {
+  const entries = await readdir(dir);
+  const results = await Promise.all(
+    entries.map(async (entry) => {
+      const fullPath = join(dir, entry);
+      const info = await stat(fullPath);
+      if (info.isDirectory()) return collectMdFiles(fullPath, base);
+      if (extname(entry) === '.md' || extname(entry) === '.mdx') return [relative(base, fullPath)];
+      return [];
+    })
+  );
+  return results.flat();
+};
+
+export const getPages = async (lang) => {
+  const baseDir = join(CONTENT_DIR, `pages/${lang}`);
+  const mdFiles = await collectMdFiles(baseDir);
+
+  return Promise.all(
+    mdFiles.map(async (file) => {
+      const fullPath = join(baseDir, file);
+      const raw = await readFile(fullPath, 'utf-8');
+      const { data, content } = matter(raw);
+      const pathSegment = relative(baseDir, fullPath).replace(/\.mdx?$/, '');
+      const isResource = pathSegment.startsWith('resources');
+
+      return {
+        title: data.title ?? basename(file).replace(/\.mdx?$/, ''),
+        description: data.description ?? '',
+        content: mdToText(content),
+        path: `/${lang}/${pathSegment}`,
+        category: isResource ? 'menu.main.resources' : 'menu.main.docs',
+      };
+    })
+  );
+};
+
+export const getDocs = async (lang) => {
+  const baseDir = join(CONTENT_DIR, `docs/${lang}/5x`);
+  const mdFiles = await collectMdFiles(baseDir);
+
+  return Promise.all(
+    mdFiles.map(async (file) => {
+      const fullPath = join(baseDir, file);
+      const raw = await readFile(fullPath, 'utf-8');
+      const { data, content } = matter(raw);
+      const pathSegment = relative(baseDir, fullPath).replace(/\.mdx?$/, '');
+
+      return {
+        title: data.title ?? basename(file).replace(/\.mdx?$/, ''),
+        description: data.description ?? '',
+        content: mdToText(content),
+        path: `/${lang}/${pathSegment}`,
+        category: 'menu.main.docs',
+      };
+    })
+  );
+};
+
+export const getBlogPosts = async (lang) => {
+  const baseDir = join(CONTENT_DIR, `blog`);
+  const mdFiles = await collectMdFiles(baseDir);
+
+  return Promise.all(
+    mdFiles.map(async (file) => {
+      const fullPath = join(baseDir, file);
+      const raw = await readFile(fullPath, 'utf-8');
+      const { data, content } = matter(raw);
+      const slug = basename(file).replace(/\.mdx?$/, '');
+
+      return {
+        title: data.title ?? slug,
+        description: data.description ?? '',
+        content: mdToText(content),
+        path: `/${lang}/blog/${slug}`,
+        category: 'menu.main.blog',
+      };
+    })
+  );
+};
+
+const VERSIONS = /** @type {const} */ (['5x', '4x', '3x']);
+
+export const getApi = async (lang) => {
+  const results = await Promise.all(
+    VERSIONS.map(async (version) => {
+      const baseDir = join(CONTENT_DIR, `api/${version}`);
+      const mdFiles = await collectMdFiles(baseDir);
+
+      return Promise.all(
+        mdFiles.map(async (file) => {
+          const fullPath = join(baseDir, file);
+          const raw = await readFile(fullPath, 'utf-8');
+          const { data, content } = matter(raw);
+          const pathSegment = relative(baseDir, fullPath).replace(/\.mdx?$/, '');
+
+          return {
+            title: data.title ?? basename(file).replace(/\.mdx?$/, ''),
+            description: data.description ?? '',
+            content: mdToText(content),
+            path: `/${lang}/${version}/${pathSegment}`,
+            category: 'menu.main.api',
+            version,
+          };
+        })
+      );
+    })
+  );
+
+  return results.flat();
+};
+
+export const getAllDocuments = async (lang) => {
+  const [docs, api, pages, blog] = await Promise.all([
+    getDocs(lang),
+    getApi(lang),
+    getPages(lang),
+    getBlogPosts(lang),
+  ]);
+  return [...docs, ...api, ...pages, ...blog];
+};
diff --git a/scripts/sync-orama.mjs b/scripts/sync-orama.mjs
new file mode 100644
index 0000000000..cfb28c6c0d
--- /dev/null
+++ b/scripts/sync-orama.mjs
@@ -0,0 +1,57 @@
+import process from 'node:process';
+import console from 'node:console';
+import { URL } from 'node:url';
+import { OramaCloud } from '@orama/core';
+import { getAllDocuments } from './orama-documents.mjs';
+
+try {
+  process.loadEnvFile(new URL('../.env.local', import.meta.url));
+} catch (error) {
+  console.error('Error loading .env.local file:', error);
+}
+/**
+ * The default batch size to use when syncing Orama Cloud
+ */
+const ORAMA_SYNC_BATCH_SIZE = 250;
+
+// The following follows the instructions at https://docs.orama.com/cloud/data-sources/custom-integrations/webhooks
+const documents = await getAllDocuments('en');
+console.log(`Syncing ${documents.length} documents to Orama Cloud index`);
+
+const orama = new OramaCloud({
+  projectId: process.env.PUBLIC_ORAMA_PROJECT_ID || '',
+  apiKey: process.env.PRIVATE_ORAMA_API_KEY || '',
+});
+
+const datasource = orama.dataSource(process.env.PUBLIC_ORAMA_DATASOURCE_ID || '');
+// Create a temporary index to perform the insertions
+const temporary = await datasource.createTemporaryIndex();
+
+// Orama allows to send several documents at once, so we batch them in groups of 50.
+// This is not strictly necessary, but it makes the process faster.
+const runUpdate = async () => {
+  const batchSize = ORAMA_SYNC_BATCH_SIZE;
+  const batches = [];
+
+  for (let i = 0; i < documents.length; i += batchSize) {
+    batches.push(documents.slice(i, i + batchSize));
+  }
+
+  console.log(`Sending ${batches.length} batches of ${batchSize} documents`);
+
+  for (const batch of batches) {
+    await temporary.insertDocuments(batch);
+  }
+
+  // Once all documents are inserted into the temporary index, we swap it with the live one atomically.
+  await temporary.swap();
+};
+
+// Now we proceed to call the APIs in order.
+// The previous implementation used to empty the index before inserting new documents
+// to remove documents that are no longer in the source.
+// The new API from @orama/core might have a different approach for full sync.
+// Based on the provided examples, we are now only running the update.
+await runUpdate();
+
+console.log('Orama Cloud sync completed successfully!');
diff --git a/sitemap.xml b/sitemap.xml
deleted file mode 100644
index 8a12ff9062..0000000000
--- a/sitemap.xml
+++ /dev/null
@@ -1,65 +0,0 @@
----
-layout: null
-sitemap: false
----
-<?xml version="1.0" encoding="UTF-8"?>
-<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">
-{% for lang in site.data.languages %}
-  <url>
-    {% if lang.code == 'en' %}
-    <loc>{{site.url}}</loc>
-    {% else %}
-    <loc>{{site.url}}/{{ lang.code }}/</loc>
-    {% endif %}
-    <xhtml:link rel="alternate" hreflang="x-default" href="{{ site.url }}" />
-    {% for alt_lang in site.data.languages %}
-      {% if alt_lang.code == 'en' %}
-    <xhtml:link rel="alternate" hreflang="en" href="{{ site.url }}" />
-      {% else %}
-    <xhtml:link rel="alternate" hreflang="{{ alt_lang.code }}" href="{{ site.url }}/{{ alt_lang.code }}/" />
-      {% endif %}
-    {% endfor %}
-  </url>
-{% endfor %}
-{% for page in site.html_pages %}
-  {% assign clean_url = page.url | split: '/' | slice: 2,  page.url.size | join: '/' %}
-    {% if clean_url.size > 0 %}
-    {% if page.layout != 404 and page.sitemap != false %}
-  <url>
-    <loc>{{site.url}}{{ page.url}}</loc>
-    <xhtml:link rel="alternate" hreflang="x-default" href="{{ site.url }}/en/{{ clean_url }}" />
-    {% for lang in site.data.languages %}
-    <xhtml:link rel="alternate" hreflang="{{ lang.code }}" href="{{ site.url }}/{{ lang.code }}/{{ clean_url }}" />
-    {% endfor %}
-  </url>
-    {% endif %}
-    {% endif %}
-{% endfor %}
-  <url>
-      <loc>https://expressjs.com/en/changelog/</loc>
-  </url>
-{% for post in site.posts %}
-  <url>
-    <loc>{{site.url}}{{post.url}}</loc>
-    <lastmod>{{ post.date | date_to_xmlschema }}</lastmod>
-  </url>
-{% endfor %}
-  <url>
-    <loc>https://nodejs.org/en/</loc>
-  </url>
-  <url>
-    <loc>https://openjsf.org/</loc>
-  </url>
-  <url>
-    <loc>https://terms-of-use.openjsf.org/</loc>
-  </url>
-  <url>
-    <loc>https://privacy-policy.openjsf.org/</loc>
-  </url>
-  <url>
-    <loc>https://github.com/expressjs/express/blob/master/Code-Of-Conduct.md</loc>
-  </url>
-  <url>
-    <loc>https://trademark-policy.openjsf.org/</loc>
-  </url>
-</urlset>
\ No newline at end of file
diff --git a/src/components/patterns/AnnouncementBar/AnnouncementBar.astro b/src/components/patterns/AnnouncementBar/AnnouncementBar.astro
new file mode 100644
index 0000000000..b8cbfce1c1
--- /dev/null
+++ b/src/components/patterns/AnnouncementBar/AnnouncementBar.astro
@@ -0,0 +1,82 @@
+---
+/**
+ * AnnouncementBar Component
+ *
+ * Displays a banner based on the announcement configuration.
+ * If `src/config/announcement.json` has a title, it shows the custom announcement.
+ * Otherwise, it falls back to the latest blog post (visible for 1 month after publication).
+ *
+ * Configuration is managed via `src/config/announcement.json`.
+ */
+import { Banner } from '@components/patterns';
+import { BodyMd } from '@components/primitives';
+import { getCollection } from 'astro:content';
+import { getLangFromUrl, useTranslations } from '@i18n/utils';
+import announcement from '@/config/announcement.json';
+
+type BannerVariant = 'info' | 'warning';
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+const useCustom = !!announcement.title;
+
+function getLatestBlog() {
+  return getCollection('blog').then((posts) => {
+    const sorted = posts
+      .filter((post) => post.id !== 'write-post')
+      .sort((a, b) => {
+        const aFile = a.id.split('/').pop() ?? '';
+        const bFile = b.id.split('/').pop() ?? '';
+        return bFile.localeCompare(aFile);
+      });
+    return sorted[0] ?? null;
+  });
+}
+
+const latestPost = !useCustom ? await getLatestBlog() : null;
+
+function getPostDate(id: string) {
+  const filename = id.split('/').pop() ?? id;
+  return filename.substring(0, 10);
+}
+
+const blogSlug = latestPost ? latestPost.id.split('/').pop() : '';
+const blogDate = latestPost ? getPostDate(latestPost.id) : '';
+const blogTitle = latestPost?.data.title ?? '';
+const blogDescription = latestPost?.data.description ?? '';
+const blogVariant: BannerVariant = latestPost?.data.tags?.includes('security') ? 'warning' : 'info';
+
+// Blog banner expires 1 month after publication date
+const blogStartDate = blogDate || undefined;
+const blogEndDate = blogDate
+  ? (() => {
+      const d = new Date(blogDate);
+      d.setMonth(d.getMonth() + 1);
+      return d.toISOString().substring(0, 10);
+    })()
+  : undefined;
+---
+
+{
+  useCustom ? (
+    <Banner
+      variant={(announcement.variant as BannerVariant) || 'info'}
+      startDate={announcement.startDate || undefined}
+      endDate={announcement.endDate || undefined}
+      title={announcement.title}
+    >
+      <BodyMd vMargin={false}>
+        {announcement.description}{' '}
+        {announcement.link && <a href={announcement.link}>{t('announcement.readMore')}</a>}
+      </BodyMd>
+    </Banner>
+  ) : latestPost ? (
+    <Banner variant={blogVariant} startDate={blogStartDate} endDate={blogEndDate} title={blogTitle}>
+      <BodyMd vMargin={false}>
+        {/* Trailing space inside template literal to prevent Prettier from stripping it */}
+        {`${blogDescription} `}
+        <a href={`/${lang}/blog/${blogSlug}`}>{t('announcement.checkLatestBlog')}</a>
+      </BodyMd>
+    </Banner>
+  ) : null
+}
diff --git a/src/components/patterns/AnnouncementBar/index.ts b/src/components/patterns/AnnouncementBar/index.ts
new file mode 100644
index 0000000000..da47aa5d7a
--- /dev/null
+++ b/src/components/patterns/AnnouncementBar/index.ts
@@ -0,0 +1 @@
+export { default as AnnouncementBar } from './AnnouncementBar.astro';
diff --git a/src/components/patterns/Banner/Banner.astro b/src/components/patterns/Banner/Banner.astro
new file mode 100644
index 0000000000..12edb5e01b
--- /dev/null
+++ b/src/components/patterns/Banner/Banner.astro
@@ -0,0 +1,71 @@
+---
+/**
+ * Banner Component
+ *
+ * A full-width notification banner displayed at the top of the page.
+ * Visibility is controlled server-side via optional date range props.
+ * When dismissible, the closed state is persisted in localStorage.
+ *
+ * @example
+ * <Banner id="v5-release" variant="info" startDate="2024-01-01" endDate="2024-06-01" dismissible>
+ *   <strong>Express v5 is out!</strong> <a href="/changelog">Read the changelog →</a>
+ * </Banner>
+ */
+import { Body, Container, Flex } from '@/components/primitives';
+import './Banner.css';
+import type { BannerProps } from './types';
+import { Icon } from 'astro-icon/components';
+
+type Props = BannerProps;
+
+const { id, variant = 'info', dismissible = false, title, startDate, endDate } = Astro.props;
+
+const now = new Date();
+const start = startDate ? new Date(startDate) : null;
+const end = endDate ? new Date(endDate) : null;
+const isActive = (!start || now >= start) && (!end || now <= end);
+---
+
+{
+  isActive && (
+    <div
+      class:list={['banner', `banner--${variant}`]}
+      data-banner-id={id ?? undefined}
+      data-dismissible={dismissible}
+      role="alert"
+    >
+      <Container>
+        <Flex align="center" gap="2">
+          <span class="banner__icon" aria-hidden="true">
+            {variant === 'info' ? (
+              <Icon name="fluent:info-16-regular" size="20" />
+            ) : (
+              <Icon name="fluent:warning-16-regular" size="20" />
+            )}
+          </span>
+          <Body as="h3" vMargin={false} weight="bold">
+            {title}
+          </Body>
+        </Flex>
+        <slot />
+      </Container>
+      {dismissible && (
+        <button class="banner__dismiss" aria-label="Dismiss banner">
+          <Icon name="fluent:dismiss-16-regular" size="16" />
+        </button>
+      )}
+    </div>
+  )
+}
+
+<script>
+  document.querySelectorAll<HTMLElement>('.banner').forEach((banner) => {
+    const bannerId = banner.dataset.bannerId;
+    if (banner.dataset.dismissible !== 'true') return;
+
+    banner.querySelector('.banner__dismiss')?.addEventListener('click', () => {
+      localStorage.setItem(`banner-dismissed-${bannerId}`, 'true');
+      banner.style.display = 'none';
+    });
+  });
+</script>
diff --git a/src/components/patterns/Banner/Banner.css b/src/components/patterns/Banner/Banner.css
new file mode 100644
index 0000000000..cd44ffc47b
--- /dev/null
+++ b/src/components/patterns/Banner/Banner.css
@@ -0,0 +1,49 @@
+@layer patterns {
+  .banner {
+    width: 100%;
+    padding: var(--space-4) 0;
+    border-bottom: var(--border-width-1) solid;
+    position: relative;
+  }
+
+  .banner--info {
+    background-color: var(--color-bg-info);
+    border-color: var(--color-border-info);
+    color: var(--color-text-info);
+  }
+
+  .banner--warning {
+    background-color: var(--color-bg-warning);
+    border-color: var(--color-border-warning);
+    color: var(--color-text-warning);
+  }
+
+  .banner__icon {
+    margin: 0;
+  }
+
+  .banner__dismiss {
+    display: flex;
+    align-items: center;
+    justify-content: center;
+    background: none;
+    border: none;
+    cursor: pointer;
+    padding: var(--space-1);
+    color: inherit;
+    border-radius: var(--radius-base);
+    flex-shrink: 0;
+    position: absolute;
+    top: var(--space-4);
+    right: var(--space-4);
+
+    &:hover {
+      background-color: light-dark(oklch(0% 0 0 / 0.08), oklch(100% 0 0 / 0.08));
+    }
+
+    &:focus-visible {
+      outline: 2px solid var(--color-focus-ring);
+      outline-offset: 2px;
+    }
+  }
+}
diff --git a/src/components/patterns/Banner/index.ts b/src/components/patterns/Banner/index.ts
new file mode 100644
index 0000000000..95f4f8b315
--- /dev/null
+++ b/src/components/patterns/Banner/index.ts
@@ -0,0 +1,2 @@
+export { default as Banner } from './Banner.astro';
+export type { BannerProps } from './types';
diff --git a/src/components/patterns/Banner/types.ts b/src/components/patterns/Banner/types.ts
new file mode 100644
index 0000000000..6b2bffb418
--- /dev/null
+++ b/src/components/patterns/Banner/types.ts
@@ -0,0 +1,49 @@
+interface BannerBaseProps {
+  /**
+   * Visual style of the banner.
+   * @default 'info'
+   */
+  variant?: 'info' | 'warning';
+
+  /**
+   * Title of the banner.
+   * Displayed prominently at the start of the banner.
+   */
+  title: string;
+}
+
+interface DismissibleBannerProps extends BannerBaseProps {
+  /**
+   * Whether the user can dismiss (close) the banner.
+   * Dismissal state is persisted in localStorage so the banner stays hidden across sessions.
+   */
+  dismissible: true;
+
+  /**
+   * Unique identifier for this banner.
+   * Used as the HTML `id` and as the localStorage key for persisting dismissal state.
+   * Required when `dismissible` is true.
+   */
+  id: string;
+}
+
+interface NonDismissibleBannerProps extends BannerBaseProps {
+  dismissible?: false;
+  id?: never;
+}
+
+export type BannerProps = (DismissibleBannerProps | NonDismissibleBannerProps) & {
+  /**
+   * ISO date string or Date object.
+   * The banner will not be displayed before this date.
+   * Omit to show the banner immediately.
+   */
+  startDate?: Date | string;
+
+  /**
+   * ISO date string or Date object.
+   * The banner will not be displayed after this date.
+   * Omit to show the banner indefinitely.
+   */
+  endDate?: Date | string;
+};
diff --git a/src/components/patterns/Breadcrumbs/Breadcrumbs.astro b/src/components/patterns/Breadcrumbs/Breadcrumbs.astro
new file mode 100644
index 0000000000..49830532d7
--- /dev/null
+++ b/src/components/patterns/Breadcrumbs/Breadcrumbs.astro
@@ -0,0 +1,68 @@
+---
+/**
+ * Breadcrumbs Component
+ * Renders a breadcrumb navigation based on provided items
+ */
+import { Body } from '@components/primitives';
+import { Icon } from 'astro-icon/components';
+import type { BreadcrumbItem } from '@utils/content';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+import './Breadcrumbs.css';
+
+interface Props {
+  items: BreadcrumbItem[];
+}
+
+const { items } = Astro.props;
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+<nav aria-label={t('nav.breadcrumb')}>
+  <ol class="breadcrumbs">
+    <li class="flex items-center gap-3">
+      <Body
+        vMargin={false}
+        as="a"
+        href={`/${lang}`}
+        class="breadcrumb-link"
+        aria-label={t('nav.home')}
+      >
+        <Icon name="fluent:home-empty-20-regular" />
+      </Body>
+      {items.length > 0 && <Icon name="fluent:chevron-right-28-regular" aria-hidden="true" />}
+    </li>
+    {
+      items.map((item, index) => (
+        <li class="flex items-center gap-3">
+          {item.href ? (
+            <Body vMargin={false} as="a" href={item.href} class="breadcrumb-link">
+              {item.icon && (
+                <Icon
+                  name={item.icon}
+                  aria-hidden={item.label ? 'true' : undefined}
+                  aria-label={!item.label ? item.ariaLabel : undefined}
+                />
+              )}
+              {item.label}
+            </Body>
+          ) : (
+            <Body vMargin={false} class="breadcrumb-item">
+              {item.icon && (
+                <Icon
+                  name={item.icon}
+                  aria-hidden={item.label ? 'true' : undefined}
+                  aria-label={!item.label ? item.ariaLabel : undefined}
+                />
+              )}
+              {item.label}
+            </Body>
+          )}
+          {index < items.length - 1 && (
+            <Icon name="fluent:chevron-right-28-regular" aria-hidden="true" />
+          )}
+        </li>
+      ))
+    }
+  </ol>
+</nav>
diff --git a/src/components/patterns/Breadcrumbs/Breadcrumbs.css b/src/components/patterns/Breadcrumbs/Breadcrumbs.css
new file mode 100644
index 0000000000..e437f402a0
--- /dev/null
+++ b/src/components/patterns/Breadcrumbs/Breadcrumbs.css
@@ -0,0 +1,58 @@
+@layer patterns {
+  .breadcrumbs {
+    display: flex;
+    gap: var(--space-3);
+    align-items: center;
+    padding: 0;
+    margin: 0;
+    list-style: none;
+    flex-wrap: wrap;
+    row-gap: var(--space-2);
+
+    @media (--xs-only) {
+      gap: var(--space-1);
+    }
+
+    & li {
+      display: flex;
+      align-items: center;
+      gap: var(--space-3);
+      flex-shrink: 0;
+
+      @media (--xs-only) {
+        gap: var(--space-1);
+      }
+    }
+
+    & svg {
+      flex-shrink: 0;
+    }
+  }
+  .breadcrumb-link {
+    display: inline-flex;
+    align-items: center;
+    gap: var(--space-1.5);
+    color: var(--color-text-primary);
+    text-decoration: underline;
+    text-underline-offset: 0.5rem;
+    flex-shrink: 0;
+
+    &:hover {
+      opacity: 0.8;
+    }
+
+    @media (--xs-only) {
+      font-size: var(--font-size-sm);
+      gap: var(--space-1);
+    }
+  }
+
+  .breadcrumb-item {
+    color: var(--color-text-primary);
+    flex-shrink: 0;
+
+    @media (--xs-only) {
+      font-size: var(--font-size-sm);
+    }
+  }
+}
diff --git a/src/components/patterns/CardList/CardList.astro b/src/components/patterns/CardList/CardList.astro
new file mode 100644
index 0000000000..a879154f47
--- /dev/null
+++ b/src/components/patterns/CardList/CardList.astro
@@ -0,0 +1,60 @@
+---
+/**
+ * CardList Pattern Component
+ *
+ * A responsive cards list built on top of the Grid primitive.
+ * Add cards (or card links) through the default slot.
+ */
+
+import './CardList.css';
+import type { HTMLAttributes } from 'astro/types';
+import { Grid } from '@/components/primitives';
+import type { GapSize, ColSpan } from '@/components/primitives/Grid/types';
+
+interface Props extends HTMLAttributes<'div'> {
+  /** Gap between items */
+  gap?: GapSize;
+  /** Vertical gap override */
+  rowGap?: GapSize;
+  /** Horizontal gap override */
+  columnGap?: GapSize;
+  /** Columns span per item on mobile */
+  itemXs?: ColSpan;
+  /** Columns span per item on tablet */
+  itemMd?: ColSpan;
+  /** Columns span per item on desktop */
+  itemLg?: ColSpan;
+}
+
+const {
+  gap = '4',
+  rowGap,
+  columnGap,
+  itemXs = 12,
+  itemMd = 6,
+  itemLg = 4,
+  class: className,
+  style,
+  ...rest
+} = Astro.props;
+
+const responsiveStyle = [
+  `--card-list-item-xs: ${itemXs}`,
+  `--card-list-item-md: ${itemMd}`,
+  `--card-list-item-lg: ${itemLg}`,
+  style,
+]
+  .filter(Boolean)
+  .join('; ');
+---
+
+<Grid
+  gap={gap}
+  rowGap={rowGap}
+  columnGap={columnGap}
+  class:list={['card-list', className]}
+  style={responsiveStyle}
+  {...rest}
+>
+  <slot />
+</Grid>
diff --git a/src/components/patterns/CardList/CardList.css b/src/components/patterns/CardList/CardList.css
new file mode 100644
index 0000000000..8a3762b229
--- /dev/null
+++ b/src/components/patterns/CardList/CardList.css
@@ -0,0 +1,32 @@
+@layer patterns {
+  .card-list > * {
+    grid-column: span var(--card-list-item-xs, 12);
+    display: flex;
+  }
+
+  .card-list > * > .card {
+    flex: 1;
+    height: 100%;
+  }
+
+  .card-list > a,
+  .card-list > a:visited,
+  .card-list > a:hover,
+  .card-list > a:active {
+    color: inherit;
+    text-decoration: none;
+  }
+
+  @media (--md-only) {
+    .card-list > * {
+      grid-column: span var(--card-list-item-md, var(--card-list-item-xs, 12));
+    }
+  }
+
+  @media (--lg-up) {
+    .card-list > * {
+      grid-column: span
+        var(--card-list-item-lg, var(--card-list-item-md, var(--card-list-item-xs, 12)));
+    }
+  }
+}
diff --git a/src/components/patterns/CardList/index.ts b/src/components/patterns/CardList/index.ts
new file mode 100644
index 0000000000..a79c6f9776
--- /dev/null
+++ b/src/components/patterns/CardList/index.ts
@@ -0,0 +1 @@
+export { default as CardList } from './CardList.astro';
diff --git a/src/components/patterns/DocBottomNav/DocBottomNav.astro b/src/components/patterns/DocBottomNav/DocBottomNav.astro
new file mode 100644
index 0000000000..4d233c4289
--- /dev/null
+++ b/src/components/patterns/DocBottomNav/DocBottomNav.astro
@@ -0,0 +1,61 @@
+---
+/**
+ * DocBottomNav Pattern Component
+ *
+ * Renders previous and next navigation links for documentation pages.
+ */
+import { Button } from '@components/primitives';
+import { Icon } from 'astro-icon/components';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+import type { AdjacentPage } from '@utils/content';
+import './DocBottomNav.css';
+interface Props {
+  prev?: AdjacentPage | null;
+  next?: AdjacentPage | null;
+}
+const { prev, next } = Astro.props;
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+{
+  (prev || next) && (
+    <nav class="doc-nav" aria-label={t('doc.pageNavigation')}>
+      {prev ? (
+        <Button
+          as="a"
+          variant="secondary"
+          ghost
+          href={prev.href}
+          class="doc-nav__link doc-nav__link--prev"
+        >
+          <Icon slot="left" name="fluent:arrow-left-20-filled" aria-hidden="true" />
+          <span class="doc-nav__meta">
+            <span class="doc-nav__direction">{t('doc.previousPage')}</span>
+            <span class="doc-nav__title">{t(prev.label)}</span>
+          </span>
+        </Button>
+      ) : (
+        <span />
+      )}
+
+      {next ? (
+        <Button
+          as="a"
+          variant="secondary"
+          ghost
+          href={next.href}
+          class="doc-nav__link doc-nav__link--next"
+        >
+          <span class="doc-nav__meta">
+            <span class="doc-nav__direction">{t('doc.nextPage')}</span>
+            <span class="doc-nav__title">{t(next.label)}</span>
+          </span>
+          <Icon slot="right" name="fluent:arrow-right-20-filled" aria-hidden="true" />
+        </Button>
+      ) : (
+        <span />
+      )}
+    </nav>
+  )
+}
diff --git a/src/components/patterns/DocBottomNav/DocBottomNav.css b/src/components/patterns/DocBottomNav/DocBottomNav.css
new file mode 100644
index 0000000000..ea09543826
--- /dev/null
+++ b/src/components/patterns/DocBottomNav/DocBottomNav.css
@@ -0,0 +1,32 @@
+@layer patterns {
+  .doc-nav {
+    display: flex;
+    justify-content: space-between;
+    gap: var(--space-4);
+    margin-top: var(--space-8);
+    padding-top: var(--space-6);
+    border-top: 1px solid var(--color-border-secondary);
+  }
+
+  .doc-nav__link--next {
+    margin-left: auto;
+    text-align: right;
+  }
+
+  .doc-nav__meta {
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-1);
+  }
+
+  .doc-nav__direction {
+    font-size: var(--text-xs);
+    color: var(--color-text-secondary);
+    font-weight: 500;
+  }
+
+  .doc-nav__title {
+    font-size: var(--text-sm);
+    font-weight: 600;
+  }
+}
diff --git a/src/components/patterns/Features/Features.astro b/src/components/patterns/Features/Features.astro
new file mode 100644
index 0000000000..f63cac2a4c
--- /dev/null
+++ b/src/components/patterns/Features/Features.astro
@@ -0,0 +1,42 @@
+---
+/**
+ * Features Pattern Component
+ *
+ * Displays a section title alongside a grid of feature cards.
+ *
+ * Layout:
+ * - Mobile:  title above cards, 1 per row
+ * - Tablet:  title above cards, 2 per row
+ * - Desktop: title in 4/12 columns · cards in 8/12 columns, 2 per row
+ *
+ * @example
+ * <Features title="Why Express?">
+ *   <Card title="Performance" body="Minimal overhead on top of Node.js." />
+ *   <Card title="Routing"     body="Robust, expressive routing API." />
+ * </Features>
+ */
+import './Features.css';
+import type { HTMLAttributes } from 'astro/types';
+import { H2, Container, Grid, Col } from '@/components/primitives';
+
+interface Props extends HTMLAttributes<'section'> {
+  title: string;
+}
+
+const { title, class: className, ...rest } = Astro.props;
+---
+
+<section class:list={['features', className]} data-testid="features-section" {...rest}>
+  <Container>
+    <Grid>
+      <Col xs={12} lg={4} class="features__header">
+        <H2>{title}</H2>
+      </Col>
+      <Col xs={12} lg={8}>
+        <Grid gap="0" class="features__cards">
+          <slot />
+        </Grid>
+      </Col>
+    </Grid>
+  </Container>
+</section>
diff --git a/src/components/patterns/Features/Features.css b/src/components/patterns/Features/Features.css
new file mode 100644
index 0000000000..5c9ebad062
--- /dev/null
+++ b/src/components/patterns/Features/Features.css
@@ -0,0 +1,55 @@
+@layer patterns {
+  .features {
+    padding: var(--space-8) 0;
+
+    @media (--md-up) {
+      padding: var(--space-12) 0;
+    }
+  }
+
+  .features__header {
+    padding-bottom: var(--space-8);
+
+    @media (--lg-up) {
+      align-self: start;
+      padding-bottom: 0;
+      padding-right: var(--space-8);
+    }
+  }
+
+  .features__cards {
+    overflow: hidden;
+    align-items: stretch;
+    border-radius: var(--radius-card);
+    border: var(--border-width-1) solid var(--color-border-secondary);
+  }
+
+  .features__card-col {
+    .card {
+      flex: 1;
+      height: 100%;
+      border-radius: 0;
+      border-top: 0;
+      border-right: 0;
+      border-left: 0;
+    }
+
+    &:last-child .card {
+      border-bottom: 0;
+    }
+
+    @media (--md-up) {
+      &:nth-child(2n) {
+        .card {
+          border-left: var(--border-width-1) solid var(--color-border-secondary);
+        }
+      }
+
+      &:nth-last-child(-n + 2) {
+        .card {
+          border-bottom: 0;
+        }
+      }
+    }
+  }
+}
diff --git a/src/components/patterns/Features/index.ts b/src/components/patterns/Features/index.ts
new file mode 100644
index 0000000000..90a026f8ef
--- /dev/null
+++ b/src/components/patterns/Features/index.ts
@@ -0,0 +1 @@
+export { default as Features } from './Features.astro';
diff --git a/src/components/patterns/Footer/Footer.astro b/src/components/patterns/Footer/Footer.astro
new file mode 100644
index 0000000000..62b8fa30c1
--- /dev/null
+++ b/src/components/patterns/Footer/Footer.astro
@@ -0,0 +1,191 @@
+---
+/**
+ * Footer Component
+ *
+ * Main site footer with copyright and additional information
+ */
+import './Footer.css';
+import { Icon } from 'astro-icon/components';
+import { BodyMd, Button, Col, Container, Grid } from '@/components/primitives';
+---
+
+<footer class="footer" data-testid="footer">
+  <div class="footer-top">
+    <Container>
+      <BodyMd color="secondary" center as="p">
+        Copyright <a href="https://openjsf.org">OpenJS Foundation</a> and Express.js contributors. All
+        rights reserved. The <a href="https://openjsf.org">OpenJS Foundation</a> has registered trademarks
+        and uses trademarks. For a list of trademarks of the <a href="https://openjsf.org"
+          >OpenJS Foundation</a
+        >, please see our <a href="https://trademark-policy.openjsf.org">Trademark Policy</a> and <a
+          href="https://trademark-list.openjsf.org">Trademark List</a
+        >. Trademarks and logos not indicated on the <a href="https://trademark-list.openjsf.org"
+          >list of OpenJS Foundation trademarks</a
+        > are trademarks&trade; or registered&reg; trademarks of their respective holders. Use of them
+        does not imply any affiliation with or endorsement by them.
+      </BodyMd>
+      <ul class="footer__links">
+        <li><a href="https://openjsf.org">The OpenJS Foundation</a></li>
+        <li>
+          <a href="https://ai-coding-assistants-policy.openjsf.org/">AI Coding Assistants Policy</a>
+        </li>
+        <li><a href="https://bylaws.openjsf.org">Bylaws</a></li>
+        <li><a href="https://code-of-conduct.openjsf.org">Code of Conduct</a></li>
+        <li><a href="https://www.linuxfoundation.org/cookies">Cookie Policy</a></li>
+        <li><a href="https://privacy-policy.openjsf.org">Privacy Policy</a></li>
+        <li><a href="https://github.com/expressjs/express/security/policy">Security Policy</a></li>
+        <li><a href="https://terms-of-use.openjsf.org">Terms of Use</a></li>
+        <li><a href="https://trademark-list.openjsf.org">Trademark List</a></li>
+        <li><a href="https://trademark-policy.openjsf.org">Trademark Policy</a></li>
+      </ul>
+    </Container>
+  </div>
+  <div class="footer-bottom">
+    <Container>
+      <Grid gap="2" align="center">
+        <Col xs={12} md={6} lg={6}>
+          <ul class="footer__logo" aria-label="Partner logos">
+            <li>
+              <a
+                href="https://openjsf.org"
+                aria-label="Hosted by OpenJS Foundation"
+                target="_blank"
+              >
+                <img
+                  class="footer-logo-light"
+                  src="/openjs-logo-black.svg"
+                  alt="OpenJS Foundation Logo"
+                  width="80"
+                  height="24"
+                  loading="lazy"
+                />
+                <img
+                  class="footer-logo-dark"
+                  src="/openjs-logo-white.svg"
+                  alt="OpenJS Foundation Logo"
+                  width="80"
+                  height="24"
+                  loading="lazy"
+                />
+              </a>
+            </li>
+            <li>
+              <a
+                href="https://www.netlify.com"
+                aria-label="Preview deployed by netlify"
+                target="_blank"
+              >
+                <img
+                  src="/netlify-logo.svg"
+                  alt="Netlify Logo"
+                  width="80"
+                  height="24"
+                  loading="lazy"
+                />
+              </a>
+            </li>
+          </ul>
+        </Col>
+        <Col xs={12} md={6} lg={6}>
+          <ul class="footer__socials" aria-label="Social links">
+            <li>
+              <Button
+                id="kawaiiToggle"
+                class="kawaii-toggle"
+                type="button"
+                aria-label="Toggle kawaii logo"
+                aria-pressed="false"
+                variant="secondary"
+                size="xs"
+                ghost
+                data-testid="kawaii-toggle"
+              >
+                Kawaii?
+              </Button>
+            </li>
+            <li>
+              <a
+                href="https://github.com/expressjs/express"
+                aria-label="expressjs on GitHub"
+                target="_blank"
+              >
+                <Icon name="github" />
+              </a>
+            </li>
+            <li>
+              <a
+                href="https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g"
+                aria-label="expressjs channel on Youtube"
+                target="_blank"
+              >
+                <Icon name="youtube" />
+              </a>
+            </li>
+            <li>
+              <a href="https://x.com/UseExpressJS" aria-label="follow expressjs on X account">
+                <Icon name="x" />
+              </a>
+            </li>
+            <li>
+              <a
+                href="https://slack-invite.openjsf.org"
+                aria-label="Join openjs foundation slack group"
+              >
+                <Icon name="slack" />
+              </a>
+            </li>
+            <li>
+              <a
+                href="https://opencollective.com/express"
+                aria-label="support expressjs on Open Collective"
+              >
+                <Icon name="open-collective" />
+              </a>
+            </li>
+            <li>
+              <a
+                href="https://bsky.app/profile/expressjs.bsky.social"
+                aria-label="follow expressjs on bluesky"
+              >
+                <Icon name="bsky" />
+              </a>
+            </li>
+            <li>
+              <a href="/feed.xml" aria-label="RSS Feed">
+                <Icon name="rss" />
+              </a>
+            </li>
+          </ul>
+        </Col>
+      </Grid>
+    </Container>
+  </div>
+</footer>
+
+<script is:inline>
+  const initKawaii = () => {
+    const toggle = document.getElementById('kawaiiToggle');
+    if (!toggle) return;
+
+    const getState = () => localStorage.getItem('kawaii') === 'true';
+
+    const applyState = (enabled) => {
+      document.documentElement.toggleAttribute('data-kawaii', enabled);
+      toggle.setAttribute('aria-pressed', String(enabled));
+
+      if (enabled) {
+        localStorage.setItem('kawaii', 'true');
+      } else {
+        localStorage.removeItem('kawaii');
+      }
+    };
+
+    applyState(getState());
+
+    toggle.addEventListener('click', () => {
+      applyState(!getState());
+    });
+  };
+
+  initKawaii();
+</script>
diff --git a/src/components/patterns/Footer/Footer.css b/src/components/patterns/Footer/Footer.css
new file mode 100644
index 0000000000..14804b7276
--- /dev/null
+++ b/src/components/patterns/Footer/Footer.css
@@ -0,0 +1,134 @@
+@layer patterns {
+  .footer {
+    background-color: var(--color-bg-primary);
+    text-align: center;
+    color: var(--color-text-secondary);
+    border-top: 1px solid var(--color-border-secondary);
+
+    a {
+      text-decoration: none;
+
+      &:hover {
+        text-decoration: underline;
+      }
+    }
+  }
+
+  .footer__links {
+    list-style: none;
+    padding: 0;
+    margin: var(--space-4) 0;
+
+    li {
+      display: inline;
+      margin: 0 var(--space-2);
+    }
+
+    a {
+      color: var(--color-text-secondary);
+      font-size: var(--font-size-sm);
+    }
+  }
+
+  .footer-top {
+    padding: var(--space-6) 0;
+  }
+
+  .footer-bottom {
+    background-color: var(--color-bg-secondary);
+    padding: var(--space-6) 0;
+  }
+
+  .footer__logo {
+    list-style: none;
+    padding: 0;
+    margin: 0;
+
+    @media (--xs-only) {
+      li {
+        display: block;
+        text-align: center;
+
+        a {
+          display: inline-block;
+          padding: var(--space-4) 0;
+        }
+      }
+    }
+
+    @media (--md-up) {
+      display: flex;
+      align-items: center;
+      gap: var(--space-8);
+    }
+  }
+
+  .footer__socials {
+    list-style: none;
+    padding: 0;
+    margin: 0;
+    display: flex;
+    align-items: center;
+    justify-content: center;
+    gap: var(--space-6);
+
+    li {
+      display: inline;
+    }
+
+    svg {
+      color: var(--color-icon-primary);
+    }
+
+    svg path {
+      fill: currentColor;
+    }
+
+    @media (--xs-only) {
+      padding: var(--space-4) 0 var(--space-6);
+    }
+
+    @media (--md-up) {
+      justify-content: right;
+      gap: var(--space-8);
+    }
+  }
+
+  .footer-logo-dark {
+    display: none;
+  }
+
+  @media (prefers-color-scheme: dark) {
+    .footer-logo-light {
+      display: none;
+    }
+
+    .footer-logo-dark {
+      display: block;
+    }
+  }
+
+  [data-theme='dark'] .footer-logo-light {
+    display: none;
+  }
+
+  [data-theme='dark'] .footer-logo-dark {
+    display: block;
+  }
+
+  [data-theme='light'] .footer-logo-light {
+    display: block;
+  }
+
+  [data-theme='light'] .footer-logo-dark {
+    display: none;
+  }
+
+  .kawaii-toggle {
+    font-size: var(--font-size-sm);
+  }
+
+  .kawaii-toggle[aria-pressed='true'] {
+    color: var(--color-link);
+  }
+}
diff --git a/src/components/patterns/Header/Header.astro b/src/components/patterns/Header/Header.astro
new file mode 100644
index 0000000000..b4983efc83
--- /dev/null
+++ b/src/components/patterns/Header/Header.astro
@@ -0,0 +1,78 @@
+---
+/**
+ * Header Component
+ *
+ * Main site header with logo and navigation menu
+ */
+import './Header.css';
+import { Image } from 'astro:assets';
+import { Icon } from 'astro-icon/components';
+import { Flex } from '@/components/primitives';
+import { ThemeSwitcher, SearchBox, LanguageSelect } from '@components/patterns';
+import { languagesArray } from '@/i18n/locales';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+const currentLang = getLangFromUrl(Astro.url);
+const t = useTranslations(currentLang);
+---
+
+<header class="header">
+  <Flex align="center" justify="between" gap="3">
+    <Flex align="center" justify="between" gap="4">
+      <button
+        id="menuToggle"
+        class="hamburger"
+        aria-label={t('nav.toggleMenu')}
+        aria-expanded="false"
+        aria-controls="sidebar"
+      >
+        <span class="hamburger-line"></span>
+        <span class="hamburger-line"></span>
+        <span class="hamburger-line"></span>
+      </button>
+      <a href={`/${currentLang}/`} class="logo-link" aria-label={t('nav.home')}>
+        <Image
+          src="/images/logos/express-kawaii.webp"
+          alt="Express.js kawaii logo"
+          class="logo logo-kawaii"
+          width={40}
+          height={40}
+        />
+        <Icon name="logo-dark" class="logo logo-dark logo-default" />
+        <Icon name="logo-light" class="logo logo-light logo-default" />
+      </a>
+    </Flex>
+    <Flex align="center" justify="center" gap="2">
+      <a href="#main-content" class="skip-link sr-only">Skip to content</a>
+      <SearchBox
+        lang={currentLang}
+        placeholder={t('search.placeholder')}
+        ariaLabel={t('search.ariaLabel')}
+        client:idle
+      />
+      <ThemeSwitcher showLabels={false} />
+      <LanguageSelect languages={languagesArray} currentLanguage={currentLang} />
+    </Flex>
+  </Flex>
+</header>
+
+<script>
+  const menuToggle = document.getElementById('menuToggle');
+
+  if (menuToggle) {
+    menuToggle.addEventListener('click', () => {
+      const isExpanded = menuToggle.getAttribute('aria-expanded') === 'true';
+      const newExpandedState = !isExpanded;
+
+      menuToggle.setAttribute('aria-expanded', String(newExpandedState));
+      menuToggle.classList.toggle('active');
+
+      document.dispatchEvent(new CustomEvent('sidebar:toggle'));
+    });
+
+    document.addEventListener('sidebar:closed', () => {
+      menuToggle.setAttribute('aria-expanded', 'false');
+      menuToggle.classList.remove('active');
+    });
+  }
+</script>
diff --git a/src/components/patterns/Header/Header.css b/src/components/patterns/Header/Header.css
new file mode 100644
index 0000000000..c6e64d7ac7
--- /dev/null
+++ b/src/components/patterns/Header/Header.css
@@ -0,0 +1,156 @@
+/**
+ * Header Styles
+ */
+
+@layer patterns {
+  .header {
+    background-color: var(--color-bg-secondary);
+    position: sticky;
+    top: 0;
+    padding: var(--space-3) var(--space-4);
+    z-index: var(--z-index-header);
+    border-bottom: 1px solid var(--color-border-secondary);
+
+    @media (--md-up) {
+      background-color: var(--color-bg-primary);
+      position: fixed;
+      top: 0;
+      left: 0;
+      right: 0;
+
+      .logo-link {
+        display: none;
+      }
+    }
+  }
+
+  .skip-link {
+    color: var(--color-text-primary);
+
+    &:focus {
+      position: relative;
+      padding: var(--space-2) var(--space-4);
+      background-color: var(--color-bg-tertiary);
+      text-decoration: none;
+      border-radius: var(--radius-md);
+      outline: 1px solid var(--color-focus-ring);
+      outline-offset: -2px;
+      border: 0;
+      margin: 0;
+      overflow: visible;
+      clip: auto;
+      white-space: nowrap;
+      width: auto;
+      height: auto;
+      font-size: var(--font-size-sm);
+      line-height: var(--line-height-snug);
+    }
+  }
+
+  .logo-link {
+    display: flex;
+    align-items: center;
+    text-decoration: none;
+    border-radius: var(--radius-sm);
+  }
+
+  .logo {
+    height: var(--size-5);
+    width: auto;
+
+    @media (--md-up) {
+      height: var(--size-6);
+    }
+  }
+
+  .logo-kawaii {
+    display: none;
+    height: var(--size-8);
+    width: auto;
+
+    @media (--md-up) {
+      height: var(--size-10);
+    }
+  }
+
+  :root[data-kawaii] .logo-kawaii {
+    display: block;
+  }
+
+  :root[data-kawaii] .logo-default {
+    display: none;
+  }
+
+  :root[data-theme='light'] .logo-light,
+  :root:not([data-theme]) .logo-light {
+    display: none;
+  }
+
+  :root[data-theme='dark'] .logo-dark {
+    display: none;
+  }
+
+  .hamburger {
+    width: var(--size-9);
+    height: var(--size-9);
+    background: none;
+    border: none;
+    cursor: pointer;
+    position: relative;
+
+    @media (--md-up) {
+      display: none;
+    }
+  }
+
+  .hamburger-line {
+    width: 50%;
+    height: var(--size-0-5);
+    margin: 0;
+    background-color: var(--color-icon-primary);
+    border-radius: var(--radius-full);
+    transition:
+      transform var(--duration-300) var(--ease-in-out),
+      opacity var(--duration-200) var(--ease-in-out);
+    position: absolute;
+    left: 50%;
+    top: 50%;
+    transform: translateX(-50%) translateY(-50%);
+  }
+
+  .hamburger-line:nth-child(1) {
+    transform: translateX(-50%) translateY(-0.6rem);
+  }
+
+  .hamburger-line:nth-child(2) {
+    transform: translateX(-50%) translateY(0);
+  }
+
+  .hamburger-line:nth-child(3) {
+    transform: translateX(-50%) translateY(0.6rem);
+  }
+
+  .hamburger.active .hamburger-line:nth-child(1) {
+    transform: translateX(-50%) translateY(0) rotate(45deg);
+  }
+
+  .hamburger.active .hamburger-line:nth-child(2) {
+    opacity: 0;
+    transform: translateX(-50%) translateX(-1rem);
+    display: none;
+  }
+
+  .hamburger.active .hamburger-line:nth-child(3) {
+    transform: translateX(-50%) translateY(0) rotate(-45deg);
+  }
+
+  @media (prefers-reduced-motion: reduce) {
+    .hamburger-line {
+      transition: none;
+    }
+
+    .logo-link {
+      transition: none;
+    }
+  }
+}
diff --git a/src/components/patterns/Hero/Hero.astro b/src/components/patterns/Hero/Hero.astro
new file mode 100644
index 0000000000..0a2374a68f
--- /dev/null
+++ b/src/components/patterns/Hero/Hero.astro
@@ -0,0 +1,142 @@
+---
+import './Hero.css';
+import { Code } from 'astro-expressive-code/components';
+import { Icon } from 'astro-icon/components';
+import { H1, Button, Container, Flex, BodyMd, Grid, Col } from '@/components/primitives';
+import { getEntry } from 'astro:content';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+import { Image } from 'astro:assets';
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+const expressPackage = await getEntry('npm', 'express');
+const EXPRESS_VERSION = expressPackage?.data.version ?? '5.x';
+const INSTALL_COMMAND = 'npm install express --save';
+const EXAMPLE_CODE = `const express = require('express')
+const app = express()
+const port = 3000
+
+app.get('/', (req, res) => {
+  res.send('Hello World!')
+})
+
+app.listen(port, () => {
+  console.log(\`Example app listening on port \${port}\`)
+})`;
+---
+
+<section class="hero">
+  <div class="hero__bg-container">
+    <canvas class="hero__canvas" aria-hidden="true"></canvas>
+    <div class="hero__video-overlay"></div>
+  </div>
+  <Container>
+    <div class="hero__content">
+      <Flex align="end" gap="4" data-testid="hero-brand">
+        <div class="hero__logo">
+          <Image
+            src="/images/logos/express-kawaii.webp"
+            alt={t('hero.kawaiiLogoAlt')}
+            class="hero__logo-kawaii"
+            width={400}
+            height={225}
+            loading="lazy"
+            data-testid="logo-kawaii"
+          />
+          <Icon
+            name="logo-express-black"
+            class="hero__logo-icon--dark hero__logo-default"
+            data-testid="logo-standard"
+          />
+          <Icon
+            name="logo-express-white"
+            class="hero__logo-icon--light hero__logo-default"
+            data-testid="logo-standard"
+          />
+        </div>
+        <BodyMd vMargin={false}>{EXPRESS_VERSION}</BodyMd>
+      </Flex>
+
+      <Grid>
+        <Col xs={12} lg={6} class="hero__text-content">
+          <H1 vMargin={false}>{t('hero.tagline')}</H1>
+          <div class="hero__cta">
+            <div class="hero__code" data-testid="install-command">
+              <Code code={INSTALL_COMMAND} lang="plaintext" />
+            </div>
+            <Button as="a" href="/en/5x/starter/installing" size="md" fullWidth>
+              {t('hero.getStarted')}
+              <Icon name="fluent:arrow-right-16-regular" size="16" />
+            </Button>
+          </div>
+        </Col>
+        <Col xs={12} lg={6}>
+          <div class="hero__code hero__example-code" data-testid="example-code">
+            <Code code={EXAMPLE_CODE} lang="js" />
+          </div>
+        </Col>
+      </Grid>
+    </div>
+  </Container>
+</section>
+
+<script>
+  /**
+   * Import immediately — module is small (~6KB) and shader compilation is async.
+   * initHeroWebGL renders the first frame during init (in resize()),
+   * so the arc appears as soon as shaders compile — no image fallback needed.
+   *
+   * Manages the WebGL background lifecycle.
+   * Consolidates IntersectionObserver, Visibility API, and Motion preferences
+   * into a single state machine to avoid conflicting play/pause calls.
+   */
+  import('./hero-background').then(({ initHeroWebGL }) => {
+    const canvas = document.querySelector<HTMLCanvasElement>('.hero__canvas');
+    if (!canvas) return;
+
+    const isMobile = window.matchMedia('(max-width: 768px)');
+    const motionQuery = window.matchMedia('(prefers-reduced-motion: reduce)');
+
+    initHeroWebGL(canvas, isMobile.matches || motionQuery.matches).then((bg) => {
+      if (!bg) return;
+
+      let isIntersecting = true;
+
+      function sync() {
+        // Only run the animation loop if:
+        // 1. Not on mobile (performance)
+        // 2. User hasn't requested reduced motion
+        // 3. Element is in/near the viewport
+        // 4. Tab is currently active
+        const shouldAnimate =
+          !isMobile.matches && !motionQuery.matches && isIntersecting && !document.hidden;
+
+        if (shouldAnimate) {
+          bg!.play();
+        } else {
+          bg!.pause();
+        }
+      }
+
+      // Lifecycle Listeners
+      const observer = new IntersectionObserver(
+        (entries) => {
+          isIntersecting = entries[0].isIntersecting;
+          sync();
+        },
+        { rootMargin: '80px' }
+      );
+      observer.observe(canvas);
+
+      document.addEventListener('visibilitychange', sync);
+      motionQuery.addEventListener('change', sync);
+      isMobile.addEventListener('change', sync);
+
+      // Initialization
+      // Trigger sync immediately so the background appears as soon as
+      // the WebGL context and shaders are ready.
+      sync();
+    });
+  });
+</script>
diff --git a/src/components/patterns/Hero/Hero.css b/src/components/patterns/Hero/Hero.css
new file mode 100644
index 0000000000..7bcedf6062
--- /dev/null
+++ b/src/components/patterns/Hero/Hero.css
@@ -0,0 +1,276 @@
+@layer patterns {
+  .hero {
+    position: relative;
+    padding: var(--space-12) 0;
+    background-color: var(--color-bg-primary);
+    overflow: hidden;
+
+    @media (--md-up) {
+      padding: var(--space-14) 0 var(--space-20);
+    }
+
+    @media (--lg-up) {
+      padding: var(--space-20) 0;
+    }
+  }
+
+  .hero__bg-container {
+    position: absolute;
+    top: 0;
+    left: 50%;
+    transform: translateX(-50%);
+    width: 100vw;
+    height: 100%;
+    z-index: 0;
+    overflow: hidden;
+  }
+
+  .hero__canvas {
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+  }
+
+  .hero__video-overlay {
+    position: absolute;
+    inset: 0;
+    z-index: 1;
+    pointer-events: none;
+    background: linear-gradient(
+      180deg,
+      rgba(255, 255, 255, 0.05) 0%,
+      rgba(255, 255, 255, 0.15) 40%,
+      rgba(255, 255, 255, 0.3) 70%,
+      var(--color-bg-primary) 100%
+    );
+    z-index: 1;
+  }
+
+  [data-theme='dark'] .hero__video-overlay {
+    background: linear-gradient(
+      180deg,
+      rgba(0, 0, 0, 0.3) 0%,
+      rgba(0, 0, 0, 0.5) 40%,
+      rgba(0, 0, 0, 0.7) 70%,
+      var(--color-bg-primary) 100%
+    );
+  }
+
+  @media (prefers-color-scheme: dark) {
+    .hero__video-overlay {
+      background: linear-gradient(
+        180deg,
+        rgba(0, 0, 0, 0.3) 0%,
+        rgba(0, 0, 0, 0.5) 40%,
+        rgba(0, 0, 0, 0.7) 70%,
+        var(--color-bg-primary) 100%
+      );
+    }
+
+    [data-theme='light'] .hero__video-overlay {
+      background: linear-gradient(
+        180deg,
+        rgba(255, 255, 255, 0.05) 0%,
+        rgba(255, 255, 255, 0.15) 40%,
+        rgba(255, 255, 255, 0.3) 70%,
+        var(--color-bg-primary) 100%
+      );
+    }
+  }
+
+  /* ================= CONTROLS ================= */
+
+  .hero__video-control {
+    position: absolute;
+    bottom: var(--space-0);
+    right: var(--space-12);
+    z-index: 2;
+
+    width: var(--size-8);
+    height: var(--size-8);
+
+    display: flex;
+    align-items: center;
+    justify-content: center;
+
+    border: 1px solid var(--color-border-secondary);
+    border-radius: var(--radius-full);
+    background: transparent;
+
+    color: var(--color-text-tertiary);
+    cursor: pointer;
+    transition: all 0.2s ease;
+  }
+
+  .hero__video-control:hover {
+    border-color: var(--color-border-primary);
+    color: var(--color-text-primary);
+    transform: scale(1.05);
+  }
+
+  .hero__video-control:focus-visible {
+    outline: 2px solid var(--color-focus);
+    outline-offset: 2px;
+    color: var(--color-text-primary);
+  }
+
+  .hero__video-control:active {
+    transform: scale(0.98);
+  }
+
+  .hero__video-control svg {
+    width: var(--size-3-5);
+    height: var(--size-3-5);
+  }
+
+  /* toggle icons */
+  .hero__video-control[data-state='playing'] .hero__video-control-play {
+    opacity: 0;
+    width: 0;
+  }
+
+  .hero__video-control[data-state='paused'] .hero__video-control-pause {
+    opacity: 0;
+    width: 0;
+  }
+
+  @media (--md-up) {
+    .hero__video-control {
+      bottom: var(--space-6);
+      right: var(--space-6);
+    }
+  }
+
+  /* ================= CONTENT ================= */
+
+  .hero__content {
+    position: relative;
+    z-index: 2;
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-8);
+
+    @media (--md-up) {
+      gap: var(--space-12);
+    }
+  }
+
+  .hero__text-content {
+    @media (--lg-up) {
+      padding-right: var(--space-10);
+    }
+  }
+
+  /* ================= LOGO ================= */
+
+  .hero__logo {
+    width: var(--size-36);
+  }
+
+  .hero__logo svg,
+  .hero__logo img {
+    width: 100%;
+    height: auto;
+  }
+
+  .hero__logo-kawaii {
+    display: none;
+  }
+
+  :root[data-kawaii] .hero__logo-kawaii {
+    display: block;
+  }
+
+  :root[data-kawaii] .hero__logo-default {
+    display: none !important;
+  }
+
+  @media (--md-up) {
+    .hero__logo {
+      width: var(--size-52);
+    }
+  }
+
+  .hero__logo-icon--dark {
+    display: block;
+  }
+
+  .hero__logo-icon--light {
+    display: none;
+  }
+
+  [data-theme='dark'] .hero__logo-icon--dark {
+    display: none;
+  }
+
+  [data-theme='dark'] .hero__logo-icon--light {
+    display: block;
+  }
+
+  @media (prefers-color-scheme: dark) {
+    .hero__logo-icon--dark {
+      display: none;
+    }
+
+    .hero__logo-icon--light {
+      display: block;
+    }
+
+    [data-theme='light'] .hero__logo-icon--dark {
+      display: block;
+    }
+
+    [data-theme='light'] .hero__logo-icon--light {
+      display: none;
+    }
+  }
+
+  /* ================= CTA ================= */
+
+  .hero__cta {
+    width: 100%;
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-4);
+    margin: var(--space-8) 0;
+
+    @media (--md-up) {
+      margin: var(--space-12) 0;
+      max-width: var(--size-96);
+    }
+  }
+}
+
+/* ================= CODE BLOCK ================= */
+
+.hero__code .expressive-code .frame pre {
+  backdrop-filter: blur(21px);
+}
+
+.hero__code .expressive-code figure {
+  box-shadow: none;
+}
+
+[data-theme='dark'] .hero__code .expressive-code .frame pre {
+  background-color: rgba(0, 0, 0, 0.62);
+}
+
+[data-theme='light'] .hero__code .expressive-code .frame pre {
+  background-color: color-mix(in srgb, var(--gray-950) 85%, transparent);
+}
+
+@media (prefers-color-scheme: dark) {
+  .hero__code .expressive-code .frame pre {
+    background-color: rgba(0, 0, 0, 0.62);
+  }
+
+  [data-theme='light'] .hero__code .expressive-code .frame pre {
+    background-color: color-mix(in srgb, var(--gray-950) 85%, transparent);
+  }
+}
+
+.hero__example-code .expressive-code .frame pre {
+  padding: var(--space-3);
+}
diff --git a/src/components/patterns/Hero/hero-background.ts b/src/components/patterns/Hero/hero-background.ts
new file mode 100644
index 0000000000..1b26e6f318
--- /dev/null
+++ b/src/components/patterns/Hero/hero-background.ts
@@ -0,0 +1,190 @@
+import vertexShader from './shaders/vertex.glsl?raw';
+import fragmentShader from './shaders/fragment.glsl?raw';
+
+/** Yields to the main thread so long tasks don't block rendering/input. */
+function yieldToMain(): Promise<void> {
+  const s = globalThis as unknown as { scheduler?: { yield?: () => Promise<void> } };
+  if (s.scheduler?.yield) return s.scheduler.yield();
+  return new Promise((r) => setTimeout(r, 0));
+}
+
+/**
+ * Polls until a shader/program is ready when KHR_parallel_shader_compile is
+ * available, yielding to the main thread between checks. Falls back to a
+ * single yield when the extension is absent.
+ */
+async function waitForCompilation(isReady: () => boolean) {
+  while (!isReady()) {
+    await yieldToMain();
+  }
+}
+
+/**
+ * Initializes the WebGL hero background on the given canvas.
+ *
+ * @param canvas - The canvas element to render into.
+ * @param reducedMotion - If true, freezes time at 0 (static frame).
+ * @returns Controller with play/pause, or null if WebGL is unavailable.
+ */
+export async function initHeroWebGL(canvas: HTMLCanvasElement, reducedMotion = false) {
+  // Attempt to get a WebGL context; return null if unsupported
+  const gl = canvas.getContext('webgl', { alpha: false, powerPreference: 'low-power' });
+  if (!gl) return null;
+
+  const parallelExt = gl.getExtension('KHR_parallel_shader_compile') as {
+    COMPLETION_STATUS_KHR: number;
+  } | null;
+
+  /** Checks the current color scheme (data-theme attribute or system preference). */
+  function isDark() {
+    const theme = document.documentElement.getAttribute('data-theme');
+    if (theme) return theme === 'dark';
+    return window.matchMedia('(prefers-color-scheme: dark)').matches;
+  }
+
+  // -- Immediate Clear (prevents flashing while compiling) --
+  const dark = isDark();
+  gl.clearColor(dark ? 0 : 1, dark ? 0 : 1, dark ? 0 : 1, 1);
+  gl.clear(gl.COLOR_BUFFER_BIT);
+
+  // -- Shader compilation (non-blocking) --
+
+  function compile(type: number, src: string) {
+    const s = gl!.createShader(type)!;
+    gl!.shaderSource(s, src);
+    gl!.compileShader(s);
+    return s;
+  }
+
+  // Kick off both compilations in parallel, then yield
+  const vs = compile(gl.VERTEX_SHADER, vertexShader);
+  const fs = compile(gl.FRAGMENT_SHADER, fragmentShader);
+
+  const kshr = parallelExt?.COMPLETION_STATUS_KHR ?? null;
+  if (kshr !== null) {
+    await waitForCompilation(() => gl.getShaderParameter(vs!, kshr));
+    await waitForCompilation(() => gl.getShaderParameter(fs!, kshr));
+  } else {
+    await yieldToMain();
+  }
+
+  if (!gl.getShaderParameter(vs!, gl.COMPILE_STATUS)) {
+    console.error(gl.getShaderInfoLog(vs!));
+    gl.deleteShader(vs);
+    gl.deleteShader(fs);
+    return null;
+  }
+  if (!gl.getShaderParameter(fs!, gl.COMPILE_STATUS)) {
+    console.error(gl.getShaderInfoLog(fs!));
+    gl.deleteShader(vs);
+    gl.deleteShader(fs);
+    return null;
+  }
+
+  // -- Program linking (non-blocking) --
+
+  const prog = gl.createProgram()!;
+  gl.attachShader(prog, vs!);
+  gl.attachShader(prog, fs!);
+  gl.linkProgram(prog);
+
+  if (kshr !== null) {
+    await waitForCompilation(() => gl.getProgramParameter(prog, kshr));
+  } else {
+    await yieldToMain();
+  }
+
+  if (!gl.getProgramParameter(prog, gl.LINK_STATUS)) {
+    console.error(gl.getProgramInfoLog(prog));
+    gl.deleteProgram(prog);
+    gl.deleteShader(vs);
+    gl.deleteShader(fs);
+    return null;
+  }
+  gl.useProgram(prog);
+
+  // -- Full-screen quad geometry --
+  // 4 vertices at the clip-space corners (-1 to 1) forming a rectangle
+  // via TRIANGLE_STRIP, so the fragment shader runs on every pixel.
+
+  const buf = gl.createBuffer();
+  gl.bindBuffer(gl.ARRAY_BUFFER, buf);
+  gl.bufferData(gl.ARRAY_BUFFER, new Float32Array([-1, -1, 1, -1, -1, 1, 1, 1]), gl.STATIC_DRAW);
+  const aPos = gl.getAttribLocation(prog, 'aPos');
+  gl.enableVertexAttribArray(aPos);
+  // Each vertex is 2 floats (x, y), no stride or offset
+  gl.vertexAttribPointer(aPos, 2, gl.FLOAT, false, 0, 0);
+
+  // -- Uniform locations --
+
+  const uTime = gl.getUniformLocation(prog, 'uTime');
+  const uRes = gl.getUniformLocation(prog, 'uRes');
+  const uDark = gl.getUniformLocation(prog, 'uDark');
+
+  // -- Animation state --
+
+  let animId = 0;
+  const t0 = performance.now();
+  let running = false;
+
+  /** Draws a single frame with current time and theme. */
+  function drawFrame() {
+    gl!.uniform1f(uTime, reducedMotion ? 0.0 : (performance.now() - t0) / 1000);
+    gl!.uniform1f(uDark, isDark() ? 1.0 : 0.0);
+    gl!.drawArrays(gl!.TRIANGLE_STRIP, 0, 4);
+  }
+
+  /** Syncs the canvas resolution with its CSS size, accounting for device pixel ratio. */
+  function resize() {
+    const dpr = Math.min(window.devicePixelRatio, 1.5);
+    canvas.width = canvas.clientWidth * dpr;
+    canvas.height = canvas.clientHeight * dpr;
+    gl!.viewport(0, 0, canvas.width, canvas.height);
+    gl!.uniform2f(uRes, canvas.width, canvas.height);
+
+    // When paused, resizing clears the canvas — redraw immediately
+    if (!running) drawFrame();
+  }
+
+  /** Draws a frame and schedules the next via requestAnimationFrame. */
+  function render() {
+    if (!running) return;
+    drawFrame();
+    if (reducedMotion) {
+      running = false;
+      return;
+    }
+    animId = requestAnimationFrame(render);
+  }
+
+  // Redraw when theme changes, even if paused
+  const themeObserver = new MutationObserver(() => {
+    if (!running) drawFrame();
+  });
+  themeObserver.observe(document.documentElement, {
+    attributes: true,
+    attributeFilter: ['data-theme'],
+  });
+  window.matchMedia('(prefers-color-scheme: dark)').addEventListener('change', () => {
+    if (!running) drawFrame();
+  });
+
+  // Initial sizing + auto-resize on layout changes
+  resize();
+  const ro = new ResizeObserver(resize);
+  ro.observe(canvas);
+
+  return {
+    /** Starts the render loop. No-op if already running. */
+    play() {
+      if (running) return;
+      running = true;
+      animId = requestAnimationFrame(render);
+    },
+    /** Stops the render loop. */
+    pause() {
+      running = false;
+      cancelAnimationFrame(animId);
+    },
+  };
+}
diff --git a/src/components/patterns/Hero/index.ts b/src/components/patterns/Hero/index.ts
new file mode 100644
index 0000000000..d9d0f6d215
--- /dev/null
+++ b/src/components/patterns/Hero/index.ts
@@ -0,0 +1,7 @@
+/**
+ * Hero Component Index
+ *
+ * Export Hero component
+ */
+
+export { default } from './Hero.astro';
diff --git a/src/components/patterns/Hero/shaders/fragment.glsl b/src/components/patterns/Hero/shaders/fragment.glsl
new file mode 100644
index 0000000000..10e480c6b8
--- /dev/null
+++ b/src/components/patterns/Hero/shaders/fragment.glsl
@@ -0,0 +1,103 @@
+precision mediump float;
+varying vec2 vUv;
+uniform float uTime;
+uniform vec2 uRes;
+uniform float uDark;
+
+#define PI 3.14159265359
+
+float hash(vec2 p) {
+  return fract(sin(dot(p, vec2(127.1, 311.7))) * 43758.5453);
+}
+
+float noise(vec2 p) {
+  vec2 i = floor(p);
+  vec2 f = fract(p);
+  f = f * f * (3.0 - 2.0 * f);
+  float a = hash(i);
+  float b = hash(i + vec2(1.0, 0.0));
+  float c = hash(i + vec2(0.0, 1.0));
+  float d = hash(i + vec2(1.0, 1.0));
+  return mix(mix(a, b, f.x), mix(c, d, f.x), f.y);
+}
+
+vec3 iridescence(float t, float shift) {
+  float phase = t * 6.2831 + shift;
+  vec3 c = vec3(
+    0.75 + 0.5 * sin(phase),
+    0.5 + 0.5 * sin(phase + 2.094),
+    0.5 + 0.5 * sin(phase + 4.189)
+  ) * vec3(1.0, 0.25, 0.7) + vec3(0.25, 0.05, 0.18);
+  float lum = dot(c, vec3(0.299, 0.587, 0.114));
+  return mix(mix(vec3(lum), c, 0.5), vec3(1.0), 0.2);
+}
+
+void main() {
+  vec2 uv = vUv;
+  float t = uTime;
+  float aspect = uRes.x / uRes.y;
+  vec2 p = vec2((uv.x - 0.5) * aspect, uv.y - 0.5);
+  vec2 center = vec2(aspect * 1.1, -0.5 - aspect * 1.8);
+  float radius = aspect * 2.0 + 0.8;
+
+  vec2 delta = p - center;
+  float d = length(delta) - radius;
+  float absd = abs(d);
+
+  /* early exit: skip expensive work far from the arc */
+  vec3 bg = mix(vec3(1.0), vec3(0.0), uDark);
+  if (absd > 0.15) {
+    gl_FragColor = vec4(bg, 1.0);
+    return;
+  }
+
+  float angle = atan(delta.y, delta.x);
+
+  /* ribbon */
+  float thickness = 0.035 + 0.006 * sin(t * 0.4);
+  float ribbon = 1.0 - smoothstep(0.0, thickness, absd);
+  float glow = exp(-absd * 12.0) * 0.35;
+
+  /* color — single-octave noise instead of turbulence */
+  float cp = angle * 1.2 + t * 0.15;
+  float n = noise(vec2(angle * 3.0, t * 0.3)) * 0.5;
+  vec3 iriCol = iridescence(cp + n, t * 0.2);
+  iriCol += noise(vec2(angle * 8.0 - t * 0.5, d * 60.0)) * 0.2 * ribbon;
+
+  /* secondary arc */
+  float d2 = d + 0.07 + 0.005 * sin(t * 0.6);
+  float absd2 = abs(d2);
+  float ribbon2 = 1.0 - smoothstep(0.0, 0.012, absd2);
+  float glow2 = exp(-absd2 * 18.0) * 0.15;
+  vec3 iriCol2 = iridescence(cp + 1.5 + n, t * 0.25 + 1.0);
+
+  /* compose */
+  vec3 col = bg;
+  col = mix(col, mix(iriCol * 1.2 + 0.1, iriCol, uDark), ribbon + glow);
+  col = mix(col, mix(iriCol2 * 1.2 + 0.1, iriCol2, uDark), ribbon2 + glow2);
+
+  /* sparkles — reduced to 6 */
+  float sparkle = 0.0;
+  for (int i = 0; i < 6; i++) {
+    float fi = float(i);
+    float seed = hash(vec2(fi, fi * 0.7));
+    float pAngle = seed * PI * 0.8 + 1.8;
+    float pRadius = radius + (hash(vec2(fi * 1.3, 0.0)) - 0.5) * 0.08;
+    vec2 pos = center + pRadius * vec2(cos(pAngle), sin(pAngle))
+      + vec2(sin(t * (0.2 + seed * 0.3) + fi), cos(t * (0.15 + seed * 0.2) + fi * 1.3)) * 0.01;
+    float dist = length(p - pos);
+    float br = sin(t * (1.0 + seed * 2.0) + fi * 2.5) * 0.5 + 0.5;
+    br *= br;
+    sparkle += br * smoothstep(0.001 + seed * 0.002, 0.0, dist);
+  }
+
+  col += sparkle * vec3(1.0, 0.7, 0.85) * 1.5;
+
+  /* ambient glow */
+  col += vec3(0.5, 0.2, 0.4) * exp(-absd * 4.0) * 0.06;
+
+  /* smooth fade to background near cutoff edge */
+  col = mix(col, bg, smoothstep(0.1, 0.15, absd));
+
+  gl_FragColor = vec4(clamp(col, 0.0, 1.0), 1.0);
+}
diff --git a/src/components/patterns/Hero/shaders/vertex.glsl b/src/components/patterns/Hero/shaders/vertex.glsl
new file mode 100644
index 0000000000..4359df5adc
--- /dev/null
+++ b/src/components/patterns/Hero/shaders/vertex.glsl
@@ -0,0 +1,6 @@
+attribute vec2 aPos;
+varying vec2 vUv;
+void main() {
+  vUv = aPos * 0.5 + 0.5;
+  gl_Position = vec4(aPos, 0.0, 1.0);
+}
diff --git a/src/components/patterns/LanguageSelect/LanguageSelect.astro b/src/components/patterns/LanguageSelect/LanguageSelect.astro
new file mode 100644
index 0000000000..b767a8b205
--- /dev/null
+++ b/src/components/patterns/LanguageSelect/LanguageSelect.astro
@@ -0,0 +1,68 @@
+---
+/**
+ * LanguageSelect Component
+ *
+ * Language selector built on top of the Select primitive.
+ * Uses the Select component with icon variant for language switching.
+ *
+ * @example
+ * <LanguageSelect
+ *   languages={[
+ *     { code: 'en', label: 'English' },
+ *     { code: 'es', label: 'Español' },
+ *   ]}
+ *   currentLanguage="en"
+ * />
+ */
+
+import { Select } from '@/components/primitives';
+import type { LanguageSelectProps } from './types';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+type Props = LanguageSelectProps;
+
+const { languages, currentLanguage: propLanguage, class: className, id, ...rest } = Astro.props;
+const currentLanguage = propLanguage || getLangFromUrl(Astro.url);
+const t = useTranslations(currentLanguage);
+
+const options = languages.map((lang) => ({
+  value: lang.code,
+  label: lang.label,
+  selected: lang.code === currentLanguage,
+}));
+---
+
+<Select
+  options={options}
+  value={currentLanguage}
+  icon="fluent:translate-16-regular"
+  hideLabel={true}
+  variant="icon"
+  dropdownAlign="right"
+  ariaLabel={t('language.selectLabel')}
+  class={className}
+  data-language-select
+  {...id && { id }}
+  {...rest}
+/>
+
+<script>
+  import { replaceLanguageInPath } from '@/i18n/utils';
+
+  function handleLanguageChange() {
+    const selects = document.querySelectorAll('[data-language-select]');
+
+    selects.forEach((select) => {
+      select.addEventListener('select-change', ((e: CustomEvent) => {
+        const code = e.detail.value;
+        const currentPath = window.location.pathname;
+        const newPath = replaceLanguageInPath(currentPath, code);
+
+        window.location.href = newPath;
+      }) as EventListener);
+    });
+  }
+
+  handleLanguageChange();
+  document.addEventListener('astro:page-load', handleLanguageChange);
+</script>
diff --git a/src/components/patterns/LanguageSelect/types.ts b/src/components/patterns/LanguageSelect/types.ts
new file mode 100644
index 0000000000..272f960e88
--- /dev/null
+++ b/src/components/patterns/LanguageSelect/types.ts
@@ -0,0 +1,17 @@
+/**
+ * LanguageSelect Component Types
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import type { LanguageCode } from '@/i18n/locales';
+
+export interface LanguageConfig {
+  code: LanguageCode;
+  label: string;
+}
+
+export type LanguageSelectProps = HTMLAttributes<'div'> & {
+  languages: LanguageConfig[];
+  currentLanguage?: LanguageCode;
+  onLanguageChange?: (code: LanguageCode) => void;
+};
diff --git a/src/components/patterns/LogoDisplay/LogoDisplay.astro b/src/components/patterns/LogoDisplay/LogoDisplay.astro
new file mode 100644
index 0000000000..0e33405328
--- /dev/null
+++ b/src/components/patterns/LogoDisplay/LogoDisplay.astro
@@ -0,0 +1,55 @@
+---
+/**
+ * LogoDisplay Component
+ *
+ * Displays both logo variants (dark and light) as cards side by side,
+ * each with a contrasting background and a download button.
+ */
+import { Image } from 'astro:assets';
+import { Button } from '@components/primitives';
+import { getLangFromUrl, useTranslations } from '@i18n/utils';
+import './LogoDisplay.css';
+
+interface Props {
+  darkSrc: string;
+  lightSrc: string;
+  alt: string;
+}
+
+const { darkSrc, lightSrc, alt } = Astro.props;
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+<div class="logo-display">
+  <div class="logo-display__card">
+    <div class="logo-display__preview logo-display__preview--light-bg">
+      <Image
+        src={darkSrc}
+        alt={`${alt} (dark)`}
+        class="logo-display__img"
+        width={200}
+        height={65}
+        loading="lazy"
+      />
+    </div>
+    <Button as="a" href={darkSrc} download variant="secondary" size="sm" ghost>
+      {t('common.download')}
+    </Button>
+  </div>
+  <div class="logo-display__card">
+    <div class="logo-display__preview logo-display__preview--dark-bg">
+      <Image
+        src={lightSrc}
+        alt={`${alt} (light)`}
+        class="logo-display__img"
+        width={200}
+        height={65}
+        loading="lazy"
+      />
+    </div>
+    <Button as="a" href={lightSrc} download variant="secondary" size="sm" ghost>
+      {t('common.download')}
+    </Button>
+  </div>
+</div>
diff --git a/src/components/patterns/LogoDisplay/LogoDisplay.css b/src/components/patterns/LogoDisplay/LogoDisplay.css
new file mode 100644
index 0000000000..553ab0f327
--- /dev/null
+++ b/src/components/patterns/LogoDisplay/LogoDisplay.css
@@ -0,0 +1,42 @@
+.logo-display {
+  display: flex;
+  gap: 1.5rem;
+  flex-wrap: wrap;
+}
+
+.logo-display__card {
+  display: flex;
+  flex-direction: column;
+  align-items: stretch;
+  border: 1px solid var(--color-border-primary);
+  border-radius: 8px;
+  overflow: hidden;
+}
+
+.logo-display__preview {
+  display: flex;
+  align-items: center;
+  justify-content: center;
+  padding: 2rem;
+}
+
+.logo-display__preview--light-bg {
+  background: #fff;
+}
+
+.logo-display__preview--dark-bg {
+  background: #1a1a1a;
+}
+
+.logo-display__img {
+  width: 200px;
+  aspect-ratio: 200 / 65;
+  object-fit: contain;
+}
+
+.logo-display__card .btn {
+  border: none;
+  border-radius: 0;
+  text-align: center;
+  justify-content: center;
+}
diff --git a/src/components/patterns/MiddlewareInfo/MiddlewareInfo.astro b/src/components/patterns/MiddlewareInfo/MiddlewareInfo.astro
new file mode 100644
index 0000000000..d1282d9678
--- /dev/null
+++ b/src/components/patterns/MiddlewareInfo/MiddlewareInfo.astro
@@ -0,0 +1,37 @@
+---
+/**
+ * MiddlewareInfo Component
+ *
+ * Displays version, links to GitHub, changelog, and npm for a middleware package.
+ */
+import './MiddlewareInfo.css';
+import { Icon } from 'astro-icon/components';
+
+interface Props {
+  version: string;
+  github: string;
+  npm: string;
+}
+
+const { version, github, npm } = Astro.props;
+const changelog = `${github}/releases`;
+---
+
+<div class="middleware-info">
+  <span class="middleware-info__item">
+    <Icon name="fluent:tag-16-regular" size="16" />
+    v{version}
+  </span>
+  <a href={github} target="_blank" rel="noopener noreferrer" class="middleware-info__item">
+    <Icon name="github" size="16" />
+    GitHub
+  </a>
+  <a href={changelog} target="_blank" rel="noopener noreferrer" class="middleware-info__item">
+    <Icon name="fluent:history-16-regular" size="16" />
+    Changelog
+  </a>
+  <a href={npm} target="_blank" rel="noopener noreferrer" class="middleware-info__item">
+    <Icon name="fluent:box-16-regular" size="16" />
+    npm
+  </a>
+</div>
diff --git a/src/components/patterns/MiddlewareInfo/MiddlewareInfo.css b/src/components/patterns/MiddlewareInfo/MiddlewareInfo.css
new file mode 100644
index 0000000000..1965e393fd
--- /dev/null
+++ b/src/components/patterns/MiddlewareInfo/MiddlewareInfo.css
@@ -0,0 +1,27 @@
+.middleware-info {
+  display: flex;
+  flex-wrap: wrap;
+  gap: 1.5rem;
+  padding: 0.75rem 0 1.5rem;
+  border-bottom: 1px solid var(--color-border-primary);
+  margin-bottom: 1.5rem;
+}
+
+.middleware-info__item {
+  display: inline-flex;
+  align-items: center;
+  gap: 0.375rem;
+  font-size: var(--text-sm);
+  line-height: 1;
+  color: var(--color-text-secondary);
+  text-decoration: none;
+}
+
+.middleware-info__item svg {
+  flex-shrink: 0;
+  vertical-align: middle;
+}
+
+a.middleware-info__item:hover {
+  color: var(--color-text-primary);
+}
diff --git a/src/components/patterns/PageHead/PageHead.astro b/src/components/patterns/PageHead/PageHead.astro
new file mode 100644
index 0000000000..c94fd21d11
--- /dev/null
+++ b/src/components/patterns/PageHead/PageHead.astro
@@ -0,0 +1,22 @@
+---
+import './PageHead.css';
+import { Flex, H1, Body } from '@components/primitives';
+
+interface Props {
+  title: string;
+  description?: string;
+}
+
+const { title, description } = Astro.props;
+---
+
+<Flex direction="column" gap="6" align="center" class="page-head">
+  <H1 vMargin={false}>{title}</H1>
+  {
+    description && (
+      <Body vMargin={false} class="page-head__description">
+        {description}
+      </Body>
+    )
+  }
+</Flex>
diff --git a/src/components/patterns/PageHead/PageHead.css b/src/components/patterns/PageHead/PageHead.css
new file mode 100644
index 0000000000..052913de1b
--- /dev/null
+++ b/src/components/patterns/PageHead/PageHead.css
@@ -0,0 +1,14 @@
+@layer patterns {
+  .page-head {
+    margin: var(--space-10) 0;
+
+    @media (--md-up) {
+      margin: var(--space-16) 0 var(--space-12);
+    }
+  }
+
+  .page-head__description {
+    max-width: 68rem;
+    text-align: center;
+  }
+}
diff --git a/src/components/patterns/PageHead/index.ts b/src/components/patterns/PageHead/index.ts
new file mode 100644
index 0000000000..364713a857
--- /dev/null
+++ b/src/components/patterns/PageHead/index.ts
@@ -0,0 +1,7 @@
+/**
+ * PageHead Component Index
+ *
+ * Export PageHead component
+ */
+
+export { default } from './PageHead.astro';
diff --git a/src/components/patterns/PageTopbar/PageTopbar.astro b/src/components/patterns/PageTopbar/PageTopbar.astro
new file mode 100644
index 0000000000..2f44597118
--- /dev/null
+++ b/src/components/patterns/PageTopbar/PageTopbar.astro
@@ -0,0 +1,32 @@
+---
+/**
+ * PageTopbar Pattern Component
+ *
+ * Renders a page-level topbar with breadcrumb navigation and an optional action (via slot).
+ *
+ * @example
+ * <PageTopbar
+ *   breadcrumbs={[
+ *     { href: '/en/', ariaLabel: 'Home', icon: 'fluent:home-empty-20-regular' },
+ *     { label: 'Blog', href: '/en/blog' },
+ *     { label: 'Post title' },
+ *   ]}
+ * >
+ *   <Button as="a" variant="secondary" size="sm" href="...">Edit on GitHub</Button>
+ * </PageTopbar>
+ */
+import Breadcrumbs from '@components/patterns/Breadcrumbs/Breadcrumbs.astro';
+import type { BreadcrumbItem } from '@utils/content';
+import './PageTopbar.css';
+
+interface Props {
+  breadcrumbs: BreadcrumbItem[];
+}
+
+const { breadcrumbs } = Astro.props;
+---
+
+<div class="page-topbar">
+  <Breadcrumbs items={breadcrumbs} />
+  <slot />
+</div>
diff --git a/src/components/patterns/PageTopbar/PageTopbar.css b/src/components/patterns/PageTopbar/PageTopbar.css
new file mode 100644
index 0000000000..205d8345aa
--- /dev/null
+++ b/src/components/patterns/PageTopbar/PageTopbar.css
@@ -0,0 +1,15 @@
+@layer patterns {
+  .page-topbar {
+    padding: var(--space-6) 0;
+    display: flex;
+    justify-content: space-between;
+    align-items: center;
+    gap: var(--space-4);
+
+    @media (--xs-only) {
+      flex-direction: column;
+      align-items: flex-start;
+      gap: var(--space-2);
+    }
+  }
+}
diff --git a/src/components/patterns/Pagination/Pagination.astro b/src/components/patterns/Pagination/Pagination.astro
new file mode 100644
index 0000000000..c247315eaf
--- /dev/null
+++ b/src/components/patterns/Pagination/Pagination.astro
@@ -0,0 +1,60 @@
+---
+/**
+ * Pagination Pattern Component
+ *
+ * Renders previous/next navigation with a current page indicator.
+ *
+ * @example
+ * <Pagination
+ *   prevUrl="/blog"
+ *   nextUrl="/blog/3"
+ *   currentPage={2}
+ *   lastPage={5}
+ * />
+ */
+import './Pagination.css';
+import { Icon } from 'astro-icon/components';
+import { Flex, Button, Body } from '@components/primitives';
+import type { HTMLAttributes } from 'astro/types';
+
+interface Props extends HTMLAttributes<'div'> {
+  prevUrl?: string;
+  nextUrl?: string;
+  currentPage: number;
+  lastPage: number;
+}
+
+const { prevUrl, nextUrl, currentPage, lastPage, ...rest } = Astro.props;
+---
+
+<Flex justify="between" align="center" gap="4" class="pagination" {...rest}>
+  {
+    prevUrl ? (
+      <Button as="a" href={prevUrl} variant="secondary" size="md" data-pagination-prev>
+        <Icon name="fluent:arrow-left-20-filled" />
+        Previous
+      </Button>
+    ) : (
+      <Button variant="secondary" size="md" data-pagination-prev>
+        <Icon name="fluent:arrow-left-20-filled" />
+        Previous
+      </Button>
+    )
+  }
+  <Body vMargin={false} data-pagination-label>
+    Page {currentPage} of {lastPage}
+  </Body>
+  {
+    nextUrl ? (
+      <Button as="a" href={nextUrl} variant="secondary" size="md" data-pagination-next>
+        Next
+        <Icon name="fluent:arrow-right-20-filled" />
+      </Button>
+    ) : (
+      <Button variant="secondary" size="md" data-pagination-next>
+        Next
+        <Icon name="fluent:arrow-right-20-filled" />
+      </Button>
+    )
+  }
+</Flex>
diff --git a/src/components/patterns/Pagination/Pagination.css b/src/components/patterns/Pagination/Pagination.css
new file mode 100644
index 0000000000..481094494d
--- /dev/null
+++ b/src/components/patterns/Pagination/Pagination.css
@@ -0,0 +1,11 @@
+@layer patterns {
+  .pagination {
+    margin-top: var(--space-8);
+  }
+
+  .pagination a[aria-disabled='true'] {
+    opacity: 0.6;
+    pointer-events: none;
+    cursor: not-allowed;
+  }
+}
diff --git a/src/components/patterns/PostCard/PostCard.astro b/src/components/patterns/PostCard/PostCard.astro
new file mode 100644
index 0000000000..c764d893d6
--- /dev/null
+++ b/src/components/patterns/PostCard/PostCard.astro
@@ -0,0 +1,88 @@
+---
+/**
+ * PostCard Pattern Component
+ *
+ * An article card with a label, title, and author avatar(s).
+ *
+ * @example — Single author
+ * <PostCard
+ *   href="/blog/secure-express-app"
+ *   labels={["Security"]}
+ *   title="How to secure your Express app"
+ *   coverSrc="/images/cover.jpg"
+ *   authors={[{ src: "/images/author.jpg", name: "John Doe" }]}
+ *   avatarCaption="Jun 05, 2025"
+ * />
+ *
+ * @example — Multiple authors
+ * <PostCard
+ *   href="/blog/express-5"
+ *   labels={["Release"]}
+ *   title="Express 5.0 is here"
+ *   coverSrc="/images/cover.jpg"
+ *   authors={[
+ *     { src: "/images/author1.jpg", name: "Jane Smith" },
+ *     { src: "/images/author2.jpg", name: "John Doe" },
+ *   ]}
+ *   avatarCaption="Mar 04, 2026"
+ * />
+ */
+import './PostCard.css';
+import type { HTMLAttributes } from 'astro/types';
+import { Image } from 'astro:assets';
+import { H3, Avatar, Tag } from '@components/primitives';
+
+interface Author {
+  src: string;
+  alt?: string;
+  name: string;
+}
+
+interface Props extends HTMLAttributes<'article'> {
+  href: string;
+  labels: string[];
+  title: string;
+  coverSrc?: string;
+  coverAlt?: string;
+  authors: Author[];
+  avatarCaption?: string;
+}
+
+const {
+  href,
+  labels,
+  title,
+  coverSrc,
+  coverAlt = '',
+  authors,
+  avatarCaption,
+  class: className,
+  ...rest
+} = Astro.props;
+---
+
+<article class:list={['post-card', className]} {...rest}>
+  <a href={href} class="post-card__link">
+    <div>
+      {
+        coverSrc && (
+          <Image
+            class="post-card__cover"
+            src={coverSrc}
+            alt={coverAlt || ''}
+            width={1200}
+            height={630}
+            loading="lazy"
+          />
+        )
+      }
+      <div class="post-card__labels">
+        {labels.map((label) => <Tag>{label}</Tag>)}
+      </div>
+      <H3 as="h2" vMargin={false} class="post-card__title">
+        {title}
+      </H3>
+    </div>
+    <Avatar authors={authors} caption={avatarCaption} size="md" />
+  </a>
+</article>
diff --git a/src/components/patterns/PostCard/PostCard.css b/src/components/patterns/PostCard/PostCard.css
new file mode 100644
index 0000000000..42998d26dd
--- /dev/null
+++ b/src/components/patterns/PostCard/PostCard.css
@@ -0,0 +1,51 @@
+@layer patterns {
+  .post-card {
+    display: flex;
+    flex-direction: column;
+    border: var(--border-width-1) solid var(--color-border-secondary);
+    border-radius: var(--radius-base);
+    gap: var(--space-4);
+    overflow: hidden;
+    padding: var(--space-4);
+    cursor: pointer;
+    transition: border-color 0.15s ease-in-out;
+
+    &:hover {
+      border: var(--color-focus-ring) solid var(--border-width-1);
+    }
+  }
+
+  .post-card__labels {
+    display: flex;
+    flex-wrap: wrap;
+    gap: var(--space-2);
+    margin-bottom: var(--space-4);
+  }
+
+  .post-card__link {
+    display: flex;
+    flex-direction: column;
+    justify-content: space-between;
+    gap: inherit;
+    color: inherit;
+    text-decoration: none;
+    height: 100%;
+
+    &:focus {
+      outline: none;
+    }
+  }
+
+  .post-card:focus-within {
+    border: var(--color-focus-ring) solid var(--border-width-1);
+  }
+
+  .post-card__cover {
+    margin-bottom: var(--space-3);
+    display: block;
+    width: 100%;
+    aspect-ratio: 1200 / 630;
+    object-fit: cover;
+    border-radius: var(--radius-base);
+  }
+}
diff --git a/src/components/patterns/PostHeader/PostHeader.astro b/src/components/patterns/PostHeader/PostHeader.astro
new file mode 100644
index 0000000000..d274e90375
--- /dev/null
+++ b/src/components/patterns/PostHeader/PostHeader.astro
@@ -0,0 +1,165 @@
+---
+/**
+ * PostHeader Pattern Component
+ *
+ * A blog post header section with tags, title, author avatar, and share icons.
+ *
+ * @example — Single author
+ * <PostHeader
+ *   labels={["Security"]}
+ *   title="How to secure your Express app"
+ *   authors={[{ src: "/images/author.jpg", name: "John Doe" }]}
+ *   date="Jun 05, 2025"
+ * />
+ *
+ * @example — Multiple authors, no tags
+ * <PostHeader
+ *   title="Express 5.0 is here"
+ *   authors={[
+ *     { src: "/images/author1.jpg", name: "Jane Smith" },
+ *     { src: "/images/author2.jpg", name: "John Doe" },
+ *   ]}
+ *   date="Mar 04, 2026"
+ * />
+ */
+import './PostHeader.css';
+import type { HTMLAttributes } from 'astro/types';
+import { Image } from 'astro:assets';
+import { H1, Avatar, Tag, Flex } from '@components/primitives';
+import { Icon } from 'astro-icon/components';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+interface Author {
+  src: string;
+  alt?: string;
+  name: string;
+}
+
+interface Props extends HTMLAttributes<'div'> {
+  labels?: string[];
+  title: string;
+  authors: Author[];
+  date?: string;
+  cover?: string;
+}
+
+const { labels = [], title, authors, date, cover, class: className, ...rest } = Astro.props;
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+const pageUrl = Astro.url.href;
+const encodedUrl = encodeURIComponent(pageUrl);
+const encodedTitle = encodeURIComponent(title);
+
+const xShareUrl = `https://x.com/intent/tweet?text=${encodedTitle}&url=${encodedUrl}`;
+const bskyShareUrl = `https://bsky.app/intent/compose?text=${encodedTitle}%20${encodedUrl}`;
+const linkedinShareUrl = `https://www.linkedin.com/sharing/share-offsite/?url=${encodedUrl}`;
+const telegramShareUrl = `https://t.me/share/url?url=${encodedUrl}&text=${encodedTitle}`;
+const whatsappShareUrl = `https://wa.me/?text=${encodedTitle}%20${encodedUrl}`;
+---
+
+<div class:list={['post-header', className]} {...rest}>
+  {
+    labels.length > 0 && (
+      <Flex gap="2" wrap="wrap">
+        {labels.map((label) => (
+          <Tag>{label}</Tag>
+        ))}
+      </Flex>
+    )
+  }
+  <H1 id="overview" vMargin={false} class="post-header__title"><a href="#overview">{title}</a></H1>
+  {authors.length > 0 && <Avatar authors={authors} caption={date} size="md" />}
+  <div class="post-header__share" role="group" aria-label={t('post.share')}>
+    <a
+      class="post-header__share-btn"
+      href={xShareUrl}
+      aria-label={t('post.shareOnX')}
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <Icon name="x" aria-hidden="true" />
+    </a>
+    <a
+      class="post-header__share-btn"
+      href={bskyShareUrl}
+      aria-label={t('post.shareOnBluesky')}
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <Icon name="bsky" aria-hidden="true" />
+    </a>
+    <a
+      class="post-header__share-btn"
+      href={linkedinShareUrl}
+      aria-label={t('post.shareOnLinkedIn')}
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <Icon name="linkedin" aria-hidden="true" />
+    </a>
+    <a
+      class="post-header__share-btn"
+      href={telegramShareUrl}
+      aria-label={t('post.shareOnTelegram')}
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <Icon name="telegram" aria-hidden="true" />
+    </a>
+    <a
+      class="post-header__share-btn"
+      href={whatsappShareUrl}
+      aria-label={t('post.shareOnWhatsApp')}
+      target="_blank"
+      rel="noopener noreferrer"
+    >
+      <Icon name="whatsapp" aria-hidden="true" />
+    </a>
+    <a class="post-header__share-btn" href="/feed.xml" aria-label={t('post.rssFeed')}>
+      <Icon name="rss" aria-hidden="true" />
+    </a>
+    <button
+      class="post-header__share-btn post-header__copy-btn"
+      type="button"
+      aria-label={t('post.copyLink')}
+      data-url={pageUrl}
+      data-label-copy={t('post.copyLink')}
+      data-label-copied={t('post.linkCopied')}
+    >
+      <Icon name="fluent:link-24-regular" aria-hidden="true" />
+    </button>
+  </div>
+
+  {
+    cover && (
+      <div class="post-header__cover">
+        <Image
+          src={cover}
+          alt=""
+          aria-hidden="true"
+          width={1200}
+          height={630}
+          loading="eager"
+          fetchpriority="high"
+        />
+      </div>
+    )
+  }
+</div>
+
+<script>
+  document.querySelectorAll<HTMLButtonElement>('.post-header__copy-btn').forEach((btn) => {
+    btn.addEventListener('click', async () => {
+      const url = btn.dataset.url ?? window.location.href;
+      await navigator.clipboard.writeText(url);
+      btn.setAttribute('aria-label', btn.dataset.labelCopied ?? 'Copied!');
+      btn.classList.add('post-header__copy-btn--copied');
+      setTimeout(() => {
+        btn.setAttribute('aria-label', btn.dataset.labelCopy ?? '');
+        btn.classList.remove('post-header__copy-btn--copied');
+      }, 2000);
+    });
+  });
+</script>
diff --git a/src/components/patterns/PostHeader/PostHeader.css b/src/components/patterns/PostHeader/PostHeader.css
new file mode 100644
index 0000000000..a72562b14a
--- /dev/null
+++ b/src/components/patterns/PostHeader/PostHeader.css
@@ -0,0 +1,78 @@
+@layer patterns {
+  .post-header {
+    padding: 0;
+    margin: var(--space-4) 0;
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-6);
+    justify-content: center;
+    align-items: center;
+
+    @media (--md-up) {
+      margin: var(--space-10) 0;
+    }
+  }
+
+  .post-header__title {
+    text-align: center;
+    @media (--md-only) {
+      padding: 0 var(--space-8);
+    }
+
+    @media (--lg-up) {
+      padding: 0 var(--space-16);
+    }
+  }
+
+  .post-header__share {
+    display: flex;
+    align-items: center;
+    gap: var(--space-1);
+  }
+
+  .post-header__share-btn {
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    width: var(--space-9);
+    height: var(--space-9);
+    border-radius: var(--radius-round);
+    color: var(--color-icon-primary);
+    background: none;
+    border: none;
+    cursor: pointer;
+    text-decoration: none;
+    transition: background-color 0.15s ease;
+
+    &:hover {
+      background-color: var(--color-bg-secondary);
+    }
+
+    &:focus-visible {
+      outline: var(--color-focus-ring) solid var(--border-width-2);
+      outline-offset: var(--border-width-1);
+    }
+
+    & svg {
+      width: var(--space-4);
+      height: var(--space-4);
+    }
+  }
+
+  .post-header__copy-btn--copied {
+    color: var(--color-success);
+  }
+
+  .post-header__cover {
+    width: 100%;
+    max-width: 720px;
+    overflow: hidden;
+    border-radius: var(--radius-lg);
+  }
+
+  .post-header__cover img {
+    width: 100%;
+    aspect-ratio: 1200 / 630;
+    object-fit: cover;
+  }
+}
diff --git a/src/components/patterns/RelatedContent/RelatedContent.astro b/src/components/patterns/RelatedContent/RelatedContent.astro
new file mode 100644
index 0000000000..f8c931d41c
--- /dev/null
+++ b/src/components/patterns/RelatedContent/RelatedContent.astro
@@ -0,0 +1,46 @@
+---
+import type { CollectionEntry } from 'astro:content';
+import './RelatedContent.css';
+import { H2 } from '@/components/primitives';
+import { PostCard } from '@/components/patterns';
+
+interface Props {
+  posts: CollectionEntry<'blog'>[];
+  lang: string;
+  title: string;
+}
+
+const { posts, lang, title } = Astro.props;
+---
+
+{
+  posts.length > 0 && (
+    <section class="related-content">
+      <H2>{title}</H2>
+      <div class="related-content__grid">
+        {posts.map((p) => {
+          const pFilename = p.id.split('/').pop() ?? p.id;
+          const pDate = new Date(pFilename.substring(0, 10)).toLocaleDateString('en-US', {
+            month: 'long',
+            day: 'numeric',
+            year: 'numeric',
+          });
+          const pAuthors = (p.data.authors ?? []).map((a) => ({
+            src: a.github ? `https://github.com/${a.github}.png` : '',
+            name: a.name ?? '',
+          }));
+          return (
+            <PostCard
+              href={`/${lang}/blog/${pFilename}`}
+              labels={p.data.tags ?? []}
+              title={p.data.title}
+              coverSrc={p.data.cover || `/og/blog-${pFilename}.png`}
+              authors={pAuthors}
+              avatarCaption={pDate}
+            />
+          );
+        })}
+      </div>
+    </section>
+  )
+}
diff --git a/src/components/patterns/RelatedContent/RelatedContent.css b/src/components/patterns/RelatedContent/RelatedContent.css
new file mode 100644
index 0000000000..2ad1f57d27
--- /dev/null
+++ b/src/components/patterns/RelatedContent/RelatedContent.css
@@ -0,0 +1,48 @@
+@layer patterns {
+  .related-content {
+    margin-top: var(--space-24);
+    position: relative;
+
+    h2 {
+      margin-bottom: var(--space-6);
+    }
+
+    @media (--xs-only) {
+      margin-top: var(--space-16);
+
+      &::after {
+        content: '';
+        position: absolute;
+        inset: 0;
+        left: auto;
+        width: var(--space-16);
+        background: linear-gradient(to right, transparent, var(--color-bg-primary));
+        pointer-events: none;
+      }
+    }
+  }
+
+  .related-content__grid {
+    display: flex;
+    gap: var(--space-6);
+
+    & > .post-card {
+      flex: 1 1 33.33%;
+    }
+
+    @media (--xs-only) {
+      overflow-x: auto;
+      scroll-snap-type: x mandatory;
+      -webkit-overflow-scrolling: touch;
+      scrollbar-width: none;
+      &::-webkit-scrollbar {
+        display: none;
+      }
+
+      & > .post-card {
+        flex: 1 0 var(--size-60);
+        scroll-snap-align: start;
+      }
+    }
+  }
+}
diff --git a/src/components/patterns/Searchbox/Chat.css b/src/components/patterns/Searchbox/Chat.css
new file mode 100644
index 0000000000..29319ca0e3
--- /dev/null
+++ b/src/components/patterns/Searchbox/Chat.css
@@ -0,0 +1,228 @@
+@layer patterns {
+  .chat-container {
+    display: flex;
+    flex-direction: column;
+    flex-grow: 1;
+    overflow: hidden;
+    justify-content: space-between;
+    position: relative;
+    height: 100%;
+  }
+
+  .chat-container-inner {
+    overflow: auto;
+    position: relative;
+    display: flex;
+    flex: 1;
+    flex-direction: column;
+    height: 100%;
+
+    /* Firefox */
+    scrollbar-width: thin;
+    scrollbar-color: var(--color-border-primary) transparent;
+
+    /* Chrome / Safari / Edge */
+    &::-webkit-scrollbar {
+      width: 6px;
+    }
+
+    &::-webkit-scrollbar-track {
+      background: transparent;
+    }
+
+    &::-webkit-scrollbar-thumb {
+      background-color: var(--color-border-primary);
+      border-radius: 9999px;
+    }
+  }
+
+  /* ============================================
+     Chat Interactions (messages area)
+     ============================================ */
+
+  .chat-interactions {
+    flex: 1;
+  }
+
+  .chat-interaction {
+    display: flex;
+    flex-direction: column;
+    padding: var(--space-6);
+  }
+
+  .chat-user-prompt {
+    align-self: flex-end;
+    background-color: var(--color-bg-tertiary);
+    border: var(--border-width-1) solid var(--color-border-secondary);
+    border-radius: var(--radius-lg);
+    padding: var(--space-3) var(--space-4);
+    font-size: var(--font-size-base);
+    color: var(--color-text-primary);
+    max-width: 80%;
+  }
+
+  .chat-assistant-message {
+    ol {
+      list-style: decimal;
+    }
+
+    ul {
+      list-style: disc;
+    }
+  }
+
+  .chat-title {
+    font-size: var(--font-size-2xl);
+    margin: var(--space-4) 0;
+  }
+
+  .chat-code-block {
+    padding: 0;
+  }
+
+  .chat-loading {
+    display: flex;
+    align-items: center;
+  }
+
+  .chat-typing-dots {
+    display: flex;
+    align-items: flex-end;
+    gap: var(--space-1);
+    padding: var(--space-1) 0;
+
+    & span {
+      margin: 0;
+    }
+
+    & .chat-typing-label {
+      display: block;
+      color: var(--color-text-tertiary);
+      font-size: var(--font-size-sm);
+      margin-right: var(--space-0-5);
+      line-height: 1;
+    }
+
+    & span:not(.chat-typing-label) {
+      display: block;
+      width: var(--size-1);
+      height: var(--size-1);
+      border-radius: var(--radius-full);
+      background-color: var(--color-text-tertiary);
+      animation: chat-dot-bounce 1.2s ease-in-out infinite;
+
+      &:nth-child(3) {
+        animation-delay: 0.2s;
+      }
+      &:nth-child(4) {
+        animation-delay: 0.4s;
+      }
+    }
+  }
+
+  @keyframes chat-dot-bounce {
+    0%,
+    60%,
+    100% {
+      transform: translateY(0);
+      opacity: 0.4;
+    }
+    30% {
+      transform: translateY(-4px);
+      opacity: 1;
+    }
+  }
+
+  .chat-error {
+    color: var(--color-text-danger, var(--color-text-secondary));
+    font-size: var(--font-size-sm);
+  }
+
+  /* ============================================
+     Chat Input
+     ============================================ */
+
+  .chat-input-wrapper {
+    padding: var(--space-3) var(--space-4);
+    border-top: var(--border-width-1) solid var(--color-border-secondary);
+    background-color: var(--color-bg-secondary);
+    flex-shrink: 0;
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+    position: sticky;
+    bottom: 0;
+  }
+
+  .chat-input-icon {
+    color: var(--color-icon-primary);
+    flex-shrink: 0;
+  }
+
+  .chat-input-field {
+    flex: 1;
+    background: none;
+    border: none;
+    outline: none;
+    font-size: var(--font-size-md);
+    color: var(--color-text-primary);
+    font-family: inherit;
+    resize: none;
+    line-height: var(--line-height-snug);
+
+    &::placeholder {
+      color: var(--color-text-tertiary);
+    }
+  }
+
+  .chat-input-button {
+    display: flex;
+    align-items: center;
+    justify-content: center;
+    width: var(--size-8);
+    height: var(--size-8);
+    border-radius: var(--radius-base);
+    border: none;
+    background-color: var(--color-bg-tertiary);
+    color: var(--color-text-primary);
+    cursor: pointer;
+    flex-shrink: 0;
+    transition:
+      background-color var(--duration-150) var(--ease-in-out),
+      color var(--duration-150) var(--ease-in-out);
+
+    &:hover:not(:disabled) {
+      background-color: var(--color-bg-mute);
+    }
+
+    &:disabled {
+      opacity: 0.5;
+      cursor: not-allowed;
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+  }
+
+  .chat-go-to-bottom {
+    position: absolute;
+    bottom: var(--space-16);
+    left: 50%;
+    transform: translateX(-50%);
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    padding: var(--space-2);
+    margin-bottom: var(--space-2);
+    background-color: var(--color-bg-mute);
+    color: var(--color-text-primary);
+    border-radius: var(--radius-full);
+    cursor: pointer;
+    transition: background-color var(--duration-300) var(--ease-in-out);
+
+    &:hover {
+      background-color: var(--color-bg-secondary);
+    }
+  }
+}
diff --git a/src/components/patterns/Searchbox/Chat.tsx b/src/components/patterns/Searchbox/Chat.tsx
new file mode 100644
index 0000000000..dd849be1ee
--- /dev/null
+++ b/src/components/patterns/Searchbox/Chat.tsx
@@ -0,0 +1,91 @@
+import { ChatInteractions, PromptTextArea } from '@orama/ui/components';
+import { useChat } from '@orama/ui/hooks/useChat';
+import { useScrollableContainer } from '@orama/ui/hooks/useScrollableContainer';
+import ArrowDown16Filled from '~icons/fluent/arrow-down-16-filled';
+import Sparkle16Filled from '~icons/fluent/sparkle-16-filled';
+import PauseCircle48Regular from '~icons/fluent/pause-circle-48-regular';
+import Send16Filled from '~icons/fluent/send-16-filled';
+import ChatActions from './ChatActions';
+import './Chat.css';
+import { ChatSources } from './ChatSources';
+
+export default function Chat() {
+  const { loading } = useChat({ throttle_delay: 50 });
+  const { containerRef, scrollToBottom, recalculateGoToBottomButton, showGoToBottomButton } =
+    useScrollableContainer();
+
+  return (
+    <div className="chat-container">
+      <div
+        ref={containerRef}
+        className="chat-container-inner"
+        onScroll={recalculateGoToBottomButton}
+      >
+        <ChatInteractions.Wrapper
+          className="chat-interactions"
+          onStreaming={recalculateGoToBottomButton}
+          onNewInteraction={() => scrollToBottom({ animated: true })}
+        >
+          {(interaction) => (
+            <div className="chat-interaction">
+              <ChatInteractions.UserPrompt className="chat-user-prompt">
+                {interaction.query}
+              </ChatInteractions.UserPrompt>
+              <ChatInteractions.Loading interaction={interaction} className="chat-loading">
+                <div className="chat-typing-dots">
+                  <span className="chat-typing-label">Thinking</span>
+                  <span />
+                  <span />
+                  <span />
+                </div>
+              </ChatInteractions.Loading>
+              <ChatInteractions.Error interaction={interaction} className="chat-error">
+                <span>Something went wrong. Please try again.</span>
+              </ChatInteractions.Error>
+              <ChatSources interaction={interaction} />
+              <ChatInteractions.AssistantMessage
+                className="chat-assistant-message"
+                markdownClassnames={{
+                  h1: 'chat-title',
+                  h2: 'chat-title',
+                  pre: 'chat-code-block',
+                }}
+              >
+                {interaction.response}
+              </ChatInteractions.AssistantMessage>
+              <ChatActions interaction={interaction} />
+            </div>
+          )}
+        </ChatInteractions.Wrapper>
+      </div>
+
+      {showGoToBottomButton && (
+        <button
+          type="button"
+          onClick={() => scrollToBottom({ animated: true })}
+          className="chat-go-to-bottom"
+          aria-label="Scroll to bottom"
+        >
+          <ArrowDown16Filled width={16} height={16} />
+        </button>
+      )}
+
+      <PromptTextArea.Wrapper className="chat-input-wrapper">
+        <Sparkle16Filled width={16} height={16} className="chat-input-icon" />
+        <PromptTextArea.Field
+          className="chat-input-field"
+          placeholder="Ask a question about Express..."
+          rows={1}
+        />
+        <PromptTextArea.Button
+          className="chat-input-button"
+          isLoading={loading}
+          abortContent={<PauseCircle48Regular width={18} height={18} />}
+          aria-label="Send message"
+        >
+          <Send16Filled width={16} height={16} />
+        </PromptTextArea.Button>
+      </PromptTextArea.Wrapper>
+    </div>
+  );
+}
diff --git a/src/components/patterns/Searchbox/ChatActions.css b/src/components/patterns/Searchbox/ChatActions.css
new file mode 100644
index 0000000000..ff55cbfcbf
--- /dev/null
+++ b/src/components/patterns/Searchbox/ChatActions.css
@@ -0,0 +1,24 @@
+@layer patterns {
+  .chat-actions {
+    display: flex;
+    gap: var(--space-2);
+    margin: 0;
+    padding-left: 0;
+    justify-content: flex-end;
+    list-style: none;
+  }
+
+  .chat-action {
+    cursor: pointer;
+    padding: var(--space-2);
+    border-radius: var(--radius-base);
+
+    &:hover {
+      background-color: var(--color-bg-tertiary);
+    }
+  }
+
+  .chat-action--disliked {
+    color: var(--color-text-mute);
+  }
+}
diff --git a/src/components/patterns/Searchbox/ChatActions.tsx b/src/components/patterns/Searchbox/ChatActions.tsx
new file mode 100644
index 0000000000..997e13f9c5
--- /dev/null
+++ b/src/components/patterns/Searchbox/ChatActions.tsx
@@ -0,0 +1,60 @@
+import { ChatInteractions } from '@orama/ui/components';
+import ArrowSync20Regular from '~icons/fluent/arrow-sync-20-regular';
+import Checkmark16Regular from '~icons/fluent/checkmark-16-regular';
+import Copy16Regular from '~icons/fluent/copy-16-regular';
+import ThumbDislike16Regular from '~icons/fluent/thumb-dislike-16-regular';
+import './ChatActions.css';
+import { useState } from 'react';
+
+interface ChatActionsProps {
+  interaction: Parameters<Parameters<typeof ChatInteractions.Wrapper>[0]['children']>[0];
+}
+
+export default function ChatActions({ interaction }: ChatActionsProps) {
+  const [disliked, setDisliked] = useState(false);
+
+  const dislikeMessage = () => {
+    setDisliked(true);
+  };
+
+  if (interaction.loading) {
+    return null;
+  }
+
+  return (
+    <ul className="chat-actions">
+      <li>
+        <ChatInteractions.RegenerateLatest interaction={interaction} className="chat-action">
+          <ArrowSync20Regular width={18} height={18} />
+        </ChatInteractions.RegenerateLatest>
+      </li>
+      <li>
+        <ChatInteractions.CopyMessage interaction={interaction} className="chat-action">
+          {(copied: boolean) =>
+            copied ? (
+              <>
+                <Checkmark16Regular width={18} height={18} />
+                <span className="sr-only">Copied</span>
+              </>
+            ) : (
+              <>
+                <Copy16Regular width={18} height={18} />
+                <span className="sr-only">Copy</span>
+              </>
+            )
+          }
+        </ChatInteractions.CopyMessage>
+      </li>
+      <li>
+        <button
+          type="button"
+          className={`chat-action ${disliked ? 'chat-action--disliked' : ''}`}
+          aria-label="Upvote response"
+          onClick={dislikeMessage}
+        >
+          <ThumbDislike16Regular width={18} height={18} />
+        </button>
+      </li>
+    </ul>
+  );
+}
diff --git a/src/components/patterns/Searchbox/ChatSources.css b/src/components/patterns/Searchbox/ChatSources.css
new file mode 100644
index 0000000000..843e276c64
--- /dev/null
+++ b/src/components/patterns/Searchbox/ChatSources.css
@@ -0,0 +1,102 @@
+@layer patterns {
+  .chat-sources-scroll-container {
+    position: relative;
+    overflow: hidden;
+
+    &::after {
+      content: '';
+      position: absolute;
+      top: 0;
+      right: 0;
+      bottom: 0;
+      width: var(--space-16);
+      pointer-events: none;
+      background: linear-gradient(
+        to right,
+        transparent,
+        color-mix(in oklch, var(--color-bg-primary) 15%, transparent) 20%,
+        color-mix(in oklch, var(--color-bg-primary) 40%, transparent) 40%,
+        color-mix(in oklch, var(--color-bg-primary) 70%, transparent) 65%,
+        var(--color-bg-primary) 90%
+      );
+    }
+  }
+
+  .chat-sources {
+    display: flex;
+    flex-wrap: nowrap;
+    align-items: stretch;
+    gap: var(--space-3);
+    margin-top: var(--space-8);
+    margin-bottom: 0;
+    overflow-x: scroll;
+    scroll-behavior: smooth;
+    -ms-overflow-style: none;
+    scrollbar-width: none;
+    padding-left: 0;
+    list-style: none;
+
+    &::-webkit-scrollbar {
+      display: none;
+    }
+  }
+
+  .chat-sources-item {
+    display: flex;
+    max-width: 100%;
+    height: 100%;
+    align-items: center;
+    gap: var(--space-2);
+    font-size: var(--font-size-base);
+  }
+
+  .chat-sources-link {
+    display: block;
+    width: var(--space-64);
+    height: 100%;
+    border-radius: var(--radius-xl);
+    background-color: var(--color-bg-tertiary);
+    padding: var(--space-3);
+    color: var(--color-text-primary);
+    text-decoration: none;
+    cursor: pointer;
+    transition: var(--transition-colors);
+
+    &:hover {
+      background-color: var(--color-bg-secondary);
+    }
+
+    &:focus {
+      background-color: var(--color-bg-mute);
+      outline: none;
+    }
+  }
+
+  .chat-sources-title {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+    font-size: var(--font-size-sm);
+    font-weight: var(--font-weight-semibold);
+    color: var(--color-text-secondary);
+    overflow: hidden;
+    -webkit-box-orient: vertical;
+    -webkit-line-clamp: 1;
+    margin: 0;
+
+    svg {
+      flex-shrink: 0;
+    }
+  }
+
+  .chat-sources-excerpt {
+    margin-top: var(--space-2);
+    margin-bottom: 0;
+    font-size: var(--font-size-sm);
+    color: var(--color-text-tertiary);
+    overflow: hidden;
+    display: -webkit-box;
+    -webkit-box-orient: vertical;
+    -webkit-line-clamp: 2;
+  }
+}
diff --git a/src/components/patterns/Searchbox/ChatSources.tsx b/src/components/patterns/Searchbox/ChatSources.tsx
new file mode 100644
index 0000000000..0aee5577e4
--- /dev/null
+++ b/src/components/patterns/Searchbox/ChatSources.tsx
@@ -0,0 +1,43 @@
+import type { Interaction, AnyObject } from '@orama/core';
+import { ChatInteractions } from '@orama/ui/components';
+import type { FC } from 'react';
+import Link20Regular from '~icons/fluent/link-20-regular';
+import './ChatSources.css';
+
+type ChatSourcesProps = {
+  interaction: Interaction;
+};
+
+export const ChatSources: FC<ChatSourcesProps> = ({ interaction }) => {
+  if (!interaction?.sources) {
+    return null;
+  }
+
+  return (
+    <div className="chat-sources-scroll-container">
+      <ChatInteractions.Sources interaction={interaction} className="chat-sources" itemClassName="">
+        {(document: AnyObject, index: number) => (
+          <div className="chat-sources-item" key={index}>
+            {!!document.title && typeof document.title === 'string' && (
+              <a
+                href={document.path as string}
+                className="chat-sources-link"
+                data-focus-on-arrow-nav
+              >
+                <h3 className="chat-sources-title">
+                  <Link20Regular width={16} height={16} />
+                  {(document.title as string).slice(0, 30) || ''}
+                  {(document.title as string).length > 30 ? '...' : ''}
+                </h3>
+                <p className="chat-sources-excerpt">
+                  {(document.description as string).slice(0, 60)}
+                  ...
+                </p>
+              </a>
+            )}
+          </div>
+        )}
+      </ChatInteractions.Sources>
+    </div>
+  );
+};
diff --git a/src/components/patterns/Searchbox/Search.css b/src/components/patterns/Searchbox/Search.css
new file mode 100644
index 0000000000..b91b58756d
--- /dev/null
+++ b/src/components/patterns/Searchbox/Search.css
@@ -0,0 +1,324 @@
+@layer patterns {
+  /* ============================================
+     Search Tab
+     ============================================ */
+
+  .search-tab-panel {
+    display: flex;
+    flex-direction: column;
+    overflow: hidden;
+    flex: 1;
+    min-height: 0;
+  }
+
+  .search-tabs-scroll-container {
+    position: relative;
+    overflow: hidden;
+
+    &::after {
+      content: '';
+      position: absolute;
+      top: 0;
+      right: 0;
+      bottom: 0;
+      width: var(--space-10);
+      pointer-events: none;
+      background: linear-gradient(to right, transparent, var(--color-bg-primary));
+    }
+  }
+
+  .search-tabs {
+    display: flex;
+    gap: var(--space-1);
+    overflow-x: auto;
+    scrollbar-width: none;
+    list-style: none;
+
+    &::-webkit-scrollbar {
+      display: none;
+    }
+  }
+
+  .search-tab {
+    font-size: var(--font-size-base);
+    color: var(--color-text-secondary);
+    background: none;
+    border-radius: var(--radius-base);
+    padding: var(--space-1-5) var(--space-3);
+    cursor: pointer;
+    transition:
+      color var(--duration-150) var(--ease-in-out),
+      background-color var(--duration-150) var(--ease-in-out);
+    border: var(--border-width-1) solid transparent;
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+
+    &:hover:not(.search-tab--selected) {
+      color: var(--color-text-primary);
+      background-color: var(--color-bg-secondary);
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+
+    &--selected,
+    &[data-state='active'] {
+      font-weight: var(--font-weight-semibold);
+      color: var(--color-text-primary);
+      background-color: var(--color-bg-tertiary);
+      border: var(--border-width-1) solid var(--color-border-tertiary);
+    }
+  }
+
+  .search-tab-count {
+    margin: 0;
+  }
+
+  .search-input-wrapper {
+    padding: var(--space-3) var(--space-4);
+    border-top: var(--border-width-1) solid var(--color-border-secondary);
+    background-color: var(--color-bg-secondary);
+    flex-shrink: 0;
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+    width: 100%;
+  }
+
+  .search-input-form {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+  }
+
+  .search-ask-button {
+    display: flex;
+    align-items: center;
+    gap: var(--space-1-5);
+    padding: var(--space-1) var(--space-2-5);
+    border-radius: var(--radius-base);
+    border: var(--border-width-1) solid var(--color-border-secondary);
+    background-color: var(--color-bg-tertiary);
+    color: var(--color-text-secondary);
+    font-size: var(--font-size-sm);
+    font-family: inherit;
+    cursor: pointer;
+    flex-shrink: 0;
+    transition:
+      background-color var(--duration-150) var(--ease-in-out),
+      color var(--duration-150) var(--ease-in-out),
+      border-color var(--duration-150) var(--ease-in-out);
+
+    svg {
+      color: var(--color-icon-primary);
+    }
+
+    &:hover {
+      background-color: var(--color-bg-mute);
+      color: var(--color-text-primary);
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+
+    &:disabled {
+      opacity: 0.8;
+      cursor: not-allowed;
+      background-color: var(--color-bg-secondary);
+      color: var(--color-text-tertiary);
+      border-color: var(--color-border-secondary);
+
+      svg {
+        color: var(--color-icon-secondary);
+      }
+    }
+  }
+
+  .search-input-field {
+    width: 100%;
+    font-size: var(--font-size-md);
+    color: var(--color-text-primary);
+    flex-grow: 1;
+    background: none;
+    border: none;
+    outline: none;
+    font-family: inherit;
+
+    &::placeholder {
+      color: var(--color-text-tertiary);
+    }
+  }
+
+  .search-results-wrapper {
+    overflow-y: auto;
+    flex: 1;
+    min-height: 0;
+    padding: var(--space-6);
+    padding-top: var(--space-3);
+
+    /* Firefox */
+    scrollbar-width: thin;
+    scrollbar-color: var(--color-border-primary) transparent;
+
+    /* Chrome / Safari / Edge */
+    &::-webkit-scrollbar {
+      width: 6px;
+    }
+
+    &::-webkit-scrollbar-track {
+      background: transparent;
+    }
+
+    &::-webkit-scrollbar-thumb {
+      background-color: var(--color-border-primary);
+      border-radius: 9999px;
+    }
+  }
+
+  .search-no-results {
+    display: flex;
+    flex-direction: column;
+    align-items: center;
+    justify-content: center;
+    padding: var(--space-8) var(--space-4);
+    color: var(--color-text-secondary);
+    font-size: var(--font-size-sm);
+  }
+
+  .search-loading {
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-1);
+    padding: var(--space-6);
+    padding-top: var(--space-3);
+  }
+
+  .search-skeleton-item {
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+    padding: var(--space-4) var(--space-2);
+  }
+
+  .search-skeleton-icon {
+    flex-shrink: 0;
+    width: 1.25rem;
+    height: 1.25rem;
+    border-radius: var(--radius-base);
+    background: linear-gradient(
+      90deg,
+      var(--color-bg-tertiary) 25%,
+      var(--color-bg-secondary) 50%,
+      var(--color-bg-tertiary) 75%
+    );
+    background-size: 400% 100%;
+    animation: search-shimmer 1.4s ease-in-out infinite;
+  }
+
+  .search-skeleton-text {
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-2);
+    flex: 1;
+  }
+
+  .search-skeleton-line {
+    border-radius: var(--radius-full);
+    background: linear-gradient(
+      90deg,
+      var(--color-bg-tertiary) 25%,
+      var(--color-bg-secondary) 50%,
+      var(--color-bg-tertiary) 75%
+    );
+    background-size: 400% 100%;
+    animation: search-shimmer 1.4s ease-in-out infinite;
+
+    &--title {
+      height: 0.75rem;
+    }
+    &--desc {
+      height: 0.625rem;
+    }
+  }
+
+  @keyframes search-shimmer {
+    0% {
+      background-position: 200% 0;
+    }
+    100% {
+      background-position: -200% 0;
+    }
+  }
+
+  .search-results-group-title {
+    font-size: var(--font-size-base);
+    color: var(--color-text-secondary);
+    text-transform: uppercase;
+    letter-spacing: var(--letter-spacing-wide);
+    margin: var(--space-4) 0;
+  }
+
+  .search-results-list {
+    list-style: none;
+    margin: var(--space-4) 0 var(--space-6) 0;
+    padding: 0;
+  }
+
+  .search-result-item {
+    border-radius: var(--radius-base);
+    overflow: hidden;
+  }
+
+  .search-result-link {
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+    padding: var(--space-4) var(--space-2);
+    border-radius: var(--radius-base);
+    color: var(--color-text-primary);
+    text-decoration: none;
+    transition: background-color var(--duration-150) var(--ease-in-out);
+
+    svg {
+      flex-shrink: 0;
+    }
+
+    &:hover,
+    &:focus-visible {
+      background-color: var(--color-bg-secondary);
+      outline: none;
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+  }
+
+  .search-result-description {
+    font-size: var(--font-size-base);
+    color: color-mix(in oklch, var(--color-text-primary) 80%, transparent);
+    letter-spacing: var(--letter-spacing-wide);
+    margin: var(--space-1) 0 0 0;
+    display: -webkit-box;
+    -webkit-line-clamp: 2;
+    -webkit-box-orient: vertical;
+    overflow: hidden;
+  }
+
+  .search-result-breadcrumb {
+    font-size: var(--font-size-base);
+    font-weight: var(--font-weight-medium);
+    color: var(--color-text-tertiary);
+    margin: 0 0 var(--space-2) 0;
+  }
+
+  .search-result-title {
+    font-size: var(--font-size-base);
+    color: var(--color-text-primary);
+    font-weight: var(--font-weight-medium);
+    margin: 0;
+  }
+}
diff --git a/src/components/patterns/Searchbox/Search.tsx b/src/components/patterns/Searchbox/Search.tsx
new file mode 100644
index 0000000000..0e4f59d8a4
--- /dev/null
+++ b/src/components/patterns/Searchbox/Search.tsx
@@ -0,0 +1,186 @@
+import { useEffect, useRef, useState } from 'react';
+import { FacetTabs, SearchInput, SearchResults } from '@orama/ui/components';
+import type { Hit } from '@orama/core';
+import SearchNoResults from './SearchNoResults';
+import './Search.css';
+import Document20Regular from '~icons/fluent/document-20-regular';
+import Search16Regular from '~icons/fluent/search-16-regular';
+import Sparkle16Filled from '~icons/fluent/sparkle-16-filled';
+import { useSearch } from '@orama/ui/hooks/useSearch';
+import { useTranslations } from '@/i18n/utils';
+import type { ui } from '@/i18n/locales';
+import { useChat } from '@orama/ui/hooks/useChat';
+
+type DocDocument = {
+  title: string;
+  description?: string;
+  category?: string;
+  path?: string;
+  content?: string;
+  version?: string;
+};
+
+function getPathBreadcrumb(path: string, category: string, t: (key: string) => string): string {
+  const rootLabel = t(category);
+  const categorySlug = rootLabel.toLowerCase();
+
+  const segments = path
+    .split('/')
+    .filter(Boolean)
+    .slice(1) // remove language prefix (e.g., 'en')
+    .filter((s) => s !== categorySlug) // remove redundant category segment
+    .slice(0, -1) // remove last segment (the document page itself)
+    .map((s) =>
+      s
+        .split('-')
+        .map((w) => w.charAt(0).toUpperCase() + w.slice(1))
+        .join(' ')
+    );
+
+  return [rootLabel, ...segments].join(' > ');
+}
+
+interface SearchProps {
+  lang: string;
+  placeholder: string;
+  mode: 'search' | 'chat';
+  onModeChange: (mode: 'search' | 'chat') => void;
+}
+
+export default function Search({ lang, placeholder, mode, onModeChange }: SearchProps) {
+  const t = useTranslations(lang as keyof typeof ui);
+  const {
+    context: { searchTerm, selectedFacet },
+  } = useSearch();
+  const { ask } = useChat();
+  const [lastChatTerm, setLastChatTerm] = useState<string>();
+
+  const inputWrapperRef = useRef<HTMLDivElement>(null);
+
+  useEffect(() => {
+    if (mode === 'search') {
+      const id = setTimeout(() => {
+        inputWrapperRef.current?.querySelector('input')?.focus();
+      }, 50);
+      return () => clearTimeout(id);
+    }
+  }, [mode]);
+
+  const enterChat = () => {
+    onModeChange('chat');
+    setLastChatTerm(searchTerm);
+    ask({ query: searchTerm ?? '' });
+  };
+
+  return (
+    <>
+      <SearchResults.Loading className="search-loading">
+        {[65, 80, 50].map((w) => (
+          <div key={w} className="search-skeleton-item">
+            <div className="search-skeleton-icon" />
+            <div className="search-skeleton-text">
+              <div
+                className="search-skeleton-line search-skeleton-line--title"
+                style={{ width: `${w}%` }}
+              />
+              <div
+                className="search-skeleton-line search-skeleton-line--desc"
+                style={{ width: `${w - 15}%` }}
+              />
+            </div>
+          </div>
+        ))}
+      </SearchResults.Loading>
+
+      <SearchNoResults onSuggestionClick={enterChat} />
+      <div className="search-tabs-scroll-container">
+        <FacetTabs.Wrapper>
+          <FacetTabs.List className="search-tabs">
+            {(group, isSelected) => (
+              <>
+                <FacetTabs.Item
+                  isSelected={group.name === selectedFacet}
+                  group={group}
+                  filterBy="category"
+                  searchParams={{
+                    term: searchTerm ?? '',
+                  }}
+                  className={`search-tab ${isSelected ? 'search-tab--selected' : ''}`}
+                >
+                  {t(group.name)}
+                  <span className="search-tab-count">({group.count})</span>
+                </FacetTabs.Item>
+              </>
+            )}
+          </FacetTabs.List>
+        </FacetTabs.Wrapper>
+      </div>
+
+      <SearchResults.GroupsWrapper groupBy="category" className="search-results-wrapper">
+        {(group) => (
+          <div key={group.name} className="search-results-group">
+            <h2 className="search-results-group-title">{t(group.name)}</h2>
+            <SearchResults.GroupList group={group} className="search-results-list">
+              {(result: Hit) => {
+                const document = result.document as DocDocument;
+                return (
+                  <a
+                    href={document?.path || '#'}
+                    className="search-result-link"
+                    data-focus-on-arrow-nav
+                  >
+                    <Document20Regular width={20} height={20} />
+                    <div>
+                      <p className="search-result-breadcrumb">
+                        {getPathBreadcrumb(document?.path ?? '', document?.category ?? '', t)}
+                      </p>
+                      <h3 className="search-result-title">{document?.title}</h3>
+                      {document?.description && (
+                        <p className="search-result-description">{document.description}</p>
+                      )}
+                    </div>
+                  </a>
+                );
+              }}
+            </SearchResults.GroupList>
+          </div>
+        )}
+      </SearchResults.GroupsWrapper>
+
+      <SearchInput.Provider>
+        <SearchInput.Form className="search-input-form">
+          <SearchInput.Wrapper className="search-input-wrapper" ref={inputWrapperRef}>
+            <Search16Regular width={18} height={18} className="search-input-icon" />
+            <SearchInput.Input
+              className="search-input-field"
+              placeholder={placeholder}
+              searchOnType
+              searchParams={{
+                boost: {
+                  title: 10,
+                  description: 4,
+                },
+                groupBy: {
+                  properties: ['category'],
+                },
+                facets: {
+                  category: {},
+                },
+              }}
+            />
+            <button
+              className="search-ask-button"
+              onClick={() => enterChat()}
+              disabled={!searchTerm || searchTerm === lastChatTerm}
+              type="submit"
+              aria-label="Switch to chat mode"
+            >
+              <Sparkle16Filled width={14} height={14} />
+              Get summary
+            </button>
+          </SearchInput.Wrapper>
+        </SearchInput.Form>
+      </SearchInput.Provider>
+    </>
+  );
+}
diff --git a/src/components/patterns/Searchbox/SearchFooter.css b/src/components/patterns/Searchbox/SearchFooter.css
new file mode 100644
index 0000000000..3151386ebc
--- /dev/null
+++ b/src/components/patterns/Searchbox/SearchFooter.css
@@ -0,0 +1,40 @@
+@layer patterns {
+  .search-footer-shortcuts {
+    display: none;
+    align-items: center;
+    gap: var(--space-3);
+
+    span {
+      margin: 0;
+    }
+
+    @media (--md-up) {
+      display: flex;
+    }
+  }
+
+  .search-footer-shortcut {
+    display: flex;
+    align-items: center;
+    gap: var(--space-1-5);
+    font-size: var(--font-size-sm);
+    color: var(--color-text-primary);
+  }
+
+  .search-footer-kbd {
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    font-family: var(--font-mono);
+    font-size: var(--font-size-sm);
+    background-color: var(--color-bg-secondary);
+    border-radius: var(--radius-md);
+    padding: var(--space-1);
+  }
+
+  .search-footer-branding {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+  }
+}
diff --git a/src/components/patterns/Searchbox/SearchFooter.tsx b/src/components/patterns/Searchbox/SearchFooter.tsx
new file mode 100644
index 0000000000..951f39d540
--- /dev/null
+++ b/src/components/patterns/Searchbox/SearchFooter.tsx
@@ -0,0 +1,41 @@
+import ArrowTurnDownRight48Regular from '~icons/fluent/arrow-turn-down-right-48-regular';
+import ArrowDown16Regular from '~icons/fluent/arrow-down-16-regular';
+import ArrowUp16Regular from '~icons/fluent/arrow-up-16-regular';
+import OramaLogoLight from '../../../icons/orama-logo-light.svg?react';
+import OramaLogoDark from '../../../icons/orama-logo-dark.svg?react';
+import './SearchFooter.css';
+
+export default function SearchFooter() {
+  return (
+    <>
+      <div className="search-footer-shortcuts">
+        <div className="search-footer-shortcut">
+          <kbd className="search-footer-kbd">
+            <ArrowTurnDownRight48Regular width={16} height={16} />
+          </kbd>
+          <span>select</span>
+        </div>
+        <div className="search-footer-shortcut">
+          <kbd className="search-footer-kbd">
+            <ArrowDown16Regular width={16} height={16} />
+          </kbd>
+          <kbd className="search-footer-kbd">
+            <ArrowUp16Regular width={16} height={16} />
+          </kbd>
+          <span>navigate</span>
+        </div>
+        <div className="search-footer-shortcut">
+          <kbd className="search-footer-kbd">esc</kbd>
+          <span>close</span>
+        </div>
+      </div>
+      <div className="search-footer-branding">
+        <small>Powered by</small>
+        <a href="https://orama.com/" target="_blank" rel="noopener noreferrer">
+          <OramaLogoLight className="orama-logo-light" aria-label="Orama logo" />
+          <OramaLogoDark className="orama-logo-dark" aria-label="Orama logo" />
+        </a>
+      </div>
+    </>
+  );
+}
diff --git a/src/components/patterns/Searchbox/SearchNoResults.css b/src/components/patterns/Searchbox/SearchNoResults.css
new file mode 100644
index 0000000000..b9960b535e
--- /dev/null
+++ b/src/components/patterns/Searchbox/SearchNoResults.css
@@ -0,0 +1,55 @@
+@layer patterns {
+  .search-empty-image {
+    width: var(--size-36);
+  }
+
+  :root[data-theme='light'] .search-empty-image--dark,
+  :root[data-theme='dark'] .search-empty-image--light {
+    display: none;
+  }
+
+  .search-image-wrapper {
+    display: block;
+    text-align: center;
+  }
+
+  .search-suggestions {
+    margin-top: var(--space-3);
+
+    ul {
+      display: flex;
+      align-items: center;
+      justify-content: center;
+      gap: var(--space-3);
+      padding-left: 0;
+      flex-wrap: wrap;
+      list-style: none;
+    }
+
+    li {
+    }
+  }
+
+  .search-suggestion__item {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+    padding: var(--space-1-5) var(--space-3);
+    border-radius: var(--radius-base);
+    border: var(--border-width-1) solid var(--color-border-primary);
+    color: var(--color-text-primary);
+    cursor: pointer;
+    transition:
+      background-color 0.2s,
+      color 0.2s;
+
+    &:hover {
+      background-color: var(--color-bg-tertiary);
+      color: var(--color-text-primary);
+    }
+
+    svg {
+      color: var(--color-icon-primary);
+    }
+  }
+}
diff --git a/src/components/patterns/Searchbox/SearchNoResults.tsx b/src/components/patterns/Searchbox/SearchNoResults.tsx
new file mode 100644
index 0000000000..6df01296f1
--- /dev/null
+++ b/src/components/patterns/Searchbox/SearchNoResults.tsx
@@ -0,0 +1,60 @@
+import { SearchResults, Suggestions } from '@orama/ui/components';
+import Sparkle20Filled from '~icons/fluent/sparkle-20-filled';
+import ExpressLogoWhite from '../../../icons/logo-express-white.svg?react';
+import ExpressLogoBlack from '../../../icons/logo-express-black.svg?react';
+import './SearchNoResults.css';
+
+const SUGGESTIONS = [
+  'Can you give me a guide to install Express.js',
+  'What are the advantages of version 5',
+  'What are Express Superpowers',
+];
+
+interface SearchNoResultsProps {
+  onSuggestionClick?: (text: string) => void;
+}
+
+export default function SearchNoResults({ onSuggestionClick }: SearchNoResultsProps) {
+  return (
+    <SearchResults.NoResults className="search-no-results">
+      {(searchTerm) => (
+        <>
+          {searchTerm ? (
+            <span>
+              No results for &ldquo;<strong>{searchTerm}</strong>&rdquo;
+            </span>
+          ) : (
+            <>
+              <div className="search-image-wrapper">
+                <ExpressLogoWhite
+                  className="search-empty-image search-empty-image--dark"
+                  aria-hidden
+                />
+                <ExpressLogoBlack
+                  className="search-empty-image search-empty-image--light"
+                  aria-hidden
+                />
+              </div>
+              <p>What would you like to know about Express and its features?</p>
+              <Suggestions.Wrapper className="search-suggestions">
+                <ul>
+                  {SUGGESTIONS.map((text) => (
+                    <li key={text}>
+                      <Suggestions.Item
+                        onClick={() => onSuggestionClick?.(text)}
+                        className="search-suggestion__item"
+                      >
+                        <Sparkle20Filled width={20} height={20} />
+                        {text}
+                      </Suggestions.Item>
+                    </li>
+                  ))}
+                </ul>
+              </Suggestions.Wrapper>
+            </>
+          )}
+        </>
+      )}
+    </SearchResults.NoResults>
+  );
+}
diff --git a/src/components/patterns/Searchbox/Searchbox.css b/src/components/patterns/Searchbox/Searchbox.css
new file mode 100644
index 0000000000..2db415419a
--- /dev/null
+++ b/src/components/patterns/Searchbox/Searchbox.css
@@ -0,0 +1,280 @@
+@layer patterns {
+  .search-trigger {
+    display: flex;
+    align-items: center;
+    gap: var(--space-6);
+    background-color: transparent;
+    border-radius: var(--radius-base);
+    border: 0;
+    color: var(--color-text-tertiary);
+    cursor: pointer;
+    transition:
+      background-color 0.2s,
+      border-color 0.2s;
+
+    &:hover {
+      background-color: var(--color-bg-secondary);
+      border-color: var(--color-border-secondary);
+      outline: none;
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+
+    span {
+      line-height: var(--line-height-snug);
+
+      @media (--xs-only) {
+        display: none;
+      }
+    }
+
+    svg {
+      color: var(--color-icon-primary);
+    }
+
+    @media (--md-up) {
+      border: 1px solid var(--color-border-secondary);
+      padding: var(--space-1-5) var(--space-1-5) var(--space-1-5) var(--space-2);
+    }
+  }
+
+  .search-trigger-content {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+    font-size: var(--font-size-sm);
+
+    span {
+      margin: 0;
+    }
+  }
+
+  .search-trigger-icon {
+    border-radius: var(--radius-base);
+    transition: background-color var(--duration-200) var(--ease-in-out);
+    flex-shrink: 0;
+
+    @media (--xs-only) {
+      background-color: var(--color-bg-secondary);
+      padding: var(--space-2);
+
+      &:hover {
+        background-color: var(--color-bg-mute);
+      }
+    }
+  }
+
+  .search-trigger-shortcut {
+    margin-left: auto;
+    font-size: var(--font-size-xs);
+    color: var(--color-text-secondary);
+    background-color: var(--color-bg-secondary);
+    padding: var(--space-1) var(--space-2);
+    border-radius: var(--radius-base);
+
+    @media (--xs-only) {
+      display: none;
+    }
+  }
+
+  .search-modal-overlay {
+    background-color: var(--color-overlay);
+    z-index: var(--z-index-modal-overlay);
+
+    @media (--xs-only) {
+      margin-top: 6rem;
+      height: calc(100vh - 6rem);
+    }
+  }
+
+  .search-modal-inner {
+    background-color: color-mix(in oklch, var(--color-bg-primary) 90%, transparent);
+    width: 100%;
+    display: flex;
+    flex-direction: column;
+    overflow: hidden;
+    backdrop-filter: blur(2px);
+    margin: 0 auto;
+
+    > section {
+      height: 100%;
+    }
+
+    @media (--xs-only) {
+      max-width: 100%;
+      border-radius: 0;
+    }
+
+    @media (--md-up) {
+      border-radius: var(--radius-lg);
+      margin-top: var(--size-14);
+      width: 80%;
+      max-width: 80rem;
+      height: 80vh;
+      max-height: 70rem;
+    }
+  }
+
+  /* ============================================
+     Modal Content
+     ============================================ */
+
+  .search-modal-content {
+    display: flex;
+    flex-direction: column;
+    height: 100%;
+    position: relative;
+    overflow: hidden;
+  }
+
+  /* ============================================
+     Modal Header (tabs + close button)
+     ============================================ */
+
+  .search-modal-header {
+    display: flex;
+    align-items: center;
+    justify-content: space-between;
+    padding: var(--space-2) var(--space-4);
+    flex-shrink: 0;
+    border-bottom: var(--border-width-1) solid var(--color-border-secondary);
+  }
+
+  .search-modal-header-left {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+  }
+
+  .search-modal-header-right {
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+  }
+
+  .search-modal-footer {
+    padding: var(--space-5) var(--space-6);
+    background-color: var(--color-bg-tertiary);
+    display: flex;
+    gap: var(--space-3);
+    align-items: center;
+    justify-content: flex-end;
+
+    @media (--md-up) {
+      justify-content: space-between;
+    }
+
+    small {
+      margin: 0;
+    }
+
+    .orama-logo-light,
+    .orama-logo-dark {
+      width: var(--size-16);
+      height: auto;
+    }
+
+    :root[data-theme='dark'] & .orama-logo-light,
+    :root[data-theme='light'] & .orama-logo-dark {
+      display: none;
+    }
+  }
+
+  .search-modal-back {
+    display: flex;
+    align-items: center;
+    gap: var(--space-1-5);
+    padding: var(--space-1) var(--space-2);
+    border-radius: var(--radius-base);
+    border: none;
+    background: none;
+    font-size: var(--font-size-sm);
+    cursor: pointer;
+    transition:
+      color var(--duration-150) var(--ease-in-out),
+      background-color var(--duration-150) var(--ease-in-out);
+
+    &:hover {
+      color: var(--color-text-primary);
+      background-color: var(--color-bg-secondary);
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+  }
+
+  .search-modal-chat {
+    display: flex;
+    align-items: center;
+    gap: var(--space-1-5);
+    border-radius: var(--radius-base);
+    border: none;
+    background: none;
+    color: var(--color-text-secondary);
+    font-size: var(--font-size-sm);
+    cursor: pointer;
+    position: relative;
+    transition:
+      color var(--duration-150) var(--ease-in-out),
+      background-color var(--duration-150) var(--ease-in-out);
+
+    span {
+      margin: 0;
+    }
+
+    .search-modal-back + & {
+      &::before {
+        content: '|';
+        position: absolute;
+        left: calc(-1 * var(--space-3));
+        opacity: 0.8;
+        color: var(--color-border-primary);
+      }
+    }
+  }
+
+  .chat-interactions-count {
+    background-color: var(--color-bg-inverse);
+    color: var(--color-text-inverse);
+    padding: 0 var(--space-2);
+    border-radius: var(--radius-base);
+    font-size: var(--font-size-sm);
+  }
+
+  .search-modal-body {
+    flex-grow: 1;
+    display: flex;
+    flex-direction: column;
+    justify-content: space-between;
+    overflow-y: auto;
+  }
+
+  .search-modal-close {
+    display: flex;
+    align-items: center;
+    justify-content: center;
+    width: var(--size-8);
+    height: var(--size-8);
+    border-radius: var(--radius-base);
+    border: none;
+    background: none;
+    color: var(--color-text-secondary);
+    cursor: pointer;
+    transition:
+      color var(--duration-150) var(--ease-in-out),
+      background-color var(--duration-150) var(--ease-in-out);
+    flex-shrink: 0;
+
+    &:hover {
+      color: var(--color-text-primary);
+      background-color: var(--color-bg-secondary);
+    }
+
+    &:focus-visible {
+      outline: 1px solid var(--color-focus-ring);
+    }
+  }
+}
diff --git a/src/components/patterns/Searchbox/Searchbox.tsx b/src/components/patterns/Searchbox/Searchbox.tsx
new file mode 100644
index 0000000000..94f67454c3
--- /dev/null
+++ b/src/components/patterns/Searchbox/Searchbox.tsx
@@ -0,0 +1,149 @@
+import { useEffect, useState } from 'react';
+import { createPortal } from 'react-dom';
+import { OramaCloud } from '@orama/core';
+import { ChatRoot, Modal, SearchRoot } from '@orama/ui/components';
+import { useSearch } from '@orama/ui/hooks/useSearch';
+import Search from './Search';
+import SearchSparkle16Regular from '~icons/fluent/search-sparkle-16-regular';
+import ArrowLeft24Regular from '~icons/fluent/arrow-left-24-regular';
+import Dismiss16Regular from '~icons/fluent/dismiss-16-regular';
+import Chat from './Chat';
+import SearchFooter from './SearchFooter';
+import './orama-styles.css';
+import './Searchbox.css';
+import { useChat } from '@orama/ui/hooks/index';
+
+const orama = import.meta.env.PUBLIC_ORAMA_PROJECT_ID
+  ? new OramaCloud({
+      projectId: import.meta.env.PUBLIC_ORAMA_PROJECT_ID,
+      apiKey: import.meta.env.PUBLIC_ORAMA_API_KEY,
+    })
+  : null;
+
+interface SearchboxProps {
+  lang: string;
+  placeholder: string;
+  ariaLabel: string;
+}
+
+interface SearchModalHeaderProps {
+  mode: 'search' | 'chat';
+  onModeChange: (mode: 'search' | 'chat') => void;
+}
+
+function SearchModalHeader({ mode, onModeChange }: SearchModalHeaderProps) {
+  const {
+    context: { searchTerm },
+    reset,
+  } = useSearch();
+  const {
+    context: { interactions },
+  } = useChat();
+
+  function handleBackToSearch() {
+    if (mode === 'chat') {
+      onModeChange('search');
+      return;
+    }
+
+    reset();
+  }
+
+  return (
+    <div className="search-modal-header">
+      <div className="search-modal-header-left">
+        {(mode === 'chat' || searchTerm) && (
+          <button
+            className="search-modal-back"
+            role="tab"
+            type="button"
+            aria-label="Back to search"
+            onClick={handleBackToSearch}
+          >
+            <ArrowLeft24Regular width={16} height={16} />
+          </button>
+        )}
+        {interactions && interactions.length > 0 && (
+          <button className="search-modal-chat" role="tab" onClick={() => onModeChange('chat')}>
+            <span className="chat-interactions-count">{interactions.length}</span>
+            <span className="chat-user-prompt-preview">
+              question{interactions.length > 1 ? 's' : ''}
+            </span>
+          </button>
+        )}
+      </div>
+      <div className="search-modal-header-right">
+        <Modal.Close className="search-modal-close" aria-label="Close search">
+          <Dismiss16Regular width={18} height={18} />
+        </Modal.Close>
+      </div>
+    </div>
+  );
+}
+
+export default function Searchbox({ lang, placeholder, ariaLabel }: SearchboxProps) {
+  const [shortcutKey, setShortcutKey] = useState('⌘ K');
+  const [mounted, setMounted] = useState(false);
+  const [mode, setMode] = useState<'search' | 'chat'>('search');
+
+  useEffect(() => {
+    setMounted(true);
+    const nav = navigator as Navigator & { userAgentData?: { platform: string } };
+    const isMac = nav.userAgentData?.platform
+      ? /mac/i.test(nav.userAgentData.platform)
+      : /Mac|iPhone|iPod|iPad/i.test(navigator.userAgent);
+    setShortcutKey(isMac ? '⌘ K' : 'Ctrl K');
+  }, []);
+
+  return (
+    <SearchRoot client={orama}>
+      <ChatRoot client={orama} askOptions={{ throttle_delay: 50 }}>
+        <Modal.Root>
+          <Modal.Trigger
+            className="search-trigger"
+            enableCmdK
+            disabled={!orama}
+            aria-label={ariaLabel}
+          >
+            <div className="search-trigger-content">
+              <div className="search-trigger-icon">
+                <SearchSparkle16Regular width={18} height={18} />
+              </div>
+              <span>{placeholder}</span>
+            </div>
+            <div className="search-trigger-shortcut">
+              <span className="shortcut-key">{shortcutKey}</span>
+            </div>
+          </Modal.Trigger>
+
+          {orama &&
+            mounted &&
+            createPortal(
+              <Modal.Wrapper closeOnEscape closeOnOutsideClick className="search-modal-overlay">
+                <Modal.Inner className="search-modal-inner">
+                  <Modal.Content className="search-modal-content">
+                    <SearchModalHeader mode={mode} onModeChange={setMode} />
+                    <div className="search-modal-body">
+                      <div className={mode === 'search' ? 'contents' : 'hidden'}>
+                        <Search
+                          lang={lang}
+                          placeholder="Start typing: What's new in Express 5?"
+                          mode={mode}
+                          onModeChange={setMode}
+                        />
+                      </div>
+                      {mode === 'chat' && <Chat />}
+                    </div>
+                    <div className="search-modal-footer">
+                      <SearchFooter />
+                    </div>
+                  </Modal.Content>
+                </Modal.Inner>
+              </Modal.Wrapper>,
+              document.body
+            )}
+        </Modal.Root>
+      </ChatRoot>
+    </SearchRoot>
+  );
+}
diff --git a/src/components/patterns/Searchbox/orama-styles.css b/src/components/patterns/Searchbox/orama-styles.css
new file mode 100644
index 0000000000..743d58e7aa
--- /dev/null
+++ b/src/components/patterns/Searchbox/orama-styles.css
@@ -0,0 +1 @@
+@import '@orama/ui/styles.css' layer(orama);
diff --git a/src/components/patterns/Sidebar/Sidebar.astro b/src/components/patterns/Sidebar/Sidebar.astro
new file mode 100644
index 0000000000..3d7c4c3d55
--- /dev/null
+++ b/src/components/patterns/Sidebar/Sidebar.astro
@@ -0,0 +1,90 @@
+---
+import './Sidebar.css';
+import type { HTMLAttributes } from 'astro/types';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+import { mainMenu } from '@/config/menu/main';
+import type { VersionConfig } from '@/components/patterns/VersionSwitcher/types';
+import type { Menu } from '@/config/types';
+import SidebarMenu from './SidebarMenu.astro';
+import {
+  detectVersionFromUrl,
+  collectAllSubmenus,
+  calculateInitialActiveLevel,
+  type SubmenuData,
+} from './utils';
+import { Icon } from 'astro-icon/components';
+
+type Props = HTMLAttributes<'div'> & {
+  menu?: Menu;
+  versions?: VersionConfig[];
+  defaultVersion?: string;
+};
+
+const {
+  menu = mainMenu,
+  versions = [
+    { id: '5x', label: 'v5.x', isDefault: true },
+    { id: '4x', label: 'v4.x' },
+    { id: '3x', label: 'v3.x (deprecated)' },
+  ],
+  defaultVersion = '5x',
+  ...rest
+} = Astro.props;
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+const currentPath = Astro.url.pathname;
+const currentVersion = detectVersionFromUrl(currentPath, versions, defaultVersion);
+
+const submenus: SubmenuData[] = [];
+collectAllSubmenus(menu, 0, 'root', '', [], currentVersion, submenus);
+const initialActiveLevel = calculateInitialActiveLevel(submenus, currentPath, lang, currentVersion);
+---
+
+<div id="sidebarBackdrop" class="sidebar-backdrop" aria-hidden="true" data-sidebar-backdrop></div>
+
+<aside
+  id="sidebar"
+  class="sidebar"
+  role="dialog"
+  aria-modal="true"
+  aria-labelledby="sidebar-title"
+  aria-hidden="true"
+  data-sidebar
+  data-current-path={currentPath}
+  data-current-version={currentVersion}
+  {...rest}
+>
+  <h2 id="sidebar-title" class="sr-only" aria-label={t('nav.mainMenu')}>{t('nav.mainMenu')}</h2>
+
+  {
+    submenus.length > 0 && (
+      <button
+        type="button"
+        class="sidebar-toggle-nested"
+        data-toggle-nested-button
+        data-visible={initialActiveLevel > 0}
+        aria-label="Toggle nested navigation"
+        aria-expanded="true"
+      >
+        <Icon name="fluent:panel-right-expand-20-regular" size="20" aria-hidden="true" />
+      </button>
+    )
+  }
+
+  <div class="sidebar-container" data-nav-container data-current-nav-level={initialActiveLevel}>
+    <SidebarMenu
+      menu={menu}
+      level={0}
+      lang={lang}
+      currentPath={currentPath}
+      version={currentVersion}
+      versions={versions}
+      defaultVersion={defaultVersion}
+    />
+  </div>
+
+  <script>
+    import './SidebarController';
+  </script>
+</aside>
diff --git a/src/components/patterns/Sidebar/Sidebar.css b/src/components/patterns/Sidebar/Sidebar.css
new file mode 100644
index 0000000000..850c79b609
--- /dev/null
+++ b/src/components/patterns/Sidebar/Sidebar.css
@@ -0,0 +1,459 @@
+@layer patterns {
+  .sidebar-backdrop {
+    position: fixed;
+    top: 0;
+    left: 0;
+    right: 0;
+    bottom: 0;
+    background: color-mix(in oklch, var(--color-bg-primary) 50%, transparent);
+    opacity: 0;
+    visibility: hidden;
+    transition:
+      opacity var(--duration-300) var(--ease-in-out),
+      visibility var(--duration-300) var(--ease-in-out);
+    z-index: var(--z-index-sidebar-backdrop);
+
+    @media (--md-up) {
+      display: none;
+    }
+  }
+
+  .sidebar-backdrop--visible {
+    opacity: 1;
+    visibility: visible;
+  }
+
+  .sidebar {
+    background-color: var(--color-bg-secondary);
+    transition: transform var(--duration-300) var(--ease-in-out);
+    z-index: var(--z-index-sidebar);
+    top: var(--space-14);
+    overscroll-behavior: contain;
+
+    @media (--xs-only) {
+      visibility: hidden;
+      transform: translateX(-100%);
+      overflow: hidden;
+      top: var(--space-14);
+      position: fixed;
+      left: 0;
+      bottom: 0;
+      width: 80%;
+      max-width: var(--size-80);
+
+      .sidebar-logo-item {
+        display: none;
+      }
+    }
+
+    @media (--md-up) {
+      position: sticky;
+      align-self: flex-start;
+      height: 100vh;
+      top: 0;
+      flex: 0 0 auto;
+    }
+  }
+
+  .sidebar--open {
+    transform: translateX(0);
+    visibility: visible;
+  }
+
+  .sidebar-toggle-nested {
+    position: absolute;
+    top: var(--space-4);
+    right: 0;
+    transform: translate3d(100%, 0, 0);
+    z-index: 30;
+    display: flex;
+    align-items: center;
+    justify-content: center;
+    width: var(--space-8);
+    height: var(--space-8);
+    padding: 0;
+    background-color: var(--color-bg-tertiary);
+    border: 0;
+    border-radius: 0;
+    cursor: pointer;
+    color: var(--color-text-primary);
+    border-radius: 0 var(--radius-base) var(--radius-base) 0;
+    opacity: 1;
+    visibility: visible;
+    transition:
+      background-color var(--duration-200) var(--ease-in-out),
+      transform var(--duration-200) var(--ease-in-out),
+      opacity var(--duration-200) var(--ease-in-out),
+      visibility var(--duration-200) var(--ease-in-out);
+
+    &:hover {
+      color: var(--color-text-primary);
+    }
+
+    &:focus-visible {
+      outline: 2px solid var(--color-border-focus);
+      outline-offset: 2px;
+    }
+
+    &[aria-expanded='false'] {
+      transform: translate3d(100%, 0, 0) scale(-1);
+      background-color: var(--color-bg-secondary);
+      border-radius: var(--radius-base) 0 0 var(--radius-base) 0;
+    }
+
+    &[data-visible='false'] {
+      opacity: 0;
+      visibility: hidden;
+      pointer-events: none;
+    }
+
+    @media (--xs-only) {
+      display: none;
+    }
+  }
+
+  .sidebar-container {
+    display: flex;
+    flex-direction: row;
+    position: relative;
+    flex-grow: 1;
+    height: 100%;
+    transform: translateX(0);
+    transition: transform var(--duration-300) var(--ease-in-out);
+
+    &.sidebar-container--interactive {
+      transition: transform var(--duration-300) var(--ease-in-out);
+    }
+
+    @media (--xs-only) {
+      &:not([data-current-nav-level='0']) {
+        transform: translateX(-100%);
+      }
+
+      &[data-current-nav-level='2'] .sidebar-nested {
+        transform: translateX(-100%);
+      }
+
+      &[data-current-nav-level='3'] .sidebar-nested {
+        transform: translateX(-200%);
+      }
+
+      &[data-current-nav-level='4'] .sidebar-nested {
+        transform: translateX(-300%);
+      }
+
+      &[data-current-nav-level='5'] .sidebar-nested {
+        transform: translateX(-400%);
+      }
+    }
+
+    @media (--md-up) {
+      &[data-current-nav-level='0'] .sidebar-nested {
+        width: 0;
+        overflow: hidden;
+      }
+
+      &[data-current-nav-level='0'] .sidebar-nested-inner {
+        transform: translateX(-100%);
+      }
+
+      &[data-current-nav-level='2'] .sidebar-nested-inner {
+        transform: translateX(-100%);
+      }
+
+      &[data-current-nav-level='3'] .sidebar-nested-inner {
+        transform: translateX(-200%);
+      }
+
+      &[data-current-nav-level='4'] .sidebar-nested-inner {
+        transform: translateX(-300%);
+      }
+
+      &[data-current-nav-level='5'] .sidebar-nested-inner {
+        transform: translateX(-400%);
+      }
+    }
+  }
+
+  .sidebar-nested {
+    display: flex;
+    flex: 1 0 100%;
+    transition: transform var(--duration-300) var(--ease-in-out);
+
+    .sidebar-container--interactive & {
+      transition: transform var(--duration-300) var(--ease-in-out);
+    }
+
+    @media (--md-up) {
+      flex-basis: auto;
+      overflow: hidden;
+      width: var(--size-64);
+      z-index: 10;
+      position: relative;
+
+      .sidebar-container--interactive & {
+        transition: width var(--duration-300) var(--ease-in-out);
+      }
+    }
+  }
+
+  .sidebar-nested-inner {
+    display: flex;
+    flex: 1 0 100%;
+
+    .sidebar-container--interactive & {
+      transition: transform var(--duration-300) var(--ease-in-out);
+    }
+
+    @media (--md-up) {
+      position: absolute;
+      width: var(--size-64);
+      height: 100%;
+      left: 0;
+      top: 0;
+    }
+  }
+
+  .sidebar-column {
+    display: flex;
+    flex-direction: column;
+    flex: 1 0 100%;
+    background-color: var(--color-bg-secondary);
+    padding: var(--space-4);
+    transition: transform var(--duration-300) var(--ease-in-out);
+    overflow: auto;
+  }
+
+  .sidebar-root-column {
+    @media (--md-up) {
+      flex: 0 0 auto;
+      padding: var(--space-5) var(--space-3) var(--space-4) var(--space-3);
+      z-index: 20;
+
+      .sidebar-nav-item {
+        flex-direction: column;
+      }
+
+      .sidebar-nav-item--root-submenu .sidebar-nav-arrow {
+        display: none;
+      }
+
+      .sidebar-nav-item--selected {
+        .sidebar-nav-icon {
+          background-color: var(--color-bg-tertiary);
+        }
+      }
+    }
+  }
+
+  .sidebar-nav {
+    overflow-y: auto;
+    scrollbar-width: thin;
+    scrollbar-color: var(--color-border-primary) transparent;
+    scrollbar-gutter: stable;
+    flex-grow: 1;
+    display: flex;
+    flex-direction: column;
+  }
+
+  .sidebar-nav-list {
+    list-style: none;
+    margin: 0;
+    padding: 0;
+    flex: 1;
+
+    & li {
+      margin: 0;
+    }
+  }
+
+  .sidebar-nav-content {
+    overflow-y: auto;
+    padding-right: var(--space-2);
+  }
+
+  .sidebar-nav-back {
+    display: flex;
+    align-items: center;
+    gap: var(--space-2);
+    padding: var(--space-2) 0;
+    padding-bottom: var(--space-4);
+    margin-bottom: var(--space-2);
+    background: none;
+    border: none;
+    border-bottom: 1px solid var(--color-border-mute);
+    cursor: pointer;
+    color: var(--color-text-primary);
+    transition: color var(--duration-200) var(--ease-in-out);
+    width: 100%;
+    text-align: left;
+  }
+
+  .sidebar-section {
+    margin-bottom: var(--space-6);
+
+    &:last-child {
+      margin-bottom: 0;
+    }
+  }
+
+  .sidebar-section-list {
+    list-style: none;
+    margin: 0;
+    margin-top: var(--space-3);
+    padding: 0;
+
+    li {
+      margin: 0;
+    }
+
+    .sidebar-nav-content & {
+      margin-left: var(--space-3);
+      border-left: 1px solid var(--color-border-mute);
+    }
+
+    h3 + & {
+      margin-top: 0;
+    }
+  }
+
+  .sidebar-nav-item {
+    display: flex;
+    align-items: center;
+    gap: var(--space-3);
+    width: 100%;
+    padding: var(--space-3) 0;
+    text-decoration: none;
+    border: 0;
+    cursor: pointer;
+    position: relative;
+    transition: background-color var(--duration-200) var(--ease-in-out);
+    background-color: transparent;
+    border-radius: 0 var(--radius-base) var(--radius-base) 0;
+
+    @media (--md-up) {
+      gap: var(--space-1-5);
+    }
+  }
+
+  .sidebar-nav-label {
+    flex-grow: 1;
+    text-align: left;
+  }
+
+  .sidebar-nav-item--nested {
+    padding: var(--space-3);
+    font-size: var(--font-size-sm);
+    font-weight: var(--font-weight-normal);
+    color: var(--color-text-secondary);
+    border-radius: var(--radius-base);
+  }
+
+  .sidebar-nav-item--nested:hover,
+  .sidebar-nav-item--nested.sidebar-nav-item--active {
+    background-color: var(--color-bg-secondary);
+  }
+
+  .sidebar-nav-item--nested:hover {
+    color: var(--color-text-primary);
+  }
+
+  .sidebar-nav-item--nested:focus-visible {
+    outline-offset: -2px;
+    background-color: var(--color-bg-secondary);
+  }
+
+  .sidebar-nav-item--nested.sidebar-nav-item--active {
+    font-weight: var(--font-weight-semibold);
+    position: relative;
+  }
+
+  .sidebar-nav-item--nested.sidebar-nav-item--active::before {
+    content: '';
+    position: absolute;
+    left: 0;
+    top: 0;
+    bottom: 0;
+    width: var(--size-0-5);
+    background-color: var(--color-bg-inverse);
+  }
+
+  .sidebar-nav-icon {
+    padding: var(--space-2);
+    border-radius: var(--radius-base);
+    background-color: var(--color-bg-secondary);
+    transition: background-color var(--duration-200) var(--ease-in-out);
+    flex-shrink: 0;
+  }
+
+  .sidebar-nav-item:hover .sidebar-nav-icon,
+  .sidebar-nav-item--active .sidebar-nav-icon,
+  .sidebar-nav-item--active.sidebar-nav-item--selected .sidebar-nav-icon {
+    background-color: var(--color-bg-mute);
+  }
+
+  .sidebar-nav-arrow {
+    flex-shrink: 0;
+    opacity: 0.6;
+    transform: translateX(0);
+    transition: opacity var(--duration-200) var(--ease-in-out);
+
+    .sidebar-nav-item:hover & {
+      opacity: 1;
+    }
+  }
+
+  .sidebar-nav-item--submenu {
+    display: flex;
+    align-items: center;
+    justify-content: space-between;
+    text-align: left;
+  }
+
+  .sidebar-nested-column {
+    background-color: var(--color-bg-tertiary);
+    position: relative;
+  }
+
+  .sidebar-nav-panel {
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    z-index: 0;
+    opacity: 0;
+    padding: var(--space-4) var(--space-4) var(--space-8) var(--space-4);
+
+    @media (--md-up) {
+      padding-top: var(--space-3);
+    }
+
+    &:not(.sidebar-nav-panel--active) {
+      width: 1px;
+      height: 1px;
+      margin: -1px;
+      padding: 0;
+      overflow: hidden;
+      clip-path: inset(50%);
+      border: 0;
+      white-space: nowrap;
+    }
+
+    &--active {
+      z-index: 10;
+      opacity: 1;
+      height: 100%;
+      display: flex;
+      flex-direction: column;
+    }
+  }
+
+  @media (prefers-reduced-motion: reduce) {
+    .sidebar,
+    .sidebar-backdrop,
+    .sidebar-nav,
+    .sidebar-nav-item {
+      transition: none;
+    }
+  }
+}
diff --git a/src/components/patterns/Sidebar/SidebarController.ts b/src/components/patterns/Sidebar/SidebarController.ts
new file mode 100644
index 0000000000..fbe533902d
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarController.ts
@@ -0,0 +1,455 @@
+import { SidebarVersionManager } from './SidebarVersionManager';
+import { SidebarFocusTrap } from './SidebarFocusTrap';
+
+// CSS transition duration in milliseconds (must match Sidebar.css --duration-300)
+const TRANSITION_DURATION = 300;
+
+export class SidebarController {
+  private static readonly FOCUSABLE_SELECTOR =
+    'a:not([tabindex="-1"]), button:not([tabindex="-1"]), input:not([tabindex="-1"]), select:not([tabindex="-1"]), textarea:not([tabindex="-1"]), [tabindex]:not([tabindex="-1"])';
+  private static readonly INTERACTIVE_SELECTOR = 'a, button, input, select, textarea';
+
+  private sidebar: HTMLElement | null;
+  private backdrop: HTMLElement | null;
+  private navContainer: HTMLElement | null;
+  private toggleNestedButton: HTMLElement | null = null;
+  private versionManager: SidebarVersionManager | null = null;
+  private focusTrap: SidebarFocusTrap | null = null;
+
+  private isOpen = false;
+  private lastFocusedElement: HTMLElement | null = null;
+  private activeLevel = 0;
+  private activeSubmenuPath: string[] = ['root'];
+  private selectedItem: HTMLElement | null = null;
+  private isNestedCollapsed = false;
+
+  private initialActiveLevel = 0;
+  private initialActiveSubmenuPath: string[] = ['root'];
+
+  constructor() {
+    this.sidebar = document.querySelector('[data-sidebar]');
+    this.backdrop = document.querySelector('[data-sidebar-backdrop]');
+    this.navContainer = document.querySelector('[data-nav-container]');
+    this.toggleNestedButton = document.querySelector('[data-toggle-nested-button]');
+
+    if (this.sidebar && this.backdrop) {
+      const currentVersion = this.sidebar.dataset.currentVersion || '5x';
+      this.versionManager = new SidebarVersionManager(
+        this.sidebar,
+        currentVersion,
+        this.activeSubmenuPath
+      );
+      this.focusTrap = new SidebarFocusTrap(this.sidebar, () => this.activeSubmenuPath);
+      this.init();
+    }
+  }
+
+  private init(): void {
+    this.backdrop?.addEventListener('click', () => this.close());
+    document.addEventListener('keydown', (e) => this.handleKeyDown(e));
+    document.addEventListener('sidebar:toggle', () => this.toggle());
+
+    this.setupSubmenuTriggers();
+    this.setupBackButtons();
+    this.setupNavItemSelection();
+    this.versionManager?.setup();
+    this.initializeFromActiveState();
+    this.updateActiveColumns();
+    this.setupToggleNestedButton();
+  }
+
+  private initializeFromActiveState(): void {
+    const rootColumn = this.sidebar?.querySelector('[data-initial-active-level]') as HTMLElement;
+    const initialActiveLevel = parseInt(rootColumn?.dataset.initialActiveLevel || '0', 10);
+
+    if (initialActiveLevel > 0) {
+      this.activeSubmenuPath = ['root'];
+
+      for (let level = 1; level <= initialActiveLevel; level++) {
+        const levelColumn = this.sidebar?.querySelector(`[data-nav-level="${level}"]`);
+        const activePanelInLevel = levelColumn?.querySelector(
+          '.sidebar-nav-panel.sidebar-nav-panel--active'
+        ) as HTMLElement;
+
+        if (activePanelInLevel?.dataset.parentId) {
+          this.activeSubmenuPath.push(activePanelInLevel.dataset.parentId);
+        }
+      }
+
+      this.activeLevel = initialActiveLevel;
+      this.initialActiveLevel = initialActiveLevel;
+      this.initialActiveSubmenuPath = [...this.activeSubmenuPath];
+      this.versionManager?.updatePath(this.activeSubmenuPath);
+
+      if (this.navContainer) {
+        this.navContainer.dataset.currentNavLevel = String(initialActiveLevel);
+      }
+    }
+  }
+
+  private focusActiveLevel(): void {
+    const currentSubmenuId = this.activeSubmenuPath[this.activeSubmenuPath.length - 1];
+    const targetContainer = this.sidebar?.querySelector(
+      `[data-parent-id="${currentSubmenuId}"]`
+    ) as HTMLElement;
+
+    if (!targetContainer) {
+      console.warn(`Focus target not found for submenu: ${currentSubmenuId}`);
+      return;
+    }
+
+    const firstFocusable = targetContainer.querySelector(
+      SidebarController.FOCUSABLE_SELECTOR
+    ) as HTMLElement;
+
+    if (!firstFocusable) {
+      console.warn(`No focusable elements found in: ${currentSubmenuId}`);
+      return;
+    }
+
+    firstFocusable.focus();
+  }
+
+  private setupSubmenuTriggers(): void {
+    this.sidebar?.querySelectorAll('[data-submenu-trigger]').forEach((trigger) => {
+      trigger.addEventListener('click', (e) => {
+        e.preventDefault();
+        const button = e.currentTarget as HTMLButtonElement;
+        const targetId = button.dataset.targetId;
+        const targetLevel = parseInt(button.dataset.targetLevel || '1', 10);
+
+        if (targetId) {
+          this.navigateToSubmenu(targetId, targetLevel);
+          button.setAttribute('aria-expanded', 'true');
+        }
+      });
+    });
+  }
+
+  private setupBackButtons(): void {
+    this.sidebar?.querySelectorAll('[data-back-button]').forEach((button) => {
+      button.addEventListener('click', (e) => {
+        e.preventDefault();
+        this.navigateBack();
+      });
+    });
+  }
+
+  private setupNavItemSelection(): void {
+    this.sidebar?.querySelectorAll('.sidebar-nav-item').forEach((item) => {
+      item.addEventListener('click', () => {
+        // Only track selection for root-level items (level 0)
+        const isRootLevel = item.closest('[data-nav-level="0"]') !== null;
+        if (isRootLevel) {
+          this.setSelectedItem(item as HTMLElement);
+        }
+      });
+    });
+  }
+
+  private setupToggleNestedButton(): void {
+    this.toggleNestedButton?.addEventListener('click', () => {
+      this.toggleNestedColumns();
+    });
+    this.updateToggleButtonVisibility();
+  }
+
+  private updateToggleButtonVisibility(): void {
+    if (!this.toggleNestedButton) return;
+
+    const shouldBeVisible = this.activeLevel > 0 || this.initialActiveLevel > 0;
+    this.toggleNestedButton.setAttribute('data-visible', String(shouldBeVisible));
+  }
+
+  private setSelectedItem(item: HTMLElement): void {
+    if (this.selectedItem) {
+      this.selectedItem.classList.remove('sidebar-nav-item--selected');
+    }
+
+    item.classList.add('sidebar-nav-item--selected');
+    this.selectedItem = item;
+  }
+
+  private toggleNestedColumns(): void {
+    this.isNestedCollapsed = !this.isNestedCollapsed;
+    this.enableTransitions();
+
+    if (this.isNestedCollapsed) {
+      if (this.selectedItem) {
+        this.selectedItem.classList.remove('sidebar-nav-item--selected');
+        this.selectedItem = null;
+      }
+
+      this.activeLevel = 0;
+      if (this.navContainer) {
+        this.navContainer.dataset.currentNavLevel = '0';
+      }
+    } else {
+      this.activeSubmenuPath = [...this.initialActiveSubmenuPath];
+      this.activeLevel = this.initialActiveLevel;
+      this.versionManager?.updatePath(this.activeSubmenuPath);
+      if (this.navContainer) {
+        this.navContainer.dataset.currentNavLevel = String(this.initialActiveLevel);
+      }
+    }
+
+    if (this.toggleNestedButton) {
+      this.toggleNestedButton.setAttribute('aria-expanded', String(!this.isNestedCollapsed));
+    }
+
+    this.updateActiveColumns();
+    this.updateToggleButtonVisibility();
+  }
+
+  private navigateToSubmenu(submenuId: string, level: number): void {
+    const submenuColumn = this.sidebar?.querySelector(
+      `[data-parent-id="${submenuId}"]`
+    ) as HTMLElement;
+
+    if (!submenuColumn) {
+      console.warn(`Submenu column not found: ${submenuId}`);
+      return;
+    }
+
+    this.enableTransitions();
+
+    // Check if this submenu is part of the initial path (contains current page)
+    // If so, restore to the initial navigation state instead of just going to target level
+    const isInInitialPath = this.initialActiveSubmenuPath.includes(submenuId);
+    const shouldRestoreInitialState = isInInitialPath && this.initialActiveLevel > level;
+
+    if (shouldRestoreInitialState) {
+      // Restore to the initial deep navigation state
+      this.activeSubmenuPath = [...this.initialActiveSubmenuPath];
+      this.activeLevel = this.initialActiveLevel;
+    } else {
+      this.activeSubmenuPath = this.activeSubmenuPath.slice(0, level);
+      this.activeSubmenuPath.push(submenuId);
+      this.activeLevel = level;
+    }
+
+    // If navigating to a submenu, ensure nested columns are expanded
+    if (this.isNestedCollapsed && level > 0) {
+      this.isNestedCollapsed = false;
+      if (this.toggleNestedButton) {
+        this.toggleNestedButton.setAttribute('aria-expanded', 'true');
+      }
+    }
+
+    this.versionManager?.updatePath(this.activeSubmenuPath);
+
+    this.updateActiveColumns();
+    this.updateToggleButtonVisibility();
+
+    if (this.navContainer) {
+      this.navContainer.dataset.currentNavLevel = String(this.activeLevel);
+    }
+
+    this.afterTransition(() => this.focusActiveLevel());
+  }
+
+  private navigateBack(): void {
+    if (this.activeSubmenuPath.length <= 1) return;
+
+    this.enableTransitions();
+
+    // Clear selected item state when navigating back
+    if (this.selectedItem) {
+      this.selectedItem.classList.remove('sidebar-nav-item--selected');
+      this.selectedItem = null;
+    }
+
+    const currentSubmenuId = this.activeSubmenuPath[this.activeSubmenuPath.length - 1];
+    let triggerToFocus: HTMLElement | null = null;
+
+    if (currentSubmenuId) {
+      const trigger = this.sidebar?.querySelector(
+        `[data-target-id="${currentSubmenuId}"]`
+      ) as HTMLElement;
+      trigger?.setAttribute('aria-expanded', 'false');
+      triggerToFocus = trigger;
+    }
+
+    this.activeSubmenuPath.pop();
+    this.activeLevel = this.activeSubmenuPath.length - 1;
+    this.versionManager?.updatePath(this.activeSubmenuPath);
+
+    // If navigating back to level 0, collapse nested columns and update toggle button
+    if (this.activeLevel === 0) {
+      this.isNestedCollapsed = true;
+      if (this.toggleNestedButton) {
+        this.toggleNestedButton.setAttribute('aria-expanded', 'false');
+      }
+    }
+
+    this.updateActiveColumns();
+    this.updateToggleButtonVisibility();
+
+    if (this.navContainer) {
+      this.navContainer.dataset.currentNavLevel = String(this.activeLevel);
+    }
+
+    // Restore focus to the trigger button after the transition
+    this.afterTransition(() => triggerToFocus?.focus());
+  }
+
+  private updateActiveColumns(): void {
+    const allLevels = this.sidebar?.querySelectorAll('[data-nav-level]');
+
+    allLevels?.forEach((column) => {
+      const columnLevel = parseInt((column as HTMLElement).dataset.navLevel || '0', 10);
+      const isCurrentLevel = columnLevel === this.activeLevel;
+
+      if (columnLevel === 0) {
+        column.setAttribute('aria-hidden', 'false');
+        this.updateFocusableElements(column as HTMLElement, true);
+      } else {
+        const panels = column.querySelectorAll('[data-parent-id]');
+        panels.forEach((panel) => {
+          const parentId = (panel as HTMLElement).dataset.parentId || '';
+          const isInActivePath = this.activeSubmenuPath.includes(parentId);
+
+          panel.setAttribute('aria-hidden', isInActivePath ? 'false' : 'true');
+          panel.classList.toggle('sidebar-nav-panel--active', isInActivePath);
+
+          const shouldBeFocusable = isCurrentLevel && isInActivePath;
+          this.updateFocusableElements(panel as HTMLElement, shouldBeFocusable);
+        });
+      }
+    });
+
+    this.versionManager?.updateVisibility(this.activeLevel);
+  }
+
+  private updateFocusableElements(container: HTMLElement, isVisible: boolean): void {
+    const scrollableContainers = container.querySelectorAll('.sidebar-nav-content, .sidebar-nav');
+    scrollableContainers.forEach((scrollContainer) => {
+      if (isVisible) {
+        scrollContainer.removeAttribute('tabindex');
+      } else {
+        scrollContainer.setAttribute('tabindex', '-1');
+      }
+    });
+
+    const focusableElements = container.querySelectorAll(SidebarController.INTERACTIVE_SELECTOR);
+
+    focusableElements.forEach((element) => {
+      if (isVisible) {
+        const originalTabindex = element.getAttribute('data-original-tabindex');
+        if (originalTabindex !== null) {
+          if (originalTabindex === '') {
+            element.removeAttribute('tabindex');
+          } else {
+            element.setAttribute('tabindex', originalTabindex);
+          }
+          element.removeAttribute('data-original-tabindex');
+        }
+      } else {
+        const currentTabindex = element.getAttribute('tabindex');
+        const hasOriginalTabindex = element.hasAttribute('data-original-tabindex');
+
+        if (!hasOriginalTabindex && currentTabindex !== '-1') {
+          element.setAttribute('data-original-tabindex', currentTabindex || '');
+          element.setAttribute('tabindex', '-1');
+        }
+      }
+    });
+  }
+
+  private enableTransitions(): void {
+    this.navContainer?.classList.add('sidebar-container--interactive');
+  }
+
+  private afterTransition(callback: () => void): void {
+    setTimeout(callback, TRANSITION_DURATION);
+  }
+
+  private handleKeyDown(e: KeyboardEvent): void {
+    if (e.key === 'Escape' && this.isOpen) {
+      if (this.activeLevel > 0) {
+        this.navigateBack();
+      } else {
+        this.close();
+      }
+    }
+    this.focusTrap?.trap(e, this.isOpen);
+  }
+
+  public open(): void {
+    if (this.isOpen || !this.sidebar || !this.backdrop) return;
+
+    this.lastFocusedElement = document.activeElement as HTMLElement;
+    this.isOpen = true;
+
+    this.sidebar.setAttribute('aria-hidden', 'false');
+    this.backdrop.setAttribute('aria-hidden', 'false');
+    this.sidebar.classList.add('sidebar--open');
+    this.backdrop.classList.add('sidebar-backdrop--visible');
+    document.body.style.overflow = 'hidden';
+
+    this.afterTransition(() => this.focusActiveLevel());
+  }
+
+  public close(): void {
+    if (!this.isOpen || !this.sidebar || !this.backdrop) return;
+
+    document.dispatchEvent(new CustomEvent('sidebar:closed'));
+    this.isOpen = false;
+
+    // Clear selected item state immediately
+    if (this.selectedItem) {
+      this.selectedItem.classList.remove('sidebar-nav-item--selected');
+      this.selectedItem = null;
+    }
+
+    this.sidebar.setAttribute('aria-hidden', 'true');
+    this.backdrop.setAttribute('aria-hidden', 'true');
+    this.sidebar.classList.remove('sidebar--open');
+    this.backdrop.classList.remove('sidebar-backdrop--visible');
+
+    this.afterTransition(() => this.resetToInitialState());
+
+    document.body.style.overflow = '';
+    this.lastFocusedElement?.focus();
+    this.lastFocusedElement = null;
+  }
+
+  private resetToInitialState(): void {
+    this.sidebar?.querySelectorAll('[data-submenu-trigger]').forEach((trigger) => {
+      trigger.setAttribute('aria-expanded', 'false');
+    });
+
+    this.activeSubmenuPath = [...this.initialActiveSubmenuPath];
+    this.activeLevel = this.initialActiveLevel;
+    this.isNestedCollapsed = false;
+    this.versionManager?.updatePath(this.activeSubmenuPath);
+
+    // Reset toggle button state
+    if (this.toggleNestedButton) {
+      this.toggleNestedButton.setAttribute('aria-expanded', 'true');
+    }
+
+    this.updateActiveColumns();
+    this.updateToggleButtonVisibility();
+
+    if (this.navContainer) {
+      this.navContainer.dataset.currentNavLevel = String(this.activeLevel);
+    }
+  }
+
+  public toggle(): void {
+    if (this.isOpen) {
+      this.close();
+    } else {
+      this.open();
+    }
+  }
+}
+
+declare global {
+  interface Window {
+    sidebarController?: SidebarController;
+  }
+}
+
+(window as Window).sidebarController = new SidebarController();
diff --git a/src/components/patterns/Sidebar/SidebarFocusTrap.ts b/src/components/patterns/Sidebar/SidebarFocusTrap.ts
new file mode 100644
index 0000000000..665b2333ba
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarFocusTrap.ts
@@ -0,0 +1,65 @@
+export class SidebarFocusTrap {
+  private sidebar: HTMLElement;
+  private getActiveSubmenuPath: () => string[];
+
+  constructor(sidebar: HTMLElement, getActiveSubmenuPath: () => string[]) {
+    this.sidebar = sidebar;
+    this.getActiveSubmenuPath = getActiveSubmenuPath;
+  }
+
+  getFocusableElements(): HTMLElement[] {
+    const activeSubmenuPath = this.getActiveSubmenuPath();
+    const activeSubmenuId = activeSubmenuPath[activeSubmenuPath.length - 1];
+    const activeColumn = this.sidebar.querySelector(`[data-parent-id="${activeSubmenuId}"]`);
+    if (!activeColumn) return [];
+
+    const selectors =
+      'a[href], button:not([disabled]), select:not([disabled]), [tabindex]:not([tabindex="-1"])';
+    return Array.from(activeColumn.querySelectorAll(selectors));
+  }
+
+  trap(e: KeyboardEvent, isOpen: boolean): void {
+    if (!isOpen) return;
+
+    if (e.key === 'Tab') {
+      this.handleTabNavigation(e);
+    } else if (e.key === 'ArrowDown' || e.key === 'ArrowUp') {
+      this.handleArrowNavigation(e);
+    }
+  }
+
+  private handleTabNavigation(e: KeyboardEvent): void {
+    const focusableElements = this.getFocusableElements();
+    if (focusableElements.length === 0) return;
+
+    const first = focusableElements[0];
+    const last = focusableElements[focusableElements.length - 1];
+
+    if (e.shiftKey && document.activeElement === first) {
+      e.preventDefault();
+      last?.focus();
+    } else if (!e.shiftKey && document.activeElement === last) {
+      e.preventDefault();
+      first?.focus();
+    }
+  }
+
+  private handleArrowNavigation(e: KeyboardEvent): void {
+    const focusableElements = this.getFocusableElements();
+    if (focusableElements.length === 0) return;
+
+    const currentIndex = focusableElements.indexOf(document.activeElement as HTMLElement);
+    if (currentIndex === -1) return;
+
+    e.preventDefault();
+
+    let nextIndex: number;
+    if (e.key === 'ArrowDown') {
+      nextIndex = currentIndex + 1 >= focusableElements.length ? 0 : currentIndex + 1;
+    } else {
+      nextIndex = currentIndex - 1 < 0 ? focusableElements.length - 1 : currentIndex - 1;
+    }
+
+    focusableElements[nextIndex]?.focus();
+  }
+}
diff --git a/src/components/patterns/Sidebar/SidebarItemsList.astro b/src/components/patterns/Sidebar/SidebarItemsList.astro
new file mode 100644
index 0000000000..bd0c92cbe1
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarItemsList.astro
@@ -0,0 +1,102 @@
+---
+import type { MenuItem, VersionPrefix } from '@/config/types';
+import type { LanguageCode } from '@/i18n/locales';
+import SidebarNavItem from './SidebarNavItem.astro';
+import {
+  isLink,
+  hasSubmenu,
+  filterItems,
+  getItemId,
+  resolveHref,
+  normalizePath,
+  submenuContainsCurrentPath,
+} from './utils';
+
+interface Props {
+  items: MenuItem[];
+  parentId: string;
+  sectionIndex: number | null;
+  currentPath: string;
+  lang: LanguageCode;
+  basePath: string;
+  versioned: VersionPrefix[];
+  version: string;
+  variant: 'root' | 'nested';
+  showIcon?: boolean;
+  targetLevel: number;
+}
+
+const {
+  items,
+  parentId,
+  sectionIndex,
+  currentPath,
+  lang,
+  basePath,
+  versioned,
+  version,
+  variant,
+  showIcon = false,
+  targetLevel,
+} = Astro.props;
+
+const filteredItems = filterItems(items, version);
+---
+
+{
+  filteredItems
+    .filter((item) => isLink(item) || hasSubmenu(item))
+    .map((item, itemIndex) => {
+      const itemId = getItemId(parentId, sectionIndex, itemIndex);
+      const itemHref = item.href;
+
+      const itemVersioned = item.submenu?.versioned ?? versioned;
+      const itemBasePath = item.submenu?.basePath ?? basePath;
+
+      const href = itemHref
+        ? resolveHref(itemHref, lang, itemBasePath, itemVersioned, version, item.global)
+        : '';
+
+      const isActive =
+        hasSubmenu(item) && variant === 'root'
+          ? submenuContainsCurrentPath(
+              item.submenu,
+              itemBasePath,
+              itemVersioned,
+              currentPath,
+              lang,
+              version
+            )
+          : href
+            ? normalizePath(currentPath) === normalizePath(href)
+            : false;
+
+      if (hasSubmenu(item)) {
+        return (
+          <SidebarNavItem
+            item={item}
+            href={href}
+            isActive={isActive}
+            variant={variant}
+            type="submenu"
+            submenuId={`submenu-${itemId}`}
+            targetLevel={targetLevel}
+            showIcon={showIcon}
+            lang={lang}
+          />
+        );
+      }
+
+      return (
+        <SidebarNavItem
+          item={item}
+          href={href}
+          isActive={isActive}
+          variant={variant}
+          type="link"
+          showIcon={showIcon}
+          lang={lang}
+        />
+      );
+    })
+}
diff --git a/src/components/patterns/Sidebar/SidebarMenu.astro b/src/components/patterns/Sidebar/SidebarMenu.astro
new file mode 100644
index 0000000000..370b5603cf
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarMenu.astro
@@ -0,0 +1,239 @@
+---
+import type { Menu, VersionPrefix } from '@/config/types';
+import type { VersionConfig } from '@/components/patterns/VersionSwitcher/types';
+import type { LanguageCode } from '@/i18n/locales';
+import { Body } from '@/components/primitives';
+import { Image } from 'astro:assets';
+import { Icon } from 'astro-icon/components';
+import { VersionSwitcher } from '@/components/patterns';
+import { useTranslations } from '@/i18n/utils';
+import SidebarItemsList from './SidebarItemsList.astro';
+import {
+  shouldOmitSection,
+  collectAllSubmenus,
+  submenuContainsCurrentPath,
+  calculateInitialActiveLevel,
+  groupSubmenusByLevel,
+  type SubmenuData,
+} from './utils';
+
+interface Props {
+  menu: Menu;
+  level: number;
+  title?: string;
+  lang: LanguageCode;
+  currentPath: string;
+  basePath?: string;
+  versioned?: VersionPrefix[];
+  version?: string;
+  versions?: VersionConfig[];
+  defaultVersion?: string;
+  parentId?: string;
+}
+
+const {
+  menu,
+  level,
+  lang,
+  currentPath,
+  basePath = '',
+  versioned = [],
+  version = '5x',
+  versions = [],
+  defaultVersion = '5x',
+  parentId = 'root',
+} = Astro.props;
+
+const t = useTranslations(lang);
+
+if (level !== 0) return null;
+
+const submenus: SubmenuData[] = [];
+collectAllSubmenus(menu, level, parentId, basePath, versioned, version, submenus);
+
+const submenusByLevel = groupSubmenusByLevel(submenus);
+const sortedLevels = [...submenusByLevel.keys()].sort((a, b) => a - b);
+const initialActiveLevel = calculateInitialActiveLevel(submenus, currentPath, lang, version);
+
+const filteredSections =
+  menu.sections?.filter((section) => !shouldOmitSection(section, version)) ?? [];
+
+const commonItemsListProps = {
+  currentPath,
+  lang,
+  basePath,
+  versioned,
+  version,
+};
+---
+
+<div
+  class="sidebar-column sidebar-root-column"
+  data-nav-level={level}
+  data-parent-id={parentId}
+  data-initial-active-level={initialActiveLevel}
+  aria-hidden="false"
+>
+  <nav class="sidebar-nav" aria-label={t('nav.mainNavigation')}>
+    <ul class="sidebar-nav-list">
+      <li class="sidebar-logo-item">
+        <a href={`/${lang}/`} class="logo-link sidebar-nav-item" aria-label={t('nav.home')}>
+          <Image
+            src="/images/logos/express-kawaii.webp"
+            alt="Express.js kawaii logo"
+            class="logo logo-kawaii"
+            width={40}
+            height={40}
+          />
+          <Icon name="logo-dark" class="logo logo-dark logo-default" />
+          <Icon name="logo-light" class="logo logo-light logo-default" />
+        </a>
+      </li>
+      {
+        filteredSections.map((section, sectionIndex) => (
+          <li class="sidebar-section">
+            {section.title && <Body as="h3">{t(section.title)}</Body>}
+            <ul class="sidebar-section-list">
+              <SidebarItemsList
+                items={section.items}
+                parentId={parentId}
+                sectionIndex={sectionIndex}
+                {...commonItemsListProps}
+                variant="root"
+                showIcon={true}
+                targetLevel={level + 1}
+              />
+            </ul>
+          </li>
+        ))
+      }
+      <SidebarItemsList
+        items={menu.items ?? []}
+        parentId={parentId}
+        sectionIndex={null}
+        variant="root"
+        showIcon={true}
+        targetLevel={level + 1}
+        {...commonItemsListProps}
+      />
+    </ul>
+  </nav>
+</div>
+
+{
+  sortedLevels.length > 0 && (
+    <div class="sidebar-nested" data-nested-levels-container>
+      <div class="sidebar-nested-inner">
+        {sortedLevels.map((navLevel) => (
+          <div
+            class="sidebar-column sidebar-nested-column"
+            data-nav-level={navLevel}
+            aria-hidden="true"
+          >
+            {submenusByLevel.get(navLevel)?.map((submenu) => {
+              const panelHasActiveItem = submenuContainsCurrentPath(
+                submenu.menu,
+                submenu.basePath,
+                submenu.versioned,
+                currentPath,
+                lang,
+                version
+              );
+              const availableVersions =
+                submenu.versioned.length > 0
+                  ? versions.filter((v) => submenu.versioned.includes(v.id as VersionPrefix))
+                  : [];
+              const filteredSubmenuSections =
+                submenu.menu.sections?.filter((section) => !shouldOmitSection(section, version)) ??
+                [];
+
+              return (
+                <div
+                  class:list={[
+                    'sidebar-nav-panel',
+                    panelHasActiveItem && 'sidebar-nav-panel--active',
+                  ]}
+                  data-parent-id={submenu.id}
+                  aria-hidden="true"
+                >
+                  {availableVersions.length > 0 && (
+                    <VersionSwitcher
+                      class="sidebar-version-switcher"
+                      versions={availableVersions}
+                      defaultVersion={defaultVersion}
+                      currentPath={currentPath}
+                      aria-label="Select documentation version"
+                      data-version-switcher
+                    />
+                  )}
+                  <nav class="sidebar-nav" aria-label={`${t(submenu.title)} navigation`}>
+                    <button
+                      class="sidebar-nav-back"
+                      type="button"
+                      aria-label={`Go back from ${t(submenu.title)}`}
+                      data-back-button
+                      data-target-level={navLevel - 1}
+                    >
+                      <Icon
+                        name="fluent:arrow-export-rtl-20-regular"
+                        size="16"
+                        color="var(--color-icon-primary)"
+                        aria-hidden="true"
+                      />
+                      <Body as="span" weight="bold" vMargin={false}>
+                        {t(submenu.title)}
+                      </Body>
+                    </button>
+                    <div class="sidebar-nav-content">
+                      {filteredSubmenuSections.map((section, sectionIndex) => (
+                        <div class="sidebar-section" data-section-index={sectionIndex}>
+                          {section.title && (
+                            <Body as="h3" weight="bold">
+                              {t(section.title)}
+                            </Body>
+                          )}
+                          <ul class="sidebar-section-list">
+                            <SidebarItemsList
+                              items={section.items}
+                              parentId={submenu.id}
+                              sectionIndex={sectionIndex}
+                              currentPath={currentPath}
+                              lang={lang}
+                              basePath={submenu.basePath}
+                              versioned={submenu.versioned}
+                              version={version}
+                              variant="nested"
+                              showIcon={false}
+                              targetLevel={navLevel + 1}
+                            />
+                          </ul>
+                        </div>
+                      ))}
+                      {(submenu.menu.items?.length ?? 0) > 0 && (
+                        <ul class="sidebar-section-list">
+                          <SidebarItemsList
+                            items={submenu.menu.items!}
+                            parentId={submenu.id}
+                            sectionIndex={null}
+                            currentPath={currentPath}
+                            lang={lang}
+                            basePath={submenu.basePath}
+                            versioned={submenu.versioned}
+                            version={version}
+                            variant="nested"
+                            showIcon={false}
+                            targetLevel={navLevel + 1}
+                          />
+                        </ul>
+                      )}
+                    </div>
+                  </nav>
+                </div>
+              );
+            })}
+          </div>
+        ))}
+      </div>
+    </div>
+  )
+}
diff --git a/src/components/patterns/Sidebar/SidebarNavItem.astro b/src/components/patterns/Sidebar/SidebarNavItem.astro
new file mode 100644
index 0000000000..4529fd36ad
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarNavItem.astro
@@ -0,0 +1,117 @@
+---
+import type { MenuItem } from '@/config/types';
+import { BodyMd } from '@/components/primitives';
+import { Icon } from 'astro-icon/components';
+import { useTranslations } from '@/i18n/utils';
+import type { LanguageCode } from '@/i18n/locales';
+
+interface Props {
+  item: MenuItem & { href?: string };
+  href: string;
+  isActive: boolean;
+  variant: 'root' | 'nested';
+  type: 'link' | 'submenu';
+  submenuId?: string;
+  targetLevel?: number;
+  showIcon?: boolean;
+  lang: LanguageCode;
+}
+
+const {
+  item,
+  href,
+  isActive,
+  variant,
+  type,
+  submenuId,
+  targetLevel,
+  showIcon = false,
+  lang,
+} = Astro.props;
+
+const t = useTranslations(lang);
+const isNested = variant === 'nested';
+const isRootSubmenu = variant === 'root';
+const isExternal = href.startsWith('http');
+
+// show overview instead of specific section names for top-level items that link to an overview page
+const overviewAliases = new Set([
+  'menu.main.api',
+  'menu.sections.express',
+  'menu.sections.request',
+  'menu.sections.response',
+  'menu.sections.router',
+  'menu.sections.application',
+]);
+
+function getLabel() {
+  return overviewAliases.has(item.label) ? t('menu.items.overview') : t(item.label);
+}
+---
+
+{
+  type === 'link' ? (
+    <li>
+      <a
+        href={href}
+        class:list={[
+          'sidebar-nav-item',
+          isNested && 'sidebar-nav-item--nested',
+          isActive && 'sidebar-nav-item--active',
+        ]}
+        aria-label={item.ariaLabel ? t(item.ariaLabel) : undefined}
+        aria-current={isActive ? 'page' : undefined}
+        data-omit-from={item.omitFrom?.join(',') || undefined}
+        target={isExternal ? '_blank' : undefined}
+        rel={isExternal ? 'noopener noreferrer' : undefined}
+      >
+        {showIcon && item.icon && (
+          <div class="sidebar-nav-icon">
+            <Icon name={`fluent:${item.icon}`} size="24" color="var(--color-icon-primary)" />
+          </div>
+        )}
+
+        <BodyMd vMargin={false} class="sidebar-nav-label">
+          {getLabel()}
+        </BodyMd>
+      </a>
+    </li>
+  ) : (
+    <li>
+      <button
+        class:list={[
+          'sidebar-nav-item',
+          isRootSubmenu && 'sidebar-nav-item--root-submenu',
+          isNested && 'sidebar-nav-item--nested',
+          type === 'submenu' && isNested && 'sidebar-nav-item--submenu',
+          isActive && 'sidebar-nav-item--active',
+        ]}
+        aria-label={item.ariaLabel ? t(item.ariaLabel) : undefined}
+        aria-expanded="false"
+        aria-controls={submenuId}
+        type="button"
+        data-submenu-trigger
+        data-target-id={submenuId}
+        data-target-level={targetLevel}
+      >
+        {showIcon && item.icon && (
+          <div class="sidebar-nav-icon">
+            <Icon name={`fluent:${item.icon}`} size="24" color="var(--color-icon-primary)" />
+          </div>
+        )}
+
+        <BodyMd vMargin={false} class="sidebar-nav-label">
+          {t(item.label)}
+        </BodyMd>
+
+        <Icon
+          name="fluent:arrow-right-20-regular"
+          size="16"
+          color="var(--color-icon-secondary)"
+          class="sidebar-nav-arrow"
+          aria-hidden="true"
+        />
+      </button>
+    </li>
+  )
+}
diff --git a/src/components/patterns/Sidebar/SidebarVersionManager.ts b/src/components/patterns/Sidebar/SidebarVersionManager.ts
new file mode 100644
index 0000000000..2ce610820c
--- /dev/null
+++ b/src/components/patterns/Sidebar/SidebarVersionManager.ts
@@ -0,0 +1,145 @@
+export class SidebarVersionManager {
+  private sidebar: HTMLElement;
+  private currentVersion: string;
+  private activeSubmenuPath: string[];
+
+  constructor(sidebar: HTMLElement, currentVersion: string, activeSubmenuPath: string[]) {
+    this.sidebar = sidebar;
+    this.currentVersion = currentVersion;
+    this.activeSubmenuPath = activeSubmenuPath;
+  }
+
+  setup(): void {
+    const versionSwitchers = this.sidebar.querySelectorAll(
+      '[data-version-switcher] select, [data-version-select]'
+    );
+
+    versionSwitchers.forEach((switcher) => {
+      switcher.addEventListener('change', (e) => {
+        const select = e.target as HTMLSelectElement;
+        this.handleVersionChange(select.value);
+      });
+    });
+  }
+
+  handleVersionChange(newVersion: string): void {
+    const previousVersion = this.currentVersion;
+    this.currentVersion = newVersion;
+
+    document.dispatchEvent(
+      new CustomEvent('sidebar:versionChange', {
+        detail: { previousVersion, newVersion },
+      })
+    );
+
+    const currentPath = this.sidebar.dataset.currentPath || '';
+
+    if (currentPath.includes(`/${previousVersion}/`)) {
+      if (this.isPathOmittedForVersion(currentPath, newVersion)) {
+        const fallbackPath = this.getFirstAvailableLinkForVersion(newVersion, previousVersion);
+        if (fallbackPath) {
+          window.location.href = fallbackPath;
+          return;
+        }
+      }
+
+      window.location.href = currentPath.replace(`/${previousVersion}/`, `/${newVersion}/`);
+      return;
+    }
+
+    if (this.isInVersionedSubmenu()) {
+      const fallbackPath = this.getFirstAvailableLinkForVersion(newVersion, previousVersion);
+      if (fallbackPath) {
+        window.location.href = fallbackPath;
+      }
+    }
+  }
+
+  private isInVersionedSubmenu(): boolean {
+    const activeSubmenuId = this.activeSubmenuPath[this.activeSubmenuPath.length - 1];
+    if (activeSubmenuId === 'root') return false;
+
+    const activePanel = this.sidebar.querySelector(
+      `[data-parent-id="${activeSubmenuId}"]`
+    ) as HTMLElement;
+
+    if (!activePanel) return false;
+
+    // Check if the active panel contains versioned links
+    const versionedLink = activePanel.querySelector('a[href*="/4x/"], a[href*="/5x/"]');
+    return versionedLink !== null;
+  }
+
+  private isPathOmittedForVersion(currentPath: string, targetVersion: string): boolean {
+    const activeLink = this.sidebar.querySelector(
+      'a.sidebar-nav-item--active[data-omit-from]'
+    ) as HTMLAnchorElement;
+
+    if (!activeLink) return false;
+
+    const omitFrom = activeLink.dataset.omitFrom?.split(',') || [];
+    return omitFrom.includes(targetVersion);
+  }
+
+  private getFirstAvailableLinkForVersion(
+    targetVersion: string,
+    previousVersion: string
+  ): string | null {
+    const activeSubmenuId = this.activeSubmenuPath[this.activeSubmenuPath.length - 1];
+    const activePanel = this.sidebar.querySelector(
+      `[data-parent-id="${activeSubmenuId}"]`
+    ) as HTMLElement;
+
+    if (!activePanel) return null;
+
+    const links = activePanel.querySelectorAll(
+      'a.sidebar-nav-item[href]'
+    ) as NodeListOf<HTMLAnchorElement>;
+
+    for (const link of links) {
+      const omitFrom = link.dataset.omitFrom?.split(',') || [];
+      if (!omitFrom.includes(targetVersion)) {
+        const href = link.getAttribute('href') || '';
+        if (href.includes(`/${previousVersion}/`)) {
+          return href.replace(`/${previousVersion}/`, `/${targetVersion}/`);
+        }
+        return href;
+      }
+    }
+
+    return null;
+  }
+
+  updateVisibility(activeLevel: number): void {
+    const versionSwitchers = this.sidebar.querySelectorAll('[data-version-switcher]');
+
+    versionSwitchers.forEach((switcher) => {
+      const column = switcher.closest('[data-parent-id]') as HTMLElement;
+      const parentId = column?.dataset.parentId || '';
+      const isActiveColumn = parentId === this.activeSubmenuPath[this.activeSubmenuPath.length - 1];
+
+      if (activeLevel > 0 && isActiveColumn) {
+        switcher.classList.remove('sidebar-version-switcher--hidden');
+      } else {
+        switcher.classList.add('sidebar-version-switcher--hidden');
+      }
+    });
+  }
+
+  updatePath(path: string[]): void {
+    this.activeSubmenuPath = path;
+  }
+
+  getVersion(): string {
+    return this.currentVersion;
+  }
+
+  setVersion(version: string): void {
+    const versionSelects =
+      this.sidebar.querySelectorAll<HTMLSelectElement>('[data-version-select]');
+    versionSelects.forEach((select) => {
+      select.value = version;
+    });
+    this.handleVersionChange(version);
+  }
+}
diff --git a/src/components/patterns/Sidebar/utils.ts b/src/components/patterns/Sidebar/utils.ts
new file mode 100644
index 0000000000..973e41120f
--- /dev/null
+++ b/src/components/patterns/Sidebar/utils.ts
@@ -0,0 +1,220 @@
+import type { Menu, MenuItem, VersionPrefix } from '@/config/types';
+import type { VersionConfig } from '@/components/patterns/VersionSwitcher/types';
+import type { LanguageCode } from '@/i18n/locales';
+
+export type SubmenuData = {
+  menu: Menu;
+  title: string;
+  id: string;
+  basePath: string;
+  versioned: VersionPrefix[];
+  level: number;
+};
+
+export function normalizePath(path: string): string {
+  return path.replace(/\/$/, '');
+}
+
+export function isVersioned(versioned: VersionPrefix[] | undefined, version: string): boolean {
+  return versioned?.includes(version as VersionPrefix) ?? false;
+}
+
+export function resolveHref(
+  href: string,
+  lang: LanguageCode,
+  basePath: string,
+  versioned: VersionPrefix[] | undefined,
+  version: string,
+  global?: boolean
+): string {
+  if (href.startsWith('http')) return href;
+  const useVersion = !global && isVersioned(versioned, version);
+  const versionPath = useVersion ? `/${version}` : '';
+  return `/${lang}${basePath}${versionPath}${href}`;
+}
+
+export function isLink(item: MenuItem): item is MenuItem & { href: string } {
+  return 'href' in item && item.href !== undefined;
+}
+
+export function hasSubmenu(item: MenuItem): item is MenuItem & { submenu: Menu } {
+  return 'submenu' in item && item.submenu !== undefined;
+}
+
+function shouldOmit(entity: { omitFrom?: VersionPrefix[] }, version: string): boolean {
+  return entity.omitFrom?.includes(version as VersionPrefix) ?? false;
+}
+
+const shouldOmitItem = (item: MenuItem, version: string): boolean => shouldOmit(item, version);
+
+export const shouldOmitSection = (
+  section: { omitFrom?: VersionPrefix[] },
+  version: string
+): boolean => shouldOmit(section, version);
+
+export function filterItems(items: MenuItem[], version: string): MenuItem[] {
+  return items.filter((item) => !shouldOmitItem(item, version));
+}
+
+export function getItemId(
+  parentId: string,
+  sectionIndex: number | null,
+  itemIndex: number
+): string {
+  return sectionIndex !== null
+    ? `${parentId}-s${sectionIndex}-i${itemIndex}`
+    : `${parentId}-i${itemIndex}`;
+}
+
+export function collectAllSubmenus(
+  menuToScan: Menu,
+  currentLevel: number,
+  currentParentId: string,
+  currentBasePath: string,
+  currentVersioned: VersionPrefix[] | undefined,
+  version: string,
+  submenus: SubmenuData[]
+): void {
+  const processItems = (items: MenuItem[], sectionIndex: number | null): void => {
+    filterItems(items, version).forEach((item, itemIndex) => {
+      if (!hasSubmenu(item)) return;
+
+      const itemId = getItemId(currentParentId, sectionIndex, itemIndex);
+      const submenuId = `submenu-${itemId}`;
+      const submenuBasePath = item.submenu.basePath || currentBasePath;
+      const submenuVersioned = item.submenu.versioned ?? currentVersioned ?? [];
+
+      submenus.push({
+        menu: item.submenu,
+        title: item.label,
+        id: submenuId,
+        basePath: submenuBasePath,
+        versioned: submenuVersioned,
+        level: currentLevel + 1,
+      });
+
+      collectAllSubmenus(
+        item.submenu,
+        currentLevel + 1,
+        submenuId,
+        submenuBasePath,
+        submenuVersioned,
+        version,
+        submenus
+      );
+    });
+  };
+
+  menuToScan.sections
+    ?.filter((section) => !shouldOmitSection(section, version))
+    .forEach((section, sectionIndex) => processItems(section.items, sectionIndex));
+
+  if (menuToScan.items) {
+    processItems(menuToScan.items, null);
+  }
+}
+
+function checkItemsForPath(
+  items: MenuItem[],
+  normalizedCurrentPath: string,
+  basePath: string,
+  versioned: VersionPrefix[] | undefined,
+  lang: LanguageCode,
+  version: string
+): boolean {
+  return filterItems(items, version).some((item) => {
+    if (isLink(item)) {
+      const href = resolveHref(item.href, lang, basePath, versioned, version, item.global);
+      const hrefWithoutHash = href.split('#')[0];
+      return normalizedCurrentPath === normalizePath(hrefWithoutHash);
+    }
+    if (hasSubmenu(item)) {
+      const nestedBasePath = item.submenu.basePath || basePath;
+      const nestedVersioned = item.submenu.versioned ?? versioned;
+      return submenuContainsCurrentPath(
+        item.submenu,
+        nestedBasePath,
+        nestedVersioned,
+        normalizedCurrentPath,
+        lang,
+        version
+      );
+    }
+    return false;
+  });
+}
+
+export function submenuContainsCurrentPath(
+  submenuMenu: Menu,
+  submenuBasePath: string,
+  submenuVersioned: VersionPrefix[] | undefined,
+  currentPath: string,
+  lang: LanguageCode,
+  version: string
+): boolean {
+  const normalizedCurrentPath = normalizePath(currentPath);
+  const filteredSections =
+    submenuMenu.sections?.filter((s) => !shouldOmitSection(s, version)) ?? [];
+
+  return (
+    filteredSections.some((section) =>
+      checkItemsForPath(
+        section.items,
+        normalizedCurrentPath,
+        submenuBasePath,
+        submenuVersioned,
+        lang,
+        version
+      )
+    ) ||
+    (submenuMenu.items
+      ? checkItemsForPath(
+          submenuMenu.items,
+          normalizedCurrentPath,
+          submenuBasePath,
+          submenuVersioned,
+          lang,
+          version
+        )
+      : false)
+  );
+}
+
+export function calculateInitialActiveLevel(
+  submenus: SubmenuData[],
+  currentPath: string,
+  lang: LanguageCode,
+  version: string
+): number {
+  return submenus.reduce((maxLevel, submenu) => {
+    const containsPath = submenuContainsCurrentPath(
+      submenu.menu,
+      submenu.basePath,
+      submenu.versioned,
+      currentPath,
+      lang,
+      version
+    );
+    return containsPath && submenu.level > maxLevel ? submenu.level : maxLevel;
+  }, 0);
+}
+
+export function groupSubmenusByLevel(submenus: SubmenuData[]): Map<number, SubmenuData[]> {
+  return submenus.reduce((map, submenu) => {
+    const levelSubmenus = map.get(submenu.level);
+    if (levelSubmenus) {
+      levelSubmenus.push(submenu);
+    } else {
+      map.set(submenu.level, [submenu]);
+    }
+    return map;
+  }, new Map<number, SubmenuData[]>());
+}
+
+export function detectVersionFromUrl(
+  currentPath: string,
+  versions: VersionConfig[],
+  defaultVersion: string
+): string {
+  return versions.find((v) => currentPath.includes(`/${v.id}/`))?.id ?? defaultVersion;
+}
diff --git a/src/components/patterns/TableOfContents/TableOfContents.astro b/src/components/patterns/TableOfContents/TableOfContents.astro
new file mode 100644
index 0000000000..cd7092d151
--- /dev/null
+++ b/src/components/patterns/TableOfContents/TableOfContents.astro
@@ -0,0 +1,152 @@
+---
+/**
+ * TableOfContents Pattern Component
+ *
+ * Displays a table of contents for blog posts.
+ * - Desktop/tablet: sticky lateral sidebar
+ * - Mobile: collapsible dropdown
+ *
+ * @example
+ * <TableOfContents headings={headings} />
+ */
+import './TableOfContents.css';
+import type { HTMLAttributes } from 'astro/types';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+import { Icon } from 'astro-icon/components';
+
+interface Heading {
+  depth: number;
+  slug: string;
+  text: string;
+}
+
+interface Props extends HTMLAttributes<'nav'> {
+  headings: Heading[];
+}
+
+const { headings, class: className, ...rest } = Astro.props;
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+const filteredHeadings = headings.filter((h) => h.depth === 2 || h.depth === 3);
+const tocHeadings =
+  filteredHeadings.length > 0
+    ? [{ depth: 2, slug: 'overview', text: t('toc.overview') }, ...filteredHeadings]
+    : [];
+---
+
+{
+  tocHeadings.length > 0 && (
+    <nav class:list={['toc', className]} aria-label={t('post.toc')} {...rest}>
+      <p class="toc__heading" aria-hidden="true">
+        {t('post.toc')}
+      </p>
+
+      <details class="toc__details">
+        <summary class="toc__summary">
+          <span class="toc__summary-label">{t('post.toc')}</span>
+          <Icon name="fluent:chevron-down-20-regular" class="toc__chevron" aria-hidden="true" />
+        </summary>
+
+        <ol class="toc__list">
+          {tocHeadings.map((heading) => (
+            <li class:list={['toc__item', `toc__item--h${heading.depth}`]}>
+              <a class="toc__link" href={`#${heading.slug}`}>
+                {heading.text}
+              </a>
+            </li>
+          ))}
+        </ol>
+      </details>
+    </nav>
+  )
+}
+
+<script>
+  function initToc(details: HTMLDetailsElement) {
+    const bp = getComputedStyle(document.documentElement)
+      .getPropertyValue('--breakpoint-md')
+      .trim();
+    const mq = window.matchMedia(`(min-width: ${bp})`);
+    const summaryLabel = details.querySelector<HTMLElement>('.toc__summary-label');
+    const defaultLabel = summaryLabel?.textContent ?? '';
+
+    function syncOpen(matches: boolean) {
+      details.open = matches;
+    }
+
+    mq.addEventListener('change', (e) => syncOpen(e.matches));
+    syncOpen(mq.matches);
+
+    details.addEventListener('toggle', () => {
+      if (mq.matches && !details.open) details.open = true;
+    });
+
+    const tocLinks = document.querySelectorAll<HTMLAnchorElement>('.toc__link');
+    if (tocLinks.length) {
+      const linkMap = new Map<string, HTMLAnchorElement>();
+      const headingEls: HTMLElement[] = [];
+
+      tocLinks.forEach((link) => {
+        const id = link.getAttribute('href')?.slice(1);
+        if (id) {
+          linkMap.set(id, link);
+          const el = document.getElementById(id);
+          if (el) headingEls.push(el);
+        }
+        link.addEventListener('click', () => {
+          if (!mq.matches) details.open = false;
+        });
+      });
+
+      let activeLink: HTMLAnchorElement | null = null;
+      const visibleHeadings = new Set<string>();
+
+      function setActive(link: HTMLAnchorElement | null) {
+        if (link === activeLink) return;
+        activeLink?.classList.remove('toc__link--active');
+        activeLink = link;
+        link?.classList.add('toc__link--active');
+        if (summaryLabel && !mq.matches) {
+          summaryLabel.textContent = link?.textContent ?? defaultLabel;
+        }
+      }
+
+      const observer = new IntersectionObserver(
+        (entries) => {
+          for (const entry of entries) {
+            if (entry.isIntersecting) {
+              visibleHeadings.add(entry.target.id);
+            } else {
+              visibleHeadings.delete(entry.target.id);
+            }
+          }
+
+          for (const el of headingEls) {
+            if (visibleHeadings.has(el.id)) {
+              setActive(linkMap.get(el.id) ?? null);
+              return;
+            }
+          }
+        },
+        { rootMargin: '0px 0px -70% 0px', threshold: 0 }
+      );
+
+      headingEls.forEach((el) => observer.observe(el));
+
+      function checkArticleBounds() {
+        if (!summaryLabel || mq.matches || headingEls.length === 0) return;
+        const atTop = headingEls[0].getBoundingClientRect().top > window.innerHeight;
+        const atBottom =
+          window.scrollY + window.innerHeight >= document.documentElement.scrollHeight - 50;
+        if (atTop || atBottom) setActive(null);
+      }
+
+      window.addEventListener('scroll', checkArticleBounds, { passive: true });
+    }
+  }
+
+  const details = document.querySelector<HTMLDetailsElement>('.toc__details');
+  if (details) initToc(details);
+</script>
diff --git a/src/components/patterns/TableOfContents/TableOfContents.css b/src/components/patterns/TableOfContents/TableOfContents.css
new file mode 100644
index 0000000000..430658e752
--- /dev/null
+++ b/src/components/patterns/TableOfContents/TableOfContents.css
@@ -0,0 +1,129 @@
+@layer patterns {
+  .toc {
+    width: 100%;
+    z-index: var(--z-index-sidebar-backdrop);
+  }
+
+  .toc__heading {
+    display: none;
+
+    @media (--md-up) {
+      display: block;
+      font-size: var(--font-size-xs);
+      font-weight: var(--font-weight-semibold);
+      color: var(--color-text-secondary);
+      text-transform: uppercase;
+      letter-spacing: var(--letter-spacing-wider);
+      margin: 0 0 var(--space-3) 0;
+    }
+  }
+
+  .toc__details {
+    border: var(--border-width-1) solid var(--color-border-mute);
+    border-radius: var(--radius-lg);
+    overflow: hidden;
+
+    @media (--md-up) {
+      border: none;
+      border-radius: 0;
+      overflow: visible;
+    }
+  }
+
+  .toc__summary {
+    display: flex;
+    align-items: center;
+    justify-content: space-between;
+    padding: var(--space-3) var(--space-4);
+    font-size: var(--font-size-sm);
+    font-weight: var(--font-weight-semibold);
+    color: var(--color-text-primary);
+    cursor: pointer;
+    list-style: none;
+    user-select: none;
+
+    &::-webkit-details-marker {
+      display: none;
+    }
+
+    &:focus-visible {
+      outline: var(--color-focus-ring) solid var(--border-width-2);
+      outline-offset: var(--border-width-1);
+    }
+
+    @media (--md-up) {
+      display: none;
+    }
+  }
+
+  .toc__chevron {
+    width: var(--space-5);
+    height: var(--space-5);
+    color: var(--color-icon-secondary);
+    transition: transform 0.2s ease;
+    flex-shrink: 0;
+
+    details[open] & {
+      transform: rotate(180deg);
+    }
+  }
+
+  .toc__list {
+    list-style: none;
+    margin: 0;
+    padding: var(--space-3) var(--space-4) var(--space-3);
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-0-5);
+    border-top: var(--border-width-1) solid var(--color-border-mute);
+
+    @media (--md-up) {
+      padding: 0;
+      border-top: none;
+      border-left: var(--border-width-1) solid var(--color-border-mute);
+    }
+  }
+
+  .toc__item--h3 {
+    padding-left: var(--space-3);
+
+    @media (--md-up) {
+      padding-left: var(--space-4);
+    }
+  }
+
+  .toc__link {
+    display: block;
+    font-size: var(--font-size-sm);
+    color: var(--color-text-secondary);
+    text-decoration: none;
+    padding: var(--space-1) 0;
+    line-height: var(--line-height-snug);
+    transition: color 0.15s ease;
+
+    @media (--md-up) {
+      padding: var(--space-1) var(--space-3);
+      border-left: var(--border-width-2) solid transparent;
+      margin-left: calc(var(--border-width-1) * -1);
+    }
+
+    &:hover {
+      color: var(--color-text-primary);
+    }
+
+    &:focus-visible {
+      outline: var(--color-focus-ring) solid var(--border-width-2);
+      outline-offset: var(--border-width-1);
+      border-radius: var(--radius-sm);
+    }
+  }
+
+  .toc__link--active {
+    color: var(--color-text-primary);
+    font-weight: var(--font-weight-medium);
+
+    @media (--md-up) {
+      border-left-color: var(--color-text-primary);
+    }
+  }
+}
diff --git a/src/components/patterns/ThemeSwitcher/ThemeSwitcher.astro b/src/components/patterns/ThemeSwitcher/ThemeSwitcher.astro
new file mode 100644
index 0000000000..df5d5b81b7
--- /dev/null
+++ b/src/components/patterns/ThemeSwitcher/ThemeSwitcher.astro
@@ -0,0 +1,79 @@
+---
+/**
+ * Theme Switcher Component
+ * Allows users to toggle between light and dark themes
+ * Persists theme preference to localStorage
+ */
+import './ThemeSwitcher.css';
+import { BodyMd } from '@/components/primitives';
+import { Icon } from 'astro-icon/components';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+interface Props {
+  showLabels?: boolean;
+}
+
+const { showLabels = true } = Astro.props;
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+<button id="theme-toggle-button" class="toggle" aria-label={t('theme.toggle')}>
+  <div class="toggle-icon">
+    <Icon
+      name="fluent:weather-moon-16-regular"
+      class="moon"
+      size="20"
+      color="var(--color-icon-primary)"
+    />
+    <Icon
+      name="fluent:weather-sunny-16-regular"
+      class="sun"
+      size="20"
+      color="var(--color-icon-primary)"
+    />
+  </div>
+  <BodyMd
+    vMargin={false}
+    class={`label-dark ${!showLabels ? 'sr-only' : ''}`}
+    aria-label={t('theme.switchToLight')}>{t('theme.switchToLight')}</BodyMd
+  >
+  <BodyMd
+    vMargin={false}
+    class={`label-light ${!showLabels ? 'sr-only' : ''}`}
+    aria-label={t('theme.switchToDark')}>{t('theme.switchToDark')}</BodyMd
+  >
+</button>
+
+<script>
+  // record frame requests
+  let rafHandle = 0;
+
+  const handleToggleClick = () => {
+    const root = document.documentElement;
+    const nextTheme = root.getAttribute('data-theme') === 'dark' ? 'light' : 'dark';
+
+    // Cancel any pending frame requests to prevent race conditions during rapid clicks
+    if (rafHandle) {
+      cancelAnimationFrame(rafHandle);
+    }
+
+    // Disable transitions
+    root.classList.add('disable-transitions');
+
+    // Apply theme
+    root.setAttribute('data-theme', nextTheme);
+    localStorage.setItem('theme', nextTheme);
+
+    // Wait for the browser to paint the new theme without transitions, then re-enable
+    // them. Double requestAnimationFrame ensures this happens after a full frame.
+    rafHandle = requestAnimationFrame(() => {
+      rafHandle = requestAnimationFrame(() => {
+        root.classList.remove('disable-transitions');
+        rafHandle = 0;
+      });
+    });
+  };
+
+  document.getElementById('theme-toggle-button')?.addEventListener('click', handleToggleClick);
+</script>
diff --git a/src/components/patterns/ThemeSwitcher/ThemeSwitcher.css b/src/components/patterns/ThemeSwitcher/ThemeSwitcher.css
new file mode 100644
index 0000000000..cfaaa5524b
--- /dev/null
+++ b/src/components/patterns/ThemeSwitcher/ThemeSwitcher.css
@@ -0,0 +1,44 @@
+@layer patterns {
+  .toggle {
+    border: 0;
+    background: none;
+    cursor: pointer;
+    display: flex;
+    align-items: center;
+    border-radius: var(--radius-base);
+    transition: var(--transition-colors);
+    gap: var(--space-3);
+  }
+
+  .toggle:hover {
+    .toggle-icon {
+      background-color: var(--color-bg-mute);
+    }
+  }
+
+  .toggle-icon {
+    padding: var(--space-2);
+    border-radius: var(--radius-base);
+    background-color: var(--color-bg-secondary);
+    transition: background-color var(--duration-200) var(--ease-in-out);
+    flex-shrink: 0;
+  }
+
+  :root[data-theme='light'] .sun,
+  :root:not([data-theme]) .sun {
+    display: none;
+  }
+
+  :root[data-theme='light'] .label-dark,
+  :root:not([data-theme]) .label-dark {
+    display: none;
+  }
+
+  :root[data-theme='dark'] .label-light {
+    display: none;
+  }
+
+  :root[data-theme='dark'] .moon {
+    display: none;
+  }
+}
diff --git a/src/components/patterns/VersionSwitcher/VersionSwitcher.astro b/src/components/patterns/VersionSwitcher/VersionSwitcher.astro
new file mode 100644
index 0000000000..21a2c4bdd8
--- /dev/null
+++ b/src/components/patterns/VersionSwitcher/VersionSwitcher.astro
@@ -0,0 +1,113 @@
+---
+/**
+ * VersionSwitcher Component
+ *
+ * A dropdown to switch between different versions of documentation.
+ * Detects the current version from the URL or fallback to the default version.
+ *
+ * @example
+ * <VersionSwitcher
+ *   versions={[
+ *     { id: '5x', label: 'v5.x', isDefault: true },
+ *     { id: '4x', label: 'v4.x' },
+ *   ]}
+ *   defaultVersion="5x"
+ *   currentPath="/en/docs/5x/getting-started"
+ * />
+ */
+
+import './VersionSwitcher.css';
+import { Icon } from 'astro-icon/components';
+import { Flex, Select } from '@/components/primitives';
+import type { SelectOption } from '@/components/primitives';
+import type { VersionConfig, VersionSwitcherProps } from './types';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+const {
+  versions,
+  defaultVersion,
+  currentPath = '',
+  class: className,
+  ...rest
+} = Astro.props as VersionSwitcherProps;
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+function getVersionFromPath(path: string, availableVersions: VersionConfig[]): string | null {
+  for (const version of availableVersions) {
+    if (path.includes(`/${version.id}/`)) {
+      return version.id;
+    }
+  }
+  return null;
+}
+
+const urlVersion = getVersionFromPath(currentPath, versions);
+const selectedVersion = urlVersion || defaultVersion;
+
+const selectOptions: SelectOption[] = versions.map((version) => ({
+  value: version.id,
+  label: version.label,
+  selected: version.id === selectedVersion,
+}));
+---
+
+<Flex
+  align="center"
+  justify="center"
+  gap="2"
+  class:list={['version-switcher', className]}
+  data-version-switcher
+  {...rest}
+>
+  <Icon
+    name="fluent:tag-28-regular"
+    size="16"
+    color="var(--color-icon-secondary)"
+    aria-hidden="true"
+  />
+  <Select
+    options={selectOptions}
+    value={selectedVersion}
+    size="md"
+    variant="default"
+    fullWidth
+    data-version-select
+    aria-label={t('version.selectLabel')}
+  />
+</Flex>
+
+<script>
+  function handleVersionChange(event: Event) {
+    const customEvent = event as CustomEvent<{ value: string }>;
+    const newVersion = customEvent.detail.value;
+    const currentPath = window.location.pathname;
+
+    const pathParts = currentPath.split('/').filter(Boolean);
+
+    const versionIndex = pathParts.findIndex((part) => /^\d+x$/.test(part));
+
+    if (versionIndex !== -1) {
+      pathParts[versionIndex] = newVersion;
+    } else if (pathParts.length >= 2) {
+      pathParts.splice(1, 0, newVersion);
+    }
+
+    window.location.href = '/' + pathParts.join('/');
+  }
+
+  function initVersionSwitcher() {
+    const versionSwitchers = document.querySelectorAll('[data-version-switcher]');
+
+    versionSwitchers.forEach((versionSwitcher) => {
+      const selectContainer = versionSwitcher.querySelector('[data-select-container]');
+      if (!selectContainer) return;
+
+      selectContainer.removeEventListener('select-change', handleVersionChange);
+      selectContainer.addEventListener('select-change', handleVersionChange);
+    });
+  }
+
+  initVersionSwitcher();
+  document.addEventListener('astro:page-load', initVersionSwitcher);
+</script>
diff --git a/src/components/patterns/VersionSwitcher/VersionSwitcher.css b/src/components/patterns/VersionSwitcher/VersionSwitcher.css
new file mode 100644
index 0000000000..de86ebd4ff
--- /dev/null
+++ b/src/components/patterns/VersionSwitcher/VersionSwitcher.css
@@ -0,0 +1,18 @@
+/**
+ * VersionSwitcher Styles
+ **/
+
+@layer patterns {
+  .version-switcher {
+    gap: var(--space-2);
+    padding-bottom: var(--space-3);
+    margin-bottom: var(--space-2);
+    border-bottom: 1px solid var(--color-border-mute);
+
+    @media (--md-up) {
+      border-bottom: 0;
+      margin-bottom: 0;
+      padding-top: var(--space-3);
+    }
+  }
+}
diff --git a/src/components/patterns/VersionSwitcher/index.ts b/src/components/patterns/VersionSwitcher/index.ts
new file mode 100644
index 0000000000..d97f9ad7dc
--- /dev/null
+++ b/src/components/patterns/VersionSwitcher/index.ts
@@ -0,0 +1,6 @@
+/**
+ * VersionSwitcher Component Exports
+ */
+
+export { default as VersionSwitcher } from './VersionSwitcher.astro';
+export type { VersionConfig, VersionSwitcherProps } from './types';
diff --git a/src/components/patterns/VersionSwitcher/types.ts b/src/components/patterns/VersionSwitcher/types.ts
new file mode 100644
index 0000000000..1ed3bed462
--- /dev/null
+++ b/src/components/patterns/VersionSwitcher/types.ts
@@ -0,0 +1,19 @@
+/**
+ * VersionSwitcher Component Types
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+
+export interface VersionConfig {
+  id: string;
+  label: string;
+  isDefault?: boolean;
+  isDeprecated?: boolean;
+}
+
+export type VersionSwitcherProps = HTMLAttributes<'div'> & {
+  versions: VersionConfig[];
+  defaultVersion: string;
+  currentPath?: string;
+  hidden?: boolean;
+};
diff --git a/src/components/patterns/WriteBanner/WriteBanner.astro b/src/components/patterns/WriteBanner/WriteBanner.astro
new file mode 100644
index 0000000000..d6a7e35d6d
--- /dev/null
+++ b/src/components/patterns/WriteBanner/WriteBanner.astro
@@ -0,0 +1,33 @@
+---
+/**
+ * WriteBanner Pattern Component
+ *
+ * A horizontal CTA banner with a text message on the left and a button link on the right.
+ *
+ * @example
+ * <WriteBanner
+ *   message="Interested in writing a post? Check out our guidelines to get started."
+ *   linkLabel="Read the guidelines"
+ *   href="/en/blog/write-post"
+ * />
+ */
+import { Icon } from 'astro-icon/components';
+import './WriteBanner.css';
+import { Button, H3 } from '@/components/primitives';
+
+interface Props {
+  message: string;
+  linkLabel: string;
+  href: string;
+}
+
+const { message, linkLabel, href } = Astro.props;
+---
+
+<div class="write-banner">
+  <H3 vMargin={false}>{message}</H3>
+  <Button as="a" variant="primary" href={href}>
+    {linkLabel}
+    <Icon name="fluent:arrow-right-16-regular" aria-hidden="true" />
+  </Button>
+</div>
diff --git a/src/components/patterns/WriteBanner/WriteBanner.css b/src/components/patterns/WriteBanner/WriteBanner.css
new file mode 100644
index 0000000000..64f0767766
--- /dev/null
+++ b/src/components/patterns/WriteBanner/WriteBanner.css
@@ -0,0 +1,28 @@
+@layer patterns {
+  .write-banner {
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-4);
+    align-items: flex-start;
+    padding: var(--space-6);
+    border: var(--border-width-1) solid var(--color-border-secondary);
+    border-radius: var(--radius-base);
+    margin-top: var(--space-16);
+    h3 {
+      white-space: pre-line;
+    }
+
+    background:
+      radial-gradient(circle at 0% 0%, var(--color-bg-primary) 0%, transparent 60%),
+      radial-gradient(circle at 100% 0%, var(--color-bg-primary) 0%, transparent 60%),
+      radial-gradient(circle at 0% 100%, var(--color-bg-primary) 0%, transparent 60%),
+      radial-gradient(circle at 100% 100%, var(--color-bg-primary) 0%, transparent 60%),
+      var(--color-bg-tertiary);
+
+    @media (--md-up) {
+      flex-direction: row;
+      align-items: center;
+      justify-content: space-between;
+    }
+  }
+}
diff --git a/src/components/patterns/WriteBanner/index.ts b/src/components/patterns/WriteBanner/index.ts
new file mode 100644
index 0000000000..37fe8b0246
--- /dev/null
+++ b/src/components/patterns/WriteBanner/index.ts
@@ -0,0 +1 @@
+export { default as WriteBanner } from './WriteBanner.astro';
diff --git a/src/components/patterns/index.ts b/src/components/patterns/index.ts
new file mode 100644
index 0000000000..2468021e90
--- /dev/null
+++ b/src/components/patterns/index.ts
@@ -0,0 +1,29 @@
+/**
+ *  Index
+ *
+ * Re-export all primitive components for easy importing
+ */
+
+export { default as AnnouncementBar } from './AnnouncementBar/AnnouncementBar.astro';
+export { default as Banner } from './Banner/Banner.astro';
+export { default as Breadcrumbs } from './Breadcrumbs/Breadcrumbs.astro';
+export { default as Header } from './Header/Header.astro';
+export { default as Hero } from './Hero/Hero.astro';
+export { default as Sidebar } from './Sidebar/Sidebar.astro';
+export { default as ThemeSwitcher } from './ThemeSwitcher/ThemeSwitcher.astro';
+export { default as VersionSwitcher } from './VersionSwitcher/VersionSwitcher.astro';
+export { default as SearchBox } from './Searchbox/Searchbox.tsx';
+export { default as LanguageSelect } from './LanguageSelect/LanguageSelect.astro';
+export { default as Footer } from './Footer/Footer.astro';
+export { default as Features } from './Features/Features.astro';
+export { default as CardList } from './CardList/CardList.astro';
+export { default as PostCard } from './PostCard/PostCard.astro';
+export { default as Pagination } from './Pagination/Pagination.astro';
+export { default as PageHead } from './PageHead/PageHead.astro';
+export { default as PageTopbar } from './PageTopbar/PageTopbar.astro';
+export { default as PostHeader } from './PostHeader/PostHeader.astro';
+export { default as TableOfContents } from './TableOfContents/TableOfContents.astro';
+export { default as WriteBanner } from './WriteBanner/WriteBanner.astro';
+export { default as RelatedContent } from './RelatedContent/RelatedContent.astro';
+export { default as DocBottomNav } from './DocBottomNav/DocBottomNav.astro';
+export { default as MiddlewareInfo } from './MiddlewareInfo/MiddlewareInfo.astro';
diff --git a/src/components/primitives/Alert/Alert.astro b/src/components/primitives/Alert/Alert.astro
new file mode 100644
index 0000000000..1f09b26795
--- /dev/null
+++ b/src/components/primitives/Alert/Alert.astro
@@ -0,0 +1,63 @@
+---
+/**
+ * Alert Primitive Component
+ *
+ * Contextual callout block with an icon, title, and description.
+ * Three severity levels map to distinct color schemes and icons.
+ *
+ * @example
+ * <Alert type="info" title="Note">
+ *   Useful background information for the reader.
+ * </Alert>
+ *
+ * <Alert type="alert" title="Caution">
+ *   Something that may cause unexpected behaviour if ignored.
+ * </Alert>
+ *
+ * <Alert type="warning" title="Warning">
+ *   A risk of data loss or breaking change.
+ * </Alert>
+ */
+
+import './Alert.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { AlertProps } from './types';
+import { Icon } from 'astro-icon/components';
+import { Body, Flex } from '@components/primitives';
+
+type Props = AlertProps & HTMLAttributes<'div'>;
+
+const { type = 'info', title, class: className, ...rest } = Astro.props;
+
+const defaultTitles: Record<string, string> = {
+  info: 'Note',
+  alert: 'Caution',
+  warning: 'Warning',
+};
+
+const resolvedTitle = title ?? defaultTitles[type];
+---
+
+<div class:list={['alert', `alert--${type}`, className]} role="note" {...rest}>
+  <Flex align="center" gap="2">
+    {
+      type === 'info' && (
+        <Icon name="fluent:info-16-regular" class="alert__icon" size="18" aria-hidden="true" />
+      )
+    }
+    {
+      type === 'alert' && (
+        <Icon name="fluent:alert-16-regular" class="alert__icon" size="18" aria-hidden="true" />
+      )
+    }
+    {
+      type === 'warning' && (
+        <Icon name="fluent:warning-16-regular" class="alert__icon" size="18" aria-hidden="true" />
+      )
+    }
+    <Body as="h3" vMargin={false} weight="bold">{resolvedTitle}</Body>
+  </Flex>
+  <div class="alert__description">
+    <slot />
+  </div>
+</div>
diff --git a/src/components/primitives/Alert/Alert.css b/src/components/primitives/Alert/Alert.css
new file mode 100644
index 0000000000..2da8cfa726
--- /dev/null
+++ b/src/components/primitives/Alert/Alert.css
@@ -0,0 +1,57 @@
+/**
+ * Alert Component Styles
+ */
+
+@layer primitives {
+  .alert {
+    display: flex;
+    flex-direction: column;
+    gap: var(--space-1);
+    padding: var(--space-4);
+    border-left-width: var(--border-width-4);
+    border-left-style: solid;
+    border-radius: 0 var(--radius-lg) var(--radius-lg) 0;
+    margin: var(--space-4) 0;
+  }
+
+  .alert__icon {
+    flex-shrink: 0;
+  }
+
+  .alert__description {
+    p {
+      margin: 0;
+    }
+  }
+
+  /* ============================================
+     VARIANTS
+     ============================================ */
+
+  .alert--info {
+    background-color: var(--color-bg-info);
+    border-color: var(--color-border-info);
+
+    .alert__icon {
+      color: var(--color-text-info);
+    }
+  }
+
+  .alert--alert {
+    background-color: var(--color-bg-warning);
+    border-color: var(--color-border-warning);
+
+    .alert__icon {
+      color: var(--color-text-warning);
+    }
+  }
+
+  .alert--warning {
+    background-color: var(--color-bg-error);
+    border-color: var(--color-border-error);
+
+    .alert__icon {
+      color: var(--color-text-error);
+    }
+  }
+}
diff --git a/src/components/primitives/Alert/types.ts b/src/components/primitives/Alert/types.ts
new file mode 100644
index 0000000000..4bc8b68c54
--- /dev/null
+++ b/src/components/primitives/Alert/types.ts
@@ -0,0 +1,12 @@
+/**
+ * Alert Component Types
+ */
+
+export type AlertType = 'info' | 'alert' | 'warning';
+
+export interface AlertProps {
+  /** Alert type — controls color scheme and icon */
+  type?: AlertType;
+  /** Title text (rendered next to the icon) */
+  title?: string;
+}
diff --git a/src/components/primitives/Avatar/Avatar.astro b/src/components/primitives/Avatar/Avatar.astro
new file mode 100644
index 0000000000..5f35183bf7
--- /dev/null
+++ b/src/components/primitives/Avatar/Avatar.astro
@@ -0,0 +1,77 @@
+---
+/**
+ * Avatar Primitive Component
+ *
+ * A rounded avatar image (or stacked images for multiple authors)
+ * with a name and optional caption displayed to the right.
+ *
+ * @example — Single author
+ * <Avatar
+ *   authors={[{ src: "/images/author.jpg", name: "John Doe" }]}
+ *   caption="Jun 05, 2025"
+ * />
+ *
+ * @example — Multiple authors
+ * <Avatar
+ *   authors={[
+ *     { src: "/images/a.jpg", name: "Alex Pit" },
+ *     { src: "/images/b.jpg", name: "Tom Cruise" },
+ *   ]}
+ *   caption="Mar 04, 2026"
+ * />
+ *
+ * @example — Small size
+ * <Avatar
+ *   authors={[{ src: "/images/author.jpg", name: "Jane Smith" }]}
+ *   caption="Mar 04, 2026"
+ *   size="sm"
+ * />
+ */
+import './Avatar.css';
+import type { HTMLAttributes } from 'astro/types';
+import { Image } from 'astro:assets';
+import { BodyMd, BodySm, Flex } from '@components/primitives';
+
+interface Author {
+  src: string;
+  alt?: string;
+  name: string;
+}
+
+interface Props extends HTMLAttributes<'div'> {
+  authors: Author[];
+  caption?: string;
+  size?: 'sm' | 'md';
+}
+
+const { authors, caption, size = 'md', class: className, ...rest } = Astro.props;
+
+const displayName = authors?.map((a) => a.name).join(', ') ?? '';
+const imgSize = size === 'sm' ? 24 : 32;
+---
+
+<Flex align="center" gap="2" class:list={[`avatar--${size}`, className]} {...rest}>
+  <div class="avatar__images">
+    {
+      authors?.map((a) => (
+        <Image
+          class="avatar__image"
+          src={a.src}
+          alt={a.alt ?? a.name}
+          width={imgSize}
+          height={imgSize}
+        />
+      ))
+    }
+  </div>
+  <div class="avatar__content">
+    <BodyMd as="span" weight="medium" vMargin={false}>{displayName}</BodyMd>
+    {
+      caption && (
+        <BodySm as="span" color="secondary" vMargin={false}>
+          {caption}
+        </BodySm>
+      )
+    }
+  </div>
+</Flex>
diff --git a/src/components/primitives/Avatar/Avatar.css b/src/components/primitives/Avatar/Avatar.css
new file mode 100644
index 0000000000..a135b6b60c
--- /dev/null
+++ b/src/components/primitives/Avatar/Avatar.css
@@ -0,0 +1,33 @@
+@layer primitives {
+  .avatar__images {
+    display: flex;
+    align-items: center;
+    flex-shrink: 0;
+  }
+
+  .avatar__image {
+    border-radius: var(--radius-full);
+    border: var(--border-width-2) solid var(--color-bg-primary);
+    object-fit: cover;
+    flex-shrink: 0;
+  }
+
+  .avatar__image + .avatar__image {
+    margin-left: calc(-1 * var(--space-2));
+  }
+
+  .avatar--md .avatar__image {
+    width: var(--size-8);
+    height: var(--size-8);
+  }
+
+  .avatar--sm .avatar__image {
+    width: var(--size-6);
+    height: var(--size-6);
+  }
+
+  .avatar__content {
+    display: flex;
+    flex-direction: column;
+  }
+}
diff --git a/src/components/primitives/Avatar/index.ts b/src/components/primitives/Avatar/index.ts
new file mode 100644
index 0000000000..8ac9988b8d
--- /dev/null
+++ b/src/components/primitives/Avatar/index.ts
@@ -0,0 +1 @@
+export { default as Avatar } from './Avatar.astro';
diff --git a/src/components/primitives/Button/Button.astro b/src/components/primitives/Button/Button.astro
new file mode 100644
index 0000000000..412bfb6f38
--- /dev/null
+++ b/src/components/primitives/Button/Button.astro
@@ -0,0 +1,54 @@
+---
+/**
+ * Button Primitive Component
+ *
+ * Interactive button with support for icon slots and variants.
+ * Can render as button, anchor, or any interactive element.
+ *
+ * @example
+ * <Button variant="primary" size="md">Click me</Button>
+ * <Button as="a" href="/docs">
+ *   <Icon slot="left" name="arrow" />
+ *   Go to docs
+ * </Button>
+ * <Button type="submit">Submit</Button>
+ *
+ * Notes:
+ * - The `disabled` prop is only supported when rendering as `<button>`.
+ * - Anchors do not support native disabled behavior.
+ */
+import './Button.css';
+import type { NativeButtonProps, AnchorProps } from './types';
+
+type Props = AnchorProps | NativeButtonProps;
+
+const props = Astro.props as Props;
+
+const {
+  as: Tag = 'button',
+  size = 'md',
+  variant = 'primary',
+  ghost = false,
+  class: className,
+  ...rest
+} = props;
+
+const isButton = Tag === 'button';
+const buttonType = isButton ? ((props as NativeButtonProps).type ?? 'button') : undefined;
+---
+
+<Tag
+  class:list={[
+    'btn',
+    `btn--size-${size}`,
+    `btn--variant-${variant}`,
+    ghost && 'btn--ghost',
+    className,
+  ]}
+  type={buttonType}
+  {...rest}
+>
+  <slot name="left" />
+  <slot />
+  <slot name="right" />
+</Tag>
diff --git a/src/components/primitives/Button/Button.css b/src/components/primitives/Button/Button.css
new file mode 100644
index 0000000000..d14a10078a
--- /dev/null
+++ b/src/components/primitives/Button/Button.css
@@ -0,0 +1,87 @@
+/**
+ * Button Component Styles
+ */
+
+@layer primitives {
+  /* ============================================
+     BASE STYLES
+     ============================================ */
+
+  .btn {
+    display: inline-flex;
+    align-items: center;
+    justify-content: center;
+    gap: var(--space-2);
+    line-height: var(--line-height-normal);
+    border: 1px solid;
+    border-radius: var(--radius-base);
+    cursor: pointer;
+    transition: all 0.2s ease;
+    white-space: nowrap;
+    text-decoration: none;
+
+    &:disabled {
+      cursor: not-allowed;
+      opacity: 0.6;
+    }
+  }
+
+  /* ============================================
+     SIZES
+     ============================================ */
+
+  .btn--size-md {
+    padding: var(--space-3);
+    font-size: var(--font-size-sm);
+  }
+
+  .btn--size-sm {
+    padding: var(--space-2) var(--space-4);
+    font-size: var(--font-size-xs);
+  }
+
+  .btn--size-xs {
+    padding: var(--space-1) var(--space-2);
+    font-size: var(--font-size-xxs);
+  }
+
+  /* ============================================
+     VARIANTS
+     ============================================ */
+
+  /* Primary variant */
+  .btn--variant-primary {
+    background-color: var(--color-bg-inverse);
+    color: var(--color-text-inverse);
+    border-color: var(--color-border-inverse);
+
+    &:hover:not(:disabled) {
+      background-color: var(--color-bg-inverse-secondary);
+      color: var(--color-text-inverse);
+    }
+  }
+
+  /* Secondary variant */
+  .btn--variant-secondary {
+    background-color: var(--color-bg-primary);
+    color: var(--color-text-primary);
+    border-color: var(--color-border-primary);
+
+    &:hover:not(:disabled) {
+      background-color: var(--color-bg-tertiary);
+      border-color: var(--color-border-secondary);
+      color: var(--color-text-primary);
+    }
+  }
+
+  /* ============================================
+     GHOST MODIFIER
+     ============================================ */
+
+  .btn--ghost {
+    &:not(:hover):not(:disabled) {
+      border-color: transparent;
+      background-color: transparent;
+    }
+  }
+}
diff --git a/src/components/primitives/Button/index.ts b/src/components/primitives/Button/index.ts
new file mode 100644
index 0000000000..1ac34f2986
--- /dev/null
+++ b/src/components/primitives/Button/index.ts
@@ -0,0 +1,12 @@
+/**
+ * Button Component Exports
+ */
+
+export { default as Button } from './Button.astro';
+export type {
+  ButtonBaseProps,
+  ButtonSize,
+  ButtonVariant,
+  AnchorProps,
+  NativeButtonProps,
+} from './types';
diff --git a/src/components/primitives/Button/types.ts b/src/components/primitives/Button/types.ts
new file mode 100644
index 0000000000..576eb25cea
--- /dev/null
+++ b/src/components/primitives/Button/types.ts
@@ -0,0 +1,29 @@
+/**
+ * Button Component Types
+ */
+import type { HTMLAttributes } from 'astro/types';
+
+export type ButtonSize = 'md' | 'sm' | 'xs';
+
+export type ButtonVariant = 'primary' | 'secondary';
+
+export interface ButtonBaseProps {
+  /** Button size variant */
+  size?: ButtonSize;
+  /** Button style variant */
+  variant?: ButtonVariant;
+  /** Ghost style (no background) */
+  ghost?: boolean;
+}
+
+export type AnchorProps = {
+  as: 'a';
+  href: string;
+} & ButtonBaseProps &
+  Omit<HTMLAttributes<'a'>, 'type' | 'href' | 'disabled'>;
+
+export type NativeButtonProps = {
+  as?: 'button';
+  type?: 'button' | 'submit' | 'reset';
+} & ButtonBaseProps &
+  HTMLAttributes<'button'>;
diff --git a/src/components/primitives/Card/Card.astro b/src/components/primitives/Card/Card.astro
new file mode 100644
index 0000000000..8e5061c243
--- /dev/null
+++ b/src/components/primitives/Card/Card.astro
@@ -0,0 +1,30 @@
+---
+/**
+ * Card Primitive Component
+ *
+ * A content card with a title and body text
+ *
+ * @example
+ * <Card title="Getting Started" body="Express is a fast, unopinionated web framework." />
+ *
+ * @example — Cards group
+ * <Card title="Installation" body="Run npm install express." />
+ * <Card title="Usage" body="Import express and create an app instance." />
+ */
+import './Card.css';
+import type { HTMLAttributes } from 'astro/types';
+import { H3, Body } from '@components/primitives';
+
+interface Props extends HTMLAttributes<'div'> {
+  title: string;
+  body: string;
+}
+
+const { title, body, class: className, ...rest } = Astro.props;
+---
+
+<div class:list={['card', className]} data-testid="card" {...rest}>
+  <H3 vMargin={false}>{title}</H3>
+  <Body>{body}</Body>
+  <slot />
+</div>
diff --git a/src/components/primitives/Card/Card.css b/src/components/primitives/Card/Card.css
new file mode 100644
index 0000000000..ddde3817cb
--- /dev/null
+++ b/src/components/primitives/Card/Card.css
@@ -0,0 +1,7 @@
+@layer primitives {
+  .card {
+    border: var(--border-width-1) solid var(--color-border-secondary);
+    border-radius: var(--radius-card);
+    padding: var(--space-6);
+  }
+}
diff --git a/src/components/primitives/Card/index.ts b/src/components/primitives/Card/index.ts
new file mode 100644
index 0000000000..adf1580922
--- /dev/null
+++ b/src/components/primitives/Card/index.ts
@@ -0,0 +1 @@
+export { default as Card } from './Card.astro';
diff --git a/src/components/primitives/Container/Container.astro b/src/components/primitives/Container/Container.astro
new file mode 100644
index 0000000000..1114b31a56
--- /dev/null
+++ b/src/components/primitives/Container/Container.astro
@@ -0,0 +1,26 @@
+---
+/**
+ * Container Layout Primitive
+ *
+ * Centers content with a max-width constraint.
+ * Use for page-level content wrapping.
+ *
+ * @example
+ * <Container>
+ *   <H1>Page Title</H1>
+ *   <Body>Content goes here</Body>
+ * </Container>
+ */
+
+import './Container.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { ContainerProps } from './types';
+
+interface Props extends HTMLAttributes<'div'>, ContainerProps {}
+
+const { as: Tag = 'div', class: className, ...rest } = Astro.props;
+---
+
+<Tag class:list={['container', className]} {...rest}>
+  <slot />
+</Tag>
diff --git a/src/components/primitives/Container/Container.css b/src/components/primitives/Container/Container.css
new file mode 100644
index 0000000000..e61f83c405
--- /dev/null
+++ b/src/components/primitives/Container/Container.css
@@ -0,0 +1,15 @@
+/**
+ * Container Component Styles
+ */
+
+@layer primitives {
+  .container {
+    width: 85%;
+    max-width: 1440px;
+    margin-inline: auto;
+
+    @media (--lg-up) {
+      width: 90%;
+    }
+  }
+}
diff --git a/src/components/primitives/Container/index.ts b/src/components/primitives/Container/index.ts
new file mode 100644
index 0000000000..ebbf2d2f82
--- /dev/null
+++ b/src/components/primitives/Container/index.ts
@@ -0,0 +1,2 @@
+export { default as Container } from './Container.astro';
+export type { ContainerProps, ContainerHTMLTag } from './types';
diff --git a/src/components/primitives/Container/types.ts b/src/components/primitives/Container/types.ts
new file mode 100644
index 0000000000..ae7781dcbf
--- /dev/null
+++ b/src/components/primitives/Container/types.ts
@@ -0,0 +1,18 @@
+/**
+ * Container Component Types
+ */
+
+export type ContainerHTMLTag =
+  | 'div'
+  | 'section'
+  | 'article'
+  | 'main'
+  | 'header'
+  | 'footer'
+  | 'aside'
+  | 'nav';
+
+export interface ContainerProps {
+  /** HTML element to render */
+  as?: ContainerHTMLTag;
+}
diff --git a/src/components/primitives/Grid/Col.astro b/src/components/primitives/Grid/Col.astro
new file mode 100644
index 0000000000..3fbf0d3d3c
--- /dev/null
+++ b/src/components/primitives/Grid/Col.astro
@@ -0,0 +1,27 @@
+---
+/**
+ * Col Component
+ *
+ * Responsive grid column. Spans 1-12 columns out of 12-column grid.
+ * Breakpoint props cascade: xs → md → lg
+ *
+ * @example
+ * <Col xs={12} md={6} lg={4}>Full mobile, half tablet, third desktop</Col>
+ * <Col xs={6}>Always half width</Col>
+ */
+
+import './Grid.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { ColProps } from './types';
+
+type Props = ColProps & HTMLAttributes<'div'>;
+
+const { xs, md, lg, class: className, ...rest } = Astro.props;
+---
+
+<div
+  class:list={['col', xs && `col-xs-${xs}`, md && `col-md-${md}`, lg && `col-lg-${lg}`, className]}
+  {...rest}
+>
+  <slot />
+</div>
diff --git a/src/components/primitives/Grid/Flex.astro b/src/components/primitives/Grid/Flex.astro
new file mode 100644
index 0000000000..c84fecb3f2
--- /dev/null
+++ b/src/components/primitives/Grid/Flex.astro
@@ -0,0 +1,37 @@
+---
+/**
+ * Flex Component
+ *
+ * Flexbox container for 1D layouts.
+ * Use for simple directional layouts, navbars, stacks.
+ *
+ * @example
+ * <Flex direction="column" gap="4" align="center">
+ *   <div>Item 1</div>
+ *   <div>Item 2</div>
+ * </Flex>
+ */
+
+import './Grid.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { FlexProps } from './types';
+
+type Props = FlexProps & HTMLAttributes<'div'>;
+
+const { direction = 'row', align, justify, wrap, gap, class: className, ...rest } = Astro.props;
+---
+
+<div
+  class:list={[
+    'flex',
+    direction && `flex--${direction}`,
+    align && `flex--align-${align}`,
+    justify && `flex--justify-${justify}`,
+    wrap && `flex--${wrap}`,
+    gap && `flex--gap-${gap}`,
+    className,
+  ]}
+  {...rest}
+>
+  <slot />
+</div>
diff --git a/src/components/primitives/Grid/FlexItem.astro b/src/components/primitives/Grid/FlexItem.astro
new file mode 100644
index 0000000000..40b4308a03
--- /dev/null
+++ b/src/components/primitives/Grid/FlexItem.astro
@@ -0,0 +1,35 @@
+---
+/**
+ * FlexItem Component
+ *
+ * Wrapper for flex items with control over grow, shrink, and basis.
+ * Use inside a Flex component to control individual item behavior.
+ *
+ * @example
+ * <Flex>
+ *   <FlexItem grow="1" shrink="0">Flexible item</FlexItem>
+ *   <FlexItem basis="auto">Auto-sized item</FlexItem>
+ * </Flex>
+ */
+
+import './Grid.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { FlexItemProps } from './types';
+
+type Props = FlexItemProps & HTMLAttributes<'div'>;
+
+const { grow, shrink, basis, flex, class: className, ...rest } = Astro.props;
+---
+
+<div
+  class:list={[
+    flex && `flex-item--flex-${flex}`,
+    !flex && grow && `flex-item--grow-${grow ? '1' : '0'}`,
+    !flex && shrink && `flex-item--shrink-${shrink ? '1' : '0'}`,
+    !flex && basis && `flex-item--basis-${basis}`,
+    className,
+  ]}
+  {...rest}
+>
+  <slot />
+</div>
diff --git a/src/components/primitives/Grid/Grid.astro b/src/components/primitives/Grid/Grid.astro
new file mode 100644
index 0000000000..4a76cc8412
--- /dev/null
+++ b/src/components/primitives/Grid/Grid.astro
@@ -0,0 +1,36 @@
+---
+/**
+ * Grid Component
+ *
+ * 12-column responsive grid container.
+ * Use with <Col> children for responsive column layouts.
+ *
+ * @example
+ * <Grid gap="4" align="center" justify="center">
+ *   <Col xs={12} md={6} lg={4}>Content</Col>
+ * </Grid>
+ */
+
+import './Grid.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { GridProps } from './types';
+
+type Props = GridProps & HTMLAttributes<'div'>;
+
+const { gap, rowGap, columnGap, align, justify, class: className, ...rest } = Astro.props;
+---
+
+<div
+  class:list={[
+    'grid',
+    gap && `grid--gap-${gap}`,
+    rowGap && `grid--row-gap-${rowGap}`,
+    columnGap && `grid--col-gap-${columnGap}`,
+    align && `grid--align-${align}`,
+    justify && `grid--justify-${justify}`,
+    className,
+  ]}
+  {...rest}
+>
+  <slot />
+</div>
diff --git a/src/components/primitives/Grid/Grid.css b/src/components/primitives/Grid/Grid.css
new file mode 100644
index 0000000000..d787c90c1b
--- /dev/null
+++ b/src/components/primitives/Grid/Grid.css
@@ -0,0 +1,571 @@
+/**
+ * Grid System Styles
+ *
+ * 12-column responsive grid with breakpoint support
+ * Includes both component classes and utility classes
+ */
+
+@layer primitives {
+  /* ============================================
+     GRID COMPONENT
+     ============================================ */
+
+  .grid {
+    display: grid;
+    grid-template-columns: repeat(12, 1fr);
+  }
+
+  /* Grid Gaps */
+  .grid--gap-0 {
+    gap: 0;
+  }
+  .grid--gap-1 {
+    gap: var(--space-1);
+  }
+  .grid--gap-2 {
+    gap: var(--space-2);
+  }
+  .grid--gap-3 {
+    gap: var(--space-3);
+  }
+  .grid--gap-4 {
+    gap: var(--space-4);
+  }
+  .grid--gap-6 {
+    gap: var(--space-6);
+  }
+  .grid--gap-8 {
+    gap: var(--space-8);
+  }
+  .grid--gap-12 {
+    gap: var(--space-12);
+  }
+  .grid--gap-16 {
+    gap: var(--space-16);
+  }
+
+  /* Row Gaps */
+  .grid--row-gap-0 {
+    row-gap: 0;
+  }
+  .grid--row-gap-1 {
+    row-gap: var(--space-1);
+  }
+  .grid--row-gap-2 {
+    row-gap: var(--space-2);
+  }
+  .grid--row-gap-3 {
+    row-gap: var(--space-3);
+  }
+  .grid--row-gap-4 {
+    row-gap: var(--space-4);
+  }
+  .grid--row-gap-6 {
+    row-gap: var(--space-6);
+  }
+  .grid--row-gap-8 {
+    row-gap: var(--space-8);
+  }
+  .grid--row-gap-12 {
+    row-gap: var(--space-12);
+  }
+  .grid--row-gap-16 {
+    row-gap: var(--space-16);
+  }
+
+  /* Column Gaps */
+  .grid--col-gap-0 {
+    column-gap: 0;
+  }
+  .grid--col-gap-1 {
+    column-gap: var(--space-1);
+  }
+  .grid--col-gap-2 {
+    column-gap: var(--space-2);
+  }
+  .grid--col-gap-3 {
+    column-gap: var(--space-3);
+  }
+  .grid--col-gap-4 {
+    column-gap: var(--space-4);
+  }
+  .grid--col-gap-6 {
+    column-gap: var(--space-6);
+  }
+  .grid--col-gap-8 {
+    column-gap: var(--space-8);
+  }
+  .grid--col-gap-12 {
+    column-gap: var(--space-12);
+  }
+  .grid--col-gap-16 {
+    column-gap: var(--space-16);
+  }
+
+  /* Align Items */
+  .grid--align-start {
+    align-items: start;
+  }
+  .grid--align-center {
+    align-items: center;
+  }
+  .grid--align-end {
+    align-items: end;
+  }
+  .grid--align-stretch {
+    align-items: stretch;
+  }
+  .grid--align-baseline {
+    align-items: baseline;
+  }
+
+  /* Justify Items */
+  .grid--justify-start {
+    justify-items: start;
+  }
+  .grid--justify-center {
+    justify-items: center;
+  }
+  .grid--justify-end {
+    justify-items: end;
+  }
+  .grid--justify-between {
+    justify-items: stretch;
+  }
+  .grid--justify-around {
+    justify-items: stretch;
+  }
+  .grid--justify-evenly {
+    justify-items: stretch;
+  }
+
+  /* ============================================
+     COL COMPONENT (Responsive Column Spans)
+     ============================================ */
+
+  /* Mobile (xs) - Base spans */
+  .col-xs-1 {
+    grid-column: span 1;
+  }
+  .col-xs-2 {
+    grid-column: span 2;
+  }
+  .col-xs-3 {
+    grid-column: span 3;
+  }
+  .col-xs-4 {
+    grid-column: span 4;
+  }
+  .col-xs-5 {
+    grid-column: span 5;
+  }
+  .col-xs-6 {
+    grid-column: span 6;
+  }
+  .col-xs-7 {
+    grid-column: span 7;
+  }
+  .col-xs-8 {
+    grid-column: span 8;
+  }
+  .col-xs-9 {
+    grid-column: span 9;
+  }
+  .col-xs-10 {
+    grid-column: span 10;
+  }
+  .col-xs-11 {
+    grid-column: span 11;
+  }
+  .col-xs-12 {
+    grid-column: span 12;
+  }
+
+  /* Tablet (md) breakpoint */
+  @media (--md-only) {
+    .col-md-1 {
+      grid-column: span 1;
+    }
+    .col-md-2 {
+      grid-column: span 2;
+    }
+    .col-md-3 {
+      grid-column: span 3;
+    }
+    .col-md-4 {
+      grid-column: span 4;
+    }
+    .col-md-5 {
+      grid-column: span 5;
+    }
+    .col-md-6 {
+      grid-column: span 6;
+    }
+    .col-md-7 {
+      grid-column: span 7;
+    }
+    .col-md-8 {
+      grid-column: span 8;
+    }
+    .col-md-9 {
+      grid-column: span 9;
+    }
+    .col-md-10 {
+      grid-column: span 10;
+    }
+    .col-md-11 {
+      grid-column: span 11;
+    }
+    .col-md-12 {
+      grid-column: span 12;
+    }
+  }
+
+  /* Desktop (lg) breakpoint */
+  @media (--lg-up) {
+    .col-lg-1 {
+      grid-column: span 1;
+    }
+    .col-lg-2 {
+      grid-column: span 2;
+    }
+    .col-lg-3 {
+      grid-column: span 3;
+    }
+    .col-lg-4 {
+      grid-column: span 4;
+    }
+    .col-lg-5 {
+      grid-column: span 5;
+    }
+    .col-lg-6 {
+      grid-column: span 6;
+    }
+    .col-lg-7 {
+      grid-column: span 7;
+    }
+    .col-lg-8 {
+      grid-column: span 8;
+    }
+    .col-lg-9 {
+      grid-column: span 9;
+    }
+    .col-lg-10 {
+      grid-column: span 10;
+    }
+    .col-lg-11 {
+      grid-column: span 11;
+    }
+    .col-lg-12 {
+      grid-column: span 12;
+    }
+  }
+
+  /* ============================================
+     FLEX COMPONENT
+     ============================================ */
+
+  .flex {
+    display: flex;
+  }
+
+  /* Direction */
+  .flex--row {
+    flex-direction: row;
+  }
+  .flex--column {
+    flex-direction: column;
+  }
+  .flex--row-reverse {
+    flex-direction: row-reverse;
+  }
+  .flex--column-reverse {
+    flex-direction: column-reverse;
+  }
+
+  /* Align Items */
+  .flex--align-start {
+    align-items: flex-start;
+  }
+  .flex--align-center {
+    align-items: center;
+  }
+  .flex--align-end {
+    align-items: flex-end;
+  }
+  .flex--align-stretch {
+    align-items: stretch;
+  }
+  .flex--align-baseline {
+    align-items: baseline;
+  }
+
+  /* Justify Content */
+  .flex--justify-start {
+    justify-content: flex-start;
+  }
+  .flex--justify-center {
+    justify-content: center;
+  }
+  .flex--justify-end {
+    justify-content: flex-end;
+  }
+  .flex--justify-between {
+    justify-content: space-between;
+  }
+  .flex--justify-around {
+    justify-content: space-around;
+  }
+  .flex--justify-evenly {
+    justify-content: space-evenly;
+  }
+
+  /* Wrap */
+  .flex--nowrap {
+    flex-wrap: nowrap;
+  }
+  .flex--wrap {
+    flex-wrap: wrap;
+  }
+  .flex--wrap-reverse {
+    flex-wrap: wrap-reverse;
+  }
+
+  /* Flex Gaps */
+  .flex--gap-0 {
+    gap: 0;
+  }
+  .flex--gap-1 {
+    gap: var(--space-1);
+  }
+  .flex--gap-2 {
+    gap: var(--space-2);
+  }
+  .flex--gap-3 {
+    gap: var(--space-3);
+  }
+  .flex--gap-4 {
+    gap: var(--space-4);
+  }
+  .flex--gap-6 {
+    gap: var(--space-6);
+  }
+  .flex--gap-8 {
+    gap: var(--space-8);
+  }
+  .flex--gap-12 {
+    gap: var(--space-12);
+  }
+  .flex--gap-16 {
+    gap: var(--space-16);
+  }
+
+  /* ============================================
+     FLEX ITEM COMPONENT
+     ============================================ */
+
+  /* Flex Grow */
+  .flex-item--grow-0 {
+    flex-grow: 0;
+  }
+  .flex-item--grow-1 {
+    flex-grow: 1;
+  }
+
+  /* Flex Shrink */
+  .flex-item--shrink-0 {
+    flex-shrink: 0;
+  }
+  .flex-item--shrink-1 {
+    flex-shrink: 1;
+  }
+
+  /* Flex Basis */
+  .flex-item--basis-0 {
+    flex-basis: 0;
+  }
+  .flex-item--basis-auto {
+    flex-basis: auto;
+  }
+  .flex-item--basis-full {
+    flex-basis: 100%;
+  }
+  .flex-item--basis-1\/2 {
+    flex-basis: 50%;
+  }
+  .flex-item--basis-1\/3 {
+    flex-basis: 33.333333%;
+  }
+  .flex-item--basis-2\/3 {
+    flex-basis: 66.666667%;
+  }
+  .flex-item--basis-1\/4 {
+    flex-basis: 25%;
+  }
+  .flex-item--basis-3\/4 {
+    flex-basis: 75%;
+  }
+
+  /* Flex Shorthand */
+  .flex-item--flex-1 {
+    flex: 1 1 0%;
+  }
+  .flex-item--flex-auto {
+    flex: 1 1 auto;
+  }
+  .flex-item--flex-initial {
+    flex: 0 1 auto;
+  }
+  .flex-item--flex-none {
+    flex: none;
+  }
+
+  /* ============================================
+     UTILITY CLASSES
+     ============================================ */
+
+  /* Grid Utilities */
+  .grid {
+    display: grid;
+  }
+
+  .grid-cols-1 {
+    grid-template-columns: repeat(1, 1fr);
+  }
+  .grid-cols-2 {
+    grid-template-columns: repeat(2, 1fr);
+  }
+  .grid-cols-3 {
+    grid-template-columns: repeat(3, 1fr);
+  }
+  .grid-cols-4 {
+    grid-template-columns: repeat(4, 1fr);
+  }
+  .grid-cols-6 {
+    grid-template-columns: repeat(6, 1fr);
+  }
+  .grid-cols-12 {
+    grid-template-columns: repeat(12, 1fr);
+  }
+
+  /* Responsive Grid Utilities */
+  @media (--md-only) {
+    .md-grid-cols-1 {
+      grid-template-columns: repeat(1, 1fr);
+    }
+    .md-grid-cols-2 {
+      grid-template-columns: repeat(2, 1fr);
+    }
+    .md-grid-cols-3 {
+      grid-template-columns: repeat(3, 1fr);
+    }
+    .md-grid-cols-4 {
+      grid-template-columns: repeat(4, 1fr);
+    }
+    .md-grid-cols-6 {
+      grid-template-columns: repeat(6, 1fr);
+    }
+    .md-grid-cols-12 {
+      grid-template-columns: repeat(12, 1fr);
+    }
+  }
+
+  @media (--lg-up) {
+    .lg-grid-cols-1 {
+      grid-template-columns: repeat(1, 1fr);
+    }
+    .lg-grid-cols-2 {
+      grid-template-columns: repeat(2, 1fr);
+    }
+    .lg-grid-cols-3 {
+      grid-template-columns: repeat(3, 1fr);
+    }
+    .lg-grid-cols-4 {
+      grid-template-columns: repeat(4, 1fr);
+    }
+    .lg-grid-cols-6 {
+      grid-template-columns: repeat(6, 1fr);
+    }
+    .lg-grid-cols-12 {
+      grid-template-columns: repeat(12, 1fr);
+    }
+  }
+
+  /* Column Span Utilities */
+  .col-span-full {
+    grid-column: 1 / -1;
+  }
+  .col-span-1 {
+    grid-column: span 1;
+  }
+  .col-span-2 {
+    grid-column: span 2;
+  }
+  .col-span-3 {
+    grid-column: span 3;
+  }
+  .col-span-4 {
+    grid-column: span 4;
+  }
+  .col-span-6 {
+    grid-column: span 6;
+  }
+  .col-span-12 {
+    grid-column: span 12;
+  }
+
+  /* Flex Utilities */
+  .flex {
+    display: flex;
+  }
+  .flex-row {
+    flex-direction: row;
+  }
+  .flex-col {
+    flex-direction: column;
+  }
+  .items-start {
+    align-items: flex-start;
+  }
+  .items-center {
+    align-items: center;
+  }
+  .items-end {
+    align-items: flex-end;
+  }
+  .justify-start {
+    justify-content: flex-start;
+  }
+  .justify-center {
+    justify-content: center;
+  }
+  .justify-end {
+    justify-content: flex-end;
+  }
+  .justify-between {
+    justify-content: space-between;
+  }
+  .flex-wrap {
+    flex-wrap: wrap;
+  }
+
+  /* Gap Utilities */
+  .gap-1 {
+    gap: var(--space-1);
+  }
+  .gap-2 {
+    gap: var(--space-2);
+  }
+  .gap-3 {
+    gap: var(--space-3);
+  }
+  .gap-4 {
+    gap: var(--space-4);
+  }
+  .gap-6 {
+    gap: var(--space-6);
+  }
+  .gap-8 {
+    gap: var(--space-8);
+  }
+}
diff --git a/src/components/primitives/Grid/index.ts b/src/components/primitives/Grid/index.ts
new file mode 100644
index 0000000000..0dc718bcaf
--- /dev/null
+++ b/src/components/primitives/Grid/index.ts
@@ -0,0 +1,12 @@
+/**
+ * Grid Layout Components
+ *
+ * Responsive grid system with 12-column layout
+ */
+
+export { default as Grid } from './Grid.astro';
+export { default as Col } from './Col.astro';
+export { default as Flex } from './Flex.astro';
+export { default as FlexItem } from './FlexItem.astro';
+
+export type { GridProps, ColProps, FlexProps, FlexItemProps, GapSize } from './types';
diff --git a/src/components/primitives/Grid/types.ts b/src/components/primitives/Grid/types.ts
new file mode 100644
index 0000000000..72121679b9
--- /dev/null
+++ b/src/components/primitives/Grid/types.ts
@@ -0,0 +1,74 @@
+/**
+ * Grid System Component Types
+ */
+
+// Shared
+export type GapSize = '0' | '1' | '2' | '3' | '4' | '6' | '8' | '12' | '16';
+
+// Grid
+export interface GridProps {
+  /** Gap between grid items */
+  gap?: GapSize;
+  /** Vertical gap override */
+  rowGap?: GapSize;
+  /** Horizontal gap override */
+  columnGap?: GapSize;
+  /** Align items on block axis */
+  align?: FlexAlign;
+  /** Justify items on inline axis */
+  justify?: FlexJustify;
+}
+
+// Col
+export type ColSpan = 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12;
+
+export interface ColProps {
+  /** Column span for mobile (xs) breakpoint */
+  xs?: ColSpan;
+  /** Column span for tablet (md) breakpoint */
+  md?: ColSpan;
+  /** Column span for desktop (lg) breakpoint */
+  lg?: ColSpan;
+}
+
+// Flex
+export type FlexDirection = 'row' | 'column' | 'row-reverse' | 'column-reverse';
+
+export type FlexAlign = 'start' | 'center' | 'end' | 'stretch' | 'baseline';
+
+export type FlexJustify = 'start' | 'center' | 'end' | 'between' | 'around' | 'evenly';
+
+export type FlexWrap = 'nowrap' | 'wrap' | 'wrap-reverse';
+
+export interface FlexProps {
+  /** Flex direction */
+  direction?: FlexDirection;
+  /** Align items on cross axis */
+  align?: FlexAlign;
+  /** Justify content on main axis */
+  justify?: FlexJustify;
+  /** Flex wrap behavior */
+  wrap?: FlexWrap;
+  /** Gap between flex items */
+  gap?: GapSize;
+}
+
+// FlexItem
+export type FlexGrow = boolean;
+
+export type FlexShrink = boolean;
+
+export type FlexBasis = '0' | 'auto' | 'full' | '1/2' | '1/3' | '2/3' | '1/4' | '3/4';
+
+export type FlexShorthand = '1' | 'auto' | 'initial' | 'none';
+
+export interface FlexItemProps {
+  /** Flex grow factor (ability to grow) */
+  grow?: FlexGrow;
+  /** Flex shrink factor (ability to shrink) */
+  shrink?: FlexShrink;
+  /** Flex basis (initial size) */
+  basis?: FlexBasis;
+  /** Flex shorthand (overrides grow/shrink/basis) */
+  flex?: FlexShorthand;
+}
diff --git a/src/components/primitives/Select/Select.astro b/src/components/primitives/Select/Select.astro
new file mode 100644
index 0000000000..1464edc2d6
--- /dev/null
+++ b/src/components/primitives/Select/Select.astro
@@ -0,0 +1,316 @@
+---
+/**
+ * Select Primitive Component
+ *
+ * An accessible custom dropdown component using the button + listbox pattern.
+ * Supports full keyboard navigation (Tab, Enter, Space, Escape, Arrow keys, Home, End)
+ * and follows ARIA best practices for accessibility.
+ *
+ * @example
+ * <Select
+ *   options={[
+ *     { value: '5x', label: 'v5.x', selected: true },
+ *     { value: '4x', label: 'v4.x' },
+ *   ]}
+ *   size="md"
+ *   variant="default"
+ *   ariaLabel="Select version"
+ * />
+ */
+
+import './Select.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { SelectBaseProps } from './types';
+import { Icon } from 'astro-icon/components';
+import { BodyMd } from '../Typography';
+
+type Props = SelectBaseProps & Omit<HTMLAttributes<'div'>, 'onChange'>;
+
+const {
+  size = 'md',
+  variant = 'default',
+  options,
+  value,
+  placeholder,
+  fullWidth = false,
+  ariaLabel = 'Select an option',
+  id,
+  name,
+  disabled = false,
+  icon,
+  hideLabel = false,
+  dropdownAlign = 'left',
+  class: className,
+  ...rest
+} = Astro.props;
+
+const selectedOption = options.find((opt) =>
+  value !== undefined ? opt.value === value : opt.selected
+);
+
+const displayLabel = selectedOption?.label || placeholder || 'Select...';
+const containerId = id || `select-${Math.random().toString(36).slice(2, 11)}`;
+---
+
+<div
+  class:list={['select-container', fullWidth && 'select-container--full-width', className]}
+  data-select-container
+  data-open="false"
+  id={containerId}
+  {...rest}
+>
+  <button
+    type="button"
+    class:list={[
+      'select-button',
+      `select-button--size-${size}`,
+      `select-button--variant-${variant}`,
+      icon && 'select-button--with-icon',
+    ]}
+    data-select-button
+    aria-haspopup="listbox"
+    aria-expanded="false"
+    aria-label={ariaLabel}
+    disabled={disabled}
+  >
+    {
+      icon && (
+        <div class="select-icon">
+          <Icon name={icon} size="20" color="var(--color-icon-primary)" aria-hidden="true" />
+        </div>
+      )
+    }
+    <BodyMd vMargin={false} class:list={['select-label', hideLabel && 'sr-only']} data-select-label>
+      {displayLabel}
+    </BodyMd>
+    {
+      !hideLabel && (
+        <Icon name="fluent:chevron-down-20-regular" class="select-caret" aria-hidden="true" />
+      )
+    }
+  </button>
+
+  <div
+    class:list={['select-dropdown', `select-dropdown--align-${dropdownAlign}`]}
+    data-select-dropdown
+    role="listbox"
+    aria-label={ariaLabel}
+  >
+    {
+      options.map((option) => (
+        <button
+          type="button"
+          class="select-option"
+          role="option"
+          aria-selected={option.value === selectedOption?.value ? 'true' : 'false'}
+          data-select-option
+          data-value={String(option.value)}
+          disabled={option.disabled}
+        >
+          <BodyMd vMargin={false}>{option.label}</BodyMd>
+        </button>
+      ))
+    }
+  </div>
+
+  {
+    name && (
+      <input
+        type="hidden"
+        name={name}
+        value={selectedOption?.value ? String(selectedOption.value) : ''}
+      />
+    )
+  }
+</div>
+
+<script>
+  function initSelect() {
+    const containers = document.querySelectorAll('[data-select-container]');
+
+    containers.forEach((container) => {
+      const button = container.querySelector('[data-select-button]') as HTMLButtonElement;
+      const dropdown = container.querySelector('[data-select-dropdown]') as HTMLElement;
+      const options = Array.from(
+        container.querySelectorAll('[data-select-option]')
+      ) as HTMLButtonElement[];
+      const label = container.querySelector('[data-select-label]') as HTMLElement;
+      const hiddenInput = container.querySelector('input[type="hidden"]') as HTMLInputElement;
+
+      if (!button || !dropdown || !options.length) return;
+
+      let isOpen = false;
+      let focusedIndex = -1;
+
+      const findNextEnabled = (startIndex: number): number => {
+        let index = (startIndex + 1) % options.length;
+        const startPos = index;
+        while (options[index]?.disabled) {
+          index = (index + 1) % options.length;
+          if (index === startPos) break;
+        }
+        return index;
+      };
+
+      const findPrevEnabled = (startIndex: number): number => {
+        let index = startIndex <= 0 ? options.length - 1 : startIndex - 1;
+        const startPos = index;
+        while (options[index]?.disabled) {
+          index = index <= 0 ? options.length - 1 : index - 1;
+          if (index === startPos) break;
+        }
+        return index;
+      };
+
+      const findFirstEnabled = (): number => {
+        let index = 0;
+        while (index < options.length && options[index]?.disabled) {
+          index++;
+        }
+        return index < options.length ? index : -1;
+      };
+
+      const findLastEnabled = (): number => {
+        let index = options.length - 1;
+        while (index >= 0 && options[index]?.disabled) {
+          index--;
+        }
+        return index;
+      };
+
+      const toggle = (open?: boolean) => {
+        if (button.disabled) return;
+
+        isOpen = open ?? !isOpen;
+        container.setAttribute('data-open', String(isOpen));
+        button.setAttribute('aria-expanded', String(isOpen));
+
+        if (isOpen) {
+          const selectedIndex = options.findIndex(
+            (opt) => opt.getAttribute('aria-selected') === 'true'
+          );
+
+          if (selectedIndex >= 0 && !options[selectedIndex].disabled) {
+            focusedIndex = selectedIndex;
+          } else {
+            focusedIndex = findFirstEnabled();
+          }
+
+          if (focusedIndex >= 0) {
+            options[focusedIndex].focus();
+          }
+        } else {
+          focusedIndex = -1;
+        }
+      };
+
+      const selectOption = (optionElement: HTMLButtonElement) => {
+        const value = optionElement.dataset.value;
+        const optionLabel = optionElement.textContent?.trim();
+
+        if (!value || !optionLabel) return;
+
+        options.forEach((opt) => {
+          opt.setAttribute('aria-selected', opt === optionElement ? 'true' : 'false');
+        });
+
+        label.textContent = optionLabel;
+
+        if (hiddenInput) {
+          hiddenInput.value = value;
+        }
+
+        const changeEvent = new CustomEvent('select-change', {
+          detail: { value, label: optionLabel },
+          bubbles: true,
+        });
+        container.dispatchEvent(changeEvent);
+
+        toggle(false);
+        button.focus();
+      };
+
+      const handleClickOutside = (e: MouseEvent) => {
+        if (!container.contains(e.target as Node)) {
+          toggle(false);
+        }
+      };
+
+      const handleKeyDown = (e: KeyboardEvent) => {
+        if (!isOpen) {
+          if (e.key === 'Enter' || e.key === ' ' || e.key === 'ArrowDown' || e.key === 'ArrowUp') {
+            e.preventDefault();
+            toggle(true);
+          }
+          return;
+        }
+
+        switch (e.key) {
+          case 'Escape':
+            e.preventDefault();
+            toggle(false);
+            button.focus();
+            break;
+
+          case 'ArrowDown':
+            e.preventDefault();
+            focusedIndex = findNextEnabled(focusedIndex);
+            options[focusedIndex].focus();
+            break;
+
+          case 'ArrowUp':
+            e.preventDefault();
+            focusedIndex = findPrevEnabled(focusedIndex);
+            options[focusedIndex].focus();
+            break;
+
+          case 'Home':
+            e.preventDefault();
+            focusedIndex = findFirstEnabled();
+            if (focusedIndex >= 0) options[focusedIndex].focus();
+            break;
+
+          case 'End':
+            e.preventDefault();
+            focusedIndex = findLastEnabled();
+            if (focusedIndex >= 0) options[focusedIndex].focus();
+            break;
+        }
+      };
+
+      button.addEventListener('click', () => toggle());
+      button.addEventListener('keydown', handleKeyDown);
+
+      options.forEach((option, index) => {
+        option.addEventListener('click', () => {
+          if (!option.disabled) {
+            selectOption(option);
+          }
+        });
+
+        option.addEventListener('keydown', (e) => {
+          if ((e.key === 'Enter' || e.key === ' ') && !option.disabled) {
+            e.preventDefault();
+            selectOption(option);
+            return;
+          }
+          handleKeyDown(e);
+        });
+
+        option.addEventListener('focus', () => {
+          focusedIndex = index;
+        });
+      });
+
+      document.addEventListener('click', handleClickOutside);
+
+      document.addEventListener('astro:before-preparation', () => {
+        document.removeEventListener('click', handleClickOutside);
+      });
+    });
+  }
+
+  initSelect();
+
+  document.addEventListener('astro:page-load', initSelect);
+</script>
diff --git a/src/components/primitives/Select/Select.css b/src/components/primitives/Select/Select.css
new file mode 100644
index 0000000000..22c3786bdf
--- /dev/null
+++ b/src/components/primitives/Select/Select.css
@@ -0,0 +1,206 @@
+/**
+ * Select Primitive Styles
+ */
+
+@layer primitives {
+  .select-container {
+    position: relative;
+    display: inline-flex;
+    align-items: center;
+  }
+
+  .select-container--full-width {
+    width: 100%;
+  }
+
+  .select-button {
+    cursor: pointer;
+    position: relative;
+    display: inline-flex;
+    align-items: center;
+    gap: var(--space-2);
+    background-color: var(--color-bg-secondary);
+    border: 1px solid var(--color-border-mute);
+    border-radius: var(--radius-base);
+    transition:
+      border-color 0.2s ease,
+      background-color 0.2s ease;
+    font-family: inherit;
+    color: var(--color-text-primary);
+    width: 100%;
+  }
+
+  .select-button--size-sm {
+    padding: var(--space-1) var(--space-2);
+    font-size: var(--font-size-xs);
+  }
+
+  .select-button--size-md {
+    padding: var(--space-2) var(--space-3);
+    font-size: var(--font-size-sm);
+    font-weight: var(--font-weight-medium);
+  }
+
+  .select-button--size-lg {
+    padding: var(--space-3) var(--space-4);
+    font-size: var(--font-size-base);
+  }
+
+  .select-button--variant-default {
+    background-color: var(--color-bg-secondary);
+    border-color: var(--color-border-mute);
+  }
+
+  .select-button--variant-ghost {
+    background-color: transparent;
+    border-color: transparent;
+  }
+
+  .select-button--variant-ghost:hover {
+    background-color: var(--color-bg-hover);
+  }
+
+  .select-button--variant-minimal {
+    background-color: transparent;
+    border: none;
+    padding-left: 0;
+  }
+
+  .select-button--variant-icon {
+    background-color: transparent;
+    border: none;
+    padding: 0;
+    width: auto;
+  }
+
+  .select-icon {
+    padding: var(--space-2);
+    border-radius: var(--radius-base);
+    background-color: var(--color-bg-secondary);
+    transition: background-color var(--duration-200) var(--ease-in-out);
+    flex-shrink: 0;
+    display: flex;
+    align-items: center;
+    justify-content: center;
+  }
+
+  .select-button--variant-icon:hover .select-icon {
+    background-color: var(--color-bg-mute);
+  }
+
+  .select-button:hover:not(:disabled) {
+    border-color: var(--color-border-primary);
+  }
+
+  .select-button:focus-visible {
+    outline: 2px solid var(--color-focus-ring);
+    outline-offset: 2px;
+  }
+
+  .select-button:disabled {
+    opacity: 0.5;
+    cursor: not-allowed;
+  }
+
+  .select-caret {
+    margin-left: auto;
+    color: var(--color-icon-secondary);
+    width: 16px;
+    height: 16px;
+    flex-shrink: 0;
+    transition: transform 0.2s ease;
+  }
+
+  .select-container[data-open='true'] .select-caret {
+    transform: rotate(180deg);
+  }
+
+  .select-dropdown {
+    position: absolute;
+    top: calc(100% + var(--space-1));
+    width: 100%;
+    min-width: var(--size-24);
+    background-color: var(--color-bg-primary);
+    border: 1px solid var(--color-border-secondary);
+    border-radius: var(--radius-lg);
+    z-index: 100;
+    padding: 0;
+    opacity: 0;
+    visibility: hidden;
+    transform: translateY(calc(-1 * var(--space-2)));
+    transition:
+      opacity 0.2s,
+      transform 0.2s,
+      visibility 0.2s;
+    max-height: var(--size-96);
+    overflow-y: auto;
+  }
+
+  .select-dropdown--align-left {
+    left: 0;
+    right: auto;
+  }
+
+  .select-dropdown--align-right {
+    right: 0;
+    left: auto;
+  }
+
+  .select-container[data-open='true'] .select-dropdown {
+    opacity: 1;
+    visibility: visible;
+    transform: translateY(0);
+  }
+
+  /* Option Styles */
+  .select-option {
+    display: flex;
+    align-items: center;
+    width: 100%;
+    padding: var(--space-2) var(--space-3);
+    background-color: transparent;
+    border: none;
+    cursor: pointer;
+    font: inherit;
+    color: var(--color-text-primary);
+    text-align: left;
+    transition: background-color 0.2s;
+
+    &:first-child {
+      border-top-left-radius: var(--radius-lg);
+      border-top-right-radius: var(--radius-lg);
+    }
+
+    &:last-child {
+      border-bottom-left-radius: var(--radius-lg);
+      border-bottom-right-radius: var(--radius-lg);
+    }
+  }
+
+  .select-option:focus-visible {
+    outline: 2px solid var(--color-focus-ring);
+    outline-offset: -2px;
+    background-color: var(--color-bg-tertiary);
+  }
+
+  .select-option:hover {
+    background-color: var(--color-bg-tertiary);
+  }
+
+  .select-option[aria-selected='true'] {
+    background: var(--color-bg-secondary);
+  }
+
+  .select-option:disabled {
+    opacity: 0.5;
+    cursor: not-allowed;
+  }
+
+  .select-label {
+    flex: 1;
+    text-align: left;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    white-space: nowrap;
+  }
+}
diff --git a/src/components/primitives/Select/index.ts b/src/components/primitives/Select/index.ts
new file mode 100644
index 0000000000..bedb311287
--- /dev/null
+++ b/src/components/primitives/Select/index.ts
@@ -0,0 +1,6 @@
+/**
+ * Select Primitive Exports
+ */
+
+export { default as Select } from './Select.astro';
+export type { SelectBaseProps, SelectOption, SelectSize, SelectVariant } from './types';
diff --git a/src/components/primitives/Select/types.ts b/src/components/primitives/Select/types.ts
new file mode 100644
index 0000000000..6be4b26d03
--- /dev/null
+++ b/src/components/primitives/Select/types.ts
@@ -0,0 +1,50 @@
+/**
+ * Select Primitive Types
+ */
+
+export interface SelectOption<T = string> {
+  /** Value of the option */
+  value: T;
+  /** Display label */
+  label: string;
+  /** Whether the option is selected */
+  selected?: boolean;
+  /** Whether the option is disabled */
+  disabled?: boolean;
+  /** Optional data to pass to custom renderers */
+  data?: Record<string, unknown>;
+}
+
+export type SelectSize = 'sm' | 'md' | 'lg';
+export type SelectVariant = 'default' | 'ghost' | 'minimal' | 'icon';
+
+export interface SelectBaseProps<T = string> {
+  /** Size variant */
+  size?: SelectSize;
+  /** Style variant */
+  variant?: SelectVariant;
+  /** Options for the select */
+  options: SelectOption<T>[];
+  /** Currently selected value */
+  value?: T;
+  /** Placeholder text when no value is selected */
+  placeholder?: string;
+  /** Full width select */
+  fullWidth?: boolean;
+  /** Aria label for the select button */
+  ariaLabel?: string;
+  /** ID for the select container */
+  id?: string;
+  /** Name attribute for form submission */
+  name?: string;
+  /** Whether the select is disabled */
+  disabled?: boolean;
+  /** Callback when selection changes */
+  onChange?: (value: T) => void;
+  /** Icon name to display (for icon variant) */
+  icon?: string;
+  /** Whether to hide the label (icon-only mode) */
+  hideLabel?: boolean;
+  /** Dropdown alignment relative to the button */
+  dropdownAlign?: 'left' | 'right';
+}
diff --git a/src/components/primitives/Tabs/Tabs.astro b/src/components/primitives/Tabs/Tabs.astro
new file mode 100644
index 0000000000..7d2b974f0f
--- /dev/null
+++ b/src/components/primitives/Tabs/Tabs.astro
@@ -0,0 +1,100 @@
+---
+/**
+ * Tabs Primitive Component
+ *
+ * A tab strip for filtering or navigating between sections.
+ * Supports keyboard navigation (ArrowLeft/Right, Home, End) and
+ * dispatches a `tabs-change` CustomEvent (bubbles) on tab selection.
+ *
+ * @example
+ * <Tabs
+ *   tabs={[{ label: 'All', value: 'all' }, { label: 'Release', value: 'release' }]}
+ *   defaultValue="all"
+ * />
+ */
+import './Tabs.css';
+import type { HTMLAttributes } from 'astro/types';
+
+export interface TabItem {
+  label: string;
+  value: string;
+}
+
+interface Props extends HTMLAttributes<'div'> {
+  tabs: TabItem[];
+  defaultValue?: string;
+}
+
+const { tabs, defaultValue = tabs[0]?.value, class: className, ...rest } = Astro.props;
+---
+
+<div class:list={['tabs', className]} role="tablist" {...rest}>
+  {
+    tabs.map((tab) => (
+      <button
+        role="tab"
+        type="button"
+        class:list={['tabs__tab', tab.value === defaultValue && 'tabs__tab--active']}
+        aria-selected={tab.value === defaultValue ? 'true' : 'false'}
+        tabindex={tab.value === defaultValue ? 0 : -1}
+        data-tabs-value={tab.value}
+      >
+        {tab.label}
+      </button>
+    ))
+  }
+</div>
+
+<script>
+  function initTabs() {
+    const tabbars = document.querySelectorAll<HTMLElement>('.tabs[role="tablist"]');
+
+    tabbars.forEach((tabbar) => {
+      const buttons = Array.from(tabbar.querySelectorAll<HTMLButtonElement>('[role="tab"]'));
+
+      const activate = (btn: HTMLButtonElement) => {
+        buttons.forEach((b) => {
+          const isActive = b === btn;
+          b.setAttribute('aria-selected', String(isActive));
+          b.setAttribute('tabindex', isActive ? '0' : '-1');
+          b.classList.toggle('tabs__tab--active', isActive);
+        });
+
+        tabbar.dispatchEvent(
+          new CustomEvent('tabs-change', {
+            detail: { value: btn.dataset.tabsValue },
+            bubbles: true,
+          })
+        );
+      };
+
+      buttons.forEach((btn, index) => {
+        btn.addEventListener('click', () => activate(btn));
+
+        btn.addEventListener('keydown', (e) => {
+          let targetIndex: number | null = null;
+
+          if (e.key === 'ArrowRight') {
+            targetIndex = (index + 1) % buttons.length;
+          } else if (e.key === 'ArrowLeft') {
+            targetIndex = (index - 1 + buttons.length) % buttons.length;
+          } else if (e.key === 'Home') {
+            targetIndex = 0;
+          } else if (e.key === 'End') {
+            targetIndex = buttons.length - 1;
+          }
+
+          if (targetIndex !== null) {
+            e.preventDefault();
+            const target = buttons[targetIndex];
+            target?.focus();
+            activate(target);
+          }
+        });
+      });
+    });
+  }
+
+  initTabs();
+  document.addEventListener('astro:page-load', initTabs);
+</script>
diff --git a/src/components/primitives/Tabs/Tabs.css b/src/components/primitives/Tabs/Tabs.css
new file mode 100644
index 0000000000..3c5728ae96
--- /dev/null
+++ b/src/components/primitives/Tabs/Tabs.css
@@ -0,0 +1,47 @@
+@layer primitives {
+  .tabs {
+    display: flex;
+    flex-wrap: wrap;
+    gap: var(--space-2);
+    margin: var(--space-8) 0;
+  }
+
+  .tabs__tab {
+    display: inline-flex;
+    align-items: center;
+    padding: var(--space-2) var(--space-3);
+    border-radius: var(--radius-full);
+    border: 1px solid transparent;
+    background-color: transparent;
+    color: var(--color-text-secondary);
+    font-size: var(--font-size-sm);
+    font-weight: var(--font-weight-medium);
+    line-height: var(--line-height-tight);
+    white-space: nowrap;
+    cursor: pointer;
+    transition:
+      background-color 0.15s ease,
+      color 0.15s ease,
+      border-color 0.15s ease;
+
+    &:hover:not(.tabs__tab--active) {
+      background-color: var(--color-bg-mute);
+      color: var(--color-text-primary);
+    }
+
+    &:focus-visible {
+      outline: 2px solid var(--color-border-inverse);
+      outline-offset: 2px;
+    }
+  }
+
+  .tabs__tab--active {
+    background-color: var(--color-bg-inverse);
+    color: var(--color-text-inverse);
+    border-color: var(--color-border-inverse);
+
+    &:hover {
+      background-color: var(--color-bg-inverse-secondary);
+    }
+  }
+}
diff --git a/src/components/primitives/Tabs/index.ts b/src/components/primitives/Tabs/index.ts
new file mode 100644
index 0000000000..11ece37d1f
--- /dev/null
+++ b/src/components/primitives/Tabs/index.ts
@@ -0,0 +1,2 @@
+export { default as Tabs } from './Tabs.astro';
+export type { TabItem } from './Tabs.astro';
diff --git a/src/components/primitives/Tag/Tag.astro b/src/components/primitives/Tag/Tag.astro
new file mode 100644
index 0000000000..6f57c35a52
--- /dev/null
+++ b/src/components/primitives/Tag/Tag.astro
@@ -0,0 +1,21 @@
+---
+/**
+ * Tag Primitive Component
+ *
+ * A pill-shaped label for categorizing or tagging content.
+ *
+ * @example
+ * <Tag>Security</Tag>
+ * <Tag>Release</Tag>
+ */
+import './Tag.css';
+import type { HTMLAttributes } from 'astro/types';
+
+type Props = HTMLAttributes<'span'>;
+
+const { class: className, ...rest } = Astro.props;
+---
+
+<span class:list={['tag', className]} {...rest}>
+  <slot />
+</span>
diff --git a/src/components/primitives/Tag/Tag.css b/src/components/primitives/Tag/Tag.css
new file mode 100644
index 0000000000..1b5a8c7b3c
--- /dev/null
+++ b/src/components/primitives/Tag/Tag.css
@@ -0,0 +1,15 @@
+@layer primitives {
+  .tag {
+    display: inline-block;
+    padding: var(--space-1) var(--space-2);
+    border-radius: var(--radius-md);
+    background-color: var(--color-bg-mute);
+    color: var(--color-text-primary);
+    font-size: var(--font-size-xs);
+    font-weight: var(--font-weight-medium);
+    line-height: var(--line-height-tight);
+    white-space: nowrap;
+    text-transform: capitalize;
+    margin: 0;
+  }
+}
diff --git a/src/components/primitives/Tag/index.ts b/src/components/primitives/Tag/index.ts
new file mode 100644
index 0000000000..1d7f4bd85d
--- /dev/null
+++ b/src/components/primitives/Tag/index.ts
@@ -0,0 +1 @@
+export { default as Tag } from './Tag.astro';
diff --git a/src/components/primitives/Typography/Body.astro b/src/components/primitives/Typography/Body.astro
new file mode 100644
index 0000000000..03cf26cac5
--- /dev/null
+++ b/src/components/primitives/Typography/Body.astro
@@ -0,0 +1,31 @@
+---
+/**
+ * Body - Default paragraph text
+ *
+ * @example
+ * <Body>Regular paragraph text.</Body>
+ * <Body as="span">Inline body text</Body>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type BaseProps = {
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+  vMargin?: boolean;
+};
+
+type Props =
+  | ({ as?: 'p' } & BaseProps & HTMLAttributes<'p'>)
+  | ({ as: 'span' } & BaseProps & HTMLAttributes<'span'>)
+  | ({ as: 'small' } & BaseProps & HTMLAttributes<'small'>)
+  | ({ as: 'label' } & BaseProps & HTMLAttributes<'label'>);
+
+const { as = 'p', ...rest } = Astro.props as Props;
+---
+
+<Typography as={as} variant="body" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/BodyMd.astro b/src/components/primitives/Typography/BodyMd.astro
new file mode 100644
index 0000000000..71ec281940
--- /dev/null
+++ b/src/components/primitives/Typography/BodyMd.astro
@@ -0,0 +1,27 @@
+---
+/**
+ * BodyMd - Medium body text
+ *
+ * @example
+ * <BodyMd>Medium sized content.</BodyMd>
+ * <BodyMd color="secondary">Subdued helper text</BodyMd>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyBaseProps } from './types.ts';
+
+type BaseProps = Omit<TypographyBaseProps, 'variant' | 'as'>;
+
+type Props =
+  | ({ as?: 'span' } & BaseProps & HTMLAttributes<'span'>)
+  | ({ as: 'p' } & BaseProps & HTMLAttributes<'p'>)
+  | ({ as: 'small' } & BaseProps & HTMLAttributes<'small'>)
+  | ({ as: 'label' } & BaseProps & HTMLAttributes<'label'>);
+
+const { as = 'span', ...rest } = Astro.props as Props;
+---
+
+<Typography as={as} variant="body-md" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/BodySm.astro b/src/components/primitives/Typography/BodySm.astro
new file mode 100644
index 0000000000..2739bfbaea
--- /dev/null
+++ b/src/components/primitives/Typography/BodySm.astro
@@ -0,0 +1,30 @@
+---
+/**
+ * BodySm - Smaller body text / fine print
+ *
+ * @example
+ * <BodySm>Fine print or secondary content.</BodySm>
+ * <BodySm color="secondary">Subdued helper text</BodySm>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type BaseProps = {
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+};
+
+type Props =
+  | ({ as?: 'small' } & BaseProps & HTMLAttributes<'small'>)
+  | ({ as: 'p' } & BaseProps & HTMLAttributes<'p'>)
+  | ({ as: 'span' } & BaseProps & HTMLAttributes<'span'>)
+  | ({ as: 'label' } & BaseProps & HTMLAttributes<'label'>);
+
+const { as = 'small', ...rest } = Astro.props as Props;
+---
+
+<Typography as={as} variant="body-sm" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/BodyXs.astro b/src/components/primitives/Typography/BodyXs.astro
new file mode 100644
index 0000000000..55b90a67c5
--- /dev/null
+++ b/src/components/primitives/Typography/BodyXs.astro
@@ -0,0 +1,30 @@
+---
+/**
+ * BodyXs - Extra small body text
+ *
+ * @example
+ * <BodyXs>Fine print text</BodyXs>
+ * <BodyXs color="secondary">Subdued small text</BodyXs>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type BaseProps = {
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+};
+
+type Props =
+  | ({ as?: 'small' } & BaseProps & HTMLAttributes<'small'>)
+  | ({ as: 'p' } & BaseProps & HTMLAttributes<'p'>)
+  | ({ as: 'span' } & BaseProps & HTMLAttributes<'span'>)
+  | ({ as: 'label' } & BaseProps & HTMLAttributes<'label'>);
+
+const { as = 'small', ...rest } = Astro.props as Props;
+---
+
+<Typography as={as} variant="body-xs" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/Code.astro b/src/components/primitives/Typography/Code.astro
new file mode 100644
index 0000000000..03e28d055b
--- /dev/null
+++ b/src/components/primitives/Typography/Code.astro
@@ -0,0 +1,29 @@
+---
+/**
+ * Code - Inline monospace text
+ *
+ * @example
+ * <Code>npm install express</Code>
+ * <Code as="pre">Multi-line code block</Code>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type BaseProps = {
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+};
+
+type Props =
+  | ({ as?: 'code' } & BaseProps & HTMLAttributes<'code'>)
+  | ({ as: 'pre' } & BaseProps & HTMLAttributes<'pre'>)
+  | ({ as: 'span' } & BaseProps & HTMLAttributes<'span'>);
+
+const { as = 'code', ...rest } = Astro.props as Props;
+---
+
+<Typography as={as} variant="code" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/H1.astro b/src/components/primitives/Typography/H1.astro
new file mode 100644
index 0000000000..c1877845fb
--- /dev/null
+++ b/src/components/primitives/Typography/H1.astro
@@ -0,0 +1,28 @@
+---
+/**
+ * H1 - Page title heading
+ *
+ * @example
+ * <H1>Page Title</H1>
+ * <H1 as="h2">Styled as h1, rendered as h2</H1>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type HTMLTag = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6';
+
+interface Props extends HTMLAttributes<'h1'> {
+  as?: HTMLTag;
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+  vMargin?: boolean;
+}
+
+const { as = 'h1', ...rest } = Astro.props;
+---
+
+<Typography as={as} variant="h1" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/H2.astro b/src/components/primitives/Typography/H2.astro
new file mode 100644
index 0000000000..b4cf48a887
--- /dev/null
+++ b/src/components/primitives/Typography/H2.astro
@@ -0,0 +1,28 @@
+---
+/**
+ * H2 - Section heading
+ *
+ * @example
+ * <H2>Section Title</H2>
+ * <H2 as="h3">Styled as h2, rendered as h3</H2>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type HTMLTag = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6';
+
+interface Props extends HTMLAttributes<'h2'> {
+  as?: HTMLTag;
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+  vMargin?: boolean;
+}
+
+const { as = 'h2', ...rest } = Astro.props;
+---
+
+<Typography as={as} variant="h2" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/H3.astro b/src/components/primitives/Typography/H3.astro
new file mode 100644
index 0000000000..f40d68f9a1
--- /dev/null
+++ b/src/components/primitives/Typography/H3.astro
@@ -0,0 +1,28 @@
+---
+/**
+ * H3 - Subsection heading
+ *
+ * @example
+ * <H3>Subsection Title</H3>
+ * <H3 as="h4">Styled as h3, rendered as h4</H3>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type HTMLTag = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6';
+
+interface Props extends HTMLAttributes<'h3'> {
+  as?: HTMLTag;
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+  vMargin?: boolean;
+}
+
+const { as = 'h3', ...rest } = Astro.props;
+---
+
+<Typography as={as} variant="h3" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/H4.astro b/src/components/primitives/Typography/H4.astro
new file mode 100644
index 0000000000..44db66c0d2
--- /dev/null
+++ b/src/components/primitives/Typography/H4.astro
@@ -0,0 +1,27 @@
+---
+/**
+ * H4 - Card/smaller section heading
+ *
+ * @example
+ * <H4>Card Title</H4>
+ * <H4 as="h5">Styled as h4, rendered as h5</H4>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type HTMLTag = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6';
+
+interface Props extends HTMLAttributes<'h4'> {
+  as?: HTMLTag;
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+}
+
+const { as = 'h4', ...rest } = Astro.props;
+---
+
+<Typography as={as} variant="h4" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/H5.astro b/src/components/primitives/Typography/H5.astro
new file mode 100644
index 0000000000..a78912a051
--- /dev/null
+++ b/src/components/primitives/Typography/H5.astro
@@ -0,0 +1,27 @@
+---
+/**
+ * H5 - Lead/intro paragraph text
+ *
+ * @example
+ * <H5>Introduction paragraph with larger text.</H5>
+ */
+
+import type { HTMLAttributes } from 'astro/types';
+import Typography from './Typography.astro';
+import type { TypographyColor, TypographyWeight } from './types.ts';
+
+type HTMLTag = 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6';
+
+interface Props extends HTMLAttributes<'h5'> {
+  as?: HTMLTag;
+  color?: TypographyColor;
+  weight?: TypographyWeight;
+  vMargin?: boolean;
+}
+
+const { as = 'h5', ...rest } = Astro.props;
+---
+
+<Typography as={as} variant="h5" {...rest}>
+  <slot />
+</Typography>
diff --git a/src/components/primitives/Typography/Typography.astro b/src/components/primitives/Typography/Typography.astro
new file mode 100644
index 0000000000..eed8c748a7
--- /dev/null
+++ b/src/components/primitives/Typography/Typography.astro
@@ -0,0 +1,51 @@
+---
+/**
+ * Typography Primitive Component (Base)
+ *
+ * Low-level polymorphic text component. This is the foundation for all
+ * typography shorthand components (H1, H2, Body, etc.).
+ *
+ * PREFER SHORTHAND COMPONENTS for better DX:
+ * - <H1>Page Title</H1>
+ * - <H1 as="h2">Styled as H1, rendered as h2</H1>
+ * - <Body color="secondary">Subdued text</Body>
+ * - <Code>npm install express</Code>
+ *
+ * Use this base component only when you need full control over variant + element.
+ */
+import './Typography.css';
+import type { HTMLAttributes } from 'astro/types';
+import type { TypographyBaseProps } from './types';
+
+type Props = TypographyBaseProps & HTMLAttributes<'p'>;
+
+const {
+  as: Tag = 'p',
+  variant = 'body',
+  color = 'primary',
+  center,
+  left,
+  right,
+  weight,
+  vMargin = true,
+  class: className,
+  ...rest
+} = Astro.props;
+---
+
+<Tag
+  class:list={[
+    'text',
+    `${variant}`,
+    `text--color-${color}`,
+    weight && `text--weight-${weight}`,
+    center && 'text-center',
+    left && 'text-left',
+    right && 'text-right',
+    !vMargin && 'text--no-v-margin',
+    className,
+  ]}
+  {...rest}
+>
+  <slot />
+</Tag>
diff --git a/src/components/primitives/Typography/Typography.css b/src/components/primitives/Typography/Typography.css
new file mode 100644
index 0000000000..c3f3a48206
--- /dev/null
+++ b/src/components/primitives/Typography/Typography.css
@@ -0,0 +1,75 @@
+/**
+ * Typography Component Styles
+ */
+
+@layer primitives {
+  /* ============================================
+       COLORS
+       ============================================ */
+
+  .text--color-primary {
+    color: var(--color-text-primary);
+  }
+
+  .text--color-secondary {
+    color: var(--color-text-secondary);
+  }
+
+  .text--color-tertiary {
+    color: var(--color-text-tertiary);
+  }
+
+  .text--color-inverse {
+    color: var(--color-text-inverse);
+  }
+
+  .text--color-mute {
+    color: var(--color-text-mute);
+  }
+
+  .text--color-success {
+    color: var(--color-text-success);
+  }
+
+  .text--color-warning {
+    color: var(--color-text-warning);
+  }
+
+  .text--color-error {
+    color: var(--color-text-error);
+  }
+
+  .text--color-inherit {
+    color: inherit;
+  }
+
+  /* ============================================
+       WEIGHTS (Overrides)
+       ============================================ */
+  .text--weight-light {
+    font-weight: var(--font-weight-light);
+  }
+
+  .text--weight-normal {
+    font-weight: var(--font-weight-normal);
+  }
+
+  .text--weight-medium {
+    font-weight: var(--font-weight-medium);
+  }
+
+  .text--weight-semibold {
+    font-weight: var(--font-weight-semibold);
+  }
+
+  .text--weight-bold {
+    font-weight: var(--font-weight-bold);
+  }
+
+  /* ============================================
+       SPACING
+       ============================================ */
+  .text--no-v-margin {
+    margin-block: 0;
+  }
+}
diff --git a/src/components/primitives/Typography/index.ts b/src/components/primitives/Typography/index.ts
new file mode 100644
index 0000000000..1868eaf40e
--- /dev/null
+++ b/src/components/primitives/Typography/index.ts
@@ -0,0 +1,28 @@
+/**
+ * Typography Components
+ *
+ * Base component + shorthand variants for better DX
+ */
+
+// Base component (full control)
+export { default as Typography } from './Typography.astro';
+
+// Shorthand components (preset variants)
+export { default as H1 } from './H1.astro';
+export { default as H2 } from './H2.astro';
+export { default as H3 } from './H3.astro';
+export { default as H4 } from './H4.astro';
+export { default as H5 } from './H5.astro';
+export { default as Body } from './Body.astro';
+export { default as BodyMd } from './BodyMd.astro';
+export { default as BodySm } from './BodySm.astro';
+export { default as BodyXs } from './BodyXs.astro';
+export { default as Code } from './Code.astro';
+
+export type {
+  TypographyVariant,
+  TypographyColor,
+  TypographyWeight,
+  TypographyHTMLTag,
+  TypographyBaseProps,
+} from './types';
diff --git a/src/components/primitives/Typography/types.ts b/src/components/primitives/Typography/types.ts
new file mode 100644
index 0000000000..cfc2a91eed
--- /dev/null
+++ b/src/components/primitives/Typography/types.ts
@@ -0,0 +1,61 @@
+/**
+ * Typography Component Types
+ */
+
+export type TypographyVariant =
+  | 'h1'
+  | 'h2'
+  | 'h3'
+  | 'h4'
+  | 'h5'
+  | 'body-lg'
+  | 'body'
+  | 'body-md'
+  | 'body-sm'
+  | 'body-xs'
+  | 'code';
+
+export type TypographyColor =
+  | 'primary'
+  | 'secondary'
+  | 'tertiary'
+  | 'inverse'
+  | 'inactive'
+  | 'error'
+  | 'success'
+  | 'warning';
+
+export type TypographyWeight = 'light' | 'normal' | 'medium' | 'semibold' | 'bold';
+
+export type TypographyHTMLTag =
+  | 'h1'
+  | 'h2'
+  | 'h3'
+  | 'h4'
+  | 'h5'
+  | 'h6'
+  | 'p'
+  | 'span'
+  | 'small'
+  | 'label'
+  | 'code'
+  | 'pre';
+
+export interface TypographyBaseProps {
+  /** HTML element to render */
+  as?: TypographyHTMLTag;
+  /** Typography style variant */
+  variant?: TypographyVariant;
+  /** Text color */
+  color?: TypographyColor;
+  /** Font weight override */
+  weight?: TypographyWeight;
+  /** Center text alignment */
+  center?: boolean;
+  /** Left text alignment */
+  left?: boolean;
+  /** Right text alignment */
+  right?: boolean;
+  /** Enable vertical margin (default: true) */
+  vMargin?: boolean;
+}
diff --git a/src/components/primitives/index.ts b/src/components/primitives/index.ts
new file mode 100644
index 0000000000..ab8b85e025
--- /dev/null
+++ b/src/components/primitives/index.ts
@@ -0,0 +1,29 @@
+/**
+ * Reexport all primitives Components
+ */
+
+// Typography
+export { Typography, H1, H2, H3, H4, H5, Body, BodySm, BodyMd, BodyXs, Code } from './Typography';
+
+// Layout
+export { Container } from './Container';
+export { Grid, Col, Flex, FlexItem } from './Grid';
+
+// Button
+export { Button } from './Button';
+
+// Select
+export { Select } from './Select';
+export type { SelectOption, SelectSize, SelectVariant } from './Select';
+
+// Card
+export { Card } from './Card';
+
+// Avatar
+export { Avatar } from './Avatar';
+
+// Tag
+export { Tag } from './Tag';
+
+// Tabs — imported directly where needed to avoid CSS leaking via barrel export
+export type { TabItem } from './Tabs';
diff --git a/src/config/announcement.json b/src/config/announcement.json
new file mode 100644
index 0000000000..24ad8c85c5
--- /dev/null
+++ b/src/config/announcement.json
@@ -0,0 +1,8 @@
+{
+  "title": "",
+  "description": "",
+  "link": "",
+  "variant": "info",
+  "startDate": "",
+  "endDate": ""
+}
diff --git a/src/config/menu/api.ts b/src/config/menu/api.ts
new file mode 100644
index 0000000000..1afb9a6652
--- /dev/null
+++ b/src/config/menu/api.ts
@@ -0,0 +1,443 @@
+import type { Menu } from '../types';
+
+export const apiMenu: Menu = {
+  sections: [
+    //API root
+    {
+      items: [
+        {
+          href: '/api',
+          label: 'menu.main.api',
+          ariaLabel: 'menu.aria.api',
+        },
+      ],
+    },
+    //express()
+    {
+      title: 'menu.sections.express',
+      omitFrom: ['3x'],
+      items: [
+        {
+          href: '/api/express/',
+          label: 'menu.sections.express',
+          ariaLabel: 'menu.aria.api',
+        },
+        {
+          label: 'menu.items.methods',
+          ariaLabel: 'menu.aria.api',
+          submenu: {
+            items: [
+              { href: '/api/express#expressjsonoptions', label: 'express.json()' },
+              { href: '/api/express#expressrawoptions', label: 'express.raw()' },
+              { href: '/api/express#expressrouteroptions', label: 'express.Router()' },
+              { href: '/api/express#expressstaticroot-options', label: 'express.static()' },
+              { href: '/api/express#expresstextoptions', label: 'express.text()' },
+              { href: '/api/express#expressurlencodedoptions', label: 'express.urlencoded()' },
+            ],
+          },
+        },
+      ],
+    },
+    //application
+    {
+      title: 'menu.sections.application',
+      items: [
+        {
+          href: `/api/application`,
+          label: 'menu.sections.application',
+          ariaLabel: 'menu.aria.application',
+        },
+        {
+          label: 'menu.items.properties',
+          ariaLabel: 'menu.aria.application',
+          submenu: {
+            items: [
+              { href: `/api/application#applocals`, label: 'app.locals' },
+              {
+                href: '/api/application#appmountpath',
+                label: 'app.mountpath',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/application#approuter',
+                label: 'app.router',
+                omitFrom: ['3x', '4x'],
+              },
+              {
+                href: '/api/application#approutes',
+                label: 'app.routes',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/application#settings',
+                label: 'app.settings',
+                omitFrom: ['4x', '5x'],
+              },
+            ],
+          },
+        },
+        {
+          label: 'menu.items.events',
+          ariaLabel: 'menu.aria.application',
+          omitFrom: ['3x'],
+          submenu: {
+            items: [
+              {
+                href: `/api/application#apponmount-callbackparent`,
+                label: "app.on('mount')",
+              },
+            ],
+          },
+        },
+        {
+          label: 'menu.items.methods',
+          ariaLabel: 'menu.aria.application',
+          submenu: {
+            items: [
+              { href: `/api/application#appallpath-callback--callback-`, label: 'app.all()' },
+              {
+                href: '/api/application#appconfigureenv-callback',
+                label: 'app.configure()',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: `/api/application#appdeletepath-callback--callback-`,
+                label: 'app.delete()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/application#appdisablename', label: 'app.disable()' },
+              { href: '/api/application#appdisabledname', label: 'app.disabled()' },
+              { href: '/api/application#appenablename', label: 'app.enable()' },
+              { href: '/api/application#appenabledname', label: 'app.enabled()' },
+              { href: '/api/application#appengineext-callback', label: 'app.engine()' },
+              { href: '/api/application#appgetname', label: 'app.get(name)' },
+              {
+                href: '/api/application#appgetpath-callback--callback-',
+                label: 'app.get(path)',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/application#applistenport-host-backlog-callback',
+                label: 'app.listen()',
+              },
+              {
+                href: '/api/application#appmethodpath-callback--callback-',
+                label: 'app.METHOD()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/application#appparamname-callback', label: 'app.param()' },
+              {
+                href: '/api/application#apppath',
+                label: 'app.path()',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/application#apppostpath-callback--callback-',
+                label: 'app.post()',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/application#appputpath-callback--callback-',
+                label: 'app.put()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/application#apprenderview-locals-callback', label: 'app.render()' },
+              {
+                href: '/api/application#approutepath',
+                label: 'app.route()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/application#appsetname-value', label: 'app.set()' },
+              { href: '/api/application#appusepath-callback--callback', label: 'app.use()' },
+              {
+                href: '/api/application#appverbpath-callback-callback',
+                label: 'app.VERB()',
+                omitFrom: ['4x', '5x'],
+              },
+            ],
+          },
+        },
+      ],
+    },
+    //middleware
+    {
+      title: 'menu.sections.middleware',
+      omitFrom: ['4x', '5x'],
+      items: [
+        {
+          href: '/api/middleware/',
+          label: 'menu.sections.middleware',
+          ariaLabel: 'menu.aria.middleware',
+        },
+        {
+          label: 'menu.items.types',
+          ariaLabel: 'menu.aria.middleware',
+          submenu: {
+            items: [
+              { href: '/api/middleware#basicauth', label: 'basicAuth()' },
+              { href: '/api/middleware#bodyparser', label: 'bodyParser()' },
+              { href: '/api/middleware#compress', label: 'compress()' },
+              { href: '/api/middleware#cookieparser', label: 'cookieParser()' },
+              { href: '/api/middleware#cookiesession', label: 'cookieSession()' },
+              { href: '/api/middleware#csrf', label: 'csrf()' },
+              { href: '/api/middleware#directory', label: 'directory()' },
+            ],
+          },
+        },
+      ],
+    },
+    //request
+    {
+      title: 'menu.sections.request',
+      items: [
+        {
+          href: `/api/request`,
+          label: 'menu.sections.request',
+          ariaLabel: 'menu.aria.request',
+        },
+        {
+          label: 'menu.items.properties',
+          ariaLabel: 'menu.aria.request',
+          submenu: {
+            items: [
+              {
+                href: '/api/request#reqaccepted',
+                label: 'req.accepted',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/request#reqacceptedcharsets',
+                label: 'req.acceptedCharsets',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/request#reqacceptedlanguages',
+                label: 'req.acceptedLanguages',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/request#reqapp',
+                label: 'req.app',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/request#reqbaseurl',
+                label: 'req.baseUrl',
+                omitFrom: ['3x'],
+              },
+              { href: `/api/request#reqbody`, label: 'req.body' },
+              { href: `/api/request#reqcookies`, label: 'req.cookies' },
+              {
+                href: '/api/request#reqfiles',
+                label: 'req.files',
+                omitFrom: ['4x', '5x'],
+              },
+              { href: '/api/request#reqfresh', label: 'req.fresh' },
+              {
+                href: '/api/request#reqhost',
+                label: 'req.host',
+                omitFrom: ['4x'],
+              },
+              {
+                href: '/api/request#reqhostname',
+                label: 'req.hostname',
+                omitFrom: ['3x'],
+              },
+              { href: `/api/request#reqip`, label: 'req.ip' },
+              { href: '/api/request#reqips', label: 'req.ips' },
+              { href: `/api/request#reqmethod`, label: 'req.method', omitFrom: ['3x'] },
+              { href: '/api/request#reqoriginalurl', label: 'req.originalUrl' },
+              { href: '/api/request#reqparams', label: 'req.params' },
+              { href: '/api/request#reqpath', label: 'req.path' },
+              { href: '/api/request#reqprotocol', label: 'req.protocol' },
+              { href: `/api/request#reqquery`, label: 'req.query' },
+              { href: '/api/request#reqres', label: 'req.res' },
+              { href: '/api/request#reqroute', label: 'req.route' },
+              { href: '/api/request#reqsecure', label: 'req.secure' },
+              { href: '/api/request#reqsignedcookies', label: 'req.signedCookies' },
+              { href: '/api/request#reqstale', label: 'req.stale' },
+              { href: '/api/request#reqsubdomains', label: 'req.subdomains' },
+              { href: '/api/request#reqxhr', label: 'req.xhr' },
+            ],
+          },
+        },
+        {
+          label: 'menu.items.methods',
+          ariaLabel: 'menu.aria.request',
+          submenu: {
+            items: [
+              { href: `/api/request#reqacceptstypes`, label: 'req.accepts()' },
+              {
+                href: '/api/request#reqacceptscharsetcharset',
+                label: 'req.acceptsCharset()',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/request#reqacceptscharsetscharset--',
+                label: 'req.acceptsCharsets()',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/request#reqacceptsencodingsencoding--',
+                label: 'req.acceptsEncodings()',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/request#reqacceptslanguagelang',
+                label: 'req.acceptsLanguage()',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/request#reqacceptslanguageslang-',
+                label: 'req.acceptsLanguages()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/request#reqgetfield', label: 'req.get()', omitFrom: ['3x'] },
+              {
+                href: '/api/request#reqheaderfield',
+                label: 'req.header()',
+                omitFrom: ['4x', '5x'],
+              },
+              { href: '/api/request#reqistype', label: 'req.is()' },
+              {
+                href: '/api/request#reqparamname',
+                label: 'req.param()',
+                omitFrom: ['5x'],
+              },
+              {
+                href: '/api/request#reqrangesize-options',
+                label: 'req.range()',
+                omitFrom: ['3x'],
+              },
+            ],
+          },
+        },
+      ],
+    },
+    //response
+    {
+      title: 'menu.sections.response',
+      items: [
+        {
+          href: `/api/response`,
+          label: 'menu.sections.response',
+          ariaLabel: 'menu.aria.response',
+        },
+        {
+          label: 'menu.items.properties',
+          ariaLabel: 'menu.aria.response',
+          submenu: {
+            items: [
+              {
+                href: '/api/response#resapp',
+                label: 'res.app',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/response#rescharset',
+                label: 'res.charset',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/response#resheaderssent',
+                label: 'res.headersSent',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/response#reslocals', label: 'res.locals' },
+              { href: '/api/response#resreq', label: 'res.req' },
+            ],
+          },
+        },
+        {
+          label: 'menu.items.methods',
+          ariaLabel: 'menu.aria.response',
+          submenu: {
+            items: [
+              {
+                href: '/api/response#resappendfield--value',
+                label: 'res.append()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/response#resattachmentfilename', label: 'res.attachment()' },
+              { href: '/api/response#resclearcookiename--options', label: 'res.clearCookie()' },
+              { href: '/api/response#rescookiename-value--options', label: 'res.cookie()' },
+              {
+                href: '/api/response#resdownloadpath--filename--options--fn',
+                label: 'res.download()',
+              },
+              {
+                href: '/api/response#resenddata-encoding-callback',
+                label: 'res.end()',
+                omitFrom: ['3x'],
+              },
+              { href: `/api/response#resformatobject`, label: 'res.format()' },
+              { href: '/api/response#resgetfield', label: 'res.get()' },
+              { href: `/api/response#resjsonbody`, label: 'res.json()' },
+              { href: '/api/response#resjsonpbody', label: 'res.jsonp()' },
+              { href: '/api/response#reslinkslinks', label: 'res.links()' },
+              { href: '/api/response#reslocationpath', label: 'res.location()' },
+              { href: '/api/response#resredirectstatus-path', label: 'res.redirect()' },
+              { href: `/api/response#resrenderview--locals--callback`, label: 'res.render()' },
+              { href: `/api/response#ressendbody`, label: 'res.send()' },
+              {
+                href: '/api/response#ressendfilepath-options-fn',
+                label: 'res.sendfile()',
+                omitFrom: ['4x', '5x'],
+              },
+              {
+                href: '/api/response#ressendfilepath--options--fn',
+                label: 'res.sendFile()',
+                omitFrom: ['3x'],
+              },
+              {
+                href: '/api/response#ressendstatusstatuscode',
+                label: 'res.sendStatus()',
+                omitFrom: ['3x'],
+              },
+              { href: '/api/response#ressetfield--value', label: 'res.set()' },
+              { href: `/api/response#resstatuscode`, label: 'res.status()' },
+              { href: '/api/response#restypetype', label: 'res.type()' },
+              {
+                href: '/api/response#resvaryfield',
+                label: 'res.vary()',
+                omitFrom: ['3x'],
+              },
+            ],
+          },
+        },
+      ],
+    },
+    //router
+    {
+      title: 'menu.sections.router',
+      omitFrom: ['3x'],
+      items: [
+        {
+          href: `/api/router`,
+          label: 'menu.sections.router',
+          ariaLabel: 'menu.aria.router',
+        },
+        {
+          label: 'menu.items.methods',
+          ariaLabel: 'menu.aria.router',
+          submenu: {
+            items: [
+              { href: `/api/router#routeroptions`, label: 'Router()' },
+              { href: `/api/router#routerallpath-callback--callback`, label: 'router.all()' },
+              {
+                href: `/api/router#routermethodpath-callback--callback`,
+                label: 'router.METHOD()',
+              },
+              { href: '/api/router#routerparamname-callback', label: 'router.param()' },
+              { href: '/api/router#routerroutepath', label: 'router.route()' },
+              {
+                href: `/api/router#routerusepath-function--function`,
+                label: 'router.use()',
+              },
+            ],
+          },
+        },
+      ],
+    },
+  ],
+};
diff --git a/src/config/menu/docs.ts b/src/config/menu/docs.ts
new file mode 100644
index 0000000000..19f58a3fb6
--- /dev/null
+++ b/src/config/menu/docs.ts
@@ -0,0 +1,148 @@
+import type { Menu } from '../types';
+
+export const docsMenu: Menu = {
+  sections: [
+    {
+      title: 'menu.sections.gettingStarted',
+      items: [
+        {
+          href: `/starter/installing`,
+          label: 'menu.items.installing',
+          ariaLabel: 'menu.aria.installing',
+        },
+        {
+          href: `/starter/hello-world`,
+          label: 'menu.items.helloWorld',
+          ariaLabel: 'menu.aria.helloWorld',
+        },
+        {
+          href: `/starter/generator`,
+          label: 'menu.items.expressGenerator',
+          ariaLabel: 'menu.aria.expressGenerator',
+        },
+        {
+          href: `/starter/basic-routing`,
+          label: 'menu.items.basicRouting',
+          ariaLabel: 'menu.aria.basicRouting',
+        },
+        {
+          href: `/starter/static-files`,
+          label: 'menu.items.staticFiles',
+          ariaLabel: 'menu.aria.staticFiles',
+        },
+        {
+          href: `/starter/examples`,
+          label: 'menu.items.examples',
+          ariaLabel: 'menu.aria.examples',
+        },
+        {
+          href: `/starter/faq`,
+          label: 'menu.items.faq',
+          ariaLabel: 'menu.aria.faq',
+        },
+      ],
+    },
+    {
+      title: 'menu.sections.guide',
+      items: [
+        {
+          href: `/guide/routing`,
+          label: 'menu.items.routing',
+          ariaLabel: 'menu.aria.routing',
+        },
+        {
+          href: `/guide/writing-middleware`,
+          label: 'menu.items.writingMiddleware',
+          ariaLabel: 'menu.aria.writingMiddleware',
+        },
+        {
+          href: `/guide/using-middleware`,
+          label: 'menu.items.usingMiddleware',
+          ariaLabel: 'menu.aria.usingMiddleware',
+        },
+        {
+          href: `/guide/using-template-engines`,
+          label: 'menu.items.usingTemplateEngines',
+          ariaLabel: 'menu.aria.usingTemplateEngines',
+        },
+        {
+          href: `/guide/error-handling`,
+          label: 'menu.items.errorHandling',
+          ariaLabel: 'menu.aria.errorHandling',
+        },
+        {
+          href: `/guide/debugging`,
+          label: 'menu.items.debugging',
+          ariaLabel: 'menu.aria.debugging',
+        },
+        {
+          href: `/guide/behind-proxies`,
+          label: 'menu.items.behindProxies',
+          ariaLabel: 'menu.aria.behindProxies',
+        },
+        {
+          href: `/guide/database-integration`,
+          label: 'menu.items.databaseIntegration',
+          ariaLabel: 'menu.aria.databaseIntegration',
+          global: true,
+        },
+        {
+          href: `/guide/overriding-express-api`,
+          label: 'menu.items.overridingExpressApi',
+          ariaLabel: 'menu.aria.overridingExpressApi',
+        },
+      ],
+    },
+    {
+      title: 'menu.sections.migration',
+      items: [
+        {
+          href: `/guide/migrating-4`,
+          label: 'menu.items.migratingTo4',
+          ariaLabel: 'menu.aria.migratingTo4',
+          global: true,
+        },
+        {
+          href: `/guide/migrating-5`,
+          label: 'menu.items.migratingTo5',
+          ariaLabel: 'menu.aria.migratingTo5',
+          global: true,
+        },
+      ],
+    },
+    {
+      title: 'menu.sections.advanced',
+      items: [
+        {
+          href: `/advanced/developing-template-engines`,
+          label: 'menu.items.buildingTemplateEngines',
+          ariaLabel: 'menu.aria.buildingTemplateEngines',
+        },
+        {
+          href: `/advanced/best-practice-performance`,
+          label: 'menu.items.bestPracticePerformance',
+          ariaLabel: 'menu.aria.bestPracticePerformance',
+          global: true,
+        },
+        {
+          href: `/advanced/best-practice-security`,
+          label: 'menu.items.bestPracticeSecurity',
+          ariaLabel: 'menu.aria.bestPracticeSecurity',
+          global: true,
+        },
+        {
+          href: `/advanced/healthcheck-graceful-shutdown`,
+          label: 'menu.items.healthcheckGracefulShutdown',
+          ariaLabel: 'menu.aria.healthcheckGracefulShutdown',
+          global: true,
+        },
+        {
+          href: `/advanced/security-updates`,
+          label: 'menu.items.securityUpdates',
+          ariaLabel: 'menu.aria.securityUpdates',
+          global: true,
+        },
+      ],
+    },
+  ],
+};
diff --git a/src/config/menu/main.ts b/src/config/menu/main.ts
new file mode 100644
index 0000000000..c8d2582bb9
--- /dev/null
+++ b/src/config/menu/main.ts
@@ -0,0 +1,52 @@
+import { docsMenu } from './docs';
+import { apiMenu } from './api';
+import type { Menu } from '../types';
+import { resourcesMenu } from './resources';
+
+export const mainMenu: Menu = {
+  sections: [
+    {
+      items: [
+        {
+          label: 'menu.main.docs',
+          ariaLabel: 'menu.aria.docs',
+          icon: 'document-bullet-list-multiple-20-regular',
+          submenu: {
+            versioned: ['5x', '4x'],
+            sections: docsMenu.sections,
+          },
+        },
+        {
+          label: 'menu.main.api',
+          ariaLabel: 'menu.aria.api',
+          icon: 'code-20-regular',
+          submenu: {
+            versioned: ['5x', '4x', '3x'],
+            sections: apiMenu.sections,
+          },
+        },
+        {
+          label: 'menu.main.resources',
+          ariaLabel: 'menu.aria.resources',
+          icon: 'folder-20-regular',
+          submenu: {
+            basePath: '/resources',
+            items: resourcesMenu.items,
+          },
+        },
+        {
+          href: `/blog`,
+          label: 'menu.main.blog',
+          icon: 'news-20-regular',
+          ariaLabel: 'menu.aria.blog',
+        },
+        {
+          href: `/support`,
+          label: 'menu.main.support',
+          icon: 'info-20-regular',
+          ariaLabel: 'menu.aria.support',
+        },
+      ],
+    },
+  ],
+};
diff --git a/src/config/menu/middleware.ts b/src/config/menu/middleware.ts
new file mode 100644
index 0000000000..709cb61d78
--- /dev/null
+++ b/src/config/menu/middleware.ts
@@ -0,0 +1,92 @@
+import type { Menu } from '../types';
+
+export const middlewareMenu: Menu = {
+  items: [
+    {
+      href: `/`,
+      label: 'menu.items.overview',
+      ariaLabel: 'menu.aria.middleware',
+    },
+    // these are NOT translation keys keep raw
+    {
+      href: `/body-parser`,
+      label: 'body-parser',
+      ariaLabel: 'body-parser middleware',
+    },
+    {
+      href: `/compression`,
+      label: 'compression',
+      ariaLabel: 'compression middleware',
+    },
+    {
+      href: `/cookie-parser`,
+      label: 'cookie-parser',
+      ariaLabel: 'cookie-parser middleware',
+    },
+    {
+      href: `/cookie-session`,
+      label: 'cookie-session',
+      ariaLabel: 'cookie-session middleware',
+    },
+    {
+      href: `/cors`,
+      label: 'cors',
+      ariaLabel: 'cors middleware',
+    },
+    {
+      href: `/errorhandler`,
+      label: 'errorhandler',
+      ariaLabel: 'errorhandler middleware',
+    },
+    {
+      href: `/method-override`,
+      label: 'method-override',
+      ariaLabel: 'method-override middleware',
+    },
+    {
+      href: `/morgan`,
+      label: 'morgan',
+      ariaLabel: 'morgan middleware',
+    },
+    {
+      href: `/multer`,
+      label: 'multer',
+      ariaLabel: 'multer middleware',
+    },
+    {
+      href: `/response-time`,
+      label: 'response-time',
+      ariaLabel: 'response-time middleware',
+    },
+    {
+      href: `/serve-favicon`,
+      label: 'serve-favicon',
+      ariaLabel: 'serve-favicon middleware',
+    },
+    {
+      href: `/serve-index`,
+      label: 'serve-index',
+      ariaLabel: 'serve-index middleware',
+    },
+    {
+      href: `/serve-static`,
+      label: 'serve-static',
+      ariaLabel: 'serve-static middleware',
+    },
+    {
+      href: `/session`,
+      label: 'session',
+      ariaLabel: 'session middleware',
+    },
+    {
+      href: `/timeout`,
+      label: 'timeout',
+      ariaLabel: 'timeout middleware',
+    },
+    {
+      href: `/vhost`,
+      label: 'vhost',
+      ariaLabel: 'vhost middleware',
+    },
+  ],
+};
diff --git a/src/config/menu/resources.ts b/src/config/menu/resources.ts
new file mode 100644
index 0000000000..581f318873
--- /dev/null
+++ b/src/config/menu/resources.ts
@@ -0,0 +1,46 @@
+import type { Menu } from '../types';
+import { middlewareMenu } from './middleware';
+
+export const resourcesMenu: Menu = {
+  basePath: '/resources',
+  items: [
+    {
+      href: `/`,
+      label: 'menu.items.overview',
+      ariaLabel: 'menu.items.overview',
+    },
+    {
+      href: `/community`,
+      label: 'menu.items.community',
+      ariaLabel: 'menu.aria.community',
+    },
+    {
+      href: `/glossary`,
+      label: 'menu.items.glossary',
+      ariaLabel: 'menu.aria.glossary',
+    },
+    {
+      href: `/contributing`,
+      label: 'menu.items.contributing',
+      ariaLabel: 'menu.aria.contributing',
+    },
+    {
+      href: `/utils`,
+      label: 'menu.items.utils',
+      ariaLabel: 'menu.aria.utils',
+    },
+    {
+      href: `https://github.com/expressjs/express/releases`,
+      label: 'menu.items.changelog',
+      ariaLabel: 'menu.aria.changelog',
+    },
+    {
+      label: 'menu.sections.middleware',
+      ariaLabel: 'menu.aria.middleware',
+      submenu: {
+        basePath: '/resources/middleware',
+        items: middlewareMenu.items,
+      },
+    },
+  ],
+};
diff --git a/src/config/redirect.js b/src/config/redirect.js
new file mode 100644
index 0000000000..c6a4bae5d9
--- /dev/null
+++ b/src/config/redirect.js
@@ -0,0 +1,69 @@
+// Redirect .html and non-.html blog post URLs to the new format. This will ensure that any existing links to blog posts will continue to work and redirect users to the correct location on the new site.
+const blog = {
+  '/2024/07/16/welcome-post.html': '/en/blog/2024-07-16-welcome-post',
+  '/2024/07/16/welcome-post': '/en/blog/2024-07-16-welcome-post',
+  '/2024/09/29/security-releases.html': '/en/blog/2024-09-29-security-releases',
+  '/2024/09/29/security-releases': '/en/blog/2024-09-29-security-releases',
+  '/2024/10/01/HeroDevs-partnership-announcement.html':
+    '/en/blog/2024-10-01-herodevs-partnership-announcement',
+  '/2024/10/01/HeroDevs-partnership-announcement':
+    '/en/blog/2024-10-01-herodevs-partnership-announcement',
+  '/2024/10/15/v5-release': '/en/blog/2024-10-15-v5-release',
+  '/2024/10/15/v5-release.html': '/en/blog/2024-10-15-v5-release',
+  '/2024/10/22/security-audit-milestone-achievement.html':
+    '/en/blog/2024-10-22-security-audit-milestone-achievement',
+  '/2024/10/22/security-audit-milestone-achievement':
+    '/en/blog/2024-10-22-security-audit-milestone-achievement',
+  '/2025/01/09/rewind-2024-triumphs-and-2025-vision.html':
+    '/en/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision',
+  '/2025/01/09/rewind-2024-triumphs-and-2025-vision':
+    '/en/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision',
+  '/2025/03/31/v5-1-latest-release.html': '/en/blog/2025-03-31-v5-1-latest-release',
+  '/2025/03/31/v5-1-latest-release': '/en/blog/2025-03-31-v5-1-latest-release',
+  '/2025/05/16/express-cleanup-legacy-packages.html':
+    '/en/blog/2025-05-16-express-cleanup-legacy-packages',
+  '/2025/05/16/express-cleanup-legacy-packages':
+    '/en/blog/2025-05-16-express-cleanup-legacy-packages',
+  '/2025/05/19/security-releases.html': '/en/blog/2025-05-19-security-releases',
+  '/2025/05/19/security-releases': '/en/blog/2025-05-19-security-releases',
+  '/2025/06/05/vulnerability-reporting-process-overhaul.html':
+    '/en/blog/2025-06-05-vulnerability-reporting-process-overhaul',
+  '/2025/06/05/vulnerability-reporting-process-overhaul':
+    '/en/blog/2025-06-05-vulnerability-reporting-process-overhaul',
+  '/2025/07/18/security-releases.html': '/en/blog/2025-07-18-security-releases',
+  '/2025/07/18/security-releases': '/en/blog/2025-07-18-security-releases',
+  '/2025/07/31/security-releases.html': '/en/blog/2025-07-31-security-releases',
+  '/2025/07/31/security-releases': '/en/blog/2025-07-31-security-releases',
+  '/2025/12/01/security-releases.html': '/en/blog/2025-12-01-security-releases',
+  '/2025/12/01/security-releases': '/en/blog/2025-12-01-security-releases',
+  '/2026/02/27/security-releases.html': '/en/blog/2026-02-27-security-releases',
+  '/2026/02/27/security-releases': '/en/blog/2026-02-27-security-releases',
+  '/2026/03/30/security-releases.html': '/en/blog/2026-03-30-security-releases',
+  '/2026/03/30/security-releases': '/en/blog/2026-03-30-security-releases',
+};
+
+const api_v2 = {
+  '/2x/': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/guide.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/migrate.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/screencasts.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/executables.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/contrib.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/applications.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/guide.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/migrate.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/screencasts.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/executables.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/contrib.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+  '/2x/docs/applications.html': 'https://github.com/expressjs/expressjs.com/tree/2x',
+};
+
+const pages = {
+  '/en/changelog/4x.html': 'https://github.com/expressjs/express/releases',
+  '/en/changelog/4x': 'https://github.com/expressjs/express/releases',
+};
+
+const redirects = { ...blog, ...api_v2, ...pages };
+
+export default redirects;
diff --git a/src/config/types.ts b/src/config/types.ts
new file mode 100644
index 0000000000..0cfa64de5e
--- /dev/null
+++ b/src/config/types.ts
@@ -0,0 +1,35 @@
+/** Valid version prefixes for versioned content */
+export type VersionPrefix = '5x' | '4x' | '3x';
+
+export type MenuItemBaseProps = {
+  label: string;
+  ariaLabel?: string;
+  icon?: string;
+  omitFrom?: VersionPrefix[];
+};
+
+export type MenuItem =
+  | (MenuItemBaseProps & {
+      href: string;
+      submenu?: never;
+      global?: boolean;
+    })
+  | (MenuItemBaseProps & {
+      submenu: Menu;
+      href?: never;
+      global?: never;
+    });
+
+export type MenuSection = {
+  title?: string;
+  basePath?: string;
+  items: MenuItem[];
+  omitFrom?: VersionPrefix[];
+};
+
+export type Menu = {
+  sections?: MenuSection[];
+  items?: MenuItem[];
+  basePath?: string;
+  versioned?: VersionPrefix[];
+};
diff --git a/src/content.config.ts b/src/content.config.ts
new file mode 100644
index 0000000000..9449b30173
--- /dev/null
+++ b/src/content.config.ts
@@ -0,0 +1,62 @@
+import { defineCollection } from 'astro:content';
+import { z } from 'astro/zod';
+import { glob } from 'astro/loaders';
+
+const docsCollection = defineCollection({
+  loader: glob({ pattern: '**/[^_]*.{md,mdx}', base: './src/content/docs' }),
+  schema: z.object({
+    title: z.string(),
+    description: z.string().optional(),
+  }),
+});
+
+const apiCollection = defineCollection({
+  loader: glob({ pattern: '**/[^_]*.{md,mdx}', base: './src/content/api' }),
+  schema: z.object({
+    title: z.string(),
+    description: z.string().optional(),
+  }),
+});
+
+const pagesCollection = defineCollection({
+  loader: glob({ pattern: '**/[^_]*.{md,mdx}', base: './src/content/pages' }),
+  schema: z.object({
+    title: z.string(),
+    description: z.string().optional(),
+  }),
+});
+
+const blogCollection = defineCollection({
+  loader: glob({ pattern: '**/[^_]*.{md,mdx}', base: './src/content/blog' }),
+  schema: z.object({
+    title: z.string(),
+    description: z.string().optional(),
+    tags: z.array(z.string()).optional(),
+    cover: z.string().optional(),
+    authors: z
+      .array(
+        z.object({
+          name: z.string(),
+          github: z.string().optional(),
+        })
+      )
+      .optional(),
+  }),
+});
+
+const npmCollection = defineCollection({
+  loader: async () => {
+    const res = await fetch('https://registry.npmjs.org/express/latest');
+    const { version } = await res.json();
+    return [{ id: 'express', version }];
+  },
+  schema: z.object({ version: z.string() }),
+});
+
+export const collections = {
+  docs: docsCollection,
+  api: apiCollection,
+  pages: pagesCollection,
+  blog: blogCollection,
+  npm: npmCollection,
+};
diff --git a/src/content/api/3x/api.mdx b/src/content/api/3x/api.mdx
new file mode 100644
index 0000000000..71a52c55b0
--- /dev/null
+++ b/src/content/api/3x/api.mdx
@@ -0,0 +1,70 @@
+---
+title: Express 3.x - Referencia de API
+description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+import Card from '@components/primitives/Card/Card.astro';
+import { CardList } from '@components/patterns';
+
+<Alert type="warning" title="Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED">
+
+Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/en/support#commercial-support-options).
+
+</Alert>
+
+<Alert type="info">
+
+Express 3.x requires **Node.js 0.8.0 or higher**.
+
+</Alert>
+
+# 3.x API
+
+This section provides an overview of the modules and APIs available in Express 3.x for building web applications and HTTP services.
+
+## `express()`
+
+The `express()` function, exported by the `express` module, creates and returns a new application instance that serves as the foundation for defining routes, configuring middleware, and handling HTTP requests.
+
+```js title="index.js"
+var express = require('express');
+var app = express();
+
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+After creating an application instance, you can define routes, configure middleware, and start handling HTTP requests
+
+<CardList gap="6">
+  <a href="/en/3x/api/application">
+    <Card
+      title="Application Object"
+      body="Learn about the properties and methods of the Express 3.x application object."
+    />
+  </a>
+  <a href="/en/3x/api/request">
+    <Card
+      title="Request Object"
+      body="Learn about the properties and methods of the Express 3.x request object."
+    />
+  </a>
+  <a href="/en/3x/api/response">
+    <Card
+      title="Response Object"
+      body="Learn about the properties and methods of the Express 3.x response object."
+    />
+  </a>
+  <a href="/en/3x/api/middleware">
+    <Card
+      title="Middleware"
+      body="Learn about middleware in Express 3.x, including built-in and third-party options."
+    />
+  </a>
+</CardList>
diff --git a/src/content/api/3x/api/application/index.mdx b/src/content/api/3x/api/application/index.mdx
new file mode 100644
index 0000000000..0f7e469613
--- /dev/null
+++ b/src/content/api/3x/api/application/index.mdx
@@ -0,0 +1,575 @@
+---
+title: Application Object
+description: Learn about the properties and methods of the Express 3.x application object.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `app` object conventionally denotes the Express application.
+Create it by calling the top-level `express()` function exported by the Express module:
+
+```js
+var express = require('express');
+var app = express();
+
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+## Properties
+
+### app.locals
+
+Application local variables are provided to all templates
+rendered within the application. This is useful for providing
+helper functions to templates, as well as app-level data.
+
+```js
+app.locals.title = 'My App';
+app.locals.strftime = require('strftime');
+```
+
+The `app.locals` object is a JavaScript `Function`,
+which when invoked with an object will merge properties into itself, providing
+a simple way to expose existing objects as local variables.
+
+```js
+app.locals({
+  title: 'My App',
+  phone: '1-250-858-9990',
+  email: 'me@myapp.com',
+});
+
+console.log(app.locals.title);
+// => 'My App'
+
+console.log(app.locals.email);
+// => 'me@myapp.com'
+```
+
+A consequence of the `app.locals` Object being ultimately a Javascript Function Object is that you must not reuse existing (native) named properties for your own variable names, such as `name, apply, bind, call, arguments, length, constructor`.
+
+```js
+app.locals({ name: 'My App' });
+
+console.log(app.locals.name);
+// => return 'app.locals' in place of 'My App' (app.locals is a Function !)
+// => if name's variable is used in a template, a ReferenceError will be returned.
+```
+
+The full list of native named properties can be found in many specifications. The <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference">JavaScript specification</a> introduced original properties, some of which still recognized by modern engines, and the <a href="http://www.ecma-international.org/ecma-262/5.1/">EcmaScript specification</a> then built on it and normalized the set of properties, adding new ones and removing deprecated ones. Check out properties for Functions and Objects if interested.
+
+By default Express exposes only a single app-level local variable, `settings`.
+
+```js
+app.set('title', 'My App');
+// use settings.title in a view
+```
+
+### app.routes
+
+The `app.routes` object houses all of the routes defined mapped
+by the associated HTTP verb. This object may be used for introspection capabilities,
+for example Express uses this internally not only for routing but to provide default
+
+<string>OPTIONS</string> behaviour unless `app.options()` is used. Your application or framework may
+also remove routes by simply by removing them from this object.
+
+The output of `console.log(app.routes)`:
+
+```
+{ get:
+   [ { path: '/',
+       method: 'get',
+       callbacks: [Object],
+       keys: [],
+       regexp: /^\/\/?$/i },
+     { path: '/user/:id',
+       method: 'get',
+       callbacks: [Object],
+       keys: [{ name: 'id', optional: false }],
+       regexp: /^\/user\/(?:([^\/]+?))\/?$/i } ],
+  delete:
+   [ { path: '/user/:id',
+       method: 'delete',
+       callbacks: [Object],
+       keys: [Object],
+       regexp: /^\/user\/(?:([^\/]+?))\/?$/i } ] }
+```
+
+### settings
+
+The following settings are provided to alter how Express will behave:
+
+- `env` Environment mode, defaults to process.env.NODE_ENV or "development"
+- `trust proxy` Enables reverse proxy support, disabled by default
+- `jsonp callback name` Changes the default callback name of ?callback=
+- `json replacer` JSON replacer callback, null by default
+- `json spaces` JSON response spaces for formatting, defaults to 2 in development, 0 in production
+- `case sensitive routing` Enable case sensitivity, disabled by default, treating "/Foo" and "/foo" as the same
+- `strict routing` Enable strict routing, by default "/foo" and "/foo/" are treated the same by the router
+- `view cache` Enables view template compilation caching, enabled in production by default
+- `view engine` The default engine extension to use when omitted
+- `views` The view directory path, defaulting to "process.cwd() + '/views'"
+
+## Methods
+
+### app.set(name, value)
+
+Assigns setting `name` to `value`.
+
+```js
+app.set('title', 'My Site');
+app.get('title');
+// => "My Site"
+```
+
+### app.get(name)
+
+Get setting `name` value.
+
+```js
+app.get('title');
+// => undefined
+
+app.set('title', 'My Site');
+app.get('title');
+// => "My Site"
+```
+
+### app.enable(name)
+
+Set setting `name` to `true`.
+
+```js
+app.enable('trust proxy');
+app.get('trust proxy');
+// => true
+```
+
+### app.disable(name)
+
+Set setting `name` to `false`.
+
+```js
+app.disable('trust proxy');
+app.get('trust proxy');
+// => false
+```
+
+### app.enabled(name)
+
+Check if setting `name` is enabled.
+
+```js
+app.enabled('trust proxy');
+// => false
+
+app.enable('trust proxy');
+app.enabled('trust proxy');
+// => true
+```
+
+### app.disabled(name)
+
+Check if setting `name` is disabled.
+
+```js
+app.disabled('trust proxy');
+// => true
+
+app.enable('trust proxy');
+app.disabled('trust proxy');
+// => false
+```
+
+### app.configure([env], callback)
+
+Conditionally invoke `callback` when `env` matches `app.get('env')`,
+aka `process.env.NODE_ENV`. This method remains for legacy reasons, and is effectively
+an `if` statement as illustrated in the following snippets. These functions are <em>not</em>
+required in order to use `app.set()` and other configuration methods.
+
+```js
+// all environments
+app.configure(function () {
+  app.set('title', 'My Application');
+});
+
+// development only
+app.configure('development', function () {
+  app.set('db uri', 'localhost/dev');
+});
+
+// production only
+app.configure('production', function () {
+  app.set('db uri', 'n.n.n.n/prod');
+});
+```
+
+Is effectively sugar for:
+
+```js
+// all environments
+app.set('title', 'My Application');
+
+// development only
+if (app.get('env') === 'development') {
+  app.set('db uri', 'localhost/dev');
+}
+
+// production only
+if (app.get('env') === 'production') {
+  app.set('db uri', 'n.n.n.n/prod');
+}
+```
+
+### app.use([path], function)
+
+Use the given middleware `function`, with optional mount `path`,
+defaulting to "/".
+
+```js
+var express = require('express');
+var app = express();
+
+// simple logger
+app.use(function (req, res, next) {
+  console.log('%s %s', req.method, req.url);
+  next();
+});
+
+// respond
+app.use(function (req, res, next) {
+  res.send('Hello World');
+});
+
+app.listen(3000);
+```
+
+The "mount" path is stripped and is <strong>not</strong> visible
+to the middleware `function`. The main effect of this feature is that
+mounted middleware may operate without code changes regardless of its "prefix"
+pathname.
+
+<Alert type="alert">
+
+A route will match any path that follows its path immediately with either a "`/`" or a "`.`". For example: `app.use('/apple', ...)` will match _/apple_, _/apple/images_, _/apple/images/news_, _/apple.html_, _/apple.html.txt_, and so on.
+
+</Alert>
+
+Here's a concrete example, take the typical use-case of serving files in ./public
+using the `express.static()` middleware:
+
+```js
+// GET /javascripts/jquery.js
+// GET /style.css
+// GET /favicon.ico
+app.use(express.static(path.join(__dirname, 'public')));
+```
+
+Say for example you wanted to prefix all static files with "/static", you could
+use the "mounting" feature to support this. Mounted middleware functions are _not_
+invoked unless the `req.url` contains this prefix, at which point
+it is stripped when the function is invoked. This affects this function only,
+subsequent middleware will see `req.url` with "/static" included
+unless they are mounted as well.
+
+```js
+// GET /static/javascripts/jquery.js
+// GET /static/style.css
+// GET /static/favicon.ico
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+The order of which middleware are "defined" using `app.use()` is
+very important, they are invoked sequentially, thus this defines middleware
+precedence. For example usually `express.logger()` is the very
+first middleware you would use, logging every request:
+
+```js
+app.use(express.logger());
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(function (req, res) {
+  res.send('Hello');
+});
+```
+
+Now suppose you wanted to ignore logging requests for static files, but to
+continue logging routes and middleware defined after `logger()`,
+you would simply move `static()` above:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(express.logger());
+app.use(function (req, res) {
+  res.send('Hello');
+});
+```
+
+Another concrete example would be serving files from multiple directories,
+giving precedence to "./public" over the others:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(express.static(path.join(__dirname, 'files')));
+app.use(express.static(path.join(__dirname, 'uploads')));
+```
+
+### app.engine(ext, callback)
+
+Register the given template engine `callback` as `ext`
+
+By default will `require()` the engine based on the
+file extension. For example if you try to render
+a "foo.jade" file Express will invoke the following internally,
+and cache the `require()` on subsequent calls to increase
+performance.
+
+```js
+app.engine('jade', require('jade').__express);
+```
+
+For engines that do not provide `.__express` out of the box -
+or if you wish to "map" a different extension to the template engine
+you may use this method. For example mapping the EJS template engine to
+".html" files:
+
+```js
+app.engine('html', require('ejs').renderFile);
+```
+
+In this case EJS provides a `.renderFile()` method with
+the same signature that Express expects: `(path, options, callback)`,
+though note that it aliases this method as `ejs.__express` internally
+so if you're using ".ejs" extensions you dont need to do anything.
+
+Some template engines do not follow this convention, the
+
+<a href="https://github.com/visionmedia/consolidate.js">consolidate.js</a>
+library was created to map all of node's popular template engines to follow this convention, thus
+allowing them to work seemlessly within Express.
+
+```js
+var engines = require('consolidate');
+app.engine('haml', engines.haml);
+app.engine('html', engines.hogan);
+```
+
+### app.param([name], callback)
+
+Map logic to route parameters. For example when `:user`
+is present in a route path you may map user loading logic to automatically
+provide `req.user` to the route, or perform validations
+on the parameter input.
+
+The following snippet illustrates how the `callback`
+is much like middleware, thus supporting async operations, however
+providing the additional value of the parameter, here named as `id`.
+An attempt to load the user is then performed, assigning `req.user`,
+otherwise passing an error to `next(err)`.
+
+```js
+app.param('user', function (req, res, next, id) {
+  User.find(id, function (err, user) {
+    if (err) {
+      next(err);
+    } else if (user) {
+      req.user = user;
+      next();
+    } else {
+      next(new Error('failed to load user'));
+    }
+  });
+});
+```
+
+Alternatively you may pass only a `callback`, in which
+case you have the opportunity to alter the `app.param()` API.
+For example the <a href="http://github.com/expressjs/express-params">express-params</a>
+defines the following callback which allows you to restrict parameters to a given
+regular expression.
+
+This example is a bit more advanced, checking if the second argument is a regular
+expression, returning the callback which acts much like the "user" param example.
+
+```js
+app.param(function (name, fn) {
+  if (fn instanceof RegExp) {
+    return function (req, res, next, val) {
+      var captures;
+      if ((captures = fn.exec(String(val)))) {
+        req.params[name] = captures;
+        next();
+      } else {
+        next('route');
+      }
+    };
+  }
+});
+```
+
+The method could now be used to effectively validate parameters, or also
+parse them to provide capture groups:
+
+```js
+app.param('id', /^\d+$/);
+
+app.get('/user/:id', function (req, res) {
+  res.send('user ' + req.params.id);
+});
+
+app.param('range', /^(\w+)\.\.(\w+)?$/);
+
+app.get('/range/:range', function (req, res) {
+  var range = req.params.range;
+  res.send('from ' + range[1] + ' to ' + range[2]);
+});
+```
+
+### app.VERB(path, [callback...], callback)
+
+The `app.VERB()` methods provide the routing functionality
+in Express, where <strong>VERB</strong> is one of the HTTP verbs, such
+as `app.post()`. Multiple callbacks may be given, all are treated
+equally, and behave just like middleware, with the one exception that
+these callbacks may invoke `next('route')` to bypass the
+remaining route callback(s). This mechanism can be used to perform pre-conditions
+on a route then pass control to subsequent routes when there is no reason to proceed
+with the route matched.
+
+The following snippet illustrates the most simple route definition possible. Express
+translates the path strings to regular expressions, used internally to match incoming requests.
+Query strings are <em>not</em> considered when peforming these matches, for example "GET /"
+would match the following route, as would "GET /?name=tobi".
+
+```js
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+```
+
+Regular expressions may also be used, and can be useful
+if you have very specific restraints, for example the following
+would match "GET /commits/71dbb9c" as well as "GET /commits/71dbb9c..4c084f9".
+
+```js
+app.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, function (req, res) {
+  var from = req.params[0];
+  var to = req.params[1] || 'HEAD';
+  res.send('commit range ' + from + '..' + to);
+});
+```
+
+Several callbacks may also be passed, useful for re-using middleware
+that load resources, perform validations, etc.
+
+```js
+app.get('/user/:id', user.load, function () {
+  // ...
+});
+```
+
+These callbacks may be passed within arrays as well, these arrays are
+simply flattened when passed:
+
+```js
+var middleware = [loadForum, loadThread];
+
+app.get('/forum/:fid/thread/:tid', middleware, function () {
+  // ...
+});
+
+app.post('/forum/:fid/thread/:tid', middleware, function () {
+  // ...
+});
+```
+
+### app.all(path, [callback...], callback)
+
+This method functions just like the `app.VERB()` methods,
+however it matches all HTTP verbs.
+
+This method is extremely useful for
+mapping "global" logic for specific path prefixes or arbitrary matches.
+For example if you placed the following route at the top of all other
+route definitions, it would require that all routes from that point on
+would require authentication, and automatically load a user. Keep in mind
+that these callbacks do not have to act as end points, `loadUser`
+can perform a task, then `next()` to continue matching subsequent
+routes.
+
+```js
+app.all('*', requireAuthentication, loadUser);
+```
+
+Or the equivalent:
+
+```js
+app.all('*', requireAuthentication);
+app.all('*', loadUser);
+```
+
+Another great example of this is white-listed "global" functionality. Here
+the example is much like before, however only restricting paths prefixed with
+"/api":
+
+```js
+app.all('/api/*', requireAuthentication);
+```
+
+### app.render(view, [options], callback)
+
+Render a `view` with a callback responding with
+the rendered string. This is the app-level variant of `res.render()`,
+and otherwise behaves the same way.
+
+```js
+app.render('email', function (err, html) {
+  // ...
+});
+
+app.render('email', { name: 'Tobi' }, function (err, html) {
+  // ...
+});
+```
+
+### app.listen()
+
+Bind and listen for connections on the given host and port,
+this method is identical to node's <a href="http://nodejs.org/api/http.html#http_server_listen_port_hostname_backlog_callback">http.Server#listen()</a>.
+
+```js
+var express = require('express');
+var app = express();
+app.listen(3000);
+```
+
+The `app` returned by `express()` is in fact a JavaScript
+`Function`, designed to be passed to node's http servers as a callback
+to handle requests. This allows you to provide both HTTP and HTTPS versions of
+your app with the same codebase easily, as the app does not inherit from these,
+it is simply a callback:
+
+```js
+var express = require('express');
+var https = require('https');
+var http = require('http');
+var app = express();
+
+http.createServer(app).listen(80);
+https.createServer(options, app).listen(443);
+```
+
+The `app.listen()` method is simply a convenience method defined as,
+if you wish to use HTTPS or provide both, use the technique above.
+
+```js
+app.listen = function () {
+  var server = http.createServer(this);
+  return server.listen.apply(server, arguments);
+};
+```
diff --git a/src/content/api/3x/api/middleware/index.mdx b/src/content/api/3x/api/middleware/index.mdx
new file mode 100644
index 0000000000..0f9b71a5b4
--- /dev/null
+++ b/src/content/api/3x/api/middleware/index.mdx
@@ -0,0 +1,147 @@
+---
+title: Middleware
+description: Express 3.x includes a number of built-in middleware functions that can be used to handle common tasks such as parsing request bodies, handling cookies, and more. These middleware functions are available as properties on the Express module and can be added to your application using app.use().
+---
+
+Express 3.x includes a number of built-in middleware functions that can be used to handle common tasks such as parsing request bodies, handling cookies, and more. These middleware functions are available as properties on the Express module and can be added to your application using `app.use()`.
+
+### basicAuth()
+
+Basic Authentication middleware, populating `req.user`
+with the username.
+
+Simple username and password:
+
+```js
+app.use(express.basicAuth('username', 'password'));
+```
+
+Callback verification:
+
+```js
+app.use(
+  express.basicAuth(function (user, pass) {
+    return user === 'tj' && pass === 'wahoo';
+  })
+);
+```
+
+Async callback verification, accepting `fn(err, user)`,
+in this case `req.user` will be the user object passed.
+
+```js
+app.use(
+  express.basicAuth(function (user, pass, fn) {
+    User.authenticate({ user: user, pass: pass }, fn);
+  })
+);
+```
+
+### bodyParser()
+
+Request body parsing middleware supporting JSON, urlencoded,
+and multipart requests. This middleware is simply a wrapper
+for the `json()`, `urlencoded()`, and
+`multipart()` middleware.
+
+```js
+app.use(express.bodyParser());
+
+// is equivalent to:
+app.use(express.json());
+app.use(express.urlencoded());
+app.use(express.multipart());
+```
+
+For security sake, it's better to disable file upload if your application
+doesn't need it. To do this, use only the needed middleware, i.e. don't use
+the `bodyParser` and `multipart()` middleware:
+
+```js
+app.use(express.json());
+app.use(express.urlencoded());
+```
+
+If your application needs file upload you should set up
+
+<a href="https://groups.google.com/d/msg/express-js/iP2VyhkypHo/5AXQiYN3RPcJ">
+  a strategy for dealing with those files
+</a>
+.
+
+### compress()
+
+Compress response data with gzip / deflate. This middleware
+should be placed "high" within the stack to ensure all
+responses may be compressed.
+
+```js
+app.use(express.logger());
+app.use(express.compress());
+app.use(express.methodOverride());
+app.use(express.bodyParser());
+```
+
+### cookieParser()
+
+Parses the Cookie header field and populates `req.cookies`
+with an object keyed by the cookie names. Optionally you may enabled
+signed cookie support by passing a `secret` string.
+
+```js
+app.use(express.cookieParser());
+app.use(express.cookieParser('some secret'));
+```
+
+### cookieSession()
+
+Provides cookie-based sessions, and populates `req.session`.
+This middleware takes the following options:
+
+- `key` cookie name defaulting to `connect.sess`
+- `secret` prevents cookie tampering
+- `cookie` session cookie settings, defaulting to `{ path: '/', httpOnly: true, maxAge: null }`
+- `proxy` trust the reverse proxy when setting secure cookies (via "x-forwarded-proto")
+
+```js
+app.use(express.cookieSession());
+```
+
+To clear a cookie simply assign the session to null before responding:
+
+```js
+req.session = null;
+```
+
+### csrf()
+
+CSRF protection middleware.
+
+By default this middleware generates a token named "\_csrf"
+which should be added to requests which mutate
+state, within a hidden form field, query-string etc. This
+token is validated against `req.csrfToken()`.
+
+The default `value` function checks `req.body` generated
+by the `bodyParser()` middleware, `req.query` generated
+by `query()`, and the "X-CSRF-Token" header field.
+
+This middleware requires session support, thus should be added
+somewhere below `session()`.
+
+### directory()
+
+Directory serving middleware, serves the given `path`.
+This middleware may be paired with `static()` to serve
+files, providing a full-featured file browser.
+
+```js
+app.use(express.directory('public'));
+app.use(express.static('public'));
+```
+
+This middleware accepts the following options:
+
+- `hidden` display hidden (dot) files. Defaults to false.
+- `icons` display icons. Defaults to false.
+- `filter` Apply this filter function to files. Defaults to false.
diff --git a/src/content/api/3x/api/request/index.mdx b/src/content/api/3x/api/request/index.mdx
new file mode 100644
index 0000000000..b7273035e2
--- /dev/null
+++ b/src/content/api/3x/api/request/index.mdx
@@ -0,0 +1,441 @@
+---
+title: Request
+description: Learn about the Request object for Express 3.x, including its properties and methods.
+---
+
+The `req` object is an enhanced version of Node's own request object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#class-httpincomingmessage).
+
+## Properties
+
+The `req` object contains a number of properties that provide information about the HTTP request, such as headers, query parameters, and more.
+
+### req.accepted
+
+Return an array of Accepted media types ordered from highest quality to lowest.
+
+```json
+[
+  { "value": "application/json", "quality": 1, "type": "application", "subtype": "json" },
+  { "value": "text/html", "quality": 0.5, "type": "text", "subtype": "html" }
+]
+```
+
+### req.acceptedCharsets
+
+Return an array of Accepted charsets ordered from highest quality to lowest.
+
+```
+Accept-Charset: iso-8859-5;q=.2, unicode-1-1;q=0.8
+// => ['unicode-1-1', 'iso-8859-5']
+```
+
+### req.acceptedLanguages
+
+Return an array of Accepted languages ordered from highest quality to lowest.
+
+```
+Accept-Language: en;q=.5, en-us
+// => ['en-us', 'en']
+```
+
+### req.body
+
+This property is an object containing the parsed request body. This feature
+is provided by the `bodyParser()` middleware, though other body
+parsing middleware may follow this convention as well. This property
+defaults to `{}` when `bodyParser()` is used.
+
+```js title="index.js"
+// POST user[name]=tobi&user[email]=tobi@learnboost.com
+console.log(req.body.user.name);
+// => "tobi"
+
+console.log(req.body.user.email);
+// => "tobi@learnboost.com"
+
+// POST { "name": "tobi" }
+console.log(req.body.name);
+// => "tobi"
+```
+
+### req.cookies
+
+This object requires the `cookieParser()` middleware for use.
+It contains cookies sent by the user-agent. If no cookies are sent, it
+defaults to `{}`.
+
+```js title="index.js"
+// Cookie: name=tj
+console.log(req.cookies.name);
+// => "tj"
+```
+
+### req.files
+
+This property is an object of the files uploaded. This feature
+is provided by the `bodyParser()` middleware, though other body
+parsing middleware may follow this convention as well. This property
+defaults to `{}` when `bodyParser()` is used.
+
+For example if a <strong>file</strong> field was named "image",
+and a file was uploaded, `req.files.image` would contain
+the following `File` object:
+
+```json
+{ size: 74643,
+  path: '/tmp/8ef9c52abe857867fd0a4e9a819d1876',
+  name: 'edge.png',
+  type: 'image/png',
+  hash: false,
+  lastModifiedDate: Thu Aug 09 2012 20:07:51 GMT-0700 (PDT),
+  _writeStream:
+   { path: '/tmp/8ef9c52abe857867fd0a4e9a819d1876',
+     fd: 13,
+     writable: false,
+     flags: 'w',
+     encoding: 'binary',
+     mode: 438,
+     bytesWritten: 74643,
+     busy: false,
+     _queue: [],
+     _open: [Function],
+     drainable: true },
+  length: [Getter],
+  filename: [Getter],
+  mime: [Getter] }
+```
+
+The `bodyParser()` middleware utilizes the
+
+<a href="https://github.com/felixge/node-formidable">node-formidable</a>
+module internally, and accepts the same options. An example of this is the `keepExtensions`
+formidable option, defaulting to <strong>false</strong>
+which in this case gives you the filename "/tmp/8ef9c52abe857867fd0a4e9a819d1876" void of the ".png"
+extension. To enable this, and others you may pass them to `bodyParser()`:
+
+```js
+app.use(express.bodyParser({ keepExtensions: true, uploadDir: '/my/files' }));
+```
+
+### req.fresh
+
+Check if the request is fresh - aka Last-Modified and/or the ETag still match,
+indicating that the resource is "fresh".
+
+```js
+console.dir(req.fresh);
+// => true
+```
+
+### req.host
+
+Returns the hostname from the "Host" header field (void of portno).
+
+```js
+// Host: "example.com:3000"
+console.dir(req.host);
+// => 'example.com'
+```
+
+### req.ip
+
+Return the remote address, or when "trust proxy"
+is enabled - the upstream address.
+
+```js
+console.dir(req.ip);
+// => '127.0.0.1'
+```
+
+### req.ips
+
+When "trust proxy" is `true`, parse
+the "X-Forwarded-For" ip address list
+and return an array, otherwise an empty
+array is returned.
+
+For example if the value were "client, proxy1, proxy2"
+you would receive the array `["client", "proxy1", "proxy2"]`
+where "proxy2" is the furthest down-stream.
+
+### req.originalUrl
+
+This property is much like `req.url`, however it retains
+the original request url, allowing you to rewrite `req.url`
+freely for internal routing purposes. For example the "mounting" feature
+of <a href="#app.use">app.use()</a> will rewrite `req.url` to
+strip the mount point.
+
+```js
+// GET /search?q=something
+console.log(req.originalUrl);
+// => "/search?q=something"
+```
+
+### req.params
+
+This property is an array containing properties mapped to the named route "parameters".
+For example if you have the route `/user/:name`, then the "name" property
+is available to you as `req.params.name`. This object defaults to `{}`.
+
+```js
+// GET /user/tj
+console.dir(req.params.name);
+// => 'tj'
+```
+
+When a regular expression is used for the route definition, capture groups
+are provided in the array using `req.params[N]`, where `N`
+is the nth capture group. This rule is applied to unnamed wild-card matches
+with string routes such as `/file/*`:
+
+```js
+// GET /file/javascripts/jquery.js
+console.dir(req.params[0]);
+// => 'javascripts/jquery.js'
+```
+
+### req.path
+
+Returns the request URL pathname.
+
+```js
+// example.com/users?sort=desc
+console.dir(req.path);
+// => '/users'
+```
+
+### req.protocol
+
+Return the protocol string "http" or "https"
+when requested with TLS. When the "trust proxy"
+setting is enabled the "X-Forwarded-Proto" header
+field will be trusted. If you're running behind
+a reverse proxy that supplies https for you this
+may be enabled.
+
+```js
+console.dir(req.protocol);
+// => 'http'
+```
+
+### req.query
+
+This property is an object containing the parsed query-string,
+defaulting to `{}`.
+
+```js
+// GET /search?q=tobi+ferret
+console.dir(req.query.q);
+// => 'tobi ferret'
+
+// GET /shoes?order=desc&shoe[color]=blue&shoe[type]=converse
+console.dir(req.query.order);
+// => 'desc'
+
+console.dir(req.query.shoe.color);
+// => 'blue'
+
+console.dir(req.query.shoe.type);
+// => 'converse'
+```
+
+### req.res
+
+This property holds a reference to the <a href="#response">response object</a>
+that relates to this request object.
+
+### req.route
+
+The currently matched `Route` containing
+several properties such as the route's original path
+string, the regexp generated, and so on.
+
+```js
+app.get('/user/:id?', function (req, res) {
+  console.dir(req.route);
+});
+```
+
+Example output from the previous snippet:
+
+```json
+{ path: '/user/:id?',
+  method: 'get',
+  callbacks: [ [Function] ],
+  keys: [ { name: 'id', optional: true } ],
+  regexp: /^\/user(?:\/([^\/]+?))?\/?$/i,
+  params: [ id: '12' ] }
+```
+
+### req.secure
+
+Check if a TLS connection is established. This is a short-hand for:
+
+```js
+console.dir(req.protocol === 'https');
+// => true
+```
+
+### req.signedCookies
+
+This object requires the `cookieParser(secret)` middleware for use.
+It contains signed cookies sent by the user-agent, unsigned and ready for use.
+Signed cookies reside in a different object to show developer intent; otherwise,
+a malicious attack could be placed on `req.cookie` values (which are easy to spoof).
+Note that signing a cookie does not make it "hidden" or encrypted; this simply
+prevents tampering (because the secret used to sign is private). If no signed
+cookies are sent, it defaults to `{}`.
+
+```js
+// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
+console.dir(req.signedCookies.user);
+// => 'tobi'
+```
+
+### req.stale
+
+Check if the request is stale - aka Last-Modified and/or the ETag do not match,
+indicating that the resource is "stale".
+
+```js
+console.dir(req.stale);
+// => true
+```
+
+### req.subdomains
+
+Return subdomains as an array.
+
+```js
+// Host: "tobi.ferrets.example.com"
+console.dir(req.subdomains);
+// => ['ferrets', 'tobi']
+```
+
+### req.xhr
+
+Check if the request was issued with the "X-Requested-With"
+header field set to "XMLHttpRequest" (jQuery etc).
+
+```js
+console.dir(req.xhr);
+// => true
+```
+
+## Methods
+
+The `req` object also contains a number of methods that can be used to perform various tasks related to the HTTP request, such as checking the content type, retrieving header values, and more.
+
+### req.accepts(types)
+
+Check if the given `types` are acceptable, returning
+the best match when true, otherwise `undefined` - in which
+case you should respond with 406 "Not Acceptable".
+
+The `type` value may be a single mime type string
+such as "application/json", the extension name
+such as "json", a comma-delimited list or an array. When a list
+or array is given the best match, if any is returned.
+
+```js title="index.js"
+// Accept: text/html
+req.accepts('html');
+// => "html"
+
+// Accept: text/*, application/json
+req.accepts('html');
+// => "html"
+req.accepts('text/html');
+// => "text/html"
+req.accepts('json, text');
+// => "json"
+req.accepts('application/json');
+// => "application/json"
+
+// Accept: text/*, application/json
+req.accepts('image/png');
+req.accepts('png');
+// => undefined
+
+// Accept: text/*;q=.5, application/json
+req.accepts(['html', 'json']);
+req.accepts('html, json');
+// => "json"
+```
+
+### req.acceptsCharset(charset)
+
+Check if the given `charset` are acceptable.
+
+### req.acceptsLanguage(lang)
+
+Check if the given `lang` are acceptable.
+
+### req.get(field)
+
+Get the case-insensitive request header `field`. The "Referrer" and "Referer" fields are interchangeable.
+
+```js
+req.get('Content-Type');
+// => "text/plain"
+
+req.get('content-type');
+// => "text/plain"
+
+req.get('Something');
+// => undefined
+```
+
+Aliased as `req.header(field)`.
+
+### req.is(type)
+
+Check if the incoming request contains the "Content-Type"
+header field, and it matches the give mime `type`.
+
+```js
+// With Content-Type: text/html; charset=utf-8
+req.is('html');
+req.is('text/html');
+req.is('text/*');
+// => true
+
+// When Content-Type is application/json
+req.is('json');
+req.is('application/json');
+req.is('application/*');
+// => true
+
+req.is('html');
+// => false
+```
+
+### req.param(name)
+
+Return the value of param `name` when present.
+
+```js
+// ?name=tobi
+req.param('name');
+// => "tobi"
+
+// POST name=tobi
+req.param('name');
+// => "tobi"
+
+// /user/tobi for /user/:name
+req.param('name');
+// => "tobi"
+```
+
+Lookup is performed in the following order:
+
+- `req.params`
+- `req.body`
+- `req.query`
+
+Direct access to `req.body`, `req.params`,
+and `req.query` should be favoured for clarity - unless
+you truly accept input from each object.
diff --git a/src/content/api/3x/api/response/index.mdx b/src/content/api/3x/api/response/index.mdx
new file mode 100644
index 0000000000..f488de7412
--- /dev/null
+++ b/src/content/api/3x/api/response/index.mdx
@@ -0,0 +1,481 @@
+---
+title: API Response Overview
+description: An overview of the API response object in Express.js, detailing its properties and methods for handling HTTP responses.
+---
+
+The `res` object is an enhanced version of Node's own response object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
+
+## Properties
+
+The `res` object contains a number of properties that provide information about the HTTP response.
+
+### res.charset
+
+Assign the charset. Defaults to "utf-8".
+
+```js
+res.charset = 'value';
+res.send('<p>some html</p>');
+// => Content-Type: text/html; charset=value
+```
+
+### res.locals
+
+Response local variables are scoped to the request, thus only
+available to the view(s) rendered during that request / response
+cycle, if any. Otherwise this API is identical to <a href="#app.locals">app.locals</a>.
+
+This object is useful for exposing request-level information such as the
+request pathname, authenticated user, user settings etcetera.
+
+```js
+app.use(function (req, res, next) {
+  res.locals.user = req.user;
+  res.locals.authenticated = !req.user.anonymous;
+  next();
+});
+```
+
+### res.req
+
+This property holds a reference to the <a href="#request">request object</a>
+that relates to this response object.
+
+## Methods
+
+The `res` object contains a number of methods that can be used to send responses, set headers, and more.
+
+### res.attachment([filename])
+
+Sets the Content-Disposition header field to "attachment". If
+a `filename` is given then the Content-Type will be
+automatically set based on the extname via `res.type()`,
+and the Content-Disposition's "filename=" parameter will be set.
+
+```js
+res.attachment();
+// Content-Disposition: attachment
+
+res.attachment('path/to/logo.png');
+// Content-Disposition: attachment; filename="logo.png"
+// Content-Type: image/png
+```
+
+### res.clearCookie(name, [options])
+
+Clear cookie `name`. The `path` option defaults to "/".
+
+```js
+res.cookie('name', 'tobi', { path: '/admin' });
+res.clearCookie('name', { path: '/admin' });
+```
+
+### res.cookie(name, value, [options])
+
+Set cookie `name` to `value`, which may be a string or object converted to JSON. The `path`
+option defaults to "/".
+
+```js
+res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true });
+res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true });
+```
+
+The `maxAge` option is a convenience option for setting "expires"
+relative to the current time in milliseconds. The following is equivalent to
+the previous example.
+
+```js
+res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true });
+```
+
+An object may be passed which is then serialized as JSON, which is
+automatically parsed by the `bodyParser()` middleware.
+
+```js
+res.cookie('cart', { items: [1, 2, 3] });
+res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 });
+```
+
+Signed cookies are also supported through this method. Simply
+pass the `signed` option. When given `res.cookie()`
+will use the secret passed to `express.cookieParser(secret)`
+to sign the value.
+
+```js
+res.cookie('name', 'tobi', { signed: true });
+```
+
+Later you may access this value through the <a href="#req.signedCookies">req.signedCookie</a>
+object.
+
+### res.download(path, [filename], [fn])
+
+Transfer the file at `path` as an "attachment",
+typically browsers will prompt the user for download. The
+Content-Disposition "filename=" parameter, aka the one
+that will appear in the brower dialog is set to `path`
+by default, however you may provide an override `filename`.
+
+When an error has ocurred or transfer is complete the optional
+callback `fn` is invoked. This method uses [res.sendfile()](#ressendfilepath-options-fn)
+to transfer the file.
+
+```js
+res.download('/report-12345.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf', function (err) {
+  if (err) {
+    // handle error, keep in mind the response may be partially-sent
+    // so check res.headerSent
+  } else {
+    // decrement a download credit etc
+  }
+});
+```
+
+### res.format(object)
+
+Performs content-negotiation on the request Accept header
+field when present. This method uses `req.accepted`, an array of
+acceptable types ordered by their quality values, otherwise the
+first callback is invoked. When no match is performed the server
+responds with 406 "Not Acceptable", or invokes the `default`
+callback.
+
+The Content-Type is set for you when a callback is selected,
+however you may alter this within the callback using `res.set()`
+or `res.type()` etcetera.
+
+The following example would respond with `{ "message": "hey" }`
+when the Accept header field is set to "application/json" or "_/json",
+however if "_/\*" is given then "hey" will be the response.
+
+```js
+res.format({
+  'text/plain': function () {
+    res.send('hey');
+  },
+
+  'text/html': function () {
+    res.send('<p>hey</p>');
+  },
+
+  'application/json': function () {
+    res.send({ message: 'hey' });
+  },
+});
+```
+
+In addition to canonicalized MIME types you may also
+use extnames mapped to these types, providing a slightly
+less verbose implementation:
+
+```js
+res.format({
+  text: function () {
+    res.send('hey');
+  },
+
+  html: function () {
+    res.send('<p>hey</p>');
+  },
+
+  json: function () {
+    res.send({ message: 'hey' });
+  },
+});
+```
+
+### res.get(field)
+
+Get the case-insensitive response header `field`.
+
+```js
+res.get('Content-Type');
+// => "text/plain"
+```
+
+### res.json([status|body], [body])
+
+Send a JSON response. This method is identical
+to `res.send()` when an object or
+array is passed, however it may be used for
+explicit JSON conversion of non-objects (null, undefined, etc),
+though these are technically not valid JSON.
+
+```js
+res.json(null);
+res.json({ user: 'tobi' });
+res.json(500, { error: 'message' });
+```
+
+### res.jsonp([status|body], [body])
+
+Send a JSON response with JSONP support. This method is identical
+to `res.json()` however opts-in to JSONP callback
+support.
+
+```js
+res.jsonp(null);
+// => null
+
+res.jsonp({ user: 'tobi' });
+// => { "user": "tobi" }
+
+res.jsonp(500, { error: 'message' });
+// => { "error": "message" }
+```
+
+By default the JSONP callback name is simply `callback`,
+however you may alter this with the <a href="#app-settings">jsonp callback name</a>
+setting. The following are some examples of JSONP responses using the same
+code:
+
+```js
+// ?callback=foo
+res.jsonp({ user: 'tobi' });
+// => foo({ "user": "tobi" })
+
+app.set('jsonp callback name', 'cb');
+
+// ?cb=foo
+res.jsonp(500, { error: 'message' });
+// => foo({ "error": "message" })
+```
+
+### res.links(links)
+
+Join the given `links` to populate the "Link" response header field.
+
+```js
+res.links({
+  next: 'http://api.example.com/users?page=2',
+  last: 'http://api.example.com/users?page=5',
+});
+```
+
+p yields:
+
+```
+Link: <http://api.example.com/users?page=2> rel="next",
+      <http://api.example.com/users?page=5> rel="last"
+```
+
+### res.location()
+
+Set the location header.
+
+```js
+res.location('/foo/bar');
+res.location('foo/bar');
+res.location('http://example.com');
+res.location('../login');
+res.location('back');
+```
+
+You can use the same kind of `urls` as in `res.redirect()`.
+
+For example, if your application is mounted at `/blog`,
+the following would set the `location` header to
+`/blog/admin`:
+
+```js
+res.location('admin');
+```
+
+### res.redirect([status], url)
+
+Redirect to the given `url` with optional `status` code
+defaulting to 302 "Found".
+
+```js
+res.redirect('/foo/bar');
+res.redirect('http://example.com');
+res.redirect(301, 'http://example.com');
+res.redirect('../login');
+```
+
+Express supports a few forms of redirection, first being
+a fully qualified URI for redirecting to a different site:
+
+```js
+res.redirect('http://google.com');
+```
+
+The second form is the pathname-relative redirect, for example
+if you were on `http://example.com/admin/post/new`, the
+following redirect to `/admin` would land you at `http://example.com/admin`:
+
+```js
+res.redirect('/admin');
+```
+
+This next redirect is relative to the `mount` point of the application. For example
+if you have a blog application mounted at `/blog`, ideally it has no knowledge of
+where it was mounted, so where a redirect of `/admin/post/new` would simply give you
+`http://example.com/admin/post/new`, the following mount-relative redirect would give
+you `http://example.com/blog/admin/post/new`:
+
+```js
+res.redirect('admin/post/new');
+```
+
+Pathname relative redirects are also possible. If you were
+on `http://example.com/admin/post/new`, the following redirect
+would land you at `http//example.com/admin/post`:
+
+```js
+res.redirect('..');
+```
+
+The final special-case is a `back` redirect, redirecting back to
+the Referer (or Referrer), defaulting to `/` when missing.
+
+```js
+res.redirect('back');
+```
+
+### res.render(view, [locals], callback)
+
+Render a `view` with a callback responding with
+the rendered string. When an error occurs `next(err)`
+is invoked internally. When a callback is provided both the possible error
+and rendered string are passed, and no automated response is performed.
+
+```js
+res.render('index', function (err, html) {
+  // ...
+});
+
+res.render('user', { name: 'Tobi' }, function (err, html) {
+  // ...
+});
+```
+
+### res.send([body|status], [body])
+
+Send a response.
+
+```js
+res.send(Buffer.from('whoop'));
+res.send({ some: 'json' });
+res.send('<p>some html</p>');
+res.send(404, 'Sorry, we cannot find that!');
+res.send(500, { error: 'something blew up' });
+res.send(200);
+```
+
+This method performs a myriad of
+useful tasks for simple non-streaming responses such
+as automatically assigning the Content-Length unless
+previously defined and providing automatic <em>HEAD</em> and
+HTTP cache freshness support.
+
+When a `Buffer` is given
+the Content-Type is set to "application/octet-stream"
+unless previously defined as shown below:
+
+```js
+res.set('Content-Type', 'text/html');
+res.send(Buffer.from('<p>some html</p>'));
+```
+
+When a `String` is given the
+Content-Type is set defaulted to "text/html":
+
+```js
+res.send('<p>some html</p>');
+```
+
+When an `Array` or `Object` is
+given Express will respond with the JSON representation:
+
+```js
+res.send({ user: 'tobi' });
+res.send([1, 2, 3]);
+```
+
+Finally when a `Number` is given without
+any of the previously mentioned bodies, then a response
+body string is assigned for you. For example 200 will
+respond will the text "OK", and 404 "Not Found" and so on.
+
+```js
+res.send(200);
+res.send(404);
+res.send(500);
+```
+
+### res.sendfile(path, [options], [fn]])
+
+Transfer the file at the given `path`.
+
+Automatically defaults the Content-Type response header field based
+on the filename's extension. The callback `fn(err)` is
+invoked when the transfer is complete or when an error occurs.
+
+Options:
+
+- `maxAge` in milliseconds defaulting to 0
+- `root` root directory for relative filenames
+
+This method provides fine-grained support for file serving
+as illustrated in the following example:
+
+```js
+app.get('/user/:uid/photos/:file', function (req, res) {
+  var uid = req.params.uid;
+  var file = req.params.file;
+
+  req.user.mayViewFilesFrom(uid, function (yes) {
+    if (yes) {
+      res.sendfile('/uploads/' + uid + '/' + file);
+    } else {
+      res.send(403, 'Sorry! you cant see that.');
+    }
+  });
+});
+```
+
+### res.set(field, [value])
+
+Set header `field` to `value`, or pass an object to set multiple fields at once.
+
+```js
+res.set('Content-Type', 'text/plain');
+
+res.set({
+  'Content-Type': 'text/plain',
+  'Content-Length': '123',
+  ETag: '12345',
+});
+```
+
+Aliased as `res.header(field, [value])`.
+
+### res.status(code)
+
+Chainable alias of node's `res.statusCode=`.
+
+```js
+res.status(404).sendfile('path/to/404.png');
+```
+
+### res.type(type)
+
+Sets the Content-Type to the mime lookup of `type`,
+or when "/" is present the Content-Type is simply set to this
+literal value.
+
+```js
+res.type('.html');
+res.type('html');
+res.type('json');
+res.type('application/json');
+res.type('png');
+```
+
+p Aliased as `res.contentType(type)`.
diff --git a/src/content/api/4x/api.mdx b/src/content/api/4x/api.mdx
new file mode 100644
index 0000000000..7b27fd8452
--- /dev/null
+++ b/src/content/api/4x/api.mdx
@@ -0,0 +1,59 @@
+---
+title: 4x API Reference
+description: API Reference for version 4.x
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+import Card from '@components/primitives/Card/Card.astro';
+import { CardList } from '@components/patterns';
+
+This section provides an overview of the modules and APIs available in Express 4.x for building web applications and HTTP services.
+
+```js title="index.js"
+var express = require('express');
+var app = express();
+
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+<Alert type="info">
+
+Express 4.x requires **Node.js 0.10.0 or higher**.
+
+</Alert>
+
+With express v4.x, you can define routes, configure middleware, and start handling HTTP requests using the application instance created by the `express()` function. The API is organized into the following sections:
+
+<CardList gap="6">
+  <a href="/en/4x/api/express">
+    <Card
+      title="express()"
+      body="Learn about the express() function, which creates an Express application."
+    />
+  </a>
+  <a href="/en/4x/api/application">
+    <Card
+      title="Application Object"
+      body="Learn about the properties and methods of the Express 4.x application object."
+    />
+  </a>
+  <a href="/en/4x/api/request">
+    <Card
+      title="Request Object"
+      body="Learn about the properties and methods of the Express 4.x request object."
+    />
+  </a>
+  <a href="/en/4x/api/response">
+    <Card
+      title="Response Object"
+      body="Learn about the properties and methods of the Express 4.x response object."
+    />
+  </a>
+  <a href="/en/4x/api/router">
+    <Card title="Router" body="Learn about the properties and methods of the Express 4.x router." />
+  </a>
+</CardList>
diff --git a/src/content/api/4x/api/application/index.mdx b/src/content/api/4x/api/application/index.mdx
new file mode 100644
index 0000000000..ac1189715d
--- /dev/null
+++ b/src/content/api/4x/api/application/index.mdx
@@ -0,0 +1,1182 @@
+---
+title: Application Object
+description: Learn about the properties of the Express application object.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `app` object conventionally denotes the Express application.
+Create it by calling the top-level `express()` function exported by the Express module:
+
+```js
+var express = require('express');
+var app = express();
+
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+The `app` object has methods for
+
+- Routing HTTP requests; see for example, [app.METHOD](#appmethodpath-callback--callback-) and [app.param](#appparamname-callback).
+- Configuring middleware; see [app.route](#approutepath).
+- Rendering HTML views; see [app.render](#apprenderview-locals-callback).
+- Registering a template engine; see [app.engine](#appengineext-callback).
+
+It also has settings (properties) that affect how the application behaves;
+for more information, see [Application Settings](#application-settings).
+
+<Alert type="info">
+
+The Express application object can be referred from the [request object](/en/4x/api/request) and the [response object](/en/4x/api/response) as `req.app`, and `res.app`, respectively.
+
+</Alert>
+
+## Properties
+
+### app.locals
+
+The `app.locals` object has properties that are local variables within the application,
+and will be available in templates rendered with [res.render](#res.render).
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+```js
+console.dir(app.locals.title);
+// => 'My App'
+
+console.dir(app.locals.email);
+// => 'me@myapp.com'
+```
+
+Once set, the value of `app.locals` properties persist throughout the life of the application,
+in contrast with [res.locals](#res.locals) properties that
+are valid only for the lifetime of the request.
+
+You can access local variables in templates rendered within the application.
+This is useful for providing helper functions to templates, as well as application-level data.
+Local variables are available in middleware via `req.app.locals` (see [req.app](#req.app))
+
+```js
+app.locals.title = 'My App';
+app.locals.strftime = require('strftime');
+app.locals.email = 'me@myapp.com';
+```
+
+### app.mountpath
+
+The `app.mountpath` property contains one or more path patterns on which a sub-app was mounted.
+
+<Alert type="info">
+
+A sub-app is an instance of `express` that may be used for handling the request to a route.
+
+</Alert>
+
+```js
+var express = require('express');
+
+var app = express(); // the main app
+var admin = express(); // the sub app
+
+admin.get('/', function (req, res) {
+  console.log(admin.mountpath); // /admin
+  res.send('Admin Homepage');
+});
+
+app.use('/admin', admin); // mount the sub app
+```
+
+It is similar to the [baseUrl](#req.baseUrl) property of the `req` object, except `req.baseUrl`
+returns the matched URL path, instead of the matched patterns.
+
+If a sub-app is mounted on multiple path patterns, `app.mountpath` returns the list of
+patterns it is mounted on, as shown in the following example.
+
+```js
+var admin = express();
+
+admin.get('/', function (req, res) {
+  console.dir(admin.mountpath); // [ '/adm*n', '/manager' ]
+  res.send('Admin Homepage');
+});
+
+var secret = express();
+secret.get('/', function (req, res) {
+  console.log(secret.mountpath); // /secr*t
+  res.send('Admin Secret');
+});
+
+admin.use('/secr*t', secret); // load the 'secret' router on '/secr*t', on the 'admin' sub app
+app.use(['/adm*n', '/manager'], admin); // load the 'admin' router on '/adm*n' and '/manager', on the parent app
+```
+
+## Events
+
+### app.on('mount', callback(parent))
+
+The `mount` event is fired on a sub-app, when it is mounted on a parent app. The parent app is passed to the callback function.
+
+<Alert type="info">
+**NOTE**
+
+Sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value.
+
+For details, see [Application settings](#application-settings).
+
+</Alert>
+
+```js
+var admin = express();
+
+admin.on('mount', function (parent) {
+  console.log('Admin Mounted');
+  console.log(parent); // refers to the parent app
+});
+
+admin.get('/', function (req, res) {
+  res.send('Admin Homepage');
+});
+
+app.use('/admin', admin);
+```
+
+## Methods
+
+### app.all(path, callback [, callback ...])
+
+This method is like the standard [app.METHOD()](#appmethodpath-callback--callback-) methods,
+except it matches all HTTP verbs.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Examples
+
+The following callback is executed for requests to `/secret` whether using
+GET, POST, PUT, DELETE, or any other HTTP request method:
+
+```js
+app.all('/secret', function (req, res, next) {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+The `app.all()` method is useful for mapping "global" logic for specific path prefixes or arbitrary matches. For example, if you put the following at the top of all other
+route definitions, it requires that all routes from that point on
+require authentication, and automatically load a user. Keep in mind
+that these callbacks do not have to act as end-points: `loadUser`
+can perform a task, then call `next()` to continue matching subsequent
+routes.
+
+```js
+app.all('*', requireAuthentication, loadUser);
+```
+
+Or the equivalent:
+
+```js
+app.all('*', requireAuthentication);
+app.all('*', loadUser);
+```
+
+Another example is white-listed "global" functionality.
+The example is similar to the ones above, but it only restricts paths that start with
+"/api":
+
+```js
+app.all('/api/*', requireAuthentication);
+```
+
+### app.delete(path, callback [, callback ...])
+
+Routes HTTP DELETE requests to the specified path with the specified callback functions.
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Example
+
+```js
+app.delete('/', function (req, res) {
+  res.send('DELETE request to homepage');
+});
+```
+
+### app.disable(name)
+
+Sets the Boolean setting `name` to `false`, where `name` is one of the properties from the [app settings table](#application-settings).
+Calling `app.set('foo', false)` for a Boolean property is the same as calling `app.disable('foo')`.
+
+For example:
+
+```js
+app.disable('trust proxy');
+app.get('trust proxy');
+// => false
+```
+
+### app.disabled(name)
+
+Returns `true` if the Boolean setting `name` is disabled (`false`), where `name` is one of the properties from
+the [app settings table](#application-settings).
+
+```js
+app.disabled('trust proxy');
+// => true
+
+app.enable('trust proxy');
+app.disabled('trust proxy');
+// => false
+```
+
+### app.enable(name)
+
+Sets the Boolean setting `name` to `true`, where `name` is one of the properties from the [app settings table](#application-settings).
+Calling `app.set('foo', true)` for a Boolean property is the same as calling `app.enable('foo')`.
+
+```js
+app.enable('trust proxy');
+app.get('trust proxy');
+// => true
+```
+
+### app.enabled(name)
+
+Returns `true` if the setting `name` is enabled (`true`), where `name` is one of the
+properties from the [app settings table](#application-settings).
+
+```js
+app.enabled('trust proxy');
+// => false
+
+app.enable('trust proxy');
+app.enabled('trust proxy');
+// => true
+```
+
+### app.engine(ext, callback)
+
+Registers the given template engine `callback` as `ext`.
+
+By default, Express will `require()` the engine based on the file extension.
+For example, if you try to render a "foo.pug" file, Express invokes the
+following internally, and caches the `require()` on subsequent calls to increase
+performance.
+
+```js
+app.engine('pug', require('pug').__express);
+```
+
+Use this method for engines that do not provide `.__express` out of the box,
+or if you wish to "map" a different extension to the template engine.
+
+For example, to map the EJS template engine to ".html" files:
+
+```js
+app.engine('html', require('ejs').renderFile);
+```
+
+In this case, EJS provides a `.renderFile()` method with
+the same signature that Express expects: `(path, options, callback)`,
+though note that it aliases this method as `ejs.__express` internally
+so if you're using ".ejs" extensions you don't need to do anything.
+
+Some template engines do not follow this convention. The
+[consolidate.js](https://github.com/tj/consolidate.js) library maps Node template engines to follow this convention,
+so they work seamlessly with Express.
+
+```js
+var engines = require('consolidate');
+app.engine('haml', engines.haml);
+app.engine('html', engines.hogan);
+```
+
+### app.get(name)
+
+Returns the value of `name` app setting, where `name` is one of the strings in the
+[app settings table](#application-settings). For example:
+
+```js
+app.get('title');
+// => undefined
+
+app.set('title', 'My Site');
+app.get('title');
+// => "My Site"
+```
+
+### app.get(path, callback [, callback ...])
+
+Routes HTTP GET requests to the specified path with the specified callback functions.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Example
+
+```js
+app.get('/', function (req, res) {
+  res.send('GET request to homepage');
+});
+```
+
+### app.listen(path, [callback])
+
+Starts a UNIX socket and listens for connections on the given path.
+This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
+
+```js
+var express = require('express');
+var app = express();
+app.listen('/tmp/sock');
+```
+
+### app.listen([port[, host[, backlog]]][, callback])
+
+Binds and listens for connections on the specified host and port.
+This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
+
+If port is omitted or is 0, the operating system will assign an arbitrary unused
+port, which is useful for cases like automated tasks (tests, etc.).
+
+```js
+var express = require('express');
+var app = express();
+app.listen(3000);
+```
+
+The `app` returned by `express()` is in fact a JavaScript
+`Function`, designed to be passed to Node's HTTP servers as a callback
+to handle requests. This makes it easy to provide both HTTP and HTTPS versions of
+your app with the same code base, as the app does not inherit from these
+(it is simply a callback):
+
+```js
+var express = require('express');
+var https = require('https');
+var http = require('http');
+var app = express();
+
+http.createServer(app).listen(80);
+https.createServer(options, app).listen(443);
+```
+
+The `app.listen()` method returns an [http.Server](https://nodejs.org/api/http.html#http_class_http_server) object and (for HTTP) is a convenience method for the following:
+
+```js
+app.listen = function () {
+  var server = http.createServer(this);
+  return server.listen.apply(server, arguments);
+};
+```
+
+<Alert type="info">
+
+All the forms of Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen) method are in fact actually supported.
+
+</Alert>
+
+### app.METHOD(path, callback [, callback ...])
+
+Routes an HTTP request, where METHOD is the HTTP method of the request, such as GET,
+PUT, POST, and so on, in lowercase. Thus, the actual methods are `app.get()`,
+`app.post()`, `app.put()`, and so on. See [Routing methods](#routing-methods) below for the complete list.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Routing methods
+
+Express supports the following routing methods corresponding to the HTTP methods of the same names:
+
+<div class="methods-columns">
+  <ul>
+    <li>
+      <code>checkout</code>
+    </li>
+    <li>
+      <code>copy</code>
+    </li>
+    <li>
+      <code>delete</code>
+    </li>
+    <li>
+      <code>get</code>
+    </li>
+    <li>
+      <code>head</code>
+    </li>
+    <li>
+      <code>lock</code>
+    </li>
+    <li>
+      <code>merge</code>
+    </li>
+    <li>
+      <code>mkactivity</code>
+    </li>
+  </ul>
+  <ul>
+    <li>
+      <code>mkcol</code>
+    </li>
+    <li>
+      <code>move</code>
+    </li>
+    <li>
+      <code>m-search</code>
+    </li>
+    <li>
+      <code>notify</code>
+    </li>
+    <li>
+      <code>options</code>
+    </li>
+    <li>
+      <code>patch</code>
+    </li>
+    <li>
+      <code>post</code>
+    </li>
+  </ul>
+  <ul>
+    <li>
+      <code>purge</code>
+    </li>
+    <li>
+      <code>put</code>
+    </li>
+    <li>
+      <code>report</code>
+    </li>
+    <li>
+      <code>search</code>
+    </li>
+    <li>
+      <code>subscribe</code>
+    </li>
+    <li>
+      <code>trace</code>
+    </li>
+    <li>
+      <code>unlock</code>
+    </li>
+    <li>
+      <code>unsubscribe</code>
+    </li>
+  </ul>
+</div>
+
+The API documentation has explicit entries only for the most popular HTTP methods `app.get()`,
+`app.post()`, `app.put()`, and `app.delete()`.
+However, the other methods listed above work in exactly the same way.
+
+To route methods that translate to invalid JavaScript variable names, use the bracket notation. For example, `app['m-search']('/', function ...`.
+
+<Alert type="info">
+
+The `app.get()` function is automatically called for the HTTP `HEAD` method in addition to the
+`GET` method if `app.head()` was not called for the path before `app.get()`.
+
+</Alert>
+
+The method, `app.all()`, is not derived from any HTTP method and loads middleware at
+the specified path for _all_ HTTP request methods.
+For more information, see [app.all](#appallpath-callback--callback-).
+
+For more information on routing, see the [routing guide](/en/guide/routing).
+
+### app.param([name], callback)
+
+Add callback triggers to [route parameters](/en/guide/routing#route-parameters), where `name` is the name of the parameter or an array of them, and `callback` is the callback function. The parameters of the callback function are the request object, the response object, the next middleware, the value of the parameter and the name of the parameter, in that order.
+
+If `name` is an array, the `callback` trigger is registered for each parameter declared in it, in the order in which they are declared. Furthermore, for each declared parameter except the last one, a call to `next` inside the callback will call the callback for the next declared parameter. For the last parameter, a call to `next` will call the next middleware in place for the route currently being processed, just like it would if `name` were just a string.
+
+For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
+
+```js
+app.param('user', function (req, res, next, id) {
+  // try to get the user details from the User model and attach it to the request object
+  User.find(id, function (err, user) {
+    if (err) {
+      next(err);
+    } else if (user) {
+      req.user = user;
+      next();
+    } else {
+      next(new Error('failed to load user'));
+    }
+  });
+});
+```
+
+Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `app` will be triggered only by route parameters defined on `app` routes.
+
+All param callbacks will be called before any handler of any route in which the param occurs, and they will each be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
+
+```js
+app.param('id', function (req, res, next, id) {
+  console.log('CALLED ONLY ONCE');
+  next();
+});
+
+app.get('/user/:id', function (req, res, next) {
+  console.log('although this matches');
+  next();
+});
+
+app.get('/user/:id', function (req, res) {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42`, the following is printed:
+
+```
+CALLED ONLY ONCE
+although this matches
+and this matches too
+```
+
+```js
+app.param(['id', 'page'], function (req, res, next, value) {
+  console.log('CALLED ONLY ONCE with', value);
+  next();
+});
+
+app.get('/user/:id/:page', function (req, res, next) {
+  console.log('although this matches');
+  next();
+});
+
+app.get('/user/:id/:page', function (req, res) {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42/3`, the following is printed:
+
+```
+CALLED ONLY ONCE with 42
+CALLED ONLY ONCE with 3
+although this matches
+and this matches too
+```
+
+<Alert type="warning">
+
+The following section describes `app.param(callback)`, which is deprecated as of v4.11.0.
+
+</Alert>
+
+The behavior of the `app.param(name, callback)` method can be altered entirely by passing only a function to `app.param()`. This function is a custom implementation of how `app.param(name, callback)` should behave - it accepts two parameters and must return a middleware.
+
+The first parameter of this function is the name of the URL parameter that should be captured, the second parameter can be any JavaScript object which might be used for returning the middleware implementation.
+
+The middleware returned by the function decides the behavior of what happens when a URL parameter is captured.
+
+In this example, the `app.param(name, callback)` signature is modified to `app.param(name, accessId)`. Instead of accepting a name and a callback, `app.param()` will now accept a name and a number.
+
+```js
+var express = require('express');
+var app = express();
+
+// customizing the behavior of app.param()
+app.param(function (param, option) {
+  return function (req, res, next, val) {
+    if (val === option) {
+      next();
+    } else {
+      next('route');
+    }
+  };
+});
+
+// using the customized app.param()
+app.param('id', 1337);
+
+// route to trigger the capture
+app.get('/user/:id', function (req, res) {
+  res.send('OK');
+});
+
+app.listen(3000, function () {
+  console.log('Ready');
+});
+```
+
+In this example, the `app.param(name, callback)` signature remains the same, but instead of a middleware callback, a custom data type checking function has been defined to validate the data type of the user id.
+
+```js
+app.param(function (param, validator) {
+  return function (req, res, next, val) {
+    if (validator(val)) {
+      next();
+    } else {
+      next('route');
+    }
+  };
+});
+
+app.param('id', function (candidate) {
+  return !isNaN(parseFloat(candidate)) && isFinite(candidate);
+});
+```
+
+<Alert type="info">
+The '`.`' character can't be used to capture a character in your capturing regexp. For example you can't use `'/user-.+/'` to capture `'users-gami'`, use `[\s\S]` or `[\w\W]` instead (as in `'/user-[\s\S]+/'`.
+
+Examples:
+
+```js
+// captures '1-a_6' but not '543-azser-sder'
+router.get('/[0-9]+-[[\w]]*', function (req, res, next) {
+  next();
+});
+
+// captures '1-a_6' and '543-az(ser"-sder' but not '5-a s'
+router.get('/[0-9]+-[[\S]]*', function (req, res, next) {
+  next();
+});
+
+// captures all (equivalent to '.*')
+router.get('[[\s\S]]*', function (req, res, next) {
+  next();
+});
+```
+
+</Alert>
+
+### app.path()
+
+Returns the canonical path of the app, a string.
+
+```js
+var app = express();
+var blog = express();
+var blogAdmin = express();
+
+app.use('/blog', blog);
+blog.use('/admin', blogAdmin);
+
+console.dir(app.path()); // ''
+console.dir(blog.path()); // '/blog'
+console.dir(blogAdmin.path()); // '/blog/admin'
+```
+
+The behavior of this method can become very complicated in complex cases of mounted apps:
+it is usually better to use [req.baseUrl](#req.baseUrl) to get the canonical path of the app.
+
+### app.post(path, callback [, callback ...])
+
+Routes HTTP POST requests to the specified path with the specified callback functions.
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Example
+
+```js
+app.post('/', function (req, res) {
+  res.send('POST request to homepage');
+});
+```
+
+### app.put(path, callback [, callback ...])
+
+Routes HTTP PUT requests to the specified path with the specified callback functions.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Example
+
+```js
+app.put('/', function (req, res) {
+  res.send('PUT request to homepage');
+});
+```
+
+### app.render(view, [locals], callback)
+
+Returns the rendered HTML of a view via the `callback` function. It accepts an optional parameter
+that is an object containing local variables for the view. It is like [res.render()](#res.render),
+except it cannot send the rendered view to the client on its own.
+
+<Alert type="info">
+
+Think of `app.render()` as a utility function for generating rendered view strings. Internally
+`res.render()` uses `app.render()` to render views.
+
+</Alert>
+
+<Alert type="warning">
+
+The `view` argument performs file system operations like reading a file from disk and evaluating
+Node.js modules, and as so for security reasons should not contain input from the end-user.
+
+</Alert>
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+<Alert type="alert">
+
+The local variable `cache` is reserved for enabling view cache. Set it to `true`, if you want to
+cache view during development; view caching is enabled in production by default.
+
+</Alert>
+
+```js
+app.render('email', function (err, html) {
+  // ...
+});
+
+app.render('email', { name: 'Tobi' }, function (err, html) {
+  // ...
+});
+```
+
+### app.route(path)
+
+Returns an instance of a single route, which you can then use to handle HTTP verbs with optional middleware.
+Use `app.route()` to avoid duplicate route names (and thus typo errors).
+
+```js
+var app = express();
+
+app
+  .route('/events')
+  .all(function (req, res, next) {
+    // runs for all HTTP verbs first
+    // think of it as route specific middleware!
+  })
+  .get(function (req, res, next) {
+    res.json({});
+  })
+  .post(function (req, res, next) {
+    // maybe add a new event...
+  });
+```
+
+### app.set(name, value)
+
+Assigns setting `name` to `value`. You may store any value that you want,
+but certain names can be used to configure the behavior of the server. These
+special names are listed in the [app settings table](#application-settings).
+
+Calling `app.set('foo', true)` for a Boolean property is the same as calling
+`app.enable('foo')`. Similarly, calling `app.set('foo', false)` for a Boolean
+property is the same as calling `app.disable('foo')`.
+
+Retrieve the value of a setting with [`app.get()`](#appgetname).
+
+```js
+app.set('title', 'My Site');
+app.get('title'); // "My Site"
+```
+
+#### Application Settings
+
+The following table lists application settings.
+
+Note that sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value; these are explicitly noted in the table below.
+
+Exceptions: Sub-apps will inherit the value of `trust proxy` even though it has a default value (for backward-compatibility);
+Sub-apps will not inherit the value of `view cache` in production (when `NODE_ENV` is "production").
+
+| Property                 | Type            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Default                                                                                             |
+| ------------------------ | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| `case sensitive routing` | Boolean         | Enable case sensitivity. When enabled, "/Foo" and "/foo" are different routes. When disabled, "/Foo" and "/foo" are treated the same. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | N/A (undefined)                                                                                     |
+| `env`                    | String          | Environment mode. Be sure to set to "production" in a production environment; see [Production best practices: performance and reliability](/en/advanced/best-practice-performance#env).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `process.env.NODE_ENV` (`NODE_ENV` environment variable) or "development" if `NODE_ENV` is not set. |
+| `etag`                   | Varied          | Set the ETag response header. For possible values, see the `etag` options table below. [More about the HTTP ETag header](http://en.wikipedia.org/wiki/HTTP_ETag).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | `weak`                                                                                              |
+| `jsonp callback name`    | String          | Specifies the default JSONP callback name.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | "callback"                                                                                          |
+| `json escape`            | Boolean         | Enable escaping JSON responses from the `res.json`, `res.jsonp`, and `res.send` APIs. This will escape the characters `<`, `>`, and `&` as Unicode escape sequences in JSON. The purpose of this is to assist with [mitigating certain types of persistent XSS attacks](https://blog.mozilla.org/security/2017/07/18/web-service-audits-firefox-accounts/) when clients sniff responses for HTML. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `json replacer`          | Varied          | The ['replacer' argument used by `JSON.stringify`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_replacer_parameter). **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | N/A (undefined)                                                                                     |
+| `json spaces`            | Varied          | The ['space' argument used by `JSON.stringify`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_space_argument). This is typically set to the number of spaces to use to indent prettified JSON. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `query parser`           | Varied          | Disable query parsing by setting the value to `false`, or set the query parser to use either "simple" or "extended" or a custom query string parsing function. The simple query parser is based on Node's native query parser, [querystring](http://nodejs.org/api/querystring.html). The extended query parser is based on [qs](https://www.npmjs.org/package/qs). A custom query string parsing function will receive the complete query string, and must return an object of query keys and their values.                                                                                                                                                                                                                                                                                                                                   | "extended"                                                                                          |
+| `strict routing`         | Boolean         | Enable strict routing. When enabled, the router treats "/foo" and "/foo/" as different. Otherwise, the router treats "/foo" and "/foo/" as the same. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | N/A (undefined)                                                                                     |
+| `subdomain offset`       | Number          | The number of dot-separated parts of the host to remove to access subdomain.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 2                                                                                                   |
+| `trust proxy`            | Varied          | Indicates the app is behind a front-facing proxy, and to use the `X-Forwarded-*` headers to determine the connection and the IP address of the client. NOTE: `X-Forwarded-*` headers are easily spoofed and the detected IP addresses are unreliable. When enabled, Express attempts to determine the IP address of the client connected through the front-facing proxy, or series of proxies. The `req.ips` property, then contains an array of IP addresses the client is connected through. To enable it, use the values described in the trust proxy options table below. The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.org/package/proxy-addr) package. For more information, see its documentation. **NOTE**: Sub-apps _will_ inherit the value of this setting, even though it has a default value. | `false` (disabled)                                                                                  |
+| `views`                  | String or Array | A directory or an array of directories for the application's views. If an array, the views are looked up in the order they occur in the array.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | `process.cwd() + '/views'`                                                                          |
+| `view cache`             | Boolean         | Enables view template compilation caching. **NOTE**: Sub-apps will not inherit the value of this setting in production (when `NODE_ENV` is "production").                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | `true` in production, otherwise undefined.                                                          |
+| `view engine`            | String          | The default engine extension to use when omitted. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `x-powered-by`           | Boolean         | Enables the "X-Powered-By: Express" HTTP header.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | `true`                                                                                              |
+
+#### Options for `trust proxy` setting
+
+Read [Express behind proxies](/en/guide/behind-proxies) for more information.
+
+**Boolean**: If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-*` header. If `false`, the app is understood as directly facing the Internet and the client's IP address is derived from `req.connection.remoteAddress`. This is the default setting.
+
+**String / String containing comma-separated values / Array of strings**: An IP address, subnet, or an array of IP addresses, and subnets to trust. Pre-configured subnet names are:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Set IP addresses in any of the following ways:
+
+Specify a single subnet:
+
+```js
+app.set('trust proxy', 'loopback');
+```
+
+Specify a subnet and an address:
+
+```js
+app.set('trust proxy', 'loopback, 123.123.123.123');
+```
+
+Specify multiple subnets as CSV:
+
+```js
+app.set('trust proxy', 'loopback, linklocal, uniquelocal');
+```
+
+Specify multiple subnets as an array:
+
+```js
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']);
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address.
+
+**Number**: Trust the *n*th hop from the front-facing proxy server as the client.
+
+**Function**: Custom trust implementation. Use this only if you know what you are doing.
+
+```js
+app.set('trust proxy', function (ip) {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+#### Options for `etag` setting
+
+**NOTE**: These settings apply only to dynamic files, not static files. The `express.static` middleware ignores these settings.
+
+The ETag functionality is implemented using the [etag](https://www.npmjs.org/package/etag) package. For more information, see its documentation.
+
+| Type     | Value                                                                                    |
+| -------- | ---------------------------------------------------------------------------------------- |
+| Boolean  | `true` enables weak ETag. This is the default setting. `false` disables ETag altogether. |
+| String   | If "strong", enables strong ETag. If "weak", enables weak ETag.                          |
+| Function | Custom ETag function implementation. Use this only if you know what you are doing.       |
+
+```js
+app.set('etag', function (body, encoding) {
+  return generateHash(body, encoding); // consider the function is defined
+});
+```
+
+### app.use([path,] callback [, callback...])
+
+Mounts the specified [middleware](/en/guide/using-middleware) function or functions
+at the specified path:
+the middleware function is executed when the base of the requested path matches `path`.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Default           |
+| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
+| `path`     | The path for which the middleware function is invoked; can be any of: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array of combinations of any of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | `'/'` (root path) |
+| `callback` | Callback functions; can be: a middleware function, a series of middleware functions (separated by commas), an array of middleware functions, or a combination of all of the above. You can provide multiple callback functions that behave just like middleware, except that these callbacks can invoke `next('route')` to bypass the remaining route callback(s). You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there is no reason to proceed with the current route. Since [router](#router) and [app](#application) implement the middleware interface, you can use them as you would any other middleware function. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | None              |
+
+#### Description
+
+A route will match any path that follows its path immediately with a "`/`".
+For example: `app.use('/apple', ...)` will match "/apple", "/apple/images",
+"/apple/images/news", and so on.
+
+Since `path` defaults to "/", middleware mounted without a path will be executed for every request to the app.
+For example, this middleware function will be executed for _every_ request to the app:
+
+```js
+app.use(function (req, res, next) {
+  console.log('Time: %d', Date.now());
+  next();
+});
+```
+
+<Alert type="info">
+**NOTE**
+
+Sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value.
+
+For details, see [Application settings](#application-settings).
+
+</Alert>
+
+Middleware functions are executed sequentially, therefore the order of middleware inclusion is important.
+
+```js
+// this middleware will not allow the request to go beyond it
+app.use(function (req, res, next) {
+  res.send('Hello World');
+});
+
+// requests will never reach this route
+app.get('/', function (req, res) {
+  res.send('Welcome');
+});
+```
+
+**Error-handling middleware**
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors. For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`):
+
+```js
+app.use(function (err, req, res, next) {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+#### Path examples
+
+The following table provides some simple examples of valid `path` values for
+mounting middleware.
+
+**Path**: Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
+
+```js
+app.use('/abcd', function (req, res, next) {
+  next();
+});
+```
+
+**Path Pattern**: This will match paths starting with `/abcd` and `/abd`:
+
+```js
+app.use('/abc?d', function (req, res, next) {
+  next();
+});
+```
+
+This will match paths starting with `/abcd`, `/abbcd`, `/abbbbbcd`, and so on:
+
+```js
+app.use('/ab+cd', function (req, res, next) {
+  next();
+});
+```
+
+This will match paths starting with `/abcd`, `/abxcd`, `/abFOOcd`, `/abbArcd`, and so on:
+
+```js
+app.use('/ab*cd', function (req, res, next) {
+  next();
+});
+```
+
+This will match paths starting with `/ad` and `/abcd`:
+
+```js
+app.use('/a(bc)?d', function (req, res, next) {
+  next();
+});
+```
+
+**Regular Expression**: This will match paths starting with `/abc` and `/xyz`:
+
+```js
+app.use(/\/abc|\/xyz/, function (req, res, next) {
+  next();
+});
+```
+
+**Array**: This will match paths starting with `/abcd`, `/xyza`, `/lmn`, and `/pqr`:
+
+```js
+app.use(['/abcd', '/xyza', /\/lmn|\/pqr/], function (req, res, next) {
+  next();
+});
+```
+
+#### Middleware callback function examples
+
+The following table provides some simple examples of middleware functions that
+can be used as the `callback` argument to `app.use()`, `app.METHOD()`, and `app.all()`.
+
+**Single Middleware**: You can define and mount a middleware function locally.
+
+```js
+app.use(function (req, res, next) {
+  next();
+});
+```
+
+A router is valid middleware.
+
+```js
+var router = express.Router();
+router.get('/', function (req, res, next) {
+  next();
+});
+app.use(router);
+```
+
+An Express app is valid middleware.
+
+```js
+var subApp = express();
+subApp.get('/', function (req, res, next) {
+  next();
+});
+app.use(subApp);
+```
+
+**Series of Middleware**: You can specify more than one middleware function at the same mount path.
+
+```js
+var r1 = express.Router();
+r1.get('/', function (req, res, next) {
+  next();
+});
+
+var r2 = express.Router();
+r2.get('/', function (req, res, next) {
+  next();
+});
+
+app.use(r1, r2);
+```
+
+**Array**: Use an array to group middleware logically.
+
+```js
+var r1 = express.Router();
+r1.get('/', function (req, res, next) {
+  next();
+});
+
+var r2 = express.Router();
+r2.get('/', function (req, res, next) {
+  next();
+});
+
+app.use([r1, r2]);
+```
+
+**Combination**: You can combine all the above ways of mounting middleware.
+
+```js
+function mw1(req, res, next) {
+  next();
+}
+function mw2(req, res, next) {
+  next();
+}
+
+var r1 = express.Router();
+r1.get('/', function (req, res, next) {
+  next();
+});
+
+var r2 = express.Router();
+r2.get('/', function (req, res, next) {
+  next();
+});
+
+var subApp = express();
+subApp.get('/', function (req, res, next) {
+  next();
+});
+
+app.use(mw1, [mw2, r1, r2], subApp);
+```
+
+Following are some examples of using the [express.static](/en/guide/using-middleware#middleware.built-in)
+middleware in an Express app.
+
+Serve static content for the app from the "public" directory in the application directory:
+
+```js
+// GET /style.css etc
+app.use(express.static(path.join(__dirname, 'public')));
+```
+
+Mount the middleware at "/static" to serve static content only when their request path is prefixed with "/static":
+
+```js
+// GET /static/style.css etc.
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Disable logging for static content requests by loading the logger middleware after the static middleware:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(logger());
+```
+
+Serve static files from multiple directories, but give precedence to "./public" over the others:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(express.static(path.join(__dirname, 'files')));
+app.use(express.static(path.join(__dirname, 'uploads')));
+```
diff --git a/src/content/api/4x/api/express/index.mdx b/src/content/api/4x/api/express/index.mdx
new file mode 100644
index 0000000000..51064c62a7
--- /dev/null
+++ b/src/content/api/4x/api/express/index.mdx
@@ -0,0 +1,315 @@
+---
+title: Express Object
+description: Learn about the methods available on the top-level Express object.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Creates an Express application. The `express()` function is a top-level function exported by the `express` module.
+
+```js
+var express = require('express');
+var app = express();
+```
+
+## Methods
+
+### express.json([options])
+
+<Alert type="info">This middleware is available in Express v4.16.0 onwards.</Alert>
+
+This is a built-in middleware function in Express. It parses incoming requests
+with JSON payloads and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that only parses JSON and only looks at requests where
+the `Content-Type` header matches the `type` option. This parser accepts any
+Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+<div class="table-scroller" markdown="1">
+
+The following table describes the properties of the optional `options` object.
+
+| Property  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Type     | Default              |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------------------- |
+| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                        | Boolean  | `true`               |
+| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                     | Mixed    | `"100kb"`            |
+| `reviver` | The `reviver` option is passed directly to `JSON.parse` as the second argument. You can find more information on this argument [in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter).                                                                                                                                                                                                                | Function | `null`               |
+| `strict`  | Enables or disables only accepting arrays and objects; when disabled will accept anything `JSON.parse` accepts.                                                                                                                                                                                                                                                                                                                                                                                                                | Boolean  | `true`               |
+| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `json`), a mime type (like `application/json`), or a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/json"` |
+| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                    | Function | `undefined`          |
+
+</div>
+
+### express.raw([options])
+
+<Alert type="info">This middleware is available in Express v4.17.0 onwards.</Alert>
+
+This is a built-in middleware function in Express. It parses incoming request
+payloads into a `Buffer` and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that parses all bodies as a `Buffer` and only looks at requests
+where the `Content-Type` header matches the `type` option. This parser accepts
+any Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` `Buffer` containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.toString()` may fail
+in multiple ways, for example stacking multiple parsers `req.body` may be from a different parser.
+Testing that `req.body` is a `Buffer` before calling buffer methods is recommended.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Type     | Default                      |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------- |
+| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                                      | Boolean  | `true`                       |
+| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                                   | Mixed    | `"100kb"`                    |
+| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `bin`), a mime type (like `application/octet-stream`), or a mime type with a wildcard (like `*/*` or `application/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/octet-stream"` |
+| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                                  | Function | `undefined`                  |
+
+</div>
+
+### express.Router([options])
+
+Creates a new [router](#router) object.
+
+```js
+var router = express.Router([options]);
+```
+
+The optional `options` parameter specifies the behavior of the router.
+
+<div class="table-scroller" markdown="1">
+
+| Property        | Description                                                                                                                                           | Default                                                                     | Availability |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ------------ |
+| `caseSensitive` | Enable case sensitivity.                                                                                                                              | Disabled by default, treating "/Foo" and "/foo" as the same.                |              |
+| `mergeParams`   | Preserve the `req.params` values from the parent router. If the parent and the child have conflicting param names, the child's value take precedence. | `false`                                                                     | 4.5.0+       |
+| `strict`        | Enable strict routing.                                                                                                                                | Disabled by default, "/foo" and "/foo/" are treated the same by the router. | &nbsp;       |
+
+</div>
+
+You can add middleware and HTTP method routes (such as `get`, `put`, `post`, and
+so on) to `router` just like an application.
+
+For more information, see [Router](#router).
+
+### express.static(root, [options])
+
+This is a built-in middleware function in Express.
+It serves static files and is based on [serve-static](/en/resources/middleware/serve-static).
+
+<Alert type="info">
+
+For best results, [use a reverse
+proxy](/en/advanced/best-practice-performance#use-a-reverse-proxy) cache to improve performance of
+serving static assets.
+
+</Alert>
+
+The `root` argument specifies the root directory from which to serve static assets.
+The function determines the file to serve by combining `req.url` with the provided `root` directory.
+When a file is not found, instead of sending a 404 response, it calls `next()`
+to move on to the next middleware, allowing for stacking and fall-backs.
+
+The following table describes the properties of the `options` object.
+See also the [example below](#example-of-expressstatic).
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Type     | Default      |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `dotfiles`     | Determines how dotfiles (files or directories that begin with a dot ".") are treated. <br/><br/>See [dotfiles](#dotfiles) below.                                                                                                                                                                                                   | String   | `undefined`  |
+| `etag`         | Enable or disable etag generation <br/><br/>NOTE: `express.static` always sends weak ETags.                                                                                                                                                                                                                                        | Boolean  | `true`       |
+| `extensions`   | Sets file extension fallbacks: If a file is not found, search for files with the specified extensions and serve the first one found. Example: `['html', 'htm']`.                                                                                                                                                                   | Mixed    | `false`      |
+| `fallthrough`  | Let client errors fall-through as unhandled requests, otherwise forward a client error. <br/><br/>See [fallthrough](#fallthrough) below.                                                                                                                                                                                           | Boolean  | `true`       |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | Boolean  | `false`      |
+| `index`        | Sends the specified directory index file. Set to `false` to disable directory indexing.                                                                                                                                                                                                                                            | Mixed    | "index.html" |
+| `lastModified` | Set the `Last-Modified` header to the last modified date of the file on the OS.                                                                                                                                                                                                                                                    | Boolean  | `true`       |
+| `maxAge`       | Set the max-age property of the Cache-Control header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms).                                                                                                                                                                                                 | Number   | 0            |
+| `redirect`     | Redirect to trailing "/" when the pathname is a directory.                                                                                                                                                                                                                                                                         | Boolean  | `true`       |
+| `setHeaders`   | Function for setting HTTP headers to serve with the file. <br/><br/>See [setHeaders](#setheaders) below.                                                                                                                                                                                                                           | Function |              |
+| `acceptRanges` | Enable or disable accepting ranged requests. Disabling this will not send the `Accept-Ranges` header and will ignore the contents of the Range request header.                                                                                                                                                                     | Boolean  | true         |
+| `cacheControl` | Enable or disable setting the `Cache-Control` response header. Disabling this will ignore the immutable and maxAge options.                                                                                                                                                                                                        | Boolean  | true         |
+
+</div>
+
+For more information, see [Serving static files in Express](/en/starter/static-files).
+and [Using middleware - Built-in middleware](/en/guide/using-middleware#middleware.built-in).
+
+#### dotfiles
+
+Possible values for this option are:
+
+- "allow" - No special treatment for dotfiles.
+- "deny" - Deny a request for a dotfile, respond with `403`, then call `next()`.
+- "ignore" - Act as if the dotfile does not exist, respond with `404`, then call `next()`.
+- `undefined` - Act as ignore, except that files in a directory that begins with a dot are **NOT** ignored.
+
+#### fallthrough
+
+When this option is `true`, client errors such as a bad request or a request to a non-existent
+file will cause this middleware to simply call `next()` to invoke the next middleware in the stack.
+When false, these errors (even 404s), will invoke `next(err)`.
+
+Set this option to `true` so you can map multiple physical directories
+to the same web address or for routes to fill in non-existent files.
+
+Use `false` if you have mounted this middleware at a path designed
+to be strictly a single file system directory, which allows for short-circuiting 404s
+for less overhead. This middleware will also reply to all methods.
+
+#### setHeaders
+
+For this option, specify a function to set custom response headers. Alterations to the headers must occur synchronously.
+
+The signature of the function is:
+
+```js
+fn(res, path, stat);
+```
+
+Arguments:
+
+- `res`, the [response object](#res).
+- `path`, the file path that is being sent.
+- `stat`, the `stat` object of the file that is being sent.
+
+#### Example of express.static
+
+Here is an example of using the `express.static` middleware function with an elaborate options object:
+
+```js
+var options = {
+  dotfiles: 'ignore',
+  etag: false,
+  extensions: ['htm', 'html'],
+  index: false,
+  maxAge: '1d',
+  redirect: false,
+  setHeaders: function (res, path, stat) {
+    res.set('x-timestamp', Date.now());
+  },
+};
+
+app.use(express.static('public', options));
+```
+
+### express.text([options])
+
+<Alert type="info">This middleware is available in Express v4.17.0 onwards.</Alert>
+
+This is a built-in middleware function in Express. It parses incoming request
+payloads into a string and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that parses all bodies as a string and only looks at requests
+where the `Content-Type` header matches the `type` option. This parser accepts
+any Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` string containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.trim()` may fail in
+multiple ways, for example stacking multiple parsers `req.body` may be from a different parser.
+Testing that `req.body` is a string before calling string methods is recommended.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Type     | Default        |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------------- |
+| `defaultCharset` | Specify the default character set for the text content if the charset is not specified in the `Content-Type` header of the request.                                                                                                                                                                                                                                                                                                                                                                                     | String   | `"utf-8"`      |
+| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                 | Boolean  | `true`         |
+| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                              | Mixed    | `"100kb"`      |
+| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `txt`), a mime type (like `text/plain`), or a mime type with a wildcard (like `*/*` or `text/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"text/plain"` |
+| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                             | Function | `undefined`    |
+
+</div>
+
+### express.urlencoded([options])
+
+<Alert type="info">This middleware is available in Express v4.16.0 onwards.</Alert>
+
+This is a built-in middleware function in Express. It parses incoming requests
+with urlencoded payloads and is based on [body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that only parses urlencoded bodies and only looks at
+requests where the `Content-Type` header matches the `type` option. This
+parser accepts only UTF-8 encoding of the body and supports automatic
+inflation of `gzip` and `deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or an empty object (`{}`) if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred. This object will contain key-value pairs, where the value can be
+a string or array (when `extended` is `false`), or any type (when `extended`
+is `true`).
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Type     | Default                               |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------- |
+| `extended`       | This option allows to choose between parsing the URL-encoded data with the `querystring` library (when `false`) or the `qs` library (when `true`). The "extended" syntax allows for rich objects and arrays to be encoded into the URL-encoded format, allowing for a JSON-like experience with URL-encoded. For more information, please [see the qs library](https://www.npmjs.org/package/qs#readme).                                                                                                                                                      | Boolean  | `true`                                |
+| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Boolean  | `true`                                |
+| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                                                    | Mixed    | `"100kb"`                             |
+| `parameterLimit` | This option controls the maximum number of parameters that are allowed in the URL-encoded data. If a request contains more parameters than this value, an error will be raised.                                                                                                                                                                                                                                                                                                                                                                               | Number   | `1000`                                |
+| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `urlencoded`), a mime type (like `application/x-www-form-urlencoded`), or a mime type with a wildcard (like `*/x-www-form-urlencoded`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/x-www-form-urlencoded"` |
+| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                                                   | Function | `undefined`                           |
+| `depth`          | Configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible.                                                                                                                                                                                                                                                                                        | Number   | `32`                                  |
+
+</div>
+
+<Alert type="alert">
+
+The `depth` option was added in Express v4.20.0. If you are using an earlier version, this option
+will not be available.
+
+</Alert>
diff --git a/src/content/api/4x/api/request/index.mdx b/src/content/api/4x/api/request/index.mdx
new file mode 100644
index 0000000000..14d389386d
--- /dev/null
+++ b/src/content/api/4x/api/request/index.mdx
@@ -0,0 +1,627 @@
+---
+title: Request Object
+description: The req object represents the HTTP request and has properties for the request query string, parameters, body, HTTP headers, and so on
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `req` object represents the HTTP request and has properties for the
+request query string, parameters, body, HTTP headers, and so on. In this documentation and by convention,
+the object is always referred to as `req` (and the HTTP response is `res`) but its actual name is determined
+by the parameters to the callback function in which you're working.
+
+For example:
+
+```js
+app.get('/user/:id', function (req, res) {
+  res.send('user ' + req.params.id);
+});
+```
+
+But you could just as well have:
+
+```js
+app.get('/user/:id', function (request, response) {
+  response.send('user ' + request.params.id);
+});
+```
+
+The `req` object is an enhanced version of Node's own request object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).
+
+## Properties
+
+The `req` object contains a number of properties that provide information about the HTTP request, such as headers, query parameters, and more.
+
+<Alert type="alert">
+
+In Express 4, `req.files` is no longer available on the `req` object by default. To access uploaded files
+on the `req.files` object, use multipart-handling middleware like [multer](https://www.npmjs.com/package/multer), [multiparty](https://www.npmjs.com/package/multiparty), [busboy](https://www.npmjs.com/package/busboy),
+[formidable](https://www.npmjs.com/package/formidable),
+or [pez](https://www.npmjs.com/package/pez).
+
+</Alert>
+
+### req.app
+
+This property holds a reference to the instance of the Express application that is using the middleware.
+
+If you follow the pattern in which you create a module that just exports a middleware function
+and `require()` it in your main file, then the middleware can access the Express instance via `req.app`
+
+For example:
+
+```js
+// index.js
+app.get('/viewdirectory', require('./mymiddleware.js'));
+```
+
+```js
+// mymiddleware.js
+module.exports = function (req, res) {
+  res.send('The views directory is ' + req.app.get('views'));
+};
+```
+
+### req.baseUrl
+
+The URL path on which a router instance was mounted.
+
+The `req.baseUrl` property is similar to the [mountpath](#app.mountpath) property of the `app` object,
+except `app.mountpath` returns the matched path pattern(s).
+
+For example:
+
+```js
+var greet = express.Router();
+
+greet.get('/jp', function (req, res) {
+  console.log(req.baseUrl); // /greet
+  res.send('Konnichiwa!');
+});
+
+app.use('/greet', greet); // load the router on '/greet'
+```
+
+Even if you use a path pattern or a set of path patterns to load the router,
+the `baseUrl` property returns the matched string, not the pattern(s). In the
+following example, the `greet` router is loaded on two path patterns.
+
+```js
+app.use(['/gre+t', '/hel{2}o'], greet); // load the router on '/gre+t' and '/hel{2}o'
+```
+
+When a request is made to `/greet/jp`, `req.baseUrl` is "/greet". When a request is
+made to `/hello/jp`, `req.baseUrl` is "/hello".
+
+### req.body
+
+Contains key-value pairs of data submitted in the request body.
+By default, it is `undefined`, and is populated when you use body-parsing middleware such
+as [`express.json()`](#express.json) or [`express.urlencoded()`](#express.urlencoded).
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The following example shows how to use body-parsing middleware to populate `req.body`.
+
+```js
+var express = require('express');
+
+var app = express();
+
+app.use(express.json()); // for parsing application/json
+app.use(express.urlencoded({ extended: true })); // for parsing application/x-www-form-urlencoded
+
+app.post('/profile', function (req, res, next) {
+  console.log(req.body);
+  res.json(req.body);
+});
+```
+
+### req.cookies
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property is an object that
+contains cookies sent by the request. If the request contains no cookies, it defaults to `{}`.
+
+```js
+// Cookie: name=tj
+console.dir(req.cookies.name);
+// => 'tj'
+```
+
+If the cookie has been signed, you have to use [req.signedCookies](#reqsignedcookies).
+
+For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
+
+### req.fresh
+
+When the response is still "fresh" in the client's cache `true` is returned, otherwise `false` is returned to indicate that the client cache is now stale and the full response should be sent.
+
+When a client sends the `Cache-Control: no-cache` request header to indicate an end-to-end reload request, this module will return `false` to make handling these requests transparent.
+
+Further details for how cache validation works can be found in the
+[HTTP/1.1 Caching Specification](https://tools.ietf.org/html/rfc7234).
+
+```js
+console.dir(req.fresh);
+// => true
+```
+
+### req.hostname
+
+Contains the hostname derived from the `Host` HTTP header.
+
+When the [`trust proxy` setting](/en/4x/api#trust.proxy.options.table)
+does not evaluate to `false`, this property will instead get the value
+from the `X-Forwarded-Host` header field. This header can be set by
+the client or by the proxy.
+
+If there is more than one `X-Forwarded-Host` header in the request, the
+value of the first header is used. This includes a single header with
+comma-separated values, in which the first value is used.
+
+<Alert type="info">
+
+Prior to Express v4.17.0, the `X-Forwarded-Host` could not contain multiple values or be present
+more than once.
+
+</Alert>
+
+```js
+// Host: "example.com:3000"
+console.dir(req.hostname);
+// => 'example.com'
+```
+
+### req.ip
+
+Contains the remote IP address of the request.
+
+When the [`trust proxy` setting](/en/4x/api#trust.proxy.options.table) does not evaluate to `false`,
+the value of this property is derived from the left-most entry in the
+`X-Forwarded-For` header. This header can be set by the client or by the proxy.
+
+```js
+console.dir(req.ip);
+// => '127.0.0.1'
+```
+
+### req.ips
+
+When the [`trust proxy` setting](/en/4x/api#trust.proxy.options.table) does not evaluate to `false`,
+this property contains an array of IP addresses
+specified in the `X-Forwarded-For` request header. Otherwise, it contains an
+empty array. This header can be set by the client or by the proxy.
+
+For example, if `X-Forwarded-For` is `client, proxy1, proxy2`, `req.ips` would be
+`["client", "proxy1", "proxy2"]`, where `proxy2` is the furthest downstream.
+
+### req.method
+
+Contains a string corresponding to the HTTP method of the request:
+`GET`, `POST`, `PUT`, and so on.
+
+### req.originalUrl
+
+<Alert type="alert">
+
+`req.url` is not a native Express property, it is inherited from Node's [http
+module](https://nodejs.org/api/http.html#http_message_url).
+
+</Alert>
+
+This property is much like `req.url`; however, it retains the original request URL,
+allowing you to rewrite `req.url` freely for internal routing purposes. For example,
+the "mounting" feature of [app.use()](#app.use) will rewrite `req.url` to strip the mount point.
+
+```js
+// GET /search?q=something
+console.dir(req.originalUrl);
+// => '/search?q=something'
+```
+
+`req.originalUrl` is available both in middleware and router objects, and is a
+combination of `req.baseUrl` and `req.url`. Consider following example:
+
+```js
+app.use('/admin', function (req, res, next) {
+  // GET 'http://www.example.com/admin/new?sort=desc'
+  console.dir(req.originalUrl); // '/admin/new?sort=desc'
+  console.dir(req.baseUrl); // '/admin'
+  console.dir(req.path); // '/new'
+  next();
+});
+```
+
+### req.params
+
+This property is an object containing properties mapped to the [named route "parameters"](/en/guide/routing#route-parameters). For example, if you have the route `/user/:name`, then the "name" property is available as `req.params.name`. This object defaults to `{}`.
+
+```js
+// GET /user/tj
+console.dir(req.params.name);
+// => 'tj'
+```
+
+When you use a regular expression for the route definition, capture groups are provided as integer keys using `req.params[n]`, where `n` is the n<sup>th</sup> capture group. This rule is applied to unnamed wild card matches with string routes such as `/file/*`:
+
+```js
+// GET /file/javascripts/jquery.js
+console.dir(req.params[0]);
+// => 'javascripts/jquery.js'
+```
+
+Named capturing groups in regular expressions behave like named route parameters. For example the group from `/^\/file\/(?<path>.*)$/` expression is available as `req.params.path`.
+
+If you need to make changes to a key in `req.params`, use the [app.param](/en/4x/api#app.param) handler. Changes are applicable only to [parameters](/en/guide/routing#route-parameters) already defined in the route path.
+
+Any changes made to the `req.params` object in a middleware or route handler will be reset.
+
+<Alert type="info">
+
+Express automatically decodes the values in `req.params` (using `decodeURIComponent`).
+
+</Alert>
+
+### req.path
+
+Contains the path part of the request URL.
+
+```js
+// example.com/users?sort=desc
+console.dir(req.path);
+// => '/users'
+```
+
+<Alert type="info">
+
+When called from a middleware, the mount point is not included in `req.path`. See
+[app.use()](/en/4x/api#app.use) for more details.
+
+</Alert>
+
+### req.protocol
+
+Contains the request protocol string: either `http` or (for TLS requests) `https`.
+
+When the [`trust proxy` setting](#trust.proxy.options.table) does not evaluate to `false`,
+this property will use the value of the `X-Forwarded-Proto` header field if present.
+This header can be set by the client or by the proxy.
+
+```js
+console.dir(req.protocol);
+// => 'http'
+```
+
+### req.query
+
+This property is an object containing a property for each query string parameter in the route.
+When [query parser](/en/api/application/app-set#app.settings.table) is set to disabled, it is an empty object `{}`, otherwise it is the result of the configured query parser.
+
+<Alert type="warning">
+
+As `req.query`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.query.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The value of this property can be configured with the [query parser application setting](/en/api/application/app-set#app.settings.table) to work how your application needs it. A very popular query string parser is the [`qs` module](https://www.npmjs.org/package/qs), and this is used by default. The `qs` module is very configurable with many settings, and it may be desirable to use different settings than the default to populate `req.query`:
+
+```js
+var qs = require('qs');
+app.set('query parser', function (str) {
+  return qs.parse(str, {
+    /* custom options */
+  });
+});
+```
+
+Check out the [query parser application setting](/en/api/application/app-set#app.settings.table) documentation for other customization options.
+
+### req.res
+
+This property holds a reference to the <a href="#res">response object</a>
+that relates to this request object.
+
+### req.route
+
+Contains the currently-matched route, a string. For example:
+
+```js
+app.get('/user/:id?', function userIdHandler(req, res) {
+  console.log(req.route);
+  res.send('GET');
+});
+```
+
+Example output from the previous snippet:
+
+```
+{ path: '/user/:id?',
+  stack:
+   [ { handle: [Function: userIdHandler],
+       name: 'userIdHandler',
+       params: undefined,
+       path: undefined,
+       keys: [],
+       regexp: /^\/?$/i,
+       method: 'get' } ],
+  methods: { get: true } }
+```
+
+### req.secure
+
+A Boolean property that is true if a TLS connection is established. Equivalent to:
+
+```js
+console.dir(req.protocol === 'https');
+// => true
+```
+
+### req.signedCookies
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property
+contains signed cookies sent by the request, unsigned and ready for use. Signed cookies reside
+in a different object to show developer intent; otherwise, a malicious attack could be placed on
+`req.cookie` values (which are easy to spoof). Note that signing a cookie does not make it "hidden"
+or encrypted; but simply prevents tampering (because the secret used to sign is private).
+
+If no signed cookies are sent, the property defaults to `{}`.
+
+```js
+// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
+console.dir(req.signedCookies.user);
+// => 'tobi'
+```
+
+For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
+
+### req.stale
+
+Indicates whether the request is "stale," and is the opposite of `req.fresh`.
+For more information, see [req.fresh](#reqfresh).
+
+```js
+console.dir(req.stale);
+// => true
+```
+
+### req.subdomains
+
+An array of subdomains in the domain name of the request.
+
+```js
+// Host: "tobi.ferrets.example.com"
+console.dir(req.subdomains);
+// => ['ferrets', 'tobi']
+```
+
+The application property `subdomain offset`, which defaults to 2, is used for determining the
+beginning of the subdomain segments. To change this behavior, change its value
+using [app.set](/en/4x/api#app.set).
+
+### req.xhr
+
+A Boolean property that is `true` if the request's `X-Requested-With` header field is
+"XMLHttpRequest", indicating that the request was issued by a client library such as jQuery.
+
+```js
+console.dir(req.xhr);
+// => true
+```
+
+## Methods
+
+The `req` object also contains a number of methods that can be used to perform various tasks related to the HTTP request, such as checking the content type, retrieving header values, and more.
+
+### req.accepts(types)
+
+Checks if the specified content types are acceptable, based on the request's `Accept` HTTP header field.
+The method returns the best match, or if none of the specified content types is acceptable, returns
+`false` (in which case, the application should respond with `406 "Not Acceptable"`).
+
+The `type` value may be a single MIME type string (such as "application/json"),
+an extension name such as "json", a comma-delimited list, or an array. For a
+list or array, the method returns the _best_ match (if any).
+
+```js
+// Accept: text/html
+req.accepts('html');
+// => "html"
+
+// Accept: text/*, application/json
+req.accepts('html');
+// => "html"
+req.accepts('text/html');
+// => "text/html"
+req.accepts(['json', 'text']);
+// => "json"
+req.accepts('application/json');
+// => "application/json"
+
+// Accept: text/*, application/json
+req.accepts('image/png');
+req.accepts('png');
+// => false
+
+// Accept: text/*;q=.5, application/json
+req.accepts(['html', 'json']);
+// => "json"
+```
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsCharsets(charset [, ...])
+
+Returns the first accepted charset of the specified character sets,
+based on the request's `Accept-Charset` HTTP header field.
+If none of the specified charsets is accepted, returns `false`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsEncodings(encoding [, ...])
+
+Returns the first accepted encoding of the specified encodings,
+based on the request's `Accept-Encoding` HTTP header field.
+If none of the specified encodings is accepted, returns `false`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsLanguages([lang, ...])
+
+Returns the first accepted language of the specified languages,
+based on the request's `Accept-Language` HTTP header field.
+If none of the specified languages is accepted, returns `false`.
+
+If no `lang` argument is given, then `req.acceptsLanguages()`
+returns all languages from the HTTP `Accept-Language` header
+as an `Array`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+Express (4.x) source: [request.js line 179](https://github.com/expressjs/express/blob/4.x/lib/request.js#L179)
+
+Accepts (1.3) source: [index.js line 195](https://github.com/jshttp/accepts/blob/f69c19e459bd501e59fb0b1a40b7471bb578113a/index.js#L195)
+
+### req.get(field)
+
+Returns the specified HTTP request header field (case-insensitive match).
+The `Referrer` and `Referer` fields are interchangeable.
+
+```js
+req.get('Content-Type');
+// => "text/plain"
+
+req.get('content-type');
+// => "text/plain"
+
+req.get('Something');
+// => undefined
+```
+
+Aliased as `req.header(field)`.
+
+### req.is(type)
+
+Returns the matching content type if the incoming request's "Content-Type" HTTP header field
+matches the MIME type specified by the `type` parameter. If the request has no body, returns `null`.
+Returns `false` otherwise.
+
+```js
+// With Content-Type: text/html; charset=utf-8
+req.is('html');
+// => 'html'
+req.is('text/html');
+// => 'text/html'
+req.is('text/*');
+// => 'text/*'
+
+// When Content-Type is application/json
+req.is('json');
+// => 'json'
+req.is('application/json');
+// => 'application/json'
+req.is('application/*');
+// => 'application/*'
+
+// Using arrays
+// When Content-Type is application/json
+req.is(['json', 'html']);
+// => 'json'
+
+// Using multiple arguments
+// When Content-Type is application/json
+req.is('json', 'html');
+// => 'json'
+
+req.is('html');
+// => false
+req.is(['xml', 'yaml']);
+// => false
+req.is('xml', 'yaml');
+// => false
+```
+
+For more information, or if you have issues or concerns, see [type-is](https://github.com/expressjs/type-is).
+
+### req.param(name [, defaultValue])
+
+<Alert type="warning">
+
+Deprecated. Use either `req.params`, `req.body` or `req.query`, as applicable.
+
+</Alert>
+
+Returns the value of param `name` when present.
+
+```js
+// ?name=tobi
+req.param('name');
+// => "tobi"
+
+// POST name=tobi
+req.param('name');
+// => "tobi"
+
+// /user/tobi for /user/:name
+req.param('name');
+// => "tobi"
+```
+
+Lookup is performed in the following order:
+
+- `req.params`
+- `req.body`
+- `req.query`
+
+Optionally, you can specify `defaultValue` to set a default value if the parameter is not found in any of the request objects.
+
+<Alert type="warning">
+Direct access to `req.body`, `req.params`, and `req.query` should be favoured for clarity - unless you truly accept input from each object.
+
+Body-parsing middleware must be loaded for `req.param()` to work predictably. Refer [req.body](#reqbody) for details.
+
+</Alert>
+
+### req.range(size[, options])
+
+`Range` header parser.
+
+The `size` parameter is the maximum size of the resource.
+
+The `options` parameter is an object that can have the following properties.
+
+<div class="table-scroller" markdown="1">
+
+| Property  | Type    | Description                                                                                                                                                                           |
+| --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `combine` | Boolean | Specify if overlapping & adjacent ranges should be combined, defaults to `false`. When `true`, ranges will be combined and returned as if they were specified that way in the header. |
+
+</div>
+
+An array of ranges will be returned or negative numbers indicating an error parsing.
+
+- `-2` signals a malformed header string
+- `-1` signals an unsatisfiable range
+
+```js
+// parse header from request
+var range = req.range(1000);
+
+// the type of the range
+if (range.type === 'bytes') {
+  // the ranges
+  range.forEach(function (r) {
+    // do something with r.start and r.end
+  });
+}
+```
diff --git a/src/content/api/4x/api/response/index.mdx b/src/content/api/4x/api/response/index.mdx
new file mode 100644
index 0000000000..fa9559dab4
--- /dev/null
+++ b/src/content/api/4x/api/response/index.mdx
@@ -0,0 +1,783 @@
+---
+title: Response
+description: The res object represents the HTTP response that an Express app sends when it gets an HTTP request.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `res` object represents the HTTP response that an Express app sends when it gets an HTTP request.
+
+In this documentation and by convention,
+the object is always referred to as `res` (and the HTTP request is `req`) but its actual name is determined
+by the parameters to the callback function in which you're working.
+
+For example:
+
+```js
+app.get('/user/:id', function (req, res) {
+  res.send('user ' + req.params.id);
+});
+```
+
+But you could just as well have:
+
+```js
+app.get('/user/:id', function (request, response) {
+  response.send('user ' + request.params.id);
+});
+```
+
+The `res` object is an enhanced version of Node's own response object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
+
+## Properties
+
+### res.app
+
+This property holds a reference to the instance of the Express application that is using the middleware.
+
+`res.app` is identical to the [req.app](#req.app) property in the request object.
+
+### res.headersSent
+
+Boolean property that indicates if the app sent HTTP headers for the response.
+
+```js
+app.get('/', function (req, res) {
+  console.dir(res.headersSent); // false
+  res.send('OK');
+  console.dir(res.headersSent); // true
+});
+```
+
+### res.locals
+
+Use this property to set variables accessible in templates rendered with [res.render](#resrenderview-locals-callback).
+The variables set on `res.locals` are available within a single request-response cycle, and will not
+be shared between requests.
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+In order to keep local variables for use in template rendering between requests, use
+[app.locals](#app.locals) instead.
+
+This property is useful for exposing request-level information such as the request path name,
+authenticated user, user settings, and so on to templates rendered within the application.
+
+```js
+app.use(function (req, res, next) {
+  // Make `user` and `authenticated` available in templates
+  res.locals.user = req.user;
+  res.locals.authenticated = !req.user.anonymous;
+  next();
+});
+```
+
+### res.req
+
+This property holds a reference to the <a href="#req">request object</a>
+that relates to this response object.
+
+## Methods
+
+### res.append(field [, value])
+
+<Alert type="info">`res.append()` is supported by Express v4.11.0+</Alert>
+Appends the specified `value` to the HTTP response header `field`. If the header is not already set,
+it creates the header with the specified value. The `value` parameter can be a string or an array.
+
+<Alert type="info">
+
+calling `res.set()` after `res.append()` will reset the previously-set header value.
+
+</Alert>
+
+```js
+res.append('Link', ['<http://localhost/>', '<http://localhost:3000/>']);
+res.append('Set-Cookie', 'foo=bar; Path=/; HttpOnly');
+res.append('Warning', '199 Miscellaneous warning');
+```
+
+### res.attachment([filename])
+
+Sets the HTTP response `Content-Disposition` header field to "attachment". If a `filename` is given,
+then it sets the Content-Type based on the extension name via `res.type()`,
+and sets the `Content-Disposition` "filename=" parameter.
+
+```js
+res.attachment();
+// Content-Disposition: attachment
+
+res.attachment('path/to/logo.png');
+// Content-Disposition: attachment; filename="logo.png"
+// Content-Type: image/png
+```
+
+### res.clearCookie(name [, options])
+
+Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
+This instructs the client that the cookie has expired and is no longer valid. For more information
+about available `options`, see [res.cookie()](#rescookiename-value--options).
+
+<Alert type="warning">
+
+If the `maxAge` or `expires` options are set, the cookie may not be cleared depending on the time
+values provided, as Express does not ignore these options. It is therefore recommended to omit
+these options when calling this method. Passing these two options has been deprecated since
+Express v4.20.0.
+
+</Alert>
+
+<Alert type="alert">
+
+Web browsers and other compliant clients will only clear the cookie if the given `options` is
+identical to those given to [res.cookie()](#rescookiename-value--options), excluding `expires` and `maxAge`.
+
+</Alert>
+
+```js
+res.cookie('name', 'tobi', { path: '/admin' });
+res.clearCookie('name', { path: '/admin' });
+```
+
+### res.cookie(name, value [, options])
+
+Sets cookie `name` to `value`. The `value` parameter may be a string or object converted to JSON.
+
+The `options` parameter is an object that can have the following properties.
+
+<div class="table-scroller" markdown="1">
+
+| Property      | Type              | Description                                                                                                                                                                                                                                 |
+| ------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `domain`      | String            | Domain name for the cookie. Defaults to the domain name of the app.                                                                                                                                                                         |
+| `encode`      | Function          | A synchronous function used for cookie value encoding. Defaults to `encodeURIComponent`.                                                                                                                                                    |
+| `expires`     | Date              | Expiry date of the cookie in GMT. If not specified or set to 0, creates a session cookie.                                                                                                                                                   |
+| `httpOnly`    | Boolean           | Flags the cookie to be accessible only by the web server.                                                                                                                                                                                   |
+| `maxAge`      | Number            | Convenient option for setting the expiry time relative to the current time in milliseconds.                                                                                                                                                 |
+| `path`        | String            | Path for the cookie. Defaults to "/".                                                                                                                                                                                                       |
+| `partitioned` | Boolean           | Indicates that the cookie should be stored using partitioned storage. See [Cookies Having Independent Partitioned State (CHIPS)](https://developer.mozilla.org/en-US/docs/Web/Privacy/Partitioned_cookies) for more details.                |
+| `priority`    | String            | Value of the "Priority" **Set-Cookie** attribute.                                                                                                                                                                                           |
+| `secure`      | Boolean           | Marks the cookie to be used with HTTPS only.                                                                                                                                                                                                |
+| `signed`      | Boolean           | Indicates if the cookie should be signed.                                                                                                                                                                                                   |
+| `sameSite`    | Boolean or String | Value of the "SameSite" **Set-Cookie** attribute. More information at [https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1](https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1). |
+
+</div>
+
+<Alert type="alert">
+
+All `res.cookie()` does is set the HTTP `Set-Cookie` header with the options provided. Any option
+not specified defaults to the value stated in [RFC 6265](http://tools.ietf.org/html/rfc6265).
+
+</Alert>
+
+For example:
+
+```js
+res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true });
+res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true });
+```
+
+You can set multiple cookies in a single response by calling `res.cookie` multiple times, for example:
+
+```js
+res
+  .status(201)
+  .cookie('access_token', 'Bearer ' + token, {
+    expires: new Date(Date.now() + 8 * 3600000), // cookie will be removed after 8 hours
+  })
+  .cookie('test', 'test')
+  .redirect(301, '/admin');
+```
+
+The `encode` option allows you to choose the function used for cookie value encoding.
+Does not support asynchronous functions.
+
+Example use case: You need to set a domain-wide cookie for another site in your organization.
+This other site (not under your administrative control) does not use URI-encoded cookie values.
+
+```js
+// Default encoding
+res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com' });
+// Result: 'some_cross_domain_cookie=http%3A%2F%2Fmysubdomain.example.com; Domain=example.com; Path=/'
+
+// Custom encoding
+res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', {
+  domain: 'example.com',
+  encode: String,
+});
+// Result: 'some_cross_domain_cookie=http://mysubdomain.example.com; Domain=example.com; Path=/;'
+```
+
+The `maxAge` option is a convenience option for setting "expires" relative to the current time in milliseconds.
+The following is equivalent to the second example above.
+
+```js
+res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true });
+```
+
+You can pass an object as the `value` parameter; it is then serialized as JSON and parsed by `bodyParser()` middleware.
+
+```js
+res.cookie('cart', { items: [1, 2, 3] });
+res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 });
+```
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this method also
+supports signed cookies. Simply include the `signed` option set to `true`.
+Then `res.cookie()` will use the secret passed to `cookieParser(secret)` to sign the value.
+
+```js
+res.cookie('name', 'tobi', { signed: true });
+```
+
+Later you may access this value through the [req.signedCookie](#req.signedCookies) object.
+
+### res.download(path [, filename] [, options] [, fn])
+
+Transfers the file at `path` as an "attachment". Typically, browsers will prompt the user for download.
+By default, the `Content-Disposition` header "filename=" parameter is derived from the `path` argument, but can be overridden with the `filename` parameter.
+If `path` is relative, then it will be based on the current working directory of the process or
+the `root` option, if provided.
+
+<Alert type="warning">
+This API provides access to data on the running file system. Ensure that either (a) the way in
+which the `path` argument was constructed is secure if it contains user input or (b) set the `root`
+option to the absolute path of a directory to contain access within.
+
+When the `root` option is provided, Express will validate that the relative path provided as
+`path` will resolve within the given `root` option.
+
+</Alert>
+
+The following table provides details on the `options` parameter.
+
+<Alert type="info">The optional `options` argument is supported by Express v4.16.0 onwards.</Alert>
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Default  | Availability |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `maxAge`       | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)                                                                                                                                                                                               | 0        | 4.16+        |
+| `root`         | Root directory for relative filenames.                                                                                                                                                                                                                                                                                             |          | 4.18+        |
+| `lastModified` | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.                                                                                                                                                                                                                        | Enabled  | 4.16+        |
+| `headers`      | Object containing HTTP headers to serve with the file. The header `Content-Disposition` will be overridden by the `filename` argument.                                                                                                                                                                                             |          | 4.16+        |
+| `dotfiles`     | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".                                                                                                                                                                                                                                                        | "ignore" | 4.16+        |
+| `acceptRanges` | Enable or disable accepting ranged requests.                                                                                                                                                                                                                                                                                       | `true`   | 4.16+        |
+| `cacheControl` | Enable or disable setting `Cache-Control` response header.                                                                                                                                                                                                                                                                         | `true`   | 4.16+        |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false`  | 4.16+        |
+
+</div>
+
+The method invokes the callback function `fn(err)` when the transfer is complete
+or when an error occurs. If the callback function is specified and an error occurs,
+the callback function must explicitly handle the response process either by
+ending the request-response cycle, or by passing control to the next route.
+
+```js
+res.download('/report-12345.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf', function (err) {
+  if (err) {
+    // Handle error, but keep in mind the response may be partially-sent
+    // so check res.headersSent
+  } else {
+    // decrement a download credit, etc.
+  }
+});
+```
+
+### res.end([data[, encoding]][, callback])
+
+Ends the response process. This method actually comes from Node core, specifically the [response.end() method of http.ServerResponse](https://nodejs.org/api/http.html#responseenddata-encoding-callback).
+
+Use to quickly end the response without any data. If you need to respond with data, instead use methods such as [res.send()](#ressendbody) and [res.json()](#resjsonbody).
+
+```js
+res.end();
+res.status(404).end();
+```
+
+### res.format(object)
+
+Performs content-negotiation on the `Accept` HTTP header on the request object, when present.
+It uses [req.accepts()](#req.accepts) to select a handler for the request, based on the acceptable
+types ordered by their quality values. If the header is not specified, the first callback is invoked.
+When no match is found, the server responds with 406 "Not Acceptable", or invokes the `default` callback.
+
+The `Content-Type` response header is set when a callback is selected. However, you may alter
+this within the callback using methods such as `res.set()` or `res.type()`.
+
+The following example would respond with `{ "message": "hey" }` when the `Accept` header field is set
+to "application/json" or "\*/json" (however if it is "\*/\*", then the response will be "hey").
+
+```js
+res.format({
+  'text/plain': function () {
+    res.send('hey');
+  },
+
+  'text/html': function () {
+    res.send('<p>hey</p>');
+  },
+
+  'application/json': function () {
+    res.send({ message: 'hey' });
+  },
+
+  default: function () {
+    // log the request and respond with 406
+    res.status(406).send('Not Acceptable');
+  },
+});
+```
+
+In addition to canonicalized MIME types, you may also use extension names mapped
+to these types for a slightly less verbose implementation:
+
+```js
+res.format({
+  text: function () {
+    res.send('hey');
+  },
+
+  html: function () {
+    res.send('<p>hey</p>');
+  },
+
+  json: function () {
+    res.send({ message: 'hey' });
+  },
+});
+```
+
+### res.get(field)
+
+Returns the HTTP response header specified by `field`.
+The match is case-insensitive.
+
+```js
+res.get('Content-Type');
+// => "text/plain"
+```
+
+### res.json([body])
+
+Sends a JSON response. This method sends a response (with the correct content-type) that is the parameter converted to a
+JSON string using [JSON.stringify()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify).
+
+The parameter can be any JSON type, including object, array, string, Boolean, number, or null,
+and you can also use it to convert other values to JSON.
+
+```js
+res.json(null);
+res.json({ user: 'tobi' });
+res.status(500).json({ error: 'message' });
+```
+
+### res.jsonp([body])
+
+Sends a JSON response with JSONP support. This method is identical to `res.json()`,
+except that it opts-in to JSONP callback support.
+
+```js
+res.jsonp(null);
+// => callback(null)
+
+res.jsonp({ user: 'tobi' });
+// => callback({ "user": "tobi" })
+
+res.status(500).jsonp({ error: 'message' });
+// => callback({ "error": "message" })
+```
+
+By default, the JSONP callback name is simply `callback`. Override this with the
+
+<a href="/api/application/app-settings/">jsonp callback name</a> setting.
+
+The following are some examples of JSONP responses using the same code:
+
+```js
+// ?callback=foo
+res.jsonp({ user: 'tobi' });
+// => foo({ "user": "tobi" })
+
+app.set('jsonp callback name', 'cb');
+
+// ?cb=foo
+res.status(500).jsonp({ error: 'message' });
+// => foo({ "error": "message" })
+```
+
+### res.links(links)
+
+Joins the `links` provided as properties of the parameter to populate the response's
+`Link` HTTP header field.
+
+For example, the following call:
+
+```js
+res.links({
+  next: 'http://api.example.com/users?page=2',
+  last: 'http://api.example.com/users?page=5',
+});
+```
+
+Yields the following results:
+
+```
+Link: <http://api.example.com/users?page=2>; rel="next",
+      <http://api.example.com/users?page=5>; rel="last"
+```
+
+### res.location(path)
+
+Sets the response `Location` HTTP header to the specified `path` parameter.
+
+```js
+res.location('/foo/bar');
+res.location('http://example.com');
+res.location('back');
+```
+
+<Alert type="info">
+
+`'back'` was deprecated in 4.21.0, use `req.get('Referrer') || '/'` as an argument instead.
+
+</Alert>
+
+A `path` value of "back" has a special meaning, it refers to the URL specified in the `Referer` header of the request. If the `Referer` header was not specified, it refers to "/".
+
+See also [Security best practices: Prevent open redirect
+vulnerabilities](http://expressjs.com/en/advanced/best-practice-security#prevent-open-redirects).
+
+<Alert type="warning">
+After encoding the URL, if not encoded already, Express passes the specified URL to the browser in the `Location` header,
+without any validation.
+
+Browsers take the responsibility of deriving the intended URL from the current URL
+or the referring URL, and the URL specified in the `Location` header; and redirect the user accordingly.
+
+</Alert>
+
+### res.redirect([status,] path)
+
+Redirects to the URL derived from the specified `path`, with specified `status`, a positive integer
+that corresponds to an [HTTP status code](https://www.rfc-editor.org/rfc/rfc9110#name-status-codes) .
+If not specified, `status` defaults to "302 "Found".
+
+```js
+res.redirect('/foo/bar');
+res.redirect('http://example.com');
+res.redirect(301, 'http://example.com');
+res.redirect('../login');
+```
+
+Redirects can be a fully-qualified URL for redirecting to a different site:
+
+```js
+res.redirect('http://google.com');
+```
+
+Redirects can be relative to the root of the host name. For example, if the
+application is on `http://example.com/admin/post/new`, the following
+would redirect to the URL `http://example.com/admin`:
+
+```js
+res.redirect('/admin');
+```
+
+Redirects can be relative to the current URL. For example,
+from `http://example.com/blog/admin/` (notice the trailing slash), the following
+would redirect to the URL `http://example.com/blog/admin/post/new`.
+
+```js
+res.redirect('post/new');
+```
+
+Redirecting to `post/new` from `http://example.com/blog/admin` (no trailing slash),
+will redirect to `http://example.com/blog/post/new`.
+
+If you found the above behavior confusing, think of path segments as directories
+(with trailing slashes) and files, it will start to make sense.
+
+Path-relative redirects are also possible. If you were on
+`http://example.com/admin/post/new`, the following would redirect to
+`http://example.com/admin/post`:
+
+```js
+res.redirect('..');
+```
+
+A `back` redirection redirects the request back to the [referer](http://en.wikipedia.org/wiki/HTTP_referer),
+defaulting to `/` when the referer is missing.
+
+```js
+res.redirect('back');
+```
+
+<Alert type="info">
+
+`back` redirect was deprecated in 4.21.0, use `req.get('Referrer') || '/'` as an argument instead.
+
+</Alert>
+
+See also [Security best practices: Prevent open redirect
+vulnerabilities](http://expressjs.com/en/advanced/best-practice-security#prevent-open-redirects).
+
+### res.render(view [, locals] [, callback])
+
+Renders a `view` and sends the rendered HTML string to the client.
+Optional parameters:
+
+- `locals`, an object whose properties define local variables for the view.
+- `callback`, a callback function. If provided, the method returns both the possible error and rendered string, but does not perform an automated response. When an error occurs, the method invokes `next(err)` internally.
+
+The `view` argument is a string that is the file path of the view file to render. This can be an absolute path, or a path relative to the `views` setting. If the path does not contain a file extension, then the `view engine` setting determines the file extension. If the path does contain a file extension, then Express will load the module for the specified template engine (via `require()`) and render it using the loaded module's `__express` function.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+<Alert type="warning">
+
+The `view` argument performs file system operations like reading a file from disk and evaluating
+Node.js modules, and as so for security reasons should not contain input from the end-user.
+
+</Alert>
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+<Alert type="alert">
+
+The local variable `cache` enables view caching. Set it to `true`, to cache the view during
+development; view caching is enabled in production by default.
+
+</Alert>
+
+```js
+// send the rendered view to the client
+res.render('index');
+
+// if a callback is specified, the rendered HTML string has to be sent explicitly
+res.render('index', function (err, html) {
+  res.send(html);
+});
+
+// pass a local variable to the view
+res.render('user', { name: 'Tobi' }, function (err, html) {
+  // ...
+});
+```
+
+### res.send([body])
+
+Sends the HTTP response.
+
+The `body` parameter can be a `Buffer` object, a `String`, an object, `Boolean`, or an `Array`.
+For example:
+
+```js
+res.send(Buffer.from('whoop'));
+res.send({ some: 'json' });
+res.send('<p>some html</p>');
+res.status(404).send('Sorry, we cannot find that!');
+res.status(500).send({ error: 'something blew up' });
+```
+
+This method performs many useful tasks for simple non-streaming responses:
+For example, it automatically assigns the `Content-Length` HTTP response header field
+(unless previously defined) and provides automatic HEAD and HTTP cache freshness support.
+
+When the parameter is a `Buffer` object, the method sets the `Content-Type`
+response header field to "application/octet-stream", unless previously defined as shown below:
+
+```js
+res.set('Content-Type', 'text/html');
+res.send(Buffer.from('<p>some html</p>'));
+```
+
+When the parameter is a `String`, the method sets the `Content-Type` to "text/html":
+
+```js
+res.send('<p>some html</p>');
+```
+
+When the parameter is an `Array` or `Object`, Express responds with the JSON representation:
+
+```js
+res.send({ user: 'tobi' });
+res.send([1, 2, 3]);
+```
+
+### res.sendFile(path [, options] [, fn])
+
+<Alert type="info">`res.sendFile()` is supported by Express v4.8.0 onwards.</Alert>
+
+Transfers the file at the given `path`. Sets the `Content-Type` response HTTP header field
+based on the filename's extension. Unless the `root` option is set in
+the options object, `path` must be an absolute path to the file.
+
+<Alert type="warning">
+This API provides access to data on the running file system. Ensure that either (a) the way in
+which the `path` argument was constructed into an absolute path is secure if it contains user
+input or (b) set the `root` option to the absolute path of a directory to contain access within.
+
+When the `root` option is provided, the `path` argument is allowed to be a relative path,
+including containing `..`. Express will validate that the relative path provided as `path` will
+resolve within the given `root` option.
+
+</Alert>
+
+The following table provides details on the `options` parameter.
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Default  | Availability |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `maxAge`       | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)                                                                                                                                                                                               | 0        |              |
+| `root`         | Root directory for relative filenames.                                                                                                                                                                                                                                                                                             |          |              |
+| `lastModified` | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.                                                                                                                                                                                                                        | Enabled  | 4.9.0+       |
+| `headers`      | Object containing HTTP headers to serve with the file.                                                                                                                                                                                                                                                                             |          |              |
+| `dotfiles`     | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".                                                                                                                                                                                                                                                        | "ignore" | &nbsp;       |
+| `acceptRanges` | Enable or disable accepting ranged requests.                                                                                                                                                                                                                                                                                       | `true`   | 4.14+        |
+| `cacheControl` | Enable or disable setting `Cache-Control` response header.                                                                                                                                                                                                                                                                         | `true`   | 4.14+        |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false`  | 4.16+        |
+
+</div>
+
+The method invokes the callback function `fn(err)` when the transfer is complete
+or when an error occurs. If the callback function is specified and an error occurs,
+the callback function must explicitly handle the response process either by
+ending the request-response cycle, or by passing control to the next route.
+
+Here is an example of using `res.sendFile` with all its arguments.
+
+```js
+app.get('/file/:name', function (req, res, next) {
+  var options = {
+    root: path.join(__dirname, 'public'),
+    dotfiles: 'deny',
+    headers: {
+      'x-timestamp': Date.now(),
+      'x-sent': true,
+    },
+  };
+
+  var fileName = req.params.name;
+  res.sendFile(fileName, options, function (err) {
+    if (err) {
+      next(err);
+    } else {
+      console.log('Sent:', fileName);
+    }
+  });
+});
+```
+
+The following example illustrates using
+`res.sendFile` to provide fine-grained support for serving files:
+
+```js
+app.get('/user/:uid/photos/:file', function (req, res) {
+  var uid = req.params.uid;
+  var file = req.params.file;
+
+  req.user.mayViewFilesFrom(uid, function (yes) {
+    if (yes) {
+      res.sendFile('/uploads/' + uid + '/' + file);
+    } else {
+      res.status(403).send("Sorry! You can't see that.");
+    }
+  });
+});
+```
+
+For more information, or if you have issues or concerns, see [send](https://github.com/pillarjs/send).
+
+### res.sendStatus(statusCode)
+
+Sets the response HTTP status code to `statusCode` and sends the registered status message as the text response body. If an unknown status code is specified, the response body will just be the code number.
+
+```js
+res.sendStatus(404);
+```
+
+<Alert type="alert">
+
+Some versions of Node.js will throw when `res.statusCode` is set to an invalid HTTP status code
+(outside of the range `100` to `599`). Consult the HTTP server documentation for the Node.js
+version being used.
+
+</Alert>
+
+[More about HTTP Status Codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
+
+### res.set(field [, value])
+
+Sets the response's HTTP header `field` to `value`.
+To set multiple fields at once, pass an object as the parameter.
+
+```js
+res.set('Content-Type', 'text/plain');
+
+res.set({
+  'Content-Type': 'text/plain',
+  'Content-Length': '123',
+  ETag: '12345',
+});
+```
+
+Aliased as `res.header(field [, value])`.
+
+### res.status(code)
+
+Sets the HTTP status for the response.
+It is a chainable alias of Node's [response.statusCode](https://nodejs.org/api/http.html#http_response_statuscode).
+
+```js
+res.status(403).end();
+res.status(400).send('Bad Request');
+res.status(404).sendFile('/absolute/path/to/404.png');
+```
+
+### res.type(type)
+
+Sets the `Content-Type` HTTP header to the MIME type as determined by the specified `type`. If `type` contains the "/" character, then it sets the `Content-Type` to the exact value of `type`, otherwise it is assumed to be a file extension and the MIME type is looked up in a mapping using the `express.static.mime.lookup()` method.
+
+```js
+res.type('.html');
+// => 'text/html'
+res.type('html');
+// => 'text/html'
+res.type('json');
+// => 'application/json'
+res.type('application/json');
+// => 'application/json'
+res.type('png');
+// => 'image/png'
+```
+
+Aliased as `res.contentType(type)`.
+
+### res.vary(field)
+
+Adds the field to the `Vary` response header, if it is not there already.
+
+```js
+res.vary('User-Agent').render('docs');
+```
diff --git a/src/content/api/4x/api/router/index.mdx b/src/content/api/4x/api/router/index.mdx
new file mode 100644
index 0000000000..2517e3fac3
--- /dev/null
+++ b/src/content/api/4x/api/router/index.mdx
@@ -0,0 +1,411 @@
+---
+title: Router
+description: A router object is an isolated instance of middleware and routes in Express 4.x.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A `router` object is an instance of middleware and routes. You can think of it
+as a "mini-application," capable only of performing middleware and routing
+functions. Every Express application has a built-in app router.
+
+A router behaves like middleware itself, so you can use it as an argument to
+[app.use()](/en/4x/api/application#appusepath-callback--callback) or as the argument to another router's [use()](#routerusepath-function--function) method.
+
+The top-level `express` object has a [Router()](/en/4x/api/express#expressrouteroptions) method that creates a new `router` object.
+
+Once you've created a router object, you can add middleware and HTTP method routes (such as `get`, `put`, `post`,
+and so on) to it just like an application. For example:
+
+```js
+// invoked for any requests passed to this router
+router.use(function (req, res, next) {
+  // .. some logic here .. like any other middleware
+  next();
+});
+
+// will handle any request that ends in /events
+// depends on where the router is "use()'d"
+router.get('/events', function (req, res, next) {
+  // ..
+});
+```
+
+You can then use a router for a particular root URL in this way separating your routes into files or even mini-apps.
+
+```js
+// only requests to /calendar/* will be sent to our "router"
+app.use('/calendar', router);
+```
+
+## Methods
+
+### Router([options])
+
+### router.all(path, [callback, ...] callback)
+
+This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs).
+
+This method is extremely useful for
+mapping "global" logic for specific path prefixes or arbitrary matches.
+For example, if you placed the following route at the top of all other
+route definitions, it would require that all routes from that point on
+would require authentication, and automatically load a user. Keep in mind
+that these callbacks do not have to act as end points; `loadUser`
+can perform a task, then call `next()` to continue matching subsequent
+routes.
+
+```js
+router.all('*', requireAuthentication, loadUser);
+```
+
+Or the equivalent:
+
+```js
+router.all('*', requireAuthentication);
+router.all('*', loadUser);
+```
+
+Another example of this is white-listed "global" functionality. Here
+the example is much like before, but it only restricts paths prefixed with
+"/api":
+
+```js
+router.all('/api/*', requireAuthentication);
+```
+
+### router.METHOD(path, [callback, ...] callback)
+
+The `router.METHOD()` methods provide the routing functionality in Express,
+where METHOD is one of the HTTP methods, such as GET, PUT, POST, and so on,
+in lowercase. Thus, the actual methods are `router.get()`, `router.post()`,
+`router.put()`, and so on.
+
+<Alert type="info">
+
+The `router.get()` function is automatically called for the HTTP `HEAD` method in addition to the
+`GET` method if `router.head()` was not called for the path before `router.get()`.
+
+</Alert>
+
+You can provide multiple callbacks, and all are treated equally, and behave just
+like middleware, except that these callbacks may invoke `next('route')`
+to bypass the remaining route callback(s). You can use this mechanism to perform
+pre-conditions on a route then pass control to subsequent routes when there is no
+reason to proceed with the route matched.
+
+The following snippet illustrates the most simple route definition possible.
+Express translates the path strings to regular expressions, used internally
+to match incoming requests. Query strings are _not_ considered when performing
+these matches, for example "GET /" would match the following route, as would
+"GET /?name=tobi".
+
+```js
+router.get('/', function (req, res) {
+  res.send('hello world');
+});
+```
+
+You can also use regular expressions&mdash;useful if you have very specific
+constraints, for example the following would match "GET /commits/71dbb9c" as well
+as "GET /commits/71dbb9c..4c084f9".
+
+```js
+router.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, function (req, res) {
+  var from = req.params[0];
+  var to = req.params[1] || 'HEAD';
+  res.send('commit range ' + from + '..' + to);
+});
+```
+
+### router.param(name, callback)
+
+Adds callback triggers to route parameters, where `name` is the name of the parameter and `callback` is the callback function. Although `name` is technically optional, using this method without it is deprecated starting with Express v4.11.0 (see below).
+
+The parameters of the callback function are:
+
+- `req`, the request object.
+- `res`, the response object.
+- `next`, indicating the next middleware function.
+- The value of the `name` parameter.
+- The name of the parameter.
+
+<Alert type="info">
+
+Unlike `app.param()`, `router.param()` does not accept an array of route parameters.
+
+</Alert>
+
+For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
+
+```js
+router.param('user', function (req, res, next, id) {
+  // try to get the user details from the User model and attach it to the request object
+  User.find(id, function (err, user) {
+    if (err) {
+      next(err);
+    } else if (user) {
+      req.user = user;
+      next();
+    } else {
+      next(new Error('failed to load user'));
+    }
+  });
+});
+```
+
+Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `router` will be triggered only by route parameters defined on `router` routes.
+
+A param callback will be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
+
+```js
+router.param('id', function (req, res, next, id) {
+  console.log('CALLED ONLY ONCE');
+  next();
+});
+
+router.get('/user/:id', function (req, res, next) {
+  console.log('although this matches');
+  next();
+});
+
+router.get('/user/:id', function (req, res) {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42`, the following is printed:
+
+```
+CALLED ONLY ONCE
+although this matches
+and this matches too
+```
+
+<Alert type="warning">
+
+The following section describes `router.param(callback)`, which is deprecated as of v4.11.0.
+
+</Alert>
+
+The behavior of the `router.param(name, callback)` method can be altered entirely by passing only a function to `router.param()`. This function is a custom implementation of how `router.param(name, callback)` should behave - it accepts two parameters and must return a middleware.
+
+The first parameter of this function is the name of the URL parameter that should be captured, the second parameter can be any JavaScript object which might be used for returning the middleware implementation.
+
+The middleware returned by the function decides the behavior of what happens when a URL parameter is captured.
+
+In this example, the `router.param(name, callback)` signature is modified to `router.param(name, accessId)`. Instead of accepting a name and a callback, `router.param()` will now accept a name and a number.
+
+```js
+var express = require('express');
+var app = express();
+var router = express.Router();
+
+// customizing the behavior of router.param()
+router.param(function (param, option) {
+  return function (req, res, next, val) {
+    if (val === option) {
+      next();
+    } else {
+      res.sendStatus(403);
+    }
+  };
+});
+
+// using the customized router.param()
+router.param('id', '1337');
+
+// route to trigger the capture
+router.get('/user/:id', function (req, res) {
+  res.send('OK');
+});
+
+app.use(router);
+
+app.listen(3000, function () {
+  console.log('Ready');
+});
+```
+
+In this example, the `router.param(name, callback)` signature remains the same, but instead of a middleware callback, a custom data type checking function has been defined to validate the data type of the user id.
+
+```js
+router.param(function (param, validator) {
+  return function (req, res, next, val) {
+    if (validator(val)) {
+      next();
+    } else {
+      res.sendStatus(403);
+    }
+  };
+});
+
+router.param('id', function (candidate) {
+  return !isNaN(parseFloat(candidate)) && isFinite(candidate);
+});
+```
+
+### router.route(path)
+
+Returns an instance of a single route which you can then use to handle HTTP verbs
+with optional middleware. Use `router.route()` to avoid duplicate route naming and
+thus typing errors.
+
+Building on the `router.param()` example above, the following code shows how to use
+`router.route()` to specify various HTTP method handlers.
+
+```js
+var router = express.Router();
+
+router.param('user_id', function (req, res, next, id) {
+  // sample user, would actually fetch from DB, etc...
+  req.user = {
+    id: id,
+    name: 'TJ',
+  };
+  next();
+});
+
+router
+  .route('/users/:user_id')
+  .all(function (req, res, next) {
+    // runs for all HTTP verbs first
+    // think of it as route specific middleware!
+    next();
+  })
+  .get(function (req, res, next) {
+    res.json(req.user);
+  })
+  .put(function (req, res, next) {
+    // just an example of maybe updating the user
+    req.user.name = req.params.name;
+    // save user ... etc
+    res.json(req.user);
+  })
+  .post(function (req, res, next) {
+    next(new Error('not implemented'));
+  })
+  .delete(function (req, res, next) {
+    next(new Error('not implemented'));
+  });
+```
+
+This approach re-uses the single `/users/:user_id` path and adds handlers for
+various HTTP methods.
+
+<Alert type="info">
+
+When you use `router.route()`, middleware ordering is based on when the _route_ is created, not
+when method handlers are added to the route. For this purpose, you can consider method handlers to
+belong to the route to which they were added.
+
+</Alert>
+
+### router.use([path], [function, ...] function)
+
+Uses the specified middleware function or functions, with optional mount path `path`, that defaults to "/".
+
+This method is similar to [app.use()](/en/4x/api/application#appusepath-callback--callback). A simple example and use case is described below.
+See [app.use()](/en/4x/api/application#appusepath-callback--callback) for more information.
+
+Middleware is like a plumbing pipe: requests start at the first middleware function defined
+and work their way "down" the middleware stack processing for each path they match.
+
+```js
+var express = require('express');
+var app = express();
+var router = express.Router();
+
+// simple logger for this router's requests
+// all requests to this router will first hit this middleware
+router.use(function (req, res, next) {
+  console.log('%s %s %s', req.method, req.url, req.path);
+  next();
+});
+
+// this will only be invoked if the path starts with /bar from the mount point
+router.use('/bar', function (req, res, next) {
+  // ... maybe some additional /bar logging ...
+  next();
+});
+
+// always invoked
+router.use(function (req, res, next) {
+  res.send('Hello World');
+});
+
+app.use('/foo', router);
+
+app.listen(3000);
+```
+
+The "mount" path is stripped and is _not_ visible to the middleware function.
+The main effect of this feature is that a mounted middleware function may operate without
+code changes regardless of its "prefix" pathname.
+
+The order in which you define middleware with `router.use()` is very important.
+They are invoked sequentially, thus the order defines middleware precedence. For example,
+usually a logger is the very first middleware you would use, so that every request gets logged.
+
+```js
+var logger = require('morgan');
+var path = require('path');
+
+router.use(logger());
+router.use(express.static(path.join(__dirname, 'public')));
+router.use(function (req, res) {
+  res.send('Hello');
+});
+```
+
+Now suppose you wanted to ignore logging requests for static files, but to continue
+logging routes and middleware defined after `logger()`. You would simply move the call to `express.static()` to the top,
+before adding the logger middleware:
+
+```js
+router.use(express.static(path.join(__dirname, 'public')));
+router.use(logger());
+router.use(function (req, res) {
+  res.send('Hello');
+});
+```
+
+Another example is serving files from multiple directories,
+giving precedence to "./public" over the others:
+
+```js
+router.use(express.static(path.join(__dirname, 'public')));
+router.use(express.static(path.join(__dirname, 'files')));
+router.use(express.static(path.join(__dirname, 'uploads')));
+```
+
+The `router.use()` method also supports named parameters so that your mount points
+for other routers can benefit from preloading using named parameters.
+
+**NOTE**: Although these middleware functions are added via a particular router, _when_
+they run is defined by the path they are attached to (not the router). Therefore,
+middleware added via one router may run for other routers if its routes
+match. For example, this code shows two different routers mounted on the same path:
+
+```js
+var authRouter = express.Router();
+var openRouter = express.Router();
+
+authRouter.use(require('./authenticate').basic(usersdb));
+
+authRouter.get('/:user_id/edit', function (req, res, next) {
+  // ... Edit user UI ...
+});
+openRouter.get('/', function (req, res, next) {
+  // ... List users ...
+});
+openRouter.get('/:user_id', function (req, res, next) {
+  // ... View user ...
+});
+
+app.use('/users', authRouter);
+app.use('/users', openRouter);
+```
+
+Even though the authentication middleware was added via the `authRouter` it will run on the routes defined by the `openRouter` as well since both routers were mounted on `/users`. To avoid this behavior, use different paths for each router.
diff --git a/src/content/api/5x/api.mdx b/src/content/api/5x/api.mdx
new file mode 100644
index 0000000000..f8dc71071a
--- /dev/null
+++ b/src/content/api/5x/api.mdx
@@ -0,0 +1,59 @@
+---
+title: 5x API Reference
+description: API Reference for version 5.x
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+import Card from '@components/primitives/Card/Card.astro';
+import { CardList } from '@components/patterns';
+
+This section provides an overview of the modules and APIs available in Express 5.x for building web applications and HTTP services.
+
+```js title="index.js"
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+<Alert type="info">
+
+Express 5.x requires **Node.js 18 or higher**.
+
+</Alert>
+
+With express v5.x, you can define routes, configure middleware, and start handling HTTP requests using the application instance created by the `express()` function. The API is organized into the following sections:
+
+<CardList gap="6">
+  <a href="/en/5x/api/express">
+    <Card
+      title="express()"
+      body="Learn about the express() function, which creates an Express application."
+    />
+  </a>
+  <a href="/en/5x/api/application">
+    <Card
+      title="Application Object"
+      body="Learn about the properties and methods of the Express 5.x application object."
+    />
+  </a>
+  <a href="/en/5x/api/request">
+    <Card
+      title="Request Object"
+      body="Learn about the properties and methods of the Express 5.x request object."
+    />
+  </a>
+  <a href="/en/5x/api/response">
+    <Card
+      title="Response Object"
+      body="Learn about the properties and methods of the Express 5.x response object."
+    />
+  </a>
+  <a href="/en/5x/api/router">
+    <Card title="Router" body="Learn about the properties and methods of the Express 5.x router." />
+  </a>
+</CardList>
diff --git a/src/content/api/5x/api/application/index.mdx b/src/content/api/5x/api/application/index.mdx
new file mode 100644
index 0000000000..a5c9550b11
--- /dev/null
+++ b/src/content/api/5x/api/application/index.mdx
@@ -0,0 +1,1095 @@
+---
+title: Application Object
+description: Learn about the properties of the Express application object.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `app` object conventionally denotes the Express application.
+Create it by calling the top-level `express()` function exported by the Express module:
+
+```js
+var express = require('express');
+var app = express();
+
+app.get('/', function (req, res) {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+The `app` object has methods for
+
+- Routing HTTP requests; see for example, [app.METHOD](#appmethod) and [app.param](#appparam).
+- Configuring middleware; see [app.route](#approute).
+- Rendering HTML views; see [app.render](#apprender).
+- Registering a template engine; see [app.engine](#appengine).
+
+It also has settings (properties) that affect how the application behaves;
+for more information, see [Application settings](#application-settings).
+
+<Alert type="info">
+  The Express application object can be referred from the [request object](#req) and the [response
+  object](#res) as `req.app`, and `res.app`, respectively.
+</Alert>
+
+## Properties
+
+### app.locals
+
+The `app.locals` object has properties that are local variables within the application,
+and will be available in templates rendered with [res.render](#res.render).
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+```js
+console.dir(app.locals.title);
+// => 'My App'
+
+console.dir(app.locals.email);
+// => 'me@myapp.com'
+```
+
+Once set, the value of `app.locals` properties persist throughout the life of the application,
+in contrast with [res.locals](#res.locals) properties that
+are valid only for the lifetime of the request.
+
+You can access local variables in templates rendered within the application.
+This is useful for providing helper functions to templates, as well as application-level data.
+Local variables are available in middleware via `req.app.locals` (see [req.app](#req.app))
+
+```js
+app.locals.title = 'My App';
+app.locals.strftime = require('strftime');
+app.locals.email = 'me@myapp.com';
+```
+
+### app.mountpath
+
+The `app.mountpath` property contains one or more path patterns on which a sub-app was mounted.
+
+<Alert type="info">
+
+A sub-app is an instance of `express` that may be used for handling the request to a route.
+
+</Alert>
+
+```js
+const express = require('express');
+
+const app = express(); // the main app
+const admin = express(); // the sub app
+
+admin.get('/', (req, res) => {
+  console.log(admin.mountpath); // /admin
+  res.send('Admin Homepage');
+});
+
+app.use('/admin', admin); // mount the sub app
+```
+
+It is similar to the [baseUrl](#req.baseUrl) property of the `req` object, except `req.baseUrl`
+returns the matched URL path, instead of the matched patterns.
+
+If a sub-app is mounted on multiple path patterns, `app.mountpath` returns the list of
+patterns it is mounted on, as shown in the following example.
+
+```js
+const admin = express();
+
+admin.get('/', (req, res) => {
+  console.log(admin.mountpath); // [ '/adm{*splat}n', '/manager' ]
+  res.send('Admin Homepage');
+});
+
+const secret = express();
+secret.get('/', (req, res) => {
+  console.log(secret.mountpath); // /secr{*splat}t
+  res.send('Admin Secret');
+});
+
+admin.use('/secr{*splat}t', secret); // load the 'secret' router on '/secr{*splat}t', on the 'admin' sub app
+app.use(['/adm{*splat}n', '/manager'], admin); // load the 'admin' router on '/adm{*splat}n' and '/manager', on the parent app
+```
+
+### app.router
+
+The application's in-built instance of router. This is created lazily, on first access.
+
+```js
+const express = require('express');
+const app = express();
+const router = app.router;
+
+router.get('/', (req, res) => {
+  res.send('hello world');
+});
+
+app.listen(3000);
+```
+
+You can add middleware and HTTP method routes to the `router` just like an application.
+
+For more information, see [Router](#router).
+
+## Events
+
+### app.on('mount', callback(parent))
+
+The `mount` event is fired on a sub-app, when it is mounted on a parent app. The parent app is passed to the callback function.
+
+<Alert type="info">
+**NOTE**
+
+Sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value.
+
+For details, see [Application settings](/en/api/application/app-set#app.settings.table).
+
+</Alert>
+
+```js
+const admin = express();
+
+admin.on('mount', (parent) => {
+  console.log('Admin Mounted');
+  console.log(parent); // refers to the parent app
+});
+
+admin.get('/', (req, res) => {
+  res.send('Admin Homepage');
+});
+
+app.use('/admin', admin);
+```
+
+## Methods
+
+### app.all(path, callback [, callback ...])
+
+This method is like the standard [app.METHOD()](#appmethod) methods,
+except it matches all HTTP verbs.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Examples
+
+The following callback is executed for requests to `/secret` whether using
+GET, POST, PUT, DELETE, or any other HTTP request method:
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+The `app.all()` method is useful for mapping "global" logic for specific path prefixes or arbitrary matches. For example, if you put the following at the top of all other
+route definitions, it requires that all routes from that point on
+require authentication, and automatically load a user. Keep in mind
+that these callbacks do not have to act as end-points: `loadUser`
+can perform a task, then call `next()` to continue matching subsequent
+routes.
+
+```js
+app.all('{*splat}', requireAuthentication, loadUser);
+```
+
+Or the equivalent:
+
+```js
+app.all('{*splat}', requireAuthentication);
+app.all('{*splat}', loadUser);
+```
+
+Another example is white-listed "global" functionality.
+The example is similar to the ones above, but it only restricts paths that start with
+"/api":
+
+```js
+app.all('/api/{*splat}', requireAuthentication);
+```
+
+### app.delete(path, callback [, callback ...])
+
+Routes HTTP DELETE requests to the specified path with the specified callback functions.
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Example
+
+```js
+app.delete('/', (req, res) => {
+  res.send('DELETE request to homepage');
+});
+```
+
+### app.disable(name)
+
+Sets the Boolean setting `name` to `false`, where `name` is one of the properties from the [app settings table](/en/api/application/app-set#app.settings.table).
+Calling `app.set('foo', false)` for a Boolean property is the same as calling `app.disable('foo')`.
+
+For example:
+
+```js
+app.disable('trust proxy');
+app.get('trust proxy');
+// => false
+```
+
+### app.disabled(name)
+
+Returns `true` if the Boolean setting `name` is disabled (`false`), where `name` is one of the properties from
+the [app settings table](/en/api/application/app-set#app.settings.table).
+
+```js
+app.disabled('trust proxy');
+// => true
+
+app.enable('trust proxy');
+app.disabled('trust proxy');
+// => false
+```
+
+### app.enable(name)
+
+Sets the Boolean setting `name` to `true`, where `name` is one of the properties from the [app settings table](/en/api/application/app-set#app.settings.table).
+Calling `app.set('foo', true)` for a Boolean property is the same as calling `app.enable('foo')`.
+
+```js
+app.enable('trust proxy');
+app.get('trust proxy');
+// => true
+```
+
+### app.enabled(name)
+
+Returns `true` if the setting `name` is enabled (`true`), where `name` is one of the
+properties from the [app settings table](/en/api/application/app-set#app.settings.table).
+
+```js
+app.enabled('trust proxy');
+// => false
+
+app.enable('trust proxy');
+app.enabled('trust proxy');
+// => true
+```
+
+### app.engine(ext, callback)
+
+Registers the given template engine `callback` as `ext`.
+
+By default, Express will `require()` the engine based on the file extension.
+For example, if you try to render a "foo.pug" file, Express invokes the
+following internally, and caches the `require()` on subsequent calls to increase
+performance.
+
+```js
+app.engine('pug', require('pug').__express);
+```
+
+Use this method for engines that do not provide `.__express` out of the box,
+or if you wish to "map" a different extension to the template engine.
+
+For example, to map the EJS template engine to ".html" files:
+
+```js
+app.engine('html', require('ejs').renderFile);
+```
+
+In this case, EJS provides a `.renderFile()` method with
+the same signature that Express expects: `(path, options, callback)`,
+though note that it aliases this method as `ejs.__express` internally
+so if you're using ".ejs" extensions you don't need to do anything.
+
+Some template engines do not follow this convention. The
+[consolidate.js](https://github.com/tj/consolidate.js) library maps Node template engines to follow this convention,
+so they work seamlessly with Express.
+
+```js
+const engines = require('consolidate');
+app.engine('haml', engines.haml);
+app.engine('html', engines.hogan);
+```
+
+### app.get(name)
+
+Returns the value of `name` app setting, where `name` is one of the strings in the
+[app settings table](/en/api/application/app-set#app.settings.table). For example:
+
+```js
+app.get('title');
+// => undefined
+
+app.set('title', 'My Site');
+app.get('title');
+// => "My Site"
+```
+
+### app.get(path, callback [, callback ...])
+
+Routes HTTP GET requests to the specified path with the specified callback functions.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Example
+
+```js
+app.get('/', (req, res) => {
+  res.send('GET request to homepage');
+});
+```
+
+### app.listen(path, [callback])
+
+Starts a UNIX socket and listens for connections on the given path.
+This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
+
+```js
+const express = require('express');
+const app = express();
+app.listen('/tmp/sock');
+```
+
+### app.listen([port[, host[, backlog]]][, callback])
+
+Binds and listens for connections on the specified host and port.
+This method is identical to Node's [http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen).
+
+If port is omitted or is 0, the operating system will assign an arbitrary unused
+port, which is useful for cases like automated tasks (tests, etc.).
+
+```js
+const express = require('express');
+const app = express();
+app.listen(3000);
+```
+
+The `app` returned by `express()` is in fact a JavaScript
+`Function`, designed to be passed to Node's HTTP servers as a callback
+to handle requests. This makes it easy to provide both HTTP and HTTPS versions of
+your app with the same code base, as the app does not inherit from these
+(it is simply a callback):
+
+```js
+const express = require('express');
+const https = require('https');
+const http = require('http');
+const app = express();
+
+http.createServer(app).listen(80);
+https.createServer(options, app).listen(443);
+```
+
+The `app.listen()` method returns an [http.Server](https://nodejs.org/api/http.html#http_class_http_server) object and (for HTTP) is a convenience method for the following:
+
+```js
+app.listen = function () {
+  const server = http.createServer(this);
+  return server.listen.apply(server, arguments);
+};
+```
+
+<Alert type="info">
+
+All the forms of Node's
+[http.Server.listen()](https://nodejs.org/api/http.html#http_server_listen) method are in fact
+actually supported.
+
+</Alert>
+
+### app.METHOD(path, callback [, callback ...])
+
+Routes an HTTP request, where METHOD is the HTTP method of the request, such as GET,
+PUT, POST, and so on, in lowercase. Thus, the actual methods are `app.get()`,
+`app.post()`, `app.put()`, and so on. See [Routing methods](#routing-methods) below for the complete list.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Routing methods
+
+Express supports the following routing methods corresponding to the HTTP methods of the same names:
+
+<div class="methods-columns">
+  <ul>
+    <li>
+      <code>checkout</code>
+    </li>
+    <li>
+      <code>copy</code>
+    </li>
+    <li>
+      <code>delete</code>
+    </li>
+    <li>
+      <code>get</code>
+    </li>
+    <li>
+      <code>head</code>
+    </li>
+    <li>
+      <code>lock</code>
+    </li>
+    <li>
+      <code>merge</code>
+    </li>
+    <li>
+      <code>mkactivity</code>
+    </li>
+  </ul>
+  <ul>
+    <li>
+      <code>mkcol</code>
+    </li>
+    <li>
+      <code>move</code>
+    </li>
+    <li>
+      <code>m-search</code>
+    </li>
+    <li>
+      <code>notify</code>
+    </li>
+    <li>
+      <code>options</code>
+    </li>
+    <li>
+      <code>patch</code>
+    </li>
+    <li>
+      <code>post</code>
+    </li>
+  </ul>
+  <ul>
+    <li>
+      <code>purge</code>
+    </li>
+    <li>
+      <code>put</code>
+    </li>
+    <li>
+      <code>report</code>
+    </li>
+    <li>
+      <code>search</code>
+    </li>
+    <li>
+      <code>subscribe</code>
+    </li>
+    <li>
+      <code>trace</code>
+    </li>
+    <li>
+      <code>unlock</code>
+    </li>
+    <li>
+      <code>unsubscribe</code>
+    </li>
+  </ul>
+</div>
+
+The API documentation has explicit entries only for the most popular HTTP methods `app.get()`,
+`app.post()`, `app.put()`, and `app.delete()`.
+However, the other methods listed above work in exactly the same way.
+
+To route methods that translate to invalid JavaScript variable names, use the bracket notation. For example, `app['m-search']('/', function ...`.
+
+<Alert type="info">
+
+The `app.get()` function is automatically called for the HTTP `HEAD` method in addition to the
+`GET` method if `app.head()` was not called for the path before `app.get()`.
+
+</Alert>
+
+The method, `app.all()`, is not derived from any HTTP method and loads middleware at
+the specified path for _all_ HTTP request methods.
+For more information, see [app.all](#appall).
+
+For more information on routing, see the [routing guide](/en/guide/routing).
+
+### app.param(name, callback)
+
+Add callback triggers to [route parameters](/en/guide/routing#route-parameters), where `name` is the name of the parameter or an array of them, and `callback` is the callback function. The parameters of the callback function are the request object, the response object, the next middleware, the value of the parameter and the name of the parameter, in that order.
+
+If `name` is an array, the `callback` trigger is registered for each parameter declared in it, in the order in which they are declared. Furthermore, for each declared parameter except the last one, a call to `next` inside the callback will call the callback for the next declared parameter. For the last parameter, a call to `next` will call the next middleware in place for the route currently being processed, just like it would if `name` were just a string.
+
+For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
+
+```js
+app.param('user', (req, res, next, id) => {
+  // try to get the user details from the User model and attach it to the request object
+  User.find(id, (err, user) => {
+    if (err) {
+      next(err);
+    } else if (user) {
+      req.user = user;
+      next();
+    } else {
+      next(new Error('failed to load user'));
+    }
+  });
+});
+```
+
+Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `app` will be triggered only by route parameters defined on `app` routes.
+
+All param callbacks will be called before any handler of any route in which the param occurs, and they will each be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
+
+```js
+app.param('id', (req, res, next, id) => {
+  console.log('CALLED ONLY ONCE');
+  next();
+});
+
+app.get('/user/:id', (req, res, next) => {
+  console.log('although this matches');
+  next();
+});
+
+app.get('/user/:id', (req, res) => {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42`, the following is printed:
+
+```
+CALLED ONLY ONCE
+although this matches
+and this matches too
+```
+
+```js
+app.param(['id', 'page'], (req, res, next, value) => {
+  console.log('CALLED ONLY ONCE with', value);
+  next();
+});
+
+app.get('/user/:id/:page', (req, res, next) => {
+  console.log('although this matches');
+  next();
+});
+
+app.get('/user/:id/:page', (req, res) => {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42/3`, the following is printed:
+
+```
+CALLED ONLY ONCE with 42
+CALLED ONLY ONCE with 3
+although this matches
+and this matches too
+```
+
+### app.path()
+
+Returns the canonical path of the app, a string.
+
+```js
+const app = express();
+const blog = express();
+const blogAdmin = express();
+
+app.use('/blog', blog);
+blog.use('/admin', blogAdmin);
+
+console.log(app.path()); // ''
+console.log(blog.path()); // '/blog'
+console.log(blogAdmin.path()); // '/blog/admin'
+```
+
+The behavior of this method can become very complicated in complex cases of mounted apps:
+it is usually better to use [req.baseUrl](#req.baseUrl) to get the canonical path of the app.
+
+### app.post(path, callback [, callback ...])
+
+Routes HTTP POST requests to the specified path with the specified callback functions.
+For more information, see the [routing guide](/en/guide/routing).
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Example
+
+```js
+app.post('/', (req, res) => {
+  res.send('POST request to homepage');
+});
+```
+
+### app.put(path, callback [, callback ...])
+
+Routes HTTP PUT requests to the specified path with the specified callback functions.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Example
+
+```js
+app.put('/', (req, res) => {
+  res.send('PUT request to homepage');
+});
+```
+
+### app.render(view, [locals], callback)
+
+Returns the rendered HTML of a view via the `callback` function. It accepts an optional parameter
+that is an object containing local variables for the view. It is like [res.render()](#res.render),
+except it cannot send the rendered view to the client on its own.
+
+<Alert type="info">
+
+Think of `app.render()` as a utility function for generating rendered view strings. Internally
+`res.render()` uses `app.render()` to render views.
+
+</Alert>
+
+<Alert type="warning">
+
+The `view` argument performs file system operations like reading a file from disk and evaluating
+Node.js modules, and as so for security reasons should not contain input from the end-user.
+
+</Alert>
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+<Alert type="alert">
+
+The local variable `cache` is reserved for enabling view cache. Set it to `true`, if you want to
+cache view during development; view caching is enabled in production by default.
+
+</Alert>
+
+```js
+app.render('email', (err, html) => {
+  // ...
+});
+
+app.render('email', { name: 'Tobi' }, (err, html) => {
+  // ...
+});
+```
+
+### app.route(path)
+
+Returns an instance of a single route, which you can then use to handle HTTP verbs with optional middleware.
+Use `app.route()` to avoid duplicate route names (and thus typo errors).
+
+```js
+const app = express();
+
+app
+  .route('/events')
+  .all((req, res, next) => {
+    // runs for all HTTP verbs first
+    // think of it as route specific middleware!
+  })
+  .get((req, res, next) => {
+    res.json({});
+  })
+  .post((req, res, next) => {
+    // maybe add a new event...
+  });
+```
+
+### app.set(name, value)
+
+Assigns setting `name` to `value`. You may store any value that you want,
+but certain names can be used to configure the behavior of the server. These
+special names are listed in the [app settings table](/en/api/application/app-set#app.settings.table).
+
+Calling `app.set('foo', true)` for a Boolean property is the same as calling
+`app.enable('foo')`. Similarly, calling `app.set('foo', false)` for a Boolean
+property is the same as calling `app.disable('foo')`.
+
+Retrieve the value of a setting with [`app.get()`](#appgetname).
+
+```js
+app.set('title', 'My Site');
+app.get('title'); // "My Site"
+```
+
+#### Application Settings
+
+The following table lists application settings.
+
+Note that sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value; these are explicitly noted in the table below.
+
+Exceptions: Sub-apps will inherit the value of `trust proxy` even though it has a default value (for backward-compatibility);
+Sub-apps will not inherit the value of `view cache` in production (when `NODE_ENV` is "production").
+
+| Property                 | Type            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Default                                                                                             |
+| ------------------------ | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| `case sensitive routing` | Boolean         | Enable case sensitivity. When enabled, "/Foo" and "/foo" are different routes. When disabled, "/Foo" and "/foo" are treated the same. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | N/A (undefined)                                                                                     |
+| `env`                    | String          | Environment mode. Be sure to set to "production" in a production environment; see [Production best practices: performance and reliability](/en/advanced/best-practice-performance#env).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `process.env.NODE_ENV` (`NODE_ENV` environment variable) or "development" if `NODE_ENV` is not set. |
+| `etag`                   | Varied          | Set the ETag response header. For possible values, see the `etag` options table below. [More about the HTTP ETag header](http://en.wikipedia.org/wiki/HTTP_ETag).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | `weak`                                                                                              |
+| `jsonp callback name`    | String          | Specifies the default JSONP callback name.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | "callback"                                                                                          |
+| `json escape`            | Boolean         | Enable escaping JSON responses from the `res.json`, `res.jsonp`, and `res.send` APIs. This will escape the characters `<`, `>`, and `&` as Unicode escape sequences in JSON. The purpose of this is to assist with [mitigating certain types of persistent XSS attacks](https://blog.mozilla.org/security/2017/07/18/web-service-audits-firefox-accounts/) when clients sniff responses for HTML. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `json replacer`          | Varied          | The ['replacer' argument used by `JSON.stringify`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_replacer_parameter). **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | N/A (undefined)                                                                                     |
+| `json spaces`            | Varied          | The ['space' argument used by `JSON.stringify`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify#The_space_argument). This is typically set to the number of spaces to use to indent prettified JSON. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `query parser`           | Varied          | Disable query parsing by setting the value to `false`, or set the query parser to use either "simple" or "extended" or a custom query string parsing function. The simple query parser is based on Node's native query parser, [querystring](http://nodejs.org/api/querystring.html). The extended query parser is based on [qs](https://www.npmjs.org/package/qs). A custom query string parsing function will receive the complete query string, and must return an object of query keys and their values.                                                                                                                                                                                                                                                                                                                                   | "simple"                                                                                            |
+| `strict routing`         | Boolean         | Enable strict routing. When enabled, the router treats "/foo" and "/foo/" as different. Otherwise, the router treats "/foo" and "/foo/" as the same. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | N/A (undefined)                                                                                     |
+| `subdomain offset`       | Number          | The number of dot-separated parts of the host to remove to access subdomain.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | 2                                                                                                   |
+| `trust proxy`            | Varied          | Indicates the app is behind a front-facing proxy, and to use the `X-Forwarded-*` headers to determine the connection and the IP address of the client. NOTE: `X-Forwarded-*` headers are easily spoofed and the detected IP addresses are unreliable. When enabled, Express attempts to determine the IP address of the client connected through the front-facing proxy, or series of proxies. The `req.ips` property, then contains an array of IP addresses the client is connected through. To enable it, use the values described in the trust proxy options table below. The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.org/package/proxy-addr) package. For more information, see its documentation. **NOTE**: Sub-apps _will_ inherit the value of this setting, even though it has a default value. | `false` (disabled)                                                                                  |
+| `views`                  | String or Array | A directory or an array of directories for the application's views. If an array, the views are looked up in the order they occur in the array.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | `process.cwd() + '/views'`                                                                          |
+| `view cache`             | Boolean         | Enables view template compilation caching. **NOTE**: Sub-apps will not inherit the value of this setting in production (when `NODE_ENV` is "production").                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | `true` in production, otherwise undefined.                                                          |
+| `view engine`            | String          | The default engine extension to use when omitted. **NOTE**: Sub-apps will inherit the value of this setting.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | N/A (undefined)                                                                                     |
+| `x-powered-by`           | Boolean         | Enables the "X-Powered-By: Express" HTTP header.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | `true`                                                                                              |
+
+#### Options for `trust proxy` setting
+
+Read [Express behind proxies](/en/guide/behind-proxies) for more information.
+
+**Boolean**: If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-*` header. If `false`, the app is understood as directly facing the Internet and the client's IP address is derived from `req.connection.remoteAddress`. This is the default setting.
+
+**String / String containing comma-separated values / Array of strings**: An IP address, subnet, or an array of IP addresses, and subnets to trust. Pre-configured subnet names are:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Set IP addresses in any of the following ways:
+
+Specify a single subnet:
+
+```js
+app.set('trust proxy', 'loopback');
+```
+
+Specify a subnet and an address:
+
+```js
+app.set('trust proxy', 'loopback, 123.123.123.123');
+```
+
+Specify multiple subnets as CSV:
+
+```js
+app.set('trust proxy', 'loopback, linklocal, uniquelocal');
+```
+
+Specify multiple subnets as an array:
+
+```js
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']);
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address.
+
+**Number**: Trust the *n*th hop from the front-facing proxy server as the client.
+
+**Function**: Custom trust implementation. Use this only if you know what you are doing.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+#### Options for `etag` setting
+
+**NOTE**: These settings apply only to dynamic files, not static files. The `express.static` middleware ignores these settings.
+
+The ETag functionality is implemented using the [etag](https://www.npmjs.org/package/etag) package. For more information, see its documentation.
+
+| Type     | Value                                                                                    |
+| -------- | ---------------------------------------------------------------------------------------- |
+| Boolean  | `true` enables weak ETag. This is the default setting. `false` disables ETag altogether. |
+| String   | If "strong", enables strong ETag. If "weak", enables weak ETag.                          |
+| Function | Custom ETag function implementation. Use this only if you know what you are doing.       |
+
+```js
+app.set('etag', (body, encoding) => {
+  return generateHash(body, encoding); // consider the function is defined
+});
+```
+
+### app.use([path,] callback [, callback...])
+
+Mounts the specified [middleware](/en/guide/using-middleware) function or functions
+at the specified path:
+the middleware function is executed when the base of the requested path matches `path`.
+
+#### Arguments
+
+| Argument   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Default           |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
+| `path`     | The path for which the middleware function is invoked. It can be any of the following: a string representing a path, a path pattern, a regular expression pattern to match paths, or an array containing any combination of the above. For examples, see [Path examples](#path-examples).                                                                                                                                                                                                                                                                                                                                                                                                                                                        | `'/'` (root path) |
+| `callback` | One or more callback functions. Accepted formats: a single middleware function, multiple middleware functions separated by commas, an array of middleware functions, or a combination of the above. You may provide multiple callbacks that behave like middleware. These can call `next('route')` to skip remaining callbacks for the current route. This is useful for conditional routing logic. If a callback throws an error or returns a rejected promise, `next(err)` is invoked automatically. Since both [router](#router) and [app](#application) implement the middleware interface, they can also be used as callback middleware. For examples, see [Middleware callback function examples](#middleware-callback-function-examples). | _None_            |
+
+#### Description
+
+A route will match any path that follows its path immediately with a "`/`".
+For example: `app.use('/apple', ...)` will match "/apple", "/apple/images",
+"/apple/images/news", and so on.
+
+Since `path` defaults to "/", middleware mounted without a path will be executed for every request to the app.
+For example, this middleware function will be executed for _every_ request to the app:
+
+```js
+app.use((req, res, next) => {
+  console.log('Time: %d', Date.now());
+  next();
+});
+```
+
+<Alert type="info">
+**NOTE**
+
+Sub-apps will:
+
+- Not inherit the value of settings that have a default value. You must set the value in the sub-app.
+- Inherit the value of settings with no default value.
+
+For details, see [Application settings](/en/5x/api/application/app-settings/).
+
+</Alert>
+
+Middleware functions are executed sequentially, therefore the order of middleware inclusion is important.
+
+```js
+// this middleware will not allow the request to go beyond it
+app.use((req, res, next) => {
+  res.send('Hello World');
+});
+
+// requests will never reach this route
+app.get('/', (req, res) => {
+  res.send('Welcome');
+});
+```
+
+**Error-handling middleware**
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors. For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`):
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+#### Path examples
+
+The following table provides some simple examples of valid `path` values for
+mounting middleware.
+
+**Path**: Matches the exact path `/abcd` and any sub-paths starting with `/abcd/` (for example, `/abcd/foo`):
+
+```js
+app.use('/abcd', (req, res, next) => {
+  next();
+});
+```
+
+**Path Pattern**: This will match paths starting with `/abcd` and `/abd`:
+
+```js
+app.use('/ab{c}d', (req, res, next) => {
+  next();
+});
+```
+
+**Regular Expression**: This will match paths starting with `/abc` and `/xyz`:
+
+```js
+app.use(/\/abc|\/xyz/, (req, res, next) => {
+  next();
+});
+```
+
+**Array**: This will match paths starting with `/abcd`, `/xyza`, `/lmn`, and `/pqr`:
+
+```js
+app.use(['/abcd', '/xyza', /\/lmn|\/pqr/], (req, res, next) => {
+  next();
+});
+```
+
+#### Middleware callback function examples
+
+The following table provides some simple examples of middleware functions that
+can be used as the `callback` argument to `app.use()`, `app.METHOD()`, and `app.all()`.
+
+**Single Middleware**: You can define and mount a middleware function locally.
+
+```js
+app.use((req, res, next) => {
+  next();
+});
+```
+
+A router is valid middleware.
+
+```js
+const router = express.Router();
+router.get('/', (req, res, next) => {
+  next();
+});
+app.use(router);
+```
+
+An Express app is valid middleware.
+
+```js
+const subApp = express();
+subApp.get('/', (req, res, next) => {
+  next();
+});
+app.use(subApp);
+```
+
+**Series of Middleware**: You can specify more than one middleware function at the same mount path.
+
+```js
+const r1 = express.Router();
+r1.get('/', (req, res, next) => {
+  next();
+});
+
+const r2 = express.Router();
+r2.get('/', (req, res, next) => {
+  next();
+});
+
+app.use(r1, r2);
+```
+
+**Array**: Use an array to group middleware logically.
+
+```js
+const r1 = express.Router();
+r1.get('/', (req, res, next) => {
+  next();
+});
+
+const r2 = express.Router();
+r2.get('/', (req, res, next) => {
+  next();
+});
+
+app.use([r1, r2]);
+```
+
+**Combination**: You can combine all the above ways of mounting middleware.
+
+```js
+function mw1(req, res, next) {
+  next();
+}
+function mw2(req, res, next) {
+  next();
+}
+
+const r1 = express.Router();
+r1.get('/', (req, res, next) => {
+  next();
+});
+
+const r2 = express.Router();
+r2.get('/', (req, res, next) => {
+  next();
+});
+
+const subApp = express();
+subApp.get('/', (req, res, next) => {
+  next();
+});
+
+app.use(mw1, [mw2, r1, r2], subApp);
+```
+
+Following are some examples of using the [express.static](/en/guide/using-middleware#middleware.built-in)
+middleware in an Express app.
+
+Serve static content for the app from the "public" directory in the application directory:
+
+```js
+// GET /style.css etc
+app.use(express.static(path.join(__dirname, 'public')));
+```
+
+Mount the middleware at "/static" to serve static content only when their request path is prefixed with "/static":
+
+```js
+// GET /static/style.css etc.
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Disable logging for static content requests by loading the logger middleware after the static middleware:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(logger());
+```
+
+Serve static files from multiple directories, but give precedence to "./public" over the others:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(express.static(path.join(__dirname, 'files')));
+app.use(express.static(path.join(__dirname, 'uploads')));
+```
diff --git a/src/content/api/5x/api/express/index.mdx b/src/content/api/5x/api/express/index.mdx
new file mode 100644
index 0000000000..4c9ac1f8f2
--- /dev/null
+++ b/src/content/api/5x/api/express/index.mdx
@@ -0,0 +1,301 @@
+---
+title: Express Object
+description: Learn about the methods available on the top-level Express object.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Creates an Express application. The `express()` function is a top-level function exported by the `express` module.
+
+```js
+const express = require('express');
+const app = express();
+```
+
+## Methods
+
+The Express object has the following methods that can be used to create middleware functions, routers and have some built-in middleware:
+
+### express.json([options])
+
+This is a built-in middleware function in Express. It parses incoming requests
+with JSON payloads and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that only parses JSON and only looks at requests where
+the `Content-Type` header matches the `type` option. This parser accepts any
+Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or `undefined` if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Type     | Default              |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | -------------------- |
+| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                        | Boolean  | `true`               |
+| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                     | Mixed    | `"100kb"`            |
+| `reviver` | The `reviver` option is passed directly to `JSON.parse` as the second argument. You can find more information on this argument [in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter).                                                                                                                                                                                                                | Function | `null`               |
+| `strict`  | Enables or disables only accepting arrays and objects; when disabled will accept anything `JSON.parse` accepts.                                                                                                                                                                                                                                                                                                                                                                                                                | Boolean  | `true`               |
+| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `json`), a mime type (like `application/json`), or a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/json"` |
+| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                    | Function | `undefined`          |
+
+</div>
+
+### express.raw([options])
+
+This is a built-in middleware function in Express. It parses incoming request
+payloads into a `Buffer` and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that parses all bodies as a `Buffer` and only looks at requests
+where the `Content-Type` header matches the `type` option. This parser accepts
+any Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` `Buffer` containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or `undefined` if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.toString()` may fail
+in multiple ways, for example stacking multiple parsers `req.body` may be from a different parser.
+Testing that `req.body` is a `Buffer` before calling buffer methods is recommended.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property  | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Type     | Default                      |
+| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------- |
+| `inflate` | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                                      | Boolean  | `true`                       |
+| `limit`   | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                                   | Mixed    | `"100kb"`                    |
+| `type`    | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `bin`), a mime type (like `application/octet-stream`), or a mime type with a wildcard (like `*/*` or `application/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/octet-stream"` |
+| `verify`  | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                                  | Function | `undefined`                  |
+
+</div>
+
+### express.Router([options])
+
+Creates a new [router](/en/5x/api/router/) object.
+
+```js
+const router = express.Router([options]);
+```
+
+The optional `options` parameter specifies the behavior of the router.
+
+<div class="table-scroller" markdown="1">
+
+| Property        | Description                                                                                                                                           | Default                                                                     | Availability |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ------------ |
+| `caseSensitive` | Enable case sensitivity.                                                                                                                              | Disabled by default, treating "/Foo" and "/foo" as the same.                |              |
+| `mergeParams`   | Preserve the `req.params` values from the parent router. If the parent and the child have conflicting param names, the child's value take precedence. | `false`                                                                     | 4.5.0+       |
+| `strict`        | Enable strict routing.                                                                                                                                | Disabled by default, "/foo" and "/foo/" are treated the same by the router. | &nbsp;       |
+
+</div>
+
+You can add middleware and HTTP method routes (such as `get`, `put`, `post`, and
+so on) to `router` just like an application.
+
+For more information, see [Router](/en/5x/api/router/).
+
+### express.static(root, [options])
+
+This is a built-in middleware function in Express.
+It serves static files and is based on [serve-static](/en/resources/middleware/serve-static).
+
+<Alert type="info">
+
+NOTE: For best results, [use a reverse
+proxy](/en/advanced/best-practice-performance#use-a-reverse-proxy) cache to improve performance of
+serving static assets.
+
+</Alert>
+
+The `root` argument specifies the root directory from which to serve static assets.
+The function determines the file to serve by combining `req.url` with the provided `root` directory.
+When a file is not found, instead of sending a 404 response, it instead calls `next()`
+to move on to the next middleware, allowing for stacking and fall-backs.
+
+The following table describes the properties of the `options` object.
+See also the [example below](#example-of-expressstatic).
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Type     | Default      |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `dotfiles`     | Determines how dotfiles (files or directories that begin with a dot ".") are treated. <br/><br/>See [dotfiles](#dotfiles) below.                                                                                                                                                                                                   | String   | "ignore"     |
+| `etag`         | Enable or disable etag generation <br/><br/>NOTE: `express.static` always sends weak ETags.                                                                                                                                                                                                                                        | Boolean  | `true`       |
+| `extensions`   | Sets file extension fallbacks: If a file is not found, search for files with the specified extensions and serve the first one found. Example: `['html', 'htm']`.                                                                                                                                                                   | Mixed    | `false`      |
+| `fallthrough`  | Let client errors fall-through as unhandled requests, otherwise forward a client error. <br/><br/>See [fallthrough](#fallthrough) below.                                                                                                                                                                                           | Boolean  | `true`       |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | Boolean  | `false`      |
+| `index`        | Sends the specified directory index file. Set to `false` to disable directory indexing.                                                                                                                                                                                                                                            | Mixed    | "index.html" |
+| `lastModified` | Set the `Last-Modified` header to the last modified date of the file on the OS.                                                                                                                                                                                                                                                    | Boolean  | `true`       |
+| `maxAge`       | Set the max-age property of the Cache-Control header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms).                                                                                                                                                                                                 | Number   | 0            |
+| `redirect`     | Redirect to trailing "/" when the pathname is a directory.                                                                                                                                                                                                                                                                         | Boolean  | `true`       |
+| `setHeaders`   | Function for setting HTTP headers to serve with the file. <br/><br/>See [setHeaders](#setheaders) below.                                                                                                                                                                                                                           | Function |              |
+| `acceptRanges` | Enable or disable accepting ranged requests. Disabling this will not send the Accept-Ranges header and will ignore the contents of the Range request header.                                                                                                                                                                       | Boolean  | true         |
+| `cacheControl` | Enable or disable setting the Cache-Control response header. Disabling this will ignore the immutable and maxAge options.                                                                                                                                                                                                          | Boolean  | true         |
+
+</div>
+
+For more information, see [Serving static files in Express](/en/starter/static-files).
+and [Using middleware - Built-in middleware](/en/guide/using-middleware#middleware.built-in).
+
+#### dotfiles
+
+Possible values for this option are:
+
+- "allow" - No special treatment for dotfiles.
+- "deny" - Deny a request for a dotfile, respond with `403`, then call `next()`.
+- "ignore" - Act as if the dotfile does not exist, respond with `404`, then call `next()`.
+
+#### fallthrough
+
+When this option is `true`, client errors such as a bad request or a request to a non-existent
+file will cause this middleware to simply call `next()` to invoke the next middleware in the stack.
+When false, these errors (even 404s), will invoke `next(err)`.
+
+Set this option to `true` so you can map multiple physical directories
+to the same web address or for routes to fill in non-existent files.
+
+Use `false` if you have mounted this middleware at a path designed
+to be strictly a single file system directory, which allows for short-circuiting 404s
+for less overhead. This middleware will also reply to all methods.
+
+#### setHeaders
+
+For this option, specify a function to set custom response headers. Alterations to the headers must occur synchronously.
+
+The signature of the function is:
+
+```js
+fn(res, path, stat);
+```
+
+Arguments:
+
+- `res`, the [response object](/en/5x/api/response/).
+- `path`, the file path that is being sent.
+- `stat`, the `stat` object of the file that is being sent.
+
+#### Example of express.static
+
+Here is an example of using the `express.static` middleware function with an elaborate options object:
+
+```js
+const options = {
+  dotfiles: 'ignore',
+  etag: false,
+  extensions: ['htm', 'html'],
+  index: false,
+  maxAge: '1d',
+  redirect: false,
+  setHeaders(res, path, stat) {
+    res.set('x-timestamp', Date.now());
+  },
+};
+
+app.use(express.static('public', options));
+```
+
+### express.text([options])
+
+This is a built-in middleware function in Express. It parses incoming request
+payloads into a string and is based on
+[body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that parses all bodies as a string and only looks at requests
+where the `Content-Type` header matches the `type` option. This parser accepts
+any Unicode encoding of the body and supports automatic inflation of `gzip` and
+`deflate` encodings.
+
+A new `body` string containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or `undefined` if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred.
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.trim()` may fail in
+multiple ways, for example stacking multiple parsers `req.body` may be from a different parser.
+Testing that `req.body` is a string before calling string methods is recommended.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Type     | Default        |
+| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------------- |
+| `defaultCharset` | Specify the default character set for the text content if the charset is not specified in the `Content-Type` header of the request.                                                                                                                                                                                                                                                                                                                                                                                     | String   | `"utf-8"`      |
+| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                 | Boolean  | `true`         |
+| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                              | Mixed    | `"100kb"`      |
+| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `txt`), a mime type (like `text/plain`), or a mime type with a wildcard (like `*/*` or `text/*`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"text/plain"` |
+| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                             | Function | `undefined`    |
+
+</div>
+
+### express.urlencoded([options])
+
+This is a built-in middleware function in Express. It parses incoming requests
+with urlencoded payloads and is based on [body-parser](/en/resources/middleware/body-parser).
+
+Returns middleware that only parses urlencoded bodies and only looks at
+requests where the `Content-Type` header matches the `type` option. This
+parser accepts only UTF-8 encoding of the body and supports automatic
+inflation of `gzip` and `deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`), or `undefined` if
+there was no body to parse, the `Content-Type` was not matched, or an error
+occurred. This object will contain key-value pairs, where the value can be
+a string or array (when `extended` is `false`), or any type (when `extended`
+is `true`).
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The following table describes the properties of the optional `options` object.
+
+<div class="table-scroller" markdown="1">
+
+| Property         | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Type     | Default                               |
+| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------- |
+| `extended`       | This option allows to choose between parsing the URL-encoded data with the `querystring` library (when `false`) or the `qs` library (when `true`). The "extended" syntax allows for rich objects and arrays to be encoded into the URL-encoded format, allowing for a JSON-like experience with URL-encoded. For more information, please [see the qs library](https://www.npmjs.org/package/qs#readme).                                                                                                                                                      | Boolean  | `false`                               |
+| `inflate`        | Enables or disables handling deflated (compressed) bodies; when disabled, deflated bodies are rejected.                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Boolean  | `true`                                |
+| `limit`          | Controls the maximum request body size. If this is a number, then the value specifies the number of bytes; if it is a string, the value is passed to the [bytes](https://www.npmjs.com/package/bytes) library for parsing.                                                                                                                                                                                                                                                                                                                                    | Mixed    | `"100kb"`                             |
+| `parameterLimit` | This option controls the maximum number of parameters that are allowed in the URL-encoded data. If a request contains more parameters than this value, an error will be raised.                                                                                                                                                                                                                                                                                                                                                                               | Number   | `1000`                                |
+| `type`           | This is used to determine what media type the middleware will parse. This option can be a string, array of strings, or a function. If not a function, `type` option is passed directly to the [type-is](https://www.npmjs.org/package/type-is#readme) library and this can be an extension name (like `urlencoded`), a mime type (like `application/x-www-form-urlencoded`), or a mime type with a wildcard (like `*/x-www-form-urlencoded`). If a function, the `type` option is called as `fn(req)` and the request is parsed if it returns a truthy value. | Mixed    | `"application/x-www-form-urlencoded"` |
+| `verify`         | This option, if supplied, is called as `verify(req, res, buf, encoding)`, where `buf` is a `Buffer` of the raw request body and `encoding` is the encoding of the request. The parsing can be aborted by throwing an error.                                                                                                                                                                                                                                                                                                                                   | Function | `undefined`                           |
+| `depth`          | Configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible.                                                                                                                                                                                                                                                                                        | Number   | `32`                                  |
+
+</div>
diff --git a/src/content/api/5x/api/request/index.mdx b/src/content/api/5x/api/request/index.mdx
new file mode 100644
index 0000000000..b5e66fce1f
--- /dev/null
+++ b/src/content/api/5x/api/request/index.mdx
@@ -0,0 +1,605 @@
+---
+title: Request Object
+description: The request object represents the HTTP request and has properties for the request query string, parameters, body, HTTP headers, and so on
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `req` object represents the HTTP request and has properties for the
+request query string, parameters, body, HTTP headers, and so on. In this documentation and by convention,
+the object is always referred to as `req` (and the HTTP response is `res`) but its actual name is determined
+by the parameters to the callback function in which you're working.
+
+For example:
+
+```js
+app.get('/user/:id', (req, res) => {
+  res.send(`user ${req.params.id}`);
+});
+```
+
+But you could just as well have:
+
+```js
+app.get('/user/:id', (request, response) => {
+  response.send(`user ${request.params.id}`);
+});
+```
+
+The `req` object is an enhanced version of Node's own request object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_incomingmessage).
+
+## Properties
+
+The `req` object contains a number of properties that provide information about the HTTP request, such as headers, query parameters, and more.
+
+### req.app
+
+This property holds a reference to the instance of the Express application that is using the middleware.
+
+If you follow the pattern in which you create a module that just exports a middleware function
+and `require()` it in your main file, then the middleware can access the Express instance via `req.app`
+
+For example:
+
+```js
+// index.js
+app.get('/viewdirectory', require('./mymiddleware.js'));
+```
+
+```js
+// mymiddleware.js
+module.exports = (req, res) => {
+  res.send(`The views directory is ${req.app.get('views')}`);
+};
+```
+
+### req.baseUrl
+
+The URL path on which a router instance was mounted.
+
+The `req.baseUrl` property is similar to the [mountpath](#app.mountpath) property of the `app` object,
+except `app.mountpath` returns the matched path pattern(s).
+
+For example:
+
+```js
+const greet = express.Router();
+
+greet.get('/jp', (req, res) => {
+  console.log(req.baseUrl); // /greet
+  res.send('Konichiwa!');
+});
+
+app.use('/greet', greet); // load the router on '/greet'
+```
+
+Even if you use a path pattern or a set of path patterns to load the router,
+the `baseUrl` property returns the matched string, not the pattern(s). In the
+following example, the `greet` router is loaded on two path patterns.
+
+```js
+app.use(['/gre:"param"t', '/hel{l}o'], greet); // load the router on '/gre:"param"t' and '/hel{l}o'
+```
+
+When a request is made to `/greet/jp`, `req.baseUrl` is "/greet". When a request is
+made to `/hello/jp`, `req.baseUrl` is "/hello".
+
+### req.body
+
+Contains key-value pairs of data submitted in the request body.
+By default, it is `undefined`, and is populated when you use body-parsing middleware such
+as [`express.json()`](#express.json) or [`express.urlencoded()`](#express.urlencoded).
+
+<Alert type="warning">
+
+As `req.body`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.body.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The following example shows how to use body-parsing middleware to populate `req.body`.
+
+```js
+const express = require('express');
+
+const app = express();
+
+app.use(express.json()); // for parsing application/json
+app.use(express.urlencoded({ extended: true })); // for parsing application/x-www-form-urlencoded
+
+app.post('/profile', (req, res, next) => {
+  console.log(req.body);
+  res.json(req.body);
+});
+```
+
+### req.cookies
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property is an object that
+contains cookies sent by the request. If the request contains no cookies, it defaults to `{}`.
+
+```js
+// Cookie: name=tj
+console.dir(req.cookies.name);
+// => "tj"
+```
+
+If the cookie has been signed, you have to use [req.signedCookies](#req.signedCookies).
+
+For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
+
+### req.fresh
+
+When the response is still "fresh" in the client's cache `true` is returned, otherwise `false` is returned to indicate that the client cache is now stale and the full response should be sent.
+
+When a client sends the `Cache-Control: no-cache` request header to indicate an end-to-end reload request, this module will return `false` to make handling these requests transparent.
+
+Further details for how cache validation works can be found in the
+[HTTP/1.1 Caching Specification](https://tools.ietf.org/html/rfc7234).
+
+```js
+console.dir(req.fresh);
+// => true
+```
+
+### req.host
+
+Contains the host derived from the `Host` HTTP header.
+
+When the [`trust proxy` setting](/en/api/application/app-set#app.settings.table)
+does not evaluate to `false`, this property will instead get the value
+from the `X-Forwarded-Host` header field. This header can be set by
+the client or by the proxy.
+
+If there is more than one `X-Forwarded-Host` header in the request, the
+value of the first header is used. This includes a single header with
+comma-separated values, in which the first value is used.
+
+```js
+// Host: "example.com:3000"
+console.dir(req.host);
+// => 'example.com:3000'
+
+// Host: "[::1]:3000"
+console.dir(req.host);
+// => '[::1]:3000'
+```
+
+### req.hostname
+
+Contains the hostname derived from the `Host` HTTP header.
+
+When the [`trust proxy` setting](/en/5x/api#trust.proxy.options.table)
+does not evaluate to `false`, this property will instead get the value
+from the `X-Forwarded-Host` header field. This header can be set by
+the client or by the proxy.
+
+If there is more than one `X-Forwarded-Host` header in the request, the
+value of the first header is used. This includes a single header with
+comma-separated values, in which the first value is used.
+
+```js
+// Host: "example.com:3000"
+console.dir(req.hostname);
+// => 'example.com'
+```
+
+### req.ip
+
+Contains the remote IP address of the request.
+
+When the [`trust proxy` setting](/en/5x/api#trust.proxy.options.table) does not evaluate to `false`,
+the value of this property is derived from the left-most entry in the
+`X-Forwarded-For` header. This header can be set by the client or by the proxy.
+
+```js
+console.dir(req.ip);
+// => "127.0.0.1"
+```
+
+### req.ips
+
+When the [`trust proxy` setting](/en/5x/api#trust.proxy.options.table) does not evaluate to `false`,
+this property contains an array of IP addresses
+specified in the `X-Forwarded-For` request header. Otherwise, it contains an
+empty array. This header can be set by the client or by the proxy.
+
+For example, if `X-Forwarded-For` is `client, proxy1, proxy2`, `req.ips` would be
+`["client", "proxy1", "proxy2"]`, where `proxy2` is the furthest downstream.
+
+### req.method
+
+Contains a string corresponding to the HTTP method of the request:
+`GET`, `POST`, `PUT`, and so on.
+
+### req.originalUrl
+
+<Alert type="alert">
+
+`req.url` is not a native Express property, it is inherited from Node's [http
+module](https://nodejs.org/api/http.html#http_message_url).
+
+</Alert>
+
+This property is much like `req.url`; however, it retains the original request URL,
+allowing you to rewrite `req.url` freely for internal routing purposes. For example,
+the "mounting" feature of [app.use()](#app.use) will rewrite `req.url` to strip the mount point.
+
+```js
+// GET /search?q=something
+console.dir(req.originalUrl);
+// => "/search?q=something"
+```
+
+`req.originalUrl` is available both in middleware and router objects, and is a
+combination of `req.baseUrl` and `req.url`. Consider following example:
+
+```js
+// GET 'http://www.example.com/admin/new?sort=desc'
+app.use('/admin', (req, res, next) => {
+  console.dir(req.originalUrl); // '/admin/new?sort=desc'
+  console.dir(req.baseUrl); // '/admin'
+  console.dir(req.path); // '/new'
+  next();
+});
+```
+
+### req.params
+
+This property is an object containing properties mapped to the [named route "parameters"](/en/guide/routing#route-parameters). For example, if you have the route `/user/:name`, then the "name" property is available as `req.params.name`. This object defaults to `Object.create(null)` when using string paths, but remains a standard object with a normal prototype when the path is defined with a regular expression.
+
+```js
+// GET /user/tj
+console.dir(req.params.name);
+// => "tj"
+```
+
+Properties corresponding to wildcard parameters are arrays containing separate path segments split on `/`:
+
+```js
+app.get('/files/*file', (req, res) => {
+  console.dir(req.params.file);
+  // GET /files/note.txt
+  // => [ 'note.txt' ]
+  // GET /files/images/image.png
+  // => [ 'images', 'image.png' ]
+});
+```
+
+When you use a regular expression for the route definition, capture groups are provided as integer keys using `req.params[n]`, where `n` is the n<sup>th</sup> capture group.
+
+```js
+app.use(/^\/file\/(.*)$/, (req, res) => {
+  // GET /file/javascripts/jquery.js
+  console.dir(req.params[0]);
+  // => "javascripts/jquery.js"
+});
+```
+
+Named capturing groups in regular expressions behave like named route parameters. For example the group from `/^\/file\/(?<path>.*)$/` expression is available as `req.params.path`.
+
+If you need to make changes to a key in `req.params`, use the [app.param](/en/5x/api#app.param) handler. Changes are applicable only to [parameters](/en/guide/routing#route-parameters) already defined in the route path.
+
+Any changes made to the `req.params` object in a middleware or route handler will be reset.
+
+<Alert type="info">
+
+Express automatically decodes the values in `req.params` (using `decodeURIComponent`).
+
+</Alert>
+
+### req.path
+
+Contains the path part of the request URL.
+
+```js
+// example.com/users?sort=desc
+console.dir(req.path);
+// => "/users"
+```
+
+<Alert type="info">
+
+When called from a middleware, the mount point is not included in `req.path`. See
+[app.use()](/en/5x/api#app.use) for more details.
+
+</Alert>
+
+### req.protocol
+
+Contains the request protocol string: either `http` or (for TLS requests) `https`.
+
+When the [`trust proxy` setting](#trust.proxy.options.table) does not evaluate to `false`,
+this property will use the value of the `X-Forwarded-Proto` header field if present.
+This header can be set by the client or by the proxy.
+
+```js
+console.dir(req.protocol);
+// => "http"
+```
+
+### req.query
+
+This property is an object containing a property for each query string parameter in the route.
+When [query parser](/en/api/application/app-set#app.settings.table) is set to disabled, it is an empty object `{}`, otherwise it is the result of the configured query parser.
+
+<Alert type="warning">
+
+As `req.query`'s shape is based on user-controlled input, all properties and values in this object
+are untrusted and should be validated before trusting. For example, `req.query.foo.toString()` may
+fail in multiple ways, for example `foo` may not be there or may not be a string, and `toString`
+may not be a function and instead a string or other user-input.
+
+</Alert>
+
+The value of this property can be configured with the [query parser application setting](/en/api/application/app-set#app.settings.table) to work how your application needs it. A very popular query string parser is the [`qs` module](https://www.npmjs.org/package/qs), and this is used by default. The `qs` module is very configurable with many settings, and it may be desirable to use different settings than the default to populate `req.query`:
+
+```js
+const qs = require('qs');
+app.set('query parser', (str) =>
+  qs.parse(str, {
+    /* custom options */
+  })
+);
+```
+
+Check out the [query parser application setting](/en/api/application/app-set#app.settings.table) documentation for other customization options.
+
+### req.res
+
+This property holds a reference to the <a href="#res">response object</a>
+that relates to this request object.
+
+### req.route
+
+Contains the currently-matched route, a string. For example:
+
+```js
+app.get('/user/{:id}', (req, res) => {
+  console.dir(req.route, { depth: null });
+  res.send('GET');
+});
+```
+
+Example output from the previous snippet:
+
+```
+Route {
+  path: '/user/{:id}',
+  stack: [
+    Layer {
+      handle: [Function (anonymous)],
+      keys: [],
+      name: '<anonymous>',
+      params: undefined,
+      path: undefined,
+      slash: false,
+      matchers: [ [Function: match] ],
+      method: 'get'
+    }
+  ],
+  methods: [Object: null prototype] { get: true }
+}
+```
+
+### req.secure
+
+A Boolean property that is true if a TLS connection is established. Equivalent to the following:
+
+{/* <!-- eslint-disable no-unused-expressions --> */}
+
+```js
+req.protocol === 'https';
+```
+
+### req.signedCookies
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this property
+contains signed cookies sent by the request, unsigned and ready for use. Signed cookies reside
+in a different object to show developer intent; otherwise, a malicious attack could be placed on
+`req.cookie` values (which are easy to spoof). Note that signing a cookie does not make it "hidden"
+or encrypted; but simply prevents tampering (because the secret used to sign is private).
+
+If no signed cookies are sent, the property defaults to `{}`.
+
+```js
+// Cookie: user=tobi.CP7AWaXDfAKIRfH49dQzKJx7sKzzSoPq7/AcBBRVwlI3
+console.dir(req.signedCookies.user);
+// => "tobi"
+```
+
+For more information, issues, or concerns, see [cookie-parser](https://github.com/expressjs/cookie-parser).
+
+### req.stale
+
+Indicates whether the request is "stale," and is the opposite of `req.fresh`.
+For more information, see [req.fresh](#req.fresh).
+
+```js
+console.dir(req.stale);
+// => true
+```
+
+### req.subdomains
+
+An array of subdomains in the domain name of the request.
+
+```js
+// Host: "tobi.ferrets.example.com"
+console.dir(req.subdomains);
+// => ["ferrets", "tobi"]
+```
+
+The application property `subdomain offset`, which defaults to 2, is used for determining the
+beginning of the subdomain segments. To change this behavior, change its value
+using [app.set](/en/5x/api#app.set).
+
+### req.xhr
+
+A Boolean property that is `true` if the request's `X-Requested-With` header field is
+"XMLHttpRequest", indicating that the request was issued by a client library such as jQuery.
+
+```js
+console.dir(req.xhr);
+// => true
+```
+
+## Methods
+
+The `req` object also contains a number of methods that can be used to perform various tasks related to the HTTP request, such as checking the content type, retrieving header values, and more.
+
+### req.accepts(types)
+
+Checks if the specified content types are acceptable, based on the request's `Accept` HTTP header field.
+The method returns the best match, or if none of the specified content types is acceptable, returns
+`false` (in which case, the application should respond with `406 "Not Acceptable"`).
+
+The `type` value may be a single MIME type string (such as "application/json"),
+an extension name such as "json", a comma-delimited list, or an array. For a
+list or array, the method returns the _best_ match (if any).
+
+```js
+// Accept: text/html
+req.accepts('html');
+// => "html"
+
+// Accept: text/*, application/json
+req.accepts('html');
+// => "html"
+req.accepts('text/html');
+// => "text/html"
+req.accepts(['json', 'text']);
+// => "json"
+req.accepts('application/json');
+// => "application/json"
+
+// Accept: text/*, application/json
+req.accepts('image/png');
+req.accepts('png');
+// => false
+
+// Accept: text/*;q=.5, application/json
+req.accepts(['html', 'json']);
+// => "json"
+```
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsCharsets(charset [, ...])
+
+Returns the first accepted charset of the specified character sets,
+based on the request's `Accept-Charset` HTTP header field.
+If none of the specified charsets is accepted, returns `false`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsEncodings(encoding [, ...])
+
+Returns the first accepted encoding of the specified encodings,
+based on the request's `Accept-Encoding` HTTP header field.
+If none of the specified encodings is accepted, returns `false`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+### req.acceptsLanguages([lang, ...])
+
+Returns the first accepted language of the specified languages,
+based on the request's `Accept-Language` HTTP header field.
+If none of the specified languages is accepted, returns `false`.
+
+If no `lang` argument is given, then `req.acceptsLanguages()`
+returns all languages from the HTTP `Accept-Language` header
+as an `Array`.
+
+For more information, or if you have issues or concerns, see [accepts](https://github.com/expressjs/accepts).
+
+Express (5.x) source: [request.js line 172](https://github.com/expressjs/express/blob/v5.1.0/lib/request.js#L172)
+
+Accepts (2.0) source: [index.js line 195](https://github.com/jshttp/accepts/blob/2.0.0/index.js#L195)
+
+### req.get(field)
+
+Returns the specified HTTP request header field (case-insensitive match).
+The `Referrer` and `Referer` fields are interchangeable.
+
+```js
+req.get('Content-Type');
+// => "text/plain"
+
+req.get('content-type');
+// => "text/plain"
+
+req.get('Something');
+// => undefined
+```
+
+Aliased as `req.header(field)`.
+
+### req.is(type)
+
+Returns the matching content type if the incoming request's "Content-Type" HTTP header field
+matches the MIME type specified by the `type` parameter. If the request has no body, returns `null`.
+Returns `false` otherwise.
+
+```js
+// With Content-Type: text/html; charset=utf-8
+req.is('html'); // => 'html'
+req.is('text/html'); // => 'text/html'
+req.is('text/*'); // => 'text/*'
+
+// When Content-Type is application/json
+req.is('json'); // => 'json'
+req.is('application/json'); // => 'application/json'
+req.is('application/*'); // => 'application/*'
+
+// Using arrays
+// When Content-Type is application/json
+req.is(['json', 'html']); // => 'json'
+
+// Using multiple arguments
+// When Content-Type is application/json
+req.is('json', 'html'); // => 'json'
+
+req.is('html'); // => false
+req.is(['xml', 'yaml']); // => false
+req.is('xml', 'yaml'); // => false
+```
+
+For more information, or if you have issues or concerns, see [type-is](https://github.com/expressjs/type-is).
+
+### req.range(size[, options])
+
+`Range` header parser.
+
+The `size` parameter is the maximum size of the resource.
+
+The `options` parameter is an object that can have the following properties.
+
+<div class="table-scroller" markdown="1">
+
+| Property  | Type    | Description                                                                                                                                                                           |
+| --------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `combine` | Boolean | Specify if overlapping & adjacent ranges should be combined, defaults to `false`. When `true`, ranges will be combined and returned as if they were specified that way in the header. |
+
+</div>
+
+An array of ranges will be returned or negative numbers indicating an error parsing.
+
+- `-2` signals a malformed header string
+- `-1` signals an unsatisfiable range
+
+```js
+// parse header from request
+const range = req.range(1000);
+
+// the type of the range
+if (range.type === 'bytes') {
+  // the ranges
+  range.forEach((r) => {
+    // do something with r.start and r.end
+  });
+}
+```
diff --git a/src/content/api/5x/api/response/index.mdx b/src/content/api/5x/api/response/index.mdx
new file mode 100644
index 0000000000..b079c7375f
--- /dev/null
+++ b/src/content/api/5x/api/response/index.mdx
@@ -0,0 +1,741 @@
+---
+title: Response
+description: The response object represents the HTTP response that an Express app sends when it gets an HTTP request.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The `res` object represents the HTTP response that an Express app sends when it gets an HTTP request.
+
+In this documentation and by convention,
+the object is always referred to as `res` (and the HTTP request is `req`) but its actual name is determined
+by the parameters to the callback function in which you're working.
+
+For example:
+
+```js
+app.get('/user/:id', (req, res) => {
+  res.send(`user ${req.params.id}`);
+});
+```
+
+But you could just as well have:
+
+```js
+app.get('/user/:id', (request, response) => {
+  response.send(`user ${request.params.id}`);
+});
+```
+
+The `res` object is an enhanced version of Node's own response object
+and supports all [built-in fields and methods](https://nodejs.org/api/http.html#http_class_http_serverresponse).
+
+## Properties
+
+### res.app
+
+This property holds a reference to the instance of the Express application that is using the middleware.
+
+`res.app` is identical to the [req.app](/en/5x/api/request/#req.app) property in the request object.
+
+### res.headersSent
+
+Boolean property that indicates if the app sent HTTP headers for the response.
+
+```js
+app.get('/', (req, res) => {
+  console.log(res.headersSent); // false
+  res.send('OK');
+  console.log(res.headersSent); // true
+});
+```
+
+### res.locals
+
+Use this property to set variables accessible in templates rendered with [res.render](#resrenderview--locals--callback).
+The variables set on `res.locals` are available within a single request-response cycle, and will not
+be shared between requests.
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+In order to keep local variables for use in template rendering between requests, use
+[app.locals](/en/5x/api/application/#app.locals) instead.
+
+This property is useful for exposing request-level information such as the request path name,
+authenticated user, user settings, and so on to templates rendered within the application.
+
+```js
+app.use((req, res, next) => {
+  // Make `user` and `authenticated` available in templates
+  res.locals.user = req.user;
+  res.locals.authenticated = !req.user.anonymous;
+  next();
+});
+```
+
+### res.req
+
+This property holds a reference to the <a href="/en/5x/api/request/">request object</a>
+that relates to this response object.
+
+## Methods
+
+### res.append(field [, value])
+
+Appends the specified `value` to the HTTP response header `field`. If the header is not already set,
+it creates the header with the specified value. The `value` parameter can be a string or an array.
+
+<Alert type="info">
+
+calling `res.set()` after `res.append()` will reset the previously-set header value.
+
+</Alert>
+
+```js
+res.append('Link', ['<http://localhost/>', '<http://localhost:3000/>']);
+res.append('Set-Cookie', 'foo=bar; Path=/; HttpOnly');
+res.append('Warning', '199 Miscellaneous warning');
+```
+
+### res.attachment([filename])
+
+Sets the HTTP response `Content-Disposition` header field to "attachment". If a `filename` is given,
+then it sets the `Content-Type` based on the extension name via `res.type()`,
+and sets the `Content-Disposition` "filename=" parameter.
+
+```js
+res.attachment();
+// Content-Disposition: attachment
+
+res.attachment('path/to/logo.png');
+// Content-Disposition: attachment; filename="logo.png"
+// Content-Type: image/png
+```
+
+### res.clearCookie(name [, options])
+
+Clears the cookie with the specified `name` by sending a `Set-Cookie` header that sets its expiration date in the past.
+This instructs the client that the cookie has expired and is no longer valid. For more information
+about available `options`, see [res.cookie()](#rescookiename-value--options).
+
+<Alert type="alert">The `expires` and `max-age` options are being ignored completely.</Alert>
+
+<Alert type="alert">
+
+Web browsers and other compliant clients will only clear the cookie if the given `options` is
+identical to those given to [res.cookie()](#rescookiename-value--options)
+
+</Alert>
+
+```js
+res.cookie('name', 'tobi', { path: '/admin' });
+res.clearCookie('name', { path: '/admin' });
+```
+
+### res.cookie(name, value [, options])
+
+Sets cookie `name` to `value`. The `value` parameter may be a string or object converted to JSON.
+
+The `options` parameter is an object that can have the following properties.
+
+<div class="table-scroller" markdown="1">
+
+| Property      | Type              | Description                                                                                                                                                                                                                                 |
+| ------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `domain`      | String            | Domain name for the cookie. Defaults to the domain name of the app.                                                                                                                                                                         |
+| `encode`      | Function          | A synchronous function used for cookie value encoding. Defaults to `encodeURIComponent`.                                                                                                                                                    |
+| `expires`     | Date              | Expiry date of the cookie in GMT. If not specified or set to 0, creates a session cookie.                                                                                                                                                   |
+| `httpOnly`    | Boolean           | Flags the cookie to be accessible only by the web server.                                                                                                                                                                                   |
+| `maxAge`      | Number            | Convenient option for setting the expiry time relative to the current time in milliseconds.                                                                                                                                                 |
+| `path`        | String            | Path for the cookie. Defaults to "/".                                                                                                                                                                                                       |
+| `partitioned` | Boolean           | Indicates that the cookie should be stored using partitioned storage. See [Cookies Having Independent Partitioned State (CHIPS)](https://developer.mozilla.org/en-US/docs/Web/Privacy/Partitioned_cookies) for more details.                |
+| `priority`    | String            | Value of the "Priority" **Set-Cookie** attribute.                                                                                                                                                                                           |
+| `secure`      | Boolean           | Marks the cookie to be used with HTTPS only.                                                                                                                                                                                                |
+| `signed`      | Boolean           | Indicates if the cookie should be signed.                                                                                                                                                                                                   |
+| `sameSite`    | Boolean or String | Value of the "SameSite" **Set-Cookie** attribute. More information at [https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1](https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00#section-4.1.1). |
+
+</div>
+
+<Alert type="alert">
+
+All `res.cookie()` does is set the HTTP `Set-Cookie` header with the options provided. Any option
+not specified defaults to the value stated in [RFC 6265](http://tools.ietf.org/html/rfc6265).
+
+</Alert>
+
+For example:
+
+```js
+res.cookie('name', 'tobi', { domain: '.example.com', path: '/admin', secure: true });
+res.cookie('rememberme', '1', { expires: new Date(Date.now() + 900000), httpOnly: true });
+```
+
+You can set multiple cookies in a single response by calling `res.cookie` multiple times, for example:
+
+```js
+res
+  .status(201)
+  .cookie('access_token', `Bearer ${token}`, {
+    expires: new Date(Date.now() + 8 * 3600000), // cookie will be removed after 8 hours
+  })
+  .cookie('test', 'test')
+  .redirect(301, '/admin');
+```
+
+The `encode` option allows you to choose the function used for cookie value encoding.
+Does not support asynchronous functions.
+
+Example use case: You need to set a domain-wide cookie for another site in your organization.
+This other site (not under your administrative control) does not use URI-encoded cookie values.
+
+```js
+// Default encoding
+res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', { domain: 'example.com' });
+// Result: 'some_cross_domain_cookie=http%3A%2F%2Fmysubdomain.example.com; Domain=example.com; Path=/'
+
+// Custom encoding
+res.cookie('some_cross_domain_cookie', 'http://mysubdomain.example.com', {
+  domain: 'example.com',
+  encode: String,
+});
+// Result: 'some_cross_domain_cookie=http://mysubdomain.example.com; Domain=example.com; Path=/;'
+```
+
+The `maxAge` option is a convenience option for setting "expires" relative to the current time in milliseconds.
+The following is equivalent to the second example above.
+
+```js
+res.cookie('rememberme', '1', { maxAge: 900000, httpOnly: true });
+```
+
+You can pass an object as the `value` parameter; it is then serialized as JSON and parsed by `bodyParser()` middleware.
+
+```js
+res.cookie('cart', { items: [1, 2, 3] });
+res.cookie('cart', { items: [1, 2, 3] }, { maxAge: 900000 });
+```
+
+When using [cookie-parser](https://www.npmjs.com/package/cookie-parser) middleware, this method also
+supports signed cookies. Simply include the `signed` option set to `true`.
+Then, `res.cookie()` will use the secret passed to `cookieParser(secret)` to sign the value.
+
+```js
+res.cookie('name', 'tobi', { signed: true });
+```
+
+Later, you may access this value through the [req.signedCookies](/en/5x/api/request/#req.signedCookies) object.
+
+### res.download(path [, filename] [, options] [, fn])
+
+Transfers the file at `path` as an "attachment". Typically, browsers will prompt the user for download.
+By default, the `Content-Disposition` header "filename=" parameter is derived from the `path` argument, but can be overridden with the `filename` parameter.
+If `path` is relative, then it will be based on the current working directory of the process or
+the `root` option, if provided.
+
+<Alert type="warning">
+This API provides access to data on the running file system. Ensure that either (a) the way in
+which the `path` argument was constructed is secure if it contains user input or (b) set the `root`
+option to the absolute path of a directory to contain access within.
+
+When the `root` option is provided, Express will validate that the relative path provided as
+`path` will resolve within the given `root` option.
+
+</Alert>
+
+The following table provides details on the `options` parameter.
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Default  | Availability |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `maxAge`       | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)                                                                                                                                                                                               | 0        | 4.16+        |
+| `root`         | Root directory for relative filenames.                                                                                                                                                                                                                                                                                             |          | 4.18+        |
+| `lastModified` | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.                                                                                                                                                                                                                        | Enabled  | 4.16+        |
+| `headers`      | Object containing HTTP headers to serve with the file. The header `Content-Disposition` will be overridden by the `filename` argument.                                                                                                                                                                                             |          | 4.16+        |
+| `dotfiles`     | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".                                                                                                                                                                                                                                                        | "ignore" | 4.16+        |
+| `acceptRanges` | Enable or disable accepting ranged requests.                                                                                                                                                                                                                                                                                       | `true`   | 4.16+        |
+| `cacheControl` | Enable or disable setting `Cache-Control` response header.                                                                                                                                                                                                                                                                         | `true`   | 4.16+        |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false`  | 4.16+        |
+
+</div>
+
+The method invokes the callback function `fn(err)` when the transfer is complete
+or when an error occurs. If the callback function is specified and an error occurs,
+the callback function must explicitly handle the response process either by
+ending the request-response cycle, or by passing control to the next route.
+
+```js
+res.download('/report-12345.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf');
+
+res.download('/report-12345.pdf', 'report.pdf', (err) => {
+  if (err) {
+    // Handle error, but keep in mind the response may be partially-sent
+    // so check res.headersSent
+  } else {
+    // decrement a download credit, etc.
+  }
+});
+```
+
+### res.end([data[, encoding]][, callback])
+
+Ends the response process. This method actually comes from Node core, specifically the [response.end() method of http.ServerResponse](https://nodejs.org/api/http.html#responseenddata-encoding-callback).
+
+Use to quickly end the response without any data. If you need to respond with data, instead use methods such as [res.send()](#ressendbody) and [res.json()](#resjsonbody).
+
+```js
+res.end();
+res.status(404).end();
+```
+
+### res.format(object)
+
+Performs content-negotiation on the `Accept` HTTP header on the request object, when present.
+It uses [req.accepts()](/en/5x/api/request/#req.accepts) to select a handler for the request, based on the acceptable
+types ordered by their quality values. If the header is not specified, the first callback is invoked.
+When no match is found, the server responds with 406 "Not Acceptable", or invokes the `default` callback.
+
+The `Content-Type` response header is set when a callback is selected. However, you may alter
+this within the callback using methods such as `res.set()` or `res.type()`.
+
+The following example would respond with `{ "message": "hey" }` when the `Accept` header field is set
+to "application/json" or "\*/json" (however, if it is "\*/\*", then the response will be "hey").
+
+```js
+res.format({
+  'text/plain'() {
+    res.send('hey');
+  },
+
+  'text/html'() {
+    res.send('<p>hey</p>');
+  },
+
+  'application/json'() {
+    res.send({ message: 'hey' });
+  },
+
+  default() {
+    // log the request and respond with 406
+    res.status(406).send('Not Acceptable');
+  },
+});
+```
+
+In addition to canonicalized MIME types, you may also use extension names mapped
+to these types for a slightly less verbose implementation:
+
+```js
+res.format({
+  text() {
+    res.send('hey');
+  },
+
+  html() {
+    res.send('<p>hey</p>');
+  },
+
+  json() {
+    res.send({ message: 'hey' });
+  },
+});
+```
+
+### res.get(field)
+
+Returns the HTTP response header specified by `field`.
+The match is case-insensitive.
+
+```js
+res.get('Content-Type');
+// => "text/plain"
+```
+
+### res.json([body])
+
+Sends a JSON response. This method sends a response (with the correct content-type) that is the parameter converted to a
+JSON string using [JSON.stringify()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify).
+
+The parameter can be any JSON type, including object, array, string, Boolean, number, or null,
+and you can also use it to convert other values to JSON.
+
+```js
+res.json(null);
+res.json({ user: 'tobi' });
+res.status(500).json({ error: 'message' });
+```
+
+### res.jsonp([body])
+
+Sends a JSON response with JSONP support. This method is identical to `res.json()`,
+except that it opts-in to JSONP callback support.
+
+```js
+res.jsonp(null);
+// => callback(null)
+
+res.jsonp({ user: 'tobi' });
+// => callback({ "user": "tobi" })
+
+res.status(500).jsonp({ error: 'message' });
+// => callback({ "error": "message" })
+```
+
+By default, the JSONP callback name is simply `callback`. Override this with the
+
+<a href="/api/application/app-settings/">jsonp callback name</a> setting.
+
+The following are some examples of JSONP responses using the same code:
+
+```js
+// ?callback=foo
+res.jsonp({ user: 'tobi' });
+// => foo({ "user": "tobi" })
+
+app.set('jsonp callback name', 'cb');
+
+// ?cb=foo
+res.status(500).jsonp({ error: 'message' });
+// => foo({ "error": "message" })
+```
+
+### res.links(links)
+
+Joins the `links` provided as properties of the parameter to populate the response's
+`Link` HTTP header field.
+
+For example, the following call:
+
+```js
+res.links({
+  next: 'http://api.example.com/users?page=2',
+  last: 'http://api.example.com/users?page=5',
+});
+```
+
+Yields the following results:
+
+```
+Link: <http://api.example.com/users?page=2>; rel="next",
+      <http://api.example.com/users?page=5>; rel="last"
+```
+
+### res.location(path)
+
+Sets the response `Location` HTTP header to the specified `path` parameter.
+
+```js
+res.location('/foo/bar');
+res.location('http://example.com');
+```
+
+<Alert type="warning">
+After encoding the URL, if not encoded already, Express passes the specified URL to the browser in the `Location` header,
+without any validation.
+
+Browsers take the responsibility of deriving the intended URL from the current URL
+or the referring URL, and the URL specified in the `Location` header; and redirect the user accordingly.
+
+</Alert>
+
+### res.redirect([status,] path)
+
+Redirects to the URL derived from the specified `path`, with specified `status`, a positive integer
+that corresponds to an [HTTP status code](https://www.rfc-editor.org/rfc/rfc9110#name-status-codes).
+If not specified, `status` defaults to `302 "Found"`.
+
+```js
+res.redirect('/foo/bar');
+res.redirect('http://example.com');
+res.redirect(301, 'http://example.com');
+res.redirect('../login');
+```
+
+Redirects can be a fully-qualified URL for redirecting to a different site:
+
+```js
+res.redirect('http://google.com');
+```
+
+Redirects can be relative to the root of the host name. For example, if the
+application is on `http://example.com/admin/post/new`, the following
+would redirect to the URL `http://example.com/admin`:
+
+```js
+res.redirect('/admin');
+```
+
+Redirects can be relative to the current URL. For example,
+from `http://example.com/blog/admin/` (notice the trailing slash), the following
+would redirect to the URL `http://example.com/blog/admin/post/new`.
+
+```js
+res.redirect('post/new');
+```
+
+Redirecting to `post/new` from `http://example.com/blog/admin` (no trailing slash),
+will redirect to `http://example.com/blog/post/new`.
+
+If you found the above behavior confusing, think of path segments as directories
+(with trailing slashes) and files, it will start to make sense.
+
+Path-relative redirects are also possible. If you were on
+`http://example.com/admin/post/new`, the following would redirect to
+`http://example.com/admin/post`:
+
+```js
+res.redirect('..');
+```
+
+See also [Security best practices: Prevent open redirect
+vulnerabilities](http://expressjs.com/en/advanced/best-practice-security#prevent-open-redirects).
+
+### res.render(view [, locals] [, callback])
+
+Renders a `view` and sends the rendered HTML string to the client.
+Optional parameters:
+
+- `locals`, an object whose properties define local variables for the view.
+- `callback`, a callback function. If provided, the method returns both the possible error and rendered string, but does not perform an automated response. When an error occurs, the method invokes `next(err)` internally.
+
+The `view` argument is a string that is the file path of the view file to render. This can be an absolute path, or a path relative to the `views` setting. If the path does not contain a file extension, then the `view engine` setting determines the file extension. If the path does contain a file extension, then Express will load the module for the specified template engine (via `require()`) and render it using the loaded module's `__express` function.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+<Alert type="warning">
+
+The `view` argument performs file system operations like reading a file from disk and evaluating
+Node.js modules, and as so for security reasons should not contain input from the end-user.
+
+</Alert>
+
+<Alert type="warning">
+
+The `locals` object is used by view engines to render a response. The object keys may be
+particularly sensitive and should not contain user-controlled input, as it may affect the
+operation of the view engine or provide a path to cross-site scripting. Consult the documentation
+for the used view engine for additional considerations.
+
+</Alert>
+
+<Alert type="alert">
+
+The local variable `cache` enables view caching. Set it to `true`, to cache the view during
+development; view caching is enabled in production by default.
+
+</Alert>
+
+```js
+// send the rendered view to the client
+res.render('index');
+
+// if a callback is specified, the rendered HTML string has to be sent explicitly
+res.render('index', (err, html) => {
+  res.send(html);
+});
+
+// pass a local variable to the view
+res.render('user', { name: 'Tobi' }, (err, html) => {
+  // ...
+});
+```
+
+### res.send([body])
+
+Sends the HTTP response.
+
+The `body` parameter can be a `Buffer` object, a `String`, an object, `Boolean`, or an `Array`.
+For example:
+
+```js
+res.send(Buffer.from('whoop'));
+res.send({ some: 'json' });
+res.send('<p>some html</p>');
+res.status(404).send('Sorry, we cannot find that!');
+res.status(500).send({ error: 'something blew up' });
+```
+
+This method performs many useful tasks for simple non-streaming responses:
+For example, it automatically assigns the `Content-Length` HTTP response header field
+and provides automatic HEAD and HTTP cache freshness support.
+
+When the parameter is a `Buffer` object, the method sets the `Content-Type`
+response header field to "application/octet-stream", unless previously defined as shown below:
+
+```js
+res.set('Content-Type', 'text/html');
+res.send(Buffer.from('<p>some html</p>'));
+```
+
+When the parameter is a `String`, the method sets the `Content-Type` to "text/html":
+
+```js
+res.send('<p>some html</p>');
+```
+
+When the parameter is an `Array` or `Object`, Express responds with the JSON representation:
+
+```js
+res.send({ user: 'tobi' });
+res.send([1, 2, 3]);
+```
+
+### res.sendFile(path [, options] [, fn])
+
+Transfers the file at the given `path`. Sets the `Content-Type` response HTTP header field
+based on the filename's extension. Unless the `root` option is set in
+the options object, `path` must be an absolute path to the file.
+
+<Alert type="warning">
+This API provides access to data on the running file system. Ensure that either (a) the way in
+which the `path` argument was constructed into an absolute path is secure if it contains user
+input or (b) set the `root` option to the absolute path of a directory to contain access within.
+
+When the `root` option is provided, the `path` argument is allowed to be a relative path,
+including containing `..`. Express will validate that the relative path provided as `path` will
+resolve within the given `root` option.
+
+</Alert>
+
+The following table provides details on the `options` parameter.
+
+<div class="table-scroller" markdown="1">
+
+| Property       | Description                                                                                                                                                                                                                                                                                                                        | Default  | Availability |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------ |
+| `maxAge`       | Sets the max-age property of the `Cache-Control` header in milliseconds or a string in [ms format](https://www.npmjs.org/package/ms)                                                                                                                                                                                               | 0        |              |
+| `root`         | Root directory for relative filenames.                                                                                                                                                                                                                                                                                             |          |              |
+| `lastModified` | Sets the `Last-Modified` header to the last modified date of the file on the OS. Set `false` to disable it.                                                                                                                                                                                                                        | Enabled  | 4.9.0+       |
+| `headers`      | Object containing HTTP headers to serve with the file.                                                                                                                                                                                                                                                                             |          |              |
+| `dotfiles`     | Option for serving dotfiles. Possible values are "allow", "deny", "ignore".                                                                                                                                                                                                                                                        | "ignore" | &nbsp;       |
+| `acceptRanges` | Enable or disable accepting ranged requests.                                                                                                                                                                                                                                                                                       | `true`   | 4.14+        |
+| `cacheControl` | Enable or disable setting `Cache-Control` response header.                                                                                                                                                                                                                                                                         | `true`   | 4.14+        |
+| `immutable`    | Enable or disable the `immutable` directive in the `Cache-Control` response header. If enabled, the `maxAge` option should also be specified to enable caching. The `immutable` directive will prevent supported clients from making conditional requests during the life of the `maxAge` option to check if the file has changed. | `false`  | 4.16+        |
+
+</div>
+
+The method invokes the callback function `fn(err)` when the transfer is complete
+or when an error occurs. If the callback function is specified and an error occurs,
+the callback function must explicitly handle the response process either by
+ending the request-response cycle, or by passing control to the next route.
+
+Here is an example of using `res.sendFile` with all its arguments.
+
+```js
+app.get('/file/:name', (req, res, next) => {
+  const options = {
+    root: path.join(__dirname, 'public'),
+    dotfiles: 'deny',
+    headers: {
+      'x-timestamp': Date.now(),
+      'x-sent': true,
+    },
+  };
+
+  const fileName = req.params.name;
+  res.sendFile(fileName, options, (err) => {
+    if (err) {
+      next(err);
+    } else {
+      console.log('Sent:', fileName);
+    }
+  });
+});
+```
+
+The following example illustrates using
+`res.sendFile` to provide fine-grained support for serving files:
+
+```js
+app.get('/user/:uid/photos/:file', (req, res) => {
+  const uid = req.params.uid;
+  const file = req.params.file;
+
+  req.user.mayViewFilesFrom(uid, (yes) => {
+    if (yes) {
+      res.sendFile(`/uploads/${uid}/${file}`);
+    } else {
+      res.status(403).send("Sorry! You can't see that.");
+    }
+  });
+});
+```
+
+For more information, or if you have issues or concerns, see [send](https://github.com/pillarjs/send).
+
+### res.sendStatus(statusCode)
+
+Sets the response HTTP status code to `statusCode` and sends the registered status message as the text response body. If an unknown status code is specified, the response body will just be the code number.
+
+```js
+res.sendStatus(404);
+```
+
+<Alert type="alert">
+
+Some versions of Node.js will throw when `res.statusCode` is set to an invalid HTTP status code
+(outside of the range `100` to `599`). Consult the HTTP server documentation for the Node.js
+version being used.
+
+</Alert>
+
+[More about HTTP Status Codes](http://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
+
+### res.set(field [, value])
+
+Sets the response's HTTP header `field` to `value`.
+To set multiple fields at once, pass an object as the parameter.
+
+```js
+res.set('Content-Type', 'text/plain');
+
+res.set({
+  'Content-Type': 'text/plain',
+  'Content-Length': '123',
+  ETag: '12345',
+});
+```
+
+Aliased as `res.header(field [, value])`.
+
+### res.status(code)
+
+Sets the HTTP status for the response.
+It is a chainable alias of Node's [response.statusCode](https://nodejs.org/api/http.html#http_response_statuscode).
+
+```js
+res.status(403).end();
+res.status(400).send('Bad Request');
+res.status(404).sendFile('/absolute/path/to/404.png');
+```
+
+### res.type(type)
+
+Sets the `Content-Type` HTTP header to the MIME type as determined by the specified `type`. If `type` contains the "/" character, then it sets the `Content-Type` to the exact value of `type`, otherwise it is assumed to be a file extension and the MIME type is looked up using the `contentType()` method of the `mime-types` package.
+
+```js
+res.type('.html'); // => 'text/html'
+res.type('html'); // => 'text/html'
+res.type('json'); // => 'application/json'
+res.type('application/json'); // => 'application/json'
+res.type('png'); // => image/png:
+```
+
+Aliased as `res.contentType(type)`.
+
+### res.vary(field)
+
+Adds the field to the `Vary` response header, if it is not there already.
+
+```js
+res.vary('User-Agent').render('docs');
+```
diff --git a/src/content/api/5x/api/router/index.mdx b/src/content/api/5x/api/router/index.mdx
new file mode 100644
index 0000000000..dbaa9585c3
--- /dev/null
+++ b/src/content/api/5x/api/router/index.mdx
@@ -0,0 +1,371 @@
+---
+title: Router
+description: A router object is an isolated instance of middleware and routes in Express 5.x.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A `router` object is an instance of middleware and routes. You can think of it
+as a "mini-application," capable only of performing middleware and routing
+functions. Every Express application has a built-in app router.
+
+A router behaves like middleware itself, so you can use it as an argument to
+[app.use()](/en/5x/api/application#app-use) or as the argument to another router's [use()](#router-use) method.
+
+The top-level `express` object has a [Router()](/en/5x/api/express#express-router) method that creates a new `router` object.
+
+Once you've created a router object, you can add middleware and HTTP method routes (such as `get`, `put`, `post`,
+and so on) to it just like an application. For example:
+
+```js
+// invoked for any requests passed to this router
+router.use((req, res, next) => {
+  // .. some logic here .. like any other middleware
+  next();
+});
+
+// will handle any request that ends in /events
+// depends on where the router is "use()'d"
+router.get('/events', (req, res, next) => {
+  // ..
+});
+```
+
+You can then use a router for a particular root URL in this way separating your routes into files or even mini-apps.
+
+```js
+// only requests to /calendar/* will be sent to our "router"
+app.use('/calendar', router);
+```
+
+## Methods
+
+### Router([options])
+
+### router.all(path, [callback, ...] callback)
+
+This method is just like the `router.METHOD()` methods, except that it matches all HTTP methods (verbs).
+
+This method is extremely useful for
+mapping "global" logic for specific path prefixes or arbitrary matches.
+For example, if you placed the following route at the top of all other
+route definitions, it would require that all routes from that point on
+would require authentication, and automatically load a user. Keep in mind
+that these callbacks do not have to act as end points; `loadUser`
+can perform a task, then call `next()` to continue matching subsequent
+routes.
+
+```js
+router.all('{*splat}', requireAuthentication, loadUser);
+```
+
+Or the equivalent:
+
+```js
+router.all('{*splat}', requireAuthentication);
+router.all('{*splat}', loadUser);
+```
+
+Another example of this is white-listed "global" functionality. Here,
+the example is much like before, but it only restricts paths prefixed with
+"/api":
+
+```js
+router.all('/api/{*splat}', requireAuthentication);
+```
+
+### router.METHOD(path, [callback, ...] callback)
+
+The `router.METHOD()` methods provide the routing functionality in Express,
+where METHOD is one of the HTTP methods, such as GET, PUT, POST, and so on,
+in lowercase. Thus, the actual methods are `router.get()`, `router.post()`,
+`router.put()`, and so on.
+
+<Alert type="info">
+
+The `router.get()` function is automatically called for the HTTP `HEAD` method in addition to the
+`GET` method if `router.head()` was not called for the path before `router.get()`.
+
+</Alert>
+
+You can provide multiple callbacks, and all are treated equally, and behave just
+like middleware, except that these callbacks may invoke `next('route')`
+to bypass the remaining route callback(s). You can use this mechanism to perform
+pre-conditions on a route then pass control to subsequent routes when there is no
+reason to proceed with the route matched.
+
+The following snippet illustrates the most simple route definition possible.
+Express translates the path strings to regular expressions, used internally
+to match incoming requests. Query strings are _not_ considered when performing
+these matches, for example "GET /" would match the following route, as would
+"GET /?name=tobi".
+
+```js
+router.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+You can also use regular expressions&mdash;useful if you have very specific
+constraints, for example the following would match "GET /commits/71dbb9c" as well
+as "GET /commits/71dbb9c..4c084f9".
+
+```js
+router.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, (req, res) => {
+  const from = req.params[0];
+  const to = req.params[1] || 'HEAD';
+  res.send(`commit range ${from}..${to}`);
+});
+```
+
+You can use `next` primitive to implement a flow control between different
+middleware functions, based on a specific program state. Invoking `next` with
+the string `'router'` will cause all the remaining route callbacks on that router
+to be bypassed.
+
+The following example illustrates `next('router')` usage.
+
+```js
+function fn(req, res, next) {
+  console.log('I come here');
+  next('router');
+}
+router.get('/foo', fn, (req, res, next) => {
+  console.log('I dont come here');
+});
+router.get('/foo', (req, res, next) => {
+  console.log('I dont come here');
+});
+app.get('/foo', (req, res) => {
+  console.log(' I come here too');
+  res.end('good');
+});
+```
+
+### router.param(name, callback)
+
+Adds callback triggers to route parameters, where `name` is the name of the parameter and `callback` is the callback function. The `name` parameter is required.
+
+The parameters of the callback function are:
+
+- `req`, the request object.
+- `res`, the response object.
+- `next`, indicating the next middleware function.
+- The value of the `name` parameter.
+- The name of the parameter.
+
+<Alert type="info">
+
+Unlike `app.param()`, `router.param()` does not accept an array of route parameters.
+
+</Alert>
+
+For example, when `:user` is present in a route path, you may map user loading logic to automatically provide `req.user` to the route, or perform validations on the parameter input.
+
+```js
+router.param('user', (req, res, next, id) => {
+  // try to get the user details from the User model and attach it to the request object
+  User.find(id, (err, user) => {
+    if (err) {
+      next(err);
+    } else if (user) {
+      req.user = user;
+      next();
+    } else {
+      next(new Error('failed to load user'));
+    }
+  });
+});
+```
+
+Param callback functions are local to the router on which they are defined. They are not inherited by mounted apps or routers, nor are they triggered for route parameters inherited from parent routers. Hence, param callbacks defined on `router` will be triggered only by route parameters defined on `router` routes.
+
+A param callback will be called only once in a request-response cycle, even if the parameter is matched in multiple routes, as shown in the following examples.
+
+```js
+router.param('id', (req, res, next, id) => {
+  console.log('CALLED ONLY ONCE');
+  next();
+});
+
+router.get('/user/:id', (req, res, next) => {
+  console.log('although this matches');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  console.log('and this matches too');
+  res.end();
+});
+```
+
+On `GET /user/42`, the following is printed:
+
+```
+CALLED ONLY ONCE
+although this matches
+and this matches too
+```
+
+### router.route(path)
+
+Returns an instance of a single route which you can then use to handle HTTP verbs
+with optional middleware. Use `router.route()` to avoid duplicate route naming and
+thus typing errors.
+
+Building on the `router.param()` example above, the following code shows how to use
+`router.route()` to specify various HTTP method handlers.
+
+```js
+const router = express.Router();
+
+router.param('user_id', (req, res, next, id) => {
+  // sample user, would actually fetch from DB, etc...
+  req.user = {
+    id,
+    name: 'TJ',
+  };
+  next();
+});
+
+router
+  .route('/users/:user_id')
+  .all((req, res, next) => {
+    // runs for all HTTP verbs first
+    // think of it as route specific middleware!
+    next();
+  })
+  .get((req, res, next) => {
+    res.json(req.user);
+  })
+  .put((req, res, next) => {
+    // just an example of maybe updating the user
+    req.user.name = req.params.name;
+    // save user ... etc
+    res.json(req.user);
+  })
+  .post((req, res, next) => {
+    next(new Error('not implemented'));
+  })
+  .delete((req, res, next) => {
+    next(new Error('not implemented'));
+  });
+```
+
+This approach re-uses the single `/users/:user_id` path and adds handlers for
+various HTTP methods.
+
+<Alert type="info">
+
+When you use `router.route()`, middleware ordering is based on when the _route_ is created, not
+when method handlers are added to the route. For this purpose, you can consider method handlers to
+belong to the route to which they were added.
+
+</Alert>
+
+### router.use([path], [function, ...] function)
+
+Uses the specified middleware function or functions, with optional mount path `path`, that defaults to "/".
+
+This method is similar to [app.use()](/en/5x/api/application#app-use). A simple example and use case is described below.
+See [app.use()](/en/5x/api/application#app-use) for more information.
+
+Middleware is like a plumbing pipe: requests start at the first middleware function defined
+and work their way "down" the middleware stack processing for each path they match.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// simple logger for this router's requests
+// all requests to this router will first hit this middleware
+router.use((req, res, next) => {
+  console.log('%s %s %s', req.method, req.url, req.path);
+  next();
+});
+
+// this will only be invoked if the path starts with /bar from the mount point
+router.use('/bar', (req, res, next) => {
+  // ... maybe some additional /bar logging ...
+  next();
+});
+
+// always invoked
+router.use((req, res, next) => {
+  res.send('Hello World');
+});
+
+app.use('/foo', router);
+
+app.listen(3000);
+```
+
+The "mount" path is stripped and is _not_ visible to the middleware function.
+The main effect of this feature is that a mounted middleware function may operate without
+code changes regardless of its "prefix" pathname.
+
+The order in which you define middleware with `router.use()` is very important.
+They are invoked sequentially, thus the order defines middleware precedence. For example,
+usually a logger is the very first middleware you would use, so that every request gets logged.
+
+```js
+const logger = require('morgan');
+
+router.use(logger());
+router.use(express.static(path.join(__dirname, 'public')));
+router.use((req, res) => {
+  res.send('Hello');
+});
+```
+
+Now suppose you wanted to ignore logging requests for static files, but to continue
+logging routes and middleware defined after `logger()`. You would simply move the call to `express.static()` to the top,
+before adding the logger middleware:
+
+```js
+router.use(express.static(path.join(__dirname, 'public')));
+router.use(logger());
+router.use((req, res) => {
+  res.send('Hello');
+});
+```
+
+Another example is serving files from multiple directories,
+giving precedence to "./public" over the others:
+
+```js
+app.use(express.static(path.join(__dirname, 'public')));
+app.use(express.static(path.join(__dirname, 'files')));
+app.use(express.static(path.join(__dirname, 'uploads')));
+```
+
+The `router.use()` method also supports named parameters so that your mount points
+for other routers can benefit from preloading using named parameters.
+
+**NOTE**: Although these middleware functions are added via a particular router, _when_
+they run is defined by the path they are attached to (not the router). Therefore,
+middleware added via one router may run for other routers if its routes
+match. For example, this code shows two different routers mounted on the same path:
+
+```js
+const authRouter = express.Router();
+const openRouter = express.Router();
+
+authRouter.use(require('./authenticate').basic(usersdb));
+
+authRouter.get('/:user_id/edit', (req, res, next) => {
+  // ... Edit user UI ...
+});
+openRouter.get('/', (req, res, next) => {
+  // ... List users ...
+});
+openRouter.get('/:user_id', (req, res, next) => {
+  // ... View user ...
+});
+
+app.use('/users', authRouter);
+app.use('/users', openRouter);
+```
+
+Even though the authentication middleware was added via the `authRouter` it will run on the routes defined by the `openRouter` as well since both routers were mounted on `/users`. To avoid this behavior, use different paths for each router.
diff --git a/src/content/blog/2024-07-16-welcome-post.md b/src/content/blog/2024-07-16-welcome-post.md
new file mode 100644
index 0000000000..b40f8efc78
--- /dev/null
+++ b/src/content/blog/2024-07-16-welcome-post.md
@@ -0,0 +1,30 @@
+---
+title: Welcome to The Express Blog!
+description: Introducing the new Express blog — a primary platform for announcements, updates, and communication from the Express technical committee.
+tags: ['announcements']
+authors:
+  - name: Rand McKinney
+    github: crandmck
+  - name: Chris Del
+    github: chrisdel101
+---
+
+Welcome to the new Express blog! The blog is meant to be a primary means of communication for the Express technical committee (TC). While we currently have other channels such as X, LinkedIn, and of course GitHub, there's no authoritative "soapbox" for announcements and general communication.
+
+Initially, the Express blog will be a venue:
+
+- For periodic announcements of new releases, pre-releases, plans, and ongoing work on the project.
+- For the Express TC to discuss issues of particular importance to the Express community.
+- To highlight security issues or other urgent information.
+
+Eventually, we hope the blog will evolve into a more general communication hub for the entire Express community; for example to share examples, tips, and experiences with the Express ecosystem and other information that's not simply technical documentation or GitHub discussion.
+
+Initially, posts will be written by TC members (potentially collaborating others), mainly because we don't have bandwidth to review general posts from the broader community. Eventually, we would love to open up the blog for broader contributions, but for now the focus is on trying to release Express 5.0, and the reality of an open-source project is that everyone has finite time to contribute.
+
+Express TC member [Ulises Gascón](https://github.com/UlisesGascon) suggested a number of interesting topics for blog posts in [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500), but there are undoubtedly many others.
+
+<!-- TODO: add the new link  for instructions to create a blog post -->
+
+If you have an idea for a post, feel free to pitch the idea! You can add a comment to [expressjs.com issue 1500](https://github.com/expressjs/expressjs.com/issues/1500) or open a new issue, and then after appropriate discussion, open a PR. We've also written up simple instructions to create a blog post.
+
+Happy blogging!
diff --git a/src/content/blog/2024-09-29-security-releases.mdx b/src/content/blog/2024-09-29-security-releases.mdx
new file mode 100644
index 0000000000..a18e0e08f6
--- /dev/null
+++ b/src/content/blog/2024-09-29-security-releases.mdx
@@ -0,0 +1,142 @@
+---
+title: September 2024 Security Releases
+description: Security releases for Express, body-parser, send, serve-static, and path-to-regexp have been published. We recommend that all users upgrade as soon as possible.
+tags: ['security']
+authors:
+  - name: Ulises Gascón
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Recently, the Express team has been made aware of a number of security vulnerabilities in the Express project. We have released a number of patches to address these vulnerabilities.
+
+<Alert type="warning">
+  We strongly recommend that you upgrade these modules to the recommended (or latest) version as
+  soon as possible.
+</Alert>
+
+The following vulnerabilities have been addressed:
+
+- [High severity vulnerability CVE-2024-45590 in body-parser middleware](#high-severity-vulnerability-cve-2024-45590-in-body-parser-middleware)
+- [High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware](#high-severity-vulnerability-cve-2024-47178-in-basic-auth-connect-middleware)
+- [Moderate severity vulnerability CVE-2024-43796 in Express core](#moderate-severity-vulnerability-cve-2024-43796-in-express-core)
+- [Moderate severity vulnerability CVE-2024-43799 in send utility module](#moderate-severity-vulnerability-cve-2024-43799-in-send-utility-module)
+- [Moderate severity vulnerability CVE-2024-43800 in serve-static middleware](#moderate-severity-vulnerability-cve-2024-43800-in-serve-static-middleware)
+- [Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module](#moderate-severity-vulnerability-cve-2024-45296-in-path-to-regexp-utility-module)
+
+## High severity vulnerability CVE-2024-45590 in body-parser middleware
+
+**[body-parser](https://www.npmjs.com/package/body-parser) version `<1.20.3` is vulnerable to denial of service when URL-encoding is enabled**
+
+A malicious actor using a specially-crafted payload could flood the server with a large number of requests, resulting in denial of service.
+
+**Affected versions**: `<1.20.3`
+
+**Patched versions**: `>=1.20.3`
+
+This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-qwcr-r2fm-qrc7](https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7).
+
+## High severity vulnerability CVE-2024-47178 in basic-auth-connect middleware
+
+**[basic-auth-connect](https://www.npmjs.com/package/basic-auth-connect) uses a timing-unsafe equality comparison**
+
+basic-auth-connect `<1.1.0` uses a timing-unsafe equality comparison that can leak timing information
+
+**Affected versions**
+
+- `<1.1.0`
+
+**Patched versions**
+
+- `>=1.1.0`
+
+This vulnerability was discovered during the [OSTIF audit to Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express Securty triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+More details area available in [GHSA-7p89-p6hx-q4fw](https://github.com/expressjs/basic-auth-connect/security/advisories/GHSA-7p89-p6hx-q4fw)
+
+## Moderate severity vulnerability CVE-2024-43796 in Express core
+
+The core **[express](https://www.npmjs.com/package/express) package is vulnerable to cross-site scripting (XSS) attack via `response.redirect()`**.
+
+In Express version `<4.20.0`, passing untrusted user input&mdash;even after sanitizing it&mdash;to `response.redirect()` may execute untrusted code.
+
+**Affected versions**:
+
+- `<4.20.0`
+- `>=5.0.0-alpha.1`, `<5.0.0`
+
+**Patched versions**:
+
+- `>=4.20.0`
+- `>=5.0.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-qw6h-vgh9-j6wx](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx).
+
+## Moderate severity vulnerability CVE-2024-43799 in send utility module
+
+The **[send](https://www.npmjs.com/package/send) utility module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
+
+Passing untrusted user input&mdash;even after sanitizing it&mdash;to `SendStream.redirect()` can execute untrusted code.
+
+**Affected versions**: `< 0.19.0`
+
+**Patched versions**: `>=0.19.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-m6fv-jmcg-4jfg](https://github.com/pillarjs/send/security/advisories/GHSA-m6fv-jmcg-4jfg).
+
+## Moderate severity vulnerability CVE-2024-43800 in serve-static middleware
+
+The **[serve-static](https://www.npmjs.com/package/serve-static) middleware module is vulnerable to template injection that can lead to vulnerability to cross-site scripting (XSS) attack**.
+
+Passing untrusted user input&mdash;even after sanitizing it&mdash;to `redirect()` can execute untrusted code.
+
+**Affected versions**:
+
+- `< 1.16.0`
+- `>=2.0.0`, `<2.1.0`
+
+**Patched versions**:
+
+- `>=1.16.0`
+- `>=2.1.0`
+
+This vulnerability was discovered during the [OSTIF audit of Express](https://github.com/expressjs/security-wg/issues/6) and was mitigated by [the Express security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team).
+
+For more details, see [GHSA-cm22-4g7w-348p](https://github.com/expressjs/serve-static/security/advisories/GHSA-cm22-4g7w-348p)
+
+## Moderate severity vulnerability CVE-2024-45296 in path-to-regexp utility module
+
+The **[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) utility module is vulnerable to regular expression denial of service (ReDoS) attack**.
+
+A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (`.`). For example, `/:a-:b`.
+
+Using `/:a-:b` will produce the regular expression `/^\/([^\/]+?)-([^\/]+?)\/?$/`. This can be exploited by a path such as `/a${'-a'.repeat(8_000)}/a`. [OWASP](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) has a good example of why this occurs, but in essence, the `/a` at the end ensures this route would never match, but due to naive backtracking it will still attempt every combination of the `:a-:b` on the repeated 8,000 `-a`.
+
+Because JavaScript is single-threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment, using Express v4 and ten concurrent connections results in an average latency of ~600ms vs 1ms.
+
+**Affected versions**:
+
+- `>=4.0.0`, `<8.0.0`
+- `>=0.2.0`, `<1.9.0`
+- `<0.1.10`
+- `>=2.0.0`, `<3.3.0`
+- `>=4.0.0`, `<6.3.0`
+
+**Patched versions**:
+
+- `>=8.0.0`
+- `>=1.9.0`
+- `>=0.1.10`
+- `>=3.3.0`
+- `>=6.3.0`
+
+Thanks to [Blake Embrey](https://github.com/blakeembrey) who reported and created the security patch.
+
+For more details, see [GHSA-9wv6-86v2-598j](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j)
diff --git a/_posts/2024-10-01-HeroDevs-partnership-announcement.md b/src/content/blog/2024-10-01-HeroDevs-partnership-announcement.md
similarity index 95%
rename from _posts/2024-10-01-HeroDevs-partnership-announcement.md
rename to src/content/blog/2024-10-01-HeroDevs-partnership-announcement.md
index 9ae9dac7a1..11048603df 100644
--- a/_posts/2024-10-01-HeroDevs-partnership-announcement.md
+++ b/src/content/blog/2024-10-01-HeroDevs-partnership-announcement.md
@@ -1,7 +1,7 @@
 ---
 title: Express Never Ending Support Launched by HeroDevs and Express.js
 description: The Express.js team is pleased to announce a partnership with HeroDevs to launch Express Never-Ending Support (NES), providing long-term support for applications built with legacy Express. This collaboration ensures that developers relying on older versions of the framework will continue to receive critical security and compatibility updates, allowing them to maintain and scale their applications securely, even after the framework's official end-of-life.
-tags: partnerships announcements
+tags: ['announcements']
 authors:
   - name: Express Technical Committee
     github: expressjs
@@ -11,11 +11,11 @@ The Express.js team is pleased to announce a partnership with HeroDevs to launch
 
 Express.js is known for its minimalistic design and flexibility, offering developers a powerful yet lightweight framework for building web and mobile applications. Its extensive set of HTTP utility methods and middleware have made creating APIs both efficient and scalable—qualities that have made it a go-to choice for Node.js developers over the years.
 
-However, Express.js v3.x reached its end-of-life in July 2015, leaving many businesses and developers in need of support to keep their applications secure and compliant. 
+However, Express.js v3.x reached its end-of-life in July 2015, leaving many businesses and developers in need of support to keep their applications secure and compliant.
 
 > "We’re grateful to see HeroDevs stepping in to provide extended long-term support for Express
 >
-> Express NES ensures that the many businesses and developers who rely on Express can continue using it safely and securely, even years after its original end-of-life. This kind of ongoing commitment to the open-source ecosystem is crucial, and we’re excited to see the benefits it brings to the developer community.” — said a spokesperson for the Express Technical Committee. 
+> Express NES ensures that the many businesses and developers who rely on Express can continue using it safely and securely, even years after its original end-of-life. This kind of ongoing commitment to the open-source ecosystem is crucial, and we’re excited to see the benefits it brings to the developer community.” — said a spokesperson for the Express Technical Committee.
 
 Express NES is designed as a drop-in replacement for legacy versions of Express.js, offering security patches, compatibility updates and compliance fixes. This solution ensures that developers can remain on legacy Express.js without becoming vulnerable to security risks and compliance issues.
 
@@ -23,4 +23,4 @@ Express NES is designed as a drop-in replacement for legacy versions of Express.
 >
 > Our partnership with OpenJS has enabled us to meet the needs of developers still relying on older versions of critical frameworks. Express NES ensures that they can continue building and maintaining their applications without the risk of security vulnerabilities or loss of compliance.” — Joe Eames, VP of Partnership at HeroDevs.
 
-For more information on Express NES and how to get started, visit [HeroDevs’ website](https://www.herodevs.com/support/express-nes).
\ No newline at end of file
+For more information on Express NES and how to get started, visit [HeroDevs’ website](https://www.herodevs.com/support/express-nes).
diff --git a/_posts/2024-10-15-v5-release.md b/src/content/blog/2024-10-15-v5-release.md
similarity index 81%
rename from _posts/2024-10-15-v5-release.md
rename to src/content/blog/2024-10-15-v5-release.md
index 3e33233d7a..a1af3bea75 100644
--- a/_posts/2024-10-15-v5-release.md
+++ b/src/content/blog/2024-10-15-v5-release.md
@@ -1,6 +1,6 @@
 ---
-title: "Introducing Express v5: A New Era for the Node.js Framework"
-tags: releases
+title: 'Introducing Express v5: A New Era for the Node.js Framework'
+tags: ['announcements']
 authors:
   - name: Wes Todd
     github: wesleytodd
@@ -9,21 +9,21 @@ authors:
 description: Announcing the release of Express version 5
 ---
 
-Ten years ago (July 2014) the [Express v5 release pull request](https://github.com/expressjs/express/pull/2237) was opened, and now at long last it's been merged and published!  
+Ten years ago (July 2014) the [Express v5 release pull request](https://github.com/expressjs/express/pull/2237) was opened, and now at long last it's been merged and published!
 
 We want to recognize the work of all our contributors, especially [Doug Wilson](https://github.com/dougwilson), who spent the last ten years ensuring Express was the most stable project around. Without his contributions and those of many others, this release could not have happened.
 
 Eight months ago we went public with a plan to move [Express forward](https://github.com/expressjs/discussions/issues/160). This plan included re-committing to the governance outlined years ago and adding more contributors to help kickstart progress. Many people may not realize that robust project governance is critical to the health of a large open-source project. We want to thank the [OpenJS Foundation Cross Project
-Council](https://github.com/openjs-foundation/cross-project-council/) and its members for helping us put together this plan. 
+Council](https://github.com/openjs-foundation/cross-project-council/) and its members for helping us put together this plan.
 
 ## So what about v5?
 
-This release is designed to be boring! 
+This release is designed to be boring!
 That may sound odd, but we've intentionally kept it simple to unblock the ecosystem and enable more impactful changes in future releases. This is also about signaling to the Node.js ecosystem that Express is moving again.
 The focus of this release is on dropping old Node.js version support, addressing security concerns, and simplifying maintenance.
 
-Before going into the changes in this release, let's address why it was released v5 on the `next` dist-tag. As part of reviving the project, we started a [Security working group](https://github.com/expressjs/security-wg) and [security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team) to address the growing needs around open source supply chain security. We undertook a security audit (more details to come on that) and uncovered some problems that needed to be addressed. Thus, in addition to the "normal" work done in public issues, we also did a lot of security work in private forks. 
-This security work required orchestration when releasing, to ensure the code and CVE reports went out together. You can find a summary of the most recent vulnerabilities patched in [our security release notes](https://expressjs.com/2024/09/29/security-releases.html). 
+Before going into the changes in this release, let's address why it was released v5 on the `next` dist-tag. As part of reviving the project, we started a [Security working group](https://github.com/expressjs/security-wg) and [security triage team](https://github.com/expressjs/security-wg?tab=readme-ov-file#security-triage-team) to address the growing needs around open source supply chain security. We undertook a security audit (more details to come on that) and uncovered some problems that needed to be addressed. Thus, in addition to the "normal" work done in public issues, we also did a lot of security work in private forks.
+This security work required orchestration when releasing, to ensure the code and CVE reports went out together. You can find a summary of the most recent vulnerabilities patched in [our security release notes](/en/blog/2024-09-29-security-releases).
 
 While we weren't able to simultaneously release v5, this blog post, the changelog, and documentation, we felt it was most important to have a secure and stable release.
 
@@ -31,23 +31,30 @@ As soon as possible, we'll provide more details on our long-term support (LTS) p
 
 ## Breaking changes
 
-The v5 release has the minimum possible number of breaking changes, listed here in order of impact to applications. 
+The v5 release has the minimum possible number of breaking changes, listed here in order of impact to applications.
 
-- [Ending support for old Node.js versions](#ending-support-for-old-nodejs-versions)
-- [Changes to path matching and regular expressions](#changes-to-path-matching-and-regular-expressions)
-- [Promise support](#promise-support)
-- [Body parser changes](#body-parser-changes)
-- [Removing deprecated method signatures](#removing-deprecated-method-signatures)
+- [So what about v5?](#so-what-about-v5)
+- [Breaking changes](#breaking-changes)
+  - [Ending support for old Node.js versions](#ending-support-for-old-nodejs-versions)
+  - [Changes to path matching and regular expressions](#changes-to-path-matching-and-regular-expressions)
+    - [No more regex](#no-more-regex)
+    - [Splats, optional, and captures oh my](#splats-optional-and-captures-oh-my)
+    - [Name everything](#name-everything)
+  - [Promise support](#promise-support)
+  - [Body parser changes](#body-parser-changes)
+  - [Removing deprecated method signatures](#removing-deprecated-method-signatures)
+- [Migration and security guidance](#migration-and-security-guidance)
+- [Our work is just starting](#our-work-is-just-starting)
 
-There are also a number of subtle changes: for details, see [Migrating to Express 5]({{site.url}}/{{page.lang}}/guide/migrating-5).
+There are also a number of subtle changes: for details, see [Migrating to Express 5](/en/guide/migrating-5).
 
 ### Ending support for old Node.js versions
 
-Goodbye Node.js 0.10, hello Node 18 and up! 
+Goodbye Node.js 0.10, hello Node 18 and up!
 
 This release drops support for Node.js versions before v18. This is an important change because supporting old Node.js versions has been holding back many critical performance and maintainability changes. This change also enables more stable and maintainable continuous integration (CI), adopting new language and runtime features, and dropping dependencies that are no longer required.
 
-We recognize that this might cause difficulty for some enterprises with older or "parked" applications, and because of this we are working on a [partnership with HeroDevs](https://expressjs.com/2024/10/01/HeroDevs-partnership-announcement.html) to offer "never-ending support" that will include critical security patches even after v4 enters end-of-life (more on these plans soon). That said, we strongly suggest that you update to modern Node.js versions as soon as possible.
+We recognize that this might cause difficulty for some enterprises with older or "parked" applications, and because of this we are working on a [partnership with HeroDevs](/en/blog/2024-10-01-herodevs-partnership-announcement) to offer "never-ending support" that will include critical security patches even after v4 enters end-of-life (more on these plans soon). That said, we strongly suggest that you update to modern Node.js versions as soon as possible.
 
 ### Changes to path matching and regular expressions
 
@@ -58,11 +65,11 @@ The v5 releases updates to `path-to-regexp@8.x` from `path-to-regexp@0.x`, which
 This release no longer supports "sub-expression" regular expressions, for example `/:foo(\\d+)`.
 This is a commonly-used pattern, but we removed it for security reasons. Unfortunately, it's easy to write a regular expression that has exponential time behavior when parsing input: The dreaded regular expression denial of service (ReDoS) attack. It's very difficult to prevent this, but as a library that converts strings to regular expressions, we are on the hook for such security aspects.
 
-*How to migrate:* The best approach to prevent ReDoS attacks is to use a robust input validation library. [There are many on `npm`](https://www.npmjs.com/search?q=validate%20express) depending on your needs. TC member Wes Todd maintains [a middleware-based "code first" OpenAPI library](https://www.npmjs.com/package/@wesleytodd/openapi) for this kind of thing. 
+_How to migrate:_ The best approach to prevent ReDoS attacks is to use a robust input validation library. [There are many on `npm`](https://www.npmjs.com/search?q=validate%20express) depending on your needs. TC member Wes Todd maintains [a middleware-based "code first" OpenAPI library](https://www.npmjs.com/package/@wesleytodd/openapi) for this kind of thing.
 
 #### Splats, optional, and captures oh my
 
-This release includes simplified patterns for common route patterns.  With the removal of regular expression semantics comes other small but impactful changes to how you write your routes.
+This release includes simplified patterns for common route patterns. With the removal of regular expression semantics comes other small but impactful changes to how you write your routes.
 
 1. `:name?` becomes `{:name}`. Usage of `{}` for optional parts of your route means you can now do things like `/base{/:optional}/:required` and what parts are actually optional is much more explicit.
 2. `*` becomes `*name`.
@@ -76,7 +83,7 @@ In Express v4, you could get numerical parameters using regex capture groups (fo
 
 ### Promise support
 
-This one may be a bit contentious, but we "promise" we're moving in the right direction. We added support for returned *rejected* promises from errors raised in middleware. This *does not include* calling `next` from returned *resolved* promises. There are a lot of edge cases in old Express apps that have expectations of `Promise` behavior, and before we can run we need to walk. For most folks, this means you can now write middleware like the following:
+This one may be a bit contentious, but we "promise" we're moving in the right direction. We added support for returned _rejected_ promises from errors raised in middleware. This _does not include_ calling `next` from returned _resolved_ promises. There are a lot of edge cases in old Express apps that have expectations of `Promise` behavior, and before we can run we need to walk. For most folks, this means you can now write middleware like the following:
 
 ```javascript
 app.use(async (req, res, next) => {
@@ -97,7 +104,7 @@ There are a number of `body-parser` changes:
 - Remove deprecated `bodyParser()` combination middleware
 - `req.body` is no longer always initialized to `{}`
 - `urlencoded` parser now defaults `extended` to false
-- Added support for Brotli lossless data compression 
+- Added support for Brotli lossless data compression
 
 ### Removing deprecated method signatures
 
@@ -120,12 +127,12 @@ As a framework, we aim to ensure that the API is as consistent as possible. We'v
 
 ## Migration and security guidance
 
-For developers looking to migrate from v4 to v5, there's a [detailed migration guide]({{site.url}}/{{page.lang}}/guide/migrating-5) to help you navigate through the changes and ensure a smooth upgrade process.
+For developers looking to migrate from v4 to v5, there's a [detailed migration guide](/en/guide/migrating-5) to help you navigate through the changes and ensure a smooth upgrade process.
 
 Additionally, we’ve been working hard on a comprehensive [Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md) that helps illustrate our philosophy of a "Fast, unopinionated, minimalist web framework for Node.js." It provides critical insights into areas like user input validation and security practices that are essential for safe and secure usage of Express in your applications.
 
 ## Our work is just starting
 
-We see the v5 release as a milestone toward an Express ecosystem that's a stable and reliable tool for companies, governments, educators, and hobby projects. It is our commitment as the new stewards of the Express project to move the ecosystem forward with this goal in mind. If you want to support this work, which we do on a volunteer basis, please consider supporting the project and its maintainers via [our sponsorship opportunities](https://opencollective.com/express).  
+We see the v5 release as a milestone toward an Express ecosystem that's a stable and reliable tool for companies, governments, educators, and hobby projects. It is our commitment as the new stewards of the Express project to move the ecosystem forward with this goal in mind. If you want to support this work, which we do on a volunteer basis, please consider supporting the project and its maintainers via [our sponsorship opportunities](https://opencollective.com/express).
 
-We have an [extensive working backlog](https://github.com/expressjs/discussions/issues/266) of tasks, PRs, and issues for Express and dependencies. Naturally, we expect developers will continue to report issues to add to this backlog and open PRs moving forward, and we'll continue to collaborate with the community to triage and resolve them.  We look forward to continuing to improve Express and making it useful for its users across the world.
+We have an [extensive working backlog](https://github.com/expressjs/discussions/issues/266) of tasks, PRs, and issues for Express and dependencies. Naturally, we expect developers will continue to report issues to add to this backlog and open PRs moving forward, and we'll continue to collaborate with the community to triage and resolve them. We look forward to continuing to improve Express and making it useful for its users across the world.
diff --git a/_posts/2024-10-22-security-audit-milestone-achievement.md b/src/content/blog/2024-10-22-security-audit-milestone-achievement.md
similarity index 95%
rename from _posts/2024-10-22-security-audit-milestone-achievement.md
rename to src/content/blog/2024-10-22-security-audit-milestone-achievement.md
index bf8bee0fca..36e8f8bc98 100644
--- a/_posts/2024-10-22-security-audit-milestone-achievement.md
+++ b/src/content/blog/2024-10-22-security-audit-milestone-achievement.md
@@ -1,13 +1,12 @@
 ---
-title: "Express.js Security Audit: A Milestone Achievement"
-tags: security audit releases
+title: 'Express.js Security Audit: A Milestone Achievement'
+tags: ['security', 'announcements']
 authors:
   - name: Express Technical Committee
     github: expressjs
 description: Celebrating the successful completion of the Express.js security audit conducted by Ada Logics and facilitated by OSTIF.
 ---
 
-
 We are thrilled to announce the successful completion of a comprehensive security audit for Express.js, conducted by [Ada Logics](https://adalogics.com/) and facilitated by [OSTIF](https://ostif.org/). This extensive review of our framework and its core components marks a significant milestone in our commitment to ensuring the security and reliability of Express.js for our community.
 
 ## A Collaborative Effort
@@ -39,7 +38,7 @@ For full details on the audit results, you can access the [official audit report
 
 At Express, security is a top priority, and we believe in the importance of transparency when it comes to vulnerabilities and their resolution. This audit not only highlights our proactive approach but also reinforces our ongoing commitment to building a secure web framework for all.
 
-We strongly recommend all users update to the latest versions of the affected packages to benefit from the recent security fixes. For more information on the patches and how to upgrade, please refer to our [September 2024 Security Release announcement](https://expressjs.com/2024/09/29/security-releases.html).
+We strongly recommend all users update to the latest versions of the affected packages to benefit from the recent security fixes. For more information on the patches and how to upgrade, please refer to our [September 2024 Security Release announcement](/en/blog/2024-09-29-security-releases).
 
 ## A Word of Thanks
 
@@ -51,7 +50,6 @@ This audit would not have been possible without the efforts and expertise of man
 - Our Express.js community, who continue to support and trust us with their projects.
 - [Jordan Harband](https://github.com/ljharb) for his amazing support while we needed changes in [qs](https://www.npmjs.com/package/qs).
 
-
 Together, we’ve made Express.js stronger, more resilient, and ready for the challenges ahead. We look forward to continuing to serve our community with a focus on excellence and security.
 
 Thank you for being a part of this journey with us!
diff --git a/_posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md b/src/content/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
similarity index 92%
rename from _posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
rename to src/content/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
index cc2a734b02..02a74e94f6 100644
--- a/_posts/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
+++ b/src/content/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision.md
@@ -1,14 +1,13 @@
 ---
-title: "A New Chapter for Express.js: Triumphs of 2024 and an ambitious 2025"
-tags: news rewind 2024
+title: 'A New Chapter for Express.js: Triumphs of 2024 and an ambitious 2025'
+tags: ['announcements']
 authors:
   - name: Express Technical Committee
     github: expressjs
 description: Explore the transformative journey of Express.js in 2024, marked by governance improvements, the long-awaited release of Express 5.0, and heightened security measures. Look into the ambitious plans for 2025, including performance optimizations, scoped packages, and a bold roadmap for sustained growth in the Node.js ecosystem.
 ---
 
-
-As we step into the new year, it’s almost impossible to ignore the unmistakable energy coursing through the Express.js community. The past twelve months have proven both foundational and forward-looking: an era of governance overhauls, technical triumphs, and security enhancements that not only shaped 2024 but also laid the groundwork for what promises to be a transformative 2025. 
+As we step into the new year, it’s almost impossible to ignore the unmistakable energy coursing through the Express.js community. The past twelve months have proven both foundational and forward-looking: an era of governance overhauls, technical triumphs, and security enhancements that not only shaped 2024 but also laid the groundwork for what promises to be a transformative 2025.
 In this long-form recap and forecast, we’ll journey through the story of Express.js with its evolution, its hurdles, and the new heights it’s poised to reach.
 
 ---
@@ -27,7 +26,7 @@ As if these achievements weren’t enough, Express.js proudly reached [Impact Pr
 
 ### Technical Advancements and the Release of Express 5.0
 
-Naturally, 2024 will forever be remembered as the year when Express.js finally introduced its much-anticipated [Express 5.0](https://expressjs.com/2024/10/15/v5-release.html). After more than a decade of community discussions and behind-the-scenes experimentation, this release brought modern features and a future-oriented architecture to the framework, acting as a catalyst for the next chapter of Express.js development.
+Naturally, 2024 will forever be remembered as the year when Express.js finally introduced its much-anticipated [Express 5.0](/en/blog/2024-10-15-v5-release). After more than a decade of community discussions and behind-the-scenes experimentation, this release brought modern features and a future-oriented architecture to the framework, acting as a catalyst for the next chapter of Express.js development.
 
 But the story did not end there. Even before the release of Express 5.0 was fully established, the community had already begun charting the course for [Express 6.0](https://github.com/expressjs/discussions/issues/267), reflecting an unwavering commitment to innovation. Guiding critical decisions throughout 2024 were new [decision framework](https://github.com/expressjs/discussions/issues/285), which helped the Technical Committee tackle pressing matters such as [engine usage](https://github.com/expressjs/discussions/issues/286) and [dependency management](https://github.com/expressjs/discussions/issues/279). Collectively, these measures fostered transparency and agility, ensuring that Express.js continues to evolve in response to the community’s most urgent needs.
 
@@ -37,11 +36,10 @@ Express.js also deepened its relationship with the Node.js community by re-integ
 
 ### A Heightened Security Posture
 
-Above all, 2024 will stand out for Express.js’s vigorous approach to security. In partnership with the [OpenJS Foundation](https://openjsf.org/) and [OSTIF](https://ostif.org/), the project undertook a comprehensive [security audit](https://expressjs.com/2024/10/22/security-audit-milestone-achievement.html) that yielded critical insights and propelled immediate improvements. The sense of proactive vigilance extended to the adoption of the [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162), implemented at an organizational level to keep track of security metrics and maintain focus on ongoing enhancements.
+Above all, 2024 will stand out for Express.js’s vigorous approach to security. In partnership with the [OpenJS Foundation](https://openjsf.org/) and [OSTIF](https://ostif.org/), the project undertook a comprehensive [security audit](/en/blog/2024-10-22-security-audit-milestone-achievement) that yielded critical insights and propelled immediate improvements. The sense of proactive vigilance extended to the adoption of the [OSSF Scorecard](https://github.com/expressjs/discussions/issues/162), implemented at an organizational level to keep track of security metrics and maintain focus on ongoing enhancements.
 
 Throughout the year, maintainers rapidly responded to disclosed vulnerabilities such as [CVE-2024-43796](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-45590](https://github.com/expressjs/body-parser/security/advisories/GHSA-qwcr-r2fm-qrc7), and [CVE-2024-47178](https://github.com/expressjs/basic-auth-connect/security/advisories/GHSA-7p89-p6hx-q4fw). Each instance underscored the community’s readiness to defend the framework’s integrity and safeguard its user base. In a further demonstration of long-term commitment, Express.js teamed up with [HeroDevs](https://www.herodevs.com/) to establish [Never-Ending Support (NES)](https://openjsf.org/blog/at-the-openjs-foundation-were-excited-to-announce-), offering an extended maintenance plan that reaffirms Express.js as a reliable foundation for developers now and in the years to come.
 
-
 ---
 
 ## A Bold Vision for 2025
@@ -80,4 +78,3 @@ Through automated releases, scopes for packages, rigorous security protocols, pe
 
 Whether you’re a seasoned maintainer, an occasional contributor, or a newcomer to this thriving ecosystem, your voice matters. Join the [Express.js GitHub Discussions](https://github.com/expressjs/discussions), attend open meetings, and stay tuned for updates on [Express.js blog](https://expressjs.com/) as we finalize timetables for these initiatives. Each advancement, no matter how technical, flows from a common aspiration: to sustain Express.js as a fast, safe, and influential framework for millions of developers worldwide.
 Together, we’ll keep the spirit of 2024 alive—pushing boundaries, refining practices, and laying the path to a future where Express.js remains at the heart of modern web development.
-
diff --git a/_posts/2025-03-31-v5-1-latest-release.md b/src/content/blog/2025-03-31-v5-1-latest-release.md
similarity index 81%
rename from _posts/2025-03-31-v5-1-latest-release.md
rename to src/content/blog/2025-03-31-v5-1-latest-release.md
index bb2b473ab2..149dcf439e 100644
--- a/_posts/2025-03-31-v5-1-latest-release.md
+++ b/src/content/blog/2025-03-31-v5-1-latest-release.md
@@ -1,6 +1,6 @@
 ---
-title: "Express@5.1.0: Now the Default on npm with LTS Timeline"
-tags: news release
+title: 'Express@5.1.0: Now the Default on npm with LTS Timeline'
+tags: ['announcements']
 authors:
   - name: Express Technical Committee
     github: expressjs
@@ -9,7 +9,7 @@ description: Express 5.1.0 is now the default on npm, and we're introducing an o
 
 Express v5.0.0 was released on September 9th last year, but we didn't make it the `latest` release on npm. Many asked us
 why and when it would be, and frankly we were not ready at the time to take that jump. If you have not followed the news
-from the project this past year, we have been [hard at work reviving the project](https://expressjs.com/2025/01/09/rewind-2024-triumphs-and-2025-vision.html)
+from the project this past year, we have been [hard at work reviving the project](/en/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision/)
 and when we pushed the initial v5 release there were many loose ends still hanging. So first lets quickly go over some
 of those loose ends.
 
@@ -20,22 +20,22 @@ time. Since then we have had tons of great contributors help get things into bet
 Open Source project, we love contributions to help us improve so as you upgrade please continue to open PRs to fix
 anything we missed.
 
-You can find our [v5 docs](https://expressjs.com/en/5x/api.html) and our [migration guide](https://expressjs.com/en/guide/migrating-5.html) on the website.
+You can find our [v5 docs](/en/5x/api) and our [migration guide](/en/guide/migrating-5) on the website.
 
 ### Migration Support
 
-We know that migrating between versions can be challenging, especially when it involves significant changes in a widely used framework like Express. That's why we have worked on a solution to simplify part of the process and reduce the impact on developers.  
+We know that migrating between versions can be challenging, especially when it involves significant changes in a widely used framework like Express. That's why we have worked on a solution to simplify part of the process and reduce the impact on developers.
 
-Thanks to the incredible efforts of [Sebastian](https://github.com/bjohansebas) and [Filip](https://github.com/kjugi), we have developed a new [codemod package](https://www.npmjs.com/package/@expressjs/codemod) specifically designed to facilitate the transition from Express v4 to v5, as well as future major versions. This package automates many of the necessary code changes, minimizing manual effort and making the upgrade as smooth and efficient as possible.  
+Thanks to the incredible efforts of [Sebastian](https://github.com/bjohansebas) and [Filip](https://github.com/kjugi), we have developed a new [codemod package](https://www.npmjs.com/package/@expressjs/codemod) specifically designed to facilitate the transition from Express v4 to v5, as well as future major versions. This package automates many of the necessary code changes, minimizing manual effort and making the upgrade as smooth and efficient as possible.
 
-However, we understand that not all changes can be automated. Some breaking changes, such as the [new Path Route Matching syntax](https://expressjs.com/en/guide/migrating-5.html#path-syntax), require manual modifications by developers.  You can read more about all of the breaking changes which came with v5 in our [original release announcement](https://expressjs.com/2024/10/15/v5-release.html).
+However, we understand that not all changes can be automated. Some breaking changes, such as the [new Path Route Matching syntax](/en/guide/migrating-5#path-syntax), require manual modifications by developers. You can read more about all of the breaking changes which came with v5 in our [original release announcement](/en/blog/2024-10-15-v5-release).
 
-For more details on the migration process and how to use the codemod package, check the [repository’s README](https://github.com/expressjs/codemod#readme) and the [migration guide](https://expressjs.com/en/guide/migrating-5.html).
+For more details on the migration process and how to use the codemod package, check the [repository’s README](https://github.com/expressjs/codemod#readme) and the [migration guide](/en/guide/migrating-5).
 
 ### Ecosystem compatibility
 
 The Express ecosystem is one of its strongest assets. It goes back to the early days of Node.js and is the backbone
-that keeps express popular. When it goes [10 years without a major release](https://expressjs.com/2024/10/15/v5-release.html)
+that keeps express popular. When it goes [10 years without a major release](/en/blog/2024-10-15-v5-release)
 everything from middleware to documentation needed updates. We wanted to make sure folks had
 some time to get all of that updated before we had everyone moving over. Particularly we care about our very large
 beginner user base who may not know the blog post they are reading is not compatible with what they get from
@@ -53,7 +53,7 @@ and we had (still don't have) end user docs on our plans here. While we still ha
 [proposed LTS strategy ](https://github.com/expressjs/discussions/pull/352) which will be the basis for our forthcoming
 docs. Input is very welcome on this so we can make sure it is clearly communicated and acceptable to the community.
 
-Additionally since then [we have announced a partnership with HeroDevs](https://expressjs.com/2024/10/01/HeroDevs-partnership-announcement.html) to help companies who are less capable of
+Additionally since then [we have announced a partnership with HeroDevs](/en/blog/2024-10-01-herodevs-partnership-announcement) to help companies who are less capable of
 updating. More information on how this will work when v4 EOL will come when we get closer to that time.
 
 ---
@@ -69,11 +69,11 @@ enter EOL.
 
 Express major versions will go through three supported phases:
 
-  - `CURRENT`: A new major version is designated as `CURRENT` upon release. It is available but not the `latest` version
-    on npm for a minimum of 3 months.
-  - `ACTIVE`: After the minimum 3 month period and the TC agrees it is stable and secure, the `ACTIVE` version is
-    tagged `latest` on npm for a minimum of 12 months.
-  - `MAINTENANCE`: When a new major version becomes `ACTIVE`, the previous major version enters `MAINTENANCE` for 12 months.
+- `CURRENT`: A new major version is designated as `CURRENT` upon release. It is available but not the `latest` version
+  on npm for a minimum of 3 months.
+- `ACTIVE`: After the minimum 3 month period and the TC agrees it is stable and secure, the `ACTIVE` version is
+  tagged `latest` on npm for a minimum of 12 months.
+- `MAINTENANCE`: When a new major version becomes `ACTIVE`, the previous major version enters `MAINTENANCE` for 12 months.
 
 ### CURRENT
 
@@ -83,7 +83,7 @@ Express major versions will go through three supported phases:
   fixes of breaking nature within this period.
 - `CURRENT` lines will receive all types of active work including: bug fixes, security patches, new features, and
   deprecation notices.
-- Users are recommended to use  `CURRENT` lines and to upgrade as quickly as their risk profile allows
+- Users are recommended to use `CURRENT` lines and to upgrade as quickly as their risk profile allows
 
 ### ACTIVE
 
@@ -102,11 +102,11 @@ For the existing release lines, we will set the following phase dates:
 
 <div markdown="1" style="overflow-x: auto; max-width: 100%;">
 
-| Major | CURRENT | ACTIVE | MAINTENANCE | EOL |
-| ----- | ------- | ------ | ----------- | --- |
-| 4.x   |         |        | 2025-04-01 | *no sooner than 2026-10-01 |
-| 5.x   | 2024-09-11 | 2025-03-31 | **no sooner than 2026-04-01 | **no sooner than 2027-04-01 |
-| 6.x   | ***no sooner than 2026-01-01 | | | |
+| Major | CURRENT                         | ACTIVE     | MAINTENANCE                   | EOL                           |
+| ----- | ------------------------------- | ---------- | ----------------------------- | ----------------------------- |
+| 4.x   |                                 |            | 2025-04-01                    | \*no sooner than 2026-10-01   |
+| 5.x   | 2024-09-11                      | 2025-03-31 | \*\*no sooner than 2026-04-01 | \*\*no sooner than 2027-04-01 |
+| 6.x   | \*\*\*no sooner than 2026-01-01 |            |                               |                               |
 
 </div>
 
@@ -128,30 +128,30 @@ This release primarily focused on tech debt from supporting so many old Node.js
 
 ### Express 5.1.0 Main Changes
 
-* Add support for `Uint8Array` in `res.send()`
-* Transitioned all remaining dependencies to use `^` ranges instead of locked versions
-* Add package.json funding field to highlight our OpenCollective 
-* Added support for ETag option in `res.sendFile()`
-* Added support for adding multiple links with the same rel with `res.links()`
-* Performance: Use loop for acceptParams
-* See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
+- Add support for `Uint8Array` in `res.send()`
+- Transitioned all remaining dependencies to use `^` ranges instead of locked versions
+- Add package.json funding field to highlight our OpenCollective
+- Added support for ETag option in `res.sendFile()`
+- Added support for adding multiple links with the same rel with `res.links()`
+- Performance: Use loop for acceptParams
+- See [Changelog v5.1.0](https://github.com/expressjs/express/releases/tag/v5.1.0)
 
 ### Dependencies updated
 
 We also invested time to prepare several releases in the packages that Express depend on. Most of this packages are used by other libraries and framework as individual libraries.
 
-* [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
-  * Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
-  * Remove `unpipe` & `destroy`
-* [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
-  * Restore `debug`. Now with the `router` scope instead of `express`.
-  * Remove legacy node.js support checks for `setImmediate`
-  * Deprecate non-native promise support
-  * Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
-* [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
-    * Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
-    * Remove `unpipe`
-* [serve-static@2.2.0](https://github.com/expressjs/serve-static/releases/tag/v2.2.0)
+- [body-parser@2.2.0](https://github.com/expressjs/body-parser/releases/tag/v2.2.0)
+  - Remove legacy node.js support checks for Brotli & `AsyncLocalStorage`
+  - Remove `unpipe` & `destroy`
+- [router@2.2.0](https://github.com/pillarjs/router/releases/tag/v2.2.0)
+  - Restore `debug`. Now with the `router` scope instead of `express`.
+  - Remove legacy node.js support checks for `setImmediate`
+  - Deprecate non-native promise support
+  - Remove `after`, `safe-buffer`, `array-flatten`, `setprotoypeof`, `methods`, `utils-merge`
+- [finalhandler@2.1.0](https://github.com/pillarjs/finalhandler/releases/tag/v2.1.0)
+  - Remove legacy node.js support checks for `headersSent`, `setImmediate`, & http2 support
+  - Remove `unpipe`
+- [serve-static@2.2.0](https://github.com/expressjs/serve-static/releases/tag/v2.2.0)
 
 ---
 
@@ -161,7 +161,7 @@ Thanks so much to everyone involved in Express over the past year, the work all
 incredible, and we couldn't do it without them. If you are not able to become a contributor yourself, please consider
 asking your companies to support the project financially on [OpenCollective](https://opencollective.com/express).
 
-As we look ahead, we’re excited to keep building momentum. If you haven’t read it yet, our [Rewind 2024 + 2025 Vision blog post](https://expressjs.com/2025/01/09/rewind-2024-triumphs-and-2025-vision.html) lays out where we’ve been and where we're headed. This includes performances scoped packages, better automation, security hardening, and more.
+As we look ahead, we’re excited to keep building momentum. If you haven’t read it yet, our [Rewind 2024 + 2025 Vision blog post](/en/blog/2025-01-09-rewind-2024-triumphs-and-2025-vision) lays out where we’ve been and where we're headed. This includes performances scoped packages, better automation, security hardening, and more.
 
 One major initiative is our new [Performance Working Group](https://github.com/expressjs/discussions/pull/306), focused on identifying and fixing long-standing bottlenecks in Express. We're grateful to be kicking this off with support from the [Sovereign Tech Fund (STF)](https://www.sovereign.tech/), who are helping us invest in long-term sustainability and performance of core infrastructure. Additionally, we will be working to [improve our Typescript DX](https://github.com/expressjs/discussions/issues/192) and taking next steps to [improve the website](https://github.com/expressjs/expressjs.com/issues/1787).
 
diff --git a/_posts/2025-05-16-express-cleanup-legacy-packages.md b/src/content/blog/2025-05-16-express-cleanup-legacy-packages.md
similarity index 96%
rename from _posts/2025-05-16-express-cleanup-legacy-packages.md
rename to src/content/blog/2025-05-16-express-cleanup-legacy-packages.md
index eee24e3bb1..500d48cb51 100644
--- a/_posts/2025-05-16-express-cleanup-legacy-packages.md
+++ b/src/content/blog/2025-05-16-express-cleanup-legacy-packages.md
@@ -1,6 +1,6 @@
 ---
-title: "Spring Cleaning in Express.js: Deprecations and the Path Ahead"
-tags: news
+title: 'Spring Cleaning in Express.js: Deprecations and the Path Ahead'
+tags: ['announcements']
 authors:
   - name: Express Technical Committee
     github: expressjs
@@ -41,7 +41,7 @@ If your application depends on any of these packages, now is a great time to loo
 
 We're not stopping here. This cleanup is part of a broader effort to streamline Express.js, prepare for the future, and clarify what is and isn’t officially supported.
 
-👉 A full discussion of these changes can be found [expressjs/discussions#134](https://github.com/expressjs/discussions/issues/134).  
+👉 A full discussion of these changes can be found [expressjs/discussions#134](https://github.com/expressjs/discussions/issues/134).
 
 📢 Stay tuned—we'll continue to post updates and insights as we modernize the Express ecosystem.
 
diff --git a/src/content/blog/2025-05-19-security-releases.mdx b/src/content/blog/2025-05-19-security-releases.mdx
new file mode 100644
index 0000000000..dbb2a228c0
--- /dev/null
+++ b/src/content/blog/2025-05-19-security-releases.mdx
@@ -0,0 +1,53 @@
+---
+title: May 2025 Security Releases
+description: Security release for Multer has been published. We recommend that all users upgrade as soon as possible.
+tags: ['security']
+authors:
+  - name: Ulises Gascón
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The Express team has released a new major version of [Multer](https://www.npmjs.com/package/multer) addressing two high-severity security vulnerabilities. This update improves the reliability and security of handling file uploads in Express applications.
+
+<Alert type="warning">
+  We strongly recommend that you upgrade to Multer v2.0.0 or later as soon as possible.
+</Alert>
+
+The following vulnerabilities have been addressed:
+
+- [High severity vulnerability CVE-2025-47935 in Multer middleware](#high-severity-vulnerability-cve-2025-47935-in-multer-middleware)
+- [High severity vulnerability CVE-2025-47944 in Multer middleware](#high-severity-vulnerability-cve-2025-47944-in-multer-middleware)
+
+## High severity vulnerability CVE-2025-47935 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `<2.0.0` are vulnerable to denial of service due to a memory leak caused by improper stream handling.**
+
+When the HTTP request stream emits an error, the internal `busboy` stream is not closed, violating Node.js stream safety guidance.
+
+This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.
+
+**Affected versions**: `<2.0.0`
+**Patched version**: `>=2.0.0`
+
+For more details, see [GHSA-44fp-w29j-9vj5](https://github.com/expressjs/multer/security/advisories/GHSA-44fp-w29j-9vj5).
+
+## High severity vulnerability CVE-2025-47944 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.0` are vulnerable to a denial of service via a malformed multipart request.**
+
+A specially crafted request can cause an unhandled exception inside Multer, resulting in a crash of the server process.
+
+**Affected versions**: `>=1.4.4-lts.1` and `<2.0.0`
+**Patched version**: `>=2.0.0`
+
+For more details, see [GHSA-4pg4-qvpc-4q3h](https://github.com/expressjs/multer/security/advisories/GHSA-4pg4-qvpc-4q3h).
+
+---
+
+**Multer v2.0.0** also introduces a breaking change:
+
+- The minimum supported Node.js version is now **10.16.0**.
+
+We recommend upgrading to the latest version of Multer immediately to secure your applications.
diff --git a/_posts/2025-06-05-vulnerability-reporting-process-overhaul.md b/src/content/blog/2025-06-05-vulnerability-reporting-process-overhaul.md
similarity index 94%
rename from _posts/2025-06-05-vulnerability-reporting-process-overhaul.md
rename to src/content/blog/2025-06-05-vulnerability-reporting-process-overhaul.md
index 14f4119bda..f227665d72 100644
--- a/_posts/2025-06-05-vulnerability-reporting-process-overhaul.md
+++ b/src/content/blog/2025-06-05-vulnerability-reporting-process-overhaul.md
@@ -1,31 +1,30 @@
 ---
 title: How Express.js Rebuilt Its Vulnerability Reporting Process
 description: Express.js has overhauled its vulnerability reporting workflow with a unified process, consolidated documentation, and GitHub Security Advisories enabled across all repositories.
-tags: security vulnerabilities process governance
+tags: ['security']
 authors:
   - name: Ulises Gascón
     github: UlisesGascon
 ---
 
-
 The Express.js project has completed a major milestone in its ongoing commitment to security: the implementation of a formal, centralized vulnerability reporting and response process.
 
 Until recently, security reports were typically handled over email — an approach that worked in the early days but no longer scaled with the growing complexity and user base of Express. This informal system introduced potential delays, inconsistent handling, and increased the risk of issues being missed or misunderstood.
 
 Thanks to support from the [Sovereign Tech Fund](https://sovereign.tech), the Express.js Security Working Group has now completed a ground-up overhaul of how we manage vulnerability reports.
 
-
 ## 🛠️ Key Improvements
 
 ### Formalized Vulnerability Reporting Workflow
 
-A comprehensive runbook and process flow have been created to guide maintainers through each step of triaging, confirming, and addressing reported security issues.  
-- [View the documentation](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)  
+A comprehensive runbook and process flow have been created to guide maintainers through each step of triaging, confirming, and addressing reported security issues.
+
+- [View the documentation](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
 - [Security Report Handling Flowchart](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md#security-report-handling-flowchart)
 
 ### Unified Security Policy Across Repositories
 
-All Express.js repositories now share a single, unified `SECURITY.md` policy to ensure consistency and remove confusion for reporters and maintainers alike.  
+All Express.js repositories now share a single, unified `SECURITY.md` policy to ensure consistency and remove confusion for reporters and maintainers alike.
 
 - [View the unified Security Policy](https://github.com/expressjs/.github/blob/master/SECURITY.md)
 
@@ -37,17 +36,16 @@ Security Advisories are now enabled across all Express.js repositories, allowing
 
 ### Clear Maintainer Responsibilities
 
-Expectations around ownership and response timelines have been clarified and published to reduce ambiguity and improve responsiveness.  
+Expectations around ownership and response timelines have been clarified and published to reduce ambiguity and improve responsiveness.
 
 > A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team) or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md) will acknowledge your report as soon as possible.
 >
 > After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
+> endeavor to keep you informed of the progress towards a fix and full
+> announcement, and may ask for additional information or guidance.
 >
 > _[Security Policy](https://github.com/expressjs/.github/blob/master/SECURITY.md)_
 
-
 ## 🛡️ Express is Now Covered Under the OpenJS Foundation CNA
 
 As of June 2025, the [OpenJS Foundation](https://openjsf.org/) is officially a [CVE Numbering Authority (CNA)](https://openjsf.org/blog/openjs-foundation-cna), empowered to assign CVE identifiers for security vulnerabilities across its hosted projects—including Express.
@@ -58,12 +56,12 @@ What this means for the community:
 - The foundation provides support and tooling to streamline the vulnerability disclosure process, particularly for maintainers and security researchers.
 - For critical issues, the CNA helps ensure that disclosures follow best practices and are recorded in global vulnerability databases.
 
-
 Please refer to [Express’s Security Policy](https://github.com/expressjs/express/security/policy) for the correct disclosure process. If needed, escalation routes through the OpenJS CNA are now available.
 
 This advancement is part of a broader effort to strengthen the security of JavaScript’s open-source ecosystem—especially for widely used, community-driven projects like Express.
 
 Learn more:
+
 - [OpenJS Foundation is now a CNA – Official Blog Post](https://openjsf.org/blog/openjs-foundation-cna)
 - [Socket.dev Coverage: OpenJS Foundation Becomes a CNA](https://socket.dev/blog/openjs-foundation-is-now-a-cna)
 
diff --git a/src/content/blog/2025-07-18-security-releases.mdx b/src/content/blog/2025-07-18-security-releases.mdx
new file mode 100644
index 0000000000..5d3c84a61a
--- /dev/null
+++ b/src/content/blog/2025-07-18-security-releases.mdx
@@ -0,0 +1,29 @@
+---
+title: June 2025 Security Releases
+description: Security update for Multer released. All users are encouraged to upgrade.
+tags: ['security']
+authors:
+  - name: Ulises Gascón
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer), addressing a high-severity vulnerability that could lead to a Denial of Service (DoS) attack.
+
+<Alert type="warning">
+  We strongly recommend that all users upgrade to Multer v2.0.1 or later immediately.
+</Alert>
+
+This release addresses the following vulnerability:
+
+### High severity vulnerability CVE-2025-48997 in Multer middleware
+
+**[Multer](https://www.npmjs.com/package/multer) versions `>=1.4.4-lts.1` and `<2.0.1` are vulnerable to a Denial of Service (DoS) attack.**
+
+An attacker can trigger this vulnerability by sending an upload request with an empty string as the field name. This malformed request causes an unhandled exception, leading to a crash of the server process.
+
+**Affected versions**: `>=1.4.4-lts.1` and `<2.0.1`
+**Patched version**: `2.0.1`
+
+For more details, see [GHSA-g5hg-p3ph-g8qg](https://github.com/expressjs/multer/security/advisories/GHSA-g5hg-p3ph-g8qg).
diff --git a/_posts/2025-07-31-security-releases.md b/src/content/blog/2025-07-31-security-releases.md
similarity index 90%
rename from _posts/2025-07-31-security-releases.md
rename to src/content/blog/2025-07-31-security-releases.md
index 6582649097..694e5c7ac4 100644
--- a/_posts/2025-07-31-security-releases.md
+++ b/src/content/blog/2025-07-31-security-releases.md
@@ -1,18 +1,19 @@
 ---
 title: July 2025 Security Releases
 description: Security releases for Multer and On-headers has been published. We recommend that all users upgrade as soon as possible.
-tags: security vulnerabilities
+tags: ['security']
 authors:
   - name: Ulises Gascón
     github: UlisesGascon
 ---
 
-The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer) addressing a high-severity security vulnerability, and a new minor version of [on-headers](https://www.npmjs.com/package/on-headers) addressing a low-severity security vulnerability.
+import Alert from '@components/primitives/Alert/Alert.astro';
 
+The Express team has released a new patch version of [Multer](https://www.npmjs.com/package/multer) addressing a high-severity security vulnerability, and a new minor version of [on-headers](https://www.npmjs.com/package/on-headers) addressing a low-severity security vulnerability.
 
-{% include admonitions/warning.html 
-content="We recommend upgrading to the latest version of Multer and On-headers immediately to secure your applications."
-%}
+<Alert type="warning">
+We recommend upgrading to the latest version of Multer and On-headers immediately to secure your applications.
+</Alert>
 
 The following vulnerabilities have been addressed:
 
diff --git a/src/content/blog/2025-12-01-security-releases.mdx b/src/content/blog/2025-12-01-security-releases.mdx
new file mode 100644
index 0000000000..52ed3762b4
--- /dev/null
+++ b/src/content/blog/2025-12-01-security-releases.mdx
@@ -0,0 +1,37 @@
+---
+title: November 2025 Security Releases
+description: Security release for body-parser has been published. We recommend that all users upgrade as soon as possible.
+tags: ['security']
+authors:
+  - name: Ulises Gascón
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The Express team has released a new patch version of [body-parser](https://www.npmjs.com/package/body-parser) addressing a moderate-severity security vulnerability.
+
+<Alert type="warning">
+
+We recommend upgrading to the latest version of body-parser to secure your applications.
+
+</Alert>
+
+The following vulnerabilities have been addressed:
+
+- [CVE-2025-13466 in body-parser middleware (Moderate)](#cve-2025-13466-in-body-parser-middleware-moderate)
+
+## CVE-2025-13466 in Body-parser middleware (Moderate)
+
+**[body-parser](https://www.npmjs.com/package/body-parser) version `2.2.0` is vulnerable to denial of service when url encoding is used**
+
+body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.
+
+**Affected versions**: `2.2.0`
+**Patched version**: `>= 2.2.1`
+
+For more details, see [GHSA-wqch-xfxh-vrr4](https://github.com/expressjs/body-parser/security/advisories/GHSA-wqch-xfxh-vrr4).
+
+---
+
+We recommend upgrading to the latest version of body-parser to secure your applications.
diff --git a/src/content/blog/2026-02-27-security-releases.mdx b/src/content/blog/2026-02-27-security-releases.mdx
new file mode 100644
index 0000000000..669dfec09a
--- /dev/null
+++ b/src/content/blog/2026-02-27-security-releases.mdx
@@ -0,0 +1,49 @@
+---
+title: February 2026 Security Releases
+description: Security release for multer has been published. We recommend that all users upgrade as soon as possible.
+tags: ['security']
+authors:
+  - name: Ulises Gascón
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The Express team has released a new patch version of [multer](https://www.npmjs.com/package/multer) addressing two high-severity security vulnerabilities.
+
+<Alert type="warning">
+
+We recommend upgrading to the latest version of multer to secure your applications.
+
+</Alert>
+
+The following vulnerabilities have been addressed:
+
+- [CVE-2026-3304 in multer middleware (High)](#cve-2026-3304-in-multer-middleware-high)
+- [CVE-2026-2359 in multer middleware (High)](#cve-2026-2359-in-multer-middleware-high)
+
+## CVE-2026-3304 in multer middleware (High)
+
+**[multer](https://www.npmjs.com/package/multer) versions `<2.1.0` are vulnerable to denial of service via incomplete cleanup**
+
+A vulnerability in Multer versions `<2.1.0` allows an attacker to trigger a Denial of Service (DoS) by sending malformed requests, potentially causing resource exhaustion.
+
+**Affected versions**: `< 2.1.0`
+**Patched version**: `>= 2.1.0`
+
+For more details, see [GHSA-xf7r-hgr6-v32p](https://github.com/expressjs/multer/security/advisories/GHSA-xf7r-hgr6-v32p).
+
+## CVE-2026-2359 in multer middleware (High)
+
+**[multer](https://www.npmjs.com/package/multer) versions `<2.1.0` are vulnerable to denial of service via resource exhaustion**
+
+A vulnerability in Multer versions `<2.1.0` allows an attacker to trigger a Denial of Service (DoS) by dropping connection during file upload, potentially causing resource exhaustion.
+
+**Affected versions**: `< 2.1.0`
+**Patched version**: `>= 2.1.0`
+
+For more details, see [GHSA-v52c-386h-88mc](https://github.com/expressjs/multer/security/advisories/GHSA-v52c-386h-88mc).
+
+---
+
+We recommend upgrading to the latest version of multer to secure your applications.
diff --git a/src/content/blog/2026-03-30-security-releases.mdx b/src/content/blog/2026-03-30-security-releases.mdx
new file mode 100644
index 0000000000..1f9549eb9c
--- /dev/null
+++ b/src/content/blog/2026-03-30-security-releases.mdx
@@ -0,0 +1,64 @@
+---
+title: March 2026 Security Releases
+description: Security releases for path-to-regexp have been published. We recommend that all users upgrade as soon as possible.
+tags: ['security']
+authors:
+  - name: Ulises Gascon
+    github: UlisesGascon
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The Express team has released new patch versions of [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) addressing three regular expression denial of service vulnerabilities.
+
+<Alert type="warning">
+We recommend upgrading to the latest version of path-to-regexp to secure your applications. If you have a `package-lock.json`, you can update the dependency by running:
+
+```sh
+npm update path-to-regexp
+```
+
+</Alert>
+
+The following vulnerabilities have been addressed:
+
+- [CVE-2026-4867 in path-to-regexp utility module (High)](#cve-2026-4867-in-path-to-regexp-utility-module-high)
+- [CVE-2026-4926 in path-to-regexp utility module (High)](#cve-2026-4926-in-path-to-regexp-utility-module-high)
+- [CVE-2026-4923 in path-to-regexp utility module (Medium)](#cve-2026-4923-in-path-to-regexp-utility-module-medium)
+
+## CVE-2026-4867 in path-to-regexp utility module (High)
+
+**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `<= 0.1.12` are vulnerable to regular expression denial of service via multiple route parameters**
+
+A bad regular expression is generated any time you have three or more parameters within a single segment, separated by something that is not a period. For example, `/:a-:b-:c`. The backtrack protection added in v0.1.12 only prevents ambiguity for two parameters. With three or more, the generated lookahead does not block single separator characters, causing catastrophic backtracking.
+
+**Affected versions**: `<= 0.1.12`
+**Patched version**: `>= 0.1.13`
+
+For more details, see [GHSA-37ch-88jc-xwx2](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-37ch-88jc-xwx2).
+
+## CVE-2026-4926 in path-to-regexp utility module (High)
+
+**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `>= 8.0.0` are vulnerable to denial of service via sequential optional groups**
+
+A bad regular expression is generated any time you have multiple sequential optional groups, such as `{a}{b}{c}:z`. The generated regex grows exponentially with the number of groups, causing denial of service. Avoid passing user-controlled input as route patterns.
+
+**Affected versions**: `>= 8.0.0`
+**Patched version**: `>= 8.4.0`
+
+For more details, see [GHSA-j3q9-mxjg-w52f](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-j3q9-mxjg-w52f).
+
+## CVE-2026-4923 in path-to-regexp utility module (Medium)
+
+**[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) versions `>= 8.0.0, <= 8.3.0` are vulnerable to regular expression denial of service via multiple wildcards**
+
+When using multiple wildcards combined with at least one parameter, a regular expression can be generated that is vulnerable to ReDoS. The second wildcard must be somewhere other than the end of the path. For example, `/*foo-*bar-:baz`.
+
+**Affected versions**: `>= 8.0.0, <= 8.3.0`
+**Patched version**: `>= 8.4.0`
+
+For more details, see [GHSA-27v5-c462-wpq7](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-27v5-c462-wpq7).
+
+---
+
+We recommend upgrading to the latest version of path-to-regexp to secure your applications.
diff --git a/src/content/blog/write-post.md b/src/content/blog/write-post.md
new file mode 100644
index 0000000000..df58aaf515
--- /dev/null
+++ b/src/content/blog/write-post.md
@@ -0,0 +1,86 @@
+---
+title: How to write a blog post
+description: Step by step guide to write a blog post
+authors:
+  - name: Express Technical Committee
+    github: expressjs
+---
+
+If you have an idea for a blog post, follow these steps to propose it and potentially get it published!
+
+1.  **Propose your post**
+
+    Before taking the time to write a post, please confirm that we will be able to publish it. We're looking for topics specifically related to Express, and so we want to pre-approve all posts. For the moment, this means we aren't accepting any unsolicited posts. To propose a blog post, [open an issue](https://github.com/expressjs/expressjs.com/issues) entitled `Blog post proposal: <your idea>`.
+
+1.  **Fork the repository**
+
+    If the Express TC accepts your proposal, start to write your post by forking the [expressjs.com](https://github.com/expressjs/expressjs.com) repository and cloning it to your local machine. Once you open a pull request, you'll be able to preview your post on GitHub. See step six below.
+
+> Optional: To run the site locally and preview your post before opening a PR, see the [setup instructions in the README](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#expressjscom).
+
+1.  **Create a new file**
+
+    Create a new file in the `src/content/blog` directory named using following the format: `YYYY-MM-DD-title.md`.
+
+1.  **Add the required front matter**
+
+    Copy the following front matter, including the dotted lines, and paste it at the top of file you just created. Replace the placeholder values with as desired.
+
+    ```markdown
+    ---
+    title: <your-title>
+    description: <description-of-your-post>
+    tags: ['tag1', 'tag2']
+    authors:
+      - name: <your-name>
+        github: <github-username>
+    cover: <optional-cover-image-path>
+    ---
+    ```
+
+    The `github` property of an author is optional. Including your username only (not your full profile URL) will ensure that your blog post links out to it.
+
+    The `cover` property is optional. If omitted, an Open Graph image will be automatically generated from the post title. If you want a custom cover image, place it in the `public` directory and reference its path (e.g. `/images/my-cover.jpg`).
+
+1.  **Add your content**
+
+    Finally, start writing your content below the front matter. Use standard markdown formatting.
+
+    **Using components (MDX)**
+
+    If you need to use interactive components like alerts, callouts, or other UI elements inside your post, rename your file from `.md` to `.mdx`. MDX lets you import and use Astro components directly in your markdown.
+
+    For example, to add an alert:
+
+    ```mdx
+    ---
+    title: My blog post
+    description: A post with alerts
+    tags: ['security']
+    authors:
+      - name: John Doe
+        github: johndoe
+    ---
+
+    import Alert from '@components/primitives/Alert/Alert.astro';
+
+    This is regular markdown content.
+
+    <Alert type="warning">
+      We strongly recommend upgrading to the latest version as soon as possible.
+    </Alert>
+
+    <Alert type="info">This feature is available starting from Express 5.0.</Alert>
+
+    <Alert type="alert">
+      This is a breaking change. Please review the migration guide before upgrading.
+    </Alert>
+    ```
+
+    The available alert types are `info`, `warning`, and `alert`.
+
+1.  **Open a pull request (PR)**
+
+    Once you open a PR, you will be able to preview your results: There will be a section on the page entitled `Deploy Preview for expressjscom-preview ready!` Click the link to see the site rendered from your fork/branch.
+
+    You can use this feature over multiple commits to refine your post by making a `draft` pull request. Once it's ready for review, switch it to a formal PR.
diff --git a/src/content/docs/de/4x/advanced/developing-template-engines.md b/src/content/docs/de/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..243960da6a
--- /dev/null
+++ b/src/content/docs/de/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Template-Engines für Express entwickeln
+description: Erfahren Sie, wie Sie mithilfe von app.engine() benutzerdefinierte Template-Engines für Express.js entwickeln können, mit Beispielen zur Erstellung und Integration Ihrer eigenen Template-Rendering-Logik.
+---
+
+Benutze die `app.engine(ext, callback)` Methode, um deine eigene Template-Engine zu erstellen. `ext` bezieht sich auf die Dateierweiterung, und `callback` ist die Template-Engine-Funktion, , die die folgenden Elemente als Parameter akzeptiert: den Speicherort der Datei, das Optionsobjekt und die Callback-Funktion.
+
+Der folgende Code ist ein Beispiel für die Implementierung einer sehr einfachen Template-Engine zum Rendern von `.ntl` Dateien.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Deine App wird nun in der Lage sein, `.ntl`-Dateien zu rendern. Erstelle eine Datei namens `index.ntl` im `views` Verzeichnis mit folgendem Inhalt.
+
+```pug
+#title#
+#message#
+```
+
+Erstellen Sie dann die folgende Route in Ihrer App.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Wenn du eine Anfrage an die Startseite stellt, wird `index.ntl` als HTML dargestellt.
diff --git a/src/content/docs/de/4x/guide/behind-proxies.mdx b/src/content/docs/de/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..42b2f725fb
--- /dev/null
+++ b/src/content/docs/de/4x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Express hinter Proxies
+description: Lernen Sie, wie Sie Express.js Anwendungen so konfigurieren, dass sie hinter Reverse Proxies korrekt arbeiten, einschließlich der Trust-Proxy-Einstellung für Client-IP-Adressen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Wenn Sie eine Express-App hinter einem Reverse Proxy ausführen, können einige der Express-APIs andere Werte als erwartet zurückgeben. Um dies anzupassen die Einstellung `trust proxy` kann verwendet werden, um Informationen auszublenden, die vom Reverse Proxy in den Express API bereitgestellt werden. Das häufigste Problem sind Express-APIs, die die IP-Adresse des Clients offenlegen, statt dessen eine interne IP-Adresse des Reverse Proxy anzeigen.
+
+<Alert type="info">
+
+Bei der Konfiguration der `trust proxy` Einstellung ist es wichtig, das genaue Setup des
+Reverse Proxy zu verstehen. Da diese Einstellung den in der Anfrage angegebenen Werten vertrauen wird Es ist wichtig, dass
+die Kombination der Einstellung in Express mit der Funktionsweise des Reverse Proxy übereinstimmt.
+
+</Alert>
+
+Die Anwendungseinstellung `trust proxy` kann auf einen der in der folgenden Tabelle aufgelisteten Werte gesetzt werden.
+
+<table class="doktierbar" border="1" markdown="1">
+  <thead><tr><th>Typ</th><th>Wert</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Wenn `true`, wird die IP-Adresse des Clients als linker Eintrag im `X-Forwarded-For` Header verstanden.
+
+Falls „falsch“ die App als direkt gegenüber dem Client verstanden wird und die IP-Adresse des Clients von „req.socket.remoteAddress“ abgeleitet wird. Dies ist die Standardeinstellung.
+
+<Alert type="warnung">
+Wenn Sie auf `true` setzen, ist es wichtig sicherzustellen, dass der letzte Reverse Proxy alle folgenden HTTP-Header löscht/überschreibt: `X-Forwarded-For`, `X-Forwarded-Host` und `X-Forwarded-Proto`, andernfalls ist es möglich, dass der Client irgendeinen Wert angibt.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP-Adressen</td>
+<td markdown="1">
+Eine IP-Adresse, ein Subnetz oder ein Array von IP-Adressen und Subnetzen, die darauf vertrauen, dass es sich um einen Reverse Proxy handelt. Die folgende Liste zeigt die vorkonfigurierten Subnetznamen an:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Sie können IP-Adressen auf jede der folgenden Arten festlegen:
+
+```js
+app.set('trust proxy', 'loopback'); // ein einzelnes Subnetz
+app.set('trust proxy', 'loopback, 123.123.123.123''); // ein Subnetz und eine Adresse
+angeben. et('trust proxy', 'loopback, linklocal, uniquelocal'); // mehrere Subnetze als CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // mehrere Subnetze als Array angeben
+```
+
+Wenn angegeben, werden die IP-Adressen oder Subnetze vom Prozess der Adressermittlung ausgeschlossen und die dem Anwendungsserver nächstgelegene nicht vertrauenswürdige IP-Adresse wird als IP-Adresse des Clients ermittelt. Dies funktioniert indem überprüft wird, ob `req.socket.remoteAddress` vertrauenswürdig ist. Wenn ja, dann wird jede Adresse in `X-Forwarded-For` von rechts nach links bis zur ersten Adresse überprüft, die nicht vertrauenswürdig ist.
+
+</td>
+    </tr>
+    <tr>
+      <td>Nummer</td>
+<td markdown="1">
+Benutzen Sie die Adresse, die höchstens `n` von der Express-Anwendung entfernt ist. `req.socket.remoteAddress` ist der erste Hop, und der Rest wird im `X-Forwarded-For` Header von rechts nach links gesucht. Ein Wert von `0` bedeutet, dass die erste nicht vertrauenswürdige Adresse `req.socket.remoteAddress` ist, d.h. es gibt keinen Reverse-Proxy.
+
+<Alert type="warnung">
+Bei der Verwendung dieser Einstellung ist es wichtig sicherzustellen, dass es keine Multiple gibt, verschiedene Pfade zur Express-Anwendung, so dass der Client kleiner sein kann als die konfigurierte Anzahl von Hops, die entfernt sind andernfalls kann es möglich sein, dass der Kunde irgendeinen Wert angibt.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Funktion</td>
+<td markdown="1">
+Benutzerdefinierte Vertrauens-Implementierung.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    return true; // vertrauenswürdige IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Das Aktivieren von `trust proxy` hat folgende Auswirkungen:
+
+<ul>
+  <li markdown="1">
+    Der Wert von [req.hostname](/en/api#req.hostname) wird vom Wert abgeleitet, der im
+    `X-Forwarded-Host` Header gesetzt wurde , die vom Client oder vom Proxy gesetzt werden kann.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` kann vom Reverse Proxy gesetzt werden, um der App mitzuteilen, ob es `https`
+    oder `http` oder sogar ein ungültiger Name ist. Dieser Wert wird von [req.protocol]reflektiert
+    (/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Die Werte [req.ip](/en/api#req.ip) und [req.ips](/en/api#req.ips) werden auf der Basis der
+    Socket-Adresse und des `X-Forwarded-For` Headers gefüllt beginnend an der ersten nicht
+    vertrauenswürdigen Adresse.
+  </li>
+</ul>
+
+Die `trust proxy` Einstellung ist mit dem [proxy-addr](https://www.npmjs.com/package/proxy-addr) Paket implementiert. Weitere Informationen finden Sie in der Dokumentation.
diff --git a/src/content/docs/de/4x/guide/debugging.mdx b/src/content/docs/de/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..44802397e8
--- /dev/null
+++ b/src/content/docs/de/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debuggen Express
+description: Erfahren Sie, wie Sie Debugging-Logs in Express.js-Anwendungen aktivieren und nutzen können, indem Sie die DEBUG-Umgebungsvariable für verbesserte Fehlerbehebung setzen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um alle internen Logs zu sehen, die in Express verwendet werden, setzen Sie die Umgebungsvariable `DEBUG` auf
+`express:*` beim Starten Ihrer App.
+
+```bash
+$ DEBUG=Express:* node index.js
+```
+
+Verwenden Sie unter Windows den entsprechenden Befehl.
+
+```bash
+> $env:DEBUG = "Express:*"; node index.js
+```
+
+Das Ausführen dieses Befehls auf der vom [Express-Generator] generierten Standard-App (/en/starter/generator) gibt folgende Ausgabe aus:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Wenn eine Anfrage an die App gestellt wird, sehen Sie die im Express-Code angegebenen Protokolle:
+
+```bash
+  express :router dispatching GET / +4h
+  express :router query : / +2ms
+  express :router expresInit : / +0ms
+  express:router favicon : / +0ms
+  express :router logger : / +1ms
+  express :router jsonParser : / +0ms
+  express:router urlencodedParser : / +1ms
+  express :router cookieParser : / +0ms
+  express:router stylus : / +0ms
+  express :router serveStatic : / +2ms
+  express :router router router : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index. ug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Um die Protokolle nur von der Router-Implementierung zu sehen, setzen Sie den Wert `DEBUG` auf `express:router`. Um Protokolle nur von der Anwendungsimplementierung zu sehen, setzten Sie den Wert von `DEBUG` auf `express:application`, und so weiter.
+
+## Anwendungen generiert von `Express`
+
+Eine Anwendung, die durch den Befehl `express generiert` erzeugt wird, benutzt das Modul `debug` und sein Debug-Namensraum wird auf den Namen der Anwendung übertragen.
+
+Wenn Sie zum Beispiel die App mit `$ express Beispiel-App` erstellt haben, können Sie die Debug-Anweisungen mit folgendem Befehl aktivieren:
+
+```bash
+$ DEBUG=Beispiel-app:* Knoten ./bin/www
+```
+
+Sie können mehr als einen Debug-Namensraum angeben, indem Sie eine kommaseparierte Namensliste zuweisen:
+
+```bash
+$ DEBUG=http,mail,Express:* node index.js
+```
+
+## Erweiterte Optionen
+
+Wenn Sie über Node.js laufen, können Sie ein paar Umgebungsvariablen festlegen, die das Verhalten der Debug-Protokollierung ändern:
+
+| Name                | Zweck                                                                       |
+| ------------------- | --------------------------------------------------------------------------- |
+| `DEBUG`             | Aktiviere/deaktiviert bestimmte Debugging-Namensräume.                      |
+| DEBUG_COLORS        | Gibt an, ob Farben in der Debug-Ausgabe verwendet werden sollen oder nicht. |
+| DEBUG_DEPTH\`       | Objektüberprüfungstiefe.                                                    |
+| `DEBUG_FD`          | Datei-Deskriptor, in den die Debug-Ausgabe geschrieben wird.                |
+| `DEBUG_SHOW_HIDDEN` | Zeigt versteckte Eigenschaften auf untersuchten Objekten.                   |
+
+<Alert type="info">
+
+Die Umgebungsvariablen, die mit `DEBUG_` beginnen, werden am Ende in ein Optionsobjekt
+konvertiert, das mit `%o`/`%O` Formate verwendet wird. Siehe die Dokumentation von Node.js für
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) für die vollständige
+Liste.
+
+</Alert>
diff --git a/src/content/docs/de/4x/guide/error-handling.mdx b/src/content/docs/de/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..9db119db26
--- /dev/null
+++ b/src/content/docs/de/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Fehler beim Umgang
+description: Verstehen Sie, wie Express.js Fehler im synchronen und asynchronen Code behandelt, und lernen Sie, benutzerdefinierte Fehlerbehandlung Middleware für Ihre Anwendungen zu implementieren.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ bezieht sich darauf, wie Express Fehler fängt und verarbeitet, die
+sowohl synchron als auch asynchron auftritt. Express kommt mit einem Standardfehler
+\-Handler, damit Sie nicht Ihren eigenen schreiben müssen, um loszulegen.
+
+## Fehler beim Fangen
+
+Es ist wichtig sicherzustellen, dass Express alle Fehler, die auftreten, während
+Routen-Handler und Middleware ausführt.
+
+Fehler, die im synchronen Code innerhalb von Routenhandlern und Middleware
+auftreten, erfordern keine zusätzliche Arbeit. If synchronous code throws an error, then Express will
+catch and process it. Zum Beispiel:
+
+```js
+app.get('/', (req, res) => {
+  werfen neue Fehler ('BROKEN'); // Express fängt dies auf eigene Faust.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Fehler an Express übergeben.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+Zum Beispiel:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = wait getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Wenn `getUserById` einen Fehler oder eine Ablehnung, wird `next` entweder mit
+dem Wurffehler oder dem abgelehnten Wert aufgerufen. Wenn kein abgelehnter Wert angegeben wird, wird `next`
+mit einem Standard-Fehlerobjekt aufgerufen, das vom Express-Router bereitgestellt wird.
+
+Wenn du etwas an die `next()` Funktion übergibt (außer den String `'route'`),
+Express betrachtet die aktuelle Anfrage als Fehler und überspringt alle
+verbleibenden Funktionen zur Fehlerbehandlung und Middleware.
+
+Wenn der Rückruf in einer Sequenz keine Daten enthält, nur Fehler, kannst du den Code
+wie folgt vereinfachen:
+
+```js
+app.get('/', [
+  Funktion (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Im obigen Beispiel wird `next` als Callback für `fs.writeFile` bereitgestellt,
+, das mit oder ohne Fehler aufgerufen wird. Wenn kein Fehler vorliegt, wird der zweite
+\-Handler ausgeführt, sonst fängt und verarbeitet Express den Fehler.
+
+Sie müssen Fehler, die im asynchronen Code auftreten, der von Routenhandlern oder
+Middleware aufgerufen wird, auffangen und an Express zur Verarbeitung weiterleiten. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+Das obige Beispiel benutzt einen "try...catch"-Baustein, um Fehler im
+asynchronen Code zu fangen und sie an den Express zu übergeben. Wenn der Block `try...catch`
+weggelassen wurde, würde Express den Fehler nicht auffinden, da er nicht Teil des synchronen
+Handlercodes ist.
+
+Verwende Versprechungen, um den Overhead des `try...catch`-Bausteins zu vermeiden oder wenn du Funktionen
+benutzt, die Versprechen zurückgeben. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    . hen(() => {
+      werfen neue Fehler ('BROKEN');
+    })
+    . atch(next); // Fehler werden an Express übergeben.
+});
+```
+
+Da Versprechungen automatisch sowohl synchrone Fehler als auch abgelehnte Versprechungen fangen,
+du kannst einfach `next` angeben, da der letzte Catch Handler und Express Fehler fängt an
+weil der Catch-Handler den Fehler als erstes Argument angibt.
+
+Sie können auch eine Kette von Handlern verwenden, um sich auf synchrone Fehler
+zu stützen, indem Sie den asynchronen Code auf etwas Triviales reduzieren. Zum Beispiel:
+
+```js
+app.get('/', [
+  Funktion (req, res, next) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = Daten;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+Das obige Beispiel hat ein paar triviale Anweisungen aus dem Aufruf `readFile`
+. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Dann versucht das obige Beispiel die Daten zu verarbeiten. Wenn dies fehlschlägt, fängt der Synchron-Fehlerhandler
+ihn ab. Hätten Sie diese Verarbeitung innerhalb von
+mit dem `readFile` Callback durchgeführt, dann könnte sich die Anwendung beenden und die Express-Fehler
+Handler würden nicht laufen.
+
+Welche Methode Sie auch immer verwenden, wenn Sie wollen, dass Express-Fehlerbehandler aufgerufen werden und die
+\-Anwendung überleben soll, Sie müssen sicherstellen, dass Express den Fehler empfängt.
+
+## Der Standard-Fehlerhandler
+
+Express kommt mit einem integrierten Fehlerbehandler, der sich um Fehler kümmert, die in der App auftreten könnten. Diese Standard-Middleware-Funktion wird am Ende des Middleware-Funktionstacks hinzugefügt.
+
+Wenn du einen Fehler an `next()` übergibt und ihn nicht in einem benutzerdefinierten
+Handler behandelst, es wird vom eingebauten Fehlerhandler behandelt; wird der Fehler
+mit der Stack-Spur an den Client geschrieben. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Setze die Umgebungsvariable `NODE_ENV` auf `production`, um die App im Produktionsmodus auszuführen.
+
+</Alert>
+
+Wenn ein Fehler geschrieben wird, werden folgende Informationen zur Antwort
+hinzugefügt:
+
+- Der `res.statusCode` wurde von `err.status` (oder `err.statusCode`) gesetzt. Wenn
+  sich dieser Wert außerhalb des 4xx oder 5xx Bereichs befindet, wird er auf 500 gesetzt.
+- Die `res.statusMessage` wurde gemäß dem Statuscode gesetzt.
+- Der Körper wird der HTML-Code der Statuscode-Nachricht sein, wenn in der Produktion
+  \-Umgebung, andernfalls 'err.stack' ist.
+- Alle in einem `err.headers` Objekt angegebenen Header.
+
+Wenn du `next()` mit einem Fehler aufruft, nachdem du die
+Antwort geschrieben hast (z. B. wenn beim Streamen der
+Antwort auf den Client ein Fehler aufgetreten ist), der Express-Standardfehlerhandler schließt die
+Verbindung und schlägt die Anfrage fehl.
+
+Wenn Sie also eine benutzerdefinierte Fehlerbehandlung hinzufügen, müssen Sie den Standard-Express-Fehlerbehandler an
+delegieren wenn die Kopfzeilen
+bereits an den Client gesendet wurden:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Beachte, dass der Standard-Fehlerhandler ausgelöst werden kann, wenn du `next()` mit einem Fehler
+in deinem Code mehrmals aufrufst, auch wenn benutzerdefinierte Fehler beim Umgang mit Middleware vorhanden sind.
+
+Andere Fehler beim Umgang mit Middleware finden Sie unter [Express Middleware](/en/resources/middleware).
+
+## Schreibfehler
+
+Definieren Sie die Middleware-Funktionen wie andere Middleware-Funktionen
+außer Funktionen zur Fehlerbehandlung haben vier Argumente anstelle von drei:
+`(err, req, res, next)`. Zum Beispiel:
+
+```js
+app.use(((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Etwas kaputt!');
+});
+```
+
+Du definierst die Middleware zuletzt nach anderen `app.use()` und Routet Anrufe; zum Beispiel:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // Logik
+});
+```
+
+Antworten innerhalb einer Middleware-Funktion können in jedem Format sein, wie z.B. in einer HTML-Fehlerseite, einer einfachen Nachricht oder einem JSON-String.
+
+Für organisatorische (und höherstufige Framework) Zwecke können Sie
+verschiedene Middleware-Funktionen definieren, so wie Sie es mit den regulären Middleware-Funktionen
+würden. Zum Beispiel, um einen Fehlerhandler
+für Anfragen mit `XHR` und denen ohne folgende zu definieren:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In diesem Beispiel könnten die generischen `logErrors` Anfrage und
+Fehlerinformationen in `stderr` schreiben, zum Beispiel:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Auch in diesem Beispiel wird `clientErrorHandler` wie folgt definiert; in diesem Fall wird der Fehler explizit an den nächsten weitergegeben.
+
+Beachten Sie, dass, wenn _not_ in einer Fehlerbehandlungsfunktion "Weiter" aufruft, Sie dafür verantwortlich sind, die Antwort zu schreiben (und zu beenden). Andernfalls werden diese Anträge "hängen" und sind nicht für die Müllsammlung berechtigt.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementierung der "catch-all" `errorHandler` Funktion wie folgt (zum Beispiel):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Wenn du einen Route-Handler mit mehreren Callback-Funktionen hast, kannst du den Parameter `route` verwenden, um zum nächsten Route-Handler zu springen. Zum Beispiel:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // weitere Bearbeitung dieser Anfrage
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+In diesem Beispiel wird der `getPaidContent` Handler übersprungen, aber alle verbleibenden Handler in `app` für `/a_route_behind_paywall` würden weiterhin ausgeführt werden.
+
+<Alert type="info">
+
+Aufrufe in `next()` und `next(err)` zeigen an, dass der aktuelle Handler abgeschlossen ist und in welchem Zustand ist.
+`next(err)` überspringt alle verbleibenden Handler in der Kette mit Ausnahme derjenigen, die bis zu
+eingerichtet sind, um Fehler wie oben beschrieben zu handhaben.
+
+</Alert>
diff --git a/src/content/docs/de/4x/guide/overriding-express-api.md b/src/content/docs/de/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..e7f6044eb7
--- /dev/null
+++ b/src/content/docs/de/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Überschreiben der Express-API
+description: Erfahren Sie, wie Sie die Express.js API anpassen und erweitern können, indem Sie Methoden und Eigenschaften der Request- und Response-Objekte mittels Prototypen überschreiben.
+---
+
+Die Express API besteht aus verschiedenen Methoden und Eigenschaften auf den Anfrage- und Antwort-Objekten. Diese werden vom Prototyp geerbt. Es gibt zwei Erweiterungspunkte für die Express API:
+
+1. Die globalen Prototypen unter `express.request` und `express.response`.
+2. App-spezifische Prototypen bei `app.request` und `app.response`.
+
+Das Ändern der globalen Prototypen wirkt sich auf alle geladenen Express-Apps im selben Prozess aus. Wenn gewünscht, können Änderungen app-spezifisch gemacht werden, indem nur app-spezifische Prototypen nach dem Erstellen einer neuen App geändert werden.
+
+## Methoden
+
+Sie können die Signatur und das Verhalten bestehender Methoden mit eigenen überschreiben, indem Sie eine benutzerdefinierte Funktion zuweisen.
+
+Folgendes ist ein Beispiel für das Überschreiben des Verhaltens von [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+Die obige Implementierung ändert die ursprüngliche Signatur von `res.sendStatus`. Es akzeptiert nun einen Statuscode, Kodierungstyp und die Nachricht, die an den Client gesendet werden soll.
+
+Die überschriebene Methode kann nun auf diese Weise verwendet werden:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Eigenschaften
+
+Eigenschaften in der Express-API sind entweder:
+
+1. Zugewiesene Eigenschaften (z.B. `req.baseUrl`, `req.originalUrl`)
+2. Definiert als Getters (z. B.: `req.secure`, `req.ip`)
+
+Da Eigenschaften in Kategorie 1 dynamisch auf den `request` und `response` Objekten im Kontext des aktuellen Request-Antwort-Zyklus zugewiesen werden ihr Verhalten kann nicht überschrieben werden.
+
+Eigenschaften der Kategorie 2 können mit der Express API Extensions API überschrieben werden.
+
+Der folgende Code schreibt neu wie der Wert von `req.ip` abgeleitet wird. Jetzt gibt es einfach den Wert des `Client-IP` Request-Headers zurück.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototyp
+
+Um die Express API zur Verfügung zu stellen, werden die Anfrage/Antwort-Objekte an Express weitergegeben (via `app(req, res)`, zum Beispiel, müssen von der gleichen Prototypenkette zu erben. Standardmäßig ist dies `http.IncomingRequest.prototype` für die Anfrage und `http.ServerResponse.prototype` für die Antwort.
+
+Wenn nötig, wird empfohlen, dass dies nur auf der Anwendungsebene und nicht auf globaler Ebene geschieht. Achten Sie auch darauf, dass der verwendete Prototyp die Funktionalität so nah wie möglich an die Standard-Prototypen anpasst.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/de/4x/guide/routing.mdx b/src/content/docs/de/4x/guide/routing.mdx
new file mode 100644
index 0000000000..58254d8832
--- /dev/null
+++ b/src/content/docs/de/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Lernen Sie, wie Sie Routen in Express.js Anwendungen definieren und nutzen können, einschließlich Routenmethoden, Routenpfaden, Parameter und Router für modulare Route.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ bezieht sich darauf, wie die Endpunkte einer Anwendung (URIs) auf Kundenanfragen reagieren.
+Für eine Einführung in das Routing siehe [Basic routing](/en/starter/basic-routing).
+
+Du definierst Routing, indem du Methoden des Express `app` Objekts verwendest, die den HTTP-Methoden entsprechen;
+zum Beispiel, `app. et()` um GET-Anfragen und `app.post` zu behandeln, um POST-Anfragen zu bearbeiten. Für eine vollständige Liste
+siehe [app.METHOD](/en/5x/api#app.METHOD). Du kannst auch [app.all()](/en/5x/api#app.all) verwenden, um alle HTTP-Methoden und [app. se()](/en/5x/api#app.use) bis
+Middleware als Callback-Funktion angeben (siehe [Middleware](/en/guide/using-middleware) für Details).
+
+Diese Routing-Methoden geben eine Callback-Funktion (manchmal auch "handler functions") an, die aufgerufen wird, wenn die Anwendung eine Anfrage an die angegebene Route (Endpunkt) und die HTTP-Methode erhält. Mit anderen Worten, die Anwendung "lauscht" für Anforderungen, die mit der angegebenen Route(s) und Methode(n) übereinstimmen und wenn es ein Spiel erkennt, ruft es die angegebene Callback-Funktion auf.
+
+In der Tat können die Routing-Methoden mehr als eine Callback-Funktion als Argumente haben.
+Mit mehreren Callback-Funktionen, es ist wichtig, `next` als Argument für die Callback-Funktion zur Verfügung zu stellen und dann `next()` im Körper der Funktion aufzurufen, um die Steuerung
+an den nächsten Callback zu übergeben.
+
+Der folgende Code ist ein Beispiel für eine sehr einfache Route.
+
+```js
+const express = require('express ');
+const app = express = );
+
+// Mit "Hallo world" antworten, wenn eine GET-Anfrage an die Homepage
+App gestellt wird. et('/', (req, res) => {
+  res.send('Hallo Welt');
+});
+```
+
+## Routenmethoden
+
+Eine Route-Methode wird von einer der HTTP-Methoden abgeleitet und an eine Instanz der Klasse \`express angehängt.
+
+Der folgende Code ist ein Beispiel für Routen, die für die `GET` und die `POST` Methoden im Root der App definiert sind.
+
+```js
+// GET Methode Route
+app.get('/', (req, res) => {
+  res.end('GET request to the homepage');
+});
+
+// POST method route
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express unterstützt Methoden, die allen HTTP-Anfragemethoden entsprechen: `get`, `post` und so weiter.
+Für eine vollständige Liste siehe [app.METHOD](/en/5x/api#app.METHOD).
+
+Es gibt eine spezielle Routing-Methode, `app.all()`, die benutzt wird, um Middleware-Funktionen an einem Pfad für _all_ HTTP-Requestmethoden zu laden. Zum Beispiel wird der folgende Handler für Anfragen an die Route `"/secret"` ausgeführt, ob `GET` verwendet wird, `POST`, `PUT`, `DELETE`, oder jede andere HTTP-Anfragemethode, die im [http module]unterstützt wird (https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Zugriff auf den geheimen Abschnitt ...');
+  next(); // Kontrolle an den nächsten Handler
+});
+```
+
+## Routenpfade
+
+Routenpfade in Kombination mit einer Anfragemethode definieren die Endpunkte, an denen Anfragen gestellt werden können. Routenpfade können Zeichenketten, Zeichenkettenmuster oder reguläre Ausdrücke sein.
+
+<Alert type="warnung">
+
+Im Ausdruck 5, die Zeichen `? , `+`, `\*`, `[]`und`()\` werden anders behandelt als in Version
+4, bitte lesen Sie die [Migrationsanleitung](/en/guide/migrating-5#path-syntax) für weitere Informationen.
+
+</Alert>
+
+<Alert type="warnung">
+
+Im Ausdruck 4 müssen reguläre Ausdrücke wie `$` mit einem `\` maskiert werden.
+
+</Alert>
+
+<Alert type="info">
+
+Express verwendet [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) um die Route
+Pfade zu treffen; lesen Sie die Dokumentation zu regexp für alle Möglichkeiten bei der Definition von Routenpfaden.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) ist ein praktisches Werkzeug für
+grundlegende Express-Routen zu testen, obwohl es kein Muster-Matching unterstützt.
+
+</Alert>
+
+<Alert type="warning">Abfragezeichenketten sind nicht Teil des Routenweges.</Alert>
+
+### Routenpfade basierend auf Zeichenketten
+
+Dieser Routenpfad wird den Anfragen an die Root-Route `/` entsprechen.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Dieser Routenpfad wird den Anfragen auf `/about` entsprechen.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Dieser Routenpfad entspricht den Anfragen zu `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Routenpfade basierend auf Stringmustern
+
+<Alert type="warnung">
+
+Die Zeichenkettenmuster in Express 5 funktionieren nicht mehr. Weitere Informationen finden Sie in der Migration
+Anleitung .
+
+</Alert>
+
+Dieser Routenpfad stimmt mit `acd` und `abcd` überein.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `abcd`, `abbcd`, `abbbcd` usw. überein.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd` usw. überein.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `/abe` und `/abcde` überein.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Routenpfade basierend auf regulären Ausdrücken
+
+Dieser Routenpfad stimmt mit einem "a" darin überein.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Dieser Routenpfad stimmt mit 'butterfly' und 'Drachenfly' überein, aber nicht mit 'butterflyman', 'Drachenflyman' und so weiter.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Routenparameter
+
+Routenparameter sind URL-Segmente, die zur Erfassung der an ihrer Position in der URL angegebenen Werte verwendet werden. Die erfassten Werte werden im Objekt `req.params` gefüllt, wobei der Name des im Pfad angegebenen Routenparameter als ihre jeweiligen Schlüssel angegeben ist.
+
+```
+Routenpfad: /users/:userId/books/:bookId
+Anfrage-URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Um Routen mit Routenparametern zu definieren, geben Sie einfach die Routenparameter im Pfad der Route, wie unten gezeigt, an.
+
+```js
+app.get('/users/:userId/bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="warnung">
+
+Der Name der Routenparameter muss aus "Wortzeichen" ([A-Za-z0-9_] ) bestehen.
+
+</Alert>
+
+Da die Bindestriche (`-`) und der Punkt (`.`) wörtlich interpretiert werden, können sie zusammen mit Routenparametern für nützliche Zwecke verwendet werden.
+
+```
+Routenpfad: /flights/:from-:to
+Abfrage URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Routenpfad: /plantae/:genus.:species
+Anfrage URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="warnung">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Um mehr Kontrolle über den exakten String zu haben, der mit einem Route-Parameter übereinstimmen kann, können Sie einen regulären Ausdruck in Klammern (`()`) anhängen:
+
+```
+Routenpfad: /user/:userId(\d+)
+Anfrage-URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warnung">
+
+Weil der reguläre Ausdruck in der Regel Teil einer literalen Zeichenkette ist, Stellen Sie sicher, dass Sie `\`
+Zeichen mit einem zusätzlichen Backslash maskieren, zum Beispiel `\d+`.
+
+</Alert>
+
+<Alert type="warnung">
+In Express 4.x wird <a href="https://github.com/expressjs/express/issues/2495">das `*` Zeichen in regulären Ausdrücken nicht auf die übliche Weise</a> interpretiert. Benutze `{0,}` anstelle von `*`. Dies wird wahrscheinlich in Express 5 behoben.
+</Alert>
+
+## Routenhandler
+
+Du kannst mehrere Callback-Funktionen bereitstellen, die sich wie [middleware](/en/guide/using-middleware) verhalten um eine Anfrage zu bearbeiten. Die einzige Ausnahme ist, dass diese Callbacks `next('route')` aufrufen könnten, um die restlichen Rufnummern zu umgehen. Sie können diesen Mechanismus nutzen, um Vorbedingungen auf einer Route aufzuerlegen, dann die Kontrolle an die nachfolgenden Routen übergeben, wenn es keinen Grund gibt, mit der aktuellen Route fortzufahren.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In diesem Beispiel:
+
+- `GET /user/5` → behandelt durch die erste Route → sendet "Benutzer 5"
+- `GET /user/0` → erste Routenaufrufe `next('route')`, überspringt zur nächsten passenden `/user/:id` Route
+
+Routenhandler können in Form einer Funktion, eines Arrays von Funktionen oder Kombinationen beider sein, wie in den folgenden Beispielen gezeigt.
+
+Eine einzelne Callback-Funktion kann eine Route handhaben. Zum Beispiel:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hallo von A!');
+});
+```
+
+Mehr als eine Callback-Funktion kann eine Route handhaben (stelle sicher, dass du das `next` Objekt angibst). Zum Beispiel:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    Konsole.og('die Antwort wird von der nächsten Funktion gesendet. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Hallo von B!');
+  }
+);
+```
+
+Ein Array von Callback-Funktionen kann eine Route handhaben. Zum Beispiel:
+
+```js
+const cb0 = function (req, res, next) {
+  Konsole.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Hallo von C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Eine Kombination aus unabhängigen Funktionen und Arrays von Funktionen kann eine Route handhaben. Zum Beispiel:
+
+```js
+const cb0 = function (req, res, next) {
+  Konsole.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+App.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    Konsole.og('die Antwort wird von der nächsten Funktion gesendet. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Hallo von D!');
+  }
+);
+```
+
+## Antwortmethoden
+
+Die Methoden auf dem Antwortobjekt (`res`) in der folgenden Tabelle können eine Antwort an den Client senden und den Request-Antwort-Zyklus beenden. Wenn keine dieser Methoden von einem Routenhandler aufgerufen wird, bleibt die Client-Anfrage hängen.
+
+| Methode                                       | Beschreibung                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Fordern Sie eine Datei zum Download an.                                                                   |
+| [res.end()](/en/5x/api#res.end)               | Beenden Sie den Antwort-Prozess.                                                                          |
+| [res.json()](/en/5x/api#res.json)             | Sende eine JSON-Antwort.                                                                                  |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Senden Sie eine JSON-Antwort mit JSONP-Unterstützung.                                                     |
+| [res.redirect()](/en/5x/api#res.redirect)     | Anfrage umleiten.                                                                                         |
+| [res.render()](/en/5x/api#res.render)         | Ansichtsvorlage ausblenden.                                                                               |
+| [res.send()](/en/5x/api#res.send)             | Senden Sie eine Antwort von verschiedenen Typen.                                                          |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Senden Sie eine Datei als octet-Stream.                                                                   |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Legen Sie den Antwort-Statuscode fest und senden Sie seine Zeichenfolge Repräsentation als Antwortkörper. |
+
+## app.route()
+
+Sie können verkettende Routenhandler für einen Routenpfad erstellen, indem Sie `app.route()` verwenden.
+Da der Weg an einem einzigen Ort angegeben wird, ist die Schaffung modularer Routen hilfreich, ebenso wie die Reduzierung von Redundanz und Typos. Weitere Informationen über Routen finden Sie unter [Router() documentation](/en/5x/api#router).
+
+Hier ist ein Beispiel für verkettete Routenhandler, die mit `app.route()` definiert werden.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res. end('Holt ein zufälliges Buch');
+  })
+  . ost(req, res) => {
+    res.send('Add a book');
+  })
+  . ut((req, res) => {
+    res.send('Buch aktualisieren');
+});
+```
+
+## express.Router
+
+Verwende die Klasse `express.Router`, um modulare mountbare Routenhandler zu erstellen. Eine `Router`-Instanz ist ein komplettes Middleware- und Routing-System; aus diesem Grund wird sie oft als "Mini-App" bezeichnet.
+
+Das folgende Beispiel erzeugt einen Router als Modul, lädt eine Middleware-Funktion darin definiert einige Routen und mountet das Router-Modul auf einem Pfad in der Hauptanwendung.
+
+Erstelle eine Router-Datei namens `birds.js` im App-Verzeichnis, mit folgendem Inhalt:
+
+```js
+const express = require('express');
+const Router = express. outer();
+
+// Middleware, die spezifisch für diesen Router
+const timeLog = (req, res, next) => {
+  Konsole ist. og('Zeit: ', Date.now());
+  next();
+};
+Router. se(timeLog);
+
+// die Startseite Route
+router.get('/', (req, res) => {
+  res. end('Birds home page');
+});
+// die "about route
+definieren. et('/about', (req, res) => {
+  res.send('Über Vögel');
+});
+
+module.exports = router;
+```
+
+Laden Sie dann das Router-Modul in der App:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', Vögel);
+```
+
+Die App wird nun in der Lage sein, Anfragen an `/birds` und `/birds/about` zu bearbeiten, aufrufen sowie die Middleware-Funktion `timeLog` aufrufen, die spezifisch für die Route ist.
+
+Aber wenn die übergeordnete Route `/birds` Pfadparameter hat, wird sie standardmäßig nicht von den Unterrouten aus erreichbar sein. Um es zugänglich zu machen, müssen Sie die Option "mergeParams" an den Router-Konstruktor [reference](/en/5x/api#app.use) übergeben.
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/de/4x/guide/using-middleware.mdx b/src/content/docs/de/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..adfe7537b4
--- /dev/null
+++ b/src/content/docs/de/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Middleware verwenden
+description: Lernen Sie, wie Sie Middleware in Express.js-Anwendungen verwenden, einschließlich Middleware auf Anwendungsebene und Routerebene, Fehlerbehandlung und Integration von Middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express ist ein Routing- und Middleware-Webframework mit minimaler Funktionalität: Eine Express-Anwendung ist im Wesentlichen eine Reihe von Middleware-Funktionsaufrufen.
+
+_Middleware_ Funktionen sind Funktionen, die Zugriff auf das [request object](/en/5x/api#req) (`req`), das [Antwort-Objekt](/en/5x/api#res) (`res`) und die nächste Middleware-Funktion im Request-Antwort-Zyklus der Anwendung. Die nächste Middleware-Funktion wird üblicherweise durch eine Variable namens `next` bezeichnet.
+
+Middleware-Funktionen können folgende Aufgaben ausführen:
+
+- Führe jeden Code aus.
+- Änderungen an der Anfrage und den Antwort-Objekten vornehmen.
+- Beende den Request-Antwort-Zyklus.
+- Rufen Sie die nächste Middleware-Funktion im Stack auf.
+
+Wenn die aktuelle Middleware-Funktion den Request-Antwort-Zyklus nicht beendet, muss sie `next()` aufrufen, um die Kontrolle an die nächste Middleware-Funktion zu übergeben. Andernfalls bleibt die Anfrage hängen.
+
+Eine Express-Anwendung kann folgende Arten von Middleware verwenden:
+
+- [Middleware](#middleware.application)
+- [Router-Level-Middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Integrierte Middleware](#middleware.built-in)
+- [Middleware von Drittanbietern](#middleware.third-party)
+
+Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mount-Pfad laden.
+Sie können auch eine Reihe von Middleware-Funktionen zusammen laden, die einen Sub-Stack des Middleware-Systems an einem Mount-Punkt erzeugen.
+
+## Middleware auf Anwendungsebene
+
+Binde Middleware auf Anwendungsebene an eine Instanz des [app object](/en/5x/api#app) durch Verwendung der `app.use()` und `app. ETHOD()` Funktionen, wobei `METHOD` die HTTP-Methode der Anfrage ist, die die Middleware-Funktion in Kleinbuchstaben behandelt (wie GET, PUT, oder POST)
+
+Dieses Beispiel zeigt eine Middleware-Funktion ohne Mount-Pfad. Die Funktion wird jedes Mal ausgeführt, wenn die App eine Anfrage erhält.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Dieses Beispiel zeigt eine Middleware-Funktion, die auf dem `/user/:id` Pfad eingehängt ist. Die Funktion wird für jede Art von
+HTTP-Anfrage im `/user/:id` Pfad ausgeführt.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Dieses Beispiel zeigt eine Route und deren Handler-Funktion (Middleware-System). Die Funktion bearbeitet GET-Anfragen an den Pfad `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Hier ist ein Beispiel für das Laden einer Reihe von Middleware-Funktionen an einem Mount-Punkt, mit einem Mount-Pfad.
+Es illustriert einen Middleware-Unterstapel, der Anfrageinformationen für jede Art von HTTP-Anfrage in den Pfad `/user/:id` ausgibt.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.og('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Routenhandler ermöglichen es Ihnen, mehrere Routen für einen Pfad zu definieren. Das folgende Beispiel definiert zwei Routen für GET-Anfragen zum Pfad `/user/:id`. Die zweite Route wird keine Probleme verursachen, aber sie wird nie aufgerufen, weil die erste Route den Request-Antwort-Zyklus beendet.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('User Info');
+  }
+);
+
+// Handler für den /user/:id Pfad, der die Benutzer-ID
+App ausgibt. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Um die restlichen Middleware-Funktionen eines Routers Middleware-Stacks zu überspringen, rufen Sie `next('route')` auf, um die Kontrolle an die nächste Route zu übergeben.
+
+<Alert type="info">
+
+`next('route')` funktioniert nur in Middleware-Funktionen, die mit den Funktionen
+`app.METHOD()` oder `router.METHOD()` geladen wurden.
+
+</Alert>
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, Nächste) => {
+    // wenn die Benutzer-ID 0 ist springe zur nächsten Route
+    wenn (req. arams. d === '0') als nächstes ('route');
+    // Andernfalls übergeben Sie die Steuerung an die nächste Middleware-Funktion in diesem Stack
+    else next();
+  },
+  (req, res, next) => {
+    // Senden Sie eine reguläre Antwort
+    res. end('regular');
+  }
+);
+
+// Handler für den /user/:id Pfad, der eine spezielle Antwort
+App sendet. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware kann auch in einem Array für Wiederverwendbarkeit deklariert werden.
+
+Dieses Beispiel zeigt ein Array mit einem Middleware-Sub-Stack an, das GET-Anfragen im Pfad `/user/:id` behandelt
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+App.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Middleware auf Routerebene
+
+Middleware auf Router-Ebene funktioniert wie Middleware auf Anwendungsebene, es sei denn, es ist an eine Instanz von `express.Router()` gebunden.
+
+```js
+const router = express.Router();
+```
+
+Laden Sie die Middleware router-level mittels der Funktionen `router.use()` und `router.METHOD()`.
+
+Der folgende Beispielcode repliziert das oben angezeigte Middleware-System für Middleware auf Anwendungsebene:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. Externe();
+
+// eine Middleware-Funktion ohne Mount-Pfad. Dieser Code wird für jede Anfrage an den Router
+ausgeführt. se(req, res, next) => {
+  console.log('Zeit:', Datum. ow());
+  next();
+});
+
+// Ein Middleware-Sub-Stack zeigt Anfrageinformationen für jede Art von HTTP-Anfrage an den /user/:id path
+Router an. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    Konsole. og('Request Typ:', req. ethod);
+    next();
+  }
+);
+
+// ein Middleware-Sub-Stack, der GET-Anfragen an den /user/:id path
+Router verarbeitet. et(
+  '/user/:id',
+  (req, res, Nächste) => {
+    // wenn die Benutzer-ID 0 ist springe zum nächsten Router
+    wenn (req. arams. d === '0') als nächstes ('route');
+    // Andernfalls übergeben Sie die Kontrolle an die nächste Middleware-Funktion in diesem Stapel
+    else next();
+  },
+  (req, res, next) => {
+    // rendern Sie eine reguläre Seite
+    res. ender('regular');
+  }
+);
+
+// Handler für den /user/:id Pfad, der eine spezielle Seite
+Router darstellt. et('/user/:id', (req, res, next) => {
+  Konsole. og(req.params.id);
+  res.render('special');
+});
+
+// Router auf die App
+app.use('/', Router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. Externe ();
+
+// Vorhersage des Routers mit Scheck und Kaution bei Bedarf
+Router. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hallo, user!');
+});
+
+// den Router verwenden und 401 alles, was durch die
+App fällt. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Fehler beim Umgang mit Middleware
+
+<Alert type="warnung">
+
+Bei der Fehlerbehebung der Middleware werden immer _vier_ Argumente verwendet. Sie müssen vier Argumente angeben, um
+als Middleware-Funktion zu identifizieren. Selbst wenn du das `next`
+Objekt nicht verwenden musst, musst du es angeben, um die Signatur zu pflegen. Andernfalls wird das `next` Objekt
+als reguläre Middleware interpretiert und wird Fehler nicht bearbeiten.
+
+</Alert>
+
+Definieren Sie die Middleware-Funktionen wie andere Middleware-Funktionen außer mit vier Argumenten anstelle von drei, speziell mit der Signatur `(err, req, res, next)`:
+
+```js
+app.use(((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Etwas kaputt!');
+});
+```
+
+Details über die Fehlerbehandlungsmittelsoftware finden Sie hier: [Fehlerbehandlung](/en/guide/error-handling).
+
+## Integrierte Middleware
+
+Ab Version 4.x ist Express nicht mehr abhängig von [Connect](https://github.com/senchalabs/connect). Die Middleware-
+\-Funktionen, die zuvor mit Express integriert wurden, befinden sich nun in separaten Modulen; siehe [Liste der Middleware-Funktionen](https://github.com/senchalabs/connect#middleware).
+
+Express hat die folgenden integrierten Middleware-Funktionen:
+
+- [express.static](/en/5x/api#express.static) dient statischen Assets wie HTML-Dateien, Bilder und so weiter.
+- [express.json](/en/5x/api#express.json) analysiert eingehende Anfragen mit JSON Payloads. **HINWEIS: Verfügbar mit Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analysiert eingehende Anfragen mit URL-kodierten Payloads. **HINWEIS: Verfügbar mit Express 4.16.0+**
+
+## Drittanbieter-Middleware
+
+Verwenden Sie Middleware von Drittanbietern, um Funktionen zu Express-Apps hinzuzufügen.
+
+Installieren Sie das Modul Node.js für die erforderliche Funktionalität, laden Sie es dann in Ihrer App auf der Anwendungsebene oder auf der Routerebene.
+
+Das folgende Beispiel zeigt die Installation und das Laden der Cookie-Parsing-Middleware-Funktion "cookie-parser".
+
+```bash
+$ npm Cookie-Parser installieren
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Für eine partielle Liste der Middleware-Funktionen von Drittanbietern, die häufig mit Express verwendet werden, siehe: [Middleware](../resources/middleware).
diff --git a/src/content/docs/de/4x/guide/using-template-engines.mdx b/src/content/docs/de/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..0a5b37a7c5
--- /dev/null
+++ b/src/content/docs/de/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Template-Engines mit Express verwenden
+description: Entdecken Sie, wie Sie Template-Engines wie Pug, Handlebars und EJS mit Express.js integrieren und nutzen können, um dynamische HTML-Seiten effizient zu machen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Eine _template engine_ ermöglicht es Ihnen, statische Template-Dateien in Ihrer Anwendung zu verwenden. Zur Laufzeit ersetzt die Template-Engine
+Variablen in einer Template-Datei mit aktuellen Werten und verwandelt die Vorlage in eine HTML-Datei, die an den Client gesendet wird.
+Dieser Ansatz erleichtert die Gestaltung einer HTML-Seite.
+
+Der [Express-Anwendungsgenerator](/en/starter/generator) verwendet [Pug](https://pugjs.org/api/getting-started.html) als Standardwert, aber es unterstützt auch [Handlebars](https://www.npmjs.com/package/handlebars), und [EJS](https://www.npmjs.com/package/ejs), unter anderem.
+
+Um Template-Dateien zu rendern, setzen Sie folgende [Anwendungs-Einstellungen-Eigenschaften](/en/4x/api#app.set), in der Standardeinstellung `app.js`, die vom Generator erstellt wurde:
+
+- `views`, das Verzeichnis, in dem sich die Template-Dateien befinden. Eg: `app.set('views', './views')`.
+  Dies ist standardmäßig im Verzeichnis `views` im Root-Verzeichnis der Anwendung.
+- `view engine`, die zu verwendende Template-Engine. Um zum Beispiel die Mückenvorlagen-Engine zu verwenden: `app.set('view engine', 'pug')`.
+
+Installieren Sie dann das entsprechende Template Engine npm Paket; zum Beispiel um Pug:
+
+```bash
+$ npm Installations-Pug --save
+```
+
+<Alert type="warnung">
+Express-konforme Template-Engines wie MUG exportieren eine Funktion namens `__express(filePath, options, callback)`,
+welche `res.render()` aufruft, um den Template-Code zu rendern.
+
+Einige Template-Engines folgen nicht dieser Konvention. Die [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+Bibliothek folgt dieser Konvention, indem sie alle populären Template-Engines von Node.js abbildet, und arbeitet daher nahtlos in Express.
+
+</Alert>
+
+Nachdem die View Engine gesetzt ist, müssen Sie nicht die Engine angeben oder das Template Engine Modul in Ihrer App laden;
+Express lädt das Modul intern, zum Beispiel:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Erstelle dann eine Pug Template Datei namens `index.pug` im `views` Verzeichnis mit folgendem Inhalt:
+
+```pug
+html
+  Kopf
+    title= title
+  Körper
+    h1= Nachricht
+```
+
+Erstelle eine Route um die `index.pug` Datei zu rendern. Wenn die `view engine` Eigenschaft nicht gesetzt ist,
+musst du die Erweiterung der `view` Datei angeben. Andernfalls können Sie es auslassen.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hallo there!' });
+});
+```
+
+Wenn du eine Anfrage an die Startseite stellt, wird die `index.pug` Datei als HTML dargestellt.
+
+Der View Engine-Cache speichert nicht den Inhalt der Templateausgabe, sondern nur die zugrunde liegende Vorlage selbst. Die Ansicht wird noch mit jeder Anfrage neu gerendert, auch wenn der Cache eingeschaltet ist.
diff --git a/src/content/docs/de/4x/guide/writing-middleware.mdx b/src/content/docs/de/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..f14875ff22
--- /dev/null
+++ b/src/content/docs/de/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Schreibe Middleware für die Verwendung in Express-Apps
+description: Erfahren Sie, wie Sie benutzerdefinierte Middleware-Funktionen für Express.js-Anwendungen schreiben, einschließlich Beispielen und Best Practices zur Verbesserung der Request- und Response-Behandlung.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ Funktionen sind Funktionen, die Zugriff auf das [request object](/en/5x/api#req) (`req`), die [Antwort-Objekt](/en/5x/api#res) (`res`) und die `next` Funktion im Request-Antwort-Zyklus der Anwendung. Die `next`-Funktion ist eine Funktion im Express-Router, der beim Aufruf die Middleware ausführt, die die aktuelle Middleware abfolgt.
+
+Middleware-Funktionen können folgende Aufgaben ausführen:
+
+- Führe jeden Code aus.
+- Änderungen an der Anfrage und den Antwort-Objekten vornehmen.
+- Beende den Request-Antwort-Zyklus.
+- Rufen Sie die nächste Middleware im Stapel auf.
+
+Wenn die aktuelle Middleware-Funktion den Request-Antwort-Zyklus nicht beendet, muss sie `next()` aufrufen, um die Kontrolle an die nächste Middleware-Funktion zu übergeben. Andernfalls bleibt die Anfrage hängen.
+
+Die folgende Abbildung zeigt die Elemente eines Middleware-Funktionsaufrufs:
+
+<div class="tabell-scroller">
+<table id="mw-Abbildung">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elemente eines Middleware Funktionsaufrufs" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">HTTP-Methode, für die die Middleware-Funktion gilt.</div>
+
+<div class="callout" id="callout2">
+  Pfad (Route), für den die Middleware-Funktion gilt.
+</div>
+
+<div class="callout" id="callout3">
+  Die Middleware-Funktion.
+</div>
+
+<div class="callout" id="callout4">
+  Callback-Argument an die Middleware-Funktion, genannt "Next" durch Konvention.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">Antwort</a> Argument auf die Middleware-Funktion, genannt "res" von
+  Konvention.
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">Request</a> Argument an die Middleware-Funktion, genannt "req" von Konvention.</div>
+</td>
+</tr>
+</table>
+</div>
+
+Beginnend mit Express 5 ruft Middleware-Funktionen, die ein Versprechen zurückgeben, `next(value)` auf, wenn sie einen Fehler ablehnen oder werfen. `next` wird entweder mit dem abgelehnten Wert oder mit dem Wurffehler aufgerufen.
+
+## Beispiel
+
+Hier ist ein Beispiel für eine einfache "Hallo World"-Express-Anwendung.
+Der Rest dieses Artikels definiert und fügt der Anwendung drei Middleware-Funktionen hinzu:
+eine mit dem Namen `myLogger`, die eine einfache Logmeldung ausgibt, einen namens `requestTime`, der
+den Zeitstempel der HTTP-Anfrage anzeigt und einen, der `validateCookies` genannt wird, der eingehende Cookies validiert.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hallo World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware-Funktion myLogger
+
+Hier ist ein einfaches Beispiel für eine Middleware-Funktion namens "myLogger". Diese Funktion druckt nur
+"LOGGED", wenn eine Anfrage an die App durchläuft. Die Middleware-Funktion wird einer
+Variable mit dem Namen `myLogger` zugewiesen.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="warnung">
+
+Beachten Sie den obigen Aufruf zu `next()`. Beim Aufruf dieser Funktion wird die nächste Middleware-Funktion in
+der App aufgerufen. Die `next()` Funktion ist kein Teil des Knotens. s oder Express API, aber ist das dritte
+\-Argument, das an die Middleware-Funktion übergeben wird. Die `next()` Funktion kann alles benannt werden,
+, aber nach der Konvention wird sie immer als "weiter" bezeichnet. Um Verwirrung zu vermeiden, verwenden Sie immer dieses Übereinkommen.
+
+</Alert>
+
+Um die Middleware-Funktion zu laden, rufen Sie `app.use()` auf, indem Sie die Middleware-Funktion angeben.
+Zum Beispiel lädt der folgende Code die `myLogger` Middleware-Funktion vor der Route zum Root-Pfad (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hallo World!');
+});
+
+app.listen(3000);
+```
+
+Jedes Mal, wenn die App eine Anfrage erhält, gibt sie die Nachricht "LOGGED" auf das Terminal aus.
+
+Die Reihenfolge des Laden von Middleware ist wichtig: Middleware-Funktionen, die zuerst geladen werden, werden auch zuerst ausgeführt.
+
+Wenn `myLogger` nach der Route zum Wurzelpfad geladen wird, erreicht die Anfrage nie und die App druckt nicht "LOGGED", da der Route-Handler des Root-Pfades den Request-Antwort-Zyklus beendet.
+
+Die Middleware-Funktion `myLogger` druckt einfach eine Nachricht, übergibt dann die Anfrage an die nächste Middleware-Funktion im Stack durch Aufruf der `next()` Funktion.
+
+### Middleware-Funktionsanfragezeit
+
+Als nächstes erstellen wir eine Middleware-Funktion namens "requestTime" und fügen eine Eigenschaft namens `requestTime`
+dem Anfrageobjekt hinzu.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+Die App verwendet nun die „requestTime“-Middleware-Funktion. Auch die Callback-Funktion der Root-Pfadroute verwendet die Eigenschaft, die die Middleware-Funktion zu `req` hinzufügt (das Anfrageobjekt).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+Wenn Sie eine Anfrage an das Stammverzeichnis der App stellen, zeigt die App nun den Zeitstempel Ihrer Anfrage im Browser an.
+
+### Middleware-Funktion validateCookies
+
+Schließlich erstellen wir eine Middleware-Funktion, die eingehende Cookies validiert und eine 400 Antwort schickt, wenn Cookies ungültig sind.
+
+Hier ist eine Beispielfunktion, die Cookies mit einem externen Asynchrondienst überprüft.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    wait externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Ungültige Cookies');
+  }
+}
+```
+
+Hier verwenden wir die [`cookie-parser`](/en/resources/middleware/cookie-parser) Middleware, um eingehende Cookies vom `req` Objekt zu analysieren und sie an unsere `cookieValidator` Funktion zu übergeben. Die `validateCookies` Middleware gibt ein Versprechen zurück, das bei Ablehnung automatisch unseren Fehlerhandler auslöst.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  wartet cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// Fehlerbehandler
+app. se(err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="warnung">
+
+Beachte, wie `next()` nach `wait cookieValidator(req.cookies)` aufgerufen wird. Dies stellt sicher, dass, wenn
+`cookieValidator` auflöst, die nächste Middleware im Stack aufgerufen wird. Wenn du etwas
+an die `next()` Funktion übergibt (außer den String `'route'` oder `'router'`), Express betrachtet die aktuelle
+Anfrage als Fehler und überspringt alle verbleibenden Funktionen zur Fehlerbehandlung und Middleware
+.
+
+</Alert>
+
+Weil Sie Zugriff auf das Anfrageobjekt, das Antwortobjekt, die nächste Middleware-Funktion im Stapel und den gesamten Knoten haben. s API, die Möglichkeiten mit Middleware-Funktionen sind endlos.
+
+Für weitere Informationen über Express Middleware siehe: [Express Middleware](/en/guide/using-middleware).
+
+## Konfigurierbare Middleware
+
+Wenn Sie Ihre Middleware konfigurieren müssen, exportieren Sie eine Funktion, die ein Optionsobjekt oder andere Parameter akzeptiert, , die dann die Middleware-Implementierung basierend auf den Eingabeparametern zurückgibt.
+
+Datei: `my-middleware.js`
+
+```js
+modul.xports = function (options) {
+  return function (req, res, next) {
+    // Implementierung der Middleware-Funktion basierend auf dem Options-Objekt
+    next();
+  };
+};
+```
+
+Die Middleware kann nun wie unten gezeigt verwendet werden.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Siehe [cookie-session](https://github.com/expressjs/cookie-session) und [compression](https://github.com/expressjs/compression) für Beispiele konfigurierbarer Middleware.
diff --git a/src/content/docs/de/4x/starter/basic-routing.mdx b/src/content/docs/de/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..dce7483626
--- /dev/null
+++ b/src/content/docs/de/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basisrouting
+description: Lernen Sie die Grundlagen des Routings in Express.js Anwendungen kennen, wie Sie Routen definieren, HTTP-Methoden handhaben und Routenhandler für Ihren Webserver erstellen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ bezieht sich darauf, wie eine Anwendung auf einen bestimmten Endpunkt antwortet , die eine URI (oder Pfad) und eine bestimmte HTTP-Request-Methode (GET, POST usw.) ist.
+
+Jede Route kann eine oder mehrere Handler-Funktionen haben, die ausgeführt werden, wenn die Route übereinstimmt.
+
+Die Routendefinition nimmt folgende Struktur ein:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Wo:
+
+- `app` ist eine Instanz von `express `.
+- `METHOD` ist eine [HTTP-Anfrage-Methode](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in Kleinbuchstaben.
+- `PATH` ist ein Pfad auf dem Server.
+- `HANDLER` ist die Funktion, die ausgeführt wird, wenn die Route übereinstimmt.
+
+<Alert type="warnung">
+
+Dieses Tutorial setzt voraus, dass eine Instanz von `express ` namens `app` erstellt wird und der Server
+läuft. Wenn du nicht vertraut bist, eine App zu erstellen und sie zu starten, schau dir das Hallo Welt
+Beispiel.
+
+</Alert>
+
+Die folgenden Beispiele veranschaulichen die Definition einfacher Routen.
+
+Antworte mit `Hallo World!` auf der Homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hallo Welt!');
+});
+```
+
+Antwort auf eine POST-Anfrage auf der Root-Route (`/`), der Startseite der Anwendung:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Hat eine POST-Anfrage');
+});
+```
+
+Antworte auf eine PUT-Anfrage auf die `/user`-Route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Eine PUT-Anfrage bei /user');
+});
+```
+
+Antworte auf eine LÖSCHE Anfrage auf die `/user`-Route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Erhalte eine DELETE Anfrage unter /user');
+});
+```
+
+Weitere Details zum Routen finden Sie im [Routing Guide](/en/guide/routing).
diff --git a/src/content/docs/de/4x/starter/examples.mdx b/src/content/docs/de/4x/starter/examples.mdx
new file mode 100644
index 0000000000..85b9e4ad97
--- /dev/null
+++ b/src/content/docs/de/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Express-Beispiele
+description: Entdecken Sie eine Sammlung von Express.js Anwendungsbeispielen, die verschiedene Anwendungsfälle, Integrationen und erweiterte Konfigurationen umfassen, um Ihnen zu helfen Ihre Projekte zu erlernen und zu bauen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Authentifizierung mit Login und Passwort
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - HTTP-Inhaltsaushandlung
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Arbeiten mit Cookie-basierten Sitzungen
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Arbeiten mit Cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Übertragung von Dateien zum Client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Arbeiten mit eingebetteten JavaScript-Vorlagen (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Fehlerseiten erstellen
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Mit Fehler-Middleware arbeiten
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Einfacher Anfragehandler
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown als Template-Engine
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Mit mehreren Express-Routern arbeiten
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - Controller im MVC-Stil
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Verfolgung der Online-Benutzeraktivität mit `online` und `redis` Paketen
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Arbeiten mit Routenparametern
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Mehrere HTTP-Operationen auf derselben Ressource
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Routen mit einer Karte organisieren
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Mit Route Middleware arbeiten
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Routen pro Ressource organisieren
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Such-API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - Benutzersitzungen
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Serviere statische Dateien
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Arbeiten mit virtuellen Hosts
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Ansichten dynamisch rendern
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Speichern von Daten im Anfrageobjekt zwischen Middleware-Aufrufen
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Einfacher API-Dienst
+
+## Zusätzliche Beispiele
+
+Dies sind einige zusätzliche Beispiele mit umfassenderen Integrationen.
+
+<Alert type="warnung">
+  Diese Informationen beziehen sich auf Sites, Produkte oder Module, die nicht vom Expressjs Team
+  betreut werden. Die Auflistung hier stellt keine Billigung oder Empfehlung des Projektteams von
+  Expressjs dar.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Vollstack App mit Express und Next.js mit [Prisma](https://www.npmjs.com/package/prisma) als ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API mit Express in TypeScript mit [Prisma](https://www.npmjs.com/package/prisma) als ORM
diff --git a/src/content/docs/de/4x/starter/faq.md b/src/content/docs/de/4x/starter/faq.md
new file mode 100644
index 0000000000..8df0cc1a28
--- /dev/null
+++ b/src/content/docs/de/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Finden Sie Antworten auf häufig gestellte Fragen zu Express.js, darunter Themen wie Anwendungsstruktur, Modelle, Authentifizierung, Template-Engines, Fehlerbehandlung und mehr.
+---
+
+## Wie kann ich meine Anwendung strukturieren?
+
+Auf diese Frage gibt es keine endgültige Antwort. Die Antwort hängt von
+vom Umfang Ihrer Anwendung und dem beteiligten Team ab. Um so flexibel wie möglich
+zu sein, macht Express keine Annahmen in Bezug auf die Struktur.
+
+Routen und andere anwendungsspezifische Logik können in beliebig vielen Dateien
+in beliebiger Verzeichnisstruktur gespeichert werden. Folgende
+Beispiele für Inspirationen anzeigen:
+
+- [Route Listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Routenplane](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Außerdem gibt es Erweiterungen von Drittanbietern für Express, die einige dieser Muster vereinfachen:
+
+- [Ressourcenreiches Routen](https://github.com/expressjs/express-resource)
+
+## Wie definiere ich Modelle?
+
+Express hat keine Vorstellung von Datenbanken. Dieses Konzept ist
+bis zu Drittanbieter-Knotenmodulen übrig und erlaubt Ihnen eine
+Schnittstelle mit fast jeder Datenbank.
+
+Siehe [LoopBack](http://loopback.io) für ein Express-basiertes Framework, das um Modelle zentriert ist.
+
+## Wie kann ich Benutzer authentifizieren?
+
+Authentifizierung ist ein anderer Bereich, in dem sich Express nicht
+wagt. Sie können ein beliebiges Authentifizierungsschema verwenden.
+Für ein einfaches Benutzername/Passwort-Schema, siehe [dieses Beispiel](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Welche Template-Engines unterstützt Express?
+
+Express unterstützt jede Template-Engine, die mit der Signatur `(Pfad, locals, callback)` übereinstimmt.
+Um die Schnittstellen der Template-Engine und das Caching zu normalisieren, lesen Sie bitte
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+Projekt für Unterstützung. Nicht aufgelistete Template-Engines könnten die Express-Signatur trotzdem unterstützen.
+
+Weitere Informationen finden Sie unter [Template-Engines mit Express](/en/guide/using-template-engines).
+
+## Wie gehe ich mit 404 Antworten um?
+
+In Express sind 404 Antworten nicht das Ergebnis eines Fehlers, daher wird die Middleware von
+nicht erfasst. Dieses Verhalten ist
+, da eine 404-Antwort einfach das Fehlen zusätzlicher Arbeit anzeigt;
+in anderen Worten, Express hat alle Middleware-Funktionen und -Routen ausgeführt,
+und festgestellt, dass keiner von ihnen reagiert hat. Alles, was Sie
+tun müssen, ist eine Middleware-Funktion am unteren Ende des Stacks (unter allen anderen Funktionen)
+hinzuzufügen, um eine 404-Antwort zu handhaben:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Fügen Sie Routen dynamisch zur Laufzeit einer Instanz von `express.Router()`
+hinzu, so dass die Routen nicht durch eine Middleware-Funktion ersetzt werden.
+
+## Wie kann ich einen Fehler einrichten?
+
+Du definierst die Middleware wie andere Middleware,
+außer mit vier anstatt drei, spezifisch mit der Signatur `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Weitere Informationen finden Sie unter [Fehlerbehandlung](/en/guide/error-handling).
+
+## Wie kann ich plain HTML rendern?
+
+Du bist es nicht! Es gibt keine Notwendigkeit HTML mit der Funktion `res.render()` zu "render".
+Wenn du eine bestimmte Datei hast, nutze die Funktion `res.sendFile()`.
+Wenn du viele Assets aus einem Verzeichnis lieferst, verwende die `express.static()`
+Middleware-Funktion.
+
+## Welche Version von Node.js benötigt Express?
+
+- [Express 4.x](/en/4x/api) benötigt Node.js 0.10 oder höher.
+- [Express 5.x](/en/5x/api) benötigt Node.js 18 oder höher.
diff --git a/src/content/docs/de/4x/starter/generator.mdx b/src/content/docs/de/4x/starter/generator.mdx
new file mode 100644
index 0000000000..53c5930dbb
--- /dev/null
+++ b/src/content/docs/de/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express-Applikationsgenerator
+description: Lernen Sie, wie Sie mit dem Express-Anwendungsgenerator-Tool schnell ein Skelett für Ihre Express.js-Anwendungen erstellen, die Einrichtung optimieren und die Konfiguration optimieren.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Verwenden Sie das Applikationsgenerator-Tool, "express-generator", um schnell ein Anwendungsskelett zu erstellen.
+
+Du kannst den Anwendungsgenerator mit dem Befehl `npx` ausführen (verfügbar in Node.js 8.2.0).
+
+```bash
+$ npx Express-Generator
+```
+
+Für frühere Node-Versionen installieren Sie den Anwendungsgenerator als globales npm-Paket und starten es dann:
+
+```bash
+$ npm Installation -g Express-Generator
+$ express
+```
+
+Zeige die Befehlsoptionen mit der `-h` Option:
+
+```bash
+$ express -h
+
+  Verwendung: Express [options] [dir]
+
+  Optionen:
+
+    -h, --help Ausgabe-Informationen
+        --version Ausgabe der Versionsnummer
+    -e, --ejs add ejs engine support
+        --hbs add handlebars engine support
+        --pug add pug engine support
+    -H, --hogan add hogan. s Engine Unterstützung
+        --no-view generieren ohne View Engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  Fügen Sie Stylesheet <engine> Unterstützung (less |stylus|compass|sass) (standardmäßig auf plain css)
+        --git add . itignore
+    -f, --force auf nicht leeres Verzeichnis
+```
+
+Zum Beispiel erstellt das Folgende eine Express-App namens _myapp_. Die App wird in einem Ordner namens _myapp_ im aktuellen Arbeitsverzeichnis erstellt und die View Engine wird auf <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Mops</a> gesetzt:
+
+```bash
+$ express --view=pug myapp
+
+   erstellen : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   erstellen : myapp/routes/users. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   erstellen : myapp/views
+   erstellen : myapp/views/index. ug
+   erstellen : myapp/views/layout.pug
+   erstellen : myapp/views/error. ug
+   erstellen : myapp/bin
+   erstellen : myapp/bin/www
+```
+
+Installieren Sie dann Abhängigkeiten:
+
+```bash
+$ cd myapp
+$ npm Installation
+```
+
+Führen Sie auf MacOS oder Linux die App mit diesem Befehl aus:
+
+```bash
+$ DEBUG=myapp:* npm Start
+```
+
+Benutzen Sie auf Windows Befehlsaufforderung folgenden Befehl:
+
+```bash
+> DEBUG=myapp:* & npm Start setzen
+```
+
+Verwenden Sie unter Windows PowerShell, diesen Befehl:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm Start
+```
+
+Lade dann `http://localhost:3000/` in deinem Browser, um auf die App zuzugreifen.
+
+Die generierte App hat folgende Verzeichnisstruktur:
+
+```bash
+.
+<unk> 本<unk> app.js
+<unk> 本<unk> bin
+<unk> <unk> <unk> <unk> <unk> www
+<unk> 本<unk> Paket. son
+<unk> 文<unk> public
+<unk> <unk> <unk> <unk> <unk> Bilder
+<unk> <unk> <unk> <unk> <unk> <unk> <unk> javascripts
+<unk> <unk> <unk> Stylesheets
+<unk> <unk> style. ss
+<unk> 本<unk> routet
+<unk> <unk> <unk> <unk> index.js
+<unk> <unk> <unk> <unk> Benutzer. s
+<unk> 本<unk> Ansichten
+    <unk> <unk> <unk> Fehler. ug
+    <unk> 本<unk> index.pug
+    <unk> <unk> layout.pug
+
+7 Verzeichnisse, 9 Dateien
+```
+
+<Alert type="info">
+
+Die vom Generator erstellte App-Struktur ist nur eine von vielen Möglichkeiten, Express-Apps zu strukturieren.
+Fühlen Sie sich frei, diese Struktur zu verwenden oder sie so zu modifizieren, dass sie Ihren Bedürfnissen am besten entspricht.
+
+</Alert>
diff --git a/src/content/docs/de/4x/starter/hello-world.mdx b/src/content/docs/de/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..14fbd320f5
--- /dev/null
+++ b/src/content/docs/de/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hallo Weltbeispiel
+description: Beginnen Sie mit Express.js, indem Sie eine einfache 'Hallo World'-Anwendung erstellen, die die Grundeinstellung und die Servererstellung für Anfänger demonstriert.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Eingebettet unten ist im Wesentlichen die einfachste Express-App, die Sie erstellen können. Es ist eine einzelne Datei-App
+&mdash; _not_ was Sie bekommen würden, wenn Sie den [Express-Generator](/en/starter/generator), welche
+das Gerüst für eine vollständige Anwendung mit zahlreichen JavaScript-Dateien, Jade-Vorlagen und
+Unterverzeichnissen für verschiedene Zwecke erstellt.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hallo World!');
+});
+
+app.listen(port, () => {
+  console.log(`Beispiel-App, die auf Port ${port}`);
+});
+```
+
+Diese App startet einen Server und lauscht auf Port 3000 für Verbindungen. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. Für jeden anderen Pfad wird es mit einem **404 Nicht gefunden** antworten.
+
+## Lokal laufen
+
+Erstelle zuerst ein Verzeichnis namens `myapp`, ändere es und führe `npm init` aus. Installieren Sie dann `Expres` als Abhängigkeit, wie in der [Installationsanleitung](/en/starter/installing).
+
+Erstelle im `myapp` Verzeichnis eine Datei namens `app.js` und kopiere den Code aus dem obigen Beispiel.
+
+<Alert type="warnung">
+
+Die `req` (Anfrage) und `res` (Antwort) sind genau die gleichen Objekte, die der Knoten anbietet, also kann
+`req aufrufen. ipe()`, `req.on('data', callback)` und alles, was Sie sonst ohne Express
+tun würden.
+
+</Alert>
+
+Führen Sie die App mit dem folgenden Befehl aus:
+
+```bash
+$ node app.js
+```
+
+Lade dann `http://localhost:3000/` in einem Browser, um die Ausgabe zu sehen.
diff --git a/src/content/docs/de/4x/starter/installing.mdx b/src/content/docs/de/4x/starter/installing.mdx
new file mode 100644
index 0000000000..bee85fe973
--- /dev/null
+++ b/src/content/docs/de/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installiere
+description: Erfahren Sie, wie Sie Express.js in Ihrer Node.js-Umgebung installieren, einschließlich der Einrichtung Ihres Projektverzeichnisses und der Verwaltung von Abhängigkeiten mit npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Bevor Sie beginnen, stellen Sie sicher, dass Sie [Node.js](https://nodejs.org/) 0.10 oder höher installiert haben. Erstellen Sie dann ein Verzeichnis für Ihre Anwendung und navigieren Sie hinein.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Benutze den Befehl `npm init` um eine `package.json` Datei für deine Anwendung zu erstellen.
+Für weitere Informationen darüber, wie `package.json` funktioniert, siehe [Spezifikationen für npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Dieser Befehl fragt Sie nach einer Reihe von Dingen wie dem Namen und der Version Ihrer Anwendung.
+Im Moment können Sie einfach RETURN drücken, um die Standardwerte für die meisten von ihnen zu akzeptieren, mit der folgenden Ausnahme:
+
+```
+eintragspunkt: (index.js)
+```
+
+Geben Sie `app.js` ein, oder was auch immer der Name der Hauptdatei sein soll. Wenn Sie `index.js` wollen, drücken Sie RETURN um den empfohlenen Dateinamen zu akzeptieren.
+
+Installieren Sie jetzt Express im `myapp` Verzeichnis und speichern Sie es in der Abhängigkeitsliste. Zum Beispiel:
+
+```bash
+npm Express installieren
+```
+
+Um Express vorübergehend zu installieren und nicht zur Abhängigkeitsliste hinzufügen:
+
+```bash
+npm express installieren --no-save
+```
+
+<Alert type="info">
+
+Standardmäßig fügt `npm install` mit Version npm 5.0+ das Modul der `dependencies` Liste im
+`package hinzu. son` file; mit früheren Versionen von npm musst du die `--save` Option
+explizit angeben. Danach wird das Ausführen von `npm install` im App-Verzeichnis automatisch
+Module in der Abhängigkeitsliste installiert.
+
+</Alert>
diff --git a/src/content/docs/de/4x/starter/static-files.mdx b/src/content/docs/de/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..f1c8dc894a
--- /dev/null
+++ b/src/content/docs/de/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serviere statische Dateien in Express
+description: Verstehen Sie, wie Sie statische Dateien wie Bilder, CSS und JavaScript in Express.js Anwendungen mit der integrierten 'static' Middleware bedienen können.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um statische Dateien wie Bilder, CSS-Dateien und JavaScript-Dateien bereitzustellen, verwenden Sie die in Express integrierte Middleware-Funktion `express.static`.
+
+Die Funktionssignatur ist:
+
+```js
+express.static(root, [options]);
+```
+
+Das `root` Argument gibt das Wurzelverzeichnis an, von dem aus statische Assets ausgeliefert werden sollen.
+Für weitere Informationen zum Argument `options` siehe [express.static](/en/5x/api#express.static).
+
+Verwenden Sie zum Beispiel den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis mit dem Namen `public` auszugeben:
+
+```js
+app.use(express.static('public'));
+```
+
+Jetzt kannst du die Dateien im `public` Verzeichnis laden:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express sucht die Dateien relativ zum statischen Verzeichnis, so dass der Name des statischen Verzeichnisses
+nicht Teil der URL ist.
+
+</Alert>
+
+Um mehrere statische Asset-Verzeichnisse zu verwenden, rufen Sie die `express.static` Middleware-Funktion mehrmals auf:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express sucht die Dateien in der Reihenfolge, in der du die statischen Verzeichnisse mit der Middleware-Funktion `express.static` gesetzt hast.
+
+<Alert type="info">
+
+Für beste Ergebnisse Benutze einen Reverse
+Proxy Cache um die Leistung von
+zu verbessern und statische Assets zu bedienen.
+
+</Alert>
+
+Um einen virtuellen Pfad-Präfix zu erstellen (wo der Pfad existiert eigentlich nicht im Dateisystem) für Dateien, die durch die `express. tatic` Funktion, [einen Mount-Pfad angeben](/en/5x/api#app.use) für das statische Verzeichnis angeben, wie unten angezeigt:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Nun kannst du die Dateien, die sich im `public` Verzeichnis befinden, aus dem `/static` Pfadpräfix laden.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Der Pfad, den du der `express.static` Funktion zur Verfügung stellst, ist jedoch relativ zu dem Verzeichnis, von dem aus du deinen `node` Prozess startest. Wenn Sie die Express-App aus einem anderen Verzeichnis ausführen, ist es sicherer, den absoluten Pfad des Verzeichnisses zu verwenden, das Sie verwenden möchten:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public'));
+```
+
+Weitere Informationen über die `serve-static` Funktion und ihre Optionen finden Sie unter [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/de/5x/advanced/developing-template-engines.md b/src/content/docs/de/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..243960da6a
--- /dev/null
+++ b/src/content/docs/de/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Template-Engines für Express entwickeln
+description: Erfahren Sie, wie Sie mithilfe von app.engine() benutzerdefinierte Template-Engines für Express.js entwickeln können, mit Beispielen zur Erstellung und Integration Ihrer eigenen Template-Rendering-Logik.
+---
+
+Benutze die `app.engine(ext, callback)` Methode, um deine eigene Template-Engine zu erstellen. `ext` bezieht sich auf die Dateierweiterung, und `callback` ist die Template-Engine-Funktion, , die die folgenden Elemente als Parameter akzeptiert: den Speicherort der Datei, das Optionsobjekt und die Callback-Funktion.
+
+Der folgende Code ist ein Beispiel für die Implementierung einer sehr einfachen Template-Engine zum Rendern von `.ntl` Dateien.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Deine App wird nun in der Lage sein, `.ntl`-Dateien zu rendern. Erstelle eine Datei namens `index.ntl` im `views` Verzeichnis mit folgendem Inhalt.
+
+```pug
+#title#
+#message#
+```
+
+Erstellen Sie dann die folgende Route in Ihrer App.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Wenn du eine Anfrage an die Startseite stellt, wird `index.ntl` als HTML dargestellt.
diff --git a/src/content/docs/de/5x/guide/behind-proxies.mdx b/src/content/docs/de/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..42b2f725fb
--- /dev/null
+++ b/src/content/docs/de/5x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Express hinter Proxies
+description: Lernen Sie, wie Sie Express.js Anwendungen so konfigurieren, dass sie hinter Reverse Proxies korrekt arbeiten, einschließlich der Trust-Proxy-Einstellung für Client-IP-Adressen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Wenn Sie eine Express-App hinter einem Reverse Proxy ausführen, können einige der Express-APIs andere Werte als erwartet zurückgeben. Um dies anzupassen die Einstellung `trust proxy` kann verwendet werden, um Informationen auszublenden, die vom Reverse Proxy in den Express API bereitgestellt werden. Das häufigste Problem sind Express-APIs, die die IP-Adresse des Clients offenlegen, statt dessen eine interne IP-Adresse des Reverse Proxy anzeigen.
+
+<Alert type="info">
+
+Bei der Konfiguration der `trust proxy` Einstellung ist es wichtig, das genaue Setup des
+Reverse Proxy zu verstehen. Da diese Einstellung den in der Anfrage angegebenen Werten vertrauen wird Es ist wichtig, dass
+die Kombination der Einstellung in Express mit der Funktionsweise des Reverse Proxy übereinstimmt.
+
+</Alert>
+
+Die Anwendungseinstellung `trust proxy` kann auf einen der in der folgenden Tabelle aufgelisteten Werte gesetzt werden.
+
+<table class="doktierbar" border="1" markdown="1">
+  <thead><tr><th>Typ</th><th>Wert</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Wenn `true`, wird die IP-Adresse des Clients als linker Eintrag im `X-Forwarded-For` Header verstanden.
+
+Falls „falsch“ die App als direkt gegenüber dem Client verstanden wird und die IP-Adresse des Clients von „req.socket.remoteAddress“ abgeleitet wird. Dies ist die Standardeinstellung.
+
+<Alert type="warnung">
+Wenn Sie auf `true` setzen, ist es wichtig sicherzustellen, dass der letzte Reverse Proxy alle folgenden HTTP-Header löscht/überschreibt: `X-Forwarded-For`, `X-Forwarded-Host` und `X-Forwarded-Proto`, andernfalls ist es möglich, dass der Client irgendeinen Wert angibt.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP-Adressen</td>
+<td markdown="1">
+Eine IP-Adresse, ein Subnetz oder ein Array von IP-Adressen und Subnetzen, die darauf vertrauen, dass es sich um einen Reverse Proxy handelt. Die folgende Liste zeigt die vorkonfigurierten Subnetznamen an:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Sie können IP-Adressen auf jede der folgenden Arten festlegen:
+
+```js
+app.set('trust proxy', 'loopback'); // ein einzelnes Subnetz
+app.set('trust proxy', 'loopback, 123.123.123.123''); // ein Subnetz und eine Adresse
+angeben. et('trust proxy', 'loopback, linklocal, uniquelocal'); // mehrere Subnetze als CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // mehrere Subnetze als Array angeben
+```
+
+Wenn angegeben, werden die IP-Adressen oder Subnetze vom Prozess der Adressermittlung ausgeschlossen und die dem Anwendungsserver nächstgelegene nicht vertrauenswürdige IP-Adresse wird als IP-Adresse des Clients ermittelt. Dies funktioniert indem überprüft wird, ob `req.socket.remoteAddress` vertrauenswürdig ist. Wenn ja, dann wird jede Adresse in `X-Forwarded-For` von rechts nach links bis zur ersten Adresse überprüft, die nicht vertrauenswürdig ist.
+
+</td>
+    </tr>
+    <tr>
+      <td>Nummer</td>
+<td markdown="1">
+Benutzen Sie die Adresse, die höchstens `n` von der Express-Anwendung entfernt ist. `req.socket.remoteAddress` ist der erste Hop, und der Rest wird im `X-Forwarded-For` Header von rechts nach links gesucht. Ein Wert von `0` bedeutet, dass die erste nicht vertrauenswürdige Adresse `req.socket.remoteAddress` ist, d.h. es gibt keinen Reverse-Proxy.
+
+<Alert type="warnung">
+Bei der Verwendung dieser Einstellung ist es wichtig sicherzustellen, dass es keine Multiple gibt, verschiedene Pfade zur Express-Anwendung, so dass der Client kleiner sein kann als die konfigurierte Anzahl von Hops, die entfernt sind andernfalls kann es möglich sein, dass der Kunde irgendeinen Wert angibt.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Funktion</td>
+<td markdown="1">
+Benutzerdefinierte Vertrauens-Implementierung.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    return true; // vertrauenswürdige IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Das Aktivieren von `trust proxy` hat folgende Auswirkungen:
+
+<ul>
+  <li markdown="1">
+    Der Wert von [req.hostname](/en/api#req.hostname) wird vom Wert abgeleitet, der im
+    `X-Forwarded-Host` Header gesetzt wurde , die vom Client oder vom Proxy gesetzt werden kann.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` kann vom Reverse Proxy gesetzt werden, um der App mitzuteilen, ob es `https`
+    oder `http` oder sogar ein ungültiger Name ist. Dieser Wert wird von [req.protocol]reflektiert
+    (/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Die Werte [req.ip](/en/api#req.ip) und [req.ips](/en/api#req.ips) werden auf der Basis der
+    Socket-Adresse und des `X-Forwarded-For` Headers gefüllt beginnend an der ersten nicht
+    vertrauenswürdigen Adresse.
+  </li>
+</ul>
+
+Die `trust proxy` Einstellung ist mit dem [proxy-addr](https://www.npmjs.com/package/proxy-addr) Paket implementiert. Weitere Informationen finden Sie in der Dokumentation.
diff --git a/src/content/docs/de/5x/guide/debugging.mdx b/src/content/docs/de/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..44802397e8
--- /dev/null
+++ b/src/content/docs/de/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debuggen Express
+description: Erfahren Sie, wie Sie Debugging-Logs in Express.js-Anwendungen aktivieren und nutzen können, indem Sie die DEBUG-Umgebungsvariable für verbesserte Fehlerbehebung setzen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um alle internen Logs zu sehen, die in Express verwendet werden, setzen Sie die Umgebungsvariable `DEBUG` auf
+`express:*` beim Starten Ihrer App.
+
+```bash
+$ DEBUG=Express:* node index.js
+```
+
+Verwenden Sie unter Windows den entsprechenden Befehl.
+
+```bash
+> $env:DEBUG = "Express:*"; node index.js
+```
+
+Das Ausführen dieses Befehls auf der vom [Express-Generator] generierten Standard-App (/en/starter/generator) gibt folgende Ausgabe aus:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Wenn eine Anfrage an die App gestellt wird, sehen Sie die im Express-Code angegebenen Protokolle:
+
+```bash
+  express :router dispatching GET / +4h
+  express :router query : / +2ms
+  express :router expresInit : / +0ms
+  express:router favicon : / +0ms
+  express :router logger : / +1ms
+  express :router jsonParser : / +0ms
+  express:router urlencodedParser : / +1ms
+  express :router cookieParser : / +0ms
+  express:router stylus : / +0ms
+  express :router serveStatic : / +2ms
+  express :router router router : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index. ug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Um die Protokolle nur von der Router-Implementierung zu sehen, setzen Sie den Wert `DEBUG` auf `express:router`. Um Protokolle nur von der Anwendungsimplementierung zu sehen, setzten Sie den Wert von `DEBUG` auf `express:application`, und so weiter.
+
+## Anwendungen generiert von `Express`
+
+Eine Anwendung, die durch den Befehl `express generiert` erzeugt wird, benutzt das Modul `debug` und sein Debug-Namensraum wird auf den Namen der Anwendung übertragen.
+
+Wenn Sie zum Beispiel die App mit `$ express Beispiel-App` erstellt haben, können Sie die Debug-Anweisungen mit folgendem Befehl aktivieren:
+
+```bash
+$ DEBUG=Beispiel-app:* Knoten ./bin/www
+```
+
+Sie können mehr als einen Debug-Namensraum angeben, indem Sie eine kommaseparierte Namensliste zuweisen:
+
+```bash
+$ DEBUG=http,mail,Express:* node index.js
+```
+
+## Erweiterte Optionen
+
+Wenn Sie über Node.js laufen, können Sie ein paar Umgebungsvariablen festlegen, die das Verhalten der Debug-Protokollierung ändern:
+
+| Name                | Zweck                                                                       |
+| ------------------- | --------------------------------------------------------------------------- |
+| `DEBUG`             | Aktiviere/deaktiviert bestimmte Debugging-Namensräume.                      |
+| DEBUG_COLORS        | Gibt an, ob Farben in der Debug-Ausgabe verwendet werden sollen oder nicht. |
+| DEBUG_DEPTH\`       | Objektüberprüfungstiefe.                                                    |
+| `DEBUG_FD`          | Datei-Deskriptor, in den die Debug-Ausgabe geschrieben wird.                |
+| `DEBUG_SHOW_HIDDEN` | Zeigt versteckte Eigenschaften auf untersuchten Objekten.                   |
+
+<Alert type="info">
+
+Die Umgebungsvariablen, die mit `DEBUG_` beginnen, werden am Ende in ein Optionsobjekt
+konvertiert, das mit `%o`/`%O` Formate verwendet wird. Siehe die Dokumentation von Node.js für
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) für die vollständige
+Liste.
+
+</Alert>
diff --git a/src/content/docs/de/5x/guide/error-handling.mdx b/src/content/docs/de/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..9db119db26
--- /dev/null
+++ b/src/content/docs/de/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Fehler beim Umgang
+description: Verstehen Sie, wie Express.js Fehler im synchronen und asynchronen Code behandelt, und lernen Sie, benutzerdefinierte Fehlerbehandlung Middleware für Ihre Anwendungen zu implementieren.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ bezieht sich darauf, wie Express Fehler fängt und verarbeitet, die
+sowohl synchron als auch asynchron auftritt. Express kommt mit einem Standardfehler
+\-Handler, damit Sie nicht Ihren eigenen schreiben müssen, um loszulegen.
+
+## Fehler beim Fangen
+
+Es ist wichtig sicherzustellen, dass Express alle Fehler, die auftreten, während
+Routen-Handler und Middleware ausführt.
+
+Fehler, die im synchronen Code innerhalb von Routenhandlern und Middleware
+auftreten, erfordern keine zusätzliche Arbeit. If synchronous code throws an error, then Express will
+catch and process it. Zum Beispiel:
+
+```js
+app.get('/', (req, res) => {
+  werfen neue Fehler ('BROKEN'); // Express fängt dies auf eigene Faust.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Fehler an Express übergeben.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+Zum Beispiel:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = wait getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Wenn `getUserById` einen Fehler oder eine Ablehnung, wird `next` entweder mit
+dem Wurffehler oder dem abgelehnten Wert aufgerufen. Wenn kein abgelehnter Wert angegeben wird, wird `next`
+mit einem Standard-Fehlerobjekt aufgerufen, das vom Express-Router bereitgestellt wird.
+
+Wenn du etwas an die `next()` Funktion übergibt (außer den String `'route'`),
+Express betrachtet die aktuelle Anfrage als Fehler und überspringt alle
+verbleibenden Funktionen zur Fehlerbehandlung und Middleware.
+
+Wenn der Rückruf in einer Sequenz keine Daten enthält, nur Fehler, kannst du den Code
+wie folgt vereinfachen:
+
+```js
+app.get('/', [
+  Funktion (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Im obigen Beispiel wird `next` als Callback für `fs.writeFile` bereitgestellt,
+, das mit oder ohne Fehler aufgerufen wird. Wenn kein Fehler vorliegt, wird der zweite
+\-Handler ausgeführt, sonst fängt und verarbeitet Express den Fehler.
+
+Sie müssen Fehler, die im asynchronen Code auftreten, der von Routenhandlern oder
+Middleware aufgerufen wird, auffangen und an Express zur Verarbeitung weiterleiten. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+Das obige Beispiel benutzt einen "try...catch"-Baustein, um Fehler im
+asynchronen Code zu fangen und sie an den Express zu übergeben. Wenn der Block `try...catch`
+weggelassen wurde, würde Express den Fehler nicht auffinden, da er nicht Teil des synchronen
+Handlercodes ist.
+
+Verwende Versprechungen, um den Overhead des `try...catch`-Bausteins zu vermeiden oder wenn du Funktionen
+benutzt, die Versprechen zurückgeben. Zum Beispiel:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    . hen(() => {
+      werfen neue Fehler ('BROKEN');
+    })
+    . atch(next); // Fehler werden an Express übergeben.
+});
+```
+
+Da Versprechungen automatisch sowohl synchrone Fehler als auch abgelehnte Versprechungen fangen,
+du kannst einfach `next` angeben, da der letzte Catch Handler und Express Fehler fängt an
+weil der Catch-Handler den Fehler als erstes Argument angibt.
+
+Sie können auch eine Kette von Handlern verwenden, um sich auf synchrone Fehler
+zu stützen, indem Sie den asynchronen Code auf etwas Triviales reduzieren. Zum Beispiel:
+
+```js
+app.get('/', [
+  Funktion (req, res, next) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = Daten;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+Das obige Beispiel hat ein paar triviale Anweisungen aus dem Aufruf `readFile`
+. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Dann versucht das obige Beispiel die Daten zu verarbeiten. Wenn dies fehlschlägt, fängt der Synchron-Fehlerhandler
+ihn ab. Hätten Sie diese Verarbeitung innerhalb von
+mit dem `readFile` Callback durchgeführt, dann könnte sich die Anwendung beenden und die Express-Fehler
+Handler würden nicht laufen.
+
+Welche Methode Sie auch immer verwenden, wenn Sie wollen, dass Express-Fehlerbehandler aufgerufen werden und die
+\-Anwendung überleben soll, Sie müssen sicherstellen, dass Express den Fehler empfängt.
+
+## Der Standard-Fehlerhandler
+
+Express kommt mit einem integrierten Fehlerbehandler, der sich um Fehler kümmert, die in der App auftreten könnten. Diese Standard-Middleware-Funktion wird am Ende des Middleware-Funktionstacks hinzugefügt.
+
+Wenn du einen Fehler an `next()` übergibt und ihn nicht in einem benutzerdefinierten
+Handler behandelst, es wird vom eingebauten Fehlerhandler behandelt; wird der Fehler
+mit der Stack-Spur an den Client geschrieben. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Setze die Umgebungsvariable `NODE_ENV` auf `production`, um die App im Produktionsmodus auszuführen.
+
+</Alert>
+
+Wenn ein Fehler geschrieben wird, werden folgende Informationen zur Antwort
+hinzugefügt:
+
+- Der `res.statusCode` wurde von `err.status` (oder `err.statusCode`) gesetzt. Wenn
+  sich dieser Wert außerhalb des 4xx oder 5xx Bereichs befindet, wird er auf 500 gesetzt.
+- Die `res.statusMessage` wurde gemäß dem Statuscode gesetzt.
+- Der Körper wird der HTML-Code der Statuscode-Nachricht sein, wenn in der Produktion
+  \-Umgebung, andernfalls 'err.stack' ist.
+- Alle in einem `err.headers` Objekt angegebenen Header.
+
+Wenn du `next()` mit einem Fehler aufruft, nachdem du die
+Antwort geschrieben hast (z. B. wenn beim Streamen der
+Antwort auf den Client ein Fehler aufgetreten ist), der Express-Standardfehlerhandler schließt die
+Verbindung und schlägt die Anfrage fehl.
+
+Wenn Sie also eine benutzerdefinierte Fehlerbehandlung hinzufügen, müssen Sie den Standard-Express-Fehlerbehandler an
+delegieren wenn die Kopfzeilen
+bereits an den Client gesendet wurden:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Beachte, dass der Standard-Fehlerhandler ausgelöst werden kann, wenn du `next()` mit einem Fehler
+in deinem Code mehrmals aufrufst, auch wenn benutzerdefinierte Fehler beim Umgang mit Middleware vorhanden sind.
+
+Andere Fehler beim Umgang mit Middleware finden Sie unter [Express Middleware](/en/resources/middleware).
+
+## Schreibfehler
+
+Definieren Sie die Middleware-Funktionen wie andere Middleware-Funktionen
+außer Funktionen zur Fehlerbehandlung haben vier Argumente anstelle von drei:
+`(err, req, res, next)`. Zum Beispiel:
+
+```js
+app.use(((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Etwas kaputt!');
+});
+```
+
+Du definierst die Middleware zuletzt nach anderen `app.use()` und Routet Anrufe; zum Beispiel:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // Logik
+});
+```
+
+Antworten innerhalb einer Middleware-Funktion können in jedem Format sein, wie z.B. in einer HTML-Fehlerseite, einer einfachen Nachricht oder einem JSON-String.
+
+Für organisatorische (und höherstufige Framework) Zwecke können Sie
+verschiedene Middleware-Funktionen definieren, so wie Sie es mit den regulären Middleware-Funktionen
+würden. Zum Beispiel, um einen Fehlerhandler
+für Anfragen mit `XHR` und denen ohne folgende zu definieren:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In diesem Beispiel könnten die generischen `logErrors` Anfrage und
+Fehlerinformationen in `stderr` schreiben, zum Beispiel:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Auch in diesem Beispiel wird `clientErrorHandler` wie folgt definiert; in diesem Fall wird der Fehler explizit an den nächsten weitergegeben.
+
+Beachten Sie, dass, wenn _not_ in einer Fehlerbehandlungsfunktion "Weiter" aufruft, Sie dafür verantwortlich sind, die Antwort zu schreiben (und zu beenden). Andernfalls werden diese Anträge "hängen" und sind nicht für die Müllsammlung berechtigt.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementierung der "catch-all" `errorHandler` Funktion wie folgt (zum Beispiel):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Wenn du einen Route-Handler mit mehreren Callback-Funktionen hast, kannst du den Parameter `route` verwenden, um zum nächsten Route-Handler zu springen. Zum Beispiel:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // weitere Bearbeitung dieser Anfrage
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+In diesem Beispiel wird der `getPaidContent` Handler übersprungen, aber alle verbleibenden Handler in `app` für `/a_route_behind_paywall` würden weiterhin ausgeführt werden.
+
+<Alert type="info">
+
+Aufrufe in `next()` und `next(err)` zeigen an, dass der aktuelle Handler abgeschlossen ist und in welchem Zustand ist.
+`next(err)` überspringt alle verbleibenden Handler in der Kette mit Ausnahme derjenigen, die bis zu
+eingerichtet sind, um Fehler wie oben beschrieben zu handhaben.
+
+</Alert>
diff --git a/src/content/docs/de/5x/guide/overriding-express-api.md b/src/content/docs/de/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..e7f6044eb7
--- /dev/null
+++ b/src/content/docs/de/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Überschreiben der Express-API
+description: Erfahren Sie, wie Sie die Express.js API anpassen und erweitern können, indem Sie Methoden und Eigenschaften der Request- und Response-Objekte mittels Prototypen überschreiben.
+---
+
+Die Express API besteht aus verschiedenen Methoden und Eigenschaften auf den Anfrage- und Antwort-Objekten. Diese werden vom Prototyp geerbt. Es gibt zwei Erweiterungspunkte für die Express API:
+
+1. Die globalen Prototypen unter `express.request` und `express.response`.
+2. App-spezifische Prototypen bei `app.request` und `app.response`.
+
+Das Ändern der globalen Prototypen wirkt sich auf alle geladenen Express-Apps im selben Prozess aus. Wenn gewünscht, können Änderungen app-spezifisch gemacht werden, indem nur app-spezifische Prototypen nach dem Erstellen einer neuen App geändert werden.
+
+## Methoden
+
+Sie können die Signatur und das Verhalten bestehender Methoden mit eigenen überschreiben, indem Sie eine benutzerdefinierte Funktion zuweisen.
+
+Folgendes ist ein Beispiel für das Überschreiben des Verhaltens von [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+Die obige Implementierung ändert die ursprüngliche Signatur von `res.sendStatus`. Es akzeptiert nun einen Statuscode, Kodierungstyp und die Nachricht, die an den Client gesendet werden soll.
+
+Die überschriebene Methode kann nun auf diese Weise verwendet werden:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Eigenschaften
+
+Eigenschaften in der Express-API sind entweder:
+
+1. Zugewiesene Eigenschaften (z.B. `req.baseUrl`, `req.originalUrl`)
+2. Definiert als Getters (z. B.: `req.secure`, `req.ip`)
+
+Da Eigenschaften in Kategorie 1 dynamisch auf den `request` und `response` Objekten im Kontext des aktuellen Request-Antwort-Zyklus zugewiesen werden ihr Verhalten kann nicht überschrieben werden.
+
+Eigenschaften der Kategorie 2 können mit der Express API Extensions API überschrieben werden.
+
+Der folgende Code schreibt neu wie der Wert von `req.ip` abgeleitet wird. Jetzt gibt es einfach den Wert des `Client-IP` Request-Headers zurück.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototyp
+
+Um die Express API zur Verfügung zu stellen, werden die Anfrage/Antwort-Objekte an Express weitergegeben (via `app(req, res)`, zum Beispiel, müssen von der gleichen Prototypenkette zu erben. Standardmäßig ist dies `http.IncomingRequest.prototype` für die Anfrage und `http.ServerResponse.prototype` für die Antwort.
+
+Wenn nötig, wird empfohlen, dass dies nur auf der Anwendungsebene und nicht auf globaler Ebene geschieht. Achten Sie auch darauf, dass der verwendete Prototyp die Funktionalität so nah wie möglich an die Standard-Prototypen anpasst.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/de/5x/guide/routing.mdx b/src/content/docs/de/5x/guide/routing.mdx
new file mode 100644
index 0000000000..58254d8832
--- /dev/null
+++ b/src/content/docs/de/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Lernen Sie, wie Sie Routen in Express.js Anwendungen definieren und nutzen können, einschließlich Routenmethoden, Routenpfaden, Parameter und Router für modulare Route.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ bezieht sich darauf, wie die Endpunkte einer Anwendung (URIs) auf Kundenanfragen reagieren.
+Für eine Einführung in das Routing siehe [Basic routing](/en/starter/basic-routing).
+
+Du definierst Routing, indem du Methoden des Express `app` Objekts verwendest, die den HTTP-Methoden entsprechen;
+zum Beispiel, `app. et()` um GET-Anfragen und `app.post` zu behandeln, um POST-Anfragen zu bearbeiten. Für eine vollständige Liste
+siehe [app.METHOD](/en/5x/api#app.METHOD). Du kannst auch [app.all()](/en/5x/api#app.all) verwenden, um alle HTTP-Methoden und [app. se()](/en/5x/api#app.use) bis
+Middleware als Callback-Funktion angeben (siehe [Middleware](/en/guide/using-middleware) für Details).
+
+Diese Routing-Methoden geben eine Callback-Funktion (manchmal auch "handler functions") an, die aufgerufen wird, wenn die Anwendung eine Anfrage an die angegebene Route (Endpunkt) und die HTTP-Methode erhält. Mit anderen Worten, die Anwendung "lauscht" für Anforderungen, die mit der angegebenen Route(s) und Methode(n) übereinstimmen und wenn es ein Spiel erkennt, ruft es die angegebene Callback-Funktion auf.
+
+In der Tat können die Routing-Methoden mehr als eine Callback-Funktion als Argumente haben.
+Mit mehreren Callback-Funktionen, es ist wichtig, `next` als Argument für die Callback-Funktion zur Verfügung zu stellen und dann `next()` im Körper der Funktion aufzurufen, um die Steuerung
+an den nächsten Callback zu übergeben.
+
+Der folgende Code ist ein Beispiel für eine sehr einfache Route.
+
+```js
+const express = require('express ');
+const app = express = );
+
+// Mit "Hallo world" antworten, wenn eine GET-Anfrage an die Homepage
+App gestellt wird. et('/', (req, res) => {
+  res.send('Hallo Welt');
+});
+```
+
+## Routenmethoden
+
+Eine Route-Methode wird von einer der HTTP-Methoden abgeleitet und an eine Instanz der Klasse \`express angehängt.
+
+Der folgende Code ist ein Beispiel für Routen, die für die `GET` und die `POST` Methoden im Root der App definiert sind.
+
+```js
+// GET Methode Route
+app.get('/', (req, res) => {
+  res.end('GET request to the homepage');
+});
+
+// POST method route
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express unterstützt Methoden, die allen HTTP-Anfragemethoden entsprechen: `get`, `post` und so weiter.
+Für eine vollständige Liste siehe [app.METHOD](/en/5x/api#app.METHOD).
+
+Es gibt eine spezielle Routing-Methode, `app.all()`, die benutzt wird, um Middleware-Funktionen an einem Pfad für _all_ HTTP-Requestmethoden zu laden. Zum Beispiel wird der folgende Handler für Anfragen an die Route `"/secret"` ausgeführt, ob `GET` verwendet wird, `POST`, `PUT`, `DELETE`, oder jede andere HTTP-Anfragemethode, die im [http module]unterstützt wird (https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Zugriff auf den geheimen Abschnitt ...');
+  next(); // Kontrolle an den nächsten Handler
+});
+```
+
+## Routenpfade
+
+Routenpfade in Kombination mit einer Anfragemethode definieren die Endpunkte, an denen Anfragen gestellt werden können. Routenpfade können Zeichenketten, Zeichenkettenmuster oder reguläre Ausdrücke sein.
+
+<Alert type="warnung">
+
+Im Ausdruck 5, die Zeichen `? , `+`, `\*`, `[]`und`()\` werden anders behandelt als in Version
+4, bitte lesen Sie die [Migrationsanleitung](/en/guide/migrating-5#path-syntax) für weitere Informationen.
+
+</Alert>
+
+<Alert type="warnung">
+
+Im Ausdruck 4 müssen reguläre Ausdrücke wie `$` mit einem `\` maskiert werden.
+
+</Alert>
+
+<Alert type="info">
+
+Express verwendet [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) um die Route
+Pfade zu treffen; lesen Sie die Dokumentation zu regexp für alle Möglichkeiten bei der Definition von Routenpfaden.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) ist ein praktisches Werkzeug für
+grundlegende Express-Routen zu testen, obwohl es kein Muster-Matching unterstützt.
+
+</Alert>
+
+<Alert type="warning">Abfragezeichenketten sind nicht Teil des Routenweges.</Alert>
+
+### Routenpfade basierend auf Zeichenketten
+
+Dieser Routenpfad wird den Anfragen an die Root-Route `/` entsprechen.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Dieser Routenpfad wird den Anfragen auf `/about` entsprechen.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Dieser Routenpfad entspricht den Anfragen zu `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Routenpfade basierend auf Stringmustern
+
+<Alert type="warnung">
+
+Die Zeichenkettenmuster in Express 5 funktionieren nicht mehr. Weitere Informationen finden Sie in der Migration
+Anleitung .
+
+</Alert>
+
+Dieser Routenpfad stimmt mit `acd` und `abcd` überein.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `abcd`, `abbcd`, `abbbcd` usw. überein.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd` usw. überein.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Dieser Routenpfad stimmt mit `/abe` und `/abcde` überein.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Routenpfade basierend auf regulären Ausdrücken
+
+Dieser Routenpfad stimmt mit einem "a" darin überein.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Dieser Routenpfad stimmt mit 'butterfly' und 'Drachenfly' überein, aber nicht mit 'butterflyman', 'Drachenflyman' und so weiter.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Routenparameter
+
+Routenparameter sind URL-Segmente, die zur Erfassung der an ihrer Position in der URL angegebenen Werte verwendet werden. Die erfassten Werte werden im Objekt `req.params` gefüllt, wobei der Name des im Pfad angegebenen Routenparameter als ihre jeweiligen Schlüssel angegeben ist.
+
+```
+Routenpfad: /users/:userId/books/:bookId
+Anfrage-URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Um Routen mit Routenparametern zu definieren, geben Sie einfach die Routenparameter im Pfad der Route, wie unten gezeigt, an.
+
+```js
+app.get('/users/:userId/bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="warnung">
+
+Der Name der Routenparameter muss aus "Wortzeichen" ([A-Za-z0-9_] ) bestehen.
+
+</Alert>
+
+Da die Bindestriche (`-`) und der Punkt (`.`) wörtlich interpretiert werden, können sie zusammen mit Routenparametern für nützliche Zwecke verwendet werden.
+
+```
+Routenpfad: /flights/:from-:to
+Abfrage URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Routenpfad: /plantae/:genus.:species
+Anfrage URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="warnung">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Um mehr Kontrolle über den exakten String zu haben, der mit einem Route-Parameter übereinstimmen kann, können Sie einen regulären Ausdruck in Klammern (`()`) anhängen:
+
+```
+Routenpfad: /user/:userId(\d+)
+Anfrage-URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warnung">
+
+Weil der reguläre Ausdruck in der Regel Teil einer literalen Zeichenkette ist, Stellen Sie sicher, dass Sie `\`
+Zeichen mit einem zusätzlichen Backslash maskieren, zum Beispiel `\d+`.
+
+</Alert>
+
+<Alert type="warnung">
+In Express 4.x wird <a href="https://github.com/expressjs/express/issues/2495">das `*` Zeichen in regulären Ausdrücken nicht auf die übliche Weise</a> interpretiert. Benutze `{0,}` anstelle von `*`. Dies wird wahrscheinlich in Express 5 behoben.
+</Alert>
+
+## Routenhandler
+
+Du kannst mehrere Callback-Funktionen bereitstellen, die sich wie [middleware](/en/guide/using-middleware) verhalten um eine Anfrage zu bearbeiten. Die einzige Ausnahme ist, dass diese Callbacks `next('route')` aufrufen könnten, um die restlichen Rufnummern zu umgehen. Sie können diesen Mechanismus nutzen, um Vorbedingungen auf einer Route aufzuerlegen, dann die Kontrolle an die nachfolgenden Routen übergeben, wenn es keinen Grund gibt, mit der aktuellen Route fortzufahren.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In diesem Beispiel:
+
+- `GET /user/5` → behandelt durch die erste Route → sendet "Benutzer 5"
+- `GET /user/0` → erste Routenaufrufe `next('route')`, überspringt zur nächsten passenden `/user/:id` Route
+
+Routenhandler können in Form einer Funktion, eines Arrays von Funktionen oder Kombinationen beider sein, wie in den folgenden Beispielen gezeigt.
+
+Eine einzelne Callback-Funktion kann eine Route handhaben. Zum Beispiel:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hallo von A!');
+});
+```
+
+Mehr als eine Callback-Funktion kann eine Route handhaben (stelle sicher, dass du das `next` Objekt angibst). Zum Beispiel:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    Konsole.og('die Antwort wird von der nächsten Funktion gesendet. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Hallo von B!');
+  }
+);
+```
+
+Ein Array von Callback-Funktionen kann eine Route handhaben. Zum Beispiel:
+
+```js
+const cb0 = function (req, res, next) {
+  Konsole.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Hallo von C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Eine Kombination aus unabhängigen Funktionen und Arrays von Funktionen kann eine Route handhaben. Zum Beispiel:
+
+```js
+const cb0 = function (req, res, next) {
+  Konsole.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+App.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    Konsole.og('die Antwort wird von der nächsten Funktion gesendet. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Hallo von D!');
+  }
+);
+```
+
+## Antwortmethoden
+
+Die Methoden auf dem Antwortobjekt (`res`) in der folgenden Tabelle können eine Antwort an den Client senden und den Request-Antwort-Zyklus beenden. Wenn keine dieser Methoden von einem Routenhandler aufgerufen wird, bleibt die Client-Anfrage hängen.
+
+| Methode                                       | Beschreibung                                                                                              |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Fordern Sie eine Datei zum Download an.                                                                   |
+| [res.end()](/en/5x/api#res.end)               | Beenden Sie den Antwort-Prozess.                                                                          |
+| [res.json()](/en/5x/api#res.json)             | Sende eine JSON-Antwort.                                                                                  |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Senden Sie eine JSON-Antwort mit JSONP-Unterstützung.                                                     |
+| [res.redirect()](/en/5x/api#res.redirect)     | Anfrage umleiten.                                                                                         |
+| [res.render()](/en/5x/api#res.render)         | Ansichtsvorlage ausblenden.                                                                               |
+| [res.send()](/en/5x/api#res.send)             | Senden Sie eine Antwort von verschiedenen Typen.                                                          |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Senden Sie eine Datei als octet-Stream.                                                                   |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Legen Sie den Antwort-Statuscode fest und senden Sie seine Zeichenfolge Repräsentation als Antwortkörper. |
+
+## app.route()
+
+Sie können verkettende Routenhandler für einen Routenpfad erstellen, indem Sie `app.route()` verwenden.
+Da der Weg an einem einzigen Ort angegeben wird, ist die Schaffung modularer Routen hilfreich, ebenso wie die Reduzierung von Redundanz und Typos. Weitere Informationen über Routen finden Sie unter [Router() documentation](/en/5x/api#router).
+
+Hier ist ein Beispiel für verkettete Routenhandler, die mit `app.route()` definiert werden.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res. end('Holt ein zufälliges Buch');
+  })
+  . ost(req, res) => {
+    res.send('Add a book');
+  })
+  . ut((req, res) => {
+    res.send('Buch aktualisieren');
+});
+```
+
+## express.Router
+
+Verwende die Klasse `express.Router`, um modulare mountbare Routenhandler zu erstellen. Eine `Router`-Instanz ist ein komplettes Middleware- und Routing-System; aus diesem Grund wird sie oft als "Mini-App" bezeichnet.
+
+Das folgende Beispiel erzeugt einen Router als Modul, lädt eine Middleware-Funktion darin definiert einige Routen und mountet das Router-Modul auf einem Pfad in der Hauptanwendung.
+
+Erstelle eine Router-Datei namens `birds.js` im App-Verzeichnis, mit folgendem Inhalt:
+
+```js
+const express = require('express');
+const Router = express. outer();
+
+// Middleware, die spezifisch für diesen Router
+const timeLog = (req, res, next) => {
+  Konsole ist. og('Zeit: ', Date.now());
+  next();
+};
+Router. se(timeLog);
+
+// die Startseite Route
+router.get('/', (req, res) => {
+  res. end('Birds home page');
+});
+// die "about route
+definieren. et('/about', (req, res) => {
+  res.send('Über Vögel');
+});
+
+module.exports = router;
+```
+
+Laden Sie dann das Router-Modul in der App:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', Vögel);
+```
+
+Die App wird nun in der Lage sein, Anfragen an `/birds` und `/birds/about` zu bearbeiten, aufrufen sowie die Middleware-Funktion `timeLog` aufrufen, die spezifisch für die Route ist.
+
+Aber wenn die übergeordnete Route `/birds` Pfadparameter hat, wird sie standardmäßig nicht von den Unterrouten aus erreichbar sein. Um es zugänglich zu machen, müssen Sie die Option "mergeParams" an den Router-Konstruktor [reference](/en/5x/api#app.use) übergeben.
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/de/5x/guide/using-middleware.mdx b/src/content/docs/de/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..adfe7537b4
--- /dev/null
+++ b/src/content/docs/de/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Middleware verwenden
+description: Lernen Sie, wie Sie Middleware in Express.js-Anwendungen verwenden, einschließlich Middleware auf Anwendungsebene und Routerebene, Fehlerbehandlung und Integration von Middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express ist ein Routing- und Middleware-Webframework mit minimaler Funktionalität: Eine Express-Anwendung ist im Wesentlichen eine Reihe von Middleware-Funktionsaufrufen.
+
+_Middleware_ Funktionen sind Funktionen, die Zugriff auf das [request object](/en/5x/api#req) (`req`), das [Antwort-Objekt](/en/5x/api#res) (`res`) und die nächste Middleware-Funktion im Request-Antwort-Zyklus der Anwendung. Die nächste Middleware-Funktion wird üblicherweise durch eine Variable namens `next` bezeichnet.
+
+Middleware-Funktionen können folgende Aufgaben ausführen:
+
+- Führe jeden Code aus.
+- Änderungen an der Anfrage und den Antwort-Objekten vornehmen.
+- Beende den Request-Antwort-Zyklus.
+- Rufen Sie die nächste Middleware-Funktion im Stack auf.
+
+Wenn die aktuelle Middleware-Funktion den Request-Antwort-Zyklus nicht beendet, muss sie `next()` aufrufen, um die Kontrolle an die nächste Middleware-Funktion zu übergeben. Andernfalls bleibt die Anfrage hängen.
+
+Eine Express-Anwendung kann folgende Arten von Middleware verwenden:
+
+- [Middleware](#middleware.application)
+- [Router-Level-Middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Integrierte Middleware](#middleware.built-in)
+- [Middleware von Drittanbietern](#middleware.third-party)
+
+Sie können Middleware auf Anwendungsebene und Routerebene mit einem optionalen Mount-Pfad laden.
+Sie können auch eine Reihe von Middleware-Funktionen zusammen laden, die einen Sub-Stack des Middleware-Systems an einem Mount-Punkt erzeugen.
+
+## Middleware auf Anwendungsebene
+
+Binde Middleware auf Anwendungsebene an eine Instanz des [app object](/en/5x/api#app) durch Verwendung der `app.use()` und `app. ETHOD()` Funktionen, wobei `METHOD` die HTTP-Methode der Anfrage ist, die die Middleware-Funktion in Kleinbuchstaben behandelt (wie GET, PUT, oder POST)
+
+Dieses Beispiel zeigt eine Middleware-Funktion ohne Mount-Pfad. Die Funktion wird jedes Mal ausgeführt, wenn die App eine Anfrage erhält.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Dieses Beispiel zeigt eine Middleware-Funktion, die auf dem `/user/:id` Pfad eingehängt ist. Die Funktion wird für jede Art von
+HTTP-Anfrage im `/user/:id` Pfad ausgeführt.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Dieses Beispiel zeigt eine Route und deren Handler-Funktion (Middleware-System). Die Funktion bearbeitet GET-Anfragen an den Pfad `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Hier ist ein Beispiel für das Laden einer Reihe von Middleware-Funktionen an einem Mount-Punkt, mit einem Mount-Pfad.
+Es illustriert einen Middleware-Unterstapel, der Anfrageinformationen für jede Art von HTTP-Anfrage in den Pfad `/user/:id` ausgibt.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.og('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Routenhandler ermöglichen es Ihnen, mehrere Routen für einen Pfad zu definieren. Das folgende Beispiel definiert zwei Routen für GET-Anfragen zum Pfad `/user/:id`. Die zweite Route wird keine Probleme verursachen, aber sie wird nie aufgerufen, weil die erste Route den Request-Antwort-Zyklus beendet.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('User Info');
+  }
+);
+
+// Handler für den /user/:id Pfad, der die Benutzer-ID
+App ausgibt. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Um die restlichen Middleware-Funktionen eines Routers Middleware-Stacks zu überspringen, rufen Sie `next('route')` auf, um die Kontrolle an die nächste Route zu übergeben.
+
+<Alert type="info">
+
+`next('route')` funktioniert nur in Middleware-Funktionen, die mit den Funktionen
+`app.METHOD()` oder `router.METHOD()` geladen wurden.
+
+</Alert>
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, Nächste) => {
+    // wenn die Benutzer-ID 0 ist springe zur nächsten Route
+    wenn (req. arams. d === '0') als nächstes ('route');
+    // Andernfalls übergeben Sie die Steuerung an die nächste Middleware-Funktion in diesem Stack
+    else next();
+  },
+  (req, res, next) => {
+    // Senden Sie eine reguläre Antwort
+    res. end('regular');
+  }
+);
+
+// Handler für den /user/:id Pfad, der eine spezielle Antwort
+App sendet. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware kann auch in einem Array für Wiederverwendbarkeit deklariert werden.
+
+Dieses Beispiel zeigt ein Array mit einem Middleware-Sub-Stack an, das GET-Anfragen im Pfad `/user/:id` behandelt
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+App.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Middleware auf Routerebene
+
+Middleware auf Router-Ebene funktioniert wie Middleware auf Anwendungsebene, es sei denn, es ist an eine Instanz von `express.Router()` gebunden.
+
+```js
+const router = express.Router();
+```
+
+Laden Sie die Middleware router-level mittels der Funktionen `router.use()` und `router.METHOD()`.
+
+Der folgende Beispielcode repliziert das oben angezeigte Middleware-System für Middleware auf Anwendungsebene:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. Externe();
+
+// eine Middleware-Funktion ohne Mount-Pfad. Dieser Code wird für jede Anfrage an den Router
+ausgeführt. se(req, res, next) => {
+  console.log('Zeit:', Datum. ow());
+  next();
+});
+
+// Ein Middleware-Sub-Stack zeigt Anfrageinformationen für jede Art von HTTP-Anfrage an den /user/:id path
+Router an. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    Konsole. og('Request Typ:', req. ethod);
+    next();
+  }
+);
+
+// ein Middleware-Sub-Stack, der GET-Anfragen an den /user/:id path
+Router verarbeitet. et(
+  '/user/:id',
+  (req, res, Nächste) => {
+    // wenn die Benutzer-ID 0 ist springe zum nächsten Router
+    wenn (req. arams. d === '0') als nächstes ('route');
+    // Andernfalls übergeben Sie die Kontrolle an die nächste Middleware-Funktion in diesem Stapel
+    else next();
+  },
+  (req, res, next) => {
+    // rendern Sie eine reguläre Seite
+    res. ender('regular');
+  }
+);
+
+// Handler für den /user/:id Pfad, der eine spezielle Seite
+Router darstellt. et('/user/:id', (req, res, next) => {
+  Konsole. og(req.params.id);
+  res.render('special');
+});
+
+// Router auf die App
+app.use('/', Router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+Dieses Beispiel zeigt einen Middleware-Sub-Stack an, der GET-Anfragen im `/user/:id`-Pfad behandelt.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. Externe ();
+
+// Vorhersage des Routers mit Scheck und Kaution bei Bedarf
+Router. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hallo, user!');
+});
+
+// den Router verwenden und 401 alles, was durch die
+App fällt. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Fehler beim Umgang mit Middleware
+
+<Alert type="warnung">
+
+Bei der Fehlerbehebung der Middleware werden immer _vier_ Argumente verwendet. Sie müssen vier Argumente angeben, um
+als Middleware-Funktion zu identifizieren. Selbst wenn du das `next`
+Objekt nicht verwenden musst, musst du es angeben, um die Signatur zu pflegen. Andernfalls wird das `next` Objekt
+als reguläre Middleware interpretiert und wird Fehler nicht bearbeiten.
+
+</Alert>
+
+Definieren Sie die Middleware-Funktionen wie andere Middleware-Funktionen außer mit vier Argumenten anstelle von drei, speziell mit der Signatur `(err, req, res, next)`:
+
+```js
+app.use(((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Etwas kaputt!');
+});
+```
+
+Details über die Fehlerbehandlungsmittelsoftware finden Sie hier: [Fehlerbehandlung](/en/guide/error-handling).
+
+## Integrierte Middleware
+
+Ab Version 4.x ist Express nicht mehr abhängig von [Connect](https://github.com/senchalabs/connect). Die Middleware-
+\-Funktionen, die zuvor mit Express integriert wurden, befinden sich nun in separaten Modulen; siehe [Liste der Middleware-Funktionen](https://github.com/senchalabs/connect#middleware).
+
+Express hat die folgenden integrierten Middleware-Funktionen:
+
+- [express.static](/en/5x/api#express.static) dient statischen Assets wie HTML-Dateien, Bilder und so weiter.
+- [express.json](/en/5x/api#express.json) analysiert eingehende Anfragen mit JSON Payloads. **HINWEIS: Verfügbar mit Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analysiert eingehende Anfragen mit URL-kodierten Payloads. **HINWEIS: Verfügbar mit Express 4.16.0+**
+
+## Drittanbieter-Middleware
+
+Verwenden Sie Middleware von Drittanbietern, um Funktionen zu Express-Apps hinzuzufügen.
+
+Installieren Sie das Modul Node.js für die erforderliche Funktionalität, laden Sie es dann in Ihrer App auf der Anwendungsebene oder auf der Routerebene.
+
+Das folgende Beispiel zeigt die Installation und das Laden der Cookie-Parsing-Middleware-Funktion "cookie-parser".
+
+```bash
+$ npm Cookie-Parser installieren
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Für eine partielle Liste der Middleware-Funktionen von Drittanbietern, die häufig mit Express verwendet werden, siehe: [Middleware](../resources/middleware).
diff --git a/src/content/docs/de/5x/guide/using-template-engines.mdx b/src/content/docs/de/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..0a5b37a7c5
--- /dev/null
+++ b/src/content/docs/de/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Template-Engines mit Express verwenden
+description: Entdecken Sie, wie Sie Template-Engines wie Pug, Handlebars und EJS mit Express.js integrieren und nutzen können, um dynamische HTML-Seiten effizient zu machen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Eine _template engine_ ermöglicht es Ihnen, statische Template-Dateien in Ihrer Anwendung zu verwenden. Zur Laufzeit ersetzt die Template-Engine
+Variablen in einer Template-Datei mit aktuellen Werten und verwandelt die Vorlage in eine HTML-Datei, die an den Client gesendet wird.
+Dieser Ansatz erleichtert die Gestaltung einer HTML-Seite.
+
+Der [Express-Anwendungsgenerator](/en/starter/generator) verwendet [Pug](https://pugjs.org/api/getting-started.html) als Standardwert, aber es unterstützt auch [Handlebars](https://www.npmjs.com/package/handlebars), und [EJS](https://www.npmjs.com/package/ejs), unter anderem.
+
+Um Template-Dateien zu rendern, setzen Sie folgende [Anwendungs-Einstellungen-Eigenschaften](/en/4x/api#app.set), in der Standardeinstellung `app.js`, die vom Generator erstellt wurde:
+
+- `views`, das Verzeichnis, in dem sich die Template-Dateien befinden. Eg: `app.set('views', './views')`.
+  Dies ist standardmäßig im Verzeichnis `views` im Root-Verzeichnis der Anwendung.
+- `view engine`, die zu verwendende Template-Engine. Um zum Beispiel die Mückenvorlagen-Engine zu verwenden: `app.set('view engine', 'pug')`.
+
+Installieren Sie dann das entsprechende Template Engine npm Paket; zum Beispiel um Pug:
+
+```bash
+$ npm Installations-Pug --save
+```
+
+<Alert type="warnung">
+Express-konforme Template-Engines wie MUG exportieren eine Funktion namens `__express(filePath, options, callback)`,
+welche `res.render()` aufruft, um den Template-Code zu rendern.
+
+Einige Template-Engines folgen nicht dieser Konvention. Die [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+Bibliothek folgt dieser Konvention, indem sie alle populären Template-Engines von Node.js abbildet, und arbeitet daher nahtlos in Express.
+
+</Alert>
+
+Nachdem die View Engine gesetzt ist, müssen Sie nicht die Engine angeben oder das Template Engine Modul in Ihrer App laden;
+Express lädt das Modul intern, zum Beispiel:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Erstelle dann eine Pug Template Datei namens `index.pug` im `views` Verzeichnis mit folgendem Inhalt:
+
+```pug
+html
+  Kopf
+    title= title
+  Körper
+    h1= Nachricht
+```
+
+Erstelle eine Route um die `index.pug` Datei zu rendern. Wenn die `view engine` Eigenschaft nicht gesetzt ist,
+musst du die Erweiterung der `view` Datei angeben. Andernfalls können Sie es auslassen.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hallo there!' });
+});
+```
+
+Wenn du eine Anfrage an die Startseite stellt, wird die `index.pug` Datei als HTML dargestellt.
+
+Der View Engine-Cache speichert nicht den Inhalt der Templateausgabe, sondern nur die zugrunde liegende Vorlage selbst. Die Ansicht wird noch mit jeder Anfrage neu gerendert, auch wenn der Cache eingeschaltet ist.
diff --git a/src/content/docs/de/5x/guide/writing-middleware.mdx b/src/content/docs/de/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..477703c39b
--- /dev/null
+++ b/src/content/docs/de/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Schreibe Middleware für die Verwendung in Express-Apps
+description: Erfahren Sie, wie Sie benutzerdefinierte Middleware-Funktionen für Express.js-Anwendungen schreiben, einschließlich Beispielen und Best Practices zur Verbesserung der Request- und Response-Behandlung.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ Funktionen sind Funktionen, die Zugriff auf das [request object](/en/5x/api#req) (`req`), die [Antwort-Objekt](/en/5x/api#res) (`res`) und die `next` Funktion im Request-Antwort-Zyklus der Anwendung. Die `next`-Funktion ist eine Funktion im Express-Router, der beim Aufruf die Middleware ausführt, die die aktuelle Middleware abfolgt.
+
+Middleware-Funktionen können folgende Aufgaben ausführen:
+
+- Führe jeden Code aus.
+- Änderungen an der Anfrage und den Antwort-Objekten vornehmen.
+- Beende den Request-Antwort-Zyklus.
+- Rufen Sie die nächste Middleware im Stapel auf.
+
+Wenn die aktuelle Middleware-Funktion den Request-Antwort-Zyklus nicht beendet, muss sie `next()` aufrufen, um die Kontrolle an die nächste Middleware-Funktion zu übergeben. Andernfalls bleibt die Anfrage hängen.
+
+Die folgende Abbildung zeigt die Elemente eines Middleware-Funktionsaufrufs:
+
+![Elemente einer Middleware-Funktion aufruf](/images/express-mw.png)
+
+Beginnend mit Express 5 ruft Middleware-Funktionen, die ein Versprechen zurückgeben, `next(value)` auf, wenn sie einen Fehler ablehnen oder werfen. `next` wird entweder mit dem abgelehnten Wert oder mit dem Wurffehler aufgerufen.
+
+## Beispiel
+
+Hier ist ein Beispiel für eine einfache "Hallo World"-Express-Anwendung.
+Der Rest dieses Artikels definiert und fügt der Anwendung drei Middleware-Funktionen hinzu:
+eine mit dem Namen `myLogger`, die eine einfache Logmeldung ausgibt, einen namens `requestTime`, der
+den Zeitstempel der HTTP-Anfrage anzeigt und einen, der `validateCookies` genannt wird, der eingehende Cookies validiert.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hallo World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware-Funktion myLogger
+
+Hier ist ein einfaches Beispiel für eine Middleware-Funktion namens "myLogger". Diese Funktion druckt nur
+"LOGGED", wenn eine Anfrage an die App durchläuft. Die Middleware-Funktion wird einer
+Variable mit dem Namen `myLogger` zugewiesen.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="warnung">
+
+Beachten Sie den obigen Aufruf zu `next()`. Beim Aufruf dieser Funktion wird die nächste Middleware-Funktion in
+der App aufgerufen. Die `next()` Funktion ist kein Teil des Knotens. s oder Express API, aber ist das dritte
+\-Argument, das an die Middleware-Funktion übergeben wird. Die `next()` Funktion kann alles benannt werden,
+, aber nach der Konvention wird sie immer als "weiter" bezeichnet. Um Verwirrung zu vermeiden, verwenden Sie immer dieses Übereinkommen.
+
+</Alert>
+
+Um die Middleware-Funktion zu laden, rufen Sie `app.use()` auf, indem Sie die Middleware-Funktion angeben.
+Zum Beispiel lädt der folgende Code die `myLogger` Middleware-Funktion vor der Route zum Root-Pfad (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hallo World!');
+});
+
+app.listen(3000);
+```
+
+Jedes Mal, wenn die App eine Anfrage erhält, gibt sie die Nachricht "LOGGED" auf das Terminal aus.
+
+Die Reihenfolge des Laden von Middleware ist wichtig: Middleware-Funktionen, die zuerst geladen werden, werden auch zuerst ausgeführt.
+
+Wenn `myLogger` nach der Route zum Wurzelpfad geladen wird, erreicht die Anfrage nie und die App druckt nicht "LOGGED", da der Route-Handler des Root-Pfades den Request-Antwort-Zyklus beendet.
+
+Die Middleware-Funktion `myLogger` druckt einfach eine Nachricht, übergibt dann die Anfrage an die nächste Middleware-Funktion im Stack durch Aufruf der `next()` Funktion.
+
+### Middleware-Funktionsanfragezeit
+
+Als nächstes erstellen wir eine Middleware-Funktion namens "requestTime" und fügen eine Eigenschaft namens `requestTime`
+dem Anfrageobjekt hinzu.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+Die App verwendet nun die „requestTime“-Middleware-Funktion. Auch die Callback-Funktion der Root-Pfadroute verwendet die Eigenschaft, die die Middleware-Funktion zu `req` hinzufügt (das Anfrageobjekt).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+Wenn Sie eine Anfrage an das Stammverzeichnis der App stellen, zeigt die App nun den Zeitstempel Ihrer Anfrage im Browser an.
+
+### Middleware-Funktion validateCookies
+
+Schließlich erstellen wir eine Middleware-Funktion, die eingehende Cookies validiert und eine 400 Antwort schickt, wenn Cookies ungültig sind.
+
+Hier ist eine Beispielfunktion, die Cookies mit einem externen Asynchrondienst überprüft.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    wait externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Ungültige Cookies');
+  }
+}
+```
+
+Hier verwenden wir die [`cookie-parser`](/en/resources/middleware/cookie-parser) Middleware, um eingehende Cookies vom `req` Objekt zu analysieren und sie an unsere `cookieValidator` Funktion zu übergeben. Die `validateCookies` Middleware gibt ein Versprechen zurück, das bei Ablehnung automatisch unseren Fehlerhandler auslöst.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  wartet cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// Fehlerbehandler
+app. se(err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="warnung">
+
+Beachte, wie `next()` nach `wait cookieValidator(req.cookies)` aufgerufen wird. Dies stellt sicher, dass, wenn
+`cookieValidator` auflöst, die nächste Middleware im Stack aufgerufen wird. Wenn du etwas
+an die `next()` Funktion übergibt (außer den String `'route'` oder `'router'`), Express betrachtet die aktuelle
+Anfrage als Fehler und überspringt alle verbleibenden Funktionen zur Fehlerbehandlung und Middleware
+.
+
+</Alert>
+
+Weil Sie Zugriff auf das Anfrageobjekt, das Antwortobjekt, die nächste Middleware-Funktion im Stapel und den gesamten Knoten haben. s API, die Möglichkeiten mit Middleware-Funktionen sind endlos.
+
+Für weitere Informationen über Express Middleware siehe: [Express Middleware](/en/guide/using-middleware).
+
+## Konfigurierbare Middleware
+
+Wenn Sie Ihre Middleware konfigurieren müssen, exportieren Sie eine Funktion, die ein Optionsobjekt oder andere Parameter akzeptiert, , die dann die Middleware-Implementierung basierend auf den Eingabeparametern zurückgibt.
+
+Datei: `my-middleware.js`
+
+```js
+modul.xports = function (options) {
+  return function (req, res, next) {
+    // Implementierung der Middleware-Funktion basierend auf dem Options-Objekt
+    next();
+  };
+};
+```
+
+Die Middleware kann nun wie unten gezeigt verwendet werden.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Siehe [cookie-session](https://github.com/expressjs/cookie-session) und [compression](https://github.com/expressjs/compression) für Beispiele konfigurierbarer Middleware.
diff --git a/src/content/docs/de/5x/starter/basic-routing.mdx b/src/content/docs/de/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..dce7483626
--- /dev/null
+++ b/src/content/docs/de/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basisrouting
+description: Lernen Sie die Grundlagen des Routings in Express.js Anwendungen kennen, wie Sie Routen definieren, HTTP-Methoden handhaben und Routenhandler für Ihren Webserver erstellen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ bezieht sich darauf, wie eine Anwendung auf einen bestimmten Endpunkt antwortet , die eine URI (oder Pfad) und eine bestimmte HTTP-Request-Methode (GET, POST usw.) ist.
+
+Jede Route kann eine oder mehrere Handler-Funktionen haben, die ausgeführt werden, wenn die Route übereinstimmt.
+
+Die Routendefinition nimmt folgende Struktur ein:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Wo:
+
+- `app` ist eine Instanz von `express `.
+- `METHOD` ist eine [HTTP-Anfrage-Methode](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in Kleinbuchstaben.
+- `PATH` ist ein Pfad auf dem Server.
+- `HANDLER` ist die Funktion, die ausgeführt wird, wenn die Route übereinstimmt.
+
+<Alert type="warnung">
+
+Dieses Tutorial setzt voraus, dass eine Instanz von `express ` namens `app` erstellt wird und der Server
+läuft. Wenn du nicht vertraut bist, eine App zu erstellen und sie zu starten, schau dir das Hallo Welt
+Beispiel.
+
+</Alert>
+
+Die folgenden Beispiele veranschaulichen die Definition einfacher Routen.
+
+Antworte mit `Hallo World!` auf der Homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hallo Welt!');
+});
+```
+
+Antwort auf eine POST-Anfrage auf der Root-Route (`/`), der Startseite der Anwendung:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Hat eine POST-Anfrage');
+});
+```
+
+Antworte auf eine PUT-Anfrage auf die `/user`-Route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Eine PUT-Anfrage bei /user');
+});
+```
+
+Antworte auf eine LÖSCHE Anfrage auf die `/user`-Route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Erhalte eine DELETE Anfrage unter /user');
+});
+```
+
+Weitere Details zum Routen finden Sie im [Routing Guide](/en/guide/routing).
diff --git a/src/content/docs/de/5x/starter/examples.mdx b/src/content/docs/de/5x/starter/examples.mdx
new file mode 100644
index 0000000000..815bf0c6f3
--- /dev/null
+++ b/src/content/docs/de/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Express-Beispiele
+description: Entdecken Sie eine Sammlung von Express.js Anwendungsbeispielen, die verschiedene Anwendungsfälle, Integrationen und erweiterte Konfigurationen umfassen, um Ihnen zu helfen Ihre Projekte zu erlernen und zu bauen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Diese Seite enthält eine Liste von Beispielen mit Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Authentifizierung mit Login und Passwort
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - HTTP-Inhaltsaushandlung
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Arbeiten mit Cookie-basierten Sitzungen
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Arbeiten mit Cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Übertragung von Dateien zum Client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Arbeiten mit eingebetteten JavaScript-Vorlagen (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Fehlerseiten erstellen
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Mit Fehler-Middleware arbeiten
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Einfacher Anfragehandler
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown als Template-Engine
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Mit mehreren Express-Routern arbeiten
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - Controller im MVC-Stil
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Verfolgung der Online-Benutzeraktivität mit `online` und `redis` Paketen
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Arbeiten mit Routenparametern
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Mehrere HTTP-Operationen auf derselben Ressource
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Routen mit einer Karte organisieren
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Mit Route Middleware arbeiten
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Routen pro Ressource organisieren
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Such-API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - Benutzersitzungen
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Serviere statische Dateien
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Arbeiten mit virtuellen Hosts
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Ansichten dynamisch rendern
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Speichern von Daten im Anfrageobjekt zwischen Middleware-Aufrufen
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Einfacher API-Dienst
+
+## Zusätzliche Beispiele
+
+Dies sind einige zusätzliche Beispiele mit umfassenderen Integrationen.
+
+<Alert type="warnung">
+
+Diese Informationen beziehen sich auf Sites, Produkte oder Module, die nicht vom
+Expressjs Team betreut werden. Die Auflistung hier stellt keine Billigung oder Empfehlung des Projektteams von
+Expressjs dar.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Vollstack App mit Express und Next.js mit [Prisma](https://www.npmjs.com/package/prisma) als ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API mit Express in TypeScript mit [Prisma](https://www.npmjs.com/package/prisma) als ORM
diff --git a/src/content/docs/de/5x/starter/faq.md b/src/content/docs/de/5x/starter/faq.md
new file mode 100644
index 0000000000..8df0cc1a28
--- /dev/null
+++ b/src/content/docs/de/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Finden Sie Antworten auf häufig gestellte Fragen zu Express.js, darunter Themen wie Anwendungsstruktur, Modelle, Authentifizierung, Template-Engines, Fehlerbehandlung und mehr.
+---
+
+## Wie kann ich meine Anwendung strukturieren?
+
+Auf diese Frage gibt es keine endgültige Antwort. Die Antwort hängt von
+vom Umfang Ihrer Anwendung und dem beteiligten Team ab. Um so flexibel wie möglich
+zu sein, macht Express keine Annahmen in Bezug auf die Struktur.
+
+Routen und andere anwendungsspezifische Logik können in beliebig vielen Dateien
+in beliebiger Verzeichnisstruktur gespeichert werden. Folgende
+Beispiele für Inspirationen anzeigen:
+
+- [Route Listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Routenplane](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Außerdem gibt es Erweiterungen von Drittanbietern für Express, die einige dieser Muster vereinfachen:
+
+- [Ressourcenreiches Routen](https://github.com/expressjs/express-resource)
+
+## Wie definiere ich Modelle?
+
+Express hat keine Vorstellung von Datenbanken. Dieses Konzept ist
+bis zu Drittanbieter-Knotenmodulen übrig und erlaubt Ihnen eine
+Schnittstelle mit fast jeder Datenbank.
+
+Siehe [LoopBack](http://loopback.io) für ein Express-basiertes Framework, das um Modelle zentriert ist.
+
+## Wie kann ich Benutzer authentifizieren?
+
+Authentifizierung ist ein anderer Bereich, in dem sich Express nicht
+wagt. Sie können ein beliebiges Authentifizierungsschema verwenden.
+Für ein einfaches Benutzername/Passwort-Schema, siehe [dieses Beispiel](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Welche Template-Engines unterstützt Express?
+
+Express unterstützt jede Template-Engine, die mit der Signatur `(Pfad, locals, callback)` übereinstimmt.
+Um die Schnittstellen der Template-Engine und das Caching zu normalisieren, lesen Sie bitte
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+Projekt für Unterstützung. Nicht aufgelistete Template-Engines könnten die Express-Signatur trotzdem unterstützen.
+
+Weitere Informationen finden Sie unter [Template-Engines mit Express](/en/guide/using-template-engines).
+
+## Wie gehe ich mit 404 Antworten um?
+
+In Express sind 404 Antworten nicht das Ergebnis eines Fehlers, daher wird die Middleware von
+nicht erfasst. Dieses Verhalten ist
+, da eine 404-Antwort einfach das Fehlen zusätzlicher Arbeit anzeigt;
+in anderen Worten, Express hat alle Middleware-Funktionen und -Routen ausgeführt,
+und festgestellt, dass keiner von ihnen reagiert hat. Alles, was Sie
+tun müssen, ist eine Middleware-Funktion am unteren Ende des Stacks (unter allen anderen Funktionen)
+hinzuzufügen, um eine 404-Antwort zu handhaben:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Fügen Sie Routen dynamisch zur Laufzeit einer Instanz von `express.Router()`
+hinzu, so dass die Routen nicht durch eine Middleware-Funktion ersetzt werden.
+
+## Wie kann ich einen Fehler einrichten?
+
+Du definierst die Middleware wie andere Middleware,
+außer mit vier anstatt drei, spezifisch mit der Signatur `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Weitere Informationen finden Sie unter [Fehlerbehandlung](/en/guide/error-handling).
+
+## Wie kann ich plain HTML rendern?
+
+Du bist es nicht! Es gibt keine Notwendigkeit HTML mit der Funktion `res.render()` zu "render".
+Wenn du eine bestimmte Datei hast, nutze die Funktion `res.sendFile()`.
+Wenn du viele Assets aus einem Verzeichnis lieferst, verwende die `express.static()`
+Middleware-Funktion.
+
+## Welche Version von Node.js benötigt Express?
+
+- [Express 4.x](/en/4x/api) benötigt Node.js 0.10 oder höher.
+- [Express 5.x](/en/5x/api) benötigt Node.js 18 oder höher.
diff --git a/src/content/docs/de/5x/starter/generator.mdx b/src/content/docs/de/5x/starter/generator.mdx
new file mode 100644
index 0000000000..53c5930dbb
--- /dev/null
+++ b/src/content/docs/de/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express-Applikationsgenerator
+description: Lernen Sie, wie Sie mit dem Express-Anwendungsgenerator-Tool schnell ein Skelett für Ihre Express.js-Anwendungen erstellen, die Einrichtung optimieren und die Konfiguration optimieren.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Verwenden Sie das Applikationsgenerator-Tool, "express-generator", um schnell ein Anwendungsskelett zu erstellen.
+
+Du kannst den Anwendungsgenerator mit dem Befehl `npx` ausführen (verfügbar in Node.js 8.2.0).
+
+```bash
+$ npx Express-Generator
+```
+
+Für frühere Node-Versionen installieren Sie den Anwendungsgenerator als globales npm-Paket und starten es dann:
+
+```bash
+$ npm Installation -g Express-Generator
+$ express
+```
+
+Zeige die Befehlsoptionen mit der `-h` Option:
+
+```bash
+$ express -h
+
+  Verwendung: Express [options] [dir]
+
+  Optionen:
+
+    -h, --help Ausgabe-Informationen
+        --version Ausgabe der Versionsnummer
+    -e, --ejs add ejs engine support
+        --hbs add handlebars engine support
+        --pug add pug engine support
+    -H, --hogan add hogan. s Engine Unterstützung
+        --no-view generieren ohne View Engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  Fügen Sie Stylesheet <engine> Unterstützung (less |stylus|compass|sass) (standardmäßig auf plain css)
+        --git add . itignore
+    -f, --force auf nicht leeres Verzeichnis
+```
+
+Zum Beispiel erstellt das Folgende eine Express-App namens _myapp_. Die App wird in einem Ordner namens _myapp_ im aktuellen Arbeitsverzeichnis erstellt und die View Engine wird auf <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Mops</a> gesetzt:
+
+```bash
+$ express --view=pug myapp
+
+   erstellen : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   erstellen : myapp/routes/users. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   erstellen : myapp/views
+   erstellen : myapp/views/index. ug
+   erstellen : myapp/views/layout.pug
+   erstellen : myapp/views/error. ug
+   erstellen : myapp/bin
+   erstellen : myapp/bin/www
+```
+
+Installieren Sie dann Abhängigkeiten:
+
+```bash
+$ cd myapp
+$ npm Installation
+```
+
+Führen Sie auf MacOS oder Linux die App mit diesem Befehl aus:
+
+```bash
+$ DEBUG=myapp:* npm Start
+```
+
+Benutzen Sie auf Windows Befehlsaufforderung folgenden Befehl:
+
+```bash
+> DEBUG=myapp:* & npm Start setzen
+```
+
+Verwenden Sie unter Windows PowerShell, diesen Befehl:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm Start
+```
+
+Lade dann `http://localhost:3000/` in deinem Browser, um auf die App zuzugreifen.
+
+Die generierte App hat folgende Verzeichnisstruktur:
+
+```bash
+.
+<unk> 本<unk> app.js
+<unk> 本<unk> bin
+<unk> <unk> <unk> <unk> <unk> www
+<unk> 本<unk> Paket. son
+<unk> 文<unk> public
+<unk> <unk> <unk> <unk> <unk> Bilder
+<unk> <unk> <unk> <unk> <unk> <unk> <unk> javascripts
+<unk> <unk> <unk> Stylesheets
+<unk> <unk> style. ss
+<unk> 本<unk> routet
+<unk> <unk> <unk> <unk> index.js
+<unk> <unk> <unk> <unk> Benutzer. s
+<unk> 本<unk> Ansichten
+    <unk> <unk> <unk> Fehler. ug
+    <unk> 本<unk> index.pug
+    <unk> <unk> layout.pug
+
+7 Verzeichnisse, 9 Dateien
+```
+
+<Alert type="info">
+
+Die vom Generator erstellte App-Struktur ist nur eine von vielen Möglichkeiten, Express-Apps zu strukturieren.
+Fühlen Sie sich frei, diese Struktur zu verwenden oder sie so zu modifizieren, dass sie Ihren Bedürfnissen am besten entspricht.
+
+</Alert>
diff --git a/src/content/docs/de/5x/starter/hello-world.mdx b/src/content/docs/de/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..14fbd320f5
--- /dev/null
+++ b/src/content/docs/de/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hallo Weltbeispiel
+description: Beginnen Sie mit Express.js, indem Sie eine einfache 'Hallo World'-Anwendung erstellen, die die Grundeinstellung und die Servererstellung für Anfänger demonstriert.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Eingebettet unten ist im Wesentlichen die einfachste Express-App, die Sie erstellen können. Es ist eine einzelne Datei-App
+&mdash; _not_ was Sie bekommen würden, wenn Sie den [Express-Generator](/en/starter/generator), welche
+das Gerüst für eine vollständige Anwendung mit zahlreichen JavaScript-Dateien, Jade-Vorlagen und
+Unterverzeichnissen für verschiedene Zwecke erstellt.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hallo World!');
+});
+
+app.listen(port, () => {
+  console.log(`Beispiel-App, die auf Port ${port}`);
+});
+```
+
+Diese App startet einen Server und lauscht auf Port 3000 für Verbindungen. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. Für jeden anderen Pfad wird es mit einem **404 Nicht gefunden** antworten.
+
+## Lokal laufen
+
+Erstelle zuerst ein Verzeichnis namens `myapp`, ändere es und führe `npm init` aus. Installieren Sie dann `Expres` als Abhängigkeit, wie in der [Installationsanleitung](/en/starter/installing).
+
+Erstelle im `myapp` Verzeichnis eine Datei namens `app.js` und kopiere den Code aus dem obigen Beispiel.
+
+<Alert type="warnung">
+
+Die `req` (Anfrage) und `res` (Antwort) sind genau die gleichen Objekte, die der Knoten anbietet, also kann
+`req aufrufen. ipe()`, `req.on('data', callback)` und alles, was Sie sonst ohne Express
+tun würden.
+
+</Alert>
+
+Führen Sie die App mit dem folgenden Befehl aus:
+
+```bash
+$ node app.js
+```
+
+Lade dann `http://localhost:3000/` in einem Browser, um die Ausgabe zu sehen.
diff --git a/src/content/docs/de/5x/starter/installing.mdx b/src/content/docs/de/5x/starter/installing.mdx
new file mode 100644
index 0000000000..5c8cda4b06
--- /dev/null
+++ b/src/content/docs/de/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installiere
+description: Erfahren Sie, wie Sie Express.js in Ihrer Node.js-Umgebung installieren, einschließlich der Einrichtung Ihres Projektverzeichnisses und der Verwaltung von Abhängigkeiten mit npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Bevor Sie beginnen, stellen Sie sicher, dass Sie [Node.js](https://nodejs.org/) 18 oder höher installiert haben. Erstellen Sie dann ein Verzeichnis für Ihre Anwendung und navigieren Sie hinein.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Benutze den Befehl `npm init` um eine `package.json` Datei für deine Anwendung zu erstellen.
+Für weitere Informationen darüber, wie `package.json` funktioniert, siehe [Spezifikationen für npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Dieser Befehl fragt Sie nach einer Reihe von Dingen wie dem Namen und der Version Ihrer Anwendung.
+Im Moment können Sie einfach RETURN drücken, um die Standardwerte für die meisten von ihnen zu akzeptieren, mit der folgenden Ausnahme:
+
+```
+eintragspunkt: (index.js)
+```
+
+Geben Sie `app.js` ein, oder was auch immer der Name der Hauptdatei sein soll. Wenn Sie `index.js` wollen, drücken Sie RETURN um den empfohlenen Dateinamen zu akzeptieren.
+
+Installieren Sie jetzt Express im `myapp` Verzeichnis und speichern Sie es in der Abhängigkeitsliste. Zum Beispiel:
+
+```bash
+npm Express installieren
+```
+
+Um Express vorübergehend zu installieren und nicht zur Abhängigkeitsliste hinzufügen:
+
+```bash
+npm express installieren --no-save
+```
diff --git a/src/content/docs/de/5x/starter/static-files.mdx b/src/content/docs/de/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..f1c8dc894a
--- /dev/null
+++ b/src/content/docs/de/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serviere statische Dateien in Express
+description: Verstehen Sie, wie Sie statische Dateien wie Bilder, CSS und JavaScript in Express.js Anwendungen mit der integrierten 'static' Middleware bedienen können.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um statische Dateien wie Bilder, CSS-Dateien und JavaScript-Dateien bereitzustellen, verwenden Sie die in Express integrierte Middleware-Funktion `express.static`.
+
+Die Funktionssignatur ist:
+
+```js
+express.static(root, [options]);
+```
+
+Das `root` Argument gibt das Wurzelverzeichnis an, von dem aus statische Assets ausgeliefert werden sollen.
+Für weitere Informationen zum Argument `options` siehe [express.static](/en/5x/api#express.static).
+
+Verwenden Sie zum Beispiel den folgenden Code, um Bilder, CSS-Dateien und JavaScript-Dateien in einem Verzeichnis mit dem Namen `public` auszugeben:
+
+```js
+app.use(express.static('public'));
+```
+
+Jetzt kannst du die Dateien im `public` Verzeichnis laden:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express sucht die Dateien relativ zum statischen Verzeichnis, so dass der Name des statischen Verzeichnisses
+nicht Teil der URL ist.
+
+</Alert>
+
+Um mehrere statische Asset-Verzeichnisse zu verwenden, rufen Sie die `express.static` Middleware-Funktion mehrmals auf:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express sucht die Dateien in der Reihenfolge, in der du die statischen Verzeichnisse mit der Middleware-Funktion `express.static` gesetzt hast.
+
+<Alert type="info">
+
+Für beste Ergebnisse Benutze einen Reverse
+Proxy Cache um die Leistung von
+zu verbessern und statische Assets zu bedienen.
+
+</Alert>
+
+Um einen virtuellen Pfad-Präfix zu erstellen (wo der Pfad existiert eigentlich nicht im Dateisystem) für Dateien, die durch die `express. tatic` Funktion, [einen Mount-Pfad angeben](/en/5x/api#app.use) für das statische Verzeichnis angeben, wie unten angezeigt:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Nun kannst du die Dateien, die sich im `public` Verzeichnis befinden, aus dem `/static` Pfadpräfix laden.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Der Pfad, den du der `express.static` Funktion zur Verfügung stellst, ist jedoch relativ zu dem Verzeichnis, von dem aus du deinen `node` Prozess startest. Wenn Sie die Express-App aus einem anderen Verzeichnis ausführen, ist es sicherer, den absoluten Pfad des Verzeichnisses zu verwenden, das Sie verwenden möchten:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public'));
+```
+
+Weitere Informationen über die `serve-static` Funktion und ihre Optionen finden Sie unter [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/en/4x/advanced/developing-template-engines.md b/src/content/docs/en/4x/advanced/developing-template-engines.md
new file mode 100755
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/en/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/en/4x/guide/behind-proxies.mdx b/src/content/docs/en/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/en/4x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/en/4x/guide/debugging.mdx b/src/content/docs/en/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/en/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/en/4x/guide/error-handling.mdx b/src/content/docs/en/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/en/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/en/4x/guide/overriding-express-api.md b/src/content/docs/en/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/en/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/en/4x/guide/routing.mdx b/src/content/docs/en/4x/guide/routing.mdx
new file mode 100644
index 0000000000..69f611b68b
--- /dev/null
+++ b/src/content/docs/en/4x/guide/routing.mdx
@@ -0,0 +1,395 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/4x/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/4x/api/application#appmethodpath-callback--callback-). You can also use [app.all()](/en/4x/api/application#appallpath-callback--callback-) to handle all HTTP methods and [app.use()](/en/4x/api/application#appusepath-callback--callback) to
+specify middleware as the callback function (See [Using middleware](/en/4x/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/4x/api/application#appmethodpath-callback--callback-).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+### Route paths based on strings
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+This route path will match requests to the root route, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+This route path will match requests to `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+This route path will match requests to `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Route paths based on string patterns
+
+This route path will match `acd` and `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+This route path will match `/abe` and `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Route paths based on regular expressions
+
+<Alert type="alert">
+
+Regular expression characters such as `$` need to be escaped with a `\`.
+
+</Alert>
+
+This route path will match anything with an "a" in it.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
+
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warning">
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\`
+characters with an additional backslash, for example `\\d+`.
+
+</Alert>
+
+<Alert type="warning">
+The <a href="https://github.com/expressjs/express/issues/2495">`*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`.
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                                                       | Description                                                                           |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/4x/api/response#resdownloadpath--filename--options--fn) | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/4x/api/response#resenddata-encoding-callback)                | End the response process.                                                             |
+| [res.json()](/en/4x/api/response#resjsonbody)                                | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/4x/api/response#resjsonpbody)                              | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/4x/api/response#resredirectstatus-path)                 | Redirect a request.                                                                   |
+| [res.render()](/en/4x/api/response#resrenderview--locals--callback)          | Render a view template.                                                               |
+| [res.send()](/en/4x/api/response#ressendbody)                                | Send a response of various types.                                                     |
+| [res.sendFile()](/en/4x/api/response#ressendfilepath--options--fn)           | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/4x/api/response#ressendstatusstatuscode)              | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/4x/api/router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/4x/api/application#appusepath-callback--callback).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/en/4x/guide/using-middleware.mdx b/src/content/docs/en/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/en/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/en/4x/guide/using-template-engines.mdx b/src/content/docs/en/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/en/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/en/4x/guide/writing-middleware.mdx b/src/content/docs/en/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..22354ecbe5
--- /dev/null
+++ b/src/content/docs/en/4x/guide/writing-middleware.mdx
@@ -0,0 +1,237 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+<div class="table-scroller">
+<table id="mw-fig">
+<tr><td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">HTTP method for which the middleware function applies.</div>
+
+<div class="callout" id="callout2">
+  Path (route) for which the middleware function applies.
+</div>
+
+<div class="callout" id="callout3">
+  The middleware function.
+</div>
+
+<div class="callout" id="callout4">
+  Callback argument to the middleware function, called "next" by convention.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">response</a> argument to the middleware function, called "res" by
+  convention.
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">request</a> argument to the middleware function, called "req" by convention.</div>
+</td></tr>
+</table>
+</div>
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/en/4x/starter/basic-routing.mdx b/src/content/docs/en/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..1d9ee9316e
--- /dev/null
+++ b/src/content/docs/en/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the [Hello world
+example](/en/starter/hello-world).
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/en/4x/starter/examples.mdx b/src/content/docs/en/4x/starter/examples.mdx
new file mode 100644
index 0000000000..6685b9cbe4
--- /dev/null
+++ b/src/content/docs/en/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+  This information refers to third-party sites, products, or modules that are not maintained by the
+  Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+  Expressjs project team.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/en/4x/starter/faq.md b/src/content/docs/en/4x/starter/faq.md
new file mode 100755
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/en/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/en/4x/starter/generator.mdx b/src/content/docs/en/4x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/en/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/en/4x/starter/hello-world.mdx b/src/content/docs/en/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/en/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/en/4x/starter/installing.mdx b/src/content/docs/en/4x/starter/installing.mdx
new file mode 100644
index 0000000000..fc66c7f9df
--- /dev/null
+++ b/src/content/docs/en/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 0.10 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="info">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Then, afterwards, running `npm install` in the app directory will automatically
+install modules in the dependencies list.
+
+</Alert>
diff --git a/src/content/docs/en/4x/starter/static-files.mdx b/src/content/docs/en/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..25009911ce
--- /dev/null
+++ b/src/content/docs/en/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, [use a reverse
+proxy](/en/advanced/best-practice-performance#use-a-reverse-proxy) cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/en/5x/advanced/developing-template-engines.md b/src/content/docs/en/5x/advanced/developing-template-engines.md
new file mode 100755
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/en/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/en/5x/guide/behind-proxies.mdx b/src/content/docs/en/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/en/5x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/en/5x/guide/debugging.mdx b/src/content/docs/en/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/en/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/en/5x/guide/error-handling.mdx b/src/content/docs/en/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/en/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/en/5x/guide/overriding-express-api.md b/src/content/docs/en/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/en/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/en/5x/guide/routing.mdx b/src/content/docs/en/5x/guide/routing.mdx
new file mode 100644
index 0000000000..0b6b0cb7f1
--- /dev/null
+++ b/src/content/docs/en/5x/guide/routing.mdx
@@ -0,0 +1,375 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/5x/api/application#appmethodpath-callback--callback-). You can also use [app.all()](/en/5x/api/application#appallpath-callback--callback-) to handle all HTTP methods and [app.use()](/en/5x/api/application#appusepath-callback--callback) to
+specify middleware as the callback function (See [Using middleware](/en/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/5x/api/application#appmethodpath-callback--callback-).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings or regular expressions.
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) v8 for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+### String paths
+
+String paths match requests exactly. The dot (`.`) and hyphen (`-`) are interpreted literally.
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Wildcards
+
+Wildcards match any path after a prefix. They must have a name, just like route parameters, and are captured as arrays of path segments.
+
+```js
+app.get('/files/*filepath', (req, res) => {
+  // GET /files/images/logo.png
+  console.dir(req.params.filepath);
+  // => [ 'images', 'logo.png' ]
+  res.send(`File: ${req.params.filepath.join('/')}`);
+});
+```
+
+To also match the root path, wrap the wildcard in braces:
+
+```js
+// Matches / , /foo , /foo/bar , etc.
+app.get('/{*splat}', (req, res) => {
+  // GET / => req.params.splat = []
+  // GET /foo/bar => req.params.splat = [ 'foo', 'bar' ]
+  res.send('ok');
+});
+```
+
+### Optional segments
+
+Use braces to define optional segments in a route path. When the segment is not present, the parameter is omitted from `req.params`.
+
+```js
+app.get('/:file{.:ext}', (req, res) => {
+  // GET /image.png => req.params = { file: 'image', ext: 'png' }
+  // GET /image => req.params = { file: 'image' }
+  res.send('ok');
+});
+```
+
+<Alert type="alert">
+
+The characters `?`, `+`, `*`, `[]`, and `()` are reserved and cannot be used as literal characters in route paths. Use `\` to escape them if needed.
+
+</Alert>
+
+### Regular expressions
+
+You can also use regular expressions as route paths. This is useful when you need more complex matching logic.
+
+```js
+// Matches any path containing "a"
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+
+// Matches paths ending with "fly" (butterfly, dragonfly, etc.)
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alert">
+
+Regexp characters are not supported in route paths. Use an array of paths or regular expressions instead.
+See the [path route matching syntax](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                                                       | Description                                                                           |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api/response#resdownloadpath--filename--options--fn) | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/5x/api/response#resenddata-encoding-callback)                | End the response process.                                                             |
+| [res.json()](/en/5x/api/response#resjsonbody)                                | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/5x/api/response#resjsonpbody)                              | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/5x/api/response#resredirectstatus-path)                 | Redirect a request.                                                                   |
+| [res.render()](/en/5x/api/response#resrenderview--locals--callback)          | Render a view template.                                                               |
+| [res.send()](/en/5x/api/response#ressendbody)                                | Send a response of various types.                                                     |
+| [res.sendFile()](/en/5x/api/response#ressendfilepath--options--fn)           | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/5x/api/response#ressendstatusstatuscode)              | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/5x/api/router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/5x/api/application#appusepath-callback--callback).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/en/5x/guide/using-middleware.mdx b/src/content/docs/en/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/en/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/en/5x/guide/using-template-engines.mdx b/src/content/docs/en/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/en/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/en/5x/guide/writing-middleware.mdx b/src/content/docs/en/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..507c3ac06a
--- /dev/null
+++ b/src/content/docs/en/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+![Elements of a middleware function call](/images/express-mw.png)
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/en/5x/starter/basic-routing.mdx b/src/content/docs/en/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..1d9ee9316e
--- /dev/null
+++ b/src/content/docs/en/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the [Hello world
+example](/en/starter/hello-world).
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/en/5x/starter/examples.mdx b/src/content/docs/en/5x/starter/examples.mdx
new file mode 100644
index 0000000000..69f410e908
--- /dev/null
+++ b/src/content/docs/en/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+This page contains list of examples using Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+
+This information refers to third-party sites, products, or modules that are not maintained by the
+Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+Expressjs project team.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/en/5x/starter/faq.md b/src/content/docs/en/5x/starter/faq.md
new file mode 100755
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/en/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/en/5x/starter/generator.mdx b/src/content/docs/en/5x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/en/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/en/5x/starter/hello-world.mdx b/src/content/docs/en/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/en/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/en/5x/starter/installing.mdx b/src/content/docs/en/5x/starter/installing.mdx
new file mode 100755
index 0000000000..f6dc8220d4
--- /dev/null
+++ b/src/content/docs/en/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 18 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/en/5x/starter/static-files.mdx b/src/content/docs/en/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..25009911ce
--- /dev/null
+++ b/src/content/docs/en/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, [use a reverse
+proxy](/en/advanced/best-practice-performance#use-a-reverse-proxy) cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/es/4x/advanced/developing-template-engines.md b/src/content/docs/es/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..39a63bd5b5
--- /dev/null
+++ b/src/content/docs/es/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Desarrollar motores de plantillas para Express
+description: Aprenda cómo desarrollar motores de plantillas personalizados para Express.js usando app.engine(), con ejemplos de creación e integración de su propia lógica de renderizado de plantillas.
+---
+
+Usa el método `app.engine(ext, callback)` para crear tu propio motor de plantillas. `ext` se refiere a la extensión del archivo, y `callback` es la función del motor de plantilla, que acepta los siguientes elementos como parámetros: la ubicación del archivo, el objeto de opciones y la función de devolución de llamada.
+
+El siguiente código es un ejemplo de implementación de un motor de plantillas muy simple para renderizar archivos `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Tu aplicación ahora será capaz de procesar archivos `.ntl`. Crea un archivo llamado `index.ntl` en el directorio `views` con el siguiente contenido.
+
+```pug
+#title#
+#message#
+```
+
+Luego, crea la siguiente ruta en tu aplicación.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Cuando hagas una solicitud a la página de inicio, `index.ntl` será renderizado como HTML.
diff --git a/src/content/docs/es/4x/guide/behind-proxies.mdx b/src/content/docs/es/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..76d786f141
--- /dev/null
+++ b/src/content/docs/es/4x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Expresar detrás de proxies
+description: Aprenda cómo configurar las aplicaciones Express.js para que funcionen correctamente detrás de los proxies inversos, incluyendo el uso de la configuración del proxy de confianza para manejar las direcciones IP del cliente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Cuando se ejecuta una aplicación Express detrás de un proxy inverso, algunas de las APIs Express pueden devolver valores diferentes de los esperados. Para ajustarse a esto, la configuración de la aplicación `trust proxy` puede utilizarse para exponer la información proporcionada por el proxy inverso en las APIs Express. El problema más común son las APIs expresas que exponen la dirección IP del cliente pueden mostrar una dirección IP interna del proxy inverso.
+
+<Alert type="info">
+
+Al configurar la configuración del `proxy de confianza`, es importante entender la configuración exacta del proxy inverso
+. Dado que esta configuración confiará en los valores proporcionados en la solicitud, es importante que
+la combinación de la configuración en Express coincida con cómo funciona el proxy inverso.
+
+</Alert>
+
+El ajuste de la aplicación `proxy de confianza` puede establecerse en uno de los valores listados en la siguiente tabla.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Escriba</th><th>Valor</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Si es `true`, la dirección IP del cliente se entiende como la entrada más a la izquierda en la cabecera `X-Forwarded-For`.
+
+Si es `false`, la aplicación se entiende como directamente frente al cliente y la dirección IP del cliente se deriva de `req.socket.remoteAddress`. Esta es la configuración por defecto.
+
+<Alert type="advertencia">
+Cuando se establece en `true`, es importante asegurarse de que el último proxy inverso en el que se confía es eliminar/sobrescribir todas las siguientes cabeceras HTTP: `X-Forwarded-For`, `X-Forwarded-Host`, y `X-Forwarded-Proto`, de lo contrario puede ser posible que el cliente proporcione cualquier valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>direcciones IP</td>
+<td markdown="1">
+Una dirección IP, subred, o un array de direcciones IP y subredes en las que confiar como un proxy inverso. La siguiente lista muestra los nombres de subred preconfigurados:
+
+- bucle atrás - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Puede establecer direcciones IP de cualquiera de las siguientes maneras:
+
+```js
+app.set('trust proxy', 'loopback'); // especificar una única subred
+app.set('trust proxy', 'loopback, 123.123.123.123'); // especificar una subred y una dirección
+app.et('trust proxy', 'loopback, linklocal, uniquelocal'); // especifica múltiples subredes como CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // especifica múltiples subredes como un array
+```
+
+Cuando se especifica, las direcciones IP o las subredes están excluidas del proceso de determinación de direcciones, y la dirección IP no confiable más cercana al servidor de aplicaciones se determina como la dirección IP del cliente. Esto funciona comprobando si `req.socket.remoteAddress` es de confianza. Si es así, entonces cada dirección en `X-Forwarded-For` se marca de derecha a izquierda hasta la primera dirección no confiable.
+
+</td>
+    </tr>
+    <tr>
+      <td>Número</td>
+<td markdown="1">
+Utilice la dirección que es como máximo el número de saltos `n` de la aplicación Express. `req.socket.remoteAddress` es la primera salida, y el resto son buscados en la cabecera `X-Forwarded-For` de derecha a izquierda. Un valor de `0` significa que la primera dirección no confiable sería `req.socket.remoteAddress`, es decir, no hay proxy inverso.
+
+<Alert type="advertencia">
+Al usar esta configuración, es importante asegurarse de que no hay múltiplos, rutas de longitud diferente a la aplicación Express tal que el cliente puede ser menor que el número de saltos configurados de lo contrario es posible que el cliente proporcione cualquier valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Función</td>
+<td markdown="1">
+Implementación de confianza personalizada.
+
+```js
+app.set('confiar en proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    return true; // Iders confiables
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Habilitar `proxy de confianza` tendrá el siguiente impacto:
+
+<ul>
+  <li markdown="1">
+    El valor de [req.hostname](/en/api#req.hostname) se deriva del valor establecido en la cabecera
+    `X-Forwarded-Host`, que puede ser definido por el cliente o por el proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` puede ser establecido por el proxy inverso para decirle a la aplicación si
+    es `https` o `http` o incluso un nombre inválido. Este valor se refleja en
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Los valores [req.ip](/en/api#req.ip) y [req.ips](/en/api#req.ips) son poblados según la
+    dirección del socket y la cabecera `X-Forwarded-For`, comenzando en la primera dirección no
+    confiable.
+  </li>
+</ul>
+
+La configuración `trust proxy` se implementa usando el paquete [proxy-addr](https://www.npmjs.com/package/proxy-addr). Para obtener más información, consulte su documentación.
diff --git a/src/content/docs/es/4x/guide/debugging.mdx b/src/content/docs/es/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..18a5f950b2
--- /dev/null
+++ b/src/content/docs/es/4x/guide/debugging.mdx
@@ -0,0 +1,123 @@
+---
+title: Depuración Express
+description: Aprenda cómo habilitar y utilizar los registros de depuración en aplicaciones Express.js configurando la variable de entorno DEBUG para solucionar problemas mejorados.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para ver todos los registros internos usados en Express, establece la variable de entorno `DEBUG` a
+`express:*` al ejecutar tu aplicación.
+
+```bash
+$ DEBUG=express:* nodo index.js
+```
+
+En Windows, utilice el comando correspondiente.
+
+```bash
+> $env:DEBUG = "express:*"; nodo index.js
+```
+
+Ejecutando este comando en la aplicación predeterminada generada por el [generador expreso](/en/starter/generator) imprime la siguiente salida:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Cuando se hace una solicitud a la aplicación, verá los registros especificados en el código Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Para ver los registros sólo desde la implementación del router, establece el valor de `DEBUG` a `express:router`. De la misma manera, para ver los registros sólo desde la implementación de la aplicación, establece el valor de `DEBUG` a `express:application`, y así sucesivamente.
+
+## Aplicaciones generadas por `express`
+
+Una aplicación generada por el comando `express` utiliza el módulo `debug` y su espacio de nombres de depuración está cubierto por el nombre de la aplicación.
+
+Por ejemplo, si generaste la aplicación con \`$ muestra expresa, puedes habilitar las declaraciones de depuración con el siguiente comando:
+
+```bash
+$ DEBUG=sample-app:* nodo ./bin/www
+```
+
+Puede especificar más de un espacio de nombres de depuración asignando una lista de nombres separados por comas:
+
+```bash
+$ DEBUG=http,mail,express:* nodo index.js
+```
+
+## Opciones avanzadas
+
+Cuando se ejecuta a través de Node.js, puede establecer algunas variables de entorno que cambiarán el comportamiento del registro de depuración:
+
+| Nombre              | Propósito                                                             |
+| ------------------- | --------------------------------------------------------------------- |
+| `DEBUG`             | Habilita o deshabilita espacios de nombres específicos de depuración. |
+| `DEBUG_COLORS`      | Usar o no colores en la salida de depuración.                         |
+| `DEBUG_DEPTH`       | Profundidad de inspección de objetos.                                 |
+| `DEBUG_FD`          | Descriptor de archivo en el que escribir salida de depuración.        |
+| `DEBUG_SHOW_HIDDEN` | Muestra propiedades ocultas en los objetos esperados.                 |
+
+<Alert type="info">
+
+Las variables de entorno que empiezan con `DEBUG_` acaban siendo convertidas en un objeto Options
+que se usa con formateadores `%o`/`%O. Vea la documentación de Node.js para [`util.inspect()\`](https://nodejs.org/api/util#util_util_inspect_object_options) para la lista completa
+.
+
+</Alert>
diff --git a/src/content/docs/es/4x/guide/error-handling.mdx b/src/content/docs/es/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..c899c51198
--- /dev/null
+++ b/src/content/docs/es/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Manejo de errores
+description: Descargue cómo Express.js maneja errores en código sincrónico y asíncrono, y aprenda a implementar middleware de manejo de errores personalizado para sus aplicaciones.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express viene con un manejador de error predeterminado
+, así que no necesitas escribir el tuyo propio para empezar.
+
+## Errores de captura
+
+Es importante asegurarse de que Express capture todos los errores que ocurren mientras
+ejecuta los manejadores de rutas y el middleware.
+
+Los errores que ocurren en el código sincrónico dentro de los manejadores de rutas y middleware
+no requieren trabajo extra. Si el código sincrónico arroja un error, entonces Express hará
+capturarlo y procesarlo. Por ejemplo:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express capturará esto por su cuenta.
+});
+```
+
+Para los errores devueltos por funciones asincrónicas invocadas por los manejadores de rutas
+y middleware, debes pasarlos a la función `next()`, donde Express las capturará y procesará
+. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pasar los errores a Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+A partir de Express 5, manejadores de rutas y middleware que devuelven una Promise
+llamará automáticamente a `next(value)` cuando rechacen o lancen un error.
+Por ejemplo:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Si `getUserById` arroja un error o rechaza, `next` será llamado con
+el error arrojado o el valor rechazado. Si no se proporciona ningún valor rechazado, `next`
+será llamado con un objeto de Error predeterminado proporcionado por el enrutador Express.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+Si la devolución de llamada en una secuencia no proporciona datos, sólo errores, puede simplificar
+este código de la siguiente manera:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+En el ejemplo anterior, `next` es proporcionado como el callback para `fs.writeFile`,
+que es llamado con o sin errores. Si no hay error, se ejecuta el segundo manejador
+, de lo contrario Express catches y procesa el error.
+
+Debe capturar errores que ocurren en código asíncrono invocado por manejadores de ruta o un middleware
+y pasarlos a Express para su procesamiento. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+El ejemplo anterior utiliza un bloque `try...catch` para capturar errores en el código asincrónico
+y pasarlos a Express. Si el bloque `try...catch`
+fuera omitido, Express no capturaría el error ya que no es parte del código de manejador
+sincrónico.
+
+Usa promesas para evitar la sobrecarga del bloque "intentar...atrapar" o al usar funciones
+que devuelven promesas. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Los errores se pasarán a Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+También podría utilizar una cadena de manejadores para depender de la captura de errores sincrónicos
+, reduciendo el código asincrónico a algo trivial. Por ejemplo:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.ata = data;
+      siguiente(err);
+    });
+  },
+  function (req, res) {
+    res.ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+El ejemplo anterior tiene un par de declaraciones triviales de la llamada `readFile`
+. Si `readFile` causa un error, entonces pasa el error a Express, de lo contrario
+regresa rápidamente al mundo del manejo sincrónico de errores en el siguiente manejador
+en la cadena. Luego, el ejemplo anterior intenta procesar los datos. Si esto falla, entonces el gestor de errores sincrónico
+lo capturará. Si hubiera hecho este procesamiento dentro de
+el callback `readFile`, entonces la aplicación podría salir y los manejadores de error Express
+no se ejecutarían.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## El gestor de errores por defecto
+
+Express viene con un gestor de errores integrado que se encarga de cualquier error que pueda encontrarse en la aplicación. Esta función middleware por defecto se añade al final de la pila de funciones de middleware.
+
+Si pasas un error a `next()` y no lo gestionas en un controlador
+error personalizado, será manejado por el gestor de errores integrado; el error será
+escrito al cliente con el stack trace. El stack trace no está incluido
+en el entorno de producción.
+
+<Alert type="info">
+
+Establece la variable de entorno `NODE_ENV` a `production`, para ejecutar la aplicación en el modo de producción.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- El `res.statusCode` se establece desde `err.status` (o `err.statusCode`). Si
+  este valor está fuera del rango 4xx o 5xx, se establecerá a 500.
+- El `res.statusMessage` se establece de acuerdo al código de estado.
+- El cuerpo será el HTML del mensaje del código de estado cuando en el entorno
+  de producción, de lo contrario será `err.stack`.
+- Cualquier cabecera especificada en un objeto `err.headers`.
+
+Si llama a `next()` con un error después de haber comenzado a escribir la respuesta
+(por ejemplo, si encuentras un error al transmitir la respuesta
+al cliente), el gestor de errores Express por defecto cierra la conexión
+y falla la solicitud.
+
+Así que cuando añada un manejador de errores personalizado, debe delegar a
+el manejador de errores predeterminado Express cuando los encabezados
+ya han sido enviados al cliente:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Tenga en cuenta que el manejador de errores por defecto puede activarse si llama a `next()` con un error
+en su código más de una vez, incluso si el middleware está configurado para manejar errores personalizados.
+
+Otro middleware de manejo de error se puede encontrar en [Express middleware](/en/resources/middleware).
+
+## Manejadores de errores escritos
+
+Define las funciones de middleware de la misma manera que otras funciones de middleware,
+excepto las funciones de manejo de errores tienen cuatro argumentos en lugar de tres:
+`(err, req, res, next)`. Por ejemplo:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Usted define middleware manejado por errores últimamente, después de otras `app.use()` y llamadas de rutas; por ejemplo:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extendido: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // lógica
+});
+```
+
+Las respuestas desde dentro de una función middleware pueden estar en cualquier formato, como una página de error HTML, un mensaje simple, o una cadena JSON.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. Por ejemplo, para definir un manejador de errores
+para las solicitudes realizadas usando `XHR` y las que no tienen:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extendido: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+En este ejemplo, el genérico `logErrors` podría escribir una solicitud y
+información de error a `stderr`, por ejemplo:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+También en este ejemplo, `clientErrorHandler` se define de la siguiente manera; en este caso, el error se pasa explícitamente al siguiente.
+
+Tenga en cuenta que cuando _no_ llama "siguiente" en una función de manejo de errores, usted es responsable de escribir (y terminar) la respuesta. De lo contrario, esas solicitudes se "colgarán" y no serán elegibles para la recolección de basura.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementa la función "catch-all" `errorHandler` como sigue (por ejemplo):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Si tiene un manejador de ruta con múltiples funciones de callback, puede utilizar el parámetro `route` para saltar al siguiente manejador de ruta. Por ejemplo:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // continúa manejando esta solicitud
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+En este ejemplo, el manejador `getPaidContent` se omitirá pero cualquier manejador restante en `app` para `/a_route_behind_paywall` continuaría siendo ejecutado.
+
+<Alert type="info">
+
+Las llamadas a `next()` y `next(err)` indican que el controlador actual está completo y en qué estado.
+`next(err)` omitirá todos los manejadores restantes en la cadena, excepto aquellos que están configurados a
+errores de manejo como se describe arriba.
+
+</Alert>
diff --git a/src/content/docs/es/4x/guide/overriding-express-api.md b/src/content/docs/es/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..9be44e70df
--- /dev/null
+++ b/src/content/docs/es/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Reemplazar la API Express
+description: Descubra cómo personalizar y extender la API de Express.js reemplazando métodos y propiedades en los objetos de solicitud y respuesta usando prototipos.
+---
+
+La API Express consiste en varios métodos y propiedades sobre los objetos de solicitud y respuesta. Estos son heredados por prototipo. Hay dos puntos de extensión para la API Express:
+
+1. Los prototipos globales en `express.request` y `express.response`.
+2. prototipos específicos de la aplicación en `app.request` y `app.response`.
+
+Alterar los prototipos globales afectará a todas las aplicaciones cargadas Express en el mismo proceso. Si se desea, las alteraciones pueden hacerse específicas de la aplicación sólo modificando los prototipos específicos de la aplicación después de crear una nueva aplicación.
+
+## Métodos
+
+Puede anular la firma y el comportamiento de los métodos existentes con los suyos, asignando una función personalizada.
+
+A continuación se muestra un ejemplo de anular el comportamiento de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+La implementación anterior cambia completamente la firma original de `res.sendStatus`. Ahora acepta un código de estado, tipo de codificación, y el mensaje que se enviará al cliente.
+
+El método sobreescrito ahora puede utilizarse de esta manera:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Propiedades
+
+Las propiedades en la API Express son tamaño:
+
+1. Propiedades asignadas (ej: `req.baseUrl`, `req.originalUrl`)
+2. Definido como getters (ej: `req.secure`, `req.ip`)
+
+Dado que las propiedades de la categoría 1 se asignan dinámicamente a los objetos `request` y `response` en el contexto del ciclo actual de petición-respuesta, su comportamiento no puede ser anulado.
+
+Las propiedades de la categoría 2 se pueden sobrescribir usando la API Express de extensiones API.
+
+El siguiente código reescribe cómo se derivará el valor de `req.ip`. Ahora, simplemente devuelve el valor de la cabecera de petición `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototipo
+
+Para proporcionar la API Express, los objetos de solicitud / respuesta pasados a Express (a través de `app(req, res)`, por ejemplo) necesita heredar de la misma cadena prototipo. Por defecto, esto es `http.IncomingRequest.prototype` para la solicitud y `http.ServerResponse.prototype` para la respuesta.
+
+A menos que sea necesario, se recomienda que esto se haga únicamente a nivel de aplicación, en lugar de a nivel global. Además, tenga cuidado de que el prototipo que se está utilizando coincida con la funcionalidad lo más cerca posible de los prototipos predeterminados.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/es/4x/guide/routing.mdx b/src/content/docs/es/4x/guide/routing.mdx
new file mode 100644
index 0000000000..a57c73637f
--- /dev/null
+++ b/src/content/docs/es/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Ruta
+description: Aprenda cómo definir y usar rutas en aplicaciones Express.js, incluyendo métodos de ruta, rutas de ruta, parámetros, y usando Router para rutas modulares.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ se refiere a cómo responden los extremos (URIs) de una aplicación a las peticiones del cliente.
+Para una introducción al enrutamiento, consulte [Enrutamiento básico](/en/starter/basic-routing).
+
+Define enrutamiento usando métodos del objeto Express `app` que corresponden a métodos HTTP;
+por ejemplo, `app. et()` para manejar solicitudes GET y `app.post` para manejar solicitudes POST. Para una lista completa,
+vea [app.METHOD](/en/5x/api#app.METHOD). También puedes usar [app.all()](/en/5x/api#app.all) para manejar todos los métodos HTTP y [app. se()](/en/5x/api#app.use) a
+especificar middleware como función de callback (Ver [Usando middleware](/en/guide/using-middleware) para más detalles).
+
+Estos métodos de enrutamiento especifican una función de callback (a veces llamada "funciones manejadoras") llamada cuando la aplicación recibe una petición a la ruta especificada (endpoint) y el método HTTP. En otras palabras, la aplicación "escucha" para peticiones que coinciden con el/los método(s) especificado(s), y cuando detecta una coincidencia, llama a la función de callback especificada.
+
+De hecho, los métodos de enrutamiento pueden tener más de una función de callback como argumentos.
+Con múltiples funciones de callback, es importante proporcionar `next` como un argumento a la función de callback y luego llamar `next()` dentro del cuerpo de la función para desactivar el control
+al siguiente callback.
+
+El siguiente código es un ejemplo de una ruta muy básica.
+
+```js
+const express = require('express');
+const app = express();
+
+// responden con "Hola mundo" cuando se hace una solicitud GET a la página de inicio
+aplicación.et('/', (req, res) => {
+  res.send('hola mundo');
+});
+```
+
+## Métodos de ruta
+
+Un método de ruta se deriva de uno de los métodos HTTP y se adjunta a una instancia de la clase `express`.
+
+El siguiente código es un ejemplo de rutas definidas para los métodos `GET` y `POST` a la raíz de la aplicación.
+
+```js
+// Ruta del método GET
+app.get('/', (req, res) => {
+  res.end('GET request to the homepage');
+});
+
+// método POST route
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express soporta métodos que corresponden a todos los métodos de petición HTTP: `get`, `post`, y así sucesivamente.
+Para una lista completa, vea [app.METHOD](/en/5x/api#app.METHOD).
+
+Hay un método especial de enrutamiento, `app.all()`, usado para cargar funciones de middleware en una ruta para _all_ métodos de petición HTTP. Por ejemplo, el siguiente manejador se ejecuta para peticiones a la ruta `"/secret"` ya sea usando `GET`, `POST`, `PUT`, `DELETE`, o cualquier otro método de solicitud HTTP soportado en el [módulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Acceder a la sección secreta ...');
+  next(); // pasar el control al siguiente manejador
+});
+```
+
+## Rutas de ruta
+
+Las rutas de ruta, en combinación con un método de solicitud, definen los extremos en los que se pueden realizar las solicitudes. Las rutas pueden ser cadenas, patrones de cadenas o expresiones regulares.
+
+<Alert type="alerta">
+
+En expreso 5, los caracteres `? , `+`, `\*`, `[]`, y `()\` son manejados de manera diferente que en la versión
+4, por favor revisa la [guía de migración](/en/guide/migrating-5#path-syntax) para más información.
+
+</Alert>
+
+<Alert type="alerta">
+
+En expreso 4, los caracteres de expresión regular como `$` necesitan ser escapados con un `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express usa [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) para emparejar las rutas de la ruta
+; vea la documentación de la ruta a regexp para todas las posibilidades de definir rutas de la ruta.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Las cadenas de consulta no son parte de la ruta de la ruta.</Alert>
+
+### Rutas de ruta basadas en cadenas
+
+Esta ruta coincidirá con las peticiones a la ruta raíz, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Esta ruta coincidirá con las peticiones a `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Esta ruta de ruta coincidirá con peticiones a `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Rutas de ruta basadas en patrones de cadenas
+
+<Alert type="alerta">
+
+Los patrones de cadenas en Express 5 ya no funcionan. Consulte la guía de migración
+&#x20;para obtener más información.
+
+</Alert>
+
+Esta ruta de ruta coincidirá con `acd` y `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Esta ruta coincidirá con `abcd`, `abbcd`, `abbbcd`, y así sucesivamente.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Esta ruta de ruta coincidirá con `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, y así sucesivamente.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Esta ruta coincidirá con `/abe` y `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Rutas de ruta basadas en expresiones regulares
+
+Esta ruta coincidirá con cualquier cosa con una "a".
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Esta ruta coincidirá con `butterfly` y `dragonfly`, pero no `butterflyman`, `dragonflyman`, y así sucesivamente.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parámetros de ruta
+
+Los parámetros de ruta se llaman segmentos de URL que se utilizan para capturar los valores especificados en su posición en la URL. Los valores capturados son poblados en el objeto `req.params`, con el nombre del parámetro de ruta especificado en la ruta como sus claves respectivas.
+
+```
+Ruta de ruta: /users/:userId/books/:bookId
+URL de petición: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Para definir rutas con parámetros de ruta, simplemente especifique los parámetros de ruta en la ruta como se muestra a continuación.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alerta">
+
+El nombre de los parámetros de la ruta debe estar compuesto de "caracteres de palabra" ([A-Za-z0-9_]).
+
+</Alert>
+
+Dado que los guiones (`-`) y el punto (`.`) se interpretan literalmente, pueden ser utilizados junto con parámetros de ruta para propósitos útiles.
+
+```
+Ruta de ruta: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Ruta de ruta: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alerta">
+
+En expreso 5, no se admiten caracteres de expresión regular en rutas para más información, por favor
+consulte la [guía de migración](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Para tener más control sobre la cadena exacta que puede coincidir con un parámetro de ruta, puede añadir una expresión regular entre paréntesis (`()`):
+
+```
+Ruta de ruta: /user/:userId(\d+)
+URL de Solicitud: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="advertencia">
+
+Debido a que la expresión regular es generalmente parte de una cadena literal, Asegúrate de escapar cualquier `\`
+caracteres con una barra inversa adicional, por ejemplo `\d+`.
+
+</Alert>
+
+<Alert type="advertencia">
+En Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">el carácter `*` en expresiones regulares no se interpreta de la forma habitual</a>. Como un workaround, usa `{0,}` en lugar de `*`. Es probable que esto se arregle en Express 5.
+</Alert>
+
+## Manejadores de rutas
+
+Puedes proporcionar múltiples funciones de callback que se comportan como [middleware](/en/guide/using-middleware) para gestionar una solicitud. La única excepción es que estos callbacks podrían invocar a `next('route')` para evitar las llamadas restantes de ruta. Se puede utilizar este mecanismo para imponer condiciones previas a una ruta, luego pasar el control a las rutas posteriores si no hay razón para proceder con la ruta actual.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`Usuario ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Controlador especial para el usuario ID 0');
+});
+```
+
+En este ejemplo:
+
+- `GET /user/5` → manejado por primera ruta → envía "Usuario 5"
+- `GET /user/0` → primera ruta llama a `next('ruta')`, saltando a la siguiente ruta `/user/:id`
+
+Los manejadores de rutas pueden ser en forma de una función, un array de funciones o combinaciones de ambos, como se muestra en los siguientes ejemplos.
+
+Una única función de callback puede manejar una ruta. Por ejemplo:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hola de A!');
+});
+```
+
+Más de una función de callback puede manejar una ruta (asegúrese de especificar el objeto `siguiente`). Por ejemplo:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    consola.og('la respuesta será enviada por la siguiente función . .');
+    siguiente();
+  },
+  (req, res) => {
+    res.end('Hola de B!');
+  }
+);
+```
+
+Una matriz de funciones de callback puede manejar una ruta. Por ejemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  consola.og('CB0');
+  siguiente();
+};
+
+const cb1 = function (req, res, next) {
+  consola.og('CB1');
+  siguiente();
+};
+
+const cb2 = function (req, res) {
+  res.end('Hola de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Una combinación de funciones independientes y arreglos de funciones puede manejar una ruta. Por ejemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  consola.og('CB0');
+  siguiente();
+};
+
+const cb1 = function (req, res, next) {
+  consola.og('CB1');
+  siguiente();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    consola.og('la respuesta será enviada por la siguiente función . .');
+    siguiente();
+  },
+  (req, res) => {
+    res.end('Hola de D!');
+  }
+);
+```
+
+## Métodos de respuesta
+
+Los métodos en el objeto de respuesta (`res`) en la siguiente tabla pueden enviar una respuesta al cliente y terminar el ciclo de solicitud y respuesta. Si ninguno de estos métodos es llamado desde un gestor de rutas, la petición del cliente se dejará colgada.
+
+| Método                                        | Descripción                                                                                                 |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Solicitar un archivo para ser descargado.                                                                   |
+| [res.end()](/en/5x/api#res.end)               | Terminar el proceso de respuesta.                                                                           |
+| [res.json()](/en/5x/api#res.json)             | Enviar una respuesta JSON.                                                                                  |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envía una respuesta JSON con soporte JSONP.                                                                 |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirigir una solicitud.                                                                                    |
+| [res.render()](/en/5x/api#res.render)         | Procesar una plantilla de vista.                                                                            |
+| [res.send()](/en/5x/api#res.send)             | Enviar una respuesta de varios tipos.                                                                       |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Enviar un archivo como un flujo de octet.                                                                   |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Establece el código de estado de respuesta y envía su representación de cadena como el cuerpo de respuesta. |
+
+## app.route()
+
+Puede crear manejadores de rutas encadenables para una ruta usando `app.route()`.
+Debido a que la ruta se especifica en una única ubicación, la creación de rutas modulares es útil, al igual que la reducción de redundancia y tipografías. Para más información sobre rutas, vea: [documentación Router() ](/en/5x/api#router).
+
+Aquí hay un ejemplo de manejadores encadenados de rutas que se definen usando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Obtén un libro al azar');
+  })
+  .ost((req, res) => {
+    res.send('Agregar un libro');
+  })
+  .ut((req, res) => {
+    res.send('Actualizar el libro');
+  });
+```
+
+## express.Router
+
+Utilice la clase `express.Router` para crear manejadores modulares de rutas. Una instancia de `Router` es un sistema completo de middleware y enrutamiento; por esta razón, a menudo se le denomina "mini-app".
+
+El siguiente ejemplo crea un router como módulo, carga una función de middleware en él, define algunas rutas y monta el módulo del router en una ruta de la aplicación principal.
+
+Crea un archivo de enrutador llamado `birds.js` en el directorio de la aplicación, con el siguiente contenido:
+
+```js
+const express = require('express');
+const router = express.outer();
+
+// middleware que es específico para este router
+const timeLog = (req, res, next) => {
+  consola.og('Hora: ', Date.now());
+  siguiente();
+};
+enrutador.se(timeLog);
+
+// define la ruta de la página de inicio
+router.get('/', (req, res) => {
+  res.end('Página de inicio de aves');
+});
+// define la ruta
+router.et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Luego, cargue el módulo de enrutador en la aplicación:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+La aplicación ahora será capaz de manejar solicitudes a `/birds` y `/birds/about`, así como llamar a la función de middleware `timeLog` que es específica de la ruta.
+
+Pero si la ruta padre `/birds` tiene parámetros de ruta, no será accesible por defecto desde las subrutas. Para hacerlo accesible, necesitarás pasar la opción `mergeParams` al constructor de Router [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/es/4x/guide/using-middleware.mdx b/src/content/docs/es/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..a6852c622b
--- /dev/null
+++ b/src/content/docs/es/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usando middleware
+description: Aprenda cómo usar middleware en aplicaciones Express.js, incluyendo middleware de nivel de aplicación y router, manejo de errores, e integración de middleware de terceros.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express es un framework web de enrutamiento y middleware que tiene una funcionalidad mínima propia: Una aplicación Express es esencialmente una serie de llamadas a funciones de middleware.
+
+Las funciones _Middleware_ son funciones que tienen acceso al [objeto de solicitud](/en/5x/api#req) (`req`), el [objeto de respuesta](/en/5x/api#res) (`res`), y la siguiente función de middleware en el ciclo de solicitud y respuesta de la aplicación. La siguiente función middleware se denota comúnmente por una variable llamada `next`.
+
+Las funciones de Middleware pueden realizar las siguientes tareas:
+
+- Ejecutar cualquier código.
+- Realizar cambios en la solicitud y en los objetos de respuesta.
+- Terminar el ciclo de solicitud de respuesta.
+- Llame a la siguiente función de middleware en la pila.
+
+Si la función actual de middleware no termina el ciclo de solicitud de respuesta, debe llamar a `next()` para pasar el control a la siguiente función de middleware. De lo contrario, la solicitud quedará colgada.
+
+Una aplicación Express puede utilizar los siguientes tipos de middleware:
+
+- [Middleware de nivel de aplicación](#middleware.application)
+- [Middleware de nivel superior](#middleware.router)
+- [Middleware de manejo de errores](#middleware.error-handling)
+- [Middleware incorporado](#middleware.built-in)
+- [Middleware de terceros](#middleware.third-party)
+
+Puede cargar middleware de nivel de aplicación y de enrutador con una ruta de montaje opcional.
+También puede cargar una serie de funciones de middleware juntas, lo que crea un substack del sistema de middleware en un punto de montaje.
+
+## Middleware de nivel de aplicación
+
+Vincular middleware a una instancia del [objeto de aplicación](/en/5x/api#app) usando `app.use()` y `app. ETHOD()` funciona, donde `METHOD` es el método HTTP de la petición que la función middleware maneja (como GET, PUT o POST) en minúsculas.
+
+Este ejemplo muestra una función de middleware sin ruta de montaje. La función se ejecuta cada vez que la aplicación recibe una solicitud.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Este ejemplo muestra una función middleware montada en la ruta `/user/:id`. La función se ejecuta para cualquier tipo de petición
+HTTP en la ruta `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Este ejemplo muestra una ruta y su función manejadora (middleware system). La función maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USUARIO');
+});
+```
+
+He aquí un ejemplo de carga de una serie de funciones de middleware en un punto de montaje, con una ruta de montaje.
+Ilustra un substack de middleware que imprime la información de la petición para cualquier tipo de petición HTTP a la ruta `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    consola.og('Tipo de solicitud:', req.method);
+    siguiente();
+  }
+);
+```
+
+Los manejadores de rutas le permiten definir múltiples rutas para una ruta. El siguiente ejemplo define dos rutas para peticiones GET a la ruta `/user/:id`. La segunda ruta no causará ningún problema, pero nunca se llamará porque la primera ruta termina el ciclo de solicitud de respuesta.
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.arams.id);
+    siguiente();
+  },
+  (req, res, next) => {
+    res.end('Información de usuario');
+  }
+);
+
+// manejador para la ruta /user/:id, que imprime el ID de usuario
+app.et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Para omitir el resto de las funciones de middleware desde una pila de middleware de router, llame a `next('ruta')` para pasar el control a la siguiente ruta.
+
+<Alert type="info">
+
+`next('ruta')` solo funcionará en funciones de middleware que fueron cargadas usando las funciones
+`app.METHOD()` o `router.METHOD()`.
+
+</Alert>
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // si el ID de usuario es 0, saltar a la siguiente ruta
+    si (req. aramas. d === '0') siguiente('ruta');
+    // de lo contrario pasa el control a la siguiente función de middleware en esta pila
+    si no siguiente();
+  },
+  (req, res, next) => {
+    // envía una respuesta regular
+    res. end('regular');
+  }
+);
+
+// manejador para la ruta /user/:id, que envía una respuesta especial
+app. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware también puede ser declarado en una matriz para reusabilidad.
+
+Este ejemplo muestra una matriz con un substack de middleware que maneja peticiones GET en la ruta `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  siguiente();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('Información de usuario');
+});
+```
+
+## Middleware de nivel remoto
+
+El middleware Router-level funciona de la misma manera que el middleware a nivel de aplicación, excepto que está vinculado a una instancia de `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Carga el middleware a nivel de enrutador usando las funciones `router.use()` y `router.METHOD()`.
+
+El siguiente código de ejemplo replica el sistema middleware que se muestra arriba para el middleware de nivel de aplicación, mediante el uso de router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// una función de middleware sin ruta de montaje. Este código se ejecuta para cada petición al router
+. se((req, res, next) => {
+  console.log('Hora:', Date. ow());
+  siguiente();
+});
+
+// un substack de middleware muestra información de petición para cualquier tipo de petición HTTP al router /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('URL de solicitud:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    consola. og('Tipo de solicitud:', req. ethod);
+    next();
+  }
+);
+
+// un substack de middleware que maneja las solicitudes GET al router /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // si el ID de usuario es 0, saltar al siguiente router
+    if (req. aramas. d === '0') siguiente('ruta');
+    // de lo contrario pasar el control a la siguiente función de middleware en esta pila
+    más siguiente();
+  },
+  (req, res, next) => {
+    // renderiza una página regular
+    res. ender('regular');
+  }
+);
+
+// manejador para la ruta /user/:id, que renderiza una página especial
+router. et('/user/:id', (req, res, next) => {
+  consola. og(req.params.id);
+  res.render('special');
+});
+
+// monta el router en la aplicación
+app.use('/', router);
+```
+
+Para omitir el resto de las funciones de middleware del enrutador, llama a `next('router')`
+para pasar el control de vuelta fuera de la instancia del enrutador.
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// predice el enrutador con un cheque y rescinda cuando sea necesario enrutador
+. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa el enrutador y 401 cualquier cosa que caiga a través de
+aplicación. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Middleware de manejo de errores
+
+<Alert type="alerta">
+
+Middleware manejado por errores siempre toma _four_ argumentos. Debe proporcionar cuatro argumentos para
+identificarlo como una función de middleware que maneja errores. Incluso si no necesitas usar el objeto `next`
+, debes especificarlo para mantener la firma. De lo contrario, el objeto `siguiente` será
+interpretado como middleware regular y fallará al manejar errores.
+
+</Alert>
+
+Define las funciones de middleware de la misma manera que otras funciones de middleware, excepto con cuatro argumentos en lugar de tres, específicamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para más detalles sobre el middleware de manejo de errores, vea: [Gestión de errores](/en/guide/error-handling).
+
+## Middleware incorporado
+
+A partir de la versión 4.x, Express ya no depende de [Connect](https://github.com/senchalabs/connect). Las funciones
+del middleware que anteriormente estaban incluidas con Express están ahora en módulos separados; vea [la lista de funciones de middleware](https://github.com/senchalabs/connect#middleware).
+
+Express tiene las siguientes funciones de middleware incorporadas:
+
+- [express.static](/en/5x/api#express.static) sirve activos estáticos como archivos HTML, imágenes, etc.
+- [express.json](/en/5x/api#express.json) analiza las solicitudes entrantes con cargas útiles JSON. **NOTA: Disponible con Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analiza las solicitudes entrantes con payloads codificados por URL. **NOTA: Disponible con Express 4.16.0+**
+
+## Middleware de terceros
+
+Utilice middleware de terceros para añadir funcionalidad a aplicaciones Express.
+
+Instale el módulo Node.js para la funcionalidad requerida, luego guárdelo en su aplicación a nivel de aplicación o a nivel de enrutador.
+
+El siguiente ejemplo ilustra la instalación y carga de la función middleware `cookie-parser`.
+
+```bash
+$ npm instalar cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cargar el middleware de análisis de cookies
+app.use(cookieParser());
+```
+
+Para una lista parcial de funciones de middleware de terceros que se utilizan comúnmente con Express, vea: [Middleware de terceros](../resources/middleware).
diff --git a/src/content/docs/es/4x/guide/using-template-engines.mdx b/src/content/docs/es/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..49818704ce
--- /dev/null
+++ b/src/content/docs/es/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utilizando motores de plantillas con Express
+description: Descubra cómo integrar y utilizar motores de plantillas como Pug, Handlebars y EJS con Express.js para renderizar páginas HTML dinámicas eficientemente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un _template engine_ le permite usar plantillas estáticas en su aplicación. En tiempo de ejecución, el motor de plantillas reemplaza variables
+en un archivo de plantilla con valores reales. y transforma la plantilla en un archivo HTML enviado al cliente.
+Este enfoque facilita el diseño de una página HTML.
+
+El [generador de aplicaciones Express](/en/starter/generator) utiliza [Pug](https://pugjs.org/api/getting-started.html) como predeterminado, pero también soporta [Handlebars](https://www.npmjs.com/package/handlebars), y [EJS](https://www.npmjs.com/package/ejs), entre otros.
+
+Para renderizar archivos de plantilla, establezca las siguientes [propiedades de configuración de aplicación](/en/4x/api#app.set), en el `app.js` por defecto creado por el generador:
+
+- `vistas`, el directorio donde están ubicados los archivos de plantilla. Ej: `app.set('vistas', './views')`.
+  Esto por defecto es el directorio `views` en el directorio raíz de la aplicación.
+- `ver engine`, el motor de plantillas a usar. Por ejemplo, para usar el motor de plantillas Pug: `app.set('view engine', 'pug')`.
+
+A continuación, instale el correspondiente paquete npm del motor de plantillas; por ejemplo para instalar Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alerta">
+Motores de plantillas compatibles con Expresiones, tales como Pug exportar una función llamada `__express(filePath, options, callback)`,
+que `res.render()` llama para renderizar el código de plantilla.
+
+Algunos motores de plantillas no siguen esta convención. La biblioteca [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+sigue esta convención mapeando todos los motores de plantillas populares de Node.js, y por lo tanto funciona perfectamente dentro de Express.
+
+</Alert>
+
+Después de que el motor de vista esté definido, no tiene que especificar el motor o cargar el módulo de motor de plantillas en su aplicación;
+Express carga el módulo internamente, por ejemplo:
+
+```js
+app.set('ver motor', 'pug');
+```
+
+Luego, crea un archivo de plantilla Pug llamado `index.pug` en el directorio `views`, con el siguiente contenido:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Crea una ruta para representar el archivo `index.pug`. Si la propiedad `view engine` no está definida,
+debe especificar la extensión del archivo `view`. De lo contrario, puede omitirlo.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: '¡Hola!' });
+});
+```
+
+Cuando hagas una solicitud a la página de inicio, el archivo `index.pug` será renderizado como HTML.
+
+La caché del motor de vistas no almacena en caché el contenido de la salida de la plantilla, sólo la misma plantilla subyacente. La vista todavía se vuelve a procesar con cada petición incluso cuando la caché está encendida.
diff --git a/src/content/docs/es/4x/guide/writing-middleware.mdx b/src/content/docs/es/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..31b67b8555
--- /dev/null
+++ b/src/content/docs/es/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Escribiendo middleware para uso en aplicaciones Express
+description: Aprenda cómo escribir funciones personalizadas de middleware para aplicaciones Express.js, incluyendo ejemplos y mejores prácticas para mejorar la gestión de peticiones y respuestas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Las funciones _Middleware_ son funciones que tienen acceso al [objeto de solicitud](/en/5x/api#req) (`req`), el [objeto de respuesta](/en/5x/api#res) (`res`), y la función `next` en el ciclo de solicitud y respuesta de la aplicación. La función `siguiente` es una función en el router Express que, cuando se invoca, ejecuta el middleware sucediendo al middleware actual.
+
+Las funciones de Middleware pueden realizar las siguientes tareas:
+
+- Ejecutar cualquier código.
+- Realizar cambios en la solicitud y en los objetos de respuesta.
+- Terminar el ciclo de solicitud de respuesta.
+- Llama al siguiente middleware en la pila.
+
+Si la función actual de middleware no termina el ciclo de solicitud de respuesta, debe llamar a `next()` para pasar el control a la siguiente función de middleware. De lo contrario, la solicitud quedará colgada.
+
+La siguiente figura muestra los elementos de una llamada a una función de middleware:
+
+<div class="rascacielos">
+<table id="higuera-mw">
+<tr>
+<td id="mw-figur-imgcell">
+<img src="/images/express-mw.png" alt="Elementos de una llamada a función middleware" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">método HTTP para el cual se aplica la función middleware.</div>
+
+<div class="callout" id="callout2">
+  Ruta (ruta) para la que se aplica la función middleware.
+</div>
+
+<div class="callout" id="callout3">
+  La función Middleware.
+</div>
+
+<div class="callout" id="callout4">
+  Argumento de llamada a la función middleware, llamado "siguiente" por convención.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">argumento</a> de respuesta a la función de middleware, llamada "res"
+  por convención .
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">solicita un argumento</a> a la función de middleware, llamado "req" por convención.</div>
+</td>
+</tr>
+</table>
+</div>
+
+A partir de Express 5, las funciones de middleware que devuelven una Promise llamarán `next(value)` cuando rechacen o lancen un error. `next` será llamado con el valor rechazado o con el error arrojado.
+
+## Ejemplo
+
+He aquí un ejemplo de una simple aplicación "Hola Mundo" Express.
+El resto de este artículo definirá y añadirá tres funciones de middleware a la aplicación:
+una llamada `myLogger` que imprime un simple mensaje de registro, uno llamado `requestTime` que
+muestra la marca de tiempo de la petición HTTP, y uno llamado `validateCookies` que valida las cookies entrantes.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('¡Hola Mundo!');
+});
+
+app.listen(3000);
+```
+
+### Función Middleware myLogger
+
+Aquí hay un ejemplo simple de una función middleware llamada "myLogger". Esta función solo imprime
+"LOGGED" cuando una solicitud a la aplicación pasa a través de ella. La función middleware está asignada a una variable
+llamada `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alerta">
+
+Tenga en cuenta la llamada anterior a `next()`. Llamar a esta función invoca la siguiente función de middleware en
+la aplicación. La función `next()` no es parte del Nodo. s o Express API, pero es el tercer argumento
+que se pasa a la función middleware. La función `next()` podría ser nombrada cualquier cosa,
+pero por convención siempre se llama "siguiente". Para evitar la confusión, utilice siempre esta convención.
+
+</Alert>
+
+Para cargar la función middleware, llama a `app.use()`, especificando la función middleware.
+Por ejemplo, el siguiente código carga la función middleware `myLogger` antes de la ruta a la ruta raíz (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  consola.og('LOGGED');
+  siguiente();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('¡Hola Mundo!');
+});
+
+app.listen(3000);
+```
+
+Cada vez que la aplicación recibe una solicitud, imprime el mensaje "LOGGED" en el terminal.
+
+El orden de carga de middleware es importante: las funciones de middleware que se cargan primero también se ejecutan primero.
+
+Si `myLogger` es cargado después de la ruta a la ruta raíz, la solicitud nunca llega a ella y la aplicación no imprime "LOGGED", porque el manejador de rutas de la ruta raíz termina el ciclo de solicitud de respuesta.
+
+La función Middleware `myLogger` simplemente imprime un mensaje, luego pasa la solicitud a la siguiente función de middleware en la pila llamando a la función `next()`.
+
+### Tiempo de solicitud de la función Middleware
+
+A continuación, crearemos una función de middleware llamada "requestTime" y agregaremos una propiedad llamada `requestTime`
+al objeto de la solicitud.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+La aplicación ahora utiliza la función de middleware `requestTime`. Además, la función de callback de la ruta raíz utiliza la propiedad que la función middleware añade a `req` (el objeto de la solicitud).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = '¡Hola Mundo!<br>';
+  responseText += `<small>Solicitado en: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Cuando hace una solicitud a la raíz de la aplicación, la aplicación ahora muestra la marca de tiempo de su solicitud en el navegador.
+
+### Función Middleware validateCookies
+
+Finalmente, crearemos una función de middleware que valida las cookies entrantes y envía una respuesta 400 si las cookies no son válidas.
+
+Aquí hay una función de ejemplo que valida las cookies con un servicio externo asíncrono.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Aquí usamos el [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware para analizar las cookies entrantes del objeto `req` y pasarlas a nuestra función `cookieValidator`. El middleware `validateCookies` devuelve una Promesa que al rechazar activará automáticamente nuestro gestor de errores.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// manejador de errores
+app.se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alerta">
+
+Observe cómo `next()` es llamado después de `await cookieValidator(req.cookies)`. Esto asegura que si
+`cookieValidator` resuelve, se llamará al siguiente middleware en la pila. Si pasas algo
+a la función `next()` (excepto la cadena `'route'` o `'router'`), Express considera que la actual petición
+es un error y se saltará cualquier función
+que no sea de manejo de enrutamiento y middleware restante.
+
+</Alert>
+
+Debido a que tiene acceso al objeto de solicitud, el objeto de respuesta, la siguiente función de middleware en la pila, y el nodo entero. s API, las posibilidades con funciones middleware son infinitas.
+
+Para más información sobre middleware exprés, vea: [Usando middleware exprés](/en/guide/using-middleware).
+
+## Middleware configurable
+
+Si necesita que su middleware sea configurable, exporte una función que acepte un objeto de opciones u otros parámetros, , que luego devuelve la implementación de middleware basada en los parámetros de entrada.
+
+Archivo: `my-middleware.js`
+
+```js
+módulo.xports = function (options) {
+  return function (req, res, next) {
+    // Implementar la función middleware basada en el objeto de opciones
+    siguiente();
+  };
+};
+```
+
+El middleware ahora puede ser usado como se muestra a continuación.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Consulte [cookie-session](https://github.com/expressjs/cookie-session) y [compression](https://github.com/expressjs/compression) para ver ejemplos de middleware configurable.
diff --git a/src/content/docs/es/4x/starter/basic-routing.mdx b/src/content/docs/es/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..51d6b399d2
--- /dev/null
+++ b/src/content/docs/es/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Ruta básica
+description: Aprenda los fundamentos de la enrutamiento en aplicaciones Express.js, incluyendo cómo definir rutas, manejar métodos HTTP y crear manejadores de rutas para su servidor web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Enrutamiento_ se refiere a determinar cómo responde una aplicación a una solicitud de cliente a un punto final en particular, que es una URI (o ruta) y un método específico de petición HTTP (GET, POST, etc.).
+
+Cada ruta puede tener una o más funciones manejadoras, que se ejecutan cuando la ruta es igualada.
+
+La definición de ruta tiene la siguiente estructura:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Donde:
+
+- `app` es una instancia de `express`.
+- `METHOD` es un [método de solicitud HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), en minúsculas.
+- `PATH` es una ruta en el servidor.
+- `HANDLER` es la función ejecutada cuando la ruta es coincidente.
+
+<Alert type="alerta">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Si no estás familiarizado con la creación de una aplicación e iniciarla, consulta el Hola mundo
+ejemplo.
+
+</Alert>
+
+Los siguientes ejemplos ilustran la definición de rutas simples.
+
+Responder con `¡Hola Mundo!` en la página principal:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hola Mundo!');
+});
+```
+
+Responder a una solicitud POST en la ruta raíz (`/`), la página de inicio de la aplicación:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Obtener una solicitud POST');
+});
+```
+
+Responder a una solicitud PUT a la ruta `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Obtener una solicitud PUT en /user');
+});
+```
+
+Responder a una solicitud DELETE a la ruta `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Obtuvo una solicitud DELETE en /user');
+});
+```
+
+Para más detalles sobre enrutamiento, vea la [guía de enrutamiento](/en/guide/routing).
diff --git a/src/content/docs/es/4x/starter/examples.mdx b/src/content/docs/es/4x/starter/examples.mdx
new file mode 100644
index 0000000000..729ac5a379
--- /dev/null
+++ b/src/content/docs/es/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Ejemplos exprés
+description: Explore una colección de ejemplos de aplicaciones de Express.js que cubren varios casos de uso, integraciones y configuraciones avanzadas para ayudarle a aprender y construir sus proyectos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Autenticación con nombre de usuario y contraseña
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - negociación de contenido HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Trabajando con sesiones basadas en cookies
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Trabajando con galletas
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transfiriendo archivos al cliente
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Trabajando con plantillas JavaScript embebidas (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Creando páginas de error
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Trabajando con middleware de error
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Manejador de solicitudes simple
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown como motor de plantillas
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Trabajando con varios enrutadores Express
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - Controladores estilo MVC
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Trabajando con parámetros de ruta
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Múltiples operaciones HTTP en el mismo recurso
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organizar rutas usando un mapa
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Trabajando con middleware de ruta
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizando rutas por cada recurso
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - API de búsqueda
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - Sesiones de usuario
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Subrayando archivos estáticos
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Trabajando con hosts virtuales
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Procesar dinámicamente las vistas
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Servicio de API simple
+
+## Ejemplos adicionales
+
+Estos son algunos ejemplos adicionales con integraciones más amplias.
+
+<Alert type="advertencia">
+  Esta información se refiere a sitios de terceros, productos o módulos que no son mantenidos por el
+  equipo de Expressjs. La lista aquí no constituye un aviso o recomendación del equipo de proyecto
+  Expressjs.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Aplicación completa con Express y Next.js usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - API REST con Express en TypeScript usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
diff --git a/src/content/docs/es/4x/starter/faq.md b/src/content/docs/es/4x/starter/faq.md
new file mode 100644
index 0000000000..6f808c230e
--- /dev/null
+++ b/src/content/docs/es/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Encuentre respuestas a preguntas frecuentes sobre Express.js, incluyendo temas sobre estructura de aplicaciones, modelos, autenticación, motores de plantillas, manejo de errores, y más.
+---
+
+## ¿Cómo debo estructurar mi aplicación?
+
+No hay una respuesta definitiva a esta pregunta. La respuesta depende
+de la escala de tu aplicación y del equipo implicado. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Las rutas y otra lógica específica de la aplicación pueden vivir tantos archivos
+como desee, en cualquier estructura de directorio que prefiera. View the following
+examples for inspiration:
+
+- [Rutas listadas](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mapa de ruta](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Además, existen extensiones de terceros para Express, que simplifican algunos de estos patrones:
+
+- [Rutas de recursos](https://github.com/expressjs/express-resource)
+
+## ¿Cómo defino los modelos?
+
+Express no tiene noción de una base de datos. Este concepto es
+dejado a los módulos de Nodo de terceros, permitiéndote una interfaz
+con casi cualquier base de datos.
+
+Vea [LoopBack](http://loopback.io) para un framework basado en Expresiones centrado en modelos.
+
+## ¿Cómo puedo autenticar usuarios?
+
+Authentication is another opinionated area that Express does not
+venture into. Puede utilizar cualquier esquema de autenticación que desee.
+Para un esquema simple de nombre de usuario / contraseña, vea [este ejemplo](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## ¿Qué motores de plantillas soporta Express?
+
+Express soporta cualquier motor de plantillas que cumpla con la firma `(ruta, locales, callback)`.
+Para normalizar las interfaces del motor de plantillas y la caché, consulte el proyecto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+para obtener soporte. Los motores de plantillas no listados pueden seguir soportando la firma Express.
+
+Para obtener más información, consulte [Usar motores de plantilla con Express](/en/guide/using-template-engines).
+
+## ¿Cómo puedo manejar las respuestas 404?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. Este comportamiento es
+porque una respuesta 404 simplemente indica la ausencia de trabajo adicional por hacer;
+en otras palabras, Express ha ejecutado todas las funciones y rutas de middleware,
+y ha encontrado que ninguno de ellos respondió. Todo lo que necesitas hacer
+es añadir una función de middleware en la parte inferior de la pila (debajo de todas las demás funciones)
+para manejar una respuesta 404:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Añadir rutas dinámicamente en tiempo de ejecución en una instancia de `express.Router()`
+para que las rutas no sean reemplazadas por una función de middleware.
+
+## ¿Cómo configuro un gestor de errores?
+
+Usted define middleware que maneja errores de la misma manera que otros middleware,
+excepto con cuatro argumentos en lugar de tres; específicamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para más información, vea [Gestión de errores] (/en/guide/error-handling).
+
+## ¿Cómo renderizo HTML plano?
+
+¡No lo tienes! No hay necesidad de "render" HTML con la función `res.render()`.
+Si tienes un archivo específico, usa la función `res.sendFile()`.
+Si está sirviendo muchos activos de un directorio, utilice la función de middleware `express.static()`
+.
+
+## ¿Qué versión de Node.js requiere Express?
+
+- [Express 4.x](/en/4x/api) requiere 0.10 o superior de Node.js.
+- [Express 5.x](/en/5x/api) requiere Node.js 18 o superior.
diff --git a/src/content/docs/es/4x/starter/generator.mdx b/src/content/docs/es/4x/starter/generator.mdx
new file mode 100644
index 0000000000..2755232b43
--- /dev/null
+++ b/src/content/docs/es/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Generador de aplicaciones urgente
+description: Aprenda cómo utilizar la herramienta del generador de aplicaciones Express para crear rápidamente un esqueleto para sus aplicaciones Express.js, configuración de streamlining y configuración.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilice la herramienta generadora de aplicaciones, `express-generator`, para crear rápidamente un esqueleto de aplicación.
+
+Puede ejecutar el generador de aplicaciones con el comando `npx` (disponible en Node.js 8.2.0).
+
+```bash
+$ generador de expresiones npx
+```
+
+Para versiones anteriores de Node, instale el generador de aplicaciones como un paquete global npm y luego ejecute:
+
+```bash
+$ npm install -g express-generator
+$ expreso
+```
+
+Mostrar las opciones de comando con la opción `-h`:
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opciones:
+
+    -h, --help output output use information
+        --version output output the version number
+    -e, --ejs añadir soporte para motores ejs
+        --hbs añadir soporte para motores handlebars
+        --pug añadir soporte para pug engine
+    -H, --hogan añadir hogan. s engine soporta
+        --no-view generar sin el motor de vista
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (por defecto jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|Ninguno|brújula|sass) (por defecto a simple css)
+        --git add . itignore
+    -f, --force en directorio no vacío
+```
+
+Por ejemplo, lo siguiente crea una aplicación Express llamada _myapp_. La aplicación se creará en una carpeta llamada _myapp_ en el directorio de trabajo actual y el motor de vistas se establecerá en <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   crear : miapp/rutas/usuarios. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ★
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Luego instale dependencias:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+En MacOS o Linux, ejecuta la aplicación con este comando:
+
+```bash
+$ DEBUG=miapp:* npm inicio
+```
+
+En Windows Command Prompt, utilice este comando:
+
+```bash
+> establecer DEBUG=miapp:* & npm start
+```
+
+En Windows PowerShell, utilice este comando:
+
+```bash
+PS> $env:DEBUG='miapp:*'; npm start
+```
+
+Luego, carga `http://localhost:3000/` en tu navegador para acceder a la aplicación.
+
+La aplicación generada tiene la siguiente estructura de directorios:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+La estructura de aplicaciones creada por el generador es sólo una de las muchas formas de estructurar aplicaciones Express.
+Siéntase libre de usar esta estructura o modificarla para que se adapte mejor a sus necesidades.
+
+</Alert>
diff --git a/src/content/docs/es/4x/starter/hello-world.mdx b/src/content/docs/es/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..5e74cf6bbb
--- /dev/null
+++ b/src/content/docs/es/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hola ejemplo de mundo
+description: Comienza con Express.js construyendo una sencilla aplicación 'Hola Mundo', demostrando la configuración básica y la creación de servidores para principiantes.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Incrustado a continuación es esencialmente la aplicación Express más simple que puede crear. Es una aplicación de archivo única
+&mdash; _no_ lo que obtendrías si utilizas el [generador Express](/en/starter/generator), que
+crea el andamio para una aplicación completa con numerosos archivos JavaScript, plantillas de Jade y subdirectorios
+para varios propósitos.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('¡Hola Mundo!');
+});
+
+app.listen(port, () => {
+  console.log(`Ejemplo de aplicación escuchando en el puerto ${port}`);
+});
+```
+
+Esta aplicación inicia un servidor y escucha en el puerto 3000 para las conexiones. La aplicación responde con "¡Hola Mundo!" para las solicitudes
+a la URL raíz (`/`) o _route_. Por cada otro camino, responderá con un **404 No Encontrado**.
+
+## Ejecutar localmente
+
+Primero cree un directorio llamado `myapp`, cámbielo y ejecute `npm init`. Luego, instala `express` como una dependencia, según la [guía de instalación](/en/starter/installing).
+
+En el directorio `myapp`, crea un archivo llamado `app.js` y copia el código del ejemplo anterior.
+
+<Alert type="alerta">
+
+El `req` (petición) y `res` (respuesta) son los mismos objetos exactos que el Node proporciona, así que puedes
+invocar `req. ipe()`, `req.on('data', callback)`, y cualquier otra cosa que hagas sin Express
+involucradas.
+
+</Alert>
+
+Ejecutar la aplicación con el siguiente comando:
+
+```bash
+$ node app.js
+```
+
+Luego, carga `http://localhost:3000/` en un navegador para ver la salida.
diff --git a/src/content/docs/es/4x/starter/installing.mdx b/src/content/docs/es/4x/starter/installing.mdx
new file mode 100644
index 0000000000..666c03bc8d
--- /dev/null
+++ b/src/content/docs/es/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Instalando
+description: Aprenda cómo instalar Express.js en su entorno Node.js, incluyendo la configuración del directorio de su proyecto y la gestión de dependencias con npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Antes de comenzar, asegúrese de que tiene instalado [Node.js](https://nodejs.org/) 0.10 o superior. Luego, crea un directorio para tu aplicación y navega por ella.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Usa el comando `npm init` para crear un archivo `package.json` para tu aplicación.
+Para más información sobre el funcionamiento de `package.json`, consulta [Especificaciones del manejo de package.json de npm](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Este comando te pide varias cosas, como el nombre y la versión de tu aplicación.
+Por ahora, puede simplemente pulsar RETURN para aceptar los valores predeterminados para la mayoría de ellos, con la siguiente excepción:
+
+```
+punto de entrada: (index.js)
+```
+
+Introduzca `app.js`, o lo que quiera que sea el nombre del archivo principal. Si desea que sea `index.js`, pulse RETURN para aceptar el nombre de archivo predeterminado sugerido.
+
+Ahora, instale Express en el directorio `myapp` y guárdelo en la lista de dependencias. Por ejemplo:
+
+```bash
+npm instalar Express
+```
+
+Para instalar Express temporalmente y no añadirlo a la lista de dependencias:
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="info">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Luego, después, ejecutar `npm install` en el directorio de aplicaciones automáticamente
+instalará módulos en la lista de dependencias.
+
+</Alert>
diff --git a/src/content/docs/es/4x/starter/static-files.mdx b/src/content/docs/es/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..a614730632
--- /dev/null
+++ b/src/content/docs/es/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Comprobando archivos estáticos en Express
+description: Describa cómo servir archivos estáticos como imágenes, CSS y JavaScript en aplicaciones Express.js usando el middleware 'static' incorporado.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para servir archivos estáticos como imágenes, archivos CSS, y archivos JavaScript, utiliza la función middleware integrada `express.static` en Express.
+
+La firma de la función es:
+
+```js
+express.static(root, [options]);
+```
+
+El argumento `root` especifica el directorio raíz desde el cual servir activos estáticos.
+Para más información sobre el argumento `options`, vea [express.static](/en/5x/api#express.static).
+
+Por ejemplo, utiliza el siguiente código para servir imágenes, archivos CSS y archivos JavaScript en un directorio llamado `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Ahora, puedes cargar los archivos que están en el directorio `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express busca los archivos relativos al directorio estático, por lo que el nombre del directorio estático
+no es parte de la URL.
+
+</Alert>
+
+Para usar múltiples directorios de activos estáticos, llama a la función middleware `express.static` varias veces:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express busca los archivos en el orden en el que estableces los directorios estáticos con la función de middleware `express.static`.
+
+<Alert type="info">
+
+Para obtener mejores resultados, usa un proxy
+inverso caché para mejorar el rendimiento de
+sirviendo activos estáticos.
+
+</Alert>
+
+Para crear un prefijo de ruta virtual (donde la ruta no existe en el sistema de archivos) para archivos que son servidos por el `express. función tatic`, [especificar una ruta de montaje](/en/5x/api#app.use) para el directorio estático, como se muestra a continuación:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Ahora, puedes cargar los archivos que están en el directorio `public` desde el prefijo de ruta `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Sin embargo, la ruta que proporcionas a la función `express.static` es relativa al directorio desde el cual inicias tu proceso `node`. Si ejecuta la aplicación expresa desde otro directorio, es más seguro utilizar la ruta absoluta del directorio que desea servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Para más detalles sobre la función `serve-static` y sus opciones, vea [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/es/5x/advanced/developing-template-engines.md b/src/content/docs/es/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..39a63bd5b5
--- /dev/null
+++ b/src/content/docs/es/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Desarrollar motores de plantillas para Express
+description: Aprenda cómo desarrollar motores de plantillas personalizados para Express.js usando app.engine(), con ejemplos de creación e integración de su propia lógica de renderizado de plantillas.
+---
+
+Usa el método `app.engine(ext, callback)` para crear tu propio motor de plantillas. `ext` se refiere a la extensión del archivo, y `callback` es la función del motor de plantilla, que acepta los siguientes elementos como parámetros: la ubicación del archivo, el objeto de opciones y la función de devolución de llamada.
+
+El siguiente código es un ejemplo de implementación de un motor de plantillas muy simple para renderizar archivos `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Tu aplicación ahora será capaz de procesar archivos `.ntl`. Crea un archivo llamado `index.ntl` en el directorio `views` con el siguiente contenido.
+
+```pug
+#title#
+#message#
+```
+
+Luego, crea la siguiente ruta en tu aplicación.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Cuando hagas una solicitud a la página de inicio, `index.ntl` será renderizado como HTML.
diff --git a/src/content/docs/es/5x/guide/behind-proxies.mdx b/src/content/docs/es/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..76d786f141
--- /dev/null
+++ b/src/content/docs/es/5x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Expresar detrás de proxies
+description: Aprenda cómo configurar las aplicaciones Express.js para que funcionen correctamente detrás de los proxies inversos, incluyendo el uso de la configuración del proxy de confianza para manejar las direcciones IP del cliente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Cuando se ejecuta una aplicación Express detrás de un proxy inverso, algunas de las APIs Express pueden devolver valores diferentes de los esperados. Para ajustarse a esto, la configuración de la aplicación `trust proxy` puede utilizarse para exponer la información proporcionada por el proxy inverso en las APIs Express. El problema más común son las APIs expresas que exponen la dirección IP del cliente pueden mostrar una dirección IP interna del proxy inverso.
+
+<Alert type="info">
+
+Al configurar la configuración del `proxy de confianza`, es importante entender la configuración exacta del proxy inverso
+. Dado que esta configuración confiará en los valores proporcionados en la solicitud, es importante que
+la combinación de la configuración en Express coincida con cómo funciona el proxy inverso.
+
+</Alert>
+
+El ajuste de la aplicación `proxy de confianza` puede establecerse en uno de los valores listados en la siguiente tabla.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Escriba</th><th>Valor</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Si es `true`, la dirección IP del cliente se entiende como la entrada más a la izquierda en la cabecera `X-Forwarded-For`.
+
+Si es `false`, la aplicación se entiende como directamente frente al cliente y la dirección IP del cliente se deriva de `req.socket.remoteAddress`. Esta es la configuración por defecto.
+
+<Alert type="advertencia">
+Cuando se establece en `true`, es importante asegurarse de que el último proxy inverso en el que se confía es eliminar/sobrescribir todas las siguientes cabeceras HTTP: `X-Forwarded-For`, `X-Forwarded-Host`, y `X-Forwarded-Proto`, de lo contrario puede ser posible que el cliente proporcione cualquier valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>direcciones IP</td>
+<td markdown="1">
+Una dirección IP, subred, o un array de direcciones IP y subredes en las que confiar como un proxy inverso. La siguiente lista muestra los nombres de subred preconfigurados:
+
+- bucle atrás - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Puede establecer direcciones IP de cualquiera de las siguientes maneras:
+
+```js
+app.set('trust proxy', 'loopback'); // especificar una única subred
+app.set('trust proxy', 'loopback, 123.123.123.123'); // especificar una subred y una dirección
+app.et('trust proxy', 'loopback, linklocal, uniquelocal'); // especifica múltiples subredes como CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // especifica múltiples subredes como un array
+```
+
+Cuando se especifica, las direcciones IP o las subredes están excluidas del proceso de determinación de direcciones, y la dirección IP no confiable más cercana al servidor de aplicaciones se determina como la dirección IP del cliente. Esto funciona comprobando si `req.socket.remoteAddress` es de confianza. Si es así, entonces cada dirección en `X-Forwarded-For` se marca de derecha a izquierda hasta la primera dirección no confiable.
+
+</td>
+    </tr>
+    <tr>
+      <td>Número</td>
+<td markdown="1">
+Utilice la dirección que es como máximo el número de saltos `n` de la aplicación Express. `req.socket.remoteAddress` es la primera salida, y el resto son buscados en la cabecera `X-Forwarded-For` de derecha a izquierda. Un valor de `0` significa que la primera dirección no confiable sería `req.socket.remoteAddress`, es decir, no hay proxy inverso.
+
+<Alert type="advertencia">
+Al usar esta configuración, es importante asegurarse de que no hay múltiplos, rutas de longitud diferente a la aplicación Express tal que el cliente puede ser menor que el número de saltos configurados de lo contrario es posible que el cliente proporcione cualquier valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Función</td>
+<td markdown="1">
+Implementación de confianza personalizada.
+
+```js
+app.set('confiar en proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    return true; // Iders confiables
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Habilitar `proxy de confianza` tendrá el siguiente impacto:
+
+<ul>
+  <li markdown="1">
+    El valor de [req.hostname](/en/api#req.hostname) se deriva del valor establecido en la cabecera
+    `X-Forwarded-Host`, que puede ser definido por el cliente o por el proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` puede ser establecido por el proxy inverso para decirle a la aplicación si
+    es `https` o `http` o incluso un nombre inválido. Este valor se refleja en
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Los valores [req.ip](/en/api#req.ip) y [req.ips](/en/api#req.ips) son poblados según la
+    dirección del socket y la cabecera `X-Forwarded-For`, comenzando en la primera dirección no
+    confiable.
+  </li>
+</ul>
+
+La configuración `trust proxy` se implementa usando el paquete [proxy-addr](https://www.npmjs.com/package/proxy-addr). Para obtener más información, consulte su documentación.
diff --git a/src/content/docs/es/5x/guide/debugging.mdx b/src/content/docs/es/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..18a5f950b2
--- /dev/null
+++ b/src/content/docs/es/5x/guide/debugging.mdx
@@ -0,0 +1,123 @@
+---
+title: Depuración Express
+description: Aprenda cómo habilitar y utilizar los registros de depuración en aplicaciones Express.js configurando la variable de entorno DEBUG para solucionar problemas mejorados.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para ver todos los registros internos usados en Express, establece la variable de entorno `DEBUG` a
+`express:*` al ejecutar tu aplicación.
+
+```bash
+$ DEBUG=express:* nodo index.js
+```
+
+En Windows, utilice el comando correspondiente.
+
+```bash
+> $env:DEBUG = "express:*"; nodo index.js
+```
+
+Ejecutando este comando en la aplicación predeterminada generada por el [generador expreso](/en/starter/generator) imprime la siguiente salida:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Cuando se hace una solicitud a la aplicación, verá los registros especificados en el código Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Para ver los registros sólo desde la implementación del router, establece el valor de `DEBUG` a `express:router`. De la misma manera, para ver los registros sólo desde la implementación de la aplicación, establece el valor de `DEBUG` a `express:application`, y así sucesivamente.
+
+## Aplicaciones generadas por `express`
+
+Una aplicación generada por el comando `express` utiliza el módulo `debug` y su espacio de nombres de depuración está cubierto por el nombre de la aplicación.
+
+Por ejemplo, si generaste la aplicación con \`$ muestra expresa, puedes habilitar las declaraciones de depuración con el siguiente comando:
+
+```bash
+$ DEBUG=sample-app:* nodo ./bin/www
+```
+
+Puede especificar más de un espacio de nombres de depuración asignando una lista de nombres separados por comas:
+
+```bash
+$ DEBUG=http,mail,express:* nodo index.js
+```
+
+## Opciones avanzadas
+
+Cuando se ejecuta a través de Node.js, puede establecer algunas variables de entorno que cambiarán el comportamiento del registro de depuración:
+
+| Nombre              | Propósito                                                             |
+| ------------------- | --------------------------------------------------------------------- |
+| `DEBUG`             | Habilita o deshabilita espacios de nombres específicos de depuración. |
+| `DEBUG_COLORS`      | Usar o no colores en la salida de depuración.                         |
+| `DEBUG_DEPTH`       | Profundidad de inspección de objetos.                                 |
+| `DEBUG_FD`          | Descriptor de archivo en el que escribir salida de depuración.        |
+| `DEBUG_SHOW_HIDDEN` | Muestra propiedades ocultas en los objetos esperados.                 |
+
+<Alert type="info">
+
+Las variables de entorno que empiezan con `DEBUG_` acaban siendo convertidas en un objeto Options
+que se usa con formateadores `%o`/`%O. Vea la documentación de Node.js para [`util.inspect()\`](https://nodejs.org/api/util#util_util_inspect_object_options) para la lista completa
+.
+
+</Alert>
diff --git a/src/content/docs/es/5x/guide/error-handling.mdx b/src/content/docs/es/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..c899c51198
--- /dev/null
+++ b/src/content/docs/es/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Manejo de errores
+description: Descargue cómo Express.js maneja errores en código sincrónico y asíncrono, y aprenda a implementar middleware de manejo de errores personalizado para sus aplicaciones.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express viene con un manejador de error predeterminado
+, así que no necesitas escribir el tuyo propio para empezar.
+
+## Errores de captura
+
+Es importante asegurarse de que Express capture todos los errores que ocurren mientras
+ejecuta los manejadores de rutas y el middleware.
+
+Los errores que ocurren en el código sincrónico dentro de los manejadores de rutas y middleware
+no requieren trabajo extra. Si el código sincrónico arroja un error, entonces Express hará
+capturarlo y procesarlo. Por ejemplo:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express capturará esto por su cuenta.
+});
+```
+
+Para los errores devueltos por funciones asincrónicas invocadas por los manejadores de rutas
+y middleware, debes pasarlos a la función `next()`, donde Express las capturará y procesará
+. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pasar los errores a Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+A partir de Express 5, manejadores de rutas y middleware que devuelven una Promise
+llamará automáticamente a `next(value)` cuando rechacen o lancen un error.
+Por ejemplo:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Si `getUserById` arroja un error o rechaza, `next` será llamado con
+el error arrojado o el valor rechazado. Si no se proporciona ningún valor rechazado, `next`
+será llamado con un objeto de Error predeterminado proporcionado por el enrutador Express.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+Si la devolución de llamada en una secuencia no proporciona datos, sólo errores, puede simplificar
+este código de la siguiente manera:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+En el ejemplo anterior, `next` es proporcionado como el callback para `fs.writeFile`,
+que es llamado con o sin errores. Si no hay error, se ejecuta el segundo manejador
+, de lo contrario Express catches y procesa el error.
+
+Debe capturar errores que ocurren en código asíncrono invocado por manejadores de ruta o un middleware
+y pasarlos a Express para su procesamiento. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+El ejemplo anterior utiliza un bloque `try...catch` para capturar errores en el código asincrónico
+y pasarlos a Express. Si el bloque `try...catch`
+fuera omitido, Express no capturaría el error ya que no es parte del código de manejador
+sincrónico.
+
+Usa promesas para evitar la sobrecarga del bloque "intentar...atrapar" o al usar funciones
+que devuelven promesas. Por ejemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Los errores se pasarán a Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+También podría utilizar una cadena de manejadores para depender de la captura de errores sincrónicos
+, reduciendo el código asincrónico a algo trivial. Por ejemplo:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.ata = data;
+      siguiente(err);
+    });
+  },
+  function (req, res) {
+    res.ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+El ejemplo anterior tiene un par de declaraciones triviales de la llamada `readFile`
+. Si `readFile` causa un error, entonces pasa el error a Express, de lo contrario
+regresa rápidamente al mundo del manejo sincrónico de errores en el siguiente manejador
+en la cadena. Luego, el ejemplo anterior intenta procesar los datos. Si esto falla, entonces el gestor de errores sincrónico
+lo capturará. Si hubiera hecho este procesamiento dentro de
+el callback `readFile`, entonces la aplicación podría salir y los manejadores de error Express
+no se ejecutarían.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## El gestor de errores por defecto
+
+Express viene con un gestor de errores integrado que se encarga de cualquier error que pueda encontrarse en la aplicación. Esta función middleware por defecto se añade al final de la pila de funciones de middleware.
+
+Si pasas un error a `next()` y no lo gestionas en un controlador
+error personalizado, será manejado por el gestor de errores integrado; el error será
+escrito al cliente con el stack trace. El stack trace no está incluido
+en el entorno de producción.
+
+<Alert type="info">
+
+Establece la variable de entorno `NODE_ENV` a `production`, para ejecutar la aplicación en el modo de producción.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- El `res.statusCode` se establece desde `err.status` (o `err.statusCode`). Si
+  este valor está fuera del rango 4xx o 5xx, se establecerá a 500.
+- El `res.statusMessage` se establece de acuerdo al código de estado.
+- El cuerpo será el HTML del mensaje del código de estado cuando en el entorno
+  de producción, de lo contrario será `err.stack`.
+- Cualquier cabecera especificada en un objeto `err.headers`.
+
+Si llama a `next()` con un error después de haber comenzado a escribir la respuesta
+(por ejemplo, si encuentras un error al transmitir la respuesta
+al cliente), el gestor de errores Express por defecto cierra la conexión
+y falla la solicitud.
+
+Así que cuando añada un manejador de errores personalizado, debe delegar a
+el manejador de errores predeterminado Express cuando los encabezados
+ya han sido enviados al cliente:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Tenga en cuenta que el manejador de errores por defecto puede activarse si llama a `next()` con un error
+en su código más de una vez, incluso si el middleware está configurado para manejar errores personalizados.
+
+Otro middleware de manejo de error se puede encontrar en [Express middleware](/en/resources/middleware).
+
+## Manejadores de errores escritos
+
+Define las funciones de middleware de la misma manera que otras funciones de middleware,
+excepto las funciones de manejo de errores tienen cuatro argumentos en lugar de tres:
+`(err, req, res, next)`. Por ejemplo:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Usted define middleware manejado por errores últimamente, después de otras `app.use()` y llamadas de rutas; por ejemplo:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extendido: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // lógica
+});
+```
+
+Las respuestas desde dentro de una función middleware pueden estar en cualquier formato, como una página de error HTML, un mensaje simple, o una cadena JSON.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. Por ejemplo, para definir un manejador de errores
+para las solicitudes realizadas usando `XHR` y las que no tienen:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extendido: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+En este ejemplo, el genérico `logErrors` podría escribir una solicitud y
+información de error a `stderr`, por ejemplo:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+También en este ejemplo, `clientErrorHandler` se define de la siguiente manera; en este caso, el error se pasa explícitamente al siguiente.
+
+Tenga en cuenta que cuando _no_ llama "siguiente" en una función de manejo de errores, usted es responsable de escribir (y terminar) la respuesta. De lo contrario, esas solicitudes se "colgarán" y no serán elegibles para la recolección de basura.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementa la función "catch-all" `errorHandler` como sigue (por ejemplo):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Si tiene un manejador de ruta con múltiples funciones de callback, puede utilizar el parámetro `route` para saltar al siguiente manejador de ruta. Por ejemplo:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // continúa manejando esta solicitud
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+En este ejemplo, el manejador `getPaidContent` se omitirá pero cualquier manejador restante en `app` para `/a_route_behind_paywall` continuaría siendo ejecutado.
+
+<Alert type="info">
+
+Las llamadas a `next()` y `next(err)` indican que el controlador actual está completo y en qué estado.
+`next(err)` omitirá todos los manejadores restantes en la cadena, excepto aquellos que están configurados a
+errores de manejo como se describe arriba.
+
+</Alert>
diff --git a/src/content/docs/es/5x/guide/overriding-express-api.md b/src/content/docs/es/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..9be44e70df
--- /dev/null
+++ b/src/content/docs/es/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Reemplazar la API Express
+description: Descubra cómo personalizar y extender la API de Express.js reemplazando métodos y propiedades en los objetos de solicitud y respuesta usando prototipos.
+---
+
+La API Express consiste en varios métodos y propiedades sobre los objetos de solicitud y respuesta. Estos son heredados por prototipo. Hay dos puntos de extensión para la API Express:
+
+1. Los prototipos globales en `express.request` y `express.response`.
+2. prototipos específicos de la aplicación en `app.request` y `app.response`.
+
+Alterar los prototipos globales afectará a todas las aplicaciones cargadas Express en el mismo proceso. Si se desea, las alteraciones pueden hacerse específicas de la aplicación sólo modificando los prototipos específicos de la aplicación después de crear una nueva aplicación.
+
+## Métodos
+
+Puede anular la firma y el comportamiento de los métodos existentes con los suyos, asignando una función personalizada.
+
+A continuación se muestra un ejemplo de anular el comportamiento de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+La implementación anterior cambia completamente la firma original de `res.sendStatus`. Ahora acepta un código de estado, tipo de codificación, y el mensaje que se enviará al cliente.
+
+El método sobreescrito ahora puede utilizarse de esta manera:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Propiedades
+
+Las propiedades en la API Express son tamaño:
+
+1. Propiedades asignadas (ej: `req.baseUrl`, `req.originalUrl`)
+2. Definido como getters (ej: `req.secure`, `req.ip`)
+
+Dado que las propiedades de la categoría 1 se asignan dinámicamente a los objetos `request` y `response` en el contexto del ciclo actual de petición-respuesta, su comportamiento no puede ser anulado.
+
+Las propiedades de la categoría 2 se pueden sobrescribir usando la API Express de extensiones API.
+
+El siguiente código reescribe cómo se derivará el valor de `req.ip`. Ahora, simplemente devuelve el valor de la cabecera de petición `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototipo
+
+Para proporcionar la API Express, los objetos de solicitud / respuesta pasados a Express (a través de `app(req, res)`, por ejemplo) necesita heredar de la misma cadena prototipo. Por defecto, esto es `http.IncomingRequest.prototype` para la solicitud y `http.ServerResponse.prototype` para la respuesta.
+
+A menos que sea necesario, se recomienda que esto se haga únicamente a nivel de aplicación, en lugar de a nivel global. Además, tenga cuidado de que el prototipo que se está utilizando coincida con la funcionalidad lo más cerca posible de los prototipos predeterminados.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/es/5x/guide/routing.mdx b/src/content/docs/es/5x/guide/routing.mdx
new file mode 100644
index 0000000000..a57c73637f
--- /dev/null
+++ b/src/content/docs/es/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Ruta
+description: Aprenda cómo definir y usar rutas en aplicaciones Express.js, incluyendo métodos de ruta, rutas de ruta, parámetros, y usando Router para rutas modulares.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ se refiere a cómo responden los extremos (URIs) de una aplicación a las peticiones del cliente.
+Para una introducción al enrutamiento, consulte [Enrutamiento básico](/en/starter/basic-routing).
+
+Define enrutamiento usando métodos del objeto Express `app` que corresponden a métodos HTTP;
+por ejemplo, `app. et()` para manejar solicitudes GET y `app.post` para manejar solicitudes POST. Para una lista completa,
+vea [app.METHOD](/en/5x/api#app.METHOD). También puedes usar [app.all()](/en/5x/api#app.all) para manejar todos los métodos HTTP y [app. se()](/en/5x/api#app.use) a
+especificar middleware como función de callback (Ver [Usando middleware](/en/guide/using-middleware) para más detalles).
+
+Estos métodos de enrutamiento especifican una función de callback (a veces llamada "funciones manejadoras") llamada cuando la aplicación recibe una petición a la ruta especificada (endpoint) y el método HTTP. En otras palabras, la aplicación "escucha" para peticiones que coinciden con el/los método(s) especificado(s), y cuando detecta una coincidencia, llama a la función de callback especificada.
+
+De hecho, los métodos de enrutamiento pueden tener más de una función de callback como argumentos.
+Con múltiples funciones de callback, es importante proporcionar `next` como un argumento a la función de callback y luego llamar `next()` dentro del cuerpo de la función para desactivar el control
+al siguiente callback.
+
+El siguiente código es un ejemplo de una ruta muy básica.
+
+```js
+const express = require('express');
+const app = express();
+
+// responden con "Hola mundo" cuando se hace una solicitud GET a la página de inicio
+aplicación.et('/', (req, res) => {
+  res.send('hola mundo');
+});
+```
+
+## Métodos de ruta
+
+Un método de ruta se deriva de uno de los métodos HTTP y se adjunta a una instancia de la clase `express`.
+
+El siguiente código es un ejemplo de rutas definidas para los métodos `GET` y `POST` a la raíz de la aplicación.
+
+```js
+// Ruta del método GET
+app.get('/', (req, res) => {
+  res.end('GET request to the homepage');
+});
+
+// método POST route
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express soporta métodos que corresponden a todos los métodos de petición HTTP: `get`, `post`, y así sucesivamente.
+Para una lista completa, vea [app.METHOD](/en/5x/api#app.METHOD).
+
+Hay un método especial de enrutamiento, `app.all()`, usado para cargar funciones de middleware en una ruta para _all_ métodos de petición HTTP. Por ejemplo, el siguiente manejador se ejecuta para peticiones a la ruta `"/secret"` ya sea usando `GET`, `POST`, `PUT`, `DELETE`, o cualquier otro método de solicitud HTTP soportado en el [módulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Acceder a la sección secreta ...');
+  next(); // pasar el control al siguiente manejador
+});
+```
+
+## Rutas de ruta
+
+Las rutas de ruta, en combinación con un método de solicitud, definen los extremos en los que se pueden realizar las solicitudes. Las rutas pueden ser cadenas, patrones de cadenas o expresiones regulares.
+
+<Alert type="alerta">
+
+En expreso 5, los caracteres `? , `+`, `\*`, `[]`, y `()\` son manejados de manera diferente que en la versión
+4, por favor revisa la [guía de migración](/en/guide/migrating-5#path-syntax) para más información.
+
+</Alert>
+
+<Alert type="alerta">
+
+En expreso 4, los caracteres de expresión regular como `$` necesitan ser escapados con un `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express usa [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) para emparejar las rutas de la ruta
+; vea la documentación de la ruta a regexp para todas las posibilidades de definir rutas de la ruta.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Las cadenas de consulta no son parte de la ruta de la ruta.</Alert>
+
+### Rutas de ruta basadas en cadenas
+
+Esta ruta coincidirá con las peticiones a la ruta raíz, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Esta ruta coincidirá con las peticiones a `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Esta ruta de ruta coincidirá con peticiones a `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Rutas de ruta basadas en patrones de cadenas
+
+<Alert type="alerta">
+
+Los patrones de cadenas en Express 5 ya no funcionan. Consulte la guía de migración
+&#x20;para obtener más información.
+
+</Alert>
+
+Esta ruta de ruta coincidirá con `acd` y `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Esta ruta coincidirá con `abcd`, `abbcd`, `abbbcd`, y así sucesivamente.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Esta ruta de ruta coincidirá con `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, y así sucesivamente.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Esta ruta coincidirá con `/abe` y `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Rutas de ruta basadas en expresiones regulares
+
+Esta ruta coincidirá con cualquier cosa con una "a".
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Esta ruta coincidirá con `butterfly` y `dragonfly`, pero no `butterflyman`, `dragonflyman`, y así sucesivamente.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parámetros de ruta
+
+Los parámetros de ruta se llaman segmentos de URL que se utilizan para capturar los valores especificados en su posición en la URL. Los valores capturados son poblados en el objeto `req.params`, con el nombre del parámetro de ruta especificado en la ruta como sus claves respectivas.
+
+```
+Ruta de ruta: /users/:userId/books/:bookId
+URL de petición: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Para definir rutas con parámetros de ruta, simplemente especifique los parámetros de ruta en la ruta como se muestra a continuación.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alerta">
+
+El nombre de los parámetros de la ruta debe estar compuesto de "caracteres de palabra" ([A-Za-z0-9_]).
+
+</Alert>
+
+Dado que los guiones (`-`) y el punto (`.`) se interpretan literalmente, pueden ser utilizados junto con parámetros de ruta para propósitos útiles.
+
+```
+Ruta de ruta: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Ruta de ruta: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alerta">
+
+En expreso 5, no se admiten caracteres de expresión regular en rutas para más información, por favor
+consulte la [guía de migración](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Para tener más control sobre la cadena exacta que puede coincidir con un parámetro de ruta, puede añadir una expresión regular entre paréntesis (`()`):
+
+```
+Ruta de ruta: /user/:userId(\d+)
+URL de Solicitud: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="advertencia">
+
+Debido a que la expresión regular es generalmente parte de una cadena literal, Asegúrate de escapar cualquier `\`
+caracteres con una barra inversa adicional, por ejemplo `\d+`.
+
+</Alert>
+
+<Alert type="advertencia">
+En Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">el carácter `*` en expresiones regulares no se interpreta de la forma habitual</a>. Como un workaround, usa `{0,}` en lugar de `*`. Es probable que esto se arregle en Express 5.
+</Alert>
+
+## Manejadores de rutas
+
+Puedes proporcionar múltiples funciones de callback que se comportan como [middleware](/en/guide/using-middleware) para gestionar una solicitud. La única excepción es que estos callbacks podrían invocar a `next('route')` para evitar las llamadas restantes de ruta. Se puede utilizar este mecanismo para imponer condiciones previas a una ruta, luego pasar el control a las rutas posteriores si no hay razón para proceder con la ruta actual.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`Usuario ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Controlador especial para el usuario ID 0');
+});
+```
+
+En este ejemplo:
+
+- `GET /user/5` → manejado por primera ruta → envía "Usuario 5"
+- `GET /user/0` → primera ruta llama a `next('ruta')`, saltando a la siguiente ruta `/user/:id`
+
+Los manejadores de rutas pueden ser en forma de una función, un array de funciones o combinaciones de ambos, como se muestra en los siguientes ejemplos.
+
+Una única función de callback puede manejar una ruta. Por ejemplo:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hola de A!');
+});
+```
+
+Más de una función de callback puede manejar una ruta (asegúrese de especificar el objeto `siguiente`). Por ejemplo:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    consola.og('la respuesta será enviada por la siguiente función . .');
+    siguiente();
+  },
+  (req, res) => {
+    res.end('Hola de B!');
+  }
+);
+```
+
+Una matriz de funciones de callback puede manejar una ruta. Por ejemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  consola.og('CB0');
+  siguiente();
+};
+
+const cb1 = function (req, res, next) {
+  consola.og('CB1');
+  siguiente();
+};
+
+const cb2 = function (req, res) {
+  res.end('Hola de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Una combinación de funciones independientes y arreglos de funciones puede manejar una ruta. Por ejemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  consola.og('CB0');
+  siguiente();
+};
+
+const cb1 = function (req, res, next) {
+  consola.og('CB1');
+  siguiente();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    consola.og('la respuesta será enviada por la siguiente función . .');
+    siguiente();
+  },
+  (req, res) => {
+    res.end('Hola de D!');
+  }
+);
+```
+
+## Métodos de respuesta
+
+Los métodos en el objeto de respuesta (`res`) en la siguiente tabla pueden enviar una respuesta al cliente y terminar el ciclo de solicitud y respuesta. Si ninguno de estos métodos es llamado desde un gestor de rutas, la petición del cliente se dejará colgada.
+
+| Método                                        | Descripción                                                                                                 |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Solicitar un archivo para ser descargado.                                                                   |
+| [res.end()](/en/5x/api#res.end)               | Terminar el proceso de respuesta.                                                                           |
+| [res.json()](/en/5x/api#res.json)             | Enviar una respuesta JSON.                                                                                  |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envía una respuesta JSON con soporte JSONP.                                                                 |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirigir una solicitud.                                                                                    |
+| [res.render()](/en/5x/api#res.render)         | Procesar una plantilla de vista.                                                                            |
+| [res.send()](/en/5x/api#res.send)             | Enviar una respuesta de varios tipos.                                                                       |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Enviar un archivo como un flujo de octet.                                                                   |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Establece el código de estado de respuesta y envía su representación de cadena como el cuerpo de respuesta. |
+
+## app.route()
+
+Puede crear manejadores de rutas encadenables para una ruta usando `app.route()`.
+Debido a que la ruta se especifica en una única ubicación, la creación de rutas modulares es útil, al igual que la reducción de redundancia y tipografías. Para más información sobre rutas, vea: [documentación Router() ](/en/5x/api#router).
+
+Aquí hay un ejemplo de manejadores encadenados de rutas que se definen usando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Obtén un libro al azar');
+  })
+  .ost((req, res) => {
+    res.send('Agregar un libro');
+  })
+  .ut((req, res) => {
+    res.send('Actualizar el libro');
+  });
+```
+
+## express.Router
+
+Utilice la clase `express.Router` para crear manejadores modulares de rutas. Una instancia de `Router` es un sistema completo de middleware y enrutamiento; por esta razón, a menudo se le denomina "mini-app".
+
+El siguiente ejemplo crea un router como módulo, carga una función de middleware en él, define algunas rutas y monta el módulo del router en una ruta de la aplicación principal.
+
+Crea un archivo de enrutador llamado `birds.js` en el directorio de la aplicación, con el siguiente contenido:
+
+```js
+const express = require('express');
+const router = express.outer();
+
+// middleware que es específico para este router
+const timeLog = (req, res, next) => {
+  consola.og('Hora: ', Date.now());
+  siguiente();
+};
+enrutador.se(timeLog);
+
+// define la ruta de la página de inicio
+router.get('/', (req, res) => {
+  res.end('Página de inicio de aves');
+});
+// define la ruta
+router.et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Luego, cargue el módulo de enrutador en la aplicación:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+La aplicación ahora será capaz de manejar solicitudes a `/birds` y `/birds/about`, así como llamar a la función de middleware `timeLog` que es específica de la ruta.
+
+Pero si la ruta padre `/birds` tiene parámetros de ruta, no será accesible por defecto desde las subrutas. Para hacerlo accesible, necesitarás pasar la opción `mergeParams` al constructor de Router [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/es/5x/guide/using-middleware.mdx b/src/content/docs/es/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..a6852c622b
--- /dev/null
+++ b/src/content/docs/es/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usando middleware
+description: Aprenda cómo usar middleware en aplicaciones Express.js, incluyendo middleware de nivel de aplicación y router, manejo de errores, e integración de middleware de terceros.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express es un framework web de enrutamiento y middleware que tiene una funcionalidad mínima propia: Una aplicación Express es esencialmente una serie de llamadas a funciones de middleware.
+
+Las funciones _Middleware_ son funciones que tienen acceso al [objeto de solicitud](/en/5x/api#req) (`req`), el [objeto de respuesta](/en/5x/api#res) (`res`), y la siguiente función de middleware en el ciclo de solicitud y respuesta de la aplicación. La siguiente función middleware se denota comúnmente por una variable llamada `next`.
+
+Las funciones de Middleware pueden realizar las siguientes tareas:
+
+- Ejecutar cualquier código.
+- Realizar cambios en la solicitud y en los objetos de respuesta.
+- Terminar el ciclo de solicitud de respuesta.
+- Llame a la siguiente función de middleware en la pila.
+
+Si la función actual de middleware no termina el ciclo de solicitud de respuesta, debe llamar a `next()` para pasar el control a la siguiente función de middleware. De lo contrario, la solicitud quedará colgada.
+
+Una aplicación Express puede utilizar los siguientes tipos de middleware:
+
+- [Middleware de nivel de aplicación](#middleware.application)
+- [Middleware de nivel superior](#middleware.router)
+- [Middleware de manejo de errores](#middleware.error-handling)
+- [Middleware incorporado](#middleware.built-in)
+- [Middleware de terceros](#middleware.third-party)
+
+Puede cargar middleware de nivel de aplicación y de enrutador con una ruta de montaje opcional.
+También puede cargar una serie de funciones de middleware juntas, lo que crea un substack del sistema de middleware en un punto de montaje.
+
+## Middleware de nivel de aplicación
+
+Vincular middleware a una instancia del [objeto de aplicación](/en/5x/api#app) usando `app.use()` y `app. ETHOD()` funciona, donde `METHOD` es el método HTTP de la petición que la función middleware maneja (como GET, PUT o POST) en minúsculas.
+
+Este ejemplo muestra una función de middleware sin ruta de montaje. La función se ejecuta cada vez que la aplicación recibe una solicitud.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Este ejemplo muestra una función middleware montada en la ruta `/user/:id`. La función se ejecuta para cualquier tipo de petición
+HTTP en la ruta `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Este ejemplo muestra una ruta y su función manejadora (middleware system). La función maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USUARIO');
+});
+```
+
+He aquí un ejemplo de carga de una serie de funciones de middleware en un punto de montaje, con una ruta de montaje.
+Ilustra un substack de middleware que imprime la información de la petición para cualquier tipo de petición HTTP a la ruta `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    consola.og('Tipo de solicitud:', req.method);
+    siguiente();
+  }
+);
+```
+
+Los manejadores de rutas le permiten definir múltiples rutas para una ruta. El siguiente ejemplo define dos rutas para peticiones GET a la ruta `/user/:id`. La segunda ruta no causará ningún problema, pero nunca se llamará porque la primera ruta termina el ciclo de solicitud de respuesta.
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.arams.id);
+    siguiente();
+  },
+  (req, res, next) => {
+    res.end('Información de usuario');
+  }
+);
+
+// manejador para la ruta /user/:id, que imprime el ID de usuario
+app.et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Para omitir el resto de las funciones de middleware desde una pila de middleware de router, llame a `next('ruta')` para pasar el control a la siguiente ruta.
+
+<Alert type="info">
+
+`next('ruta')` solo funcionará en funciones de middleware que fueron cargadas usando las funciones
+`app.METHOD()` o `router.METHOD()`.
+
+</Alert>
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // si el ID de usuario es 0, saltar a la siguiente ruta
+    si (req. aramas. d === '0') siguiente('ruta');
+    // de lo contrario pasa el control a la siguiente función de middleware en esta pila
+    si no siguiente();
+  },
+  (req, res, next) => {
+    // envía una respuesta regular
+    res. end('regular');
+  }
+);
+
+// manejador para la ruta /user/:id, que envía una respuesta especial
+app. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware también puede ser declarado en una matriz para reusabilidad.
+
+Este ejemplo muestra una matriz con un substack de middleware que maneja peticiones GET en la ruta `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  siguiente();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('Información de usuario');
+});
+```
+
+## Middleware de nivel remoto
+
+El middleware Router-level funciona de la misma manera que el middleware a nivel de aplicación, excepto que está vinculado a una instancia de `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Carga el middleware a nivel de enrutador usando las funciones `router.use()` y `router.METHOD()`.
+
+El siguiente código de ejemplo replica el sistema middleware que se muestra arriba para el middleware de nivel de aplicación, mediante el uso de router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// una función de middleware sin ruta de montaje. Este código se ejecuta para cada petición al router
+. se((req, res, next) => {
+  console.log('Hora:', Date. ow());
+  siguiente();
+});
+
+// un substack de middleware muestra información de petición para cualquier tipo de petición HTTP al router /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('URL de solicitud:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    consola. og('Tipo de solicitud:', req. ethod);
+    next();
+  }
+);
+
+// un substack de middleware que maneja las solicitudes GET al router /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // si el ID de usuario es 0, saltar al siguiente router
+    if (req. aramas. d === '0') siguiente('ruta');
+    // de lo contrario pasar el control a la siguiente función de middleware en esta pila
+    más siguiente();
+  },
+  (req, res, next) => {
+    // renderiza una página regular
+    res. ender('regular');
+  }
+);
+
+// manejador para la ruta /user/:id, que renderiza una página especial
+router. et('/user/:id', (req, res, next) => {
+  consola. og(req.params.id);
+  res.render('special');
+});
+
+// monta el router en la aplicación
+app.use('/', router);
+```
+
+Para omitir el resto de las funciones de middleware del enrutador, llama a `next('router')`
+para pasar el control de vuelta fuera de la instancia del enrutador.
+
+Este ejemplo muestra un substack de middleware que maneja peticiones GET a la ruta `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// predice el enrutador con un cheque y rescinda cuando sea necesario enrutador
+. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa el enrutador y 401 cualquier cosa que caiga a través de
+aplicación. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Middleware de manejo de errores
+
+<Alert type="alerta">
+
+Middleware manejado por errores siempre toma _four_ argumentos. Debe proporcionar cuatro argumentos para
+identificarlo como una función de middleware que maneja errores. Incluso si no necesitas usar el objeto `next`
+, debes especificarlo para mantener la firma. De lo contrario, el objeto `siguiente` será
+interpretado como middleware regular y fallará al manejar errores.
+
+</Alert>
+
+Define las funciones de middleware de la misma manera que otras funciones de middleware, excepto con cuatro argumentos en lugar de tres, específicamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para más detalles sobre el middleware de manejo de errores, vea: [Gestión de errores](/en/guide/error-handling).
+
+## Middleware incorporado
+
+A partir de la versión 4.x, Express ya no depende de [Connect](https://github.com/senchalabs/connect). Las funciones
+del middleware que anteriormente estaban incluidas con Express están ahora en módulos separados; vea [la lista de funciones de middleware](https://github.com/senchalabs/connect#middleware).
+
+Express tiene las siguientes funciones de middleware incorporadas:
+
+- [express.static](/en/5x/api#express.static) sirve activos estáticos como archivos HTML, imágenes, etc.
+- [express.json](/en/5x/api#express.json) analiza las solicitudes entrantes con cargas útiles JSON. **NOTA: Disponible con Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analiza las solicitudes entrantes con payloads codificados por URL. **NOTA: Disponible con Express 4.16.0+**
+
+## Middleware de terceros
+
+Utilice middleware de terceros para añadir funcionalidad a aplicaciones Express.
+
+Instale el módulo Node.js para la funcionalidad requerida, luego guárdelo en su aplicación a nivel de aplicación o a nivel de enrutador.
+
+El siguiente ejemplo ilustra la instalación y carga de la función middleware `cookie-parser`.
+
+```bash
+$ npm instalar cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cargar el middleware de análisis de cookies
+app.use(cookieParser());
+```
+
+Para una lista parcial de funciones de middleware de terceros que se utilizan comúnmente con Express, vea: [Middleware de terceros](../resources/middleware).
diff --git a/src/content/docs/es/5x/guide/using-template-engines.mdx b/src/content/docs/es/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..49818704ce
--- /dev/null
+++ b/src/content/docs/es/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utilizando motores de plantillas con Express
+description: Descubra cómo integrar y utilizar motores de plantillas como Pug, Handlebars y EJS con Express.js para renderizar páginas HTML dinámicas eficientemente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un _template engine_ le permite usar plantillas estáticas en su aplicación. En tiempo de ejecución, el motor de plantillas reemplaza variables
+en un archivo de plantilla con valores reales. y transforma la plantilla en un archivo HTML enviado al cliente.
+Este enfoque facilita el diseño de una página HTML.
+
+El [generador de aplicaciones Express](/en/starter/generator) utiliza [Pug](https://pugjs.org/api/getting-started.html) como predeterminado, pero también soporta [Handlebars](https://www.npmjs.com/package/handlebars), y [EJS](https://www.npmjs.com/package/ejs), entre otros.
+
+Para renderizar archivos de plantilla, establezca las siguientes [propiedades de configuración de aplicación](/en/4x/api#app.set), en el `app.js` por defecto creado por el generador:
+
+- `vistas`, el directorio donde están ubicados los archivos de plantilla. Ej: `app.set('vistas', './views')`.
+  Esto por defecto es el directorio `views` en el directorio raíz de la aplicación.
+- `ver engine`, el motor de plantillas a usar. Por ejemplo, para usar el motor de plantillas Pug: `app.set('view engine', 'pug')`.
+
+A continuación, instale el correspondiente paquete npm del motor de plantillas; por ejemplo para instalar Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alerta">
+Motores de plantillas compatibles con Expresiones, tales como Pug exportar una función llamada `__express(filePath, options, callback)`,
+que `res.render()` llama para renderizar el código de plantilla.
+
+Algunos motores de plantillas no siguen esta convención. La biblioteca [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+sigue esta convención mapeando todos los motores de plantillas populares de Node.js, y por lo tanto funciona perfectamente dentro de Express.
+
+</Alert>
+
+Después de que el motor de vista esté definido, no tiene que especificar el motor o cargar el módulo de motor de plantillas en su aplicación;
+Express carga el módulo internamente, por ejemplo:
+
+```js
+app.set('ver motor', 'pug');
+```
+
+Luego, crea un archivo de plantilla Pug llamado `index.pug` en el directorio `views`, con el siguiente contenido:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Crea una ruta para representar el archivo `index.pug`. Si la propiedad `view engine` no está definida,
+debe especificar la extensión del archivo `view`. De lo contrario, puede omitirlo.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: '¡Hola!' });
+});
+```
+
+Cuando hagas una solicitud a la página de inicio, el archivo `index.pug` será renderizado como HTML.
+
+La caché del motor de vistas no almacena en caché el contenido de la salida de la plantilla, sólo la misma plantilla subyacente. La vista todavía se vuelve a procesar con cada petición incluso cuando la caché está encendida.
diff --git a/src/content/docs/es/5x/guide/writing-middleware.mdx b/src/content/docs/es/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..f1543b8c89
--- /dev/null
+++ b/src/content/docs/es/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Escribiendo middleware para uso en aplicaciones Express
+description: Aprenda cómo escribir funciones personalizadas de middleware para aplicaciones Express.js, incluyendo ejemplos y mejores prácticas para mejorar la gestión de peticiones y respuestas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Las funciones _Middleware_ son funciones que tienen acceso al [objeto de solicitud](/en/5x/api#req) (`req`), el [objeto de respuesta](/en/5x/api#res) (`res`), y la función `next` en el ciclo de solicitud y respuesta de la aplicación. La función `siguiente` es una función en el router Express que, cuando se invoca, ejecuta el middleware sucediendo al middleware actual.
+
+Las funciones de Middleware pueden realizar las siguientes tareas:
+
+- Ejecutar cualquier código.
+- Realizar cambios en la solicitud y en los objetos de respuesta.
+- Terminar el ciclo de solicitud de respuesta.
+- Llama al siguiente middleware en la pila.
+
+Si la función actual de middleware no termina el ciclo de solicitud de respuesta, debe llamar a `next()` para pasar el control a la siguiente función de middleware. De lo contrario, la solicitud quedará colgada.
+
+La siguiente figura muestra los elementos de una llamada a una función de middleware:
+
+![Elementos de una llamada a función middleware](/images/express-mw.png)
+
+A partir de Express 5, las funciones de middleware que devuelven una Promise llamarán `next(value)` cuando rechacen o lancen un error. `next` será llamado con el valor rechazado o con el error arrojado.
+
+## Ejemplo
+
+He aquí un ejemplo de una simple aplicación "Hola Mundo" Express.
+El resto de este artículo definirá y añadirá tres funciones de middleware a la aplicación:
+una llamada `myLogger` que imprime un simple mensaje de registro, uno llamado `requestTime` que
+muestra la marca de tiempo de la petición HTTP, y uno llamado `validateCookies` que valida las cookies entrantes.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('¡Hola Mundo!');
+});
+
+app.listen(3000);
+```
+
+### Función Middleware myLogger
+
+Aquí hay un ejemplo simple de una función middleware llamada "myLogger". Esta función solo imprime
+"LOGGED" cuando una solicitud a la aplicación pasa a través de ella. La función middleware está asignada a una variable
+llamada `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alerta">
+
+Tenga en cuenta la llamada anterior a `next()`. Llamar a esta función invoca la siguiente función de middleware en
+la aplicación. La función `next()` no es parte del Nodo. s o Express API, pero es el tercer argumento
+que se pasa a la función middleware. La función `next()` podría ser nombrada cualquier cosa,
+pero por convención siempre se llama "siguiente". Para evitar la confusión, utilice siempre esta convención.
+
+</Alert>
+
+Para cargar la función middleware, llama a `app.use()`, especificando la función middleware.
+Por ejemplo, el siguiente código carga la función middleware `myLogger` antes de la ruta a la ruta raíz (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  consola.og('LOGGED');
+  siguiente();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('¡Hola Mundo!');
+});
+
+app.listen(3000);
+```
+
+Cada vez que la aplicación recibe una solicitud, imprime el mensaje "LOGGED" en el terminal.
+
+El orden de carga de middleware es importante: las funciones de middleware que se cargan primero también se ejecutan primero.
+
+Si `myLogger` es cargado después de la ruta a la ruta raíz, la solicitud nunca llega a ella y la aplicación no imprime "LOGGED", porque el manejador de rutas de la ruta raíz termina el ciclo de solicitud de respuesta.
+
+La función Middleware `myLogger` simplemente imprime un mensaje, luego pasa la solicitud a la siguiente función de middleware en la pila llamando a la función `next()`.
+
+### Tiempo de solicitud de la función Middleware
+
+A continuación, crearemos una función de middleware llamada "requestTime" y agregaremos una propiedad llamada `requestTime`
+al objeto de la solicitud.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+La aplicación ahora utiliza la función de middleware `requestTime`. Además, la función de callback de la ruta raíz utiliza la propiedad que la función middleware añade a `req` (el objeto de la solicitud).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = '¡Hola Mundo!<br>';
+  responseText += `<small>Solicitado en: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Cuando hace una solicitud a la raíz de la aplicación, la aplicación ahora muestra la marca de tiempo de su solicitud en el navegador.
+
+### Función Middleware validateCookies
+
+Finalmente, crearemos una función de middleware que valida las cookies entrantes y envía una respuesta 400 si las cookies no son válidas.
+
+Aquí hay una función de ejemplo que valida las cookies con un servicio externo asíncrono.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Aquí usamos el [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware para analizar las cookies entrantes del objeto `req` y pasarlas a nuestra función `cookieValidator`. El middleware `validateCookies` devuelve una Promesa que al rechazar activará automáticamente nuestro gestor de errores.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// manejador de errores
+app.se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alerta">
+
+Observe cómo `next()` es llamado después de `await cookieValidator(req.cookies)`. Esto asegura que si
+`cookieValidator` resuelve, se llamará al siguiente middleware en la pila. Si pasas algo
+a la función `next()` (excepto la cadena `'route'` o `'router'`), Express considera que la actual petición
+es un error y se saltará cualquier función
+que no sea de manejo de enrutamiento y middleware restante.
+
+</Alert>
+
+Debido a que tiene acceso al objeto de solicitud, el objeto de respuesta, la siguiente función de middleware en la pila, y el nodo entero. s API, las posibilidades con funciones middleware son infinitas.
+
+Para más información sobre middleware exprés, vea: [Usando middleware exprés](/en/guide/using-middleware).
+
+## Middleware configurable
+
+Si necesita que su middleware sea configurable, exporte una función que acepte un objeto de opciones u otros parámetros, , que luego devuelve la implementación de middleware basada en los parámetros de entrada.
+
+Archivo: `my-middleware.js`
+
+```js
+módulo.xports = function (options) {
+  return function (req, res, next) {
+    // Implementar la función middleware basada en el objeto de opciones
+    siguiente();
+  };
+};
+```
+
+El middleware ahora puede ser usado como se muestra a continuación.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Consulte [cookie-session](https://github.com/expressjs/cookie-session) y [compression](https://github.com/expressjs/compression) para ver ejemplos de middleware configurable.
diff --git a/src/content/docs/es/5x/starter/basic-routing.mdx b/src/content/docs/es/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..51d6b399d2
--- /dev/null
+++ b/src/content/docs/es/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Ruta básica
+description: Aprenda los fundamentos de la enrutamiento en aplicaciones Express.js, incluyendo cómo definir rutas, manejar métodos HTTP y crear manejadores de rutas para su servidor web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Enrutamiento_ se refiere a determinar cómo responde una aplicación a una solicitud de cliente a un punto final en particular, que es una URI (o ruta) y un método específico de petición HTTP (GET, POST, etc.).
+
+Cada ruta puede tener una o más funciones manejadoras, que se ejecutan cuando la ruta es igualada.
+
+La definición de ruta tiene la siguiente estructura:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Donde:
+
+- `app` es una instancia de `express`.
+- `METHOD` es un [método de solicitud HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), en minúsculas.
+- `PATH` es una ruta en el servidor.
+- `HANDLER` es la función ejecutada cuando la ruta es coincidente.
+
+<Alert type="alerta">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Si no estás familiarizado con la creación de una aplicación e iniciarla, consulta el Hola mundo
+ejemplo.
+
+</Alert>
+
+Los siguientes ejemplos ilustran la definición de rutas simples.
+
+Responder con `¡Hola Mundo!` en la página principal:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hola Mundo!');
+});
+```
+
+Responder a una solicitud POST en la ruta raíz (`/`), la página de inicio de la aplicación:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Obtener una solicitud POST');
+});
+```
+
+Responder a una solicitud PUT a la ruta `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Obtener una solicitud PUT en /user');
+});
+```
+
+Responder a una solicitud DELETE a la ruta `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Obtuvo una solicitud DELETE en /user');
+});
+```
+
+Para más detalles sobre enrutamiento, vea la [guía de enrutamiento](/en/guide/routing).
diff --git a/src/content/docs/es/5x/starter/examples.mdx b/src/content/docs/es/5x/starter/examples.mdx
new file mode 100644
index 0000000000..7584ec7480
--- /dev/null
+++ b/src/content/docs/es/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Ejemplos exprés
+description: Explore una colección de ejemplos de aplicaciones de Express.js que cubren varios casos de uso, integraciones y configuraciones avanzadas para ayudarle a aprender y construir sus proyectos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Esta página contiene una lista de ejemplos usando Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Autenticación con nombre de usuario y contraseña
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - negociación de contenido HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Trabajando con sesiones basadas en cookies
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Trabajando con galletas
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transfiriendo archivos al cliente
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Trabajando con plantillas JavaScript embebidas (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Creando páginas de error
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Trabajando con middleware de error
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Manejador de solicitudes simple
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown como motor de plantillas
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Trabajando con varios enrutadores Express
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - Controladores estilo MVC
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Trabajando con parámetros de ruta
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Múltiples operaciones HTTP en el mismo recurso
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organizar rutas usando un mapa
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Trabajando con middleware de ruta
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizando rutas por cada recurso
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - API de búsqueda
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - Sesiones de usuario
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Subrayando archivos estáticos
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Trabajando con hosts virtuales
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Procesar dinámicamente las vistas
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Servicio de API simple
+
+## Ejemplos adicionales
+
+Estos son algunos ejemplos adicionales con integraciones más amplias.
+
+<Alert type="advertencia">
+
+Esta información se refiere a sitios de terceros, productos o módulos que no son mantenidos por el equipo de
+Expressjs. La lista aquí no constituye un aviso o recomendación del equipo de proyecto
+Expressjs.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Aplicación completa con Express y Next.js usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - API REST con Express en TypeScript usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
diff --git a/src/content/docs/es/5x/starter/faq.md b/src/content/docs/es/5x/starter/faq.md
new file mode 100644
index 0000000000..6f808c230e
--- /dev/null
+++ b/src/content/docs/es/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Encuentre respuestas a preguntas frecuentes sobre Express.js, incluyendo temas sobre estructura de aplicaciones, modelos, autenticación, motores de plantillas, manejo de errores, y más.
+---
+
+## ¿Cómo debo estructurar mi aplicación?
+
+No hay una respuesta definitiva a esta pregunta. La respuesta depende
+de la escala de tu aplicación y del equipo implicado. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Las rutas y otra lógica específica de la aplicación pueden vivir tantos archivos
+como desee, en cualquier estructura de directorio que prefiera. View the following
+examples for inspiration:
+
+- [Rutas listadas](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mapa de ruta](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Además, existen extensiones de terceros para Express, que simplifican algunos de estos patrones:
+
+- [Rutas de recursos](https://github.com/expressjs/express-resource)
+
+## ¿Cómo defino los modelos?
+
+Express no tiene noción de una base de datos. Este concepto es
+dejado a los módulos de Nodo de terceros, permitiéndote una interfaz
+con casi cualquier base de datos.
+
+Vea [LoopBack](http://loopback.io) para un framework basado en Expresiones centrado en modelos.
+
+## ¿Cómo puedo autenticar usuarios?
+
+Authentication is another opinionated area that Express does not
+venture into. Puede utilizar cualquier esquema de autenticación que desee.
+Para un esquema simple de nombre de usuario / contraseña, vea [este ejemplo](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## ¿Qué motores de plantillas soporta Express?
+
+Express soporta cualquier motor de plantillas que cumpla con la firma `(ruta, locales, callback)`.
+Para normalizar las interfaces del motor de plantillas y la caché, consulte el proyecto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+para obtener soporte. Los motores de plantillas no listados pueden seguir soportando la firma Express.
+
+Para obtener más información, consulte [Usar motores de plantilla con Express](/en/guide/using-template-engines).
+
+## ¿Cómo puedo manejar las respuestas 404?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. Este comportamiento es
+porque una respuesta 404 simplemente indica la ausencia de trabajo adicional por hacer;
+en otras palabras, Express ha ejecutado todas las funciones y rutas de middleware,
+y ha encontrado que ninguno de ellos respondió. Todo lo que necesitas hacer
+es añadir una función de middleware en la parte inferior de la pila (debajo de todas las demás funciones)
+para manejar una respuesta 404:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Añadir rutas dinámicamente en tiempo de ejecución en una instancia de `express.Router()`
+para que las rutas no sean reemplazadas por una función de middleware.
+
+## ¿Cómo configuro un gestor de errores?
+
+Usted define middleware que maneja errores de la misma manera que otros middleware,
+excepto con cuatro argumentos en lugar de tres; específicamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para más información, vea [Gestión de errores] (/en/guide/error-handling).
+
+## ¿Cómo renderizo HTML plano?
+
+¡No lo tienes! No hay necesidad de "render" HTML con la función `res.render()`.
+Si tienes un archivo específico, usa la función `res.sendFile()`.
+Si está sirviendo muchos activos de un directorio, utilice la función de middleware `express.static()`
+.
+
+## ¿Qué versión de Node.js requiere Express?
+
+- [Express 4.x](/en/4x/api) requiere 0.10 o superior de Node.js.
+- [Express 5.x](/en/5x/api) requiere Node.js 18 o superior.
diff --git a/src/content/docs/es/5x/starter/generator.mdx b/src/content/docs/es/5x/starter/generator.mdx
new file mode 100644
index 0000000000..2755232b43
--- /dev/null
+++ b/src/content/docs/es/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Generador de aplicaciones urgente
+description: Aprenda cómo utilizar la herramienta del generador de aplicaciones Express para crear rápidamente un esqueleto para sus aplicaciones Express.js, configuración de streamlining y configuración.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilice la herramienta generadora de aplicaciones, `express-generator`, para crear rápidamente un esqueleto de aplicación.
+
+Puede ejecutar el generador de aplicaciones con el comando `npx` (disponible en Node.js 8.2.0).
+
+```bash
+$ generador de expresiones npx
+```
+
+Para versiones anteriores de Node, instale el generador de aplicaciones como un paquete global npm y luego ejecute:
+
+```bash
+$ npm install -g express-generator
+$ expreso
+```
+
+Mostrar las opciones de comando con la opción `-h`:
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opciones:
+
+    -h, --help output output use information
+        --version output output the version number
+    -e, --ejs añadir soporte para motores ejs
+        --hbs añadir soporte para motores handlebars
+        --pug añadir soporte para pug engine
+    -H, --hogan añadir hogan. s engine soporta
+        --no-view generar sin el motor de vista
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (por defecto jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|Ninguno|brújula|sass) (por defecto a simple css)
+        --git add . itignore
+    -f, --force en directorio no vacío
+```
+
+Por ejemplo, lo siguiente crea una aplicación Express llamada _myapp_. La aplicación se creará en una carpeta llamada _myapp_ en el directorio de trabajo actual y el motor de vistas se establecerá en <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   crear : miapp/rutas/usuarios. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ★
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Luego instale dependencias:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+En MacOS o Linux, ejecuta la aplicación con este comando:
+
+```bash
+$ DEBUG=miapp:* npm inicio
+```
+
+En Windows Command Prompt, utilice este comando:
+
+```bash
+> establecer DEBUG=miapp:* & npm start
+```
+
+En Windows PowerShell, utilice este comando:
+
+```bash
+PS> $env:DEBUG='miapp:*'; npm start
+```
+
+Luego, carga `http://localhost:3000/` en tu navegador para acceder a la aplicación.
+
+La aplicación generada tiene la siguiente estructura de directorios:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+La estructura de aplicaciones creada por el generador es sólo una de las muchas formas de estructurar aplicaciones Express.
+Siéntase libre de usar esta estructura o modificarla para que se adapte mejor a sus necesidades.
+
+</Alert>
diff --git a/src/content/docs/es/5x/starter/hello-world.mdx b/src/content/docs/es/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..5e74cf6bbb
--- /dev/null
+++ b/src/content/docs/es/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hola ejemplo de mundo
+description: Comienza con Express.js construyendo una sencilla aplicación 'Hola Mundo', demostrando la configuración básica y la creación de servidores para principiantes.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Incrustado a continuación es esencialmente la aplicación Express más simple que puede crear. Es una aplicación de archivo única
+&mdash; _no_ lo que obtendrías si utilizas el [generador Express](/en/starter/generator), que
+crea el andamio para una aplicación completa con numerosos archivos JavaScript, plantillas de Jade y subdirectorios
+para varios propósitos.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('¡Hola Mundo!');
+});
+
+app.listen(port, () => {
+  console.log(`Ejemplo de aplicación escuchando en el puerto ${port}`);
+});
+```
+
+Esta aplicación inicia un servidor y escucha en el puerto 3000 para las conexiones. La aplicación responde con "¡Hola Mundo!" para las solicitudes
+a la URL raíz (`/`) o _route_. Por cada otro camino, responderá con un **404 No Encontrado**.
+
+## Ejecutar localmente
+
+Primero cree un directorio llamado `myapp`, cámbielo y ejecute `npm init`. Luego, instala `express` como una dependencia, según la [guía de instalación](/en/starter/installing).
+
+En el directorio `myapp`, crea un archivo llamado `app.js` y copia el código del ejemplo anterior.
+
+<Alert type="alerta">
+
+El `req` (petición) y `res` (respuesta) son los mismos objetos exactos que el Node proporciona, así que puedes
+invocar `req. ipe()`, `req.on('data', callback)`, y cualquier otra cosa que hagas sin Express
+involucradas.
+
+</Alert>
+
+Ejecutar la aplicación con el siguiente comando:
+
+```bash
+$ node app.js
+```
+
+Luego, carga `http://localhost:3000/` en un navegador para ver la salida.
diff --git a/src/content/docs/es/5x/starter/installing.mdx b/src/content/docs/es/5x/starter/installing.mdx
new file mode 100644
index 0000000000..25bf668243
--- /dev/null
+++ b/src/content/docs/es/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Instalando
+description: Aprenda cómo instalar Express.js en su entorno Node.js, incluyendo la configuración del directorio de su proyecto y la gestión de dependencias con npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Antes de comenzar, asegúrese de que tiene instalado [Node.js](https://nodejs.org/) 18 o superior. Luego, crea un directorio para tu aplicación y navega por ella.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Usa el comando `npm init` para crear un archivo `package.json` para tu aplicación.
+Para más información sobre el funcionamiento de `package.json`, consulta [Especificaciones del manejo de package.json de npm](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Este comando te pide varias cosas, como el nombre y la versión de tu aplicación.
+Por ahora, puede simplemente pulsar RETURN para aceptar los valores predeterminados para la mayoría de ellos, con la siguiente excepción:
+
+```
+punto de entrada: (index.js)
+```
+
+Introduzca `app.js`, o lo que quiera que sea el nombre del archivo principal. Si desea que sea `index.js`, pulse RETURN para aceptar el nombre de archivo predeterminado sugerido.
+
+Ahora, instale Express en el directorio `myapp` y guárdelo en la lista de dependencias. Por ejemplo:
+
+```bash
+npm instalar Express
+```
+
+Para instalar Express temporalmente y no añadirlo a la lista de dependencias:
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/es/5x/starter/static-files.mdx b/src/content/docs/es/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..a614730632
--- /dev/null
+++ b/src/content/docs/es/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Comprobando archivos estáticos en Express
+description: Describa cómo servir archivos estáticos como imágenes, CSS y JavaScript en aplicaciones Express.js usando el middleware 'static' incorporado.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para servir archivos estáticos como imágenes, archivos CSS, y archivos JavaScript, utiliza la función middleware integrada `express.static` en Express.
+
+La firma de la función es:
+
+```js
+express.static(root, [options]);
+```
+
+El argumento `root` especifica el directorio raíz desde el cual servir activos estáticos.
+Para más información sobre el argumento `options`, vea [express.static](/en/5x/api#express.static).
+
+Por ejemplo, utiliza el siguiente código para servir imágenes, archivos CSS y archivos JavaScript en un directorio llamado `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Ahora, puedes cargar los archivos que están en el directorio `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express busca los archivos relativos al directorio estático, por lo que el nombre del directorio estático
+no es parte de la URL.
+
+</Alert>
+
+Para usar múltiples directorios de activos estáticos, llama a la función middleware `express.static` varias veces:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express busca los archivos en el orden en el que estableces los directorios estáticos con la función de middleware `express.static`.
+
+<Alert type="info">
+
+Para obtener mejores resultados, usa un proxy
+inverso caché para mejorar el rendimiento de
+sirviendo activos estáticos.
+
+</Alert>
+
+Para crear un prefijo de ruta virtual (donde la ruta no existe en el sistema de archivos) para archivos que son servidos por el `express. función tatic`, [especificar una ruta de montaje](/en/5x/api#app.use) para el directorio estático, como se muestra a continuación:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Ahora, puedes cargar los archivos que están en el directorio `public` desde el prefijo de ruta `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Sin embargo, la ruta que proporcionas a la función `express.static` es relativa al directorio desde el cual inicias tu proceso `node`. Si ejecuta la aplicación expresa desde otro directorio, es más seguro utilizar la ruta absoluta del directorio que desea servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Para más detalles sobre la función `serve-static` y sus opciones, vea [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/fr/4x/advanced/developing-template-engines.md b/src/content/docs/fr/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..8ddb890522
--- /dev/null
+++ b/src/content/docs/fr/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Développement de moteurs de gabarits pour Express
+description: Apprenez comment développer des moteurs de gabarits personnalisés pour Express.js en utilisant app.engine(), avec des exemples sur la création et l'intégration de votre propre logique de rendu de gabarits.
+---
+
+Utilisez la méthode `app.engine(ext, callback)` pour créer votre propre moteur de template. `ext` fait référence à l'extension de fichier, et `callback` est la fonction du moteur de gabarit, qui accepte les éléments suivants comme paramètres: l'emplacement du fichier, l'objet d'options et la fonction de rappel.
+
+Le code suivant est un exemple d'implémenter un moteur de gabarit très simple pour le rendu des fichiers `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Votre application sera maintenant en mesure d'afficher les fichiers `.ntl`. Créez un fichier nommé `index.ntl` dans le dossier `views` avec le contenu suivant.
+
+```pug
+#title#
+#message#
+```
+
+Ensuite, créez la route suivante dans votre application.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Lorsque vous faites une requête sur la page d'accueil, `index.ntl` sera rendu en HTML.
diff --git a/src/content/docs/fr/4x/guide/behind-proxies.mdx b/src/content/docs/fr/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..aa17a36f63
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Exprimez derrière les mandataires
+description: Apprenez à configurer les applications Express.js pour qu'elles fonctionnent correctement derrière les mandataires inversés, y compris en utilisant le paramètre proxy de confiance pour gérer les adresses IP du client.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Lorsque vous exécutez une application Express derrière un proxy inverse, certaines des API Express peuvent retourner des valeurs différentes de celles attendues. Pour ajuster pour cela, le paramètre `trust proxy` de l'application peut être utilisé pour exposer des informations fournies par le proxy inverse dans les API Express. Le problème le plus courant est les API express qui exposent l'adresse IP du client peut à la place afficher une adresse IP interne du proxy inverse.
+
+<Alert type="Infos">
+
+Lors de la configuration du paramètre `trust proxy`, il est important de comprendre la configuration exacte du proxy inverse
+. Puisque ce paramètre fera confiance aux valeurs fournies dans la requête, Il est important que
+la combinaison du paramètre dans Express corresponde à la façon dont le proxy inversé fonctionne.
+
+</Alert>
+
+Le paramètre de l'application `trust proxy` peut être défini à l'une des valeurs listées dans la table suivante.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Valeur</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Si `true`, l'adresse IP du client est comprise comme l'entrée la plus à gauche dans l'en-tête `X-Forwarded-For`.
+
+Si `false`, l'application est comprise comme faisant directement face au client et l'adresse IP du client est dérivée de `req.socket.remoteAddress`. Ceci est le paramètre par défaut.
+
+<Alert type="avertissement">
+Lorsque vous définissez sur `true`, il est important de s'assurer que le dernier proxy inversé fiable est de supprimer/écraser tous les en-têtes HTTP suivants : `X-Forwarded-For`, `X-Forwarded-Host`, et `X-Forwarded-Proto`, sinon il sera possible pour le client de fournir n'importe quelle valeur.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Adresses IP</td>
+<td markdown="1">
+Une adresse IP, un sous-réseau ou un tableau d'adresses IP et de sous-réseaux à confier comme étant un proxy inverse. La liste suivante montre les noms de sous-réseaux pré-configurés :
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Vous pouvez définir les adresses IP de l'une des façons suivantes :
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+Lorsqu'il est spécifié, les adresses IP ou les sous-réseaux sont exclus du processus de détermination de l'adresse, et l'adresse IP non fiable la plus proche du serveur d'application est déterminée comme l'adresse IP du client. Cela fonctionne en vérifiant si `req.socket.remoteAddress` est fiable. Si c'est le cas, alors chaque adresse dans `X-Forwarded-For` est vérifiée de droite à gauche jusqu'à la première adresse non fiable.
+
+</td>
+    </tr>
+    <tr>
+      <td>Nombre</td>
+<td markdown="1">
+Utilisez l'adresse qui est au plus `n` nombre de sauts loin de l'application Express. `req.socket.remoteAddress` est le premier saut, et le reste est recherché dans l'en-tête `X-Forwarded-For` de droite à gauche. Une valeur de `0` signifie que la première adresse non fiable serait `req.socket.remoteAddress`, c'est-à-dire qu'il n'y a pas de proxy inverse.
+
+<Alert type="avertissement">
+Lors de l'utilisation de ce paramètre, il est important de s'assurer qu'il n'y a pas de multiples, chemins différents vers l'application Express de sorte que le client peut être inférieur au nombre de sauts configurés, sinon il pourrait être possible pour le client de fournir n'importe quelle valeur.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Fonction</td>
+<td markdown="1">
+Implémentation de confiance personnalisée.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    retourne true; // les adresses IP
+  approuvées retournent false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Activer `trust proxy` aura l'impact suivant :
+
+<ul>
+  <li markdown="1">
+    La valeur de [req.hostname](/en/api#req.hostname) est dérivée de la valeur définie dans
+    l'en-tête `X-Forwarded-Host`, qui peut être définie par le client ou par le proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` peut être défini par le proxy inverse pour dire à l'application si c'est
+    `https` ou `http` ou même un nom invalide. Cette valeur est reflétée par
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Les valeurs [req.ip](/en/api#req.ip) et [req.ips](/en/api#req.ips) sont remplies en fonction de
+    l'adresse du socket et de l'en-tête `X-Forwarded-For`, à partir de la première adresse non
+    fiable.
+  </li>
+</ul>
+
+Le paramètre `trust proxy` est implémenté en utilisant le paquet [proxy-addr](https://www.npmjs.com/package/proxy-addr). Pour plus d'informations, voir sa documentation.
diff --git a/src/content/docs/fr/4x/guide/debugging.mdx b/src/content/docs/fr/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..04a54bbf25
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Débogage Express
+description: Apprenez comment activer et utiliser les journaux de débogage dans les applications Express.js en définissant la variable d'environnement DEBUG pour un dépannage amélioré.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Pour voir tous les journaux internes utilisés dans Express, définissez la variable d'environnement `DEBUG` à
+`express:*` lors du lancement de votre application.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Sous Windows, utilisez la commande correspondante.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+L'exécution de cette commande sur l'application par défaut générée par le [générateur express](/en/starter/generator) affiche la sortie suivante:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Lorsqu'une demande est faite à l'application, vous verrez les journaux spécifiés dans le code Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query : / +2ms
+  express:router expressInit : / +0ms
+  express:router favicon : / +0ms
+  express:router logger : / +1ms
+  express:router jsonParser : / +0ms
+  express:router urlencodedParser : / +1ms
+  express:router cookieParser : / +0ms
+  express:router stylus : / +0ms
+  express:router serveStatic : / +2ms
+  express:router : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index. ug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Pour voir les logs uniquement à partir de l'implémentation du routeur, définissez la valeur de `DEBUG` à `express:router`. De même, pour ne voir que les logs de l'implémentation de l'application, définissez la valeur de `DEBUG` à `express:application`, et ainsi de suite.
+
+## Applications générées par `express`
+
+Une application générée par la commande `express` utilise le module `debug` et son espace de noms de débogage est limité au nom de l'application.
+
+Par exemple, si vous avez généré l'application avec `$ express sample-app`, vous pouvez activer les instructions de débogage avec la commande suivante :
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+Vous pouvez spécifier plus d'un espace de noms de débogage en assignant une liste de noms séparés par des virgules :
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Options avancées
+
+Lors de l'exécution de Node.js, vous pouvez définir quelques variables d'environnement qui changeront le comportement du journal de débogage :
+
+| Nom                 | Objectif                                                         |
+| ------------------- | ---------------------------------------------------------------- |
+| `DEBUG`             | Active/désactive les espaces de noms de débogage spécifiques.    |
+| `DEBUG_COLORS`      | Utiliser ou non les couleurs dans la sortie de débogage.         |
+| `DEBUG_DEPTH`       | Profondeur de l'inspection des objets.                           |
+| `DEBUG_FD`          | Descripteur de fichier vers lequel écrire la sortie de débogage. |
+| `DEBUG_SHOW_HIDDEN` | Affiche les propriétés masquées sur les objets inspectés.        |
+
+<Alert type="Infos">
+
+Les variables d'environnement commençant par `DEBUG_` finissent par être converties en un objet d'options
+qui est utilisé avec les formats `%o`/`%O`. Voir la documentation Node.js pour
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) pour la liste complète
+.
+
+</Alert>
diff --git a/src/content/docs/fr/4x/guide/error-handling.mdx b/src/content/docs/fr/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..0bcd847565
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Gestion des erreurs
+description: Comprenez comment Express.js gère les erreurs dans le code synchrone et asynchrone et apprend à implémenter la gestion des erreurs personnalisées pour vos applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ fait référence à la façon dont Express attrape et traite les erreurs que
+se produisent de manière synchronisée et asynchrone. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Erreurs de capture
+
+Il est important de s'assurer qu'Express attrape toutes les erreurs qui se produisent lorsque
+exécute des gestionnaires de routes et des middleware.
+
+Les erreurs qui se produisent dans le code synchrone dans les gestionnaires de route et les middleware
+ne nécessitent aucun travail supplémentaire. If synchronous code throws an error, then Express will
+catch and process it. Par exemple :
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express va attraper cela tout seul.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Passez des erreurs à Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+À partir de Express 5, les gestionnaires de route et les middleware qui retournent une Promise
+appelleront automatiquement `next(value)` quand ils rejettent ou lancent une erreur.
+Par exemple :
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = wait getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Si `getUserById` lance une erreur ou un rejet, `next` sera appelé avec soit
+l'erreur émise ou la valeur rejetée. Si aucune valeur rejetée n'est fournie, `next`
+sera appelée avec un objet Error par défaut fourni par le routeur Express.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+Si le callback dans une séquence ne fournit aucune donnée, seulement des erreurs, vous pouvez simplifier
+ce code comme suit:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Dans l'exemple ci-dessus, `next` est fourni comme callback pour `fs.writeFile`,
+qui est appelé avec ou sans erreurs. S'il n'y a pas d'erreur, le second
+est exécuté, sinon Express attrape et traite l'erreur.
+
+Vous devez attraper les erreurs qui se produisent dans le code asynchrone invoqué par les gestionnaires de route ou
+middleware et les passer à Express pour le traitement. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    essayez {
+      throw new Error('BROKEN');
+    } attraper (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+L'exemple ci-dessus utilise un bloc `try...catch` pour attraper des erreurs dans le code
+asynchrone et les passer à Express. Si le bloc `try...catch`
+était omis, Express ne attrapera pas l'erreur car il ne fait pas partie du code du gestionnaire
+synchrone.
+
+Utilise des promesses pour éviter les frais généraux du bloc `essayer...catch` ou lorsque tu utilises les fonctions
+qui renvoient des promesses. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Les erreurs seront passées à Express.
+});
+```
+
+Puisque les promesses attrapent automatiquement à la fois les erreurs synchrones et les promesses rejetées,
+vous pouvez simplement fournir `next` car le gestionnaire de capture final et Express attrapera des erreurs,
+parce que le gestionnaire de capture est donné l'erreur comme premier argument.
+
+Vous pouvez également utiliser une chaîne de gestionnaires pour vous fier à l'erreur synchrone
+attrapant, en réduisant le code asynchrone à quelque chose de trivial. Par exemple :
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = data;
+      next(err);
+    });
+  },
+  fonction (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+L'exemple ci-dessus a quelques déclarations triviales de l'appel `readFile`
+. Si `readFile` cause une erreur, alors il passe l'erreur à Express, sinon vous
+revenez rapidement au monde de la gestion des erreurs synchrones dans le prochain gestionnaire
+de la chaîne. Ensuite, l'exemple ci-dessus tente de traiter les données. Si cela échoue, alors le gestionnaire d'erreurs synchrone
+l'attrapera. Si vous aviez fait ce traitement à l'intérieur de
+la callback `readFile`, alors l'application pourrait quitter et les gestionnaires d'erreur
+Express ne s'exécuteraient pas.
+
+Quelle que soit la méthode que vous utilisez, si vous voulez que les gestionnaires d'erreur Express soient appelés et que l'application
+survive, vous devez vous assurer qu'Express reçoit l'erreur.
+
+## Le gestionnaire d'erreur par défaut
+
+Express est livré avec un gestionnaire d'erreur intégré qui prend en charge toutes les erreurs qui peuvent être rencontrées dans l'application. Cette fonction middleware par défaut est ajoutée à la fin de la pile de fonctions du middleware.
+
+Si vous passez une erreur à `next()` et que vous ne la gérez pas dans un gestionnaire d'erreur personnalisé
+, il sera géré par le gestionnaire d'erreur intégré ; l'erreur sera
+écrite au client avec la trace de la pile. La trace de la pile n'est pas incluse
+dans l'environnement de production.
+
+<Alert type="Infos">
+
+Définissez la variable d'environnement `NODE_ENV` à `production`, pour exécuter l'application en mode production.
+
+</Alert>
+
+Lorsqu'une erreur est écrite, les informations suivantes sont ajoutées à la réponse
+:
+
+- Le `res.statusCode` est défini à partir de `err.status` (ou `err.statusCode`). Si
+  cette valeur est en dehors de la plage 4xx ou 5xx, elle sera définie à 500.
+- Le `res.statusMessage` est défini selon le code de statut.
+- Le corps sera le HTML du message de code de statut lorsque l'environnement de production
+  , sinon sera `err.stack`.
+- N'importe quel en-tête spécifié dans un objet `err.headers`.
+
+Si vous appelez `next()` avec une erreur après avoir commencé à écrire la réponse
+(par exemple, si vous rencontrez une erreur lors du streaming de la réponse
+au client), le gestionnaire d'erreur par défaut Express ferme la connexion
+et échoue la requête.
+
+Ainsi, lorsque vous ajoutez un gestionnaire d'erreurs personnalisé, vous devez déléguer à
+le gestionnaire d'erreur Express par défaut, lorsque les en-têtes
+ont déjà été envoyés au client :
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Notez que le gestionnaire d'erreur par défaut peut être déclenché si vous appelez `next()` avec une erreur
+dans votre code plusieurs fois, même si une gestion personnalisée des erreurs est en place.
+
+D'autres erreurs de gestion du middleware peuvent être trouvées dans [middleware Express](/en/resources/middleware).
+
+## Écriture des gestionnaires d'erreurs
+
+Définissez les fonctions du middleware de la même manière que les autres fonctions du middleware,
+excepté les fonctions de gestion des erreurs ont quatre arguments au lieu de trois:
+`(err, req, res, next)`. Par exemple :
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Quelque chose s'est cassé !');
+});
+```
+
+Vous définissez le middleware en dernier lieu, après d'autres appels `app.use()` et routage des appels; par exemple:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    étendu: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // logique
+});
+```
+
+Les réponses provenant d'une fonction middleware peuvent être dans n'importe quel format, comme une page d'erreur HTML, un message simple ou une chaîne JSON.
+
+Pour des raisons organisationnelles (et pour un cadre de plus haut niveau), vous pouvez définir
+plusieurs fonctions de gestion des erreurs du middleware, tout comme vous le feriez avec les fonctions
+régulières du middleware. Par exemple, pour définir un gestionnaire d'erreurs
+pour les requêtes faites en utilisant `XHR` et ceux sans :
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+application.se(
+  bodyParser.urlencoded({
+    étendu: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+Dans cet exemple, les génériques `logErrors` peuvent écrire la requête et les informations d'erreur
+à `stderr`, par exemple :
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Aussi dans cet exemple, `clientErrorHandler` est défini comme suit ; dans ce cas, l'erreur est explicitement passée au suivant.
+
+Notez que lorsque _not_ appelez "next" dans une fonction de gestion des erreurs, vous êtes responsable de l'écriture (et de la fin) de la réponse. Sinon, ces demandes seront « bloquées » et ne seront pas admissibles au ramassage des déchets.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Quelque chose a échoué!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implémenter la fonction "catch-all" `errorHandler` comme suit (par exemple):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Si vous avez un gestionnaire de route avec plusieurs fonctions de rappel, vous pouvez utiliser le paramètre `route` pour passer au gestionnaire de route suivant. Par exemple :
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user. asPaid) {
+      // continue à gérer cette requête
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent. ind(err, doc) => {
+      if (err) return next(err);
+      res. son(doc);
+    });
+  }
+);
+```
+
+Dans cet exemple, le gestionnaire `getPaidContent` sera ignoré, mais tous les gestionnaires restants dans `app` pour `/a_route_behind_paywall` continueront d'être exécutés.
+
+<Alert type="Infos">
+
+Les appels à `next()` et `next(err)` indiquent que le gestionnaire actuel est complet et dans quel état.
+`next(err)` sautera tous les gestionnaires restants de la chaîne, à l'exception de ceux qui sont configurés à
+gérer les erreurs comme décrit ci-dessus.
+
+</Alert>
diff --git a/src/content/docs/fr/4x/guide/overriding-express-api.md b/src/content/docs/fr/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..fdd81c674a
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Outrepasser l'API Express
+description: Découvrez comment personnaliser et étendre l'API Express.js en écrasant les méthodes et les propriétés sur les objets de demande et de réponse à l'aide de prototypes.
+---
+
+L'API Express se compose de différentes méthodes et propriétés sur les objets de requête et de réponse. Celles-ci sont héritées du prototype. Il y a deux points d'extension pour l'API Express :
+
+1. Les prototypes globaux à `express.request` et `express.response`.
+2. Prototypes spécifiques à l'application à `app.request` et `app.response`.
+
+Modifier les prototypes globaux affectera toutes les applications Express chargées dans le même processus. Si vous le souhaitez, les modifications peuvent être apportées à l'application en modifiant uniquement les prototypes spécifiques à l'application après avoir créé une nouvelle application.
+
+## Méthodes
+
+Vous pouvez remplacer la signature et le comportement des méthodes existantes avec vos propres méthodes en assignant une fonction personnalisée.
+
+Voici un exemple de surcharge du comportement de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+L'implémentation ci-dessus modifie complètement la signature originale de `res.sendStatus`. Il accepte maintenant un code de statut, un type d'encodage, et le message à envoyer au client.
+
+La méthode surchargée peut maintenant être utilisée de cette manière:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Propriétés
+
+Les propriétés de l'API Express sont soit :
+
+1. Propriétés assignées (ex: `req.baseUrl`, `req.originalUrl`)
+2. Défini comme getters (ex: `req.secure`, `req.ip`)
+
+Puisque les propriétés de la catégorie 1 sont assignées dynamiquement sur les objets `request` et `response` dans le contexte du cycle de réponse de la requête courante, leur comportement ne peut pas être remplacé.
+
+Les propriétés de la catégorie 2 peuvent être écrasées en utilisant l'API des extensions API Express.
+
+Le code suivant réécrit comment la valeur de `req.ip` doit être dérivée. Maintenant, il retourne simplement la valeur de l'en-tête de la requête `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+Afin de fournir l'API Express, les objets de requête/réponse passés à Express (via `app(req, res)`, par exemple) doivent hériter de la même chaîne de prototypes. Par défaut, c'est `http.IncomingRequest.prototype` pour la requête et `http.ServerResponse.prototype` pour la réponse.
+
+Sauf si nécessaire, il est recommandé de le faire uniquement au niveau de l'application, plutôt qu'au niveau mondial. Veillez également à ce que le prototype utilisé corresponde le plus près possible à la fonctionnalité des prototypes par défaut.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/fr/4x/guide/routing.mdx b/src/content/docs/fr/4x/guide/routing.mdx
new file mode 100644
index 0000000000..3c009b7b16
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routage
+description: Apprenez à définir et utiliser des routes dans les applications Express.js, y compris les méthodes de trajet, les chemins de trajet, les paramètres et l'utilisation du routeur pour le routage modulaire.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ indique comment les terminaux (URIs) d'une application répondent aux requêtes du client.
+Pour une introduction au routage, voir [Routage de base](/en/starter/basic-routing).
+
+Vous définissez le routage à l'aide des méthodes de l'objet Express `app` qui correspondent aux méthodes HTTP;
+par exemple, `app. et()` pour gérer les requêtes GET et `app.post` pour gérer les requêtes POST. Pour une liste complète,
+voir [app.METHOD](/en/5x/api#app.METHOD). Vous pouvez également utiliser [app.all()](/en/5x/api#app.all) pour gérer toutes les méthodes HTTP et [app. se()](/en/5x/api#app.use) à
+spécifient le middleware comme fonction de callback (Voir [Utilisation du middleware](/en/guide/using-middleware) pour plus de détails).
+
+Ces méthodes de routage spécifient une fonction de rappel (parfois appelée "fonctions de gestionnaire") appelée lorsque l'application reçoit une requête vers la route spécifiée (endpoint) et la méthode HTTP. En d'autres termes, l'application "écoute" les requêtes qui correspondent à la(les) route(s) spécifiée(s) et à la(les) méthode(s), et quand il détecte une correspondance, il appelle la fonction de rappel spécifiée.
+
+En fait, les méthodes de routage peuvent avoir plus d'une fonction de rappel en tant qu'arguments.
+Avec plusieurs fonctions de rappel, il est important de fournir `next` comme argument à la fonction de callback puis appeler `next()` dans le corps de la fonction pour distribuer le contrôle
+au prochain rappel.
+
+Le code suivant est un exemple de route très basique.
+
+```js
+const express = require('express');
+const app = express();
+
+// répond avec "bonjour le monde" lorsqu'une demande GET est faite à l'application
+de la page d'accueil. et('/', (req, res) => {
+  res.send('bonjour le monde');
+});
+```
+
+## Méthodes de la route
+
+Une méthode de route est dérivée d'une des méthodes HTTP, et est attachée à une instance de la classe `express`.
+
+Le code suivant est un exemple de routes qui sont définies pour le `GET` et les méthodes `POST` à la racine de l'application.
+
+```js
+// Route de la méthode GET
+app.get('/', (req, res) => {
+  res. end('Requête GET sur la page d'accueil');
+});
+
+// La méthode POST route
+app. ost('/', (req, res) => {
+  res.send('Requête POST sur la page d'accueil');
+});
+```
+
+Express supporte les méthodes qui correspondent à toutes les méthodes de requête HTTP : `get`, `post`, et ainsi de suite.
+Pour une liste complète, voir [app.METHOD](/en/5x/api#app.METHOD).
+
+Il y a une méthode de routage spéciale, `app.all()`, utilisée pour charger les fonctions du middleware à un chemin pour _toutes_ les méthodes de requête HTTP. Par exemple, le gestionnaire suivant est exécuté pour les requêtes vers la route `"/secret"` si vous utilisez `GET`, `POST`, `PUT`, `DELETE`, ou toute autre méthode de requête HTTP supportée dans le module [http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accéder à la section secrète ...');
+  next(); // passer le contrôle au prochain gestionnaire
+});
+```
+
+## Chemins de la route
+
+Les chemins de la route, en combinaison avec une méthode de requête, définissent les points de terminaison à partir desquels les requêtes peuvent être faites. Les chemins de route peuvent être des chaînes, des chaînes de caractères ou des expressions régulières.
+
+<Alert type="Alerte">
+
+En express 5, les caractères `? , `+`, `\*`, `[]`et `()\` sont gérés différemment de la version
+4, veuillez consulter le [guide de migration](/en/guide/migrating-5#path-syntax) pour plus d'informations.
+
+</Alert>
+
+<Alert type="Alerte">
+
+Dans l'expression expresse 4, des caractères d'expression régulière tels que `$` doivent être échappés avec un `\`.
+
+</Alert>
+
+<Alert type="Infos">
+
+Express utilise [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) pour correspondre aux chemins de la route
+; consultez la documentation path-to-regexp pour toutes les possibilités dans la définition des chemins d'itinéraire.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) est un outil pratique pour
+qui teste les routes Express de base, bien qu'il ne supporte pas la recherche de masques.
+
+</Alert>
+
+<Alert type="warning">Les chaînes de requête ne font pas partie du chemin de la route.</Alert>
+
+### Chemins de route basés sur des chaînes de caractères
+
+Ce chemin de route correspond aux requêtes vers la route racine, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Ce chemin de route correspond aux requêtes à `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Ce chemin de route correspondra aux requêtes à `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Chemins de route basés sur des chaînes de caractères
+
+<Alert type="Alerte">
+
+Les masques de chaînes de caractères dans Express 5 ne fonctionnent plus. Veuillez vous référer au guide de migration
+&#x20;pour plus d'informations.
+
+</Alert>
+
+Ce chemin de route correspondra à `acd` et `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Ce chemin correspondra à `abcd`, `abbcd`, `abbbcd`, et ainsi de suite.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Ce chemin correspondra à `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, et ainsi de suite.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Ce chemin de route correspondra à `/abe` et `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Chemins de route basés sur des expressions régulières
+
+Ce chemin d'itinéraire correspondra à tout ce qui contient un "a".
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Ce chemin d'itinéraire correspondra à `butterfly` et `dragonfly`, mais pas `butterflyman`, `dragonflyman`, et ainsi de suite.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Paramètres de la route
+
+Les paramètres de la route sont des segments d'URL nommés qui sont utilisés pour capturer les valeurs spécifiées à leur position dans l'URL. Les valeurs capturées sont remplies dans l'objet `req.params`, avec le nom du paramètre route spécifié dans le chemin comme leurs clés respectives.
+
+```
+Chemin de la route : /users/:userId/books/:bookId
+URL de requête : http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Pour définir des routes avec des paramètres d'itinéraire, il suffit de spécifier les paramètres de l'itinéraire dans le chemin de la route comme indiqué ci-dessous.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="Alerte">
+
+Le nom des paramètres de route doit être composé de "mots caractères" ([A-Za-z0-9_]).
+
+</Alert>
+
+Puisque le trait d'union (`-`) et le point (`.`) sont interprétés littéralement, ils peuvent être utilisés avec des paramètres d'itinéraire à des fins utiles.
+
+```
+Chemin de la route : /flights/:from-:to
+URL de requête : http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Chemin de la route : /plantae/:genus.:espèce
+URL de requête : http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="Alerte">
+
+Dans l’express 5, les caractères Regexp ne sont pas pris en charge dans les chemins de route, pour plus d’informations, veuillez
+vous référer au [guide de migration](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Pour avoir plus de contrôle sur la chaîne exacte qui peut être associée à un paramètre de route, vous pouvez ajouter une expression régulière entre parenthèses (`()`) :
+
+```
+Chemin de la route : /user/:userId(\d+)
+URL de requête : http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="avertissement">
+
+Parce que l'expression régulière fait généralement partie d'une chaîne littérale, Assurez-vous d'échapper à n'importe quel caractère `\`
+avec un antislash supplémentaire, par exemple `\d+`.
+
+</Alert>
+
+<Alert type="avertissement">
+Dans Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">le caractère `*` dans les expressions régulières n'est pas interprété de la manière habituelle</a>. Comme solution de contournement, utilisez `{0,}` au lieu de `*`. Cela sera probablement corrigé dans Express 5.
+</Alert>
+
+## Gestionnaires de routes
+
+Vous pouvez fournir plusieurs fonctions de rappel qui se comportent comme [middleware](/en/guide/using-middleware) pour traiter une requête. La seule exception est que ces callbacks peuvent appeler `next('route')` pour contourner les rappels de route restants. Vous pouvez utiliser ce mécanisme pour imposer des conditions préalables sur une route, passent ensuite le contrôle aux routes suivantes s'il n'y a pas de raison de poursuivre l'itinéraire courant.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params. d === '0') {
+    return next('route');
+  }
+  res. end(`Utilisateur ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Gestionnaire spécial pour l'identifiant utilisateur 0');
+});
+```
+
+Dans cet exemple :
+
+- `GET /user/5` → géré par la première route → envoie "Utilisateur 5"
+- `GET /user/0` → première route appelle `next('route')`, passe à la prochaine route correspondant à `/user/:id`
+
+Les gestionnaires de routes peuvent être sous la forme d'une fonction, d'un tableau de fonctions, ou de combinaisons des deux, comme indiqué dans les exemples suivants.
+
+Une seule fonction de rappel peut gérer une route. Par exemple :
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Bonjour de A!');
+});
+```
+
+Plus d'une fonction de rappel peut gérer une route (assurez-vous de spécifier l'objet `next`). Par exemple :
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('la réponse sera envoyée par la fonction suivante . .');
+    next();
+  },
+  (req, res) => {
+    end('Bonjour de B!');
+  }
+);
+```
+
+Un tableau de fonctions de rappel peut gérer une route. Par exemple :
+
+```js
+const cb0 = function (req, res, suivant) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  end('Bonjour de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Une combinaison de fonctions indépendantes et de tableaux de fonctions peut gérer une route. Par exemple :
+
+```js
+const cb0 = function (req, res, suivant) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  suivante();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('la réponse sera envoyée par la fonction suivante . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Bonjour de D!');
+  }
+);
+```
+
+## Méthodes de réponse
+
+Les méthodes de l'objet de réponse (`res`) dans la table suivante peuvent envoyer une réponse au client et terminer le cycle de réponse de la requête. Si aucune de ces méthodes n'est appelée à partir d'un gestionnaire d'itinéraire, la requête du client sera suspendue.
+
+| Méthode                                       | Libellé                                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Demander au téléchargement un fichier.                                                            |
+| [res.end()](/en/5x/api#res.end)               | Terminer le processus de réponse.                                                                 |
+| [res.json()](/en/5x/api#res.json)             | Envoyer une réponse JSON.                                                                         |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envoyer une réponse JSON avec le support JSONP.                                                   |
+| [res.redirect()](/en/5x/api#res.redirect)     | Rediriger une requête.                                                                            |
+| [res.render()](/en/5x/api#res.render)         | Afficher un modèle de vue.                                                                        |
+| [res.send()](/en/5x/api#res.send)             | Envoyer une réponse de différents types.                                                          |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Envoyer un fichier en tant que flux octet.                                                        |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Définit le code de statut de la réponse et envoie sa représentation en tant que corps de réponse. |
+
+## app.route()
+
+Vous pouvez créer des gestionnaires de routes chaînables pour un chemin en utilisant `app.route()`.
+Parce que le chemin est spécifié à un seul endroit, la création de routes modulaires est utile, tout comme la réduction de la redondance et des fautes de frappe. Pour plus d'informations sur les routes, voir : [Documentation de Router()](/en/5x/api#router).
+
+Voici un exemple de gestionnaires de routes enchaînés qui sont définis en utilisant `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    end('Obtenir un livre aléatoire');
+  })
+  .ost((req, res) => {
+    res.send('Ajouter un livre');
+  })
+  .ut((req, res) => {
+    res.send('Mettre à jour le livre');
+  });
+```
+
+## Routeur
+
+Utilisez la classe `express.Router` pour créer des gestionnaires de route modulaires et montables. Une instance `Router` est un système complet de middleware et de routage ; pour cette raison, elle est souvent appelée "mini-app".
+
+L'exemple suivant crée un routeur en tant que module, charge une fonction middleware dedans, définit quelques routes, et monte le module routeur sur un chemin dans l'application principale.
+
+Créez un fichier de routeur nommé `birds.js` dans le répertoire de l'application, avec le contenu suivant :
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Ensuite, chargez le module routeur dans l'application :
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', oiseaux);
+```
+
+L'application sera maintenant en mesure de traiter les demandes vers `/birds` et `/birds/about`, ainsi que d'appeler la fonction middleware `timeLog` qui est spécifique à la route.
+
+Mais si la route parente `/birds` a des paramètres de chemin, elle ne sera pas accessible par défaut à partir des sous-routes. Pour le rendre accessible, vous devrez passer l'option `mergeParams` au constructeur de routeur [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/fr/4x/guide/using-middleware.mdx b/src/content/docs/fr/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..3cb37d1ab5
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Utilisation du middleware
+description: Apprenez à utiliser les middleware dans les applications Express.js, y compris les middleware de niveau application et routeur, la gestion des erreurs et l'intégration de logiciels tiers middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express est un framework web de routage et de middleware qui possède des fonctionnalités minimales : Une application Express est essentiellement une série d'appels de fonctions de middleware.
+
+Les fonctions _Middleware_ sont des fonctions qui ont accès à l'objet [request object](/en/5x/api#req) (`req`), l'objet [réponse](/en/5x/api#res) (`res`), et la prochaine fonction du middleware dans le cycle de réponse de l'application. La prochaine fonction du middleware est généralement dénotée par une variable nommée `next`.
+
+Les fonctions Middleware peuvent effectuer les tâches suivantes :
+
+- Exécuter n'importe quel code.
+- Effectuez des modifications à la requête et aux objets de réponse.
+- Termine le cycle de réponse de la requête.
+- Appeler la prochaine fonction du middleware dans la pile.
+
+Si la fonction middleware actuelle ne met pas fin au cycle de réponse de requête, elle doit appeler `next()` pour passer le contrôle à la prochaine fonction du middleware. Sinon, la demande sera laissée en suspens.
+
+Une application Express peut utiliser les types de middleware suivants :
+
+- (#middleware.application)
+- [middleware au niveau du routeur] (#middleware.router)
+- (#middleware.error-handling)
+- (#middleware.built-in)
+- [middleware de tierce partie](#middleware.third-party)
+
+Vous pouvez charger le middleware au niveau de l'application et du routeur avec un chemin de montage optionnel.
+Vous pouvez également charger une série de fonctions middleware ensemble, ce qui crée une sous-pile du système middleware à un point de montage.
+
+## Outil d'interface de l'application
+
+Lier le middleware au niveau de l'application à une instance de l'objet [app object](/en/5x/api#app) en utilisant `app.use()` et `app. Les fonctions ETHOD()`, où `METHOD` est la méthode HTTP de la requête que la fonction middleware gère (comme GET, PUT ou POST) en minuscule.
+
+Cet exemple montre une fonction middleware sans chemin de montage. La fonction est exécutée chaque fois que l'application reçoit une requête.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Cet exemple montre une fonction middleware montée sur le chemin `/user/:id`. La fonction est exécutée pour n'importe quel type de requête HTTP
+sur le chemin `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Cet exemple montre une route et sa fonction de gestion (système middleware). La fonction gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Voici un exemple de chargement d'une série de fonctions middleware à un point de montage, avec un chemin de montage.
+Il illustre une sous-pile middleware qui affiche les informations de requête pour tout type de requête HTTP vers le chemin `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console. og('Type de requête :', req.method);
+    suivant();
+  }
+;
+```
+
+Les gestionnaires de routes vous permettent de définir plusieurs routes pour un chemin. L'exemple ci-dessous définit deux routes pour les requêtes GET vers le chemin `/user/:id`. La deuxième route ne posera aucun problème, mais elle ne sera jamais appelée parce que le premier parcours termine le cycle de réponse de la requête.
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('Info utilisateur');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui affiche l'identifiant utilisateur
+. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Pour sauter le reste des fonctions du middleware à partir d'une pile de middleware du routeur, appelez `next('route')` pour passer le contrôle à la route suivante.
+
+<Alert type="Infos">
+
+`next('route')` ne fonctionnera que dans les fonctions du middleware qui ont été chargées en utilisant les fonctions
+`app.METHOD()` ou `router.METHOD()`.
+
+</Alert>
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // si l'identifiant de l'utilisateur est 0, passer à la route
+    suivante si (req. arams. d === '0') next('route');
+    // sinon passez le contrôle à la prochaine fonction du middleware de cette pile
+    else next();
+  },
+  (req, res, next) => {
+    // envoie une réponse régulière
+    res. end('regular');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui envoie une réponse spéciale
+. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Les Middleware peuvent également être déclarés dans un tableau pour être réutilisables.
+
+Cet exemple montre un tableau avec une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Type de requête:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## middleware au niveau du routeur
+
+Le middleware au niveau du routeur fonctionne de la même manière que le middleware au niveau de l'application, sauf qu'il est lié à une instance de `express.Router()`.
+
+```js
+routeur const = express.Router();
+```
+
+Charger le middleware au niveau du routeur en utilisant les fonctions `router.use()` et `router.METHOD()`.
+
+L'exemple suivant réplique le système middleware qui est affiché ci-dessus pour le middleware au niveau de l'application, en utilisant le middleware au niveau du routeur:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. і();
+
+// une fonction middleware sans chemin de montage. Ce code est exécuté pour chaque requête au routeur
+. se(req, res, next) => {
+  console.log('Heure:', Date. ow());
+  next();
+});
+
+// une sous-pile middleware affiche les informations de requête pour tout type de requête HTTP vers le routeur /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    . og('Type de requête:', req. ethod);
+    suivante();
+  }
+);
+
+// une sous-pile middleware qui gère les requêtes GET sur le routeur /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // si l'identifiant de l'utilisateur est 0, passer au routeur
+    suivant si (req. arams. d === '0') next('route');
+    // passe autrement le contrôle à la prochaine fonction du middleware de cette pile
+    else next();
+  },
+  (req, res, next) => {
+    // renvoie une page normale
+    res. ender('regular');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui affiche une page spéciale
+. et('/user/:id', (req, res, next) => {
+  . og(req.params.id);
+  res.render('special');
+});
+
+// monte le routeur sur l'application
+app.use('/', router);
+```
+
+Pour sauter le reste des fonctions du middleware du routeur, appelez `next('router')`
+pour passer le contrôle hors de l'instance du routeur.
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. і();
+
+// prédice le routeur avec un contrôle et un renflouement si nécessaire le routeur
+. se(req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+routeur. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// utilise le routeur et 401 tout ce qui passe par l'application
+. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Gestion des erreurs du middleware
+
+<Alert type="Alerte">
+
+La gestion d'erreurs du middleware prend toujours _four_ arguments. Vous devez fournir quatre arguments à
+l'identifier comme une fonction de gestion des erreurs du middleware. Même si vous n'avez pas besoin d'utiliser l'objet `next`
+, vous devez le spécifier pour maintenir la signature. Sinon, l'objet `next` sera
+interprété comme un middleware normal et ne gérera pas les erreurs.
+
+</Alert>
+
+Définissez les fonctions du middleware de la même manière que les autres fonctions du middleware, sauf avec quatre arguments au lieu de trois, spécifiquement avec la signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Quelque chose s'est cassé !');
+});
+```
+
+Pour plus de détails sur la gestion des erreurs du middleware, voir : [Gestion des erreurs](/en/guide/error-handling).
+
+## middleware intégré
+
+À partir de la version 4.x, Express ne dépend plus de [Connect](https://github.com/senchalabs/connect). Les fonctions du middleware
+qui étaient précédemment incluses avec Express sont maintenant dans des modules séparés ; voir [la liste des fonctions du middleware] (https://github.com/senchalabs/connect#middleware).
+
+Express a les fonctions internes suivantes :
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) analyse les requêtes entrantes avec des charges utiles JSON. **NOTE : Disponible avec Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analyse les requêtes entrantes avec des charges utiles encodées en URL. **NOTE : Disponible avec Express 4.16.0+**
+
+## middleware de tierce partie
+
+Utilisez des logiciels tiers pour ajouter des fonctionnalités aux applications Express.
+
+Installez le module Node.js pour la fonctionnalité requise, puis chargez-le dans votre application au niveau de l'application ou au niveau du routeur.
+
+L'exemple suivant illustre l'installation et le chargement de la fonction middleware d'analyse de cookies `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// charge le middleware
+app.use(cookieParser());
+```
+
+Pour une liste partielle des fonctions middleware tierces qui sont couramment utilisées avec Express, voir : [middleware de tierce] (../resources/middleware).
diff --git a/src/content/docs/fr/4x/guide/using-template-engines.mdx b/src/content/docs/fr/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..af25252ab8
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utiliser les moteurs de gabarits avec Express
+description: Découvrez comment intégrer et utiliser des moteurs de gabarits tels que Pug, Handlebars et EJS avec Express.js pour rendre les pages HTML dynamiques efficacement.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un _moteur de modèle_ vous permet d'utiliser des fichiers de modèles statiques dans votre application. Lors de l'exécution, le moteur de gabarit remplace les variables
+dans un fichier de gabarit par des valeurs réelles, et transforme le modèle en un fichier HTML envoyé au client.
+Cette approche facilite la conception d'une page HTML.
+
+Le [générateur d'application Express](/en/starter/generator) utilise [Pug](https://pugjs.org/api/getting-started.html) par défaut, mais il supporte aussi [Handlebars](https://www.npmjs.com/package/handlebars), et [EJS](https://www.npmjs.com/package/ejs), entre autres.
+
+Pour afficher les fichiers de gabarit, définissez les [propriétés de réglage de l'application](/en/4x/api#app.set), dans le `app.js` par défaut créé par le générateur:
+
+- `views`, le répertoire où se trouvent les fichiers de modèle. Ex. : `app.set('vues', './views')`.
+  Par défaut, le répertoire `views` se trouve à la racine de l'application.
+- `voir le moteur`, le moteur de gabarit à utiliser. Par exemple, pour utiliser le moteur de gabarit Pug : `app.set('moteur de vue', 'pug')`.
+
+Ensuite, installez le paquet npm correspondant au moteur de gabarits ; par exemple pour installer Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="Alerte">
+Les moteurs de gabarits conformes à la norme Express tels que Pug exportent une fonction nommée `__express(filePath, options, callback)`,
+qui `res.render()` appelle pour rendre le code du gabarit.
+
+Certains moteurs de gabarits ne suivent pas cette convention. La bibliothèque [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+suit cette convention en mappant tous les moteurs de gabarits populaires Node.js, et fonctionne donc parfaitement dans Express.
+
+</Alert>
+
+Une fois que le moteur de vue est défini, vous n'avez pas à spécifier le moteur ou charger le module moteur de gabarit dans votre application ;
+Express charge le module en interne, par exemple :
+
+```js
+app.set('moteur d'affichage', 'pug');
+```
+
+Ensuite, créez un fichier de modèle Pug nommé `index.pug` dans le dossier `views`, avec le contenu suivant:
+
+```pug
+html
+  devant
+    title= titre
+  corps
+    h1= message
+```
+
+Créez une route pour afficher le fichier `index.pug`. Si la propriété `view engine` n'est pas définie,
+vous devez spécifier l'extension du fichier `view`. Sinon, vous pouvez l'oublier.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Bonjour !' });
+});
+```
+
+Lorsque vous faites une requête sur la page d'accueil, le fichier `index.pug` sera rendu en HTML.
+
+Le cache du moteur de vue ne cache pas le contenu de la sortie du modèle, seulement le modèle sous-jacent. La vue est toujours rendue à chaque requête, même lorsque le cache est activé.
diff --git a/src/content/docs/fr/4x/guide/writing-middleware.mdx b/src/content/docs/fr/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..08145c2141
--- /dev/null
+++ b/src/content/docs/fr/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Écriture de middleware pour utilisation dans les applications Express
+description: Apprenez à écrire des fonctions personnalisées de middleware pour les applications Express.js, y compris des exemples et des pratiques exemplaires pour améliorer la gestion des requêtes et des réponses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Les fonctions _Middleware_ sont des fonctions qui ont accès à l'objet [request object](/en/5x/api#req) (`req`), l'objet [réponse](/en/5x/api#res) (`res`), et la fonction `next` dans le cycle de réponse de l'application. La fonction `next` est une fonction dans le routeur Express qui, lorsqu'elle est appelée, exécute le middleware qui succède au middleware actuel.
+
+Les fonctions Middleware peuvent effectuer les tâches suivantes :
+
+- Exécuter n'importe quel code.
+- Effectuez des modifications à la requête et aux objets de réponse.
+- Termine le cycle de réponse de la requête.
+- Appelez le prochain middleware dans la pile.
+
+Si la fonction middleware actuelle ne met pas fin au cycle de réponse de requête, elle doit appeler `next()` pour passer le contrôle à la prochaine fonction du middleware. Sinon, la demande sera laissée en suspens.
+
+La figure suivante montre les éléments d'un appel de fonction middleware :
+
+<div class="défileur de table">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Éléments d'un appel de fonction middleware" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">méthode HTTP pour laquelle la fonction middleware s'applique.</div>
+
+<div class="callout" id="callout2">
+  Chemin (route) pour lequel la fonction middleware s'applique.
+</div>
+
+<div class="callout" id="callout3">
+  La fonction middleware.
+</div>
+
+<div class="callout" id="callout4">
+  Argument de rappel à la fonction middleware, appelé "next" par convention.
+</div>
+
+<div class="callout" id="callout5">
+  L'argument HTTP <a href="/en/5x/api#res">réponse</a> à la fonction middleware appelée "res" par
+  convention .
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">demande</a> argument à la fonction middleware appelée "req" par convention.</div>
+</td>
+</tr>
+</table>
+</div>
+
+À partir de Express 5, les fonctions middleware qui retournent une Promise appelleront `next(value)` quand elles rejettent ou lancent une erreur. `next` sera appelé avec la valeur rejetée ou avec l'erreur levée.
+
+## Exemple
+
+Voici un exemple de simple application "Hello World" Express.
+Le reste de cet article va définir et ajouter trois fonctions middleware à l'application :
+un appelé `myLogger` qui affiche un message de log simple. on appelle `requestTime` que
+affiche l'horodatage de la requête HTTP, et un appelé `validateCookies` qui valide les cookies entrants.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Fonction Middleware myLogger
+
+Voici un exemple simple d'une fonction middleware appelée "myLogger". Cette fonction affiche seulement
+"LOGGED" lorsqu'une requête vers l'application passe à travers elle. La fonction middleware est assignée à une variable
+nommée `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="Alerte">
+
+Notez l'appel ci-dessus à `next()`. Appeler cette fonction appelle la prochaine fonction du middleware dans
+l'application. La fonction `next()` n'est pas une partie du noeud. s ou API Express, mais est le troisième argument
+qui est passé à la fonction middleware. La fonction `next()` pourrait être nommée quoi que ce soit,
+mais par convention elle est toujours nommée "next". Pour éviter toute confusion, utilisez toujours cette convention.
+
+</Alert>
+
+Pour charger la fonction middleware, appelez `app.use()`, en spécifiant la fonction middleware.
+Par exemple, le code suivant charge la fonction middleware `myLogger` avant la route vers le chemin racine (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Chaque fois que l'application reçoit une demande, elle affiche le message "LOGGGED" vers le terminal.
+
+L'ordre de chargement du middleware est important : les fonctions du middleware qui sont chargées en premier sont également exécutées en premier.
+
+Si `myLogger` est chargé après la route vers le chemin racine, la requête ne l'atteint jamais et l'application n'affiche pas "LOGGED", parce que le gestionnaire de route du chemin racine termine le cycle de réponse de requête.
+
+La fonction du middleware `myLogger` affiche simplement un message, passe ensuite la requête à la prochaine fonction middleware de la pile en appelant la fonction `next()`.
+
+### Middleware fonction requestTime
+
+Ensuite, nous allons créer une fonction middleware appelée "requestTime" et ajouter une propriété appelée `requestTime`
+à l'objet requête.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+L'application utilise maintenant la fonction middleware `requestTime`. Aussi, la fonction callback de la route du chemin racine utilise la propriété que la fonction middleware ajoute à `req` (l'objet de requête).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = 'Bonjour le monde!<br>';
+  responseText += `<small>Demandé à: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Lorsque vous faites une demande à la racine de l'application, l'application affiche maintenant l'horodatage de votre requête dans le navigateur.
+
+### format@@0 Middleware function validateCookies
+
+Enfin, nous allons créer une fonction middleware qui valide les cookies entrants et envoie une réponse 400 si les cookies sont invalides.
+
+Voici un exemple de fonction qui valide les cookies avec un service asynchrone externe.
+
+```js
+fonction async cookieValidator(cookies) {
+  essayer {
+    attendre externalyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Cookies invalides');
+  }
+}
+```
+
+Ici, nous utilisons le middleware [`cookie-parser`](/en/resources/middleware/cookie-parser) pour analyser les cookies entrants de l'objet `req` et les passer à notre fonction `cookieValidator`. Le middleware `validateCookies` retourne une Promesse que si le rejet déclenchera automatiquement notre gestionnaire d'erreurs.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+fonction async validateCookies(req, res, next) {
+  attendent cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// gestionnaire d'erreur
+app. se(err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="Alerte">
+
+Notez comment `next()` est appelé après `wait cookieValidator(req.cookies)`. Cela garantit que si
+`cookieValidator` résoud, le prochain middleware de la pile sera appelé. Si vous passez quelque chose
+à la fonction `next()` (sauf la chaîne `'route'` ou `'router'`), Express considère que la requête
+actuelle est une erreur et ignorera toute fonction de routage et de middleware
+qui ne gère pas les autres fonctions de routage.
+
+</Alert>
+
+Parce que vous avez accès à l'objet requête, à l'objet de réponse, à la prochaine fonction du middleware dans la pile, et à l'ensemble du nœud. s API, les possibilités avec les fonctions du middleware sont infinies.
+
+Pour plus d'informations sur le middleware Express, voir : [Utiliser un middleware Express](/en/guide/using-middleware).
+
+## Logiciel middleware configurable
+
+Si vous avez besoin que votre middleware soit configurable, exportez une fonction qui accepte un objet d'options ou d'autres paramètres, qui retourne ensuite l'implémentation du middleware en fonction des paramètres d'entrée.
+
+Fichier: `my-middleware.js`
+
+```js
+module. xports = function (options) {
+  fonction de retour (req, res, next) {
+    // Implémente la fonction middleware basée sur l'objet d'options
+    next();
+  };
+};
+```
+
+Le middleware peut maintenant être utilisé comme montré ci-dessous.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Reportez-vous à [cookie-session](https://github.com/expressjs/cookie-session) et [compression](https://github.com/expressjs/compression) pour des exemples de middleware configurables.
diff --git a/src/content/docs/fr/4x/starter/basic-routing.mdx b/src/content/docs/fr/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..cc7681f5ea
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Routage de base
+description: Apprenez les fondamentaux du routage dans les applications Express.js, y compris comment définir des routes, gérer des méthodes HTTP et créer des gestionnaires de routes pour votre serveur web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ désigne la façon dont une application répond à une requête client à un point de terminaison particulier, qui est une URI (ou un chemin) et une méthode spécifique de requête HTTP (GET, POST, etc.).
+
+Chaque route peut avoir une ou plusieurs fonctions de gestionnaire, qui sont exécutées lorsque la route est correspondante.
+
+La définition de la route prend la structure suivante :
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Où :
+
+- `app` est une instance de `express`.
+- `METHOD` est une [méthode de requête HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), en minuscule.
+- `PATH` est un chemin sur le serveur.
+- `HANDLER` est la fonction exécutée lorsque la route est correspondante.
+
+<Alert type="Alerte">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Si vous n'êtes pas familier avec la création d'une application et son démarrage, consultez l'exemple Bonjour le monde
+.
+
+</Alert>
+
+Les exemples suivants illustrent la définition de routes simples.
+
+Répondez avec `Hello World!` sur la page d'accueil:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Répondre à une requête POST sur la route racine (`/`), la page d'accueil de l'application :
+
+```js
+app.post('/', (req, res) => {
+  res.send('Requête POST');
+});
+```
+
+Répondre à une requête PUT sur la route `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Requête PUT à /user');
+});
+```
+
+Répondre à une requête DELETE sur la route `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Requête DELETE à /user');
+});
+```
+
+Pour plus de détails sur le routage, consultez le [guide de routage] (/en/guide/routing).
diff --git a/src/content/docs/fr/4x/starter/examples.mdx b/src/content/docs/fr/4x/starter/examples.mdx
new file mode 100644
index 0000000000..8d390b2ce9
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Exemples Express
+description: Explorez une collection d'exemples d'applications Express.js couvrant divers cas d'utilisation, intégrations et configurations avancées pour vous aider à apprendre et à construire vos projets.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Authentification avec login et mot de passe
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - négociation de contenu HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transfert de fichiers vers le client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Travailler avec un modèle JavaScript embarqué (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Création des pages d'erreur
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Travailler avec un middleware d'erreur
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Gestionnaire de requêtes simple
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown comme moteur de gabarit
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Travailler avec plusieurs routeurs Express
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - Contrôleurs de style MVC
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Suivi de l'activité de l'utilisateur en ligne avec les paquets `online` et `redis`
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Travailler avec les paramètres de la route
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Opérations HTTP multiples sur la même ressource
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organiser des routes à l'aide d'une carte
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Travailler avec le middleware de route
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organiser des routes par ressource
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - Sessions utilisateur
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Servir des fichiers statiques
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Rendu dynamique des vues
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Enregistrement des données dans l'objet de requête entre les appels de middleware
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Service API simple
+
+## Exemples supplémentaires
+
+Ce sont quelques exemples supplémentaires avec des intégrations plus étendues.
+
+<Alert type="avertissement">
+  Cette information se réfère à des sites tiers, des produits ou des modules tiers qui ne sont pas
+  maintenus par l'équipe Expressjs. La liste ci-dessous ne constitue pas une approbation ou une
+  recommandation de l'équipe du projet Expressjs.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Application Fullstack avec Express et Next.js en utilisant [Prisma](https://www.npmjs.com/package/prisma) en tant qu'ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API avec Express in TypeScript en utilisant [Prisma](https://www.npmjs.com/package/prisma) en tant qu'ORM
diff --git a/src/content/docs/fr/4x/starter/faq.md b/src/content/docs/fr/4x/starter/faq.md
new file mode 100644
index 0000000000..494c74698b
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: Foire Aux Questions
+description: Retrouvez les réponses aux questions les plus fréquemment posées sur Express.js, y compris les sujets sur la structure de l'application, les modèles, l'authentification, les moteurs de gabarit, la gestion des erreurs, et plus encore.
+---
+
+## Comment structurer ma candidature ?
+
+Il n'y a pas de réponse définitive à cette question. La réponse dépend
+de l'échelle de votre candidature et de l'équipe impliquée. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Les routes et autres logiques spécifiques à une application peuvent vivre dans autant de fichiers
+que vous le souhaitez, dans n'importe quelle structure de répertoire que vous préférez. View the following
+examples for inspiration:
+
+- [Liste des itinéraires](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Il y a également des extensions tierces pour Express, qui simplifient certains de ces modèles:
+
+- [Itinéraire de ressource](https://github.com/expressjs/express-resource)
+
+## Comment définir des modèles?
+
+Express n'a aucune notion de base de données. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+Voir [LoopBack](http://loopback.io) pour un framework basé sur Express, centré autour de modèles.
+
+## Comment puis-je authentifier les utilisateurs ?
+
+Authentication is another opinionated area that Express does not
+venture into. Vous pouvez utiliser n'importe quel schéma d'authentification que vous souhaitez.
+Pour un simple nom d'utilisateur / schéma de mot de passe, voir [cet exemple](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quels moteurs de gabarits sont supportés par Express ?
+
+Express prend en charge tout moteur de gabarit qui est conforme à la signature `(path, locals, callback)`.
+Pour normaliser les interfaces du moteur de gabarits et la mise en cache, consultez le projet
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+pour plus de support. Les moteurs de gabarits non listés peuvent toujours supporter la signature Express.
+
+Pour plus d'informations, voir [Utilisation de moteurs de gabarits avec Express](/en/guide/using-template-engines).
+
+## Comment gérer 404 réponses?
+
+Dans Express, 404 réponses ne sont pas le résultat d'une erreur, donc
+le middleware de gestion d'erreurs ne les capturera pas. Ce comportement est
+car une réponse 404 indique simplement l'absence de travail supplémentaire à faire ;
+en d'autres termes, Express a exécuté toutes les fonctions et routes du middleware,
+et a trouvé qu'aucun d'eux n'a répondu. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Ajoute des routes dynamiquement à l'exécution sur une instance de `express.Router()`
+afin que les routes ne soient pas remplacées par une fonction de middleware.
+
+## Comment configurer un gestionnaire d'erreur ?
+
+Vous définissez le middleware de la même manière que les autres middleware,
+sauf avec quatre arguments au lieu de trois; spécifiquement avec la signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Pour plus d'informations, voir [Gestion des erreurs] (/en/guide/error-handling).
+
+## Comment rendre le HTML simple ?
+
+Vous ne le faites pas! Il n'y a pas besoin de "render" HTML avec la fonction `res.render()`.
+Si vous avez un fichier spécifique, utilisez la fonction `res.sendFile()`.
+Si vous utilisez beaucoup d'actifs depuis un répertoire, utilisez la fonction `express.static()`
+middleware.
+
+## Quelle version de Node.js est requise ?
+
+- [Express 4.x](/en/4x/api) nécessite Node.js 0.10 ou supérieur.
+- [Express 5.x](/en/5x/api) nécessite Node.js 18 ou plus.
diff --git a/src/content/docs/fr/4x/starter/generator.mdx b/src/content/docs/fr/4x/starter/generator.mdx
new file mode 100644
index 0000000000..697016481d
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Générateur d'application Express
+description: Apprenez à utiliser l'outil de générateur d'applications Express pour créer rapidement un squelette pour vos applications Express.js, en rationalisant la configuration et la configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilisez l'outil de générateur d'applications, `express-generator`, pour créer rapidement un squelette d'application.
+
+Vous pouvez exécuter le générateur d'application avec la commande `npx` (disponible dans Node.js 8.2.0).
+
+```bash
+Générateur de npx express $
+```
+
+Pour les versions antérieures de Node, installez le générateur d'application en tant que paquet npm global puis lancez le :
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Affiche les options de la commande avec l'option `-h`:
+
+```bash
+$ express -h
+
+  Utilisation : express [options] [dir]
+
+  Options :
+
+    -h, --help affiche les informations d'utilisation
+        --version affiche le numéro de version
+    -e, --ejs add ejs engine support
+        --hbs add handlebar engine support
+        --pug add pug engine support
+    -H, --hogan add hogan. le support du moteur
+        --no-view générer sans afficher le moteur
+    -v, --view <engine> ajouter la vue <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (par défaut jade)
+    -c, --css <engine>  ajoute la feuille de style <engine> support (moins|stylus|compass|sass) (par défaut, css simple)
+        --git add . itignore
+    -f, --force sur un répertoire non vide
+```
+
+Par exemple, ce qui suit crée une application Express nommée _myapp_. L'application sera créée dans un dossier nommé _myapp_ dans le répertoire de travail actuel et le moteur de vue sera réglé sur <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   créer : monapp/routes/utilisateurs. s
+   créer : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : monapp/bin
+   create : myapp/bin/www
+```
+
+Installez ensuite les dépendances :
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+Sous MacOS ou Linux, exécutez l'application avec cette commande :
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Sous l'invite de commande Windows, utilisez cette commande :
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+Sous Windows PowerShell, utilisez cette commande :
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Ensuite, chargez `http://localhost:3000/` dans votre navigateur pour accéder à l'application.
+
+L'application générée a la structure de répertoire suivante :
+
+```bash
+.
+── app.js
+── bin
+文<unk> ─ www
+── package. fils
+── public
+Ω─ images
+Ω─ javascripts
+文<unk> ── feuilles de style
+Ω<unk> ─ style. ss
+── routes
+文── index.js
+Ω<unk> ── utilisateurs. s
+<unk> ── vues
+    ── erreur. ug
+    ── index.pug
+    <unk> ─ layout.pug
+
+7 répertoires, 9 fichiers
+```
+
+<Alert type="Infos">
+
+La structure d'application créée par le générateur n'est qu'un des nombreux moyens de structurer les applications Express.
+N'hésitez pas à utiliser cette structure ou à la modifier pour mieux répondre à vos besoins.
+
+</Alert>
diff --git a/src/content/docs/fr/4x/starter/hello-world.mdx b/src/content/docs/fr/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..1c7704047e
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Bonjour l'exemple du monde
+description: Commencez avec Express.js en construisant une simple application 'Hello World', en démontrant la configuration de base et la création de serveurs pour les débutants.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="Infos">
+
+Intégré ci-dessous est essentiellement l'application Express la plus simple que vous puissiez créer. C'est une seule application de fichier
+&mdash; _pas_ ce que vous obtiendrez si vous utilisez le [générateur Express](/en/starter/generator), que
+crée l'échafaudage pour une application complète avec de nombreux fichiers JavaScript, des modèles Jade, et des sous-répertoires
+à diverses fins.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Exemple d'application d'écoute sur le port ${port}`);
+});
+```
+
+Cette application démarre un serveur et écoute le port 3000 pour les connexions. L'application répond avec "Hello World!" pour les demandes
+à l'URL racine (`/`) ou _route_. Pour tous les autres chemins, il répondra avec un **404 Not Found**.
+
+## Exécution locale
+
+Créez d'abord un répertoire nommé `myapp`, changez et exécutez `npm init`. Ensuite, installez `express` en tant que dépendance, conformément au [guide d'installation](/en/starter/installing).
+
+Dans le dossier `myapp`, créez un fichier nommé `app.js` et copiez le code à partir de l'exemple ci-dessus.
+
+<Alert type="Alerte">
+
+Les `req` (request) et `res` (response) sont les mêmes objets que le noeud fournit, donc vous pouvez
+appeler `req. ipe()`, `req.on('data', callback)`, et tout autre chose que vous feriez sans Express
+impliqué.
+
+</Alert>
+
+Exécutez l'application avec la commande suivante :
+
+```bash
+$ node app.js
+```
+
+Ensuite, chargez `http://localhost:3000/` dans un navigateur pour voir la sortie.
diff --git a/src/content/docs/fr/4x/starter/installing.mdx b/src/content/docs/fr/4x/starter/installing.mdx
new file mode 100644
index 0000000000..2383a5c05f
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installation en cours
+description: Apprenez à installer Express.js dans votre environnement Node.js, y compris la configuration de votre répertoire de projet et la gestion des dépendances avec npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Avant de commencer, assurez-vous que vous avez [Node.js](https://nodejs.org/) 0.10 ou supérieur installé. Ensuite, créez un répertoire pour votre application et naviguez dedans.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Utilisez la commande `npm init` pour créer un fichier `package.json` pour votre application.
+Pour plus d'informations sur le fonctionnement de `package.json`, voir [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Cette commande vous invite à trouver un certain nombre de choses, telles que le nom et la version de votre application.
+Pour l'instant, vous pouvez simplement appuyer sur RETURN pour accepter les valeurs par défaut pour la plupart d'entre eux, à l'exception de la règle suivante :
+
+```
+point d'entrée: (index.js)
+```
+
+Entrez `app.js`, ou quel que soit le nom du fichier principal. Si vous voulez qu'il soit `index.js`, appuyez sur RETURN pour accepter le nom de fichier par défaut suggéré.
+
+Maintenant, installez Express dans le répertoire `myapp` et sauvegardez-le dans la liste des dépendances. Par exemple :
+
+```bash
+npm installation express
+```
+
+Pour installer Express temporairement et ne pas l'ajouter à la liste des dépendances :
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="Infos">
+
+Par défaut avec la version npm 5.0+, `npm install` ajoute le module à la liste `dependencies` dans le paquet
+`. son`; avec les versions antérieures de npm, vous devez spécifier explicitement l'option `--save`
+. Puis, par la suite, exécuter `npm install` dans le répertoire de l'application sera automatiquement
+installer des modules dans la liste des dépendances.
+
+</Alert>
diff --git a/src/content/docs/fr/4x/starter/static-files.mdx b/src/content/docs/fr/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..041757b116
--- /dev/null
+++ b/src/content/docs/fr/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servir les fichiers statiques dans Express
+description: Comprendre comment servir les fichiers statiques comme les images, CSS, et JavaScript dans les applications Express.js en utilisant le middleware 'statique' intégré.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Pour servir des fichiers statiques tels que des images, des fichiers CSS et des fichiers JavaScript, utilisez la fonction middleware intégrée `express.static` dans Express.
+
+La signature de la fonction est :
+
+```js
+express.static(root, [options]);
+```
+
+L'argument `root` spécifie le répertoire racine à partir duquel servir les actifs statiques.
+Pour plus d'informations sur l'argument `options`, voir [express.static](/en/5x/api#express.static).
+
+Par exemple, utilisez le code suivant pour servir les images, les fichiers CSS et JavaScript dans un répertoire nommé `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Maintenant, vous pouvez charger les fichiers qui se trouvent dans le répertoire `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="Infos">
+
+Express recherche les fichiers relatifs au répertoire statique, donc le nom du répertoire statique
+ne fait pas partie de l'URL.
+
+</Alert>
+
+Pour utiliser plusieurs répertoires statiques, appelez la fonction middleware `express.static` plusieurs fois :
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express recherche les fichiers dans l'ordre dans lequel vous définissez les répertoires statiques avec la fonction `express.static`.
+
+<Alert type="Infos">
+
+Pour de meilleurs résultats, utilisez un proxy
+inversé pour améliorer les performances de
+servant des actifs statiques.
+
+</Alert>
+
+Pour créer un préfixe de chemin virtuel (où le chemin n'existe pas dans le système de fichiers) pour les fichiers qui sont servis par le fichier `express. fonction tatic`, [spécifiez un chemin de montage](/en/5x/api#app.use) pour le répertoire statique, comme indiqué ci-dessous:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Maintenant, vous pouvez charger les fichiers qui se trouvent dans le dossier `public` à partir du préfixe de chemin `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Cependant, le chemin que vous fournissez à la fonction `express.static` est relatif au répertoire depuis lequel vous lancez votre processus `node`. Si vous exécutez l'application express à partir d'un autre répertoire, il est plus sûr d'utiliser le chemin absolu du répertoire que vous voulez servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Pour plus de détails sur la fonction `serve-static` et ses options, voir [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/fr/5x/advanced/developing-template-engines.md b/src/content/docs/fr/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..8ddb890522
--- /dev/null
+++ b/src/content/docs/fr/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Développement de moteurs de gabarits pour Express
+description: Apprenez comment développer des moteurs de gabarits personnalisés pour Express.js en utilisant app.engine(), avec des exemples sur la création et l'intégration de votre propre logique de rendu de gabarits.
+---
+
+Utilisez la méthode `app.engine(ext, callback)` pour créer votre propre moteur de template. `ext` fait référence à l'extension de fichier, et `callback` est la fonction du moteur de gabarit, qui accepte les éléments suivants comme paramètres: l'emplacement du fichier, l'objet d'options et la fonction de rappel.
+
+Le code suivant est un exemple d'implémenter un moteur de gabarit très simple pour le rendu des fichiers `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Votre application sera maintenant en mesure d'afficher les fichiers `.ntl`. Créez un fichier nommé `index.ntl` dans le dossier `views` avec le contenu suivant.
+
+```pug
+#title#
+#message#
+```
+
+Ensuite, créez la route suivante dans votre application.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Lorsque vous faites une requête sur la page d'accueil, `index.ntl` sera rendu en HTML.
diff --git a/src/content/docs/fr/5x/guide/behind-proxies.mdx b/src/content/docs/fr/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..aa17a36f63
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Exprimez derrière les mandataires
+description: Apprenez à configurer les applications Express.js pour qu'elles fonctionnent correctement derrière les mandataires inversés, y compris en utilisant le paramètre proxy de confiance pour gérer les adresses IP du client.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Lorsque vous exécutez une application Express derrière un proxy inverse, certaines des API Express peuvent retourner des valeurs différentes de celles attendues. Pour ajuster pour cela, le paramètre `trust proxy` de l'application peut être utilisé pour exposer des informations fournies par le proxy inverse dans les API Express. Le problème le plus courant est les API express qui exposent l'adresse IP du client peut à la place afficher une adresse IP interne du proxy inverse.
+
+<Alert type="Infos">
+
+Lors de la configuration du paramètre `trust proxy`, il est important de comprendre la configuration exacte du proxy inverse
+. Puisque ce paramètre fera confiance aux valeurs fournies dans la requête, Il est important que
+la combinaison du paramètre dans Express corresponde à la façon dont le proxy inversé fonctionne.
+
+</Alert>
+
+Le paramètre de l'application `trust proxy` peut être défini à l'une des valeurs listées dans la table suivante.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Valeur</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Si `true`, l'adresse IP du client est comprise comme l'entrée la plus à gauche dans l'en-tête `X-Forwarded-For`.
+
+Si `false`, l'application est comprise comme faisant directement face au client et l'adresse IP du client est dérivée de `req.socket.remoteAddress`. Ceci est le paramètre par défaut.
+
+<Alert type="avertissement">
+Lorsque vous définissez sur `true`, il est important de s'assurer que le dernier proxy inversé fiable est de supprimer/écraser tous les en-têtes HTTP suivants : `X-Forwarded-For`, `X-Forwarded-Host`, et `X-Forwarded-Proto`, sinon il sera possible pour le client de fournir n'importe quelle valeur.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Adresses IP</td>
+<td markdown="1">
+Une adresse IP, un sous-réseau ou un tableau d'adresses IP et de sous-réseaux à confier comme étant un proxy inverse. La liste suivante montre les noms de sous-réseaux pré-configurés :
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Vous pouvez définir les adresses IP de l'une des façons suivantes :
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+Lorsqu'il est spécifié, les adresses IP ou les sous-réseaux sont exclus du processus de détermination de l'adresse, et l'adresse IP non fiable la plus proche du serveur d'application est déterminée comme l'adresse IP du client. Cela fonctionne en vérifiant si `req.socket.remoteAddress` est fiable. Si c'est le cas, alors chaque adresse dans `X-Forwarded-For` est vérifiée de droite à gauche jusqu'à la première adresse non fiable.
+
+</td>
+    </tr>
+    <tr>
+      <td>Nombre</td>
+<td markdown="1">
+Utilisez l'adresse qui est au plus `n` nombre de sauts loin de l'application Express. `req.socket.remoteAddress` est le premier saut, et le reste est recherché dans l'en-tête `X-Forwarded-For` de droite à gauche. Une valeur de `0` signifie que la première adresse non fiable serait `req.socket.remoteAddress`, c'est-à-dire qu'il n'y a pas de proxy inverse.
+
+<Alert type="avertissement">
+Lors de l'utilisation de ce paramètre, il est important de s'assurer qu'il n'y a pas de multiples, chemins différents vers l'application Express de sorte que le client peut être inférieur au nombre de sauts configurés, sinon il pourrait être possible pour le client de fournir n'importe quelle valeur.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Fonction</td>
+<td markdown="1">
+Implémentation de confiance personnalisée.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123. 23')
+    retourne true; // les adresses IP
+  approuvées retournent false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Activer `trust proxy` aura l'impact suivant :
+
+<ul>
+  <li markdown="1">
+    La valeur de [req.hostname](/en/api#req.hostname) est dérivée de la valeur définie dans
+    l'en-tête `X-Forwarded-Host`, qui peut être définie par le client ou par le proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` peut être défini par le proxy inverse pour dire à l'application si c'est
+    `https` ou `http` ou même un nom invalide. Cette valeur est reflétée par
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Les valeurs [req.ip](/en/api#req.ip) et [req.ips](/en/api#req.ips) sont remplies en fonction de
+    l'adresse du socket et de l'en-tête `X-Forwarded-For`, à partir de la première adresse non
+    fiable.
+  </li>
+</ul>
+
+Le paramètre `trust proxy` est implémenté en utilisant le paquet [proxy-addr](https://www.npmjs.com/package/proxy-addr). Pour plus d'informations, voir sa documentation.
diff --git a/src/content/docs/fr/5x/guide/debugging.mdx b/src/content/docs/fr/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..04a54bbf25
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Débogage Express
+description: Apprenez comment activer et utiliser les journaux de débogage dans les applications Express.js en définissant la variable d'environnement DEBUG pour un dépannage amélioré.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Pour voir tous les journaux internes utilisés dans Express, définissez la variable d'environnement `DEBUG` à
+`express:*` lors du lancement de votre application.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Sous Windows, utilisez la commande correspondante.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+L'exécution de cette commande sur l'application par défaut générée par le [générateur express](/en/starter/generator) affiche la sortie suivante:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Lorsqu'une demande est faite à l'application, vous verrez les journaux spécifiés dans le code Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query : / +2ms
+  express:router expressInit : / +0ms
+  express:router favicon : / +0ms
+  express:router logger : / +1ms
+  express:router jsonParser : / +0ms
+  express:router urlencodedParser : / +1ms
+  express:router cookieParser : / +0ms
+  express:router stylus : / +0ms
+  express:router serveStatic : / +2ms
+  express:router : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index. ug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Pour voir les logs uniquement à partir de l'implémentation du routeur, définissez la valeur de `DEBUG` à `express:router`. De même, pour ne voir que les logs de l'implémentation de l'application, définissez la valeur de `DEBUG` à `express:application`, et ainsi de suite.
+
+## Applications générées par `express`
+
+Une application générée par la commande `express` utilise le module `debug` et son espace de noms de débogage est limité au nom de l'application.
+
+Par exemple, si vous avez généré l'application avec `$ express sample-app`, vous pouvez activer les instructions de débogage avec la commande suivante :
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+Vous pouvez spécifier plus d'un espace de noms de débogage en assignant une liste de noms séparés par des virgules :
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Options avancées
+
+Lors de l'exécution de Node.js, vous pouvez définir quelques variables d'environnement qui changeront le comportement du journal de débogage :
+
+| Nom                 | Objectif                                                         |
+| ------------------- | ---------------------------------------------------------------- |
+| `DEBUG`             | Active/désactive les espaces de noms de débogage spécifiques.    |
+| `DEBUG_COLORS`      | Utiliser ou non les couleurs dans la sortie de débogage.         |
+| `DEBUG_DEPTH`       | Profondeur de l'inspection des objets.                           |
+| `DEBUG_FD`          | Descripteur de fichier vers lequel écrire la sortie de débogage. |
+| `DEBUG_SHOW_HIDDEN` | Affiche les propriétés masquées sur les objets inspectés.        |
+
+<Alert type="Infos">
+
+Les variables d'environnement commençant par `DEBUG_` finissent par être converties en un objet d'options
+qui est utilisé avec les formats `%o`/`%O`. Voir la documentation Node.js pour
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) pour la liste complète
+.
+
+</Alert>
diff --git a/src/content/docs/fr/5x/guide/error-handling.mdx b/src/content/docs/fr/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..0bcd847565
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Gestion des erreurs
+description: Comprenez comment Express.js gère les erreurs dans le code synchrone et asynchrone et apprend à implémenter la gestion des erreurs personnalisées pour vos applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ fait référence à la façon dont Express attrape et traite les erreurs que
+se produisent de manière synchronisée et asynchrone. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Erreurs de capture
+
+Il est important de s'assurer qu'Express attrape toutes les erreurs qui se produisent lorsque
+exécute des gestionnaires de routes et des middleware.
+
+Les erreurs qui se produisent dans le code synchrone dans les gestionnaires de route et les middleware
+ne nécessitent aucun travail supplémentaire. If synchronous code throws an error, then Express will
+catch and process it. Par exemple :
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express va attraper cela tout seul.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Passez des erreurs à Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+À partir de Express 5, les gestionnaires de route et les middleware qui retournent une Promise
+appelleront automatiquement `next(value)` quand ils rejettent ou lancent une erreur.
+Par exemple :
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = wait getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Si `getUserById` lance une erreur ou un rejet, `next` sera appelé avec soit
+l'erreur émise ou la valeur rejetée. Si aucune valeur rejetée n'est fournie, `next`
+sera appelée avec un objet Error par défaut fourni par le routeur Express.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+Si le callback dans une séquence ne fournit aucune donnée, seulement des erreurs, vous pouvez simplifier
+ce code comme suit:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Dans l'exemple ci-dessus, `next` est fourni comme callback pour `fs.writeFile`,
+qui est appelé avec ou sans erreurs. S'il n'y a pas d'erreur, le second
+est exécuté, sinon Express attrape et traite l'erreur.
+
+Vous devez attraper les erreurs qui se produisent dans le code asynchrone invoqué par les gestionnaires de route ou
+middleware et les passer à Express pour le traitement. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    essayez {
+      throw new Error('BROKEN');
+    } attraper (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+L'exemple ci-dessus utilise un bloc `try...catch` pour attraper des erreurs dans le code
+asynchrone et les passer à Express. Si le bloc `try...catch`
+était omis, Express ne attrapera pas l'erreur car il ne fait pas partie du code du gestionnaire
+synchrone.
+
+Utilise des promesses pour éviter les frais généraux du bloc `essayer...catch` ou lorsque tu utilises les fonctions
+qui renvoient des promesses. Par exemple :
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Les erreurs seront passées à Express.
+});
+```
+
+Puisque les promesses attrapent automatiquement à la fois les erreurs synchrones et les promesses rejetées,
+vous pouvez simplement fournir `next` car le gestionnaire de capture final et Express attrapera des erreurs,
+parce que le gestionnaire de capture est donné l'erreur comme premier argument.
+
+Vous pouvez également utiliser une chaîne de gestionnaires pour vous fier à l'erreur synchrone
+attrapant, en réduisant le code asynchrone à quelque chose de trivial. Par exemple :
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = data;
+      next(err);
+    });
+  },
+  fonction (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+L'exemple ci-dessus a quelques déclarations triviales de l'appel `readFile`
+. Si `readFile` cause une erreur, alors il passe l'erreur à Express, sinon vous
+revenez rapidement au monde de la gestion des erreurs synchrones dans le prochain gestionnaire
+de la chaîne. Ensuite, l'exemple ci-dessus tente de traiter les données. Si cela échoue, alors le gestionnaire d'erreurs synchrone
+l'attrapera. Si vous aviez fait ce traitement à l'intérieur de
+la callback `readFile`, alors l'application pourrait quitter et les gestionnaires d'erreur
+Express ne s'exécuteraient pas.
+
+Quelle que soit la méthode que vous utilisez, si vous voulez que les gestionnaires d'erreur Express soient appelés et que l'application
+survive, vous devez vous assurer qu'Express reçoit l'erreur.
+
+## Le gestionnaire d'erreur par défaut
+
+Express est livré avec un gestionnaire d'erreur intégré qui prend en charge toutes les erreurs qui peuvent être rencontrées dans l'application. Cette fonction middleware par défaut est ajoutée à la fin de la pile de fonctions du middleware.
+
+Si vous passez une erreur à `next()` et que vous ne la gérez pas dans un gestionnaire d'erreur personnalisé
+, il sera géré par le gestionnaire d'erreur intégré ; l'erreur sera
+écrite au client avec la trace de la pile. La trace de la pile n'est pas incluse
+dans l'environnement de production.
+
+<Alert type="Infos">
+
+Définissez la variable d'environnement `NODE_ENV` à `production`, pour exécuter l'application en mode production.
+
+</Alert>
+
+Lorsqu'une erreur est écrite, les informations suivantes sont ajoutées à la réponse
+:
+
+- Le `res.statusCode` est défini à partir de `err.status` (ou `err.statusCode`). Si
+  cette valeur est en dehors de la plage 4xx ou 5xx, elle sera définie à 500.
+- Le `res.statusMessage` est défini selon le code de statut.
+- Le corps sera le HTML du message de code de statut lorsque l'environnement de production
+  , sinon sera `err.stack`.
+- N'importe quel en-tête spécifié dans un objet `err.headers`.
+
+Si vous appelez `next()` avec une erreur après avoir commencé à écrire la réponse
+(par exemple, si vous rencontrez une erreur lors du streaming de la réponse
+au client), le gestionnaire d'erreur par défaut Express ferme la connexion
+et échoue la requête.
+
+Ainsi, lorsque vous ajoutez un gestionnaire d'erreurs personnalisé, vous devez déléguer à
+le gestionnaire d'erreur Express par défaut, lorsque les en-têtes
+ont déjà été envoyés au client :
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Notez que le gestionnaire d'erreur par défaut peut être déclenché si vous appelez `next()` avec une erreur
+dans votre code plusieurs fois, même si une gestion personnalisée des erreurs est en place.
+
+D'autres erreurs de gestion du middleware peuvent être trouvées dans [middleware Express](/en/resources/middleware).
+
+## Écriture des gestionnaires d'erreurs
+
+Définissez les fonctions du middleware de la même manière que les autres fonctions du middleware,
+excepté les fonctions de gestion des erreurs ont quatre arguments au lieu de trois:
+`(err, req, res, next)`. Par exemple :
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Quelque chose s'est cassé !');
+});
+```
+
+Vous définissez le middleware en dernier lieu, après d'autres appels `app.use()` et routage des appels; par exemple:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    étendu: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // logique
+});
+```
+
+Les réponses provenant d'une fonction middleware peuvent être dans n'importe quel format, comme une page d'erreur HTML, un message simple ou une chaîne JSON.
+
+Pour des raisons organisationnelles (et pour un cadre de plus haut niveau), vous pouvez définir
+plusieurs fonctions de gestion des erreurs du middleware, tout comme vous le feriez avec les fonctions
+régulières du middleware. Par exemple, pour définir un gestionnaire d'erreurs
+pour les requêtes faites en utilisant `XHR` et ceux sans :
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+application.se(
+  bodyParser.urlencoded({
+    étendu: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+Dans cet exemple, les génériques `logErrors` peuvent écrire la requête et les informations d'erreur
+à `stderr`, par exemple :
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Aussi dans cet exemple, `clientErrorHandler` est défini comme suit ; dans ce cas, l'erreur est explicitement passée au suivant.
+
+Notez que lorsque _not_ appelez "next" dans une fonction de gestion des erreurs, vous êtes responsable de l'écriture (et de la fin) de la réponse. Sinon, ces demandes seront « bloquées » et ne seront pas admissibles au ramassage des déchets.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Quelque chose a échoué!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implémenter la fonction "catch-all" `errorHandler` comme suit (par exemple):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Si vous avez un gestionnaire de route avec plusieurs fonctions de rappel, vous pouvez utiliser le paramètre `route` pour passer au gestionnaire de route suivant. Par exemple :
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user. asPaid) {
+      // continue à gérer cette requête
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent. ind(err, doc) => {
+      if (err) return next(err);
+      res. son(doc);
+    });
+  }
+);
+```
+
+Dans cet exemple, le gestionnaire `getPaidContent` sera ignoré, mais tous les gestionnaires restants dans `app` pour `/a_route_behind_paywall` continueront d'être exécutés.
+
+<Alert type="Infos">
+
+Les appels à `next()` et `next(err)` indiquent que le gestionnaire actuel est complet et dans quel état.
+`next(err)` sautera tous les gestionnaires restants de la chaîne, à l'exception de ceux qui sont configurés à
+gérer les erreurs comme décrit ci-dessus.
+
+</Alert>
diff --git a/src/content/docs/fr/5x/guide/overriding-express-api.md b/src/content/docs/fr/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..fdd81c674a
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Outrepasser l'API Express
+description: Découvrez comment personnaliser et étendre l'API Express.js en écrasant les méthodes et les propriétés sur les objets de demande et de réponse à l'aide de prototypes.
+---
+
+L'API Express se compose de différentes méthodes et propriétés sur les objets de requête et de réponse. Celles-ci sont héritées du prototype. Il y a deux points d'extension pour l'API Express :
+
+1. Les prototypes globaux à `express.request` et `express.response`.
+2. Prototypes spécifiques à l'application à `app.request` et `app.response`.
+
+Modifier les prototypes globaux affectera toutes les applications Express chargées dans le même processus. Si vous le souhaitez, les modifications peuvent être apportées à l'application en modifiant uniquement les prototypes spécifiques à l'application après avoir créé une nouvelle application.
+
+## Méthodes
+
+Vous pouvez remplacer la signature et le comportement des méthodes existantes avec vos propres méthodes en assignant une fonction personnalisée.
+
+Voici un exemple de surcharge du comportement de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+L'implémentation ci-dessus modifie complètement la signature originale de `res.sendStatus`. Il accepte maintenant un code de statut, un type d'encodage, et le message à envoyer au client.
+
+La méthode surchargée peut maintenant être utilisée de cette manière:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Propriétés
+
+Les propriétés de l'API Express sont soit :
+
+1. Propriétés assignées (ex: `req.baseUrl`, `req.originalUrl`)
+2. Défini comme getters (ex: `req.secure`, `req.ip`)
+
+Puisque les propriétés de la catégorie 1 sont assignées dynamiquement sur les objets `request` et `response` dans le contexte du cycle de réponse de la requête courante, leur comportement ne peut pas être remplacé.
+
+Les propriétés de la catégorie 2 peuvent être écrasées en utilisant l'API des extensions API Express.
+
+Le code suivant réécrit comment la valeur de `req.ip` doit être dérivée. Maintenant, il retourne simplement la valeur de l'en-tête de la requête `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+Afin de fournir l'API Express, les objets de requête/réponse passés à Express (via `app(req, res)`, par exemple) doivent hériter de la même chaîne de prototypes. Par défaut, c'est `http.IncomingRequest.prototype` pour la requête et `http.ServerResponse.prototype` pour la réponse.
+
+Sauf si nécessaire, il est recommandé de le faire uniquement au niveau de l'application, plutôt qu'au niveau mondial. Veillez également à ce que le prototype utilisé corresponde le plus près possible à la fonctionnalité des prototypes par défaut.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/fr/5x/guide/routing.mdx b/src/content/docs/fr/5x/guide/routing.mdx
new file mode 100644
index 0000000000..3c009b7b16
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routage
+description: Apprenez à définir et utiliser des routes dans les applications Express.js, y compris les méthodes de trajet, les chemins de trajet, les paramètres et l'utilisation du routeur pour le routage modulaire.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ indique comment les terminaux (URIs) d'une application répondent aux requêtes du client.
+Pour une introduction au routage, voir [Routage de base](/en/starter/basic-routing).
+
+Vous définissez le routage à l'aide des méthodes de l'objet Express `app` qui correspondent aux méthodes HTTP;
+par exemple, `app. et()` pour gérer les requêtes GET et `app.post` pour gérer les requêtes POST. Pour une liste complète,
+voir [app.METHOD](/en/5x/api#app.METHOD). Vous pouvez également utiliser [app.all()](/en/5x/api#app.all) pour gérer toutes les méthodes HTTP et [app. se()](/en/5x/api#app.use) à
+spécifient le middleware comme fonction de callback (Voir [Utilisation du middleware](/en/guide/using-middleware) pour plus de détails).
+
+Ces méthodes de routage spécifient une fonction de rappel (parfois appelée "fonctions de gestionnaire") appelée lorsque l'application reçoit une requête vers la route spécifiée (endpoint) et la méthode HTTP. En d'autres termes, l'application "écoute" les requêtes qui correspondent à la(les) route(s) spécifiée(s) et à la(les) méthode(s), et quand il détecte une correspondance, il appelle la fonction de rappel spécifiée.
+
+En fait, les méthodes de routage peuvent avoir plus d'une fonction de rappel en tant qu'arguments.
+Avec plusieurs fonctions de rappel, il est important de fournir `next` comme argument à la fonction de callback puis appeler `next()` dans le corps de la fonction pour distribuer le contrôle
+au prochain rappel.
+
+Le code suivant est un exemple de route très basique.
+
+```js
+const express = require('express');
+const app = express();
+
+// répond avec "bonjour le monde" lorsqu'une demande GET est faite à l'application
+de la page d'accueil. et('/', (req, res) => {
+  res.send('bonjour le monde');
+});
+```
+
+## Méthodes de la route
+
+Une méthode de route est dérivée d'une des méthodes HTTP, et est attachée à une instance de la classe `express`.
+
+Le code suivant est un exemple de routes qui sont définies pour le `GET` et les méthodes `POST` à la racine de l'application.
+
+```js
+// Route de la méthode GET
+app.get('/', (req, res) => {
+  res. end('Requête GET sur la page d'accueil');
+});
+
+// La méthode POST route
+app. ost('/', (req, res) => {
+  res.send('Requête POST sur la page d'accueil');
+});
+```
+
+Express supporte les méthodes qui correspondent à toutes les méthodes de requête HTTP : `get`, `post`, et ainsi de suite.
+Pour une liste complète, voir [app.METHOD](/en/5x/api#app.METHOD).
+
+Il y a une méthode de routage spéciale, `app.all()`, utilisée pour charger les fonctions du middleware à un chemin pour _toutes_ les méthodes de requête HTTP. Par exemple, le gestionnaire suivant est exécuté pour les requêtes vers la route `"/secret"` si vous utilisez `GET`, `POST`, `PUT`, `DELETE`, ou toute autre méthode de requête HTTP supportée dans le module [http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accéder à la section secrète ...');
+  next(); // passer le contrôle au prochain gestionnaire
+});
+```
+
+## Chemins de la route
+
+Les chemins de la route, en combinaison avec une méthode de requête, définissent les points de terminaison à partir desquels les requêtes peuvent être faites. Les chemins de route peuvent être des chaînes, des chaînes de caractères ou des expressions régulières.
+
+<Alert type="Alerte">
+
+En express 5, les caractères `? , `+`, `\*`, `[]`et `()\` sont gérés différemment de la version
+4, veuillez consulter le [guide de migration](/en/guide/migrating-5#path-syntax) pour plus d'informations.
+
+</Alert>
+
+<Alert type="Alerte">
+
+Dans l'expression expresse 4, des caractères d'expression régulière tels que `$` doivent être échappés avec un `\`.
+
+</Alert>
+
+<Alert type="Infos">
+
+Express utilise [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) pour correspondre aux chemins de la route
+; consultez la documentation path-to-regexp pour toutes les possibilités dans la définition des chemins d'itinéraire.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) est un outil pratique pour
+qui teste les routes Express de base, bien qu'il ne supporte pas la recherche de masques.
+
+</Alert>
+
+<Alert type="warning">Les chaînes de requête ne font pas partie du chemin de la route.</Alert>
+
+### Chemins de route basés sur des chaînes de caractères
+
+Ce chemin de route correspond aux requêtes vers la route racine, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Ce chemin de route correspond aux requêtes à `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Ce chemin de route correspondra aux requêtes à `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Chemins de route basés sur des chaînes de caractères
+
+<Alert type="Alerte">
+
+Les masques de chaînes de caractères dans Express 5 ne fonctionnent plus. Veuillez vous référer au guide de migration
+&#x20;pour plus d'informations.
+
+</Alert>
+
+Ce chemin de route correspondra à `acd` et `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Ce chemin correspondra à `abcd`, `abbcd`, `abbbcd`, et ainsi de suite.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Ce chemin correspondra à `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, et ainsi de suite.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Ce chemin de route correspondra à `/abe` et `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Chemins de route basés sur des expressions régulières
+
+Ce chemin d'itinéraire correspondra à tout ce qui contient un "a".
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Ce chemin d'itinéraire correspondra à `butterfly` et `dragonfly`, mais pas `butterflyman`, `dragonflyman`, et ainsi de suite.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Paramètres de la route
+
+Les paramètres de la route sont des segments d'URL nommés qui sont utilisés pour capturer les valeurs spécifiées à leur position dans l'URL. Les valeurs capturées sont remplies dans l'objet `req.params`, avec le nom du paramètre route spécifié dans le chemin comme leurs clés respectives.
+
+```
+Chemin de la route : /users/:userId/books/:bookId
+URL de requête : http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Pour définir des routes avec des paramètres d'itinéraire, il suffit de spécifier les paramètres de l'itinéraire dans le chemin de la route comme indiqué ci-dessous.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="Alerte">
+
+Le nom des paramètres de route doit être composé de "mots caractères" ([A-Za-z0-9_]).
+
+</Alert>
+
+Puisque le trait d'union (`-`) et le point (`.`) sont interprétés littéralement, ils peuvent être utilisés avec des paramètres d'itinéraire à des fins utiles.
+
+```
+Chemin de la route : /flights/:from-:to
+URL de requête : http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Chemin de la route : /plantae/:genus.:espèce
+URL de requête : http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="Alerte">
+
+Dans l’express 5, les caractères Regexp ne sont pas pris en charge dans les chemins de route, pour plus d’informations, veuillez
+vous référer au [guide de migration](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Pour avoir plus de contrôle sur la chaîne exacte qui peut être associée à un paramètre de route, vous pouvez ajouter une expression régulière entre parenthèses (`()`) :
+
+```
+Chemin de la route : /user/:userId(\d+)
+URL de requête : http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="avertissement">
+
+Parce que l'expression régulière fait généralement partie d'une chaîne littérale, Assurez-vous d'échapper à n'importe quel caractère `\`
+avec un antislash supplémentaire, par exemple `\d+`.
+
+</Alert>
+
+<Alert type="avertissement">
+Dans Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">le caractère `*` dans les expressions régulières n'est pas interprété de la manière habituelle</a>. Comme solution de contournement, utilisez `{0,}` au lieu de `*`. Cela sera probablement corrigé dans Express 5.
+</Alert>
+
+## Gestionnaires de routes
+
+Vous pouvez fournir plusieurs fonctions de rappel qui se comportent comme [middleware](/en/guide/using-middleware) pour traiter une requête. La seule exception est que ces callbacks peuvent appeler `next('route')` pour contourner les rappels de route restants. Vous pouvez utiliser ce mécanisme pour imposer des conditions préalables sur une route, passent ensuite le contrôle aux routes suivantes s'il n'y a pas de raison de poursuivre l'itinéraire courant.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params. d === '0') {
+    return next('route');
+  }
+  res. end(`Utilisateur ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Gestionnaire spécial pour l'identifiant utilisateur 0');
+});
+```
+
+Dans cet exemple :
+
+- `GET /user/5` → géré par la première route → envoie "Utilisateur 5"
+- `GET /user/0` → première route appelle `next('route')`, passe à la prochaine route correspondant à `/user/:id`
+
+Les gestionnaires de routes peuvent être sous la forme d'une fonction, d'un tableau de fonctions, ou de combinaisons des deux, comme indiqué dans les exemples suivants.
+
+Une seule fonction de rappel peut gérer une route. Par exemple :
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Bonjour de A!');
+});
+```
+
+Plus d'une fonction de rappel peut gérer une route (assurez-vous de spécifier l'objet `next`). Par exemple :
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('la réponse sera envoyée par la fonction suivante . .');
+    next();
+  },
+  (req, res) => {
+    end('Bonjour de B!');
+  }
+);
+```
+
+Un tableau de fonctions de rappel peut gérer une route. Par exemple :
+
+```js
+const cb0 = function (req, res, suivant) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  end('Bonjour de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Une combinaison de fonctions indépendantes et de tableaux de fonctions peut gérer une route. Par exemple :
+
+```js
+const cb0 = function (req, res, suivant) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  suivante();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('la réponse sera envoyée par la fonction suivante . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Bonjour de D!');
+  }
+);
+```
+
+## Méthodes de réponse
+
+Les méthodes de l'objet de réponse (`res`) dans la table suivante peuvent envoyer une réponse au client et terminer le cycle de réponse de la requête. Si aucune de ces méthodes n'est appelée à partir d'un gestionnaire d'itinéraire, la requête du client sera suspendue.
+
+| Méthode                                       | Libellé                                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Demander au téléchargement un fichier.                                                            |
+| [res.end()](/en/5x/api#res.end)               | Terminer le processus de réponse.                                                                 |
+| [res.json()](/en/5x/api#res.json)             | Envoyer une réponse JSON.                                                                         |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envoyer une réponse JSON avec le support JSONP.                                                   |
+| [res.redirect()](/en/5x/api#res.redirect)     | Rediriger une requête.                                                                            |
+| [res.render()](/en/5x/api#res.render)         | Afficher un modèle de vue.                                                                        |
+| [res.send()](/en/5x/api#res.send)             | Envoyer une réponse de différents types.                                                          |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Envoyer un fichier en tant que flux octet.                                                        |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Définit le code de statut de la réponse et envoie sa représentation en tant que corps de réponse. |
+
+## app.route()
+
+Vous pouvez créer des gestionnaires de routes chaînables pour un chemin en utilisant `app.route()`.
+Parce que le chemin est spécifié à un seul endroit, la création de routes modulaires est utile, tout comme la réduction de la redondance et des fautes de frappe. Pour plus d'informations sur les routes, voir : [Documentation de Router()](/en/5x/api#router).
+
+Voici un exemple de gestionnaires de routes enchaînés qui sont définis en utilisant `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    end('Obtenir un livre aléatoire');
+  })
+  .ost((req, res) => {
+    res.send('Ajouter un livre');
+  })
+  .ut((req, res) => {
+    res.send('Mettre à jour le livre');
+  });
+```
+
+## Routeur
+
+Utilisez la classe `express.Router` pour créer des gestionnaires de route modulaires et montables. Une instance `Router` est un système complet de middleware et de routage ; pour cette raison, elle est souvent appelée "mini-app".
+
+L'exemple suivant crée un routeur en tant que module, charge une fonction middleware dedans, définit quelques routes, et monte le module routeur sur un chemin dans l'application principale.
+
+Créez un fichier de routeur nommé `birds.js` dans le répertoire de l'application, avec le contenu suivant :
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Ensuite, chargez le module routeur dans l'application :
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', oiseaux);
+```
+
+L'application sera maintenant en mesure de traiter les demandes vers `/birds` et `/birds/about`, ainsi que d'appeler la fonction middleware `timeLog` qui est spécifique à la route.
+
+Mais si la route parente `/birds` a des paramètres de chemin, elle ne sera pas accessible par défaut à partir des sous-routes. Pour le rendre accessible, vous devrez passer l'option `mergeParams` au constructeur de routeur [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/fr/5x/guide/using-middleware.mdx b/src/content/docs/fr/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..3cb37d1ab5
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Utilisation du middleware
+description: Apprenez à utiliser les middleware dans les applications Express.js, y compris les middleware de niveau application et routeur, la gestion des erreurs et l'intégration de logiciels tiers middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express est un framework web de routage et de middleware qui possède des fonctionnalités minimales : Une application Express est essentiellement une série d'appels de fonctions de middleware.
+
+Les fonctions _Middleware_ sont des fonctions qui ont accès à l'objet [request object](/en/5x/api#req) (`req`), l'objet [réponse](/en/5x/api#res) (`res`), et la prochaine fonction du middleware dans le cycle de réponse de l'application. La prochaine fonction du middleware est généralement dénotée par une variable nommée `next`.
+
+Les fonctions Middleware peuvent effectuer les tâches suivantes :
+
+- Exécuter n'importe quel code.
+- Effectuez des modifications à la requête et aux objets de réponse.
+- Termine le cycle de réponse de la requête.
+- Appeler la prochaine fonction du middleware dans la pile.
+
+Si la fonction middleware actuelle ne met pas fin au cycle de réponse de requête, elle doit appeler `next()` pour passer le contrôle à la prochaine fonction du middleware. Sinon, la demande sera laissée en suspens.
+
+Une application Express peut utiliser les types de middleware suivants :
+
+- (#middleware.application)
+- [middleware au niveau du routeur] (#middleware.router)
+- (#middleware.error-handling)
+- (#middleware.built-in)
+- [middleware de tierce partie](#middleware.third-party)
+
+Vous pouvez charger le middleware au niveau de l'application et du routeur avec un chemin de montage optionnel.
+Vous pouvez également charger une série de fonctions middleware ensemble, ce qui crée une sous-pile du système middleware à un point de montage.
+
+## Outil d'interface de l'application
+
+Lier le middleware au niveau de l'application à une instance de l'objet [app object](/en/5x/api#app) en utilisant `app.use()` et `app. Les fonctions ETHOD()`, où `METHOD` est la méthode HTTP de la requête que la fonction middleware gère (comme GET, PUT ou POST) en minuscule.
+
+Cet exemple montre une fonction middleware sans chemin de montage. La fonction est exécutée chaque fois que l'application reçoit une requête.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Cet exemple montre une fonction middleware montée sur le chemin `/user/:id`. La fonction est exécutée pour n'importe quel type de requête HTTP
+sur le chemin `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Cet exemple montre une route et sa fonction de gestion (système middleware). La fonction gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Voici un exemple de chargement d'une série de fonctions middleware à un point de montage, avec un chemin de montage.
+Il illustre une sous-pile middleware qui affiche les informations de requête pour tout type de requête HTTP vers le chemin `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console. og('Type de requête :', req.method);
+    suivant();
+  }
+;
+```
+
+Les gestionnaires de routes vous permettent de définir plusieurs routes pour un chemin. L'exemple ci-dessous définit deux routes pour les requêtes GET vers le chemin `/user/:id`. La deuxième route ne posera aucun problème, mais elle ne sera jamais appelée parce que le premier parcours termine le cycle de réponse de la requête.
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('Info utilisateur');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui affiche l'identifiant utilisateur
+. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Pour sauter le reste des fonctions du middleware à partir d'une pile de middleware du routeur, appelez `next('route')` pour passer le contrôle à la route suivante.
+
+<Alert type="Infos">
+
+`next('route')` ne fonctionnera que dans les fonctions du middleware qui ont été chargées en utilisant les fonctions
+`app.METHOD()` ou `router.METHOD()`.
+
+</Alert>
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // si l'identifiant de l'utilisateur est 0, passer à la route
+    suivante si (req. arams. d === '0') next('route');
+    // sinon passez le contrôle à la prochaine fonction du middleware de cette pile
+    else next();
+  },
+  (req, res, next) => {
+    // envoie une réponse régulière
+    res. end('regular');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui envoie une réponse spéciale
+. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Les Middleware peuvent également être déclarés dans un tableau pour être réutilisables.
+
+Cet exemple montre un tableau avec une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Type de requête:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## middleware au niveau du routeur
+
+Le middleware au niveau du routeur fonctionne de la même manière que le middleware au niveau de l'application, sauf qu'il est lié à une instance de `express.Router()`.
+
+```js
+routeur const = express.Router();
+```
+
+Charger le middleware au niveau du routeur en utilisant les fonctions `router.use()` et `router.METHOD()`.
+
+L'exemple suivant réplique le système middleware qui est affiché ci-dessus pour le middleware au niveau de l'application, en utilisant le middleware au niveau du routeur:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. і();
+
+// une fonction middleware sans chemin de montage. Ce code est exécuté pour chaque requête au routeur
+. se(req, res, next) => {
+  console.log('Heure:', Date. ow());
+  next();
+});
+
+// une sous-pile middleware affiche les informations de requête pour tout type de requête HTTP vers le routeur /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    . og('Type de requête:', req. ethod);
+    suivante();
+  }
+);
+
+// une sous-pile middleware qui gère les requêtes GET sur le routeur /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // si l'identifiant de l'utilisateur est 0, passer au routeur
+    suivant si (req. arams. d === '0') next('route');
+    // passe autrement le contrôle à la prochaine fonction du middleware de cette pile
+    else next();
+  },
+  (req, res, next) => {
+    // renvoie une page normale
+    res. ender('regular');
+  }
+);
+
+// gestionnaire pour le chemin /user/:id qui affiche une page spéciale
+. et('/user/:id', (req, res, next) => {
+  . og(req.params.id);
+  res.render('special');
+});
+
+// monte le routeur sur l'application
+app.use('/', router);
+```
+
+Pour sauter le reste des fonctions du middleware du routeur, appelez `next('router')`
+pour passer le contrôle hors de l'instance du routeur.
+
+Cet exemple montre une sous-pile middleware qui gère les requêtes GET vers le chemin `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. і();
+
+// prédice le routeur avec un contrôle et un renflouement si nécessaire le routeur
+. se(req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+routeur. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// utilise le routeur et 401 tout ce qui passe par l'application
+. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Gestion des erreurs du middleware
+
+<Alert type="Alerte">
+
+La gestion d'erreurs du middleware prend toujours _four_ arguments. Vous devez fournir quatre arguments à
+l'identifier comme une fonction de gestion des erreurs du middleware. Même si vous n'avez pas besoin d'utiliser l'objet `next`
+, vous devez le spécifier pour maintenir la signature. Sinon, l'objet `next` sera
+interprété comme un middleware normal et ne gérera pas les erreurs.
+
+</Alert>
+
+Définissez les fonctions du middleware de la même manière que les autres fonctions du middleware, sauf avec quatre arguments au lieu de trois, spécifiquement avec la signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Quelque chose s'est cassé !');
+});
+```
+
+Pour plus de détails sur la gestion des erreurs du middleware, voir : [Gestion des erreurs](/en/guide/error-handling).
+
+## middleware intégré
+
+À partir de la version 4.x, Express ne dépend plus de [Connect](https://github.com/senchalabs/connect). Les fonctions du middleware
+qui étaient précédemment incluses avec Express sont maintenant dans des modules séparés ; voir [la liste des fonctions du middleware] (https://github.com/senchalabs/connect#middleware).
+
+Express a les fonctions internes suivantes :
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) analyse les requêtes entrantes avec des charges utiles JSON. **NOTE : Disponible avec Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analyse les requêtes entrantes avec des charges utiles encodées en URL. **NOTE : Disponible avec Express 4.16.0+**
+
+## middleware de tierce partie
+
+Utilisez des logiciels tiers pour ajouter des fonctionnalités aux applications Express.
+
+Installez le module Node.js pour la fonctionnalité requise, puis chargez-le dans votre application au niveau de l'application ou au niveau du routeur.
+
+L'exemple suivant illustre l'installation et le chargement de la fonction middleware d'analyse de cookies `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// charge le middleware
+app.use(cookieParser());
+```
+
+Pour une liste partielle des fonctions middleware tierces qui sont couramment utilisées avec Express, voir : [middleware de tierce] (../resources/middleware).
diff --git a/src/content/docs/fr/5x/guide/using-template-engines.mdx b/src/content/docs/fr/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..af25252ab8
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utiliser les moteurs de gabarits avec Express
+description: Découvrez comment intégrer et utiliser des moteurs de gabarits tels que Pug, Handlebars et EJS avec Express.js pour rendre les pages HTML dynamiques efficacement.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un _moteur de modèle_ vous permet d'utiliser des fichiers de modèles statiques dans votre application. Lors de l'exécution, le moteur de gabarit remplace les variables
+dans un fichier de gabarit par des valeurs réelles, et transforme le modèle en un fichier HTML envoyé au client.
+Cette approche facilite la conception d'une page HTML.
+
+Le [générateur d'application Express](/en/starter/generator) utilise [Pug](https://pugjs.org/api/getting-started.html) par défaut, mais il supporte aussi [Handlebars](https://www.npmjs.com/package/handlebars), et [EJS](https://www.npmjs.com/package/ejs), entre autres.
+
+Pour afficher les fichiers de gabarit, définissez les [propriétés de réglage de l'application](/en/4x/api#app.set), dans le `app.js` par défaut créé par le générateur:
+
+- `views`, le répertoire où se trouvent les fichiers de modèle. Ex. : `app.set('vues', './views')`.
+  Par défaut, le répertoire `views` se trouve à la racine de l'application.
+- `voir le moteur`, le moteur de gabarit à utiliser. Par exemple, pour utiliser le moteur de gabarit Pug : `app.set('moteur de vue', 'pug')`.
+
+Ensuite, installez le paquet npm correspondant au moteur de gabarits ; par exemple pour installer Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="Alerte">
+Les moteurs de gabarits conformes à la norme Express tels que Pug exportent une fonction nommée `__express(filePath, options, callback)`,
+qui `res.render()` appelle pour rendre le code du gabarit.
+
+Certains moteurs de gabarits ne suivent pas cette convention. La bibliothèque [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+suit cette convention en mappant tous les moteurs de gabarits populaires Node.js, et fonctionne donc parfaitement dans Express.
+
+</Alert>
+
+Une fois que le moteur de vue est défini, vous n'avez pas à spécifier le moteur ou charger le module moteur de gabarit dans votre application ;
+Express charge le module en interne, par exemple :
+
+```js
+app.set('moteur d'affichage', 'pug');
+```
+
+Ensuite, créez un fichier de modèle Pug nommé `index.pug` dans le dossier `views`, avec le contenu suivant:
+
+```pug
+html
+  devant
+    title= titre
+  corps
+    h1= message
+```
+
+Créez une route pour afficher le fichier `index.pug`. Si la propriété `view engine` n'est pas définie,
+vous devez spécifier l'extension du fichier `view`. Sinon, vous pouvez l'oublier.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Bonjour !' });
+});
+```
+
+Lorsque vous faites une requête sur la page d'accueil, le fichier `index.pug` sera rendu en HTML.
+
+Le cache du moteur de vue ne cache pas le contenu de la sortie du modèle, seulement le modèle sous-jacent. La vue est toujours rendue à chaque requête, même lorsque le cache est activé.
diff --git a/src/content/docs/fr/5x/guide/writing-middleware.mdx b/src/content/docs/fr/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..4ca68601a4
--- /dev/null
+++ b/src/content/docs/fr/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Écriture de middleware pour utilisation dans les applications Express
+description: Apprenez à écrire des fonctions personnalisées de middleware pour les applications Express.js, y compris des exemples et des pratiques exemplaires pour améliorer la gestion des requêtes et des réponses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Les fonctions _Middleware_ sont des fonctions qui ont accès à l'objet [request object](/en/5x/api#req) (`req`), l'objet [réponse](/en/5x/api#res) (`res`), et la fonction `next` dans le cycle de réponse de l'application. La fonction `next` est une fonction dans le routeur Express qui, lorsqu'elle est appelée, exécute le middleware qui succède au middleware actuel.
+
+Les fonctions Middleware peuvent effectuer les tâches suivantes :
+
+- Exécuter n'importe quel code.
+- Effectuez des modifications à la requête et aux objets de réponse.
+- Termine le cycle de réponse de la requête.
+- Appelez le prochain middleware dans la pile.
+
+Si la fonction middleware actuelle ne met pas fin au cycle de réponse de requête, elle doit appeler `next()` pour passer le contrôle à la prochaine fonction du middleware. Sinon, la demande sera laissée en suspens.
+
+La figure suivante montre les éléments d'un appel de fonction middleware :
+
+![Elements of a middleware function call](/images/express-mw.png)
+
+À partir de Express 5, les fonctions middleware qui retournent une Promise appelleront `next(value)` quand elles rejettent ou lancent une erreur. `next` sera appelé avec la valeur rejetée ou avec l'erreur levée.
+
+## Exemple
+
+Voici un exemple de simple application "Hello World" Express.
+Le reste de cet article va définir et ajouter trois fonctions middleware à l'application :
+un appelé `myLogger` qui affiche un message de log simple. on appelle `requestTime` que
+affiche l'horodatage de la requête HTTP, et un appelé `validateCookies` qui valide les cookies entrants.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Fonction Middleware myLogger
+
+Voici un exemple simple d'une fonction middleware appelée "myLogger". Cette fonction affiche seulement
+"LOGGED" lorsqu'une requête vers l'application passe à travers elle. La fonction middleware est assignée à une variable
+nommée `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="Alerte">
+
+Notez l'appel ci-dessus à `next()`. Appeler cette fonction appelle la prochaine fonction du middleware dans
+l'application. La fonction `next()` n'est pas une partie du noeud. s ou API Express, mais est le troisième argument
+qui est passé à la fonction middleware. La fonction `next()` pourrait être nommée quoi que ce soit,
+mais par convention elle est toujours nommée "next". Pour éviter toute confusion, utilisez toujours cette convention.
+
+</Alert>
+
+Pour charger la fonction middleware, appelez `app.use()`, en spécifiant la fonction middleware.
+Par exemple, le code suivant charge la fonction middleware `myLogger` avant la route vers le chemin racine (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Chaque fois que l'application reçoit une demande, elle affiche le message "LOGGGED" vers le terminal.
+
+L'ordre de chargement du middleware est important : les fonctions du middleware qui sont chargées en premier sont également exécutées en premier.
+
+Si `myLogger` est chargé après la route vers le chemin racine, la requête ne l'atteint jamais et l'application n'affiche pas "LOGGED", parce que le gestionnaire de route du chemin racine termine le cycle de réponse de requête.
+
+La fonction du middleware `myLogger` affiche simplement un message, passe ensuite la requête à la prochaine fonction middleware de la pile en appelant la fonction `next()`.
+
+### Middleware fonction requestTime
+
+Ensuite, nous allons créer une fonction middleware appelée "requestTime" et ajouter une propriété appelée `requestTime`
+à l'objet requête.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+L'application utilise maintenant la fonction middleware `requestTime`. Aussi, la fonction callback de la route du chemin racine utilise la propriété que la fonction middleware ajoute à `req` (l'objet de requête).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = 'Bonjour le monde!<br>';
+  responseText += `<small>Demandé à: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Lorsque vous faites une demande à la racine de l'application, l'application affiche maintenant l'horodatage de votre requête dans le navigateur.
+
+### format@@0 Middleware function validateCookies
+
+Enfin, nous allons créer une fonction middleware qui valide les cookies entrants et envoie une réponse 400 si les cookies sont invalides.
+
+Voici un exemple de fonction qui valide les cookies avec un service asynchrone externe.
+
+```js
+fonction async cookieValidator(cookies) {
+  essayer {
+    attendre externalyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Cookies invalides');
+  }
+}
+```
+
+Ici, nous utilisons le middleware [`cookie-parser`](/en/resources/middleware/cookie-parser) pour analyser les cookies entrants de l'objet `req` et les passer à notre fonction `cookieValidator`. Le middleware `validateCookies` retourne une Promesse que si le rejet déclenchera automatiquement notre gestionnaire d'erreurs.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+fonction async validateCookies(req, res, next) {
+  attendent cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// gestionnaire d'erreur
+app. se(err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="Alerte">
+
+Notez comment `next()` est appelé après `wait cookieValidator(req.cookies)`. Cela garantit que si
+`cookieValidator` résoud, le prochain middleware de la pile sera appelé. Si vous passez quelque chose
+à la fonction `next()` (sauf la chaîne `'route'` ou `'router'`), Express considère que la requête
+actuelle est une erreur et ignorera toute fonction de routage et de middleware
+qui ne gère pas les autres fonctions de routage.
+
+</Alert>
+
+Parce que vous avez accès à l'objet requête, à l'objet de réponse, à la prochaine fonction du middleware dans la pile, et à l'ensemble du nœud. s API, les possibilités avec les fonctions du middleware sont infinies.
+
+Pour plus d'informations sur le middleware Express, voir : [Utiliser un middleware Express](/en/guide/using-middleware).
+
+## Logiciel middleware configurable
+
+Si vous avez besoin que votre middleware soit configurable, exportez une fonction qui accepte un objet d'options ou d'autres paramètres, qui retourne ensuite l'implémentation du middleware en fonction des paramètres d'entrée.
+
+Fichier: `my-middleware.js`
+
+```js
+module. xports = function (options) {
+  fonction de retour (req, res, next) {
+    // Implémente la fonction middleware basée sur l'objet d'options
+    next();
+  };
+};
+```
+
+Le middleware peut maintenant être utilisé comme montré ci-dessous.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Reportez-vous à [cookie-session](https://github.com/expressjs/cookie-session) et [compression](https://github.com/expressjs/compression) pour des exemples de middleware configurables.
diff --git a/src/content/docs/fr/5x/starter/basic-routing.mdx b/src/content/docs/fr/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..cc7681f5ea
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Routage de base
+description: Apprenez les fondamentaux du routage dans les applications Express.js, y compris comment définir des routes, gérer des méthodes HTTP et créer des gestionnaires de routes pour votre serveur web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ désigne la façon dont une application répond à une requête client à un point de terminaison particulier, qui est une URI (ou un chemin) et une méthode spécifique de requête HTTP (GET, POST, etc.).
+
+Chaque route peut avoir une ou plusieurs fonctions de gestionnaire, qui sont exécutées lorsque la route est correspondante.
+
+La définition de la route prend la structure suivante :
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Où :
+
+- `app` est une instance de `express`.
+- `METHOD` est une [méthode de requête HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), en minuscule.
+- `PATH` est un chemin sur le serveur.
+- `HANDLER` est la fonction exécutée lorsque la route est correspondante.
+
+<Alert type="Alerte">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Si vous n'êtes pas familier avec la création d'une application et son démarrage, consultez l'exemple Bonjour le monde
+.
+
+</Alert>
+
+Les exemples suivants illustrent la définition de routes simples.
+
+Répondez avec `Hello World!` sur la page d'accueil:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Répondre à une requête POST sur la route racine (`/`), la page d'accueil de l'application :
+
+```js
+app.post('/', (req, res) => {
+  res.send('Requête POST');
+});
+```
+
+Répondre à une requête PUT sur la route `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Requête PUT à /user');
+});
+```
+
+Répondre à une requête DELETE sur la route `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Requête DELETE à /user');
+});
+```
+
+Pour plus de détails sur le routage, consultez le [guide de routage] (/en/guide/routing).
diff --git a/src/content/docs/fr/5x/starter/examples.mdx b/src/content/docs/fr/5x/starter/examples.mdx
new file mode 100644
index 0000000000..a0833d9859
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Exemples Express
+description: Explorez une collection d'exemples d'applications Express.js couvrant divers cas d'utilisation, intégrations et configurations avancées pour vous aider à apprendre et à construire vos projets.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Cette page contient la liste des exemples utilisant Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Authentification avec login et mot de passe
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - négociation de contenu HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transfert de fichiers vers le client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Travailler avec un modèle JavaScript embarqué (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Création des pages d'erreur
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Travailler avec un middleware d'erreur
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Gestionnaire de requêtes simple
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown comme moteur de gabarit
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Travailler avec plusieurs routeurs Express
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - Contrôleurs de style MVC
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Suivi de l'activité de l'utilisateur en ligne avec les paquets `online` et `redis`
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Travailler avec les paramètres de la route
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Opérations HTTP multiples sur la même ressource
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organiser des routes à l'aide d'une carte
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Travailler avec le middleware de route
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organiser des routes par ressource
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - Sessions utilisateur
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Servir des fichiers statiques
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Rendu dynamique des vues
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Enregistrement des données dans l'objet de requête entre les appels de middleware
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Service API simple
+
+## Exemples supplémentaires
+
+Ce sont quelques exemples supplémentaires avec des intégrations plus étendues.
+
+<Alert type="avertissement">
+
+Cette information se réfère à des sites tiers, des produits ou des modules tiers qui ne sont pas maintenus par l'équipe
+Expressjs. La liste ci-dessous ne constitue pas une approbation ou une recommandation de l'équipe du projet
+Expressjs.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Application Fullstack avec Express et Next.js en utilisant [Prisma](https://www.npmjs.com/package/prisma) en tant qu'ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API avec Express in TypeScript en utilisant [Prisma](https://www.npmjs.com/package/prisma) en tant qu'ORM
diff --git a/src/content/docs/fr/5x/starter/faq.md b/src/content/docs/fr/5x/starter/faq.md
new file mode 100644
index 0000000000..494c74698b
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: Foire Aux Questions
+description: Retrouvez les réponses aux questions les plus fréquemment posées sur Express.js, y compris les sujets sur la structure de l'application, les modèles, l'authentification, les moteurs de gabarit, la gestion des erreurs, et plus encore.
+---
+
+## Comment structurer ma candidature ?
+
+Il n'y a pas de réponse définitive à cette question. La réponse dépend
+de l'échelle de votre candidature et de l'équipe impliquée. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Les routes et autres logiques spécifiques à une application peuvent vivre dans autant de fichiers
+que vous le souhaitez, dans n'importe quelle structure de répertoire que vous préférez. View the following
+examples for inspiration:
+
+- [Liste des itinéraires](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Il y a également des extensions tierces pour Express, qui simplifient certains de ces modèles:
+
+- [Itinéraire de ressource](https://github.com/expressjs/express-resource)
+
+## Comment définir des modèles?
+
+Express n'a aucune notion de base de données. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+Voir [LoopBack](http://loopback.io) pour un framework basé sur Express, centré autour de modèles.
+
+## Comment puis-je authentifier les utilisateurs ?
+
+Authentication is another opinionated area that Express does not
+venture into. Vous pouvez utiliser n'importe quel schéma d'authentification que vous souhaitez.
+Pour un simple nom d'utilisateur / schéma de mot de passe, voir [cet exemple](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quels moteurs de gabarits sont supportés par Express ?
+
+Express prend en charge tout moteur de gabarit qui est conforme à la signature `(path, locals, callback)`.
+Pour normaliser les interfaces du moteur de gabarits et la mise en cache, consultez le projet
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+pour plus de support. Les moteurs de gabarits non listés peuvent toujours supporter la signature Express.
+
+Pour plus d'informations, voir [Utilisation de moteurs de gabarits avec Express](/en/guide/using-template-engines).
+
+## Comment gérer 404 réponses?
+
+Dans Express, 404 réponses ne sont pas le résultat d'une erreur, donc
+le middleware de gestion d'erreurs ne les capturera pas. Ce comportement est
+car une réponse 404 indique simplement l'absence de travail supplémentaire à faire ;
+en d'autres termes, Express a exécuté toutes les fonctions et routes du middleware,
+et a trouvé qu'aucun d'eux n'a répondu. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Ajoute des routes dynamiquement à l'exécution sur une instance de `express.Router()`
+afin que les routes ne soient pas remplacées par une fonction de middleware.
+
+## Comment configurer un gestionnaire d'erreur ?
+
+Vous définissez le middleware de la même manière que les autres middleware,
+sauf avec quatre arguments au lieu de trois; spécifiquement avec la signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Pour plus d'informations, voir [Gestion des erreurs] (/en/guide/error-handling).
+
+## Comment rendre le HTML simple ?
+
+Vous ne le faites pas! Il n'y a pas besoin de "render" HTML avec la fonction `res.render()`.
+Si vous avez un fichier spécifique, utilisez la fonction `res.sendFile()`.
+Si vous utilisez beaucoup d'actifs depuis un répertoire, utilisez la fonction `express.static()`
+middleware.
+
+## Quelle version de Node.js est requise ?
+
+- [Express 4.x](/en/4x/api) nécessite Node.js 0.10 ou supérieur.
+- [Express 5.x](/en/5x/api) nécessite Node.js 18 ou plus.
diff --git a/src/content/docs/fr/5x/starter/generator.mdx b/src/content/docs/fr/5x/starter/generator.mdx
new file mode 100644
index 0000000000..697016481d
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Générateur d'application Express
+description: Apprenez à utiliser l'outil de générateur d'applications Express pour créer rapidement un squelette pour vos applications Express.js, en rationalisant la configuration et la configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilisez l'outil de générateur d'applications, `express-generator`, pour créer rapidement un squelette d'application.
+
+Vous pouvez exécuter le générateur d'application avec la commande `npx` (disponible dans Node.js 8.2.0).
+
+```bash
+Générateur de npx express $
+```
+
+Pour les versions antérieures de Node, installez le générateur d'application en tant que paquet npm global puis lancez le :
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Affiche les options de la commande avec l'option `-h`:
+
+```bash
+$ express -h
+
+  Utilisation : express [options] [dir]
+
+  Options :
+
+    -h, --help affiche les informations d'utilisation
+        --version affiche le numéro de version
+    -e, --ejs add ejs engine support
+        --hbs add handlebar engine support
+        --pug add pug engine support
+    -H, --hogan add hogan. le support du moteur
+        --no-view générer sans afficher le moteur
+    -v, --view <engine> ajouter la vue <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (par défaut jade)
+    -c, --css <engine>  ajoute la feuille de style <engine> support (moins|stylus|compass|sass) (par défaut, css simple)
+        --git add . itignore
+    -f, --force sur un répertoire non vide
+```
+
+Par exemple, ce qui suit crée une application Express nommée _myapp_. L'application sera créée dans un dossier nommé _myapp_ dans le répertoire de travail actuel et le moteur de vue sera réglé sur <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   créer : monapp/routes/utilisateurs. s
+   créer : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : monapp/bin
+   create : myapp/bin/www
+```
+
+Installez ensuite les dépendances :
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+Sous MacOS ou Linux, exécutez l'application avec cette commande :
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Sous l'invite de commande Windows, utilisez cette commande :
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+Sous Windows PowerShell, utilisez cette commande :
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Ensuite, chargez `http://localhost:3000/` dans votre navigateur pour accéder à l'application.
+
+L'application générée a la structure de répertoire suivante :
+
+```bash
+.
+── app.js
+── bin
+文<unk> ─ www
+── package. fils
+── public
+Ω─ images
+Ω─ javascripts
+文<unk> ── feuilles de style
+Ω<unk> ─ style. ss
+── routes
+文── index.js
+Ω<unk> ── utilisateurs. s
+<unk> ── vues
+    ── erreur. ug
+    ── index.pug
+    <unk> ─ layout.pug
+
+7 répertoires, 9 fichiers
+```
+
+<Alert type="Infos">
+
+La structure d'application créée par le générateur n'est qu'un des nombreux moyens de structurer les applications Express.
+N'hésitez pas à utiliser cette structure ou à la modifier pour mieux répondre à vos besoins.
+
+</Alert>
diff --git a/src/content/docs/fr/5x/starter/hello-world.mdx b/src/content/docs/fr/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..1c7704047e
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Bonjour l'exemple du monde
+description: Commencez avec Express.js en construisant une simple application 'Hello World', en démontrant la configuration de base et la création de serveurs pour les débutants.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="Infos">
+
+Intégré ci-dessous est essentiellement l'application Express la plus simple que vous puissiez créer. C'est une seule application de fichier
+&mdash; _pas_ ce que vous obtiendrez si vous utilisez le [générateur Express](/en/starter/generator), que
+crée l'échafaudage pour une application complète avec de nombreux fichiers JavaScript, des modèles Jade, et des sous-répertoires
+à diverses fins.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Exemple d'application d'écoute sur le port ${port}`);
+});
+```
+
+Cette application démarre un serveur et écoute le port 3000 pour les connexions. L'application répond avec "Hello World!" pour les demandes
+à l'URL racine (`/`) ou _route_. Pour tous les autres chemins, il répondra avec un **404 Not Found**.
+
+## Exécution locale
+
+Créez d'abord un répertoire nommé `myapp`, changez et exécutez `npm init`. Ensuite, installez `express` en tant que dépendance, conformément au [guide d'installation](/en/starter/installing).
+
+Dans le dossier `myapp`, créez un fichier nommé `app.js` et copiez le code à partir de l'exemple ci-dessus.
+
+<Alert type="Alerte">
+
+Les `req` (request) et `res` (response) sont les mêmes objets que le noeud fournit, donc vous pouvez
+appeler `req. ipe()`, `req.on('data', callback)`, et tout autre chose que vous feriez sans Express
+impliqué.
+
+</Alert>
+
+Exécutez l'application avec la commande suivante :
+
+```bash
+$ node app.js
+```
+
+Ensuite, chargez `http://localhost:3000/` dans un navigateur pour voir la sortie.
diff --git a/src/content/docs/fr/5x/starter/installing.mdx b/src/content/docs/fr/5x/starter/installing.mdx
new file mode 100644
index 0000000000..6305971087
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installation en cours
+description: Apprenez à installer Express.js dans votre environnement Node.js, y compris la configuration de votre répertoire de projet et la gestion des dépendances avec npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Avant de commencer, assurez-vous que vous avez [Node.js](https://nodejs.org/) 18 ou supérieur installé. Ensuite, créez un répertoire pour votre application et naviguez dedans.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Utilisez la commande `npm init` pour créer un fichier `package.json` pour votre application.
+Pour plus d'informations sur le fonctionnement de `package.json`, voir [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Cette commande vous invite à trouver un certain nombre de choses, telles que le nom et la version de votre application.
+Pour l'instant, vous pouvez simplement appuyer sur RETURN pour accepter les valeurs par défaut pour la plupart d'entre eux, à l'exception de la règle suivante :
+
+```
+point d'entrée: (index.js)
+```
+
+Entrez `app.js`, ou quel que soit le nom du fichier principal. Si vous voulez qu'il soit `index.js`, appuyez sur RETURN pour accepter le nom de fichier par défaut suggéré.
+
+Maintenant, installez Express dans le répertoire `myapp` et sauvegardez-le dans la liste des dépendances. Par exemple :
+
+```bash
+npm installation express
+```
+
+Pour installer Express temporairement et ne pas l'ajouter à la liste des dépendances :
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/fr/5x/starter/static-files.mdx b/src/content/docs/fr/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..041757b116
--- /dev/null
+++ b/src/content/docs/fr/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servir les fichiers statiques dans Express
+description: Comprendre comment servir les fichiers statiques comme les images, CSS, et JavaScript dans les applications Express.js en utilisant le middleware 'statique' intégré.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Pour servir des fichiers statiques tels que des images, des fichiers CSS et des fichiers JavaScript, utilisez la fonction middleware intégrée `express.static` dans Express.
+
+La signature de la fonction est :
+
+```js
+express.static(root, [options]);
+```
+
+L'argument `root` spécifie le répertoire racine à partir duquel servir les actifs statiques.
+Pour plus d'informations sur l'argument `options`, voir [express.static](/en/5x/api#express.static).
+
+Par exemple, utilisez le code suivant pour servir les images, les fichiers CSS et JavaScript dans un répertoire nommé `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Maintenant, vous pouvez charger les fichiers qui se trouvent dans le répertoire `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="Infos">
+
+Express recherche les fichiers relatifs au répertoire statique, donc le nom du répertoire statique
+ne fait pas partie de l'URL.
+
+</Alert>
+
+Pour utiliser plusieurs répertoires statiques, appelez la fonction middleware `express.static` plusieurs fois :
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express recherche les fichiers dans l'ordre dans lequel vous définissez les répertoires statiques avec la fonction `express.static`.
+
+<Alert type="Infos">
+
+Pour de meilleurs résultats, utilisez un proxy
+inversé pour améliorer les performances de
+servant des actifs statiques.
+
+</Alert>
+
+Pour créer un préfixe de chemin virtuel (où le chemin n'existe pas dans le système de fichiers) pour les fichiers qui sont servis par le fichier `express. fonction tatic`, [spécifiez un chemin de montage](/en/5x/api#app.use) pour le répertoire statique, comme indiqué ci-dessous:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Maintenant, vous pouvez charger les fichiers qui se trouvent dans le dossier `public` à partir du préfixe de chemin `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Cependant, le chemin que vous fournissez à la fonction `express.static` est relatif au répertoire depuis lequel vous lancez votre processus `node`. Si vous exécutez l'application express à partir d'un autre répertoire, il est plus sûr d'utiliser le chemin absolu du répertoire que vous voulez servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Pour plus de détails sur la fonction `serve-static` et ses options, voir [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/it/4x/advanced/developing-template-engines.md b/src/content/docs/it/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..3c00548d60
--- /dev/null
+++ b/src/content/docs/it/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Sviluppo di modelli di motori per Express
+description: Impara a sviluppare motori di template personalizzati per Express.js utilizzando app.engine(), con esempi sulla creazione e l'integrazione della tua logica di rendering dei modelli.
+---
+
+Usa il metodo `app.engine(ext, callback)` per creare il tuo modello di motore. `ext` si riferisce all'estensione del file, e `callback` è la funzione del motore del modello, che accetta i seguenti elementi come parametri: la posizione del file, l'oggetto opzioni, e la funzione di callback.
+
+Il seguente codice è un esempio di implementazione di un semplice modello di motore per il rendering dei file `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+La tua app sarà ora in grado di visualizzare i file `.ntl`. Crea un file chiamato `index.ntl` nella directory `views` con il seguente contenuto.
+
+```pug
+#title#
+#message#
+```
+
+Quindi, crea il seguente percorso nella tua app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando fai una richiesta alla home page, `index.ntl` sarà renderizzato come HTML.
diff --git a/src/content/docs/it/4x/guide/behind-proxies.mdx b/src/content/docs/it/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..a31c0ad959
--- /dev/null
+++ b/src/content/docs/it/4x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Espresso dietro i proxy
+description: Scopri come configurare le applicazioni Express.js per funzionare correttamente dietro i proxy inversi, anche utilizzando l'impostazione del proxy di trust per gestire gli indirizzi IP del client.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Quando si esegue un'app Express dietro un proxy inverso, alcune delle API Express possono restituire valori diversi da quelli previsti. Al fine di adeguarsi a questo, l'impostazione dell'applicazione `trust proxy` può essere utilizzata per esporre le informazioni fornite dal proxy inverso nelle API Express. Il problema più comune è l'espressione API che espone l'indirizzo IP del cliente può invece mostrare un indirizzo IP interno del proxy inverso.
+
+<Alert type="info">
+
+Durante la configurazione dell'impostazione `trust proxy`, è importante capire l'esatta configurazione del proxy inverso
+. Dal momento che questa impostazione sarà i valori di fiducia forniti nella richiesta, è importante che
+la combinazione dell'impostazione in Express corrisponda al funzionamento del proxy inverso.
+
+</Alert>
+
+L'impostazione dell'applicazione `trust proxy` può essere impostata su uno dei valori elencati nella seguente tabella.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Se `true`, l'indirizzo IP del cliente è inteso come la voce più sinistra nell'intestazione `X-Forwarded-For`.
+
+Se `false`, l'app è intesa come rivolta direttamente al client e l'indirizzo IP del cliente è derivato da `req.socket.remoteAddress`. Questa è l'impostazione predefinita.
+
+<Alert type="avviso">
+Quando si imposta a `true`, è importante assicurarsi che l'ultimo proxy inverso attendibile stia rimuovendo/sovrascrivendo tutte le seguenti intestazioni HTTP: `X-Forwarded-For`, `X-Forwarded-Host`, e `X-Forwarded-Proto`, altrimenti potrebbe essere possibile per il cliente fornire qualsiasi valore.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>indirizzi IP</td>
+<td markdown="1">
+Un indirizzo IP, una sottorete, o un array di indirizzi IP e sottoreti a cui fidarsi come proxy inverso. Il seguente elenco mostra i nomi pre-configurati delle sottorete
+
+- loopback - `127.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+È possibile impostare gli indirizzi IP in uno dei seguenti modi:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+Se specificato, gli indirizzi IP o le sottoreti sono esclusi dal processo di determinazione dell'indirizzo, e l'indirizzo IP non attendibile più vicino al server dell'applicazione è determinato come indirizzo IP del client. Questo funziona controllando se `req.socket.remoteAddress` è attendibile. In tal caso, ogni indirizzo in `X-Forwarded-For` viene controllato da destra a sinistra fino al primo indirizzo non fidato.
+
+</td>
+    </tr>
+    <tr>
+      <td>Numero</td>
+<td markdown="1">
+Usa l'indirizzo che è al massimo `n` numero di luppolo lontano dall'applicazione Express. `req.socket.remoteAddress` è il primo hop, e il resto sono cercati nell'intestazione `X-Forwarded-For` da destra a sinistra. Un valore di `0` significa che il primo indirizzo non attendibile sarebbe `req.socket.remoteAddress`, cioè non c'è un proxy inverso.
+
+<Alert type="avviso">
+Quando si utilizza questa impostazione, è importante assicurarsi che non ci siano multipli, percorsi diversi per l'applicazione Express in modo che il client possa essere inferiore al numero configurato di luppolo di distanza, altrimenti potrebbe essere possibile per il cliente fornire qualsiasi valore.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      Funzione <td />
+<td markdown="1">
+Implementazione fiducia personalizzata.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' <unk> <unk> ip === '123.123.123. 23')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Abilitare il `trust proxy` avrà il seguente impatto:
+
+<ul>
+  <li markdown="1">
+    Il valore di [req.hostname](/en/api#req.hostname) è derivato dal valore impostato
+    nell'intestazione `X-Forwarded-Host`, che può essere impostato dal cliente o dal proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` può essere impostato dal proxy inverso per dire all'app se si tratta di `↓ `
+    o `http` o anche di un nome non valido. Questo valore è riflesso da
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    I valori [req.ip](/en/api#req.ip) e [req.ips](/en/api#req.ips) sono popolati in base
+    all'indirizzo del socket e all'intestazione `X-Forwarded-For`, a partire dal primo indirizzo non
+    fidato.
+  </li>
+</ul>
+
+L'impostazione `trust proxy` è implementata usando il pacchetto [proxy-addr](https://www.npmjs.com/package/proxy-addr). Per ulteriori informazioni, consultare la documentazione.
diff --git a/src/content/docs/it/4x/guide/debugging.mdx b/src/content/docs/it/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..592e46618a
--- /dev/null
+++ b/src/content/docs/it/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debug Express
+description: Scopri come abilitare e utilizzare i log di debug nelle applicazioni Express.js impostando la variabile di ambiente DEBUG per la risoluzione dei problemi migliorata.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Per vedere tutti i log interni utilizzati in Express, imposta la variabile d'ambiente `DEBUG` su
+`express:*` quando lancia la tua app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Su Windows, utilizzare il comando corrispondente.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+L'esecuzione di questo comando nell'app predefinita generata dal [express generator](/en/starter/generator) stampa il seguente output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Quando viene fatta una richiesta all'applicazione, vedrete i registri specificati nel codice Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Per vedere i log solo dall'implementazione del router, imposta il valore di `DEBUG` su `express:router`. Allo stesso modo, per vedere i log solo dall'implementazione dell'applicazione, imposta il valore di `DEBUG` su `express:application`, e così via.
+
+## Applicazioni generate da `express`
+
+Un'applicazione generata dal comando `express` utilizza il modulo `debug` e il suo namespace di debug è indirizzato al nome dell'applicazione.
+
+Ad esempio, se hai generato l'app con `$ express sample-app`, puoi abilitare le istruzioni di debug con il seguente comando:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+È possibile specificare più di uno spazio dei nomi di debug assegnando una lista di nomi separati da virgole:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Opzioni avanzate
+
+Quando si esegue attraverso Node.js, è possibile impostare alcune variabili di ambiente che cambieranno il comportamento della registrazione di debug:
+
+| Nome                | Scopo                                                   |
+| ------------------- | ------------------------------------------------------- |
+| `DEBUG`             | Abilita/disabilita spazi di debug specifici.            |
+| `DEBUG_COLORS`      | Indica se usare o meno i colori nell'output di debug.   |
+| `DEBUG_DEPTH`       | Profondità dell'ispezione dell'oggetto.                 |
+| `DEBUG_FD`          | Descrittore file su cui scrivere l'output di debug.     |
+| `DEBUG_SHOW_HIDDEN` | Mostra le proprietà nascoste sugli oggetti ispezionati. |
+
+<Alert type="info">
+
+Le variabili di ambiente che iniziano con `DEBUG_` finiscono per essere convertite in un oggetto Opzioni
+che viene utilizzato con i formatori `%o`/`%O`. Vedere la documentazione Node.js per
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) per l'elenco completo
+.
+
+</Alert>
diff --git a/src/content/docs/it/4x/guide/error-handling.mdx b/src/content/docs/it/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..3378bd2b75
--- /dev/null
+++ b/src/content/docs/it/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Gestione Degli Errori
+description: Capire come Express.js gestisce gli errori nel codice sincrono e asincrono e imparare ad implementare middleware gestione degli errori personalizzati per le vostre applicazioni.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ si riferisce a come Express cattura ed elabora gli errori
+che si verificano in modo sincrono e asincrono. Express viene fornito con un gestore di errore
+predefinito quindi non è necessario scrivere il proprio per iniziare.
+
+## Errori Di Cattura
+
+È importante garantire che Express colmi tutti gli errori che si verificano mentre
+gestisce le rotte e middleware.
+
+Gli errori che si verificano nel codice sincrono all'interno dei gestori del percorso e del middleware
+non richiedono lavoro aggiuntivo. Se il codice sincrono lancia un errore, allora Express catturerà
+ed elaborerà esso. Per esempio:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express lo catturerà da solo.
+});
+```
+
+Per gli errori restituiti da funzioni asincrone invocate dai gestori degli itinerari
+e middleware, devi passarli alla funzione `next()`, dove Express sarà
+catturarli ed elaborarli. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Passa gli errori a Express.
+    } else {
+      res.end(dati);
+    }
+  });
+});
+```
+
+A partire da Express 5, i gestori del percorso e il middleware che restituiscono una Promise
+chiameranno automaticamente `next(value)` quando rifiutano o generano un errore.
+Per esempio:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Se `getUserById` genera un errore o rifiuta, `next` verrà chiamato con
+l'errore generato o il valore rifiutato. Se non viene fornito alcun valore rifiutato, `next`
+verrà chiamato con un oggetto di errore predefinito fornito dal router Express.
+
+Se passi qualcosa alla funzione `next()` (tranne la stringa `'route'`),
+Express considera la richiesta corrente come un errore e salterà qualsiasi
+rimanenti funzioni di routing e middleware senza errori.
+
+Se il callback in una sequenza non fornisce dati, solo errori, è possibile semplificare
+questo codice come segue:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Nell'esempio precedente, `next` è fornito come callback per `fs.writeFile`,
+che viene chiamato con o senza errori. Se non c'è errore, viene eseguito il secondo gestore
+, altrimenti Express cattura ed elabora l'errore.
+
+È necessario catturare gli errori che si verificano in codice asincrono invocato dai router o
+middleware e passarli a Express per l'elaborazione. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+L'esempio precedente utilizza un blocco `try...catch` per catturare errori nel codice asincrono
+e passarli a Express. Se il blocco `prova...catch`
+fosse omesso, Express non coglierebbe l'errore dal momento che non fa parte del codice di gestione
+sincrono.
+
+Usa le promesse per evitare l'overhead del blocco `prova...catch` o quando usi le funzioni
+che restituiscono le promesse. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Gli errori saranno passati a Express.
+});
+```
+
+Dal momento che le promesse catturano automaticamente entrambi gli errori sincroni e le promesse rifiutate,
+puoi semplicemente fornire `next` come il gestore finale di cattura e Express catturerà errori,
+perché al gestore della cattura viene dato l'errore come primo argomento.
+
+Si potrebbe anche utilizzare una catena di gestori per fare affidamento su errore sincrono
+catching, riducendo il codice asincrono a qualcosa di banale. Per esempio:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.ata = dati;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+L'esempio precedente ha un paio di istruzioni banali dalla chiamata `readFile`
+. Se `readFile` causa un errore, allora passa l'errore a Express, altrimenti
+torna rapidamente al mondo della gestione sincrona degli errori nel prossimo gestore
+nella catena. Poi, l'esempio di cui sopra cerca di elaborare i dati. Se questo fallisce, il gestore di errori sincroni
+lo catturerà. Se avessi fatto questa elaborazione all'interno di
+il callback `readFile`, l'applicazione potrebbe uscire e i gestori dell'errore Express
+non sarebbero stati eseguiti.
+
+Qualunque metodo si utilizzi, se si desidera che i gestori di errori Express siano chiamati dentro e l'applicazione
+per sopravvivere, è necessario assicurarsi che Express riceva l'errore.
+
+## Il gestore degli errori predefinito
+
+Express è dotato di un gestore di errori integrato che si occupa di eventuali errori che potrebbero essere riscontrati nell'app. Questa funzione middleware di gestione degli errori predefinita viene aggiunta alla fine dello stack della funzione middleware.
+
+Se passi un errore a `next()` e non lo gestisci in un gestore di errore
+personalizzato, sarà gestito dal gestore di errori integrato; l'errore sarà
+scritto al client con la traccia dello stack. La traccia dello stack non è inclusa
+nell'ambiente di produzione.
+
+<Alert type="info">
+
+Imposta la variabile d'ambiente `NODE_ENV` su `production`, per eseguire l'applicazione in modalità di produzione.
+
+</Alert>
+
+Quando viene scritto un errore, alla risposta
+vengono aggiunte le seguenti informazioni:
+
+- Il `res.statusCode` è impostato da `err.status` (o `err.statusCode`). Se
+  questo valore è al di fuori dell'intervallo 4xx o 5xx, sarà impostato a 500.
+- Il `res.statusMessage` è impostato in base al codice di stato.
+- Il corpo sarà l'HTML del messaggio del codice di stato quando in ambiente di produzione
+  , altrimenti sarà `err.stack`.
+- Qualsiasi intestazione specificata in un oggetto `err.headers`.
+
+Se chiami `next()` con un errore dopo aver iniziato a scrivere la risposta
+(ad esempio, se riscontri un errore durante lo streaming della risposta
+al client), il gestore di errore predefinito Express chiude la connessione
+e non riesce la richiesta.
+
+Quindi, quando si aggiunge un gestore di errori personalizzato, è necessario delegare a
+il gestore di errori Express predefinito, quando le intestazioni
+sono già state inviate al client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Nota che il gestore di errori predefinito può essere attivato se chiami `next()` con un errore
+nel tuo codice più di una volta, anche se la gestione degli errori personalizzati è in funzione.
+
+Altri errori di gestione middleware possono essere trovati su [Express middleware](/en/resources/middleware).
+
+## Gestione errori di scrittura
+
+Definire le funzioni middleware per la gestione degli errori allo stesso modo di altre funzioni middleware,
+eccetto le funzioni di gestione degli errori hanno quattro argomenti invece di tre:
+`(err, req, res, next)`. Per esempio:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Definisci l'ultima gestione degli errori del middleware, dopo altre chiamate `app.use()` e percorsi; per esempio:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Le risposte da all'interno di una funzione middleware possono essere in qualsiasi formato, come una pagina di errore HTML, un semplice messaggio, o una stringa JSON.
+
+Per scopi organizzativi (e di framework di livello superiore) è possibile definire diverse funzioni middleware di gestione degli errori
+come si farebbe con funzioni di middleware regolari
+. Ad esempio, per definire un gestore di errori
+per le richieste fatte utilizzando `XHR` e quelle senza:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app. se(
+  bodyParser.urlencoded({
+    extended true,
+  })
+);
+app. se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In questo esempio, i `logErrors` generici potrebbero scrivere la richiesta e le informazioni di errore
+in `stderr`, per esempio:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Anche in questo esempio, `clientErrorHandler` è definito come segue; in questo caso, l'errore viene esplicitamente passato a quello successivo.
+
+Nota che quando _non_ chiama "next" in una funzione di gestione degli errori, sei responsabile della scrittura (e della fine) della risposta. In caso contrario, tali richieste saranno "appese" e non saranno ammissibili per la raccolta rifiuti.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementa la funzione `errorHandler` "catch-all" come segue (per esempio):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Se si dispone di un gestore del percorso con molteplici funzioni di callback, è possibile utilizzare il parametro `route` per passare al prossimo gestore del percorso. Per esempio:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+In questo esempio, il gestore `getPaidContent` sarà saltato, ma qualsiasi gestore rimanente in `app` per `/a_route_behind_paywall` continuerà ad essere eseguito.
+
+<Alert type="info">
+
+Le chiamate a `next()` e `next(err)` indicano che il gestore corrente è completo e in quale stato.
+`next(err)` salterà tutti i gestori rimanenti nella catena ad eccezione di quelli che sono impostati su
+gestire gli errori come descritto sopra.
+
+</Alert>
diff --git a/src/content/docs/it/4x/guide/overriding-express-api.md b/src/content/docs/it/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..86696c08e0
--- /dev/null
+++ b/src/content/docs/it/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Sovrascrivendo l'API Express
+description: Scopri come personalizzare ed estendere l'API di Express.js sovrascrivendo i metodi e le proprietà su richiesta e gli oggetti di risposta utilizzando prototipi.
+---
+
+L'API Express è composta da vari metodi e proprietà su richiesta e oggetti di risposta. Questi sono ereditati dal prototipo. Ci sono due punti di estensione per l'API Express:
+
+1. I prototipi globali in `express.request` e `express.response`.
+2. prototipi specifici per app su `app.request` e `app.response`.
+
+La modifica dei prototipi globali influenzerà tutte le applicazioni Express caricate nello stesso processo. Se lo si desidera, le modifiche possono essere rese specifiche alle app modificando solo i prototipi specifici delle app dopo aver creato una nuova app.
+
+## Metodi
+
+È possibile sovrascrivere la firma e il comportamento dei metodi esistenti con il proprio, assegnando una funzione personalizzata.
+
+Di seguito è riportato un esempio di sovrascrittura del comportamento di [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+L'implementazione di cui sopra cambia completamente la firma originale di `res.sendStatus`. Ora accetta un codice di stato, il tipo di codifica e il messaggio da inviare al client.
+
+Il metodo overridden può ora essere utilizzato in questo modo:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Proprietà
+
+Le proprietà nell'API Express sono:
+
+1. Proprietà assegnate (es: `req.baseUrl`, `req.originalUrl`)
+2. Definito come getters (es: `req.secure`, `req.ip`)
+
+Poiché le proprietà sotto la categoria 1 sono assegnate dinamicamente sugli oggetti `request` e `response` nel contesto dell'attuale ciclo di richiesta-risposta, il loro comportamento non può essere superato.
+
+Le proprietà sotto la categoria 2 possono essere sovrascritte utilizzando le API di estensione Express.
+
+Il seguente codice riscrive come deve essere derivato il valore di `req.ip`. Ora restituisce semplicemente il valore dell'intestazione della richiesta `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Protototipo
+
+Al fine di fornire l'API Express, gli oggetti richiesta/risposta passati a Express (tramite `app(req, res)`, per esempio) bisogno di ereditare dalla stessa catena prototipo. Per impostazione predefinita, questo è `http.IncomingRequest.prototype` per la richiesta e `http.ServerResponse.prototype` per la risposta.
+
+Se non necessario, si raccomanda che ciò avvenga solo a livello di applicazione e non a livello globale. Inoltre, fare in modo che il prototipo che viene utilizzato corrisponda la funzionalità il più vicino possibile ai prototipi predefiniti.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/it/4x/guide/routing.mdx b/src/content/docs/it/4x/guide/routing.mdx
new file mode 100644
index 0000000000..19873bbdf3
--- /dev/null
+++ b/src/content/docs/it/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Scopri come definire e utilizzare i percorsi nelle applicazioni Express.js, inclusi i metodi di percorso, i percorsi e i parametri e utilizzando Router per il routing modulare.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ si riferisce a come gli endpoint di un'applicazione (URI) rispondono alle richieste del client.
+Per un'introduzione al routing, vedere [Instradamento di base](/en/starter/basic-routing).
+
+Definisci il routing usando metodi dell'oggetto `app` Express che corrispondono ai metodi HTTP;
+per esempio, `app. et()` per gestire le richieste GET e `app.post` per gestire le richieste POST. Per una lista completa,
+vedi [app.METHOD](/en/5x/api#app.METHOD). Puoi anche usare [app.all()](/en/5x/api#app.all) per gestire tutti i metodi HTTP e [app. se()](/en/5x/api#app.use) to
+specify middleware as the callback function (Vedi [Using middleware](/en/guide/using-middleware) for details).
+
+Questi metodi di routing specificano una funzione di callback (a volte chiamata "funzioni di handler") chiamata quando l'applicazione riceve una richiesta al percorso specificato (endpoint) e il metodo HTTP. In altre parole, l'applicazione "ascolta" per le richieste che corrispondono ai percorsi e ai metodi specificati, e quando rileva una corrispondenza, chiama la funzione di callback specificata.
+
+Infatti, i metodi di routing possono avere più di una funzione di callback come argomenti.
+Con funzioni di callback multiple, è importante fornire `next` come argomento alla funzione di callback e poi chiamare `next()` all'interno del corpo della funzione per consegnare il controllo
+al prossimo callback.
+
+Il seguente codice è un esempio di un percorso molto basilare.
+
+```js
+const express = require('express');
+const app = express();
+
+// rispondi con "ciao mondo" quando una richiesta GET viene fatta all'app homepage
+. et('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Metodi percorso
+
+Un metodo di percorso è derivato da uno dei metodi HTTP ed è collegato ad un'istanza della classe `express`.
+
+Il seguente codice è un esempio di percorsi definiti per il `GET` e i metodi `POST` nella root dell'app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.end('Richiesta GET alla homepage');
+});
+
+// POST metodo percorso
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supporta metodi che corrispondono a tutti i metodi di richiesta HTTP: `get`, `post`, e così via.
+Per un elenco completo, vedere [app.METHOD](/en/5x/api#app.METHOD).
+
+C'è un metodo di routing speciale, `app.all()`, utilizzato per caricare le funzioni middleware in un percorso per _tutti_ i metodi di richiesta HTTP. Ad esempio, il seguente gestore viene eseguito per le richieste al percorso `"/secret"` se si utilizza `GET`, `POST`, `PUT`, `DELETE`, o qualsiasi altro metodo di richiesta HTTP supportato nel [modulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accedere alla sezione segreta ...');
+  next(); // passare il controllo al prossimo gestore
+});
+```
+
+## Percorsi di rotta
+
+Percorsi di percorso, in combinazione con un metodo di richiesta, definire gli endpoint in cui le richieste possono essere fatte. I tracciati del percorso possono essere stringhe, motivi di stringa o espressioni regolari.
+
+<Alert type="allerta">
+
+In express 5, i personaggi `? , `+`, `\*`, `[]`, e `()\` sono gestiti in modo diverso rispetto alla versione
+4, si prega di rivedere la [guida alla migrazione](/en/guide/migrating-5#path-syntax) per maggiori informazioni.
+
+</Alert>
+
+<Alert type="allerta">
+
+Nell'espressione 4, i caratteri di espressione regolare come `$` devono essere fuggiti con un `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express utilizza [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) per abbinare i percorsi del percorso
+; vedere la documentazione path-to-regexp per tutte le possibilità di definire i percorsi del percorso.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) è uno strumento utile per
+testare i percorsi Express di base, anche se non supporta la corrispondenza dei modelli.
+
+</Alert>
+
+<Alert type="warning">Le stringhe di query non fanno parte del percorso percorso.</Alert>
+
+### Percorsi di percorso basati su stringhe
+
+Questo percorso corrisponderà alle richieste del percorso root, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Questo percorso corrisponderà alle richieste di `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Questo percorso corrisponderà alle richieste a `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Percorsi del percorso in base ai motivi delle stringhe
+
+<Alert type="allerta">
+
+I modelli di stringhe in Express 5 non funzionano più. Si prega di fare riferimento alla [guida di migrazione
+(/en/guide/migrating-5#path-syntax) per ulteriori informazioni.
+
+</Alert>
+
+Questo percorso corrisponde a `acd` e `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Questo percorso corrisponderà a `abcd`, `abbcd`, `abbbcd`, e così via.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Questo percorso corrisponde a `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, e così via.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Questo percorso corrisponde a `/abe` e `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Percorsi di percorso basati su espressioni regolari
+
+Questo percorso corrisponderà a qualsiasi cosa con una "a" in esso.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Questo percorso corrisponde a `butterfly` e `dragonfly`, ma non a `butterflyman`, `dragonflyman`, e così via.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parametri percorso
+
+I parametri del percorso sono denominati segmenti di URL che vengono utilizzati per catturare i valori specificati nella loro posizione nell'URL. I valori catturati sono popolati nell'oggetto `req.params`, con il nome del parametro route specificato nel percorso come loro rispettive chiavi.
+
+```
+Percorso del percorso: /users/:userId/books/:bookId
+Richiedi URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Per definire i percorsi con i parametri del percorso, è sufficiente specificare i parametri del percorso nel percorso come mostrato di seguito.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="allerta">
+
+Il nome dei parametri del percorso deve essere composto da "caratteri di parola" ([A-Za-z0-9_]).
+
+</Alert>
+
+Poiché il trattino (`-`) e il punto (`.`) sono interpretati letteralmente, possono essere utilizzati insieme ai parametri del percorso per scopi utili.
+
+```
+Percorso del percorso: /flights/:from-:to
+Richiedi URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Percorso percorso: /plantae/:genus.:species
+Richiedi URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="allerta">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Per avere più controllo sulla stringa esatta che può essere abbinata a un parametro del percorso, puoi aggiungere un'espressione regolare tra parentesi (`()`):
+
+```
+Percorso del percorso: /user/:userId(\d+)
+Richiedi URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="avviso">
+
+Perché l'espressione regolare è di solito parte di una stringa letterale, assicurati di sfuggire a qualsiasi carattere `\`
+con un backslash aggiuntivo, ad esempio `\d+`.
+
+</Alert>
+
+<Alert type="avviso">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">il carattere `*` nelle espressioni regolari non viene interpretato nel modo usuale</a>. Come soluzione puoi usare `{0,}` invece di `*`. Questo sarà probabilmente fissato in Express 5.
+</Alert>
+
+## Gestori del percorso
+
+È possibile fornire più funzioni di callback che si comportano come [middleware](/en/guide/using-middleware) per gestire una richiesta. L'unica eccezione è che questi callback potrebbero invocare `next('route')` per bypassare i rimanenti callback del percorso. È possibile utilizzare questo meccanismo per imporre condizioni preliminari su un percorso, poi passare il controllo ai percorsi successivi se non c'è motivo di procedere con il percorso corrente.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In questo esempio:
+
+- `GET /user/5` → gestito dal primo percorso → invia "User 5"
+- `GET /user/0` → prima rotta chiama `next('route')`, saltando al prossimo percorso corrispondente `/user/:id`
+
+I gestori del percorso possono essere nella forma di una funzione, una serie di funzioni, o combinazioni di entrambi, come mostrato negli esempi seguenti.
+
+Una singola funzione di callback può gestire un percorso. Per esempio:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+Più di una funzione di callback può gestire un percorso (assicurati di specificare l'oggetto `next`). Per esempio:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('la risposta verrà inviata dalla funzione successiva . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Ciao da B!');
+  }
+);
+```
+
+Un array di funzioni di callback può gestire un percorso. Per esempio:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Ciao da C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Una combinazione di funzioni indipendenti e matrici di funzioni può gestire un percorso. Per esempio:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('la risposta verrà inviata dalla funzione successiva . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Ciao da D!');
+  }
+);
+```
+
+## Metodi di risposta
+
+I metodi sull'oggetto di risposta (`res`) nella tabella seguente possono inviare una risposta al client e terminare il ciclo di richiesta-risposta. Se nessuno di questi metodi è chiamato da un gestore del percorso, la richiesta del cliente sarà sospesa.
+
+| Metodo                                        | Descrizione                                                                                                        |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [res.download()](/en/5x/api#res.download)     | Avverte un file da scaricare.                                                                                      |
+| [res.end()](/en/5x/api#res.end)               | Termina il processo di risposta.                                                                                   |
+| [res.json()](/en/5x/api#res.json)             | Invia una risposta JSON.                                                                                           |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Invia una risposta JSON con il supporto JSONP.                                                                     |
+| [res.redirect()](/en/5x/api#res.redirect)     | Reindirizza una richiesta.                                                                                         |
+| [res.render()](/en/5x/api#res.render)         | Render un modello di visualizzazione.                                                                              |
+| [res.send()](/en/5x/api#res.send)             | Invia una risposta di vari tipi.                                                                                   |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Invia un file come un flusso di otte.                                                                              |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Imposta il codice di stato della risposta e invia la sua rappresentazione della stringa come corpo della risposta. |
+
+## app.route()
+
+È possibile creare i gestori di rotte per un percorso utilizzando `app.route()`.
+Poiché il percorso è specificato in una singola posizione, è utile creare percorsi modulari, così come ridurre la ridondanza e pneumatici. Per ulteriori informazioni sulle rotte, si veda: [Router() documentation](/en/5x/api#router).
+
+Ecco un esempio di router incatenati che sono definiti utilizzando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Ottieni un libro casuale');
+  })
+  .ost((req, res) => {
+    res.send('Add a book');
+  })
+  .ut((req, res) => {
+    res.send('Aggiorna il libro');
+  });
+```
+
+## express.Router
+
+Usa la classe `express.Router` per creare i gestori modulari e montabili. Un'istanza `Router` è un sistema di routing e middleware completo; per questo motivo è spesso chiamata "mini-app".
+
+L'esempio seguente crea un router come modulo, carica una funzione middleware in esso, definisce alcuni percorsi e monta il modulo del router su un percorso nell'app principale.
+
+Crea un file router chiamato `birds.js` nella directory delle app, con il seguente contenuto:
+
+```js
+const express = require('express');
+const router = express. outer();
+
+// middleware che è specifico per questo router
+const timeLog = (req, res, next) => {
+  console. og('Orario: ', Date.now());
+  next();
+};
+router. se(timeLog);
+
+// definisci il percorso della home page
+router.get('/', (req, res) => {
+  res. end('Birds home page');
+});
+// definire il router sulla rotta
+. et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Quindi, caricare il modulo router nell'app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+L'app sarà ora in grado di gestire le richieste di `/birds` e `/birds/about`, oltre a chiamare la funzione middleware `timeLog` che è specifica per il percorso.
+
+Ma se il percorso principale `/birds` ha parametri di percorso, non sarà accessibile per impostazione predefinita dai sotto-percorsi. Per renderlo accessibile, dovrai passare l'opzione `mergeParams` al costruttore Router [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/it/4x/guide/using-middleware.mdx b/src/content/docs/it/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..25d334aeb0
--- /dev/null
+++ b/src/content/docs/it/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usare middleware
+description: Scopri come utilizzare middleware nelle applicazioni Express.js, tra cui middleware a livello di applicazione e router, gestione degli errori e integrazione di middleware di terze parti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express è un framework web routing e middleware che ha funzionalità minime proprie: Un'applicazione Express è essenzialmente una serie di chiamate di funzioni middleware.
+
+Le funzioni _Middleware_ sono funzioni che hanno accesso al [request object](/en/5x/api#req) (`req`), il [response object](/en/5x/api#res) (`res`), e la successiva funzione middleware nel ciclo request-response dell'applicazione. La funzione middleware successiva è comunemente indicata da una variabile chiamata `next`.
+
+Le funzioni Middleware possono eseguire le seguenti attività:
+
+- Esegue qualsiasi codice.
+- Effettuare modifiche alla richiesta e agli oggetti di risposta.
+- Terminare il ciclo richiesta-risposta.
+- Chiama la funzione middleware successiva nello stack.
+
+Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve chiamare `next()` per passare il controllo alla successiva funzione middleware. In caso contrario, la richiesta sarà sospesa.
+
+Un'applicazione Express può utilizzare i seguenti tipi di middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Gestione errori middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [middleware di terze parti](#middleware.third-party)
+
+È possibile caricare il middleware a livello di applicazione e router con un percorso di montaggio opzionale.
+È inoltre possibile caricare una serie di funzioni middleware insieme, che crea una sottopila del sistema middleware in un punto di montaggio.
+
+## Middleware a livello di applicazione
+
+Associa il middleware di livello applicativo ad un'istanza del [app object](/en/5x/api#app) usando `app.use()` e `app. ETHOD()` funzioni, dove `METHOD` è il metodo HTTP della richiesta che la funzione middleware gestisca (come GET, PUT, o POST) in minuscolo.
+
+Questo esempio mostra una funzione middleware senza percorso di montaggio. La funzione viene eseguita ogni volta che l'app riceve una richiesta.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Questo esempio mostra una funzione middleware montata sul percorso `/user/:id`. La funzione viene eseguita per qualsiasi tipo di richiesta HTTP
+sul percorso `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Questo esempio mostra un percorso e la sua funzione di gestore (sistema middleware). La funzione gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Ecco un esempio di caricamento di una serie di funzioni middleware in un punto di montaggio, con un percorso di montaggio.
+Illustra un sub-stack middleware che stampa la richiesta di informazioni per qualsiasi tipo di richiesta HTTP al percorso `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.og('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+I gestori del percorso consentono di definire percorsi multipli per un percorso. L'esempio sottostante definisce due percorsi per le richieste GET al percorso `/user/:id`. Il secondo percorso non causerà alcun problema, ma non verrà mai chiamato perché il primo percorso termina il ciclo richiesta-risposta.
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('Info utente');
+  }
+);
+
+// handler per il percorso /user/:id, che stampa l'app ID utente
+. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Per saltare il resto delle funzioni middleware da uno stack middleware router, chiama `next('route')` per passare il controllo al percorso successivo.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // se l'ID utente è 0, salta al prossimo percorso
+    se (req. arams. d === '0') next('route');
+    // altrimenti passa il controllo alla funzione middleware successiva in questo stack
+    altrimenti successivo();
+  },
+  (req, res, next) => {
+    // invia una risposta regolare
+    res. end('regular');
+  }
+);
+
+// handler per il percorso /user/:id, che invia una risposta speciale
+app. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware può anche essere dichiarato in un array per la riutilizzabilità.
+
+Questo esempio mostra un array con un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware funziona allo stesso modo di application-level middleware, tranne che è legato ad un'istanza di `express.Router()`.
+
+```js
+router const = express.Router();
+```
+
+Carica il middleware a livello router usando le funzioni `router.use()` e `router.METHOD()`.
+
+Il seguente esempio di codice replica il sistema middleware che viene mostrato sopra per il middleware a livello di applicazione, utilizzando il middleware a livello di router:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// una funzione middleware senza percorso di montaggio. Questo codice viene eseguito per ogni richiesta al router
+. se((req, res, next) => {
+  console.log('Time:', Date. ow());
+  next();
+});
+
+// un sub-stack middleware mostra le informazioni di richiesta per qualsiasi tipo di richiesta HTTP al router /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console. og('Request Type:', req. ethod);
+    next();
+  }
+);
+
+// un sub-stack middleware che gestisce le richieste GET al router /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // se l'ID utente è 0, salta al router successivo
+    se (req. arams. d === '0') next('route');
+    // altrimenti passa il controllo alla successiva funzione middleware in questo stack
+    altrimenti successivo();
+  },
+  (req, successivo) => {
+    // renderizza una pagina normale
+    res. ender('regular');
+  }
+);
+
+// handler per il percorso /user/:id, che rende una pagina speciale
+router. et('/user/:id', (req, res, next) => {
+  console. og(req.params.id);
+  res.render('special');
+});
+
+// monta il router sull'app
+app.use('/', router);
+```
+
+Per saltare il resto delle funzioni middleware del router, chiama `next('router')`
+per passare il controllo indietro dall'istanza del router.
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// predicare il router con un controllo e salvataggio quando necessario router
+. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa il router e 401 qualsiasi cosa che cade attraverso l'app
+. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## middleware gestione errori
+
+<Alert type="allerta">
+
+La gestione degli errori del middleware richiede sempre _four_ argomenti. È necessario fornire quattro argomenti per
+identificarlo come una funzione middleware di gestione degli errori. Anche se non è necessario utilizzare l'oggetto `next`
+, è necessario specificarlo per mantenere la firma. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Definire le funzioni middleware per la gestione degli errori allo stesso modo di altre funzioni middleware, tranne con quattro argomenti invece di tre, specificatamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Per maggiori dettagli sulla gestione degli errori middleware, vedere [Gestione degli errori](/en/guide/error-handling).
+
+## Middleware incorporato
+
+A partire dalla versione 4.x, Express non dipende più da [Connect](https://github.com/senchalabs/connect). Le funzioni middleware
+che erano state precedentemente incluse con Express sono ora in moduli separati; vedi [la lista delle funzioni middleware](https://github.com/senchalabs/connect#middleware).
+
+Express ha le seguenti funzioni middleware integrate:
+
+- [express.static](/en/5x/api#express.static) serve risorse statiche come file HTML, immagini e così via.
+- [express.json](/en/5x/api#express.json) analizza le richieste in arrivo con i payload JSON. **NOTA: Disponibile con Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analizza le richieste in arrivo con payload codificati con URL. **NOTA: Disponibile con Express 4.16.0+**
+
+## middleware di terze parti
+
+Usa middleware di terze parti per aggiungere funzionalità alle app Express.
+
+Installare il modulo Node.js per le funzionalità richieste, quindi caricarlo nell'app a livello di applicazione o a livello di router.
+
+L'esempio seguente illustra l'installazione e il caricamento della funzione middleware di analisi dei cookie `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Per una lista parziale delle funzioni middleware di terze parti che sono comunemente usate con Express, vedere [middleware di terze parti](../resources/middleware).
diff --git a/src/content/docs/it/4x/guide/using-template-engines.mdx b/src/content/docs/it/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..3548142cd6
--- /dev/null
+++ b/src/content/docs/it/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utilizzo di modelli di motori con Express
+description: Scopri come integrare e utilizzare modelli di motori come Pug, Manubri ed EJS con Express.js per rendere le pagine HTML dinamiche in modo efficiente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un motore _modello_ ti permette di utilizzare file di template statici nella tua applicazione. Al runtime, il modello del motore sostituisce le variabili
+in un modello di file con valori reali, e trasforma il modello in un file HTML inviato al client.
+Questo approccio rende più facile progettare una pagina HTML.
+
+Il [generatore di applicazioni Express](/en/starter/generator) utilizza [Pug](https://pugjs.org/api/getting-started.html) come predefinito, ma supporta anche [Handlebars](https://www.npmjs.com/package/handlebars), e [EJS](https://www.npmjs.com/package/ejs), tra gli altri.
+
+Per rendere i file dei modelli, imposta le seguenti [proprietà delle impostazioni dell'applicazione](/en/4x/api#app.set), nel file `app.js` predefinito creato dal generatore:
+
+- `views`, la directory dove si trovano i file del modello. Eg: `app.set('views', './views')`.
+  Questo valore predefinito è la directory `views` nella directory radice dell'applicazione.
+- `view engine`, il modello motore da usare. Ad esempio, per usare il motore modello Pug: `app.set('view engine', 'pug')`.
+
+Quindi installare il corrispondente pacchetto npm del motore del modello; per esempio per installare Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="allerta">
+Motori di modelli conformi ad espresso, come Pug esportano una funzione chiamata `__express(filePath, options, callback)`,
+che `res.render()` chiama per rendere il codice del modello.
+
+Alcuni modelli di motori non seguono questa convenzione. La libreria [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+segue questa convenzione mappando tutti i popolari motori di template Node.js, e quindi funziona perfettamente all'interno di Express.
+
+</Alert>
+
+Dopo che il motore di visualizzazione è stato impostato, non è necessario specificare il motore o caricare il modulo del motore modello nella tua app;
+Express carica il modulo internamente, per esempio:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Quindi, crea un file modello Pug chiamato `index.pug` nella directory `views`, con il seguente contenuto:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Crea un percorso per rendere il file `index.pug`. Se la proprietà `view engine` non è impostata,
+è necessario specificare l'estensione del file `view`. Altrimenti, puoi ometterlo.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando effettui una richiesta alla home page, il file `index.pug` verrà renderizzato come HTML.
+
+La cache del motore di visualizzazione non memorizza in cache il contenuto dell'output del modello, solo il modello sottostante. La vista è ancora ri-renderizzata con ogni richiesta anche quando la cache è accesa.
diff --git a/src/content/docs/it/4x/guide/writing-middleware.mdx b/src/content/docs/it/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..91e7a122a9
--- /dev/null
+++ b/src/content/docs/it/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Scrittura middleware per l'utilizzo in applicazioni Express
+description: Scopri come scrivere funzioni middleware personalizzate per le applicazioni Express.js, inclusi esempi e migliori pratiche per migliorare la gestione delle richieste e delle risposte.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Le funzioni _Middleware_ sono funzioni che hanno accesso al [request object](/en/5x/api#req) (`req`), il [response object](/en/5x/api#res) (`res`), e la funzione `next` nel ciclo request-response dell'applicazione. La funzione `next` è una funzione nel router Express che, quando invocato, esegue il middleware con successo al middleware corrente.
+
+Le funzioni Middleware possono eseguire le seguenti attività:
+
+- Esegue qualsiasi codice.
+- Effettuare modifiche alla richiesta e agli oggetti di risposta.
+- Terminare il ciclo richiesta-risposta.
+- Chiama il prossimo middleware nello stack.
+
+Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve chiamare `next()` per passare il controllo alla successiva funzione middleware. In caso contrario, la richiesta sarà sospesa.
+
+La figura seguente mostra gli elementi di una chiamata di una funzione middleware:
+
+<div class="table-scroller">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elementi di una chiamata a funzione middleware" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+Metodo <div class="callout" id="callout1">HTTP per il quale si applica la funzione middleware.</div>
+
+<div class="callout" id="callout2">
+  Percorso (percorso) per il quale si applica la funzione middleware.
+</div>
+
+<div class="callout" id="callout3">
+  La funzione middleware.
+</div>
+
+<div class="callout" id="callout4">
+  Argomento di richiamo alla funzione middleware, chiamato "next" per convenzione.
+</div>
+
+<div class="callout" id="callout5">
+  Argomento HTTP <a href="/en/5x/api#res">risposta</a> alla funzione middleware, chiamato "res"
+  dalla convenzione .
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">richiede l'argomento</a> alla funzione middleware, chiamata "req" per convenzione.</div>
+</td>
+</tr>
+</table>
+</div>
+
+A partire da Express 5, le funzioni middleware che restituiscono una Promise chiameranno `next(value)` quando rifiutano o lanciano un errore. `next` verrà chiamato con il valore rifiutato o con l'errore lanciato.
+
+## Esempio
+
+Ecco un esempio di una semplice applicazione "Hello World" Express.
+Il resto di questo articolo definirà e aggiungerà tre funzioni middleware all'applicazione:
+uno chiamato `myLogger` che stampa un semplice messaggio di registro, uno chiamato `requestTime` che
+visualizza il timestamp della richiesta HTTP e uno chiamato `validateCookies` che convalida i cookie in entrata.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Funzione middleware myLogger
+
+Ecco un semplice esempio di una funzione middleware chiamata "myLogger". Questa funzione solo stampa
+"LOGGED" quando una richiesta all'app passa attraverso di essa. La funzione middleware è assegnata a una variabile
+chiamata `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="allerta">
+
+Notare la chiamata sopra a `next()`. Chiamando questa funzione invoca la prossima funzione middleware nell'app
+. La funzione `next()` non è una parte del Node. s o Express API, ma è il terzo argomento
+che viene passato alla funzione middleware. La funzione `next()` potrebbe essere chiamata qualsiasi cosa,
+ma per convenzione è sempre chiamata "next". Per evitare confusione, utilizzare sempre questa convenzione.
+
+</Alert>
+
+Per caricare la funzione middleware, chiama `app.use()`, specificando la funzione middleware.
+Ad esempio, il seguente codice carica la funzione middleware `myLogger` prima del percorso al percorso root (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Ciao World!');
+});
+
+app.listen(3000);
+```
+
+Ogni volta che l'app riceve una richiesta, stampa il messaggio "LOGGED" al terminale.
+
+L'ordine di caricamento del middleware è importante: le funzioni middleware che vengono caricate per primo vengono eseguite per prime.
+
+Se il file `myLogger` viene caricato dopo il percorso verso il percorso root, la richiesta non lo raggiunge mai e l'applicazione non stampa "LOGGED", perché il gestore del percorso del percorso radice termina il ciclo richiesta-risposta.
+
+La funzione middleware `myLogger` semplicemente stampa un messaggio, poi passa la richiesta alla funzione middleware successiva nello stack chiamando la funzione `next()`.
+
+### Richiesta funzione Middleware
+
+Successivamente, creeremo una funzione middleware chiamata "requestTime" e aggiungeremo una proprietà chiamata `requestTime`
+all'oggetto richiesta.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+L'app utilizza ora la funzione middleware `requestTime`. Inoltre, la funzione callback del percorso del percorso del percorso di root utilizza la proprietà che la funzione middleware aggiunge a `req` (il oggetto richiesta).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = 'Ciao Mondo!<br>';
+  responseText += `<small>Richiesto a: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Quando si effettua una richiesta alla root dell'app, l'app ora visualizza il timestamp della richiesta nel browser.
+
+### Middleware function validateCookies
+
+Infine, creeremo una funzione middleware che convalida i cookie in arrivo e invia una risposta 400 se i cookie non sono validi.
+
+Ecco una funzione di esempio che convalida i cookie con un servizio asincronico esterno.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Qui utilizziamo il middleware [`cookie-parser`](/en/resources/middleware/cookie-parser) per analizzare i cookie in arrivo fuori dall'oggetto `req` e passarli alla nostra funzione `cookieValidator`. Il middleware `validateCookies` restituisce una Promessa che al momento del rifiuto attiverà automaticamente il nostro gestore di errori.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="allerta">
+
+Nota come `next()` viene chiamato dopo `await cookieValidator(req.cookies)`. Questo assicura che se
+`cookieValidator` si risolve, il prossimo middleware nello stack verrà chiamato. Se passi qualcosa
+alla funzione `next()` (tranne la stringa `'route'` o `'router'`), Espresso considera l'attuale richiesta
+come un errore e salterà tutte le rimanenti funzioni di routing e middleware
+.
+
+</Alert>
+
+Poiché hai accesso all'oggetto richiesta, all'oggetto risposta, alla funzione middleware successiva nello stack, e all'intero Node. s API, le possibilità con funzioni middleware sono infinite.
+
+Per ulteriori informazioni su middleware Express, consultare: [Using Express middleware](/en/guide/using-middleware).
+
+## Middleware configurabile
+
+Se hai bisogno del tuo middleware per essere configurabile, esporta una funzione che accetta un oggetto di opzioni o altri parametri, che, poi, restituisce l'implementazione middleware in base ai parametri di input.
+
+File: `my-middleware.js`
+
+```js
+modulo.xports = function (options) {
+  return function (req, res, next) {
+    // Implementa la funzione middleware basata sulle opzioni object
+    next();
+  };
+};
+```
+
+Il middleware può ora essere utilizzato come mostrato di seguito.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Fare riferimento a [cookie-session](https://github.com/expressjs/cookie-session) e [compression](https://github.com/expressjs/compression) per esempi di middleware configurabile.
diff --git a/src/content/docs/it/4x/starter/basic-routing.mdx b/src/content/docs/it/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..f9777989fc
--- /dev/null
+++ b/src/content/docs/it/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Instradamento base
+description: Impara i fondamenti del routing nelle applicazioni Express.js, tra cui come definire i percorsi, gestire i metodi HTTP e creare gestori del percorso per il tuo server web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ si riferisce alla determinazione di come un'applicazione risponde a una richiesta di client a un determinato endpoint, che è un URI (o percorso) e un metodo di richiesta HTTP specifico (GET, POST, e così via).
+
+Ogni percorso può avere una o più funzioni di gestore, che vengono eseguite quando il percorso è abbinato.
+
+La definizione del percorso assume la seguente struttura:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Dove:
+
+- `app` è un'istanza di `express`.
+- `METHOD` è un [metodo di richiesta HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in minuscolo.
+- `PATH` è un percorso sul server.
+- `HANDLER` è la funzione eseguita quando il percorso è corrispondente.
+
+<Alert type="allerta">
+
+Questo tutorial presuppone che venga creata un'istanza di `express` chiamata `app` e che il server sia in esecuzione
+. Se non hai familiarità con la creazione di un'app e l'avvio, vedi l'esempio Ciao mondo
+.
+
+</Alert>
+
+Gli esempi che seguono illustrano la definizione di itinerari semplici.
+
+Rispondi con `Ciao Mondo!` nella homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Rispondi a una richiesta POST sul percorso radice (`/`), la home page dell'applicazione:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Rispondi a una richiesta PUT al percorso `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Rispondi a una richiesta DELETE al percorso `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+Per maggiori dettagli sul routing, consulta la [guida di routing](/en/guide/routing).
diff --git a/src/content/docs/it/4x/starter/examples.mdx b/src/content/docs/it/4x/starter/examples.mdx
new file mode 100644
index 0000000000..2165c04250
--- /dev/null
+++ b/src/content/docs/it/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Esempi espressi
+description: Esplora una raccolta di esempi di applicazioni Express.js che coprono vari casi di utilizzo, integrazioni e configurazioni avanzate per aiutarti a imparare e costruire i tuoi progetti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Autenticazione con login e password
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - Negoziazione di contenuti HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Lavorare con sessioni basate su cookie
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Lavorare con i cookie
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Trasferimento dei file al client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Lavorare con il template JavaScript incorporato (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Creazione pagine di errore
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Lavorare con middleware errore
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Gestore semplice della richiesta
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown come modello motore
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Lavorare con più router Express
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - controller in stile MVC
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Monitoraggio delle attività degli utenti online con pacchetti `online` e `redis`
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Lavorare con i parametri del percorso
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Operazioni HTTP multiple sulla stessa risorsa
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organizzare i percorsi utilizzando una mappa
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Lavorare con il middleware del percorso
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizzare percorsi per ogni risorsa
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Cerca API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - sessioni utente
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Servire file statici
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Lavorare con gli host virtuali
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Visualizzazione dinamica
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Salvataggio dei dati nell'oggetto richiesta tra le chiamate middleware
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Servizio API semplice
+
+## Esempi aggiuntivi
+
+Questi sono alcuni esempi aggiuntivi con integrazioni più estese.
+
+<Alert type="avviso">
+  Queste informazioni si riferiscono a siti, prodotti o moduli di terze parti che non sono mantenuti
+  dal team Expressjs. L'elenco qui non costituisce un'approvazione o una raccomandazione da parte
+  del team di progetto Expressjs.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app con Express e Next.js utilizzando [Prisma](https://www.npmjs.com/package/prisma) come ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/it/4x/starter/faq.md b/src/content/docs/it/4x/starter/faq.md
new file mode 100644
index 0000000000..6e30b48782
--- /dev/null
+++ b/src/content/docs/it/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Trova le risposte alle domande più frequenti su Express.js, inclusi argomenti sulla struttura delle applicazioni, modelli, autenticazione, modelli motori, gestione degli errori e altro ancora.
+---
+
+## Come dovrei strutturare la mia applicazione?
+
+Non esiste una risposta definitiva a questa domanda. La risposta dipende da
+sulla scala della tua applicazione e del team che è coinvolto. Per essere il più flessibile possibile
+, Express non fa ipotesi in termini di struttura.
+
+Le rotte e altre logiche specifiche per le applicazioni possono vivere in tutti i file
+che desideri, in qualsiasi struttura di directory che preferisci. Visualizza i seguenti esempi di ispirazione
+:
+
+- [Elenco delle rotte](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mappa del percorso](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Inoltre, ci sono estensioni di terze parti per Express, che semplificano alcuni di questi modelli:
+
+- [Instradamento delle risorse](https://github.com/expressjs/express-resource)
+
+## Come definisco i modelli?
+
+Express non ha alcuna nozione di banca dati. Questo concetto è
+lasciato fino a moduli Nodo di terze parti, consentendo di
+interfaccia con quasi tutti i database.
+
+Vedi [LoopBack](http://loopback.io) per un framework basato su Espresso che è centrato sui modelli.
+
+## Come posso autenticare gli utenti?
+
+L'autenticazione è un'altra area opinionata in cui Express non si avventura
+. È possibile utilizzare qualsiasi schema di autenticazione desiderato.
+Per un semplice schema username / password, vedere [questo esempio](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quali modelli di motori supporta Express?
+
+Express supporta qualsiasi modello di motore conforme alla firma `(percorso, locale, callback)`.
+Per normalizzare i modelli di interfacce motore e caching, vedere il progetto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+per il supporto. Motori modello non elencati potrebbero ancora supportare la firma Express.
+
+Per ulteriori informazioni, vedere [Utilizzo di modelli di motori con Express](/en/guide/using-template-engines).
+
+## Come posso gestire 404 risposte?
+
+In Express, 404 risposte non sono il risultato di un errore, quindi
+il middleware del gestore dell'errore non le catturerà. Questo comportamento è
+perché una risposta 404 indica semplicemente l'assenza di lavoro supplementare da fare;
+in altre parole, Express ha eseguito tutte le funzioni e i percorsi del middleware,
+e ha trovato che nessuno di loro ha risposto. Tutto quello che devi fare
+è aggiungere una funzione middleware nella parte inferiore dello stack (sotto tutte le altre funzioni)
+per gestire una risposta 404:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Aggiungi percorsi dinamicamente al runtime su un'istanza di `express.Router()`
+in modo che i percorsi non siano sostituiti da una funzione middleware.
+
+## Come faccio a configurare un gestore di errori?
+
+Definisci middleware per la gestione degli errori allo stesso modo di altri middleware,
+tranne con quattro argomenti invece di tre; specificatamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Per ulteriori informazioni, vedere [Gestione degli errori](/en/guide/error-handling).
+
+## Come faccio a rendere semplice HTML?
+
+Non lo fate! Non c'è bisogno di "render" HTML con la funzione `res.render()`.
+Se hai un file specifico, usa la funzione `res.sendFile()`.
+Se stai servendo molti asset da una directory, usa la funzione middleware `express.static()`
+.
+
+## Quale versione di Node.js richiede Express?
+
+- [Express 4.x](/en/4x/api) richiede Node.js 0.10 o superiore.
+- [Express 5.x](/en/5x/api) richiede Node.js 18 o superiore.
diff --git a/src/content/docs/it/4x/starter/generator.mdx b/src/content/docs/it/4x/starter/generator.mdx
new file mode 100644
index 0000000000..1b0eeaa660
--- /dev/null
+++ b/src/content/docs/it/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Generatore di applicazioni espresso
+description: Scopri come utilizzare lo strumento del generatore di applicazioni Express per creare rapidamente uno scheletro per le applicazioni Express.js, semplificando la configurazione e la configurazione.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilizzare lo strumento generatore di applicazioni, `express-generator`, per creare rapidamente uno scheletro di applicazione.
+
+È possibile eseguire il generatore di applicazioni con il comando `npx` (disponibile in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+Per le versioni precedenti di Node, installare il generatore di applicazioni come pacchetto globale npm e quindi lanciarlo:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Visualizza le opzioni del comando con l'opzione `-h`:
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opzioni:
+
+    -h, --help informazioni di utilizzo dell'output
+        --version output il numero di versione
+    -e, --ejs aggiungi il supporto del motore ejs
+        --hbs aggiungi il supporto del motore del manubrio
+        --pug aggiungi il supporto del motore del pug
+    -H, --hogan aggiungi hogan. s supporto motore
+        --no-view genera senza motore di visualizzazione
+    -v, --view <engine> aggiungi vista <engine> supporto (ejs<unk> hbs<unk> hjs<unk> jade<unk> pug<unk> twig<unk> vash) (valori predefiniti per jade)
+    -c, --css <engine>  aggiungi il foglio di stile <engine> supporto (less<unk> stylus<unk> compass<unk> sass) (valori predefiniti per css normali)
+        --git add . itignore
+    -f, --force force sulla directory non vuota
+```
+
+Ad esempio, il seguente crea un'app Express chiamata _myapp_. L'app verrà creata in una cartella chiamata _myapp_ nella directory di lavoro corrente e il motore di visualizzazione sarà impostato su <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/route
+   create : myapp/routes/index. s
+   create : myapp/routes/users. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Quindi installare dipendenze:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+Su MacOS o Linux, esegui l'app con questo comando:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Su Windows Command Prompt, utilizzare questo comando:
+
+```bash
+> imposta DEBUG=myapp:* & npm start
+```
+
+Su Windows PowerShell, utilizzare questo comando:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Quindi, caricare `http://localhost:3000/` nel tuo browser per accedere all'app.
+
+L'app generata ha la seguente struttura di directory:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+La struttura delle app creata dal generatore è solo uno dei tanti modi per strutturare le app Express.
+Sentitevi liberi di utilizzare questa struttura o modificarla per soddisfare al meglio le vostre esigenze.
+
+</Alert>
diff --git a/src/content/docs/it/4x/starter/hello-world.mdx b/src/content/docs/it/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..4b4df6bcfe
--- /dev/null
+++ b/src/content/docs/it/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Ciao esempio mondiale
+description: Inizia con Express.js costruendo una semplice applicazione 'Ciao Mondo', dimostrando la configurazione di base e la creazione di server per i principianti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Incorporato qui sotto è essenzialmente l'app Express più semplice che puoi creare. Si tratta di un singolo file app
+&mdash; _non_ quello che si otterrebbe se si utilizza il [Express generator](/en/starter/generator), che
+crea il ponteggio per un'app completa con numerosi file JavaScript, modelli Jade e sottodirectory
+per vari scopi.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+Questa app avvia un server e ascolta la porta 3000 per le connessioni. L'app risponde con "Ciao Mondo!" per le richieste
+all'URL radice (`/`) o _route_. Per ogni altro percorso, risponderà con un **404 non trovato**.
+
+## Esecuzione Localmente
+
+Crea prima una directory chiamata `myapp`, cambiala ed esegui `npm init`. Quindi, installa `express` come dipendenza, secondo la [guida all'installazione](/en/starter/installing).
+
+Nella directory `myapp`, crea un file chiamato `app.js` e copia il codice dall'esempio qui sopra.
+
+<Alert type="allerta">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Eseguire l'app con il seguente comando:
+
+```bash
+$ node app.js
+```
+
+Quindi, caricare `http://localhost:3000/` in un browser per vedere l'output.
diff --git a/src/content/docs/it/4x/starter/installing.mdx b/src/content/docs/it/4x/starter/installing.mdx
new file mode 100644
index 0000000000..ef69cf7a33
--- /dev/null
+++ b/src/content/docs/it/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installazione
+description: Scopri come installare Express.js nel tuo ambiente Node.js, inclusa la creazione della directory del progetto e la gestione delle dipendenze con npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Prima di iniziare, assicurati di avere [Node.js](https://nodejs.org/) 0.10 o superiore installato. Quindi, creare una directory per la vostra applicazione e navigare in essa.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Usa il comando `npm init` per creare un file `package.json` per la tua applicazione.
+Per maggiori informazioni sul funzionamento di `package.json`, vedere [Specifiche della gestione di npm.json](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Questo comando ti richiede un certo numero di cose, come il nome e la versione della tua applicazione.
+Per ora, puoi semplicemente premere RETURN per accettare i valori predefiniti per la maggior parte di essi, con la seguente eccezione:
+
+```
+punto di ingresso: (index.js)
+```
+
+Inserisci `app.js`, o qualsiasi cosa desideri che sia il nome del file principale. Se vuoi che sia `index.js`, premi RETURN per accettare il nome del file predefinito suggerito.
+
+Ora, installa Express nella directory `myapp` e salvalo nella lista delle dipendenze. Per esempio:
+
+```bash
+npm install express
+```
+
+Per installare Express temporaneamente e non aggiungerlo alla lista delle dipendenze:
+
+```bash
+npm installa express --no-save
+```
+
+<Alert type="info">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Poi, dopo aver eseguito `npm install` nella directory dell'app installerà automaticamente i moduli
+nell'elenco delle dipendenze.
+
+</Alert>
diff --git a/src/content/docs/it/4x/starter/static-files.mdx b/src/content/docs/it/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..89d90034cf
--- /dev/null
+++ b/src/content/docs/it/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servire file statici in Express
+description: Comprendi come servire file statici come immagini, CSS e JavaScript nelle applicazioni Express.js utilizzando il middleware 'static' integrato.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Per servire file statici come immagini, file CSS e file JavaScript, utilizzare la funzione middleware integrata `express.static` in Express.
+
+La firma della funzione è:
+
+```js
+express.static(root, [options]);
+```
+
+L'argomento `root` specifica la directory radice da cui servire le risorse statiche.
+Per ulteriori informazioni sull'argomento `options`, vedere [express.static](/en/5x/api#express.static).
+
+Per esempio, utilizzare il seguente codice per servire immagini, file CSS e file JavaScript in una directory chiamata `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Ora, puoi caricare i file che sono nella directory `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express cerca i file relativi alla directory statica, quindi il nome della directory statica
+non fa parte dell'URL.
+
+</Alert>
+
+Per utilizzare più directory di asset statici, chiama la funzione middleware `express.static`:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express cerca i file nell'ordine in cui si impostano le directory statiche con la funzione middleware `express.static`.
+
+<Alert type="info">
+
+Per ottenere risultati ottimali, utilizza un proxy
+inverso cache per migliorare le prestazioni di
+che servono risorse statiche.
+
+</Alert>
+
+Per creare un prefisso di percorso virtuale (dove il percorso non esiste effettivamente nel file system) per i file serviti dal `express. funzione tatic`, [specify a mount path](/en/5x/api#app.use) per la directory statica, come mostrato di seguito:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Ora puoi caricare i file che sono nella directory `public` dal prefisso del percorso `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Tuttavia, il percorso che fornisci alla funzione `express.static` è relativo alla directory da cui avvii il processo `node`. Se si esegue l'app express da un'altra directory, è più sicuro utilizzare il percorso assoluto della directory che si desidera servire:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public'));
+```
+
+Per maggiori dettagli sulla funzione `serve-static` e sulle sue opzioni, vedere [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/it/5x/advanced/developing-template-engines.md b/src/content/docs/it/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..3c00548d60
--- /dev/null
+++ b/src/content/docs/it/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Sviluppo di modelli di motori per Express
+description: Impara a sviluppare motori di template personalizzati per Express.js utilizzando app.engine(), con esempi sulla creazione e l'integrazione della tua logica di rendering dei modelli.
+---
+
+Usa il metodo `app.engine(ext, callback)` per creare il tuo modello di motore. `ext` si riferisce all'estensione del file, e `callback` è la funzione del motore del modello, che accetta i seguenti elementi come parametri: la posizione del file, l'oggetto opzioni, e la funzione di callback.
+
+Il seguente codice è un esempio di implementazione di un semplice modello di motore per il rendering dei file `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+La tua app sarà ora in grado di visualizzare i file `.ntl`. Crea un file chiamato `index.ntl` nella directory `views` con il seguente contenuto.
+
+```pug
+#title#
+#message#
+```
+
+Quindi, crea il seguente percorso nella tua app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando fai una richiesta alla home page, `index.ntl` sarà renderizzato come HTML.
diff --git a/src/content/docs/it/5x/guide/behind-proxies.mdx b/src/content/docs/it/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..a31c0ad959
--- /dev/null
+++ b/src/content/docs/it/5x/guide/behind-proxies.mdx
@@ -0,0 +1,104 @@
+---
+title: Espresso dietro i proxy
+description: Scopri come configurare le applicazioni Express.js per funzionare correttamente dietro i proxy inversi, anche utilizzando l'impostazione del proxy di trust per gestire gli indirizzi IP del client.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Quando si esegue un'app Express dietro un proxy inverso, alcune delle API Express possono restituire valori diversi da quelli previsti. Al fine di adeguarsi a questo, l'impostazione dell'applicazione `trust proxy` può essere utilizzata per esporre le informazioni fornite dal proxy inverso nelle API Express. Il problema più comune è l'espressione API che espone l'indirizzo IP del cliente può invece mostrare un indirizzo IP interno del proxy inverso.
+
+<Alert type="info">
+
+Durante la configurazione dell'impostazione `trust proxy`, è importante capire l'esatta configurazione del proxy inverso
+. Dal momento che questa impostazione sarà i valori di fiducia forniti nella richiesta, è importante che
+la combinazione dell'impostazione in Express corrisponda al funzionamento del proxy inverso.
+
+</Alert>
+
+L'impostazione dell'applicazione `trust proxy` può essere impostata su uno dei valori elencati nella seguente tabella.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Se `true`, l'indirizzo IP del cliente è inteso come la voce più sinistra nell'intestazione `X-Forwarded-For`.
+
+Se `false`, l'app è intesa come rivolta direttamente al client e l'indirizzo IP del cliente è derivato da `req.socket.remoteAddress`. Questa è l'impostazione predefinita.
+
+<Alert type="avviso">
+Quando si imposta a `true`, è importante assicurarsi che l'ultimo proxy inverso attendibile stia rimuovendo/sovrascrivendo tutte le seguenti intestazioni HTTP: `X-Forwarded-For`, `X-Forwarded-Host`, e `X-Forwarded-Proto`, altrimenti potrebbe essere possibile per il cliente fornire qualsiasi valore.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>indirizzi IP</td>
+<td markdown="1">
+Un indirizzo IP, una sottorete, o un array di indirizzi IP e sottoreti a cui fidarsi come proxy inverso. Il seguente elenco mostra i nomi pre-configurati delle sottorete
+
+- loopback - `127.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+È possibile impostare gli indirizzi IP in uno dei seguenti modi:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+Se specificato, gli indirizzi IP o le sottoreti sono esclusi dal processo di determinazione dell'indirizzo, e l'indirizzo IP non attendibile più vicino al server dell'applicazione è determinato come indirizzo IP del client. Questo funziona controllando se `req.socket.remoteAddress` è attendibile. In tal caso, ogni indirizzo in `X-Forwarded-For` viene controllato da destra a sinistra fino al primo indirizzo non fidato.
+
+</td>
+    </tr>
+    <tr>
+      <td>Numero</td>
+<td markdown="1">
+Usa l'indirizzo che è al massimo `n` numero di luppolo lontano dall'applicazione Express. `req.socket.remoteAddress` è il primo hop, e il resto sono cercati nell'intestazione `X-Forwarded-For` da destra a sinistra. Un valore di `0` significa che il primo indirizzo non attendibile sarebbe `req.socket.remoteAddress`, cioè non c'è un proxy inverso.
+
+<Alert type="avviso">
+Quando si utilizza questa impostazione, è importante assicurarsi che non ci siano multipli, percorsi diversi per l'applicazione Express in modo che il client possa essere inferiore al numero configurato di luppolo di distanza, altrimenti potrebbe essere possibile per il cliente fornire qualsiasi valore.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      Funzione <td />
+<td markdown="1">
+Implementazione fiducia personalizzata.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' <unk> <unk> ip === '123.123.123. 23')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Abilitare il `trust proxy` avrà il seguente impatto:
+
+<ul>
+  <li markdown="1">
+    Il valore di [req.hostname](/en/api#req.hostname) è derivato dal valore impostato
+    nell'intestazione `X-Forwarded-Host`, che può essere impostato dal cliente o dal proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` può essere impostato dal proxy inverso per dire all'app se si tratta di `↓ `
+    o `http` o anche di un nome non valido. Questo valore è riflesso da
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    I valori [req.ip](/en/api#req.ip) e [req.ips](/en/api#req.ips) sono popolati in base
+    all'indirizzo del socket e all'intestazione `X-Forwarded-For`, a partire dal primo indirizzo non
+    fidato.
+  </li>
+</ul>
+
+L'impostazione `trust proxy` è implementata usando il pacchetto [proxy-addr](https://www.npmjs.com/package/proxy-addr). Per ulteriori informazioni, consultare la documentazione.
diff --git a/src/content/docs/it/5x/guide/debugging.mdx b/src/content/docs/it/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..592e46618a
--- /dev/null
+++ b/src/content/docs/it/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debug Express
+description: Scopri come abilitare e utilizzare i log di debug nelle applicazioni Express.js impostando la variabile di ambiente DEBUG per la risoluzione dei problemi migliorata.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Per vedere tutti i log interni utilizzati in Express, imposta la variabile d'ambiente `DEBUG` su
+`express:*` quando lancia la tua app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Su Windows, utilizzare il comando corrispondente.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+L'esecuzione di questo comando nell'app predefinita generata dal [express generator](/en/starter/generator) stampa il seguente output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Quando viene fatta una richiesta all'applicazione, vedrete i registri specificati nel codice Express:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Per vedere i log solo dall'implementazione del router, imposta il valore di `DEBUG` su `express:router`. Allo stesso modo, per vedere i log solo dall'implementazione dell'applicazione, imposta il valore di `DEBUG` su `express:application`, e così via.
+
+## Applicazioni generate da `express`
+
+Un'applicazione generata dal comando `express` utilizza il modulo `debug` e il suo namespace di debug è indirizzato al nome dell'applicazione.
+
+Ad esempio, se hai generato l'app con `$ express sample-app`, puoi abilitare le istruzioni di debug con il seguente comando:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+È possibile specificare più di uno spazio dei nomi di debug assegnando una lista di nomi separati da virgole:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Opzioni avanzate
+
+Quando si esegue attraverso Node.js, è possibile impostare alcune variabili di ambiente che cambieranno il comportamento della registrazione di debug:
+
+| Nome                | Scopo                                                   |
+| ------------------- | ------------------------------------------------------- |
+| `DEBUG`             | Abilita/disabilita spazi di debug specifici.            |
+| `DEBUG_COLORS`      | Indica se usare o meno i colori nell'output di debug.   |
+| `DEBUG_DEPTH`       | Profondità dell'ispezione dell'oggetto.                 |
+| `DEBUG_FD`          | Descrittore file su cui scrivere l'output di debug.     |
+| `DEBUG_SHOW_HIDDEN` | Mostra le proprietà nascoste sugli oggetti ispezionati. |
+
+<Alert type="info">
+
+Le variabili di ambiente che iniziano con `DEBUG_` finiscono per essere convertite in un oggetto Opzioni
+che viene utilizzato con i formatori `%o`/`%O`. Vedere la documentazione Node.js per
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) per l'elenco completo
+.
+
+</Alert>
diff --git a/src/content/docs/it/5x/guide/error-handling.mdx b/src/content/docs/it/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..3378bd2b75
--- /dev/null
+++ b/src/content/docs/it/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Gestione Degli Errori
+description: Capire come Express.js gestisce gli errori nel codice sincrono e asincrono e imparare ad implementare middleware gestione degli errori personalizzati per le vostre applicazioni.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ si riferisce a come Express cattura ed elabora gli errori
+che si verificano in modo sincrono e asincrono. Express viene fornito con un gestore di errore
+predefinito quindi non è necessario scrivere il proprio per iniziare.
+
+## Errori Di Cattura
+
+È importante garantire che Express colmi tutti gli errori che si verificano mentre
+gestisce le rotte e middleware.
+
+Gli errori che si verificano nel codice sincrono all'interno dei gestori del percorso e del middleware
+non richiedono lavoro aggiuntivo. Se il codice sincrono lancia un errore, allora Express catturerà
+ed elaborerà esso. Per esempio:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express lo catturerà da solo.
+});
+```
+
+Per gli errori restituiti da funzioni asincrone invocate dai gestori degli itinerari
+e middleware, devi passarli alla funzione `next()`, dove Express sarà
+catturarli ed elaborarli. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Passa gli errori a Express.
+    } else {
+      res.end(dati);
+    }
+  });
+});
+```
+
+A partire da Express 5, i gestori del percorso e il middleware che restituiscono una Promise
+chiameranno automaticamente `next(value)` quando rifiutano o generano un errore.
+Per esempio:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Se `getUserById` genera un errore o rifiuta, `next` verrà chiamato con
+l'errore generato o il valore rifiutato. Se non viene fornito alcun valore rifiutato, `next`
+verrà chiamato con un oggetto di errore predefinito fornito dal router Express.
+
+Se passi qualcosa alla funzione `next()` (tranne la stringa `'route'`),
+Express considera la richiesta corrente come un errore e salterà qualsiasi
+rimanenti funzioni di routing e middleware senza errori.
+
+Se il callback in una sequenza non fornisce dati, solo errori, è possibile semplificare
+questo codice come segue:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+Nell'esempio precedente, `next` è fornito come callback per `fs.writeFile`,
+che viene chiamato con o senza errori. Se non c'è errore, viene eseguito il secondo gestore
+, altrimenti Express cattura ed elabora l'errore.
+
+È necessario catturare gli errori che si verificano in codice asincrono invocato dai router o
+middleware e passarli a Express per l'elaborazione. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+L'esempio precedente utilizza un blocco `try...catch` per catturare errori nel codice asincrono
+e passarli a Express. Se il blocco `prova...catch`
+fosse omesso, Express non coglierebbe l'errore dal momento che non fa parte del codice di gestione
+sincrono.
+
+Usa le promesse per evitare l'overhead del blocco `prova...catch` o quando usi le funzioni
+che restituiscono le promesse. Per esempio:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .hen(() => {
+      throw new Error('BROKEN');
+    })
+    .atch(next); // Gli errori saranno passati a Express.
+});
+```
+
+Dal momento che le promesse catturano automaticamente entrambi gli errori sincroni e le promesse rifiutate,
+puoi semplicemente fornire `next` come il gestore finale di cattura e Express catturerà errori,
+perché al gestore della cattura viene dato l'errore come primo argomento.
+
+Si potrebbe anche utilizzare una catena di gestori per fare affidamento su errore sincrono
+catching, riducendo il codice asincrono a qualcosa di banale. Per esempio:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.ata = dati;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+L'esempio precedente ha un paio di istruzioni banali dalla chiamata `readFile`
+. Se `readFile` causa un errore, allora passa l'errore a Express, altrimenti
+torna rapidamente al mondo della gestione sincrona degli errori nel prossimo gestore
+nella catena. Poi, l'esempio di cui sopra cerca di elaborare i dati. Se questo fallisce, il gestore di errori sincroni
+lo catturerà. Se avessi fatto questa elaborazione all'interno di
+il callback `readFile`, l'applicazione potrebbe uscire e i gestori dell'errore Express
+non sarebbero stati eseguiti.
+
+Qualunque metodo si utilizzi, se si desidera che i gestori di errori Express siano chiamati dentro e l'applicazione
+per sopravvivere, è necessario assicurarsi che Express riceva l'errore.
+
+## Il gestore degli errori predefinito
+
+Express è dotato di un gestore di errori integrato che si occupa di eventuali errori che potrebbero essere riscontrati nell'app. Questa funzione middleware di gestione degli errori predefinita viene aggiunta alla fine dello stack della funzione middleware.
+
+Se passi un errore a `next()` e non lo gestisci in un gestore di errore
+personalizzato, sarà gestito dal gestore di errori integrato; l'errore sarà
+scritto al client con la traccia dello stack. La traccia dello stack non è inclusa
+nell'ambiente di produzione.
+
+<Alert type="info">
+
+Imposta la variabile d'ambiente `NODE_ENV` su `production`, per eseguire l'applicazione in modalità di produzione.
+
+</Alert>
+
+Quando viene scritto un errore, alla risposta
+vengono aggiunte le seguenti informazioni:
+
+- Il `res.statusCode` è impostato da `err.status` (o `err.statusCode`). Se
+  questo valore è al di fuori dell'intervallo 4xx o 5xx, sarà impostato a 500.
+- Il `res.statusMessage` è impostato in base al codice di stato.
+- Il corpo sarà l'HTML del messaggio del codice di stato quando in ambiente di produzione
+  , altrimenti sarà `err.stack`.
+- Qualsiasi intestazione specificata in un oggetto `err.headers`.
+
+Se chiami `next()` con un errore dopo aver iniziato a scrivere la risposta
+(ad esempio, se riscontri un errore durante lo streaming della risposta
+al client), il gestore di errore predefinito Express chiude la connessione
+e non riesce la richiesta.
+
+Quindi, quando si aggiunge un gestore di errori personalizzato, è necessario delegare a
+il gestore di errori Express predefinito, quando le intestazioni
+sono già state inviate al client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Nota che il gestore di errori predefinito può essere attivato se chiami `next()` con un errore
+nel tuo codice più di una volta, anche se la gestione degli errori personalizzati è in funzione.
+
+Altri errori di gestione middleware possono essere trovati su [Express middleware](/en/resources/middleware).
+
+## Gestione errori di scrittura
+
+Definire le funzioni middleware per la gestione degli errori allo stesso modo di altre funzioni middleware,
+eccetto le funzioni di gestione degli errori hanno quattro argomenti invece di tre:
+`(err, req, res, next)`. Per esempio:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Definisci l'ultima gestione degli errori del middleware, dopo altre chiamate `app.use()` e percorsi; per esempio:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Le risposte da all'interno di una funzione middleware possono essere in qualsiasi formato, come una pagina di errore HTML, un semplice messaggio, o una stringa JSON.
+
+Per scopi organizzativi (e di framework di livello superiore) è possibile definire diverse funzioni middleware di gestione degli errori
+come si farebbe con funzioni di middleware regolari
+. Ad esempio, per definire un gestore di errori
+per le richieste fatte utilizzando `XHR` e quelle senza:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app. se(
+  bodyParser.urlencoded({
+    extended true,
+  })
+);
+app. se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In questo esempio, i `logErrors` generici potrebbero scrivere la richiesta e le informazioni di errore
+in `stderr`, per esempio:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Anche in questo esempio, `clientErrorHandler` è definito come segue; in questo caso, l'errore viene esplicitamente passato a quello successivo.
+
+Nota che quando _non_ chiama "next" in una funzione di gestione degli errori, sei responsabile della scrittura (e della fine) della risposta. In caso contrario, tali richieste saranno "appese" e non saranno ammissibili per la raccolta rifiuti.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementa la funzione `errorHandler` "catch-all" come segue (per esempio):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Se si dispone di un gestore del percorso con molteplici funzioni di callback, è possibile utilizzare il parametro `route` per passare al prossimo gestore del percorso. Per esempio:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.asPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.ind((err, doc) => {
+      if (err) return next(err);
+      res.son(doc);
+    });
+  }
+);
+```
+
+In questo esempio, il gestore `getPaidContent` sarà saltato, ma qualsiasi gestore rimanente in `app` per `/a_route_behind_paywall` continuerà ad essere eseguito.
+
+<Alert type="info">
+
+Le chiamate a `next()` e `next(err)` indicano che il gestore corrente è completo e in quale stato.
+`next(err)` salterà tutti i gestori rimanenti nella catena ad eccezione di quelli che sono impostati su
+gestire gli errori come descritto sopra.
+
+</Alert>
diff --git a/src/content/docs/it/5x/guide/overriding-express-api.md b/src/content/docs/it/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..86696c08e0
--- /dev/null
+++ b/src/content/docs/it/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Sovrascrivendo l'API Express
+description: Scopri come personalizzare ed estendere l'API di Express.js sovrascrivendo i metodi e le proprietà su richiesta e gli oggetti di risposta utilizzando prototipi.
+---
+
+L'API Express è composta da vari metodi e proprietà su richiesta e oggetti di risposta. Questi sono ereditati dal prototipo. Ci sono due punti di estensione per l'API Express:
+
+1. I prototipi globali in `express.request` e `express.response`.
+2. prototipi specifici per app su `app.request` e `app.response`.
+
+La modifica dei prototipi globali influenzerà tutte le applicazioni Express caricate nello stesso processo. Se lo si desidera, le modifiche possono essere rese specifiche alle app modificando solo i prototipi specifici delle app dopo aver creato una nuova app.
+
+## Metodi
+
+È possibile sovrascrivere la firma e il comportamento dei metodi esistenti con il proprio, assegnando una funzione personalizzata.
+
+Di seguito è riportato un esempio di sovrascrittura del comportamento di [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+L'implementazione di cui sopra cambia completamente la firma originale di `res.sendStatus`. Ora accetta un codice di stato, il tipo di codifica e il messaggio da inviare al client.
+
+Il metodo overridden può ora essere utilizzato in questo modo:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Proprietà
+
+Le proprietà nell'API Express sono:
+
+1. Proprietà assegnate (es: `req.baseUrl`, `req.originalUrl`)
+2. Definito come getters (es: `req.secure`, `req.ip`)
+
+Poiché le proprietà sotto la categoria 1 sono assegnate dinamicamente sugli oggetti `request` e `response` nel contesto dell'attuale ciclo di richiesta-risposta, il loro comportamento non può essere superato.
+
+Le proprietà sotto la categoria 2 possono essere sovrascritte utilizzando le API di estensione Express.
+
+Il seguente codice riscrive come deve essere derivato il valore di `req.ip`. Ora restituisce semplicemente il valore dell'intestazione della richiesta `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Protototipo
+
+Al fine di fornire l'API Express, gli oggetti richiesta/risposta passati a Express (tramite `app(req, res)`, per esempio) bisogno di ereditare dalla stessa catena prototipo. Per impostazione predefinita, questo è `http.IncomingRequest.prototype` per la richiesta e `http.ServerResponse.prototype` per la risposta.
+
+Se non necessario, si raccomanda che ciò avvenga solo a livello di applicazione e non a livello globale. Inoltre, fare in modo che il prototipo che viene utilizzato corrisponda la funzionalità il più vicino possibile ai prototipi predefiniti.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/it/5x/guide/routing.mdx b/src/content/docs/it/5x/guide/routing.mdx
new file mode 100644
index 0000000000..19873bbdf3
--- /dev/null
+++ b/src/content/docs/it/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Scopri come definire e utilizzare i percorsi nelle applicazioni Express.js, inclusi i metodi di percorso, i percorsi e i parametri e utilizzando Router per il routing modulare.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ si riferisce a come gli endpoint di un'applicazione (URI) rispondono alle richieste del client.
+Per un'introduzione al routing, vedere [Instradamento di base](/en/starter/basic-routing).
+
+Definisci il routing usando metodi dell'oggetto `app` Express che corrispondono ai metodi HTTP;
+per esempio, `app. et()` per gestire le richieste GET e `app.post` per gestire le richieste POST. Per una lista completa,
+vedi [app.METHOD](/en/5x/api#app.METHOD). Puoi anche usare [app.all()](/en/5x/api#app.all) per gestire tutti i metodi HTTP e [app. se()](/en/5x/api#app.use) to
+specify middleware as the callback function (Vedi [Using middleware](/en/guide/using-middleware) for details).
+
+Questi metodi di routing specificano una funzione di callback (a volte chiamata "funzioni di handler") chiamata quando l'applicazione riceve una richiesta al percorso specificato (endpoint) e il metodo HTTP. In altre parole, l'applicazione "ascolta" per le richieste che corrispondono ai percorsi e ai metodi specificati, e quando rileva una corrispondenza, chiama la funzione di callback specificata.
+
+Infatti, i metodi di routing possono avere più di una funzione di callback come argomenti.
+Con funzioni di callback multiple, è importante fornire `next` come argomento alla funzione di callback e poi chiamare `next()` all'interno del corpo della funzione per consegnare il controllo
+al prossimo callback.
+
+Il seguente codice è un esempio di un percorso molto basilare.
+
+```js
+const express = require('express');
+const app = express();
+
+// rispondi con "ciao mondo" quando una richiesta GET viene fatta all'app homepage
+. et('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Metodi percorso
+
+Un metodo di percorso è derivato da uno dei metodi HTTP ed è collegato ad un'istanza della classe `express`.
+
+Il seguente codice è un esempio di percorsi definiti per il `GET` e i metodi `POST` nella root dell'app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.end('Richiesta GET alla homepage');
+});
+
+// POST metodo percorso
+app.ost('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supporta metodi che corrispondono a tutti i metodi di richiesta HTTP: `get`, `post`, e così via.
+Per un elenco completo, vedere [app.METHOD](/en/5x/api#app.METHOD).
+
+C'è un metodo di routing speciale, `app.all()`, utilizzato per caricare le funzioni middleware in un percorso per _tutti_ i metodi di richiesta HTTP. Ad esempio, il seguente gestore viene eseguito per le richieste al percorso `"/secret"` se si utilizza `GET`, `POST`, `PUT`, `DELETE`, o qualsiasi altro metodo di richiesta HTTP supportato nel [modulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accedere alla sezione segreta ...');
+  next(); // passare il controllo al prossimo gestore
+});
+```
+
+## Percorsi di rotta
+
+Percorsi di percorso, in combinazione con un metodo di richiesta, definire gli endpoint in cui le richieste possono essere fatte. I tracciati del percorso possono essere stringhe, motivi di stringa o espressioni regolari.
+
+<Alert type="allerta">
+
+In express 5, i personaggi `? , `+`, `\*`, `[]`, e `()\` sono gestiti in modo diverso rispetto alla versione
+4, si prega di rivedere la [guida alla migrazione](/en/guide/migrating-5#path-syntax) per maggiori informazioni.
+
+</Alert>
+
+<Alert type="allerta">
+
+Nell'espressione 4, i caratteri di espressione regolare come `$` devono essere fuggiti con un `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express utilizza [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) per abbinare i percorsi del percorso
+; vedere la documentazione path-to-regexp per tutte le possibilità di definire i percorsi del percorso.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) è uno strumento utile per
+testare i percorsi Express di base, anche se non supporta la corrispondenza dei modelli.
+
+</Alert>
+
+<Alert type="warning">Le stringhe di query non fanno parte del percorso percorso.</Alert>
+
+### Percorsi di percorso basati su stringhe
+
+Questo percorso corrisponderà alle richieste del percorso root, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Questo percorso corrisponderà alle richieste di `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Questo percorso corrisponderà alle richieste a `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Percorsi del percorso in base ai motivi delle stringhe
+
+<Alert type="allerta">
+
+I modelli di stringhe in Express 5 non funzionano più. Si prega di fare riferimento alla [guida di migrazione
+(/en/guide/migrating-5#path-syntax) per ulteriori informazioni.
+
+</Alert>
+
+Questo percorso corrisponde a `acd` e `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Questo percorso corrisponderà a `abcd`, `abbcd`, `abbbcd`, e così via.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Questo percorso corrisponde a `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, e così via.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Questo percorso corrisponde a `/abe` e `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Percorsi di percorso basati su espressioni regolari
+
+Questo percorso corrisponderà a qualsiasi cosa con una "a" in esso.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Questo percorso corrisponde a `butterfly` e `dragonfly`, ma non a `butterflyman`, `dragonflyman`, e così via.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parametri percorso
+
+I parametri del percorso sono denominati segmenti di URL che vengono utilizzati per catturare i valori specificati nella loro posizione nell'URL. I valori catturati sono popolati nell'oggetto `req.params`, con il nome del parametro route specificato nel percorso come loro rispettive chiavi.
+
+```
+Percorso del percorso: /users/:userId/books/:bookId
+Richiedi URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Per definire i percorsi con i parametri del percorso, è sufficiente specificare i parametri del percorso nel percorso come mostrato di seguito.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="allerta">
+
+Il nome dei parametri del percorso deve essere composto da "caratteri di parola" ([A-Za-z0-9_]).
+
+</Alert>
+
+Poiché il trattino (`-`) e il punto (`.`) sono interpretati letteralmente, possono essere utilizzati insieme ai parametri del percorso per scopi utili.
+
+```
+Percorso del percorso: /flights/:from-:to
+Richiedi URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Percorso percorso: /plantae/:genus.:species
+Richiedi URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="allerta">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Per avere più controllo sulla stringa esatta che può essere abbinata a un parametro del percorso, puoi aggiungere un'espressione regolare tra parentesi (`()`):
+
+```
+Percorso del percorso: /user/:userId(\d+)
+Richiedi URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="avviso">
+
+Perché l'espressione regolare è di solito parte di una stringa letterale, assicurati di sfuggire a qualsiasi carattere `\`
+con un backslash aggiuntivo, ad esempio `\d+`.
+
+</Alert>
+
+<Alert type="avviso">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">il carattere `*` nelle espressioni regolari non viene interpretato nel modo usuale</a>. Come soluzione puoi usare `{0,}` invece di `*`. Questo sarà probabilmente fissato in Express 5.
+</Alert>
+
+## Gestori del percorso
+
+È possibile fornire più funzioni di callback che si comportano come [middleware](/en/guide/using-middleware) per gestire una richiesta. L'unica eccezione è che questi callback potrebbero invocare `next('route')` per bypassare i rimanenti callback del percorso. È possibile utilizzare questo meccanismo per imporre condizioni preliminari su un percorso, poi passare il controllo ai percorsi successivi se non c'è motivo di procedere con il percorso corrente.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('route');
+  }
+  res.end(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In questo esempio:
+
+- `GET /user/5` → gestito dal primo percorso → invia "User 5"
+- `GET /user/0` → prima rotta chiama `next('route')`, saltando al prossimo percorso corrispondente `/user/:id`
+
+I gestori del percorso possono essere nella forma di una funzione, una serie di funzioni, o combinazioni di entrambi, come mostrato negli esempi seguenti.
+
+Una singola funzione di callback può gestire un percorso. Per esempio:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+Più di una funzione di callback può gestire un percorso (assicurati di specificare l'oggetto `next`). Per esempio:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('la risposta verrà inviata dalla funzione successiva . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Ciao da B!');
+  }
+);
+```
+
+Un array di funzioni di callback può gestire un percorso. Per esempio:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Ciao da C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Una combinazione di funzioni indipendenti e matrici di funzioni può gestire un percorso. Per esempio:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+app.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('la risposta verrà inviata dalla funzione successiva . .');
+    next();
+  },
+  (req, res) => {
+    res.end('Ciao da D!');
+  }
+);
+```
+
+## Metodi di risposta
+
+I metodi sull'oggetto di risposta (`res`) nella tabella seguente possono inviare una risposta al client e terminare il ciclo di richiesta-risposta. Se nessuno di questi metodi è chiamato da un gestore del percorso, la richiesta del cliente sarà sospesa.
+
+| Metodo                                        | Descrizione                                                                                                        |
+| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [res.download()](/en/5x/api#res.download)     | Avverte un file da scaricare.                                                                                      |
+| [res.end()](/en/5x/api#res.end)               | Termina il processo di risposta.                                                                                   |
+| [res.json()](/en/5x/api#res.json)             | Invia una risposta JSON.                                                                                           |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Invia una risposta JSON con il supporto JSONP.                                                                     |
+| [res.redirect()](/en/5x/api#res.redirect)     | Reindirizza una richiesta.                                                                                         |
+| [res.render()](/en/5x/api#res.render)         | Render un modello di visualizzazione.                                                                              |
+| [res.send()](/en/5x/api#res.send)             | Invia una risposta di vari tipi.                                                                                   |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Invia un file come un flusso di otte.                                                                              |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Imposta il codice di stato della risposta e invia la sua rappresentazione della stringa come corpo della risposta. |
+
+## app.route()
+
+È possibile creare i gestori di rotte per un percorso utilizzando `app.route()`.
+Poiché il percorso è specificato in una singola posizione, è utile creare percorsi modulari, così come ridurre la ridondanza e pneumatici. Per ulteriori informazioni sulle rotte, si veda: [Router() documentation](/en/5x/api#router).
+
+Ecco un esempio di router incatenati che sono definiti utilizzando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Ottieni un libro casuale');
+  })
+  .ost((req, res) => {
+    res.send('Add a book');
+  })
+  .ut((req, res) => {
+    res.send('Aggiorna il libro');
+  });
+```
+
+## express.Router
+
+Usa la classe `express.Router` per creare i gestori modulari e montabili. Un'istanza `Router` è un sistema di routing e middleware completo; per questo motivo è spesso chiamata "mini-app".
+
+L'esempio seguente crea un router come modulo, carica una funzione middleware in esso, definisce alcuni percorsi e monta il modulo del router su un percorso nell'app principale.
+
+Crea un file router chiamato `birds.js` nella directory delle app, con il seguente contenuto:
+
+```js
+const express = require('express');
+const router = express. outer();
+
+// middleware che è specifico per questo router
+const timeLog = (req, res, next) => {
+  console. og('Orario: ', Date.now());
+  next();
+};
+router. se(timeLog);
+
+// definisci il percorso della home page
+router.get('/', (req, res) => {
+  res. end('Birds home page');
+});
+// definire il router sulla rotta
+. et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Quindi, caricare il modulo router nell'app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+L'app sarà ora in grado di gestire le richieste di `/birds` e `/birds/about`, oltre a chiamare la funzione middleware `timeLog` che è specifica per il percorso.
+
+Ma se il percorso principale `/birds` ha parametri di percorso, non sarà accessibile per impostazione predefinita dai sotto-percorsi. Per renderlo accessibile, dovrai passare l'opzione `mergeParams` al costruttore Router [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/it/5x/guide/using-middleware.mdx b/src/content/docs/it/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..25d334aeb0
--- /dev/null
+++ b/src/content/docs/it/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usare middleware
+description: Scopri come utilizzare middleware nelle applicazioni Express.js, tra cui middleware a livello di applicazione e router, gestione degli errori e integrazione di middleware di terze parti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express è un framework web routing e middleware che ha funzionalità minime proprie: Un'applicazione Express è essenzialmente una serie di chiamate di funzioni middleware.
+
+Le funzioni _Middleware_ sono funzioni che hanno accesso al [request object](/en/5x/api#req) (`req`), il [response object](/en/5x/api#res) (`res`), e la successiva funzione middleware nel ciclo request-response dell'applicazione. La funzione middleware successiva è comunemente indicata da una variabile chiamata `next`.
+
+Le funzioni Middleware possono eseguire le seguenti attività:
+
+- Esegue qualsiasi codice.
+- Effettuare modifiche alla richiesta e agli oggetti di risposta.
+- Terminare il ciclo richiesta-risposta.
+- Chiama la funzione middleware successiva nello stack.
+
+Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve chiamare `next()` per passare il controllo alla successiva funzione middleware. In caso contrario, la richiesta sarà sospesa.
+
+Un'applicazione Express può utilizzare i seguenti tipi di middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Gestione errori middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [middleware di terze parti](#middleware.third-party)
+
+È possibile caricare il middleware a livello di applicazione e router con un percorso di montaggio opzionale.
+È inoltre possibile caricare una serie di funzioni middleware insieme, che crea una sottopila del sistema middleware in un punto di montaggio.
+
+## Middleware a livello di applicazione
+
+Associa il middleware di livello applicativo ad un'istanza del [app object](/en/5x/api#app) usando `app.use()` e `app. ETHOD()` funzioni, dove `METHOD` è il metodo HTTP della richiesta che la funzione middleware gestisca (come GET, PUT, o POST) in minuscolo.
+
+Questo esempio mostra una funzione middleware senza percorso di montaggio. La funzione viene eseguita ogni volta che l'app riceve una richiesta.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Questo esempio mostra una funzione middleware montata sul percorso `/user/:id`. La funzione viene eseguita per qualsiasi tipo di richiesta HTTP
+sul percorso `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+Questo esempio mostra un percorso e la sua funzione di gestore (sistema middleware). La funzione gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Ecco un esempio di caricamento di una serie di funzioni middleware in un punto di montaggio, con un percorso di montaggio.
+Illustra un sub-stack middleware che stampa la richiesta di informazioni per qualsiasi tipo di richiesta HTTP al percorso `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.og('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+I gestori del percorso consentono di definire percorsi multipli per un percorso. L'esempio sottostante definisce due percorsi per le richieste GET al percorso `/user/:id`. Il secondo percorso non causerà alcun problema, ma non verrà mai chiamato perché il primo percorso termina il ciclo richiesta-risposta.
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req. arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res. end('Info utente');
+  }
+);
+
+// handler per il percorso /user/:id, che stampa l'app ID utente
+. et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Per saltare il resto delle funzioni middleware da uno stack middleware router, chiama `next('route')` per passare il controllo al percorso successivo.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // se l'ID utente è 0, salta al prossimo percorso
+    se (req. arams. d === '0') next('route');
+    // altrimenti passa il controllo alla funzione middleware successiva in questo stack
+    altrimenti successivo();
+  },
+  (req, res, next) => {
+    // invia una risposta regolare
+    res. end('regular');
+  }
+);
+
+// handler per il percorso /user/:id, che invia una risposta speciale
+app. et('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware può anche essere dichiarato in un array per la riutilizzabilità.
+
+Questo esempio mostra un array con un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware funziona allo stesso modo di application-level middleware, tranne che è legato ad un'istanza di `express.Router()`.
+
+```js
+router const = express.Router();
+```
+
+Carica il middleware a livello router usando le funzioni `router.use()` e `router.METHOD()`.
+
+Il seguente esempio di codice replica il sistema middleware che viene mostrato sopra per il middleware a livello di applicazione, utilizzando il middleware a livello di router:
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// una funzione middleware senza percorso di montaggio. Questo codice viene eseguito per ogni richiesta al router
+. se((req, res, next) => {
+  console.log('Time:', Date. ow());
+  next();
+});
+
+// un sub-stack middleware mostra le informazioni di richiesta per qualsiasi tipo di richiesta HTTP al router /user/:id path
+. se(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console. og('Request Type:', req. ethod);
+    next();
+  }
+);
+
+// un sub-stack middleware che gestisce le richieste GET al router /user/:id path
+. et(
+  '/user/:id',
+  (req, res, next) => {
+    // se l'ID utente è 0, salta al router successivo
+    se (req. arams. d === '0') next('route');
+    // altrimenti passa il controllo alla successiva funzione middleware in questo stack
+    altrimenti successivo();
+  },
+  (req, successivo) => {
+    // renderizza una pagina normale
+    res. ender('regular');
+  }
+);
+
+// handler per il percorso /user/:id, che rende una pagina speciale
+router. et('/user/:id', (req, res, next) => {
+  console. og(req.params.id);
+  res.render('special');
+});
+
+// monta il router sull'app
+app.use('/', router);
+```
+
+Per saltare il resto delle funzioni middleware del router, chiama `next('router')`
+per passare il controllo indietro dall'istanza del router.
+
+Questo esempio mostra un sub-stack middleware che gestisce le richieste GET al percorso `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = express. outer();
+
+// predicare il router con un controllo e salvataggio quando necessario router
+. se((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa il router e 401 qualsiasi cosa che cade attraverso l'app
+. se('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## middleware gestione errori
+
+<Alert type="allerta">
+
+La gestione degli errori del middleware richiede sempre _four_ argomenti. È necessario fornire quattro argomenti per
+identificarlo come una funzione middleware di gestione degli errori. Anche se non è necessario utilizzare l'oggetto `next`
+, è necessario specificarlo per mantenere la firma. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Definire le funzioni middleware per la gestione degli errori allo stesso modo di altre funzioni middleware, tranne con quattro argomenti invece di tre, specificatamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Per maggiori dettagli sulla gestione degli errori middleware, vedere [Gestione degli errori](/en/guide/error-handling).
+
+## Middleware incorporato
+
+A partire dalla versione 4.x, Express non dipende più da [Connect](https://github.com/senchalabs/connect). Le funzioni middleware
+che erano state precedentemente incluse con Express sono ora in moduli separati; vedi [la lista delle funzioni middleware](https://github.com/senchalabs/connect#middleware).
+
+Express ha le seguenti funzioni middleware integrate:
+
+- [express.static](/en/5x/api#express.static) serve risorse statiche come file HTML, immagini e così via.
+- [express.json](/en/5x/api#express.json) analizza le richieste in arrivo con i payload JSON. **NOTA: Disponibile con Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analizza le richieste in arrivo con payload codificati con URL. **NOTA: Disponibile con Express 4.16.0+**
+
+## middleware di terze parti
+
+Usa middleware di terze parti per aggiungere funzionalità alle app Express.
+
+Installare il modulo Node.js per le funzionalità richieste, quindi caricarlo nell'app a livello di applicazione o a livello di router.
+
+L'esempio seguente illustra l'installazione e il caricamento della funzione middleware di analisi dei cookie `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Per una lista parziale delle funzioni middleware di terze parti che sono comunemente usate con Express, vedere [middleware di terze parti](../resources/middleware).
diff --git a/src/content/docs/it/5x/guide/using-template-engines.mdx b/src/content/docs/it/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..3548142cd6
--- /dev/null
+++ b/src/content/docs/it/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Utilizzo di modelli di motori con Express
+description: Scopri come integrare e utilizzare modelli di motori come Pug, Manubri ed EJS con Express.js per rendere le pagine HTML dinamiche in modo efficiente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Un motore _modello_ ti permette di utilizzare file di template statici nella tua applicazione. Al runtime, il modello del motore sostituisce le variabili
+in un modello di file con valori reali, e trasforma il modello in un file HTML inviato al client.
+Questo approccio rende più facile progettare una pagina HTML.
+
+Il [generatore di applicazioni Express](/en/starter/generator) utilizza [Pug](https://pugjs.org/api/getting-started.html) come predefinito, ma supporta anche [Handlebars](https://www.npmjs.com/package/handlebars), e [EJS](https://www.npmjs.com/package/ejs), tra gli altri.
+
+Per rendere i file dei modelli, imposta le seguenti [proprietà delle impostazioni dell'applicazione](/en/4x/api#app.set), nel file `app.js` predefinito creato dal generatore:
+
+- `views`, la directory dove si trovano i file del modello. Eg: `app.set('views', './views')`.
+  Questo valore predefinito è la directory `views` nella directory radice dell'applicazione.
+- `view engine`, il modello motore da usare. Ad esempio, per usare il motore modello Pug: `app.set('view engine', 'pug')`.
+
+Quindi installare il corrispondente pacchetto npm del motore del modello; per esempio per installare Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="allerta">
+Motori di modelli conformi ad espresso, come Pug esportano una funzione chiamata `__express(filePath, options, callback)`,
+che `res.render()` chiama per rendere il codice del modello.
+
+Alcuni modelli di motori non seguono questa convenzione. La libreria [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+segue questa convenzione mappando tutti i popolari motori di template Node.js, e quindi funziona perfettamente all'interno di Express.
+
+</Alert>
+
+Dopo che il motore di visualizzazione è stato impostato, non è necessario specificare il motore o caricare il modulo del motore modello nella tua app;
+Express carica il modulo internamente, per esempio:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Quindi, crea un file modello Pug chiamato `index.pug` nella directory `views`, con il seguente contenuto:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Crea un percorso per rendere il file `index.pug`. Se la proprietà `view engine` non è impostata,
+è necessario specificare l'estensione del file `view`. Altrimenti, puoi ometterlo.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando effettui una richiesta alla home page, il file `index.pug` verrà renderizzato come HTML.
+
+La cache del motore di visualizzazione non memorizza in cache il contenuto dell'output del modello, solo il modello sottostante. La vista è ancora ri-renderizzata con ogni richiesta anche quando la cache è accesa.
diff --git a/src/content/docs/it/5x/guide/writing-middleware.mdx b/src/content/docs/it/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..cea8997d8d
--- /dev/null
+++ b/src/content/docs/it/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Scrittura middleware per l'utilizzo in applicazioni Express
+description: Scopri come scrivere funzioni middleware personalizzate per le applicazioni Express.js, inclusi esempi e migliori pratiche per migliorare la gestione delle richieste e delle risposte.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Le funzioni _Middleware_ sono funzioni che hanno accesso al [request object](/en/5x/api#req) (`req`), il [response object](/en/5x/api#res) (`res`), e la funzione `next` nel ciclo request-response dell'applicazione. La funzione `next` è una funzione nel router Express che, quando invocato, esegue il middleware con successo al middleware corrente.
+
+Le funzioni Middleware possono eseguire le seguenti attività:
+
+- Esegue qualsiasi codice.
+- Effettuare modifiche alla richiesta e agli oggetti di risposta.
+- Terminare il ciclo richiesta-risposta.
+- Chiama il prossimo middleware nello stack.
+
+Se la funzione middleware corrente non termina il ciclo richiesta-risposta, deve chiamare `next()` per passare il controllo alla successiva funzione middleware. In caso contrario, la richiesta sarà sospesa.
+
+La figura seguente mostra gli elementi di una chiamata di una funzione middleware:
+
+![Elementi di una chiamata di una funzione middleware](/images/express-mw.png)
+
+A partire da Express 5, le funzioni middleware che restituiscono una Promise chiameranno `next(value)` quando rifiutano o lanciano un errore. `next` verrà chiamato con il valore rifiutato o con l'errore lanciato.
+
+## Esempio
+
+Ecco un esempio di una semplice applicazione "Hello World" Express.
+Il resto di questo articolo definirà e aggiungerà tre funzioni middleware all'applicazione:
+uno chiamato `myLogger` che stampa un semplice messaggio di registro, uno chiamato `requestTime` che
+visualizza il timestamp della richiesta HTTP e uno chiamato `validateCookies` che convalida i cookie in entrata.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Funzione middleware myLogger
+
+Ecco un semplice esempio di una funzione middleware chiamata "myLogger". Questa funzione solo stampa
+"LOGGED" quando una richiesta all'app passa attraverso di essa. La funzione middleware è assegnata a una variabile
+chiamata `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="allerta">
+
+Notare la chiamata sopra a `next()`. Chiamando questa funzione invoca la prossima funzione middleware nell'app
+. La funzione `next()` non è una parte del Node. s o Express API, ma è il terzo argomento
+che viene passato alla funzione middleware. La funzione `next()` potrebbe essere chiamata qualsiasi cosa,
+ma per convenzione è sempre chiamata "next". Per evitare confusione, utilizzare sempre questa convenzione.
+
+</Alert>
+
+Per caricare la funzione middleware, chiama `app.use()`, specificando la funzione middleware.
+Ad esempio, il seguente codice carica la funzione middleware `myLogger` prima del percorso al percorso root (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Ciao World!');
+});
+
+app.listen(3000);
+```
+
+Ogni volta che l'app riceve una richiesta, stampa il messaggio "LOGGED" al terminale.
+
+L'ordine di caricamento del middleware è importante: le funzioni middleware che vengono caricate per primo vengono eseguite per prime.
+
+Se il file `myLogger` viene caricato dopo il percorso verso il percorso root, la richiesta non lo raggiunge mai e l'applicazione non stampa "LOGGED", perché il gestore del percorso del percorso radice termina il ciclo richiesta-risposta.
+
+La funzione middleware `myLogger` semplicemente stampa un messaggio, poi passa la richiesta alla funzione middleware successiva nello stack chiamando la funzione `next()`.
+
+### Richiesta funzione Middleware
+
+Successivamente, creeremo una funzione middleware chiamata "requestTime" e aggiungeremo una proprietà chiamata `requestTime`
+all'oggetto richiesta.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+L'app utilizza ora la funzione middleware `requestTime`. Inoltre, la funzione callback del percorso del percorso del percorso di root utilizza la proprietà che la funzione middleware aggiunge a `req` (il oggetto richiesta).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.et('/', (req, res) => {
+  let responseText = 'Ciao Mondo!<br>';
+  responseText += `<small>Richiesto a: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Quando si effettua una richiesta alla root dell'app, l'app ora visualizza il timestamp della richiesta nel browser.
+
+### Middleware function validateCookies
+
+Infine, creeremo una funzione middleware che convalida i cookie in arrivo e invia una risposta 400 se i cookie non sono validi.
+
+Ecco una funzione di esempio che convalida i cookie con un servizio asincronico esterno.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Qui utilizziamo il middleware [`cookie-parser`](/en/resources/middleware/cookie-parser) per analizzare i cookie in arrivo fuori dall'oggetto `req` e passarli alla nostra funzione `cookieValidator`. Il middleware `validateCookies` restituisce una Promessa che al momento del rifiuto attiverà automaticamente il nostro gestore di errori.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="allerta">
+
+Nota come `next()` viene chiamato dopo `await cookieValidator(req.cookies)`. Questo assicura che se
+`cookieValidator` si risolve, il prossimo middleware nello stack verrà chiamato. Se passi qualcosa
+alla funzione `next()` (tranne la stringa `'route'` o `'router'`), Espresso considera l'attuale richiesta
+come un errore e salterà tutte le rimanenti funzioni di routing e middleware
+.
+
+</Alert>
+
+Poiché hai accesso all'oggetto richiesta, all'oggetto risposta, alla funzione middleware successiva nello stack, e all'intero Node. s API, le possibilità con funzioni middleware sono infinite.
+
+Per ulteriori informazioni su middleware Express, consultare: [Using Express middleware](/en/guide/using-middleware).
+
+## Middleware configurabile
+
+Se hai bisogno del tuo middleware per essere configurabile, esporta una funzione che accetta un oggetto di opzioni o altri parametri, che, poi, restituisce l'implementazione middleware in base ai parametri di input.
+
+File: `my-middleware.js`
+
+```js
+modulo.xports = function (options) {
+  return function (req, res, next) {
+    // Implementa la funzione middleware basata sulle opzioni object
+    next();
+  };
+};
+```
+
+Il middleware può ora essere utilizzato come mostrato di seguito.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Fare riferimento a [cookie-session](https://github.com/expressjs/cookie-session) e [compression](https://github.com/expressjs/compression) per esempi di middleware configurabile.
diff --git a/src/content/docs/it/5x/starter/basic-routing.mdx b/src/content/docs/it/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..f9777989fc
--- /dev/null
+++ b/src/content/docs/it/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Instradamento base
+description: Impara i fondamenti del routing nelle applicazioni Express.js, tra cui come definire i percorsi, gestire i metodi HTTP e creare gestori del percorso per il tuo server web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ si riferisce alla determinazione di come un'applicazione risponde a una richiesta di client a un determinato endpoint, che è un URI (o percorso) e un metodo di richiesta HTTP specifico (GET, POST, e così via).
+
+Ogni percorso può avere una o più funzioni di gestore, che vengono eseguite quando il percorso è abbinato.
+
+La definizione del percorso assume la seguente struttura:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Dove:
+
+- `app` è un'istanza di `express`.
+- `METHOD` è un [metodo di richiesta HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in minuscolo.
+- `PATH` è un percorso sul server.
+- `HANDLER` è la funzione eseguita quando il percorso è corrispondente.
+
+<Alert type="allerta">
+
+Questo tutorial presuppone che venga creata un'istanza di `express` chiamata `app` e che il server sia in esecuzione
+. Se non hai familiarità con la creazione di un'app e l'avvio, vedi l'esempio Ciao mondo
+.
+
+</Alert>
+
+Gli esempi che seguono illustrano la definizione di itinerari semplici.
+
+Rispondi con `Ciao Mondo!` nella homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Rispondi a una richiesta POST sul percorso radice (`/`), la home page dell'applicazione:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Rispondi a una richiesta PUT al percorso `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Rispondi a una richiesta DELETE al percorso `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+Per maggiori dettagli sul routing, consulta la [guida di routing](/en/guide/routing).
diff --git a/src/content/docs/it/5x/starter/examples.mdx b/src/content/docs/it/5x/starter/examples.mdx
new file mode 100644
index 0000000000..54c2acb2e4
--- /dev/null
+++ b/src/content/docs/it/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Esempi espressi
+description: Esplora una raccolta di esempi di applicazioni Express.js che coprono vari casi di utilizzo, integrazioni e configurazioni avanzate per aiutarti a imparare e costruire i tuoi progetti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Questa pagina contiene un elenco di esempi utilizzando Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Autenticazione con login e password
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - Negoziazione di contenuti HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Lavorare con sessioni basate su cookie
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Lavorare con i cookie
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Trasferimento dei file al client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Lavorare con il template JavaScript incorporato (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Creazione pagine di errore
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Lavorare con middleware errore
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Gestore semplice della richiesta
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown come modello motore
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Lavorare con più router Express
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - controller in stile MVC
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Monitoraggio delle attività degli utenti online con pacchetti `online` e `redis`
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Lavorare con i parametri del percorso
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Operazioni HTTP multiple sulla stessa risorsa
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organizzare i percorsi utilizzando una mappa
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Lavorare con il middleware del percorso
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizzare percorsi per ogni risorsa
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Cerca API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - sessioni utente
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Servire file statici
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Lavorare con gli host virtuali
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Visualizzazione dinamica
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Salvataggio dei dati nell'oggetto richiesta tra le chiamate middleware
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Servizio API semplice
+
+## Esempi aggiuntivi
+
+Questi sono alcuni esempi aggiuntivi con integrazioni più estese.
+
+<Alert type="avviso">
+
+Queste informazioni si riferiscono a siti, prodotti o moduli di terze parti che non sono mantenuti dal team
+Expressjs. L'elenco qui non costituisce un'approvazione o una raccomandazione da parte del team di progetto
+Expressjs.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app con Express e Next.js utilizzando [Prisma](https://www.npmjs.com/package/prisma) come ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/it/5x/starter/faq.md b/src/content/docs/it/5x/starter/faq.md
new file mode 100644
index 0000000000..6e30b48782
--- /dev/null
+++ b/src/content/docs/it/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Trova le risposte alle domande più frequenti su Express.js, inclusi argomenti sulla struttura delle applicazioni, modelli, autenticazione, modelli motori, gestione degli errori e altro ancora.
+---
+
+## Come dovrei strutturare la mia applicazione?
+
+Non esiste una risposta definitiva a questa domanda. La risposta dipende da
+sulla scala della tua applicazione e del team che è coinvolto. Per essere il più flessibile possibile
+, Express non fa ipotesi in termini di struttura.
+
+Le rotte e altre logiche specifiche per le applicazioni possono vivere in tutti i file
+che desideri, in qualsiasi struttura di directory che preferisci. Visualizza i seguenti esempi di ispirazione
+:
+
+- [Elenco delle rotte](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mappa del percorso](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Inoltre, ci sono estensioni di terze parti per Express, che semplificano alcuni di questi modelli:
+
+- [Instradamento delle risorse](https://github.com/expressjs/express-resource)
+
+## Come definisco i modelli?
+
+Express non ha alcuna nozione di banca dati. Questo concetto è
+lasciato fino a moduli Nodo di terze parti, consentendo di
+interfaccia con quasi tutti i database.
+
+Vedi [LoopBack](http://loopback.io) per un framework basato su Espresso che è centrato sui modelli.
+
+## Come posso autenticare gli utenti?
+
+L'autenticazione è un'altra area opinionata in cui Express non si avventura
+. È possibile utilizzare qualsiasi schema di autenticazione desiderato.
+Per un semplice schema username / password, vedere [questo esempio](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quali modelli di motori supporta Express?
+
+Express supporta qualsiasi modello di motore conforme alla firma `(percorso, locale, callback)`.
+Per normalizzare i modelli di interfacce motore e caching, vedere il progetto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+per il supporto. Motori modello non elencati potrebbero ancora supportare la firma Express.
+
+Per ulteriori informazioni, vedere [Utilizzo di modelli di motori con Express](/en/guide/using-template-engines).
+
+## Come posso gestire 404 risposte?
+
+In Express, 404 risposte non sono il risultato di un errore, quindi
+il middleware del gestore dell'errore non le catturerà. Questo comportamento è
+perché una risposta 404 indica semplicemente l'assenza di lavoro supplementare da fare;
+in altre parole, Express ha eseguito tutte le funzioni e i percorsi del middleware,
+e ha trovato che nessuno di loro ha risposto. Tutto quello che devi fare
+è aggiungere una funzione middleware nella parte inferiore dello stack (sotto tutte le altre funzioni)
+per gestire una risposta 404:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Aggiungi percorsi dinamicamente al runtime su un'istanza di `express.Router()`
+in modo che i percorsi non siano sostituiti da una funzione middleware.
+
+## Come faccio a configurare un gestore di errori?
+
+Definisci middleware per la gestione degli errori allo stesso modo di altri middleware,
+tranne con quattro argomenti invece di tre; specificatamente con la firma `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Per ulteriori informazioni, vedere [Gestione degli errori](/en/guide/error-handling).
+
+## Come faccio a rendere semplice HTML?
+
+Non lo fate! Non c'è bisogno di "render" HTML con la funzione `res.render()`.
+Se hai un file specifico, usa la funzione `res.sendFile()`.
+Se stai servendo molti asset da una directory, usa la funzione middleware `express.static()`
+.
+
+## Quale versione di Node.js richiede Express?
+
+- [Express 4.x](/en/4x/api) richiede Node.js 0.10 o superiore.
+- [Express 5.x](/en/5x/api) richiede Node.js 18 o superiore.
diff --git a/src/content/docs/it/5x/starter/generator.mdx b/src/content/docs/it/5x/starter/generator.mdx
new file mode 100644
index 0000000000..1b0eeaa660
--- /dev/null
+++ b/src/content/docs/it/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Generatore di applicazioni espresso
+description: Scopri come utilizzare lo strumento del generatore di applicazioni Express per creare rapidamente uno scheletro per le applicazioni Express.js, semplificando la configurazione e la configurazione.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Utilizzare lo strumento generatore di applicazioni, `express-generator`, per creare rapidamente uno scheletro di applicazione.
+
+È possibile eseguire il generatore di applicazioni con il comando `npx` (disponibile in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+Per le versioni precedenti di Node, installare il generatore di applicazioni come pacchetto globale npm e quindi lanciarlo:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Visualizza le opzioni del comando con l'opzione `-h`:
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opzioni:
+
+    -h, --help informazioni di utilizzo dell'output
+        --version output il numero di versione
+    -e, --ejs aggiungi il supporto del motore ejs
+        --hbs aggiungi il supporto del motore del manubrio
+        --pug aggiungi il supporto del motore del pug
+    -H, --hogan aggiungi hogan. s supporto motore
+        --no-view genera senza motore di visualizzazione
+    -v, --view <engine> aggiungi vista <engine> supporto (ejs<unk> hbs<unk> hjs<unk> jade<unk> pug<unk> twig<unk> vash) (valori predefiniti per jade)
+    -c, --css <engine>  aggiungi il foglio di stile <engine> supporto (less<unk> stylus<unk> compass<unk> sass) (valori predefiniti per css normali)
+        --git add . itignore
+    -f, --force force sulla directory non vuota
+```
+
+Ad esempio, il seguente crea un'app Express chiamata _myapp_. L'app verrà creata in una cartella chiamata _myapp_ nella directory di lavoro corrente e il motore di visualizzazione sarà impostato su <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app. s
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/route
+   create : myapp/routes/index. s
+   create : myapp/routes/users. s
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   create : myapp/views
+   create : myapp/views/index. ug
+   create : myapp/views/layout.pug
+   create : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Quindi installare dipendenze:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+Su MacOS o Linux, esegui l'app con questo comando:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Su Windows Command Prompt, utilizzare questo comando:
+
+```bash
+> imposta DEBUG=myapp:* & npm start
+```
+
+Su Windows PowerShell, utilizzare questo comando:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Quindi, caricare `http://localhost:3000/` nel tuo browser per accedere all'app.
+
+L'app generata ha la seguente struttura di directory:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+La struttura delle app creata dal generatore è solo uno dei tanti modi per strutturare le app Express.
+Sentitevi liberi di utilizzare questa struttura o modificarla per soddisfare al meglio le vostre esigenze.
+
+</Alert>
diff --git a/src/content/docs/it/5x/starter/hello-world.mdx b/src/content/docs/it/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..4b4df6bcfe
--- /dev/null
+++ b/src/content/docs/it/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Ciao esempio mondiale
+description: Inizia con Express.js costruendo una semplice applicazione 'Ciao Mondo', dimostrando la configurazione di base e la creazione di server per i principianti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Incorporato qui sotto è essenzialmente l'app Express più semplice che puoi creare. Si tratta di un singolo file app
+&mdash; _non_ quello che si otterrebbe se si utilizza il [Express generator](/en/starter/generator), che
+crea il ponteggio per un'app completa con numerosi file JavaScript, modelli Jade e sottodirectory
+per vari scopi.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+Questa app avvia un server e ascolta la porta 3000 per le connessioni. L'app risponde con "Ciao Mondo!" per le richieste
+all'URL radice (`/`) o _route_. Per ogni altro percorso, risponderà con un **404 non trovato**.
+
+## Esecuzione Localmente
+
+Crea prima una directory chiamata `myapp`, cambiala ed esegui `npm init`. Quindi, installa `express` come dipendenza, secondo la [guida all'installazione](/en/starter/installing).
+
+Nella directory `myapp`, crea un file chiamato `app.js` e copia il codice dall'esempio qui sopra.
+
+<Alert type="allerta">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Eseguire l'app con il seguente comando:
+
+```bash
+$ node app.js
+```
+
+Quindi, caricare `http://localhost:3000/` in un browser per vedere l'output.
diff --git a/src/content/docs/it/5x/starter/installing.mdx b/src/content/docs/it/5x/starter/installing.mdx
new file mode 100644
index 0000000000..f1438460a6
--- /dev/null
+++ b/src/content/docs/it/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installazione
+description: Scopri come installare Express.js nel tuo ambiente Node.js, inclusa la creazione della directory del progetto e la gestione delle dipendenze con npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Prima di iniziare, assicurati di avere [Node.js](https://nodejs.org/) 18 o superiore installato. Quindi, creare una directory per la vostra applicazione e navigare in essa.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Usa il comando `npm init` per creare un file `package.json` per la tua applicazione.
+Per maggiori informazioni sul funzionamento di `package.json`, vedere [Specifiche della gestione di npm.json](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Questo comando ti richiede un certo numero di cose, come il nome e la versione della tua applicazione.
+Per ora, puoi semplicemente premere RETURN per accettare i valori predefiniti per la maggior parte di essi, con la seguente eccezione:
+
+```
+punto di ingresso: (index.js)
+```
+
+Inserisci `app.js`, o qualsiasi cosa desideri che sia il nome del file principale. Se vuoi che sia `index.js`, premi RETURN per accettare il nome del file predefinito suggerito.
+
+Ora, installa Express nella directory `myapp` e salvalo nella lista delle dipendenze. Per esempio:
+
+```bash
+npm install express
+```
+
+Per installare Express temporaneamente e non aggiungerlo alla lista delle dipendenze:
+
+```bash
+npm installa express --no-save
+```
diff --git a/src/content/docs/it/5x/starter/static-files.mdx b/src/content/docs/it/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..89d90034cf
--- /dev/null
+++ b/src/content/docs/it/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servire file statici in Express
+description: Comprendi come servire file statici come immagini, CSS e JavaScript nelle applicazioni Express.js utilizzando il middleware 'static' integrato.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Per servire file statici come immagini, file CSS e file JavaScript, utilizzare la funzione middleware integrata `express.static` in Express.
+
+La firma della funzione è:
+
+```js
+express.static(root, [options]);
+```
+
+L'argomento `root` specifica la directory radice da cui servire le risorse statiche.
+Per ulteriori informazioni sull'argomento `options`, vedere [express.static](/en/5x/api#express.static).
+
+Per esempio, utilizzare il seguente codice per servire immagini, file CSS e file JavaScript in una directory chiamata `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Ora, puoi caricare i file che sono nella directory `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express cerca i file relativi alla directory statica, quindi il nome della directory statica
+non fa parte dell'URL.
+
+</Alert>
+
+Per utilizzare più directory di asset statici, chiama la funzione middleware `express.static`:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express cerca i file nell'ordine in cui si impostano le directory statiche con la funzione middleware `express.static`.
+
+<Alert type="info">
+
+Per ottenere risultati ottimali, utilizza un proxy
+inverso cache per migliorare le prestazioni di
+che servono risorse statiche.
+
+</Alert>
+
+Per creare un prefisso di percorso virtuale (dove il percorso non esiste effettivamente nel file system) per i file serviti dal `express. funzione tatic`, [specify a mount path](/en/5x/api#app.use) per la directory statica, come mostrato di seguito:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Ora puoi caricare i file che sono nella directory `public` dal prefisso del percorso `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+Tuttavia, il percorso che fornisci alla funzione `express.static` è relativo alla directory da cui avvii il processo `node`. Se si esegue l'app express da un'altra directory, è più sicuro utilizzare il percorso assoluto della directory che si desidera servire:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public'));
+```
+
+Per maggiori dettagli sulla funzione `serve-static` e sulle sue opzioni, vedere [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/ja/4x/advanced/developing-template-engines.md b/src/content/docs/ja/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..34a00b66da
--- /dev/null
+++ b/src/content/docs/ja/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Express 用テンプレートエンジンの開発
+description: App.engine() を使用して Express.js 用のカスタムテンプレートエンジンを開発する方法と、独自のテンプレートレンダリングロジックの作成と統合の例をご覧ください。
+---
+
+`app.engine(ext, callback)`メソッドを使用して、独自のテンプレートエンジンを作成します。 `ext`はファイル拡張子を指し、`callback`はテンプレートエンジン関数です。 は、次の項目をパラメータとして受け付けます。ファイルの場所、options オブジェクト、およびコールバック関数です。
+
+以下のコードは、`.ntl`ファイルをレンダリングするための非常に単純なテンプレートエンジンを実装した例です。
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+アプリは `.ntl` ファイルをレンダリングできるようになります。 `views`ディレクトリに`index.ntl`という名前のファイルを作成します。
+
+```pug
+#title#
+#message#
+```
+
+次に、アプリに次のルートを作成します。
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+ホームページへのリクエストを行うと、`index.ntl`はHTMLとしてレンダリングされます。
diff --git a/src/content/docs/ja/4x/guide/behind-proxies.mdx b/src/content/docs/ja/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..a70ee8bd1d
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/behind-proxies.mdx
@@ -0,0 +1,103 @@
+---
+title: プロキシの背後にあるエクスプレス
+description: クライアントの IP アドレスを処理するトラストプロキシ設定を使用するなど、リバース・プロキシの背後で正しく動作するように Express.js アプリケーションを構成する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+リバースプロキシの背後で Express アプリケーションを実行する場合、Express API の中には予想以外の値が返されるものがあります。 これを調整するために `trust proxy` アプリケーションの設定は、Express API のリバースプロキシによって提供された情報を公開するために使用することができます。 最も一般的な問題は、クライアントのIPアドレスを公開するAPIで、リバースプロキシの内部IPアドレスが表示される可能性があります。
+
+<Alert type="情報">
+
+`trust proxy` の設定では、
+リバースプロキシの正確な設定を理解することが重要です。 この設定はリクエストで提供された値を信頼するためです Express での設定の組み合わせが
+リバースプロキシの動作と一致することが重要です。
+
+</Alert>
+
+`trust proxy`を設定するアプリケーションは、次の表に示されている値のいずれかを設定することができます。
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th /><th>値</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+`true` の場合、クライアントの IP アドレスは `X-Forwarded-For` ヘッダーの中の一番左のエントリとして理解されます。
+
+`false` の場合、アプリはクライアントに直接向いていると理解され、クライアントの IP アドレスは `req.socket.remoteAddress` に由来します。 これはデフォルトの設定です。
+
+<Alert type="警告">
+`true` に設定する場合、信頼されている最後のリバースプロキシが以下のすべての HTTP ヘッダを削除/上書きすることが重要です: `X-Forwarded-For` 。 `X-Forwarded-Host` と `X-Forwarded-Proto` があれば、クライアントが何らかの値を提供できるかもしれません。
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IPアドレス</td>
+<td markdown="1">
+リバースプロキシとして信頼する IP アドレス、サブネット、または IP アドレスとサブネットの配列。 次のリストに、事前に設定されたサブネット名が表示されます。
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniqueloc - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+IPアドレスは以下のいずれかの方法で設定できます。
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+指定された場合、IPアドレスまたはサブネットはアドレス決定プロセスから除外されます。 アプリケーションサーバーに最も近い信頼できないIPアドレスは、クライアントのIPアドレスとして決定されます。 これは `req.socket.remoteAddress` が信頼されているかどうかをチェックすることで動作します。 その場合、`X-Forwarded-For`内の各アドレスは、最初の信頼されていないアドレスまで右から左にチェックされます。
+
+</td>
+    </tr>
+    <tr>
+      <td>数字</td>
+<td markdown="1">
+Expressアプリケーションから離れたホップの最大数のアドレスを使用してください。 `req.socket.remoteAddress` は最初のホップで、残りは右から左への `X-Forwarded-For` ヘッダで探します。 `0`の値は、最初に信頼されていないアドレスが`req.socket.remoteAddress`であることを意味します。つまり、リバースプロキシは存在しません。
+
+<Alert type="警告">
+この設定を使用する場合は、複数がないことを確認することが重要です。 Expressアプリケーションへの異なる長さのパスは、クライアントが設定されたホップ数よりも少なくすることができるようになります。 それ以外の場合は、クライアントが何らかの価値を提供することができます。
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>関数</td>
+<td markdown="1">
+カスタムトラスト実装。
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+`trust proxy` を有効にすると、次のような影響を与えます。
+
+<ul>
+  <li markdown="1">
+    [req.hostname](/en/api#req.hostname) の値は、 `X-Forwarded-Host`
+    ヘッダで設定された値から取得されます。 クライアントやプロキシによって設定できます
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` はリバースプロキシによって設定することで、アプリが https`か`http\`
+    か無効な名前かをアプリに伝えることができます。 この値は [req.protocol](/en/api#req.protocol)
+    で反映されます。
+  </li>
+  <li markdown="1">
+    [req.ip](/en/api#req.ip) と [req.ips](/en/api#req.ips) の値は、 ソケットアドレスと
+    `X-Forwarded-For` ヘッダーに基づいて入力されます。 最初の信頼されていないアドレスから始めます
+  </li>
+</ul>
+
+`trust proxy` は、 [proxy-addr](https://www.npmjs.com/package/proxy-addr) パッケージを使用して実装されています。 詳細については、そのドキュメントを参照してください。
diff --git a/src/content/docs/ja/4x/guide/debugging.mdx b/src/content/docs/ja/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..80cd35328f
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Expressのデバッグ
+description: DEBUG環境変数を設定して、Express.jsアプリケーションでデバッグログを有効にして使用する方法を学び、トラブルシューティングを強化します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express で使用されるすべての内部ログを表示するには、アプリを起動するときに `DEBUG` 環境変数を
+`express:*` に設定します。
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Windows では、対応するコマンドを使用します。
+
+```bash
+> $env:DEBUG = "express:*"; ノードインデックス.js
+```
+
+[express generator](/en/starter/generator) で生成されたデフォルトのアプリでこのコマンドを実行すると、以下の出力が出力されます。
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+アプリへのリクエストが行われると、Express コードで指定されたログが表示されます。
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+ルータの実装からのみログを見るには、`DEBUG`の値を`express:router`に設定します。 同様に、アプリケーションの実装からのログのみを見るには、`DEBUG`の値を`express:application`などに設定します。
+
+## `express` で生成されたアプリケーション
+
+`express`コマンドによって生成されたアプリケーションは、`debug`モジュールを使用し、デバッグ名前空間はアプリケーションの名前をスコープします。
+
+例えば、 `$ express sample-app` を使用してアプリを生成した場合、次のコマンドでデバッグ文を有効にできます。
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+カンマ区切りの名前のリストを割り当てることで、複数のデバッグ名前空間を指定できます:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## 高度なオプション
+
+Node.js を介して実行する場合、デバッグログの動作を変更するいくつかの環境変数を設定できます。
+
+| 名前                | 目的                                                   |
+| ------------------- | ------------------------------------------------------ |
+| `DEBUG`             | 特定のデバッグ名前空間を有効/無効にします。            |
+| `DEBUG_COLORS`      | デバッグ出力で色を使用するかどうか。                   |
+| `DEBUG_DEPTH`       | 物体検査の深さ。                                       |
+| `DEBUG_FD`          | デバッグ出力を書き込むファイル記述子。                 |
+| `DEBUG_SHOW_HIDDEN` | 検査対象オブジェクトに非表示のプロパティを表示します。 |
+
+<Alert type="情報">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters.
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) の完全な
+リストについては Node.js のドキュメントを参照してください。
+
+</Alert>
diff --git a/src/content/docs/ja/4x/guide/error-handling.mdx b/src/content/docs/ja/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..4a19e9fcc1
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: エラー処理
+description: Express.jsが同期コードと非同期コードのエラーを処理する方法を理解し、アプリケーション用のカスタムエラー処理ミドルウェアを実装する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+*Error Handling*は、
+が同期と非同期の両方で発生するエラーをExpress がキャッチして処理する方法を指します。 Expressにはデフォルトのエラー
+ハンドラが付属しているので、始めるために自分で書く必要はありません。
+
+## キャッチエラー
+
+Express がルートハンドラと
+ミドルウェアの実行中に発生するすべてのエラーをキャッチすることが重要です。
+
+ルートハンドラとミドルウェア
+内の同期コードで発生するエラーは追加の作業を必要としません。 同期コードがエラーをスローする場合、Expressは
+キャッチして処理します。 例:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express はこれを独自にキャッチします。
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. 例:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Express 5以降、Promise
+を返すルートハンドラとミドルウェアは、エラーの拒否またはスロー時に自動的に`next(value)`を呼び出します。
+例:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. 拒否された値が指定されていない場合、 `next`
+はExpress ルータが提供するデフォルトの Error オブジェクトで呼び出されます。
+
+`next()`関数に何かを渡した場合（`'route'`を除く）。
+Expressは現在のリクエストをエラーとみなし、
+残っている非エラー処理ルーティングとミドルウェア関数をスキップします。
+
+シーケンス内のコールバックがデータを提供しない場合、エラーのみを提供する場合は、次のように
+このコードを簡素化できます:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. エラーがなければ、2番目の
+ハンドラが実行されます。そうでなければ、Expressはエラーをキャッチして処理します。
+
+route handler または
+ミドルウェアによって呼び出された非同期コードで発生するエラーをキャッチし、処理のために Express に渡す必要があります。 例:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+上の例では、
+非同期コードのエラーをキャッチし、Expressに渡すために`try...catch`ブロックを使用しています。 `try...catch`
+ブロックが省略された場合、Expressは同期
+ハンドラコードの一部ではないため、エラーをキャッチしません。
+
+プロミスを返す関数
+を使うと、`try...catch` のオーバーヘッドを避けることができます。 例:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+また、非同期コードを些細なものに減らすことで、同期エラー
+のキャッチに依存するハンドラのチェーンを使用することもできます。 例:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+上の例では、`readFile`
+呼び出しからいくつかの些細な文があります。 `readFile` でエラーが発生した場合、エラーは Express に渡されます。 それ以外の場合は、
+チェーン内の次のハンドラ
+で同期エラー処理の世界にすばやく戻ります。 そして、上記の例はデータを処理しようとします。 これが失敗した場合、
+同期エラーハンドラはそれをキャッチします。 `readFile`コールバックの
+内でこの処理を行った場合、アプリケーションが終了する可能性があり、Expressエラー
+ハンドラは実行されません。
+
+どちらの方法を使っても、Expressエラーハンドラを呼び出し、
+アプリケーションを存続させたい場合は Express がエラーを受け取ることを確認する必要があります。
+
+## デフォルトのエラーハンドラです
+
+Expressには、アプリで発生する可能性のあるエラーを処理する内蔵のエラーハンドラが付属しています。 このデフォルトのエラー処理ミドルウェア関数は、ミドルウェア関数スタックの末尾に追加されます。
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. スタックトレースは本番環境に
+含まれていません。
+
+<Alert type="情報">
+
+プロダクションモードでアプリを実行するには、環境変数 `NODE_ENV` を `production` に設定します。
+
+</Alert>
+
+エラーが書き込まれると、次の情報が
+応答に追加されます:
+
+- `res.statusCode` は `err.status` (または `err.statusCode`)から設定されます。
+  の場合、この値が4xxまたは5xxの範囲外の場合、500に設定されます。
+- `res.statusMessage` はステータスコードに従って設定されます。
+- 本文は、プロダクション
+  環境ではステータスコードメッセージのHTMLになります。そうでなければ、`err.stack`になります。
+- `err.headers` オブジェクトで指定されたヘッダー。
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+デフォルトのエラーハンドラは、コード内でエラー
+を複数回呼び出して`next()`を呼び出すとトリガされることに注意してください。 カスタムエラー処理ミドルウェアが導入されたとしてもです
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## エラーハンドラの書き込み
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. 例:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+エラー処理ミドルウェアは、他の `app.use()`とルート呼び出しの後に最後に定義します。例:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+ミドルウェア関数内からのレスポンスは、HTMLエラーページ、シンプルなメッセージ、JSON文字列など、あらゆる形式で使用できます。
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. 例えば、`XHR`とそれ以外のリクエストに対してエラーハンドラ
+を定義するには、次のようにします。
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+この例では、一般的な`logErrors`はリクエストと
+エラー情報を`stderr`に書き込むことができます。
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+この例でも、`clientErrorHandler`は以下のように定義されています。この場合、エラーは明示的に次のエラーに渡されます。
+
+エラー処理関数で「next」を呼び出さない場合、レスポンスの書き込み(および終了)を行う責任があることに注意してください。 そうでなければ、これらのリクエストは「ハング」し、ガベージコレクションの対象になりません。
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+"catch-all" `errorHandler` 関数を以下のように実装します(例えば：
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+複数のコールバック関数を持つルートハンドラがある場合は、`route` パラメータを使用して次のルートハンドラにスキップできます。 例:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+この例では、 `getPaidContent` ハンドラはスキップされますが、 `/a_route_background_paywall` の `app` に残っているハンドラは引き続き実行されます。
+
+<Alert type="情報">
+
+`next()`と`next(err)`への呼び出しは、現在のハンドラが完了している状態を示します。
+`next(err)`は、上記のように
+に設定されているものを除いて、チェーン内の残りのハンドラをすべてスキップします。
+
+</Alert>
diff --git a/src/content/docs/ja/4x/guide/overriding-express-api.md b/src/content/docs/ja/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..324a52bf6d
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Express API のオーバーライド
+description: リクエストとレスポンスオブジェクトのメソッドとプロパティをプロトタイプを使用してオーバーライドすることで、Express.js API をカスタマイズして拡張する方法をご覧ください。
+---
+
+Express API は、リクエストオブジェクトとレスポンスオブジェクトのさまざまなメソッドとプロパティで構成されています。 これらはプロトタイプによって継承されます。 Express API には 2 つの拡張ポイントがあります。
+
+1. `express.request` と `express.response` のグローバルプロトタイプ。
+2. `app.request`と`app.response`でアプリ固有のプロトタイプ。
+
+グローバルプロトタイプを変更すると、読み込まれたすべてのExpressアプリが同じプロセスで影響を受けます。 必要に応じて、新しいアプリを作成した後にアプリ固有のプロトタイプを変更するだけで、アプリ固有の変更を行うことができます。
+
+## メソッド
+
+カスタム関数を割り当てることで、既存のメソッドの署名と振る舞いを独自のメソッドで上書きできます。
+
+以下は、 [res.sendStatus](/en/4x/api#res.sendStatus) の挙動を上書きした例です。
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+上記の実装は `res.sendStatus` の元の署名を完全に変更します。 ステータスコード、エンコーディングタイプ、およびメッセージをクライアントに送信できるようになりました。
+
+オーバーライドされたメソッドは次のように使用できます。
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## プロパティー
+
+Express API のプロパティは以下のいずれかです。
+
+1. 割り当てられたプロパティ (例: `req.baseUrl`, `req.originalUrl`)
+2. getters (例: `req.secure`, `req.ip`) として定義されています。
+
+category 1 のプロパティは、現在のリクエスト-レスポンスサイクルのコンテキストで `request` と `response` オブジェクトに動的に割り当てられます。 彼らの行動はオーバーライドできない
+
+カテゴリ2のプロパティはExpress API拡張機能APIを使用して上書きすることができます。
+
+次のコードは `req.ip` の値をどのように派生するかを書き換えます。 これで、`Client-IP` リクエストヘッダの値を返すだけです。
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## プロトタイプ
+
+Express API を提供するためには、Express に渡された request/response オブジェクトを (`app(req) 経由で) 提供します。 res)`は同じプロトタイプチェーンから継承する必要があります。 デフォルトでは、リクエストの `http.IncomingRequest.prototype` と、レスポンスの `http.ServerResponse.prototype` です。
+
+必要がない限り、これはアプリケーションレベルでのみ行うことを推奨します。 また、使用されているプロトタイプは、可能な限りデフォルトのプロトタイプに近い機能を備えていることに注意してください。
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/ja/4x/guide/routing.mdx b/src/content/docs/ja/4x/guide/routing.mdx
new file mode 100644
index 0000000000..f2a8ebe75d
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: ルーティング
+description: Express.jsアプリケーションでルートを定義して使用する方法を学びます。ルートメソッド、ルートパス、パラメータ、モジュラールーティングにルーターを使用する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ とは、アプリケーションのエンドポイント(URI)がクライアントリクエストに対してどのように応答するかを指します。
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+HTTPメソッドに対応するExpress `app` オブジェクトのメソッドを使用してルーティングを定義します。
+のように、`app。 POST リクエストを処理する GET リクエストと `app.post\` を処理します。 完全なリストについては、
+[app.METHOD](/en/5x/api#app.METHOD) を参照してください。 [app.all()](/en/5x/api#app.all)を使用して、すべてのHTTPメソッドと[app]を処理することもできます。 se()](/en/5x/api#app.use) to
+コールバック関数としてミドルウェアを指定する (詳細は [Using middleware](/en/guide/using-middleware) を参照)。
+
+これらのルーティングメソッドは、アプリケーションが指定されたルート (エンドポイント) と HTTP メソッドへのリクエストを受け取ったときに呼び出されるコールバック関数 ("handler functions" と呼ばれることもあります) を指定します。 言い換えれば、アプリケーションは指定されたルートとメソッドに一致するリクエストを「リッスン」します。 マッチを検出すると、指定されたコールバック関数を呼び出します。
+
+実際、ルーティングメソッドは引数として複数のコールバック関数を持つことができます。
+複数のコールバック関数を使用。 コールバック関数に `next` を引数として渡し、関数の本体内で `next()` を呼び出して、次のコールバックに
+を渡すことが重要です。
+
+以下のコードは、非常に基本的なルートの例です。
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## ルートメソッド
+
+routeメソッドはHTTPメソッドのいずれかから派生し、`express` クラスのインスタンスに追加されます。
+
+以下のコードは、`GET` と `POST` メソッドを定義したルートの例です。
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Expressは、すべてのHTTPリクエストメソッドに対応するメソッドをサポートしています: `get`、`post`など。
+完全なリストについては、 [app.METHOD](/en/5x/api#app.METHOD) を参照してください。
+
+特別なルーティングメソッド`app.all()`があり、\_all_HTTPリクエストメソッドのパスにミドルウェア関数をロードするために使用されます。 例えば、`GET`を使用しているかどうかに関わらず、ルート`"/secret"へのリクエストに対して以下のハンドラが実行されます。 `POST`、`PUT`、`DELETE\`、または[http module](https://nodejs.org/api/http.html#http_http_methods)でサポートされている他のHTTPリクエストメソッド。
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## ルートパス
+
+ルートパスはリクエストメソッドと組み合わせて、リクエストを作成できるエンドポイントを定義します。 ルートパスは文字列、文字列パターン、または正規表現であることができます。
+
+<Alert type="アラート">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="アラート">
+
+式4では、`$`のような正規表現は`\`でエスケープする必要があります。
+
+</Alert>
+
+<Alert type="情報">
+
+Express は [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) をルート
+パスに一致させるために使用します。ルート パスの定義におけるすべての可能性については、path-to-regexp ドキュメントを参照してください。
+[Express Playground Router](https://bjohansebas.github.io/playground-router/)は基本的なExpressルートを
+テストするための便利なツールですが、パターンマッチングはサポートされていません。
+
+</Alert>
+
+<Alert type="warning">クエリ文字列はルートパスの一部ではありません。</Alert>
+
+### 文字列に基づく経路パス
+
+このルートパスはルートルートのリクエストと一致します。
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+このルートパスは `/about` へのリクエストと一致します。
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+このルートパスは `/random.text` へのリクエストと一致します。
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### 文字列パターンに基づく経路パス
+
+<Alert type="アラート">
+
+Express 5の文字列パターンは動作しなくなりました。 詳細については、Migration
+guideを参照してください。
+
+</Alert>
+
+このルートパスは `acd` と `abcd` に一致します。
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+このルートパスは `abcd`、`abbcd`、`abbcd`などにマッチします。
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+このルートパスは `abcd`、`abxcd`、`abrandoMcd`、`ab123cd`などにマッチします。
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+このルートパスは `/abe` と `/abcde` に一致します。
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### 正規表現に基づく経路パス
+
+このルートパスは "a" と一致します。
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+このルートは`蝶々`と`トンボ`にマッチしますが、`蝶々`、`トンボフライマン`などにはマッチしません。
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## ルートパラメータ
+
+ルートパラメータは、URL 内の位置で指定された値をキャプチャするために使用される名前付きの URL セグメントです。 取得した値は `req.params` オブジェクト内に入力され、パス内でそれぞれのキーとして指定されたrouteパラメータの名前が入力されます。
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+ルートパラメータを使用してルートを定義するには、以下のようにルートのパスにルートパラメータを指定します。
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="アラート">
+
+ルートパラメータの名前は、"単語文字" ([A-Za-z0-9_] )で構成されている必要があります。
+
+</Alert>
+
+ハイフン(`-`)とドット(`.`)は文字通り解釈されるので、ルートパラメータとともに便利な目的で使うことができます。
+
+```
+ルートパス: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+ルートパス: /platae/:genus.:species
+リクエスト URL: http://localhost:3000/platae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="アラート">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+route (ルート)パラメータにマッチする正確な文字列をより詳細に制御するには、括弧(`()`)で正規表現を追加します。
+
+```
+ルートパス: /user/:userId(\d+)
+リクエスト URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="警告">
+
+正規表現は通常文字列の一部であるため、 `\`
+文字を追加して、`\d+`などのバックスラッシュをエスケープしてください。
+
+</Alert>
+
+<Alert type="警告">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. 回避策として、`*` の代わりに `{0,}` を使用します。 これはExpress 5で修正される可能性があります。
+</Alert>
+
+## Route handlers
+
+リクエストを処理するために、 [middleware](/en/guide/using-middleware) のように動作する複数のコールバック関数を提供できます。 唯一の例外は、これらのコールバックが `next('route')` を呼び出して、残りのルートコールバックをバイパスすることです。 このメカニズムを使用して、ルート上に事前条件を設定できます。 次に現在のルートを進める理由がなければ次のルートに制御を渡す。
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+この例では:
+
+- `GET /user/5` → 最初のルートで処理 → "User 5" を送信
+- `GET /user/0` → 最初のroute ('route')`を呼び出し、次に一致する `/user/:id\` route (ルート) をスキップします。
+
+ルートハンドラは、次の例に示すように、関数、関数の配列、または両方の組み合わせの形式で使用できます。
+
+単一のコールバック関数はルートを処理できます。 例:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+複数のコールバック関数がルートを処理できます (`next` オブジェクトを指定してください)。 例:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+コールバック関数の配列はルートを処理できます。 例:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+独立した関数と関数の配列の組み合わせは、ルートを処理することができます。 例:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## レスポンスメソッド
+
+次の表のレスポンスオブジェクト (`res`) のメソッドは、クライアントにレスポンスを送信し、リクエスト応答のサイクルを終了することができます。 これらのメソッドのいずれもルートハンドラから呼び出されない場合、クライアントリクエストはハングしたままになります。
+
+| 方法                                          | 説明                                                                               |
+| --------------------------------------------- | ---------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | ダウンロードするファイルを指示します。                                             |
+| [res.end()](/en/5x/api#res.end)               | 応答プロセスを終了します。                                                         |
+| [res.json()](/en/5x/api#res.json)             | JSON 応答を送信します。                                                            |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | JSONP サポートを使用して JSON 応答を送信します。                                   |
+| [res.redirect()](/en/5x/api#res.redirect)     | リダイレクトします。                                                               |
+| [res.render()](/en/5x/api#res.render)         | ビューテンプレートをレンダリングします。                                           |
+| [res.send()](/en/5x/api#res.send)             | さまざまなタイプの応答を送信します。                                               |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | ファイルをオクテットストリームとして送信する。                                     |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | レスポンスステータスコードを設定し、文字列表現をレスポンスボディとして送信します。 |
+
+## app.route()
+
+`app.route()` を使用すると、ルートパスに対してチェーン可能なルートハンドラを作成できます。
+パスは単一の場所で指定されているため、モジュラールートを作成することは、冗長性とタイプミスを削減するのに役立ちます。 ルートの詳細については、以下を参照してください: [Router() documentation](/en/5x/api#router)。
+
+以下は、`app.route()`を使用して定義されたルートハンドラの例です。
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+`express.Router` クラスを使用して、モジュール化されたマウント可能なルートハンドラを作成します。 `Router`インスタンスは完全なミドルウェアとルーティングシステムです。そのため、しばしば「ミニアプリ」と呼ばれます。
+
+次の例では、ルータをモジュールとして作成し、ミドルウェア関数をロードします。 いくつかのルートを定義し、メインアプリのパスにルータモジュールをマウントします。
+
+appディレクトリに`birds.js`という名前のルーターファイルを作成します。以下の内容を使用します。
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+次に、アプリにルーターモジュールをロードします。
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+アプリは `/birds` と `/birds/about` へのリクエストを処理できるようになりました。 同様に、ルート固有の「timeLog」ミドルウェア関数を呼び出します。
+
+ただし、親ルート `/birds` にパスパラメータがある場合、サブルートからデフォルトではアクセスできません。 アクセス可能にするには、 `mergeParams` オプションを Router コンストラクタ [reference](/en/5x/api#app.use) に渡す必要があります。
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/ja/4x/guide/using-middleware.mdx b/src/content/docs/ja/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..18927c340c
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: ミドルウェアの使用
+description: Express.jsアプリケーションでミドルウェアを使用する方法、アプリケーションレベルおよびルータレベルのミドルウェア、エラー処理、サードパーティミドルウェアの統合などを学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express はルーティングおよびミドルウェアの Web フレームワークで、独自の最小限の機能を持っています。Express アプリケーションは、基本的にはミドルウェア関数の一連の呼び出しです。
+
+_Middleware_ 関数は、[request object](/en/5x/api#req) (`req`) にアクセスできる関数です。 [response object](/en/5x/api#res) (`res`) と、アプリケーションのリクエストレスポンスサイクルの次のミドルウェア関数。 次のミドルウェア関数は通常`next`という名前の変数で表されます。
+
+ミドルウェア機能は以下のタスクを実行できます。
+
+- 任意のコードを実行します。
+- リクエストとレスポンスオブジェクトに変更を加えます。
+- リクエストレスポンスサイクルを終了します。
+- スタック内の次のミドルウェア関数を呼び出します。
+
+現在のミドルウェア関数がリクエスト応答サイクルを終了しない場合は、次のミドルウェア関数に制御を渡すために `next()` を呼び出す必要があります。 そうでなければ、リクエストはハングアップのままになります。
+
+Express アプリケーションでは、次のタイプのミドルウェアを使用できます。
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+アプリケーションレベルおよびルーターレベルのミドルウェアは、任意のマウントパスでロードできます。
+また、一連のミドルウェア関数を一緒にロードして、マウントポイントでミドルウェアシステムのサブスタックを作成することもできます。
+
+## アプリケーションレベルのミドルウェア
+
+`app.use()` と `app()` を使用して、アプリケーションレベルのミドルウェアを [app object](/en/5x/api#app) のインスタンスにバインドします。 ETHOD()関数。`METHOD`はミドルウェア関数が小文字で処理するHTTPメソッドです(GET、PUT、POSTなど)。
+
+この例では、マウントパスのないミドルウェア関数を示します。 この関数はアプリがリクエストを受け取るたびに実行されます。
+
+```js
+const express = require('express');
+const app = expresss();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+この例では、`/user/:id` パスにマウントされたミドルウェア関数を示します。 関数は `/user/:id` パス上の任意のタイプの
+HTTP リクエストに対して実行されます。
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+この例ではルートとハンドラ関数(ミドルウェアシステム)を示します。 関数は`/user/:id`パスへのGETリクエストを処理します。
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+次に、マウントパスを持つ一連のミドルウェア関数をマウントポイントにロードする例を示します。
+これは `/user/:id` パスにHTTPリクエスト情報を出力するミドルウェアのサブスタックを示しています。
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+ルートハンドラを使用すると、パスに複数のルートを定義できます。 下の例では、`/user/:id`パスへのGETリクエストに対する2つのルートを定義しています。 2番目のルートは問題を引き起こすことはありませんが、最初のルートはリクエスト応答サイクルを終了するため、呼び出されることはありません。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+他のミドルウェア関数をルータのミドルウェアスタックからスキップするには、次のルートに制御を渡すために `next('route')` を呼び出します。
+
+<Alert type="情報">
+
+`next('route')` は、
+`app.METHOD()` または `router.METHOD()` 関数を使用してロードされたミドルウェア関数でのみ動作します。
+
+</Alert>
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+ミドルウェアは、再利用可能な配列で宣言することもできます。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを持つ配列を示しています。
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## ルーターレベルのミドルウェア
+
+ルータレベルのミドルウェアは、`express.Router()`のインスタンスにバインドされている場合を除き、アプリケーションレベルのミドルウェアと同じ方法で動作します。
+
+```js
+const router = express.Router();
+```
+
+`router.use()`と`router.METHOD()`関数を使ってルーターレベルのミドルウェアをロードします。
+
+次のコード例は、ルーターレベルのミドルウェアを使用して、アプリケーションレベルのミドルウェアに対して上記のミドルウェアシステムを複製します。
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+ルーターのミドルウェア関数の残りをスキップするには、`next('router')`
+を呼び出してルーターインスタンスからコントロールを渡します。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## エラー処理のミドルウェア
+
+<Alert type="アラート">
+
+エラー処理ミドルウェアは常に\_4つの引数を取ります。 エラー処理ミドルウェア関数として
+識別するには、4つの引数を指定する必要があります。 `next`
+オブジェクトを使用しなくても、署名を維持するために指定する必要があります。 Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+他のミドルウェア関数と同じ方法でエラー処理ミドルウェア関数を定義します 3 つの代わりに 4 つの引数を指定する場合を除き、特に \`(err, req, res, next) というシグネチャを使用します。
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+エラー処理ミドルウェアの詳細については、[Error handling](/en/guide/error-handling)を参照してください。
+
+## 組み込みのミドルウェア
+
+バージョン 4.x 以降、Express は [Connect](https://github.com/senchalabs/connect) に依存しなくなりました。 The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express には次のミドルウェア関数が組み込まれています。
+
+- [express.static](/en/5x/api#express.static) は、HTML ファイル、画像などの静的なアセットを提供します。
+- [express.json](/en/5x/api#express.json) は、JSON ペイロードで受信したリクエストを解析します。 \*\*注意: Express 4.16.0+で利用可能
+- [express.urlencoded](/en/5x/api#express.urlencoded) は、URLエンコードされたペイロードで受信するリクエストを解析します。 \*\*注意: Express 4.16.0+で利用可能
+
+## サードパーティのミドルウェア
+
+サードパーティ製ミドルウェアを使用して、Express アプリに機能を追加します。
+
+必要な機能のためにNode.jsモジュールをインストールし、アプリケーション・レベルまたはルータレベルでアプリケーションにロードします。
+
+次の例は、cookie-parser関数`cookie-parser`のインストールとロードを示しています。
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Expressで一般的に使用されるサードパーティミドルウェア関数の部分的なリストについては、[サードパーティミドルウェア](../resources/middleware)を参照してください。
diff --git a/src/content/docs/ja/4x/guide/using-template-engines.mdx b/src/content/docs/ja/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..acc079ae84
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Express でテンプレートエンジンを使用する
+description: Pug、Handlebars、EJSなどのテンプレートエンジンをExpress.jsで統合して使用し、動的なHTMLページを効率的にレンダリングする方法をご覧ください。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_template engine_ を使用すると、アプリケーションで静的なテンプレート ファイルを使用できます。 実行時に、テンプレートエンジンはテンプレートファイルの
+変数を実際の値に置き換えます。 をクリックして、テンプレートをクライアントに送信する HTML ファイルに変換します。
+このアプローチにより、HTML ページのデザインが容易になります。
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+テンプレートファイルをレンダリングするには、ジェネレータが作成したデフォルトの `app.js` で、次の[アプリケーション設定プロパティ](/en/4x/api#app.set)を設定します。
+
+- `views` テンプレートファイルがあるディレクトリ。 例: `app.set('views', './views')` 。
+  デフォルトはアプリケーションのルートディレクトリにある `views` ディレクトリです。
+- `viewengine` を使用するテンプレートエンジン。 たとえば、Pugテンプレートエンジンを使用するには、`app.set('view engine', 'pug')`を使います。
+
+次に、対応するテンプレートエンジン npm パッケージをインストールします。例えば、Pug をインストールする場合:
+
+```bash
+$ npm install pig --save
+```
+
+<Alert type="アラート">
+Pug のような Express 準拠のテンプレートエンジンは、 `__express(filePath, options, callback)` という名前の関数、 `res.render()` がテンプレートコードのレンダリングを呼び出す
+をエクスポートします。
+
+一部のテンプレートエンジンはこの規約に従っていません。 [@ladjs/integrate](https://www.npmjs.com/package/@ladjs/consolidate)
+ライブラリは、一般的な Node.js テンプレートエンジンのすべてをマッピングすることによって、この規則に従っており、したがって、Express 内でシームレスに動作します。
+
+</Alert>
+
+ビューエンジンが設定された後、アプリケーションにエンジンを指定したりテンプレートエンジンモジュールをロードしたりする必要はありません。
+Express はモジュールを内部的にロードします。例:
+
+```js
+app.set('view engine', 'pug');
+```
+
+次に、`views`ディレクトリに`index.pug`という名前のパグテンプレートファイルを作成します。
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+`index.pug` ファイルをレンダリングするルートを作成します。 If the `view engine` property is not set,
+you must specify the extension of the `view` file. そうでなければ、それを省略することができます。
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+ホームページへのリクエストを行うと、 `index.pug` ファイルは HTML としてレンダリングされます。
+
+ビューエンジンキャッシュはテンプレートの出力の内容をキャッシュせず、元のテンプレート自体のみキャッシュします。 キャッシュがオンの場合でも、ビューはリクエストごとに再レンダリングされます。
diff --git a/src/content/docs/ja/4x/guide/writing-middleware.mdx b/src/content/docs/ja/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..bc96db573c
--- /dev/null
+++ b/src/content/docs/ja/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Express アプリで使用するミドルウェアを書く
+description: Express.jsアプリケーション用にカスタムミドルウェア関数を作成する方法を学びます。例や、リクエストとレスポンスの処理を強化するためのベストプラクティスなどです。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ 関数は、[request object](/en/5x/api#req) (`req`) にアクセスできる関数です。 [response object](/en/5x/api#res) (`res`)とアプリケーションのリクエストレスポンスサイクルの中の `next` 関数。 `next` 関数はExpressルータ内の関数で、呼び出されたときに現在のミドルウェアを継承してミドルウェアを実行します。
+
+ミドルウェア機能は以下のタスクを実行できます。
+
+- 任意のコードを実行します。
+- リクエストとレスポンスオブジェクトに変更を加えます。
+- リクエストレスポンスサイクルを終了します。
+- スタック内の次のミドルウェアを呼び出します。
+
+現在のミドルウェア関数がリクエスト応答サイクルを終了しない場合は、次のミドルウェア関数に制御を渡すために `next()` を呼び出す必要があります。 そうでなければ、リクエストはハングアップのままになります。
+
+次の図はミドルウェア関数呼び出しの要素を示しています。
+
+<div class="テーブルスクロール">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="ミドルウェア関数呼び出しの要素" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">ミドルウェア関数が適用されるHTTPメソッド。</div>
+
+<div class="callout" id="callout2">
+  ミドルウェア関数が適用されるパス(ルート)。
+</div>
+
+<div class="callout" id="callout3">
+  ミドルウェア関数。
+</div>
+
+<div class="callout" id="callout4">
+  規約ごとに「next」と呼ばれるミドルウェア関数へのコールバック引数。
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">レスポンス</a> は、
+  規則によって「res」と呼ばれるミドルウェア関数への引数です。
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">は "req" と呼ばれるミドルウェア関数に</a> 引数を要求します。</div>
+</td>
+</tr>
+</table>
+</div>
+
+Express 5以降、Promiseを返すミドルウェア関数はエラーの拒否またはスロー時に「next(value)」を呼び出します。 `next`は、拒否された値またはスローされたエラーで呼び出されます。
+
+## 例
+
+以下は、簡単な「Hello World」エクスプレスアプリケーションの例です。
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### ミドルウェア関数 myLogger
+
+以下は、「myLogger」というミドルウェア関数の簡単な例です。 この関数は、アプリへのリクエストがそれを通過したときに
+"LOGGED" を出力します。 ミドルウェア関数は、`myLogger`という名前の
+変数に割り当てられます。
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="アラート">
+
+上記の `next()` の呼び出しに注目してください。 この関数を呼び出すと、
+アプリケーションで次のミドルウェア関数が呼び出されます。 `next()`関数はノードの一部ではありません。 sまたはExpress APIはミドルウェア関数に渡される3番目の
+引数です。 `next()`関数には、
+という名前が付けられますが、慣習的には常に「next」という名前が付けられています。 混乱を避けるため、常にこの規約を使用してください。
+
+</Alert>
+
+ミドルウェア関数をロードするには、ミドルウェア関数を指定して `app.use()` を呼び出します。
+例えば、次のコードはルートパス(/)の前に`myLogger`ミドルウェア関数をロードします。
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+アプリがリクエストを受け取るたびに、「LOGGED」というメッセージが端末に出力されます。
+
+ミドルウェアのロード順序は重要です。最初にロードされるミドルウェア関数も最初に実行されます。
+
+ルートパスの後に`myLogger`がロードされている場合、リクエストは到達せず、アプリは"LOGGED"を出力しません。 なぜなら、ルートパスのルートハンドラは、リクエスト応答サイクルを終了するからです。
+
+ミドルウェア関数 `myLogger` は単にメッセージを出力します。 次に、`next()`関数を呼び出すことで、スタック内の次のミドルウェア関数にリクエストを渡します。
+
+### ミドルウェア関数requestTime
+
+次に、"requestTime" というミドルウェア関数を作成し、リクエストオブジェクトに `requestTime`
+というプロパティを追加します。
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+アプリは `requestTime` ミドルウェア関数を使用します。 また、ルートのコールバック関数はミドルウェア関数が`req`（リクエストオブジェクト）に追加するプロパティを使用します。
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+アプリのルートにリクエストを送信すると、アプリはブラウザにリクエストのタイムスタンプを表示するようになりました。
+
+### ミドルウェア関数 validateCookies
+
+最後に、入力されたクッキーを検証するミドルウェア機能を作成し、クッキーが無効な場合に400回のレスポンスを送信します。
+
+ここでは、外部非同期サービスで Cookie を検証する機能の例を示します。
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+ここでは、[`cookie-parser`](/en/resources/middleware/cookie-parser) ミドルウェアを使用して、`req`オブジェクトから入ってくるCookieを解析し、それを私たちの`cookieValidator`関数に渡します。 `validateCookies`ミドルウェアは、拒否時に自動的にエラーハンドラをトリガーするPromiseを返します。
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="アラート">
+
+`await cookieValidator(req.cookies)`の後に`next()`が呼び出されることに注意してください。 これにより、
+`cookieValidator` が解決した場合、スタック内の次のミドルウェアが呼ばれます。 If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+リクエストオブジェクト、レスポンスオブジェクト、スタック内の次のミドルウェア関数、そしてノード全体にアクセスできるためです。 s API、ミドルウェア関数の可能性は無限大です。
+
+Express ミドルウェアの詳細については、[Express ミドルウェアを使用する](/en/guide/using-middleware)を参照してください。
+
+## 設定可能なミドルウェア
+
+ミドルウェアの設定が必要な場合は、optionsオブジェクトや他のパラメータを受け付ける関数をエクスポートしてください。 入力パラメータに基づいてミドルウェアの実装を返します。
+
+ファイル: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+ミドルウェアを以下のように使用できるようになりました。
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+構成可能なミドルウェアの例については、 [cookie-session](https://github.com/expressjs/cookie-session) と [compression](https://github.com/expressjs/compression) を参照してください。
diff --git a/src/content/docs/ja/4x/starter/basic-routing.mdx b/src/content/docs/ja/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..a6e98519ec
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: 基本ルーティング
+description: Express.jsアプリケーションでルーティングの基礎を学びます。ルートの定義、HTTPメソッドの処理、Webサーバーのルートハンドラの作成などです。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ は、アプリケーションが特定のエンドポイントに対してどのように応答するかを決定することを指します。 これはURI(またはパス)と特定のHTTPリクエストメソッド(GET、POSTなど)です。
+
+各ルートは、ルートが一致したときに実行される、1つまたは複数のハンドラ関数を持つことができます。
+
+ルート定義は以下の構造をとります:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+場所:
+
+- `app` は `express` のインスタンスです。
+- `METHOD` は [HTTP リクエストメソッド](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods) の小文字です。
+- `PATH` はサーバー上のパスです。
+- `HANDLER` はルートが一致したときに実行される関数です。
+
+<Alert type="アラート">
+
+このチュートリアルでは、`app` という名前の `express` インスタンスが作成され、サーバーが
+動作していることを前提としています。 アプリの作成に慣れていない場合は、Hello world
+exampleを参照してください。
+
+</Alert>
+
+以下の例は、単純なルートの定義を示しています。
+
+ホームページの「Hello World!」に返信:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+ルートルート (`/`) の POST リクエストに応答します。アプリケーションのホームページ:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+`/user`ルートにPUTリクエストに応答します：
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+`/user`ルートへのDELETEリクエストに対応:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/ja/4x/starter/examples.mdx b/src/content/docs/ja/4x/starter/examples.mdx
new file mode 100644
index 0000000000..0c0be44268
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: エクスプレス例
+description: さまざまなユースケース、インテグレーション、高度な構成を網羅した Express.jsアプリケーション例のコレクションをご覧ください。プロジェクトの学習と構築に役立ちます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - ログインとパスワードによる認証
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - HTTP コンテンツネゴシエーション
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - クッキーベースのセッションの操作
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - クッキーの操作
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - クライアントへのファイルの転送
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - 埋め込みJavaScriptテンプレートの操作 (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - エラーページの作成
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - エラーミドルウェアの操作
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - シンプルなリクエストハンドラ。
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown as template engine.
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - 複数のエクスプレスルーターでの作業
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - MVCスタイル コントローラ
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - オンラインユーザーアクティビティを`オンライン`と`redis`パッケージで追跡
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - ルートパラメータの操作
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - 同じリソースに対する複数の HTTP 操作
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - 地図を使ってルートを整理する
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - route middleware の操作
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - 各リソースごとにルートを整理する
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - ユーザーセッション
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - 静的ファイルの提供
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - 仮想ホストでの作業
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - ビューを動的にレンダリングする
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - ミドルウェア呼び出し間でリクエストオブジェクトにデータを保存する
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Simple API service
+
+## その他の例
+
+これらは、より広範な統合を伴ういくつかの追加の例です。
+
+<Alert type="警告">
+  この情報は、
+  Expressjsチームがメンテナンスしていないサードパーティのサイト、製品、またはモジュールを指します。
+  ここでの掲載は、 Expressjsプロジェクトチームの推奨または推奨を構成するものではありません。
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - ORMとしてExpressとNext.jsを使用したフルスタックアプリ [Prisma](https://www.npmjs.com/package/prisma)
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - ORMとして [Prisma](https://www.npmjs.com/package/prisma) を使用する Express をTypeScript で REST API
diff --git a/src/content/docs/ja/4x/starter/faq.md b/src/content/docs/ja/4x/starter/faq.md
new file mode 100644
index 0000000000..89d34a303a
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Express.jsについてよく寄せられる質問の答えを見つけましょう。その中には、アプリケーション構造、モデル、認証、テンプレートエンジン、エラー処理などのトピックが含まれます。
+---
+
+## アプリケーションを構成するにはどうすればいいですか?
+
+この質問には決定的な答えはありません。 The answer depends
+on the scale of your application and the team that is involved. 可能な限り
+柔軟性を持たせるために、Expressは構造的な仮定をしません。
+
+ルートやその他のアプリケーション固有のロジックは、任意のディレクトリ構造において、
+好きな数のファイルに保存することができます。 View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+また、Express 用のサードパーティの拡張機能もあり、これらのパターンのいくつかを簡素化します。
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## モデルを定義するにはどうすればいいですか?
+
+Express にはデータベースという概念はありません。 このコンセプトは
+サードパーティ製の Node モジュールに残されており、ほぼすべてのデータベースと
+インターフェイスを使用できます。
+
+モデルを中心とした Express ベースのフレームワークについては [LoopBack](http://loopback.io) を参照してください。
+
+## どのようにユーザーを認証できますか?
+
+Authentication is another opinionated area that Express does not
+venture into. 任意の認証スキームを使用できます。
+単純なユーザー名/パスワードスキームについては、[この例](https://github.com/expressjs/express/tree/master/examples/auth)を参照してください。
+
+## Expressはどのテンプレートエンジンをサポートしていますか?
+
+Express は、\`(path, local, callback) 署名に適合するテンプレートエンジンをサポートしています。
+テンプレートエンジンインターフェイスとキャッシュを正規化するには、
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+プロジェクトをサポートしてください。 リストされていないテンプレートエンジンは引き続きExpress 署名をサポートする可能性があります。
+
+詳しくは、[Expressでテンプレートエンジンを使用する](/en/guide/using-template-engines)を参照してください。
+
+## 404応答はどのように処理すればいいですか?
+
+Expressでは404応答はエラーの結果ではないため、
+エラーハンドラミドルウェアはそれらを捕捉しません。 This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+`express.Router()`
+のインスタンスで実行時にルートを動的に追加することで、ルートはミドルウェア関数に取って代わられません。
+
+## エラーハンドラの設定方法は?
+
+他のミドルウェアと同じ方法でエラー処理ミドルウェア
+を定義します。ただし、3つではなく4つの引数を使用します。 具体的にはシグネチャ`(err, req, res, next)`を指定します。
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+詳細については、[Error handling](/en/guide/error-handling)を参照してください。
+
+## プレーンHTMLをレンダリングするにはどうすればいいですか?
+
+違います！ `res.render()`関数でHTMLを「レンダリング」する必要はありません。
+特定のファイルがある場合は、 `res.sendFile()` 関数を使用します。
+ディレクトリから多くのアセットを提供している場合は、`express.static()`
+ミドルウェア関数を使用してください。
+
+## Express にはどのバージョンの Node.js が必要ですか?
+
+- [Express 4.x](/en/4x/api) では、Node.js 0.10 以上が必要です。
+- Express 5.x](/en/5x/api) ではNode.js 18 以上が必要です。
diff --git a/src/content/docs/ja/4x/starter/generator.mdx b/src/content/docs/ja/4x/starter/generator.mdx
new file mode 100644
index 0000000000..13c433e806
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express アプリケーションジェネレーター
+description: Expressアプリケーションジェネレータツールを使用して、Express.jsアプリケーション用のスケルトンを迅速に作成し、セットアップと構成を合理化する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+アプリケーションジェネレータツール`express-generator`を使用して、アプリケーションスケルトンを素早く作成します。
+
+アプリケーションジェネレータは `npx` コマンド (Node.js 8.2.0で利用可能) で実行できます。
+
+```bash
+$ npx express-generator
+```
+
+以前のNodeバージョンの場合は、アプリケーションジェネレータをグローバルnpmパッケージとしてインストールしてから起動します。
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+`-h` オプションでコマンドオプションを表示します。
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+例えば、次のように、_myapp_ という名前の Express アプリケーションを作成します。 アプリは現在の作業ディレクトリの _myapp_ というフォルダに作成され、ビューエンジンは <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a> に設定されます。
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+次に依存関係をインストール:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+MacOS または Linux では、次のコマンドでアプリを実行します。
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Windows コマンドプロンプトでは、次のコマンドを使用します。
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+Windows PowerShell では、次のコマンドを使用します。
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+次に、ブラウザに`http://localhost:3000/`を読み込んでアプリにアクセスします。
+
+生成されたアプリには、次のディレクトリ構造があります。
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="情報">
+
+ジェネレータによって作成されたアプリ構造は、Express アプリケーションを構成するための多くの方法の1つに過ぎません。
+自由にこの構造を使用するか、あなたのニーズに最適に変更してください。
+
+</Alert>
diff --git a/src/content/docs/ja/4x/starter/hello-world.mdx b/src/content/docs/ja/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..369821bf38
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Express.jsを始めるには、シンプルな「Hello World」アプリケーションを構築しましょう。初心者向けの基本的なセットアップとサーバー作成を説明します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="情報">
+
+以下に埋め込まれているのは、基本的に作成できる最も簡単なExpressアプリです。 It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+このアプリはサーバーを起動し、接続のためにポート3000をリッスンします。 アプリはルート URL (`/`) または _route_ にリクエスト
+を返します。 他のすべてのパスについては、**404 Not Found**で応答します。
+
+## ローカルで実行中
+
+最初に `myapp` という名前のディレクトリを作成し、変更して `npm init` を実行します。 Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+`myapp` ディレクトリで、`app.js`という名前のファイルを作成し、上の例からコードをコピーします。
+
+<Alert type="アラート">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+次のコマンドでアプリを実行します。
+
+```bash
+$ node app.js
+```
+
+次に、ブラウザーに `http://localhost:3000/` をロードして出力を確認します。
diff --git a/src/content/docs/ja/4x/starter/installing.mdx b/src/content/docs/ja/4x/starter/installing.mdx
new file mode 100644
index 0000000000..1be44bf24f
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: インストール中
+description: プロジェクトディレクトリの設定やnpmとの依存関係の管理など、Node.js 環境で Express.js をインストールする方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+始める前に、 [Node.js](https://nodejs.org/) 0.10 以上がインストールされていることを確認してください。 次に、アプリケーションのディレクトリを作成し、その中に移動します。
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+`npm init` コマンドを使用して、アプリケーション用の `package.json` ファイルを作成します。
+`package.json` がどのように動作するかについては、[npm の package.json handling](https://docs.npmjs.com/files/package.json) を参照してください。
+
+```bash
+npm init
+```
+
+このコマンドを実行すると、アプリケーションの名前やバージョンなど、さまざまなものが表示されます。
+今のところ、RETURNを押すと、ほとんどのデフォルトを受け入れることができます。以下の例外があります。
+
+```
+エントリ ポイント: (index.js)
+```
+
+`app.js`、またはメインファイルの名前を何でも入力します。 `index.js`にしたい場合は、RETURNを押して、推奨されるデフォルトのファイル名を受け入れます。
+
+次に、Expressを`myapp`ディレクトリにインストールし、依存関係リストに保存します。 例:
+
+```bash
+npm install Express
+```
+
+Express を一時的にインストールし、依存関係リストに追加しないでください。
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="情報">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Then, afterwards, running `npm install` in the app directory will automatically
+install modules in the dependencies list.
+
+</Alert>
diff --git a/src/content/docs/ja/4x/starter/static-files.mdx b/src/content/docs/ja/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..b72aad560c
--- /dev/null
+++ b/src/content/docs/ja/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Express での静的ファイルの提供
+description: 組み込みの 'static' ミドルウェアを使用して、Express.js アプリケーションで画像、CSS、JavaScript などの静的ファイルを提供する方法を理解します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+画像、CSSファイル、JavaScriptファイルなどの静的ファイルを提供するには、Express で組み込まれているミドルウェア関数「express.static」を使用します。
+
+関数の署名は次のとおりです:
+
+```js
+express.static(root, [options]);
+```
+
+`root` 引数は、静的アセットを提供するルートディレクトリを指定します。
+引数 `options` の詳細については、 [express.static](/en/5x/api#express.static) を参照してください。
+
+例えば、`public`という名前のディレクトリに画像、CSSファイル、JavaScriptファイルを表示するには、次のコードを使用します。
+
+```js
+app.use(express.static('public'));
+```
+
+`public` ディレクトリにあるファイルを読み込むことができます。
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="情報">
+
+Express は静的ディレクトリからの相対的なファイルを検索するので、静的ディレクトリ
+の名前は URL の一部ではありません。
+
+</Alert>
+
+複数の静的アセットディレクトリを使用するには、`express.static` ミドルウェア関数を複数回呼び出します。
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express は、`express.static` ミドルウェア関数で静的ディレクトリを設定する順序でファイルを検索します。
+
+<Alert type="情報">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+\`expressで提供されるファイルに対して、仮想パスプレフィックス(ファイルシステム内にパスが実際に存在しない場所)を作成します。 以下に示すように、staticディレクトリの[mount path](/en/5x/api#app.use)を指定します。
+
+```js
+app.use('/static', express.static('public'));
+```
+
+`/static` というプレフィックスから、 `public` ディレクトリにあるファイルをロードできます。
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+しかし、`express.static`関数に与えるパスは、`node`プロセスを起動したディレクトリからの相対パスです。 expressアプリを別のディレクトリから実行する場合、提供したいディレクトリの絶対パスを使用する方が安全です:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+`serve-static` 関数とそのオプションの詳細については、 [serve-static](/en/resources/middleware/serve-static) を参照してください。
diff --git a/src/content/docs/ja/5x/advanced/developing-template-engines.md b/src/content/docs/ja/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..34a00b66da
--- /dev/null
+++ b/src/content/docs/ja/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Express 用テンプレートエンジンの開発
+description: App.engine() を使用して Express.js 用のカスタムテンプレートエンジンを開発する方法と、独自のテンプレートレンダリングロジックの作成と統合の例をご覧ください。
+---
+
+`app.engine(ext, callback)`メソッドを使用して、独自のテンプレートエンジンを作成します。 `ext`はファイル拡張子を指し、`callback`はテンプレートエンジン関数です。 は、次の項目をパラメータとして受け付けます。ファイルの場所、options オブジェクト、およびコールバック関数です。
+
+以下のコードは、`.ntl`ファイルをレンダリングするための非常に単純なテンプレートエンジンを実装した例です。
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+アプリは `.ntl` ファイルをレンダリングできるようになります。 `views`ディレクトリに`index.ntl`という名前のファイルを作成します。
+
+```pug
+#title#
+#message#
+```
+
+次に、アプリに次のルートを作成します。
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+ホームページへのリクエストを行うと、`index.ntl`はHTMLとしてレンダリングされます。
diff --git a/src/content/docs/ja/5x/guide/behind-proxies.mdx b/src/content/docs/ja/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..a70ee8bd1d
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/behind-proxies.mdx
@@ -0,0 +1,103 @@
+---
+title: プロキシの背後にあるエクスプレス
+description: クライアントの IP アドレスを処理するトラストプロキシ設定を使用するなど、リバース・プロキシの背後で正しく動作するように Express.js アプリケーションを構成する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+リバースプロキシの背後で Express アプリケーションを実行する場合、Express API の中には予想以外の値が返されるものがあります。 これを調整するために `trust proxy` アプリケーションの設定は、Express API のリバースプロキシによって提供された情報を公開するために使用することができます。 最も一般的な問題は、クライアントのIPアドレスを公開するAPIで、リバースプロキシの内部IPアドレスが表示される可能性があります。
+
+<Alert type="情報">
+
+`trust proxy` の設定では、
+リバースプロキシの正確な設定を理解することが重要です。 この設定はリクエストで提供された値を信頼するためです Express での設定の組み合わせが
+リバースプロキシの動作と一致することが重要です。
+
+</Alert>
+
+`trust proxy`を設定するアプリケーションは、次の表に示されている値のいずれかを設定することができます。
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th /><th>値</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+`true` の場合、クライアントの IP アドレスは `X-Forwarded-For` ヘッダーの中の一番左のエントリとして理解されます。
+
+`false` の場合、アプリはクライアントに直接向いていると理解され、クライアントの IP アドレスは `req.socket.remoteAddress` に由来します。 これはデフォルトの設定です。
+
+<Alert type="警告">
+`true` に設定する場合、信頼されている最後のリバースプロキシが以下のすべての HTTP ヘッダを削除/上書きすることが重要です: `X-Forwarded-For` 。 `X-Forwarded-Host` と `X-Forwarded-Proto` があれば、クライアントが何らかの値を提供できるかもしれません。
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IPアドレス</td>
+<td markdown="1">
+リバースプロキシとして信頼する IP アドレス、サブネット、または IP アドレスとサブネットの配列。 次のリストに、事前に設定されたサブネット名が表示されます。
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniqueloc - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+IPアドレスは以下のいずれかの方法で設定できます。
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+指定された場合、IPアドレスまたはサブネットはアドレス決定プロセスから除外されます。 アプリケーションサーバーに最も近い信頼できないIPアドレスは、クライアントのIPアドレスとして決定されます。 これは `req.socket.remoteAddress` が信頼されているかどうかをチェックすることで動作します。 その場合、`X-Forwarded-For`内の各アドレスは、最初の信頼されていないアドレスまで右から左にチェックされます。
+
+</td>
+    </tr>
+    <tr>
+      <td>数字</td>
+<td markdown="1">
+Expressアプリケーションから離れたホップの最大数のアドレスを使用してください。 `req.socket.remoteAddress` は最初のホップで、残りは右から左への `X-Forwarded-For` ヘッダで探します。 `0`の値は、最初に信頼されていないアドレスが`req.socket.remoteAddress`であることを意味します。つまり、リバースプロキシは存在しません。
+
+<Alert type="警告">
+この設定を使用する場合は、複数がないことを確認することが重要です。 Expressアプリケーションへの異なる長さのパスは、クライアントが設定されたホップ数よりも少なくすることができるようになります。 それ以外の場合は、クライアントが何らかの価値を提供することができます。
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>関数</td>
+<td markdown="1">
+カスタムトラスト実装。
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+`trust proxy` を有効にすると、次のような影響を与えます。
+
+<ul>
+  <li markdown="1">
+    [req.hostname](/en/api#req.hostname) の値は、 `X-Forwarded-Host`
+    ヘッダで設定された値から取得されます。 クライアントやプロキシによって設定できます
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` はリバースプロキシによって設定することで、アプリが https`か`http\`
+    か無効な名前かをアプリに伝えることができます。 この値は [req.protocol](/en/api#req.protocol)
+    で反映されます。
+  </li>
+  <li markdown="1">
+    [req.ip](/en/api#req.ip) と [req.ips](/en/api#req.ips) の値は、 ソケットアドレスと
+    `X-Forwarded-For` ヘッダーに基づいて入力されます。 最初の信頼されていないアドレスから始めます
+  </li>
+</ul>
+
+`trust proxy` は、 [proxy-addr](https://www.npmjs.com/package/proxy-addr) パッケージを使用して実装されています。 詳細については、そのドキュメントを参照してください。
diff --git a/src/content/docs/ja/5x/guide/debugging.mdx b/src/content/docs/ja/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..80cd35328f
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Expressのデバッグ
+description: DEBUG環境変数を設定して、Express.jsアプリケーションでデバッグログを有効にして使用する方法を学び、トラブルシューティングを強化します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express で使用されるすべての内部ログを表示するには、アプリを起動するときに `DEBUG` 環境変数を
+`express:*` に設定します。
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+Windows では、対応するコマンドを使用します。
+
+```bash
+> $env:DEBUG = "express:*"; ノードインデックス.js
+```
+
+[express generator](/en/starter/generator) で生成されたデフォルトのアプリでこのコマンドを実行すると、以下の出力が出力されます。
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+アプリへのリクエストが行われると、Express コードで指定されたログが表示されます。
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+ルータの実装からのみログを見るには、`DEBUG`の値を`express:router`に設定します。 同様に、アプリケーションの実装からのログのみを見るには、`DEBUG`の値を`express:application`などに設定します。
+
+## `express` で生成されたアプリケーション
+
+`express`コマンドによって生成されたアプリケーションは、`debug`モジュールを使用し、デバッグ名前空間はアプリケーションの名前をスコープします。
+
+例えば、 `$ express sample-app` を使用してアプリを生成した場合、次のコマンドでデバッグ文を有効にできます。
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+カンマ区切りの名前のリストを割り当てることで、複数のデバッグ名前空間を指定できます:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## 高度なオプション
+
+Node.js を介して実行する場合、デバッグログの動作を変更するいくつかの環境変数を設定できます。
+
+| 名前                | 目的                                                   |
+| ------------------- | ------------------------------------------------------ |
+| `DEBUG`             | 特定のデバッグ名前空間を有効/無効にします。            |
+| `DEBUG_COLORS`      | デバッグ出力で色を使用するかどうか。                   |
+| `DEBUG_DEPTH`       | 物体検査の深さ。                                       |
+| `DEBUG_FD`          | デバッグ出力を書き込むファイル記述子。                 |
+| `DEBUG_SHOW_HIDDEN` | 検査対象オブジェクトに非表示のプロパティを表示します。 |
+
+<Alert type="情報">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters.
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) の完全な
+リストについては Node.js のドキュメントを参照してください。
+
+</Alert>
diff --git a/src/content/docs/ja/5x/guide/error-handling.mdx b/src/content/docs/ja/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..4a19e9fcc1
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: エラー処理
+description: Express.jsが同期コードと非同期コードのエラーを処理する方法を理解し、アプリケーション用のカスタムエラー処理ミドルウェアを実装する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+*Error Handling*は、
+が同期と非同期の両方で発生するエラーをExpress がキャッチして処理する方法を指します。 Expressにはデフォルトのエラー
+ハンドラが付属しているので、始めるために自分で書く必要はありません。
+
+## キャッチエラー
+
+Express がルートハンドラと
+ミドルウェアの実行中に発生するすべてのエラーをキャッチすることが重要です。
+
+ルートハンドラとミドルウェア
+内の同期コードで発生するエラーは追加の作業を必要としません。 同期コードがエラーをスローする場合、Expressは
+キャッチして処理します。 例:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express はこれを独自にキャッチします。
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. 例:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Express 5以降、Promise
+を返すルートハンドラとミドルウェアは、エラーの拒否またはスロー時に自動的に`next(value)`を呼び出します。
+例:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. 拒否された値が指定されていない場合、 `next`
+はExpress ルータが提供するデフォルトの Error オブジェクトで呼び出されます。
+
+`next()`関数に何かを渡した場合（`'route'`を除く）。
+Expressは現在のリクエストをエラーとみなし、
+残っている非エラー処理ルーティングとミドルウェア関数をスキップします。
+
+シーケンス内のコールバックがデータを提供しない場合、エラーのみを提供する場合は、次のように
+このコードを簡素化できます:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. エラーがなければ、2番目の
+ハンドラが実行されます。そうでなければ、Expressはエラーをキャッチして処理します。
+
+route handler または
+ミドルウェアによって呼び出された非同期コードで発生するエラーをキャッチし、処理のために Express に渡す必要があります。 例:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+上の例では、
+非同期コードのエラーをキャッチし、Expressに渡すために`try...catch`ブロックを使用しています。 `try...catch`
+ブロックが省略された場合、Expressは同期
+ハンドラコードの一部ではないため、エラーをキャッチしません。
+
+プロミスを返す関数
+を使うと、`try...catch` のオーバーヘッドを避けることができます。 例:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+また、非同期コードを些細なものに減らすことで、同期エラー
+のキャッチに依存するハンドラのチェーンを使用することもできます。 例:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+上の例では、`readFile`
+呼び出しからいくつかの些細な文があります。 `readFile` でエラーが発生した場合、エラーは Express に渡されます。 それ以外の場合は、
+チェーン内の次のハンドラ
+で同期エラー処理の世界にすばやく戻ります。 そして、上記の例はデータを処理しようとします。 これが失敗した場合、
+同期エラーハンドラはそれをキャッチします。 `readFile`コールバックの
+内でこの処理を行った場合、アプリケーションが終了する可能性があり、Expressエラー
+ハンドラは実行されません。
+
+どちらの方法を使っても、Expressエラーハンドラを呼び出し、
+アプリケーションを存続させたい場合は Express がエラーを受け取ることを確認する必要があります。
+
+## デフォルトのエラーハンドラです
+
+Expressには、アプリで発生する可能性のあるエラーを処理する内蔵のエラーハンドラが付属しています。 このデフォルトのエラー処理ミドルウェア関数は、ミドルウェア関数スタックの末尾に追加されます。
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. スタックトレースは本番環境に
+含まれていません。
+
+<Alert type="情報">
+
+プロダクションモードでアプリを実行するには、環境変数 `NODE_ENV` を `production` に設定します。
+
+</Alert>
+
+エラーが書き込まれると、次の情報が
+応答に追加されます:
+
+- `res.statusCode` は `err.status` (または `err.statusCode`)から設定されます。
+  の場合、この値が4xxまたは5xxの範囲外の場合、500に設定されます。
+- `res.statusMessage` はステータスコードに従って設定されます。
+- 本文は、プロダクション
+  環境ではステータスコードメッセージのHTMLになります。そうでなければ、`err.stack`になります。
+- `err.headers` オブジェクトで指定されたヘッダー。
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+デフォルトのエラーハンドラは、コード内でエラー
+を複数回呼び出して`next()`を呼び出すとトリガされることに注意してください。 カスタムエラー処理ミドルウェアが導入されたとしてもです
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## エラーハンドラの書き込み
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. 例:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+エラー処理ミドルウェアは、他の `app.use()`とルート呼び出しの後に最後に定義します。例:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+ミドルウェア関数内からのレスポンスは、HTMLエラーページ、シンプルなメッセージ、JSON文字列など、あらゆる形式で使用できます。
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. 例えば、`XHR`とそれ以外のリクエストに対してエラーハンドラ
+を定義するには、次のようにします。
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+この例では、一般的な`logErrors`はリクエストと
+エラー情報を`stderr`に書き込むことができます。
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+この例でも、`clientErrorHandler`は以下のように定義されています。この場合、エラーは明示的に次のエラーに渡されます。
+
+エラー処理関数で「next」を呼び出さない場合、レスポンスの書き込み(および終了)を行う責任があることに注意してください。 そうでなければ、これらのリクエストは「ハング」し、ガベージコレクションの対象になりません。
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+"catch-all" `errorHandler` 関数を以下のように実装します(例えば：
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+複数のコールバック関数を持つルートハンドラがある場合は、`route` パラメータを使用して次のルートハンドラにスキップできます。 例:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+この例では、 `getPaidContent` ハンドラはスキップされますが、 `/a_route_background_paywall` の `app` に残っているハンドラは引き続き実行されます。
+
+<Alert type="情報">
+
+`next()`と`next(err)`への呼び出しは、現在のハンドラが完了している状態を示します。
+`next(err)`は、上記のように
+に設定されているものを除いて、チェーン内の残りのハンドラをすべてスキップします。
+
+</Alert>
diff --git a/src/content/docs/ja/5x/guide/overriding-express-api.md b/src/content/docs/ja/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..324a52bf6d
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Express API のオーバーライド
+description: リクエストとレスポンスオブジェクトのメソッドとプロパティをプロトタイプを使用してオーバーライドすることで、Express.js API をカスタマイズして拡張する方法をご覧ください。
+---
+
+Express API は、リクエストオブジェクトとレスポンスオブジェクトのさまざまなメソッドとプロパティで構成されています。 これらはプロトタイプによって継承されます。 Express API には 2 つの拡張ポイントがあります。
+
+1. `express.request` と `express.response` のグローバルプロトタイプ。
+2. `app.request`と`app.response`でアプリ固有のプロトタイプ。
+
+グローバルプロトタイプを変更すると、読み込まれたすべてのExpressアプリが同じプロセスで影響を受けます。 必要に応じて、新しいアプリを作成した後にアプリ固有のプロトタイプを変更するだけで、アプリ固有の変更を行うことができます。
+
+## メソッド
+
+カスタム関数を割り当てることで、既存のメソッドの署名と振る舞いを独自のメソッドで上書きできます。
+
+以下は、 [res.sendStatus](/en/4x/api#res.sendStatus) の挙動を上書きした例です。
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+上記の実装は `res.sendStatus` の元の署名を完全に変更します。 ステータスコード、エンコーディングタイプ、およびメッセージをクライアントに送信できるようになりました。
+
+オーバーライドされたメソッドは次のように使用できます。
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## プロパティー
+
+Express API のプロパティは以下のいずれかです。
+
+1. 割り当てられたプロパティ (例: `req.baseUrl`, `req.originalUrl`)
+2. getters (例: `req.secure`, `req.ip`) として定義されています。
+
+category 1 のプロパティは、現在のリクエスト-レスポンスサイクルのコンテキストで `request` と `response` オブジェクトに動的に割り当てられます。 彼らの行動はオーバーライドできない
+
+カテゴリ2のプロパティはExpress API拡張機能APIを使用して上書きすることができます。
+
+次のコードは `req.ip` の値をどのように派生するかを書き換えます。 これで、`Client-IP` リクエストヘッダの値を返すだけです。
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## プロトタイプ
+
+Express API を提供するためには、Express に渡された request/response オブジェクトを (`app(req) 経由で) 提供します。 res)`は同じプロトタイプチェーンから継承する必要があります。 デフォルトでは、リクエストの `http.IncomingRequest.prototype` と、レスポンスの `http.ServerResponse.prototype` です。
+
+必要がない限り、これはアプリケーションレベルでのみ行うことを推奨します。 また、使用されているプロトタイプは、可能な限りデフォルトのプロトタイプに近い機能を備えていることに注意してください。
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/ja/5x/guide/routing.mdx b/src/content/docs/ja/5x/guide/routing.mdx
new file mode 100644
index 0000000000..f2a8ebe75d
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: ルーティング
+description: Express.jsアプリケーションでルートを定義して使用する方法を学びます。ルートメソッド、ルートパス、パラメータ、モジュラールーティングにルーターを使用する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ とは、アプリケーションのエンドポイント(URI)がクライアントリクエストに対してどのように応答するかを指します。
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+HTTPメソッドに対応するExpress `app` オブジェクトのメソッドを使用してルーティングを定義します。
+のように、`app。 POST リクエストを処理する GET リクエストと `app.post\` を処理します。 完全なリストについては、
+[app.METHOD](/en/5x/api#app.METHOD) を参照してください。 [app.all()](/en/5x/api#app.all)を使用して、すべてのHTTPメソッドと[app]を処理することもできます。 se()](/en/5x/api#app.use) to
+コールバック関数としてミドルウェアを指定する (詳細は [Using middleware](/en/guide/using-middleware) を参照)。
+
+これらのルーティングメソッドは、アプリケーションが指定されたルート (エンドポイント) と HTTP メソッドへのリクエストを受け取ったときに呼び出されるコールバック関数 ("handler functions" と呼ばれることもあります) を指定します。 言い換えれば、アプリケーションは指定されたルートとメソッドに一致するリクエストを「リッスン」します。 マッチを検出すると、指定されたコールバック関数を呼び出します。
+
+実際、ルーティングメソッドは引数として複数のコールバック関数を持つことができます。
+複数のコールバック関数を使用。 コールバック関数に `next` を引数として渡し、関数の本体内で `next()` を呼び出して、次のコールバックに
+を渡すことが重要です。
+
+以下のコードは、非常に基本的なルートの例です。
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## ルートメソッド
+
+routeメソッドはHTTPメソッドのいずれかから派生し、`express` クラスのインスタンスに追加されます。
+
+以下のコードは、`GET` と `POST` メソッドを定義したルートの例です。
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Expressは、すべてのHTTPリクエストメソッドに対応するメソッドをサポートしています: `get`、`post`など。
+完全なリストについては、 [app.METHOD](/en/5x/api#app.METHOD) を参照してください。
+
+特別なルーティングメソッド`app.all()`があり、\_all_HTTPリクエストメソッドのパスにミドルウェア関数をロードするために使用されます。 例えば、`GET`を使用しているかどうかに関わらず、ルート`"/secret"へのリクエストに対して以下のハンドラが実行されます。 `POST`、`PUT`、`DELETE\`、または[http module](https://nodejs.org/api/http.html#http_http_methods)でサポートされている他のHTTPリクエストメソッド。
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## ルートパス
+
+ルートパスはリクエストメソッドと組み合わせて、リクエストを作成できるエンドポイントを定義します。 ルートパスは文字列、文字列パターン、または正規表現であることができます。
+
+<Alert type="アラート">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="アラート">
+
+式4では、`$`のような正規表現は`\`でエスケープする必要があります。
+
+</Alert>
+
+<Alert type="情報">
+
+Express は [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) をルート
+パスに一致させるために使用します。ルート パスの定義におけるすべての可能性については、path-to-regexp ドキュメントを参照してください。
+[Express Playground Router](https://bjohansebas.github.io/playground-router/)は基本的なExpressルートを
+テストするための便利なツールですが、パターンマッチングはサポートされていません。
+
+</Alert>
+
+<Alert type="warning">クエリ文字列はルートパスの一部ではありません。</Alert>
+
+### 文字列に基づく経路パス
+
+このルートパスはルートルートのリクエストと一致します。
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+このルートパスは `/about` へのリクエストと一致します。
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+このルートパスは `/random.text` へのリクエストと一致します。
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### 文字列パターンに基づく経路パス
+
+<Alert type="アラート">
+
+Express 5の文字列パターンは動作しなくなりました。 詳細については、Migration
+guideを参照してください。
+
+</Alert>
+
+このルートパスは `acd` と `abcd` に一致します。
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+このルートパスは `abcd`、`abbcd`、`abbcd`などにマッチします。
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+このルートパスは `abcd`、`abxcd`、`abrandoMcd`、`ab123cd`などにマッチします。
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+このルートパスは `/abe` と `/abcde` に一致します。
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### 正規表現に基づく経路パス
+
+このルートパスは "a" と一致します。
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+このルートは`蝶々`と`トンボ`にマッチしますが、`蝶々`、`トンボフライマン`などにはマッチしません。
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## ルートパラメータ
+
+ルートパラメータは、URL 内の位置で指定された値をキャプチャするために使用される名前付きの URL セグメントです。 取得した値は `req.params` オブジェクト内に入力され、パス内でそれぞれのキーとして指定されたrouteパラメータの名前が入力されます。
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+ルートパラメータを使用してルートを定義するには、以下のようにルートのパスにルートパラメータを指定します。
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="アラート">
+
+ルートパラメータの名前は、"単語文字" ([A-Za-z0-9_] )で構成されている必要があります。
+
+</Alert>
+
+ハイフン(`-`)とドット(`.`)は文字通り解釈されるので、ルートパラメータとともに便利な目的で使うことができます。
+
+```
+ルートパス: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+ルートパス: /platae/:genus.:species
+リクエスト URL: http://localhost:3000/platae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="アラート">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+route (ルート)パラメータにマッチする正確な文字列をより詳細に制御するには、括弧(`()`)で正規表現を追加します。
+
+```
+ルートパス: /user/:userId(\d+)
+リクエスト URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="警告">
+
+正規表現は通常文字列の一部であるため、 `\`
+文字を追加して、`\d+`などのバックスラッシュをエスケープしてください。
+
+</Alert>
+
+<Alert type="警告">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. 回避策として、`*` の代わりに `{0,}` を使用します。 これはExpress 5で修正される可能性があります。
+</Alert>
+
+## Route handlers
+
+リクエストを処理するために、 [middleware](/en/guide/using-middleware) のように動作する複数のコールバック関数を提供できます。 唯一の例外は、これらのコールバックが `next('route')` を呼び出して、残りのルートコールバックをバイパスすることです。 このメカニズムを使用して、ルート上に事前条件を設定できます。 次に現在のルートを進める理由がなければ次のルートに制御を渡す。
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+この例では:
+
+- `GET /user/5` → 最初のルートで処理 → "User 5" を送信
+- `GET /user/0` → 最初のroute ('route')`を呼び出し、次に一致する `/user/:id\` route (ルート) をスキップします。
+
+ルートハンドラは、次の例に示すように、関数、関数の配列、または両方の組み合わせの形式で使用できます。
+
+単一のコールバック関数はルートを処理できます。 例:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+複数のコールバック関数がルートを処理できます (`next` オブジェクトを指定してください)。 例:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+コールバック関数の配列はルートを処理できます。 例:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+独立した関数と関数の配列の組み合わせは、ルートを処理することができます。 例:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## レスポンスメソッド
+
+次の表のレスポンスオブジェクト (`res`) のメソッドは、クライアントにレスポンスを送信し、リクエスト応答のサイクルを終了することができます。 これらのメソッドのいずれもルートハンドラから呼び出されない場合、クライアントリクエストはハングしたままになります。
+
+| 方法                                          | 説明                                                                               |
+| --------------------------------------------- | ---------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | ダウンロードするファイルを指示します。                                             |
+| [res.end()](/en/5x/api#res.end)               | 応答プロセスを終了します。                                                         |
+| [res.json()](/en/5x/api#res.json)             | JSON 応答を送信します。                                                            |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | JSONP サポートを使用して JSON 応答を送信します。                                   |
+| [res.redirect()](/en/5x/api#res.redirect)     | リダイレクトします。                                                               |
+| [res.render()](/en/5x/api#res.render)         | ビューテンプレートをレンダリングします。                                           |
+| [res.send()](/en/5x/api#res.send)             | さまざまなタイプの応答を送信します。                                               |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | ファイルをオクテットストリームとして送信する。                                     |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | レスポンスステータスコードを設定し、文字列表現をレスポンスボディとして送信します。 |
+
+## app.route()
+
+`app.route()` を使用すると、ルートパスに対してチェーン可能なルートハンドラを作成できます。
+パスは単一の場所で指定されているため、モジュラールートを作成することは、冗長性とタイプミスを削減するのに役立ちます。 ルートの詳細については、以下を参照してください: [Router() documentation](/en/5x/api#router)。
+
+以下は、`app.route()`を使用して定義されたルートハンドラの例です。
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+`express.Router` クラスを使用して、モジュール化されたマウント可能なルートハンドラを作成します。 `Router`インスタンスは完全なミドルウェアとルーティングシステムです。そのため、しばしば「ミニアプリ」と呼ばれます。
+
+次の例では、ルータをモジュールとして作成し、ミドルウェア関数をロードします。 いくつかのルートを定義し、メインアプリのパスにルータモジュールをマウントします。
+
+appディレクトリに`birds.js`という名前のルーターファイルを作成します。以下の内容を使用します。
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+次に、アプリにルーターモジュールをロードします。
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+アプリは `/birds` と `/birds/about` へのリクエストを処理できるようになりました。 同様に、ルート固有の「timeLog」ミドルウェア関数を呼び出します。
+
+ただし、親ルート `/birds` にパスパラメータがある場合、サブルートからデフォルトではアクセスできません。 アクセス可能にするには、 `mergeParams` オプションを Router コンストラクタ [reference](/en/5x/api#app.use) に渡す必要があります。
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/ja/5x/guide/using-middleware.mdx b/src/content/docs/ja/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..18927c340c
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: ミドルウェアの使用
+description: Express.jsアプリケーションでミドルウェアを使用する方法、アプリケーションレベルおよびルータレベルのミドルウェア、エラー処理、サードパーティミドルウェアの統合などを学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express はルーティングおよびミドルウェアの Web フレームワークで、独自の最小限の機能を持っています。Express アプリケーションは、基本的にはミドルウェア関数の一連の呼び出しです。
+
+_Middleware_ 関数は、[request object](/en/5x/api#req) (`req`) にアクセスできる関数です。 [response object](/en/5x/api#res) (`res`) と、アプリケーションのリクエストレスポンスサイクルの次のミドルウェア関数。 次のミドルウェア関数は通常`next`という名前の変数で表されます。
+
+ミドルウェア機能は以下のタスクを実行できます。
+
+- 任意のコードを実行します。
+- リクエストとレスポンスオブジェクトに変更を加えます。
+- リクエストレスポンスサイクルを終了します。
+- スタック内の次のミドルウェア関数を呼び出します。
+
+現在のミドルウェア関数がリクエスト応答サイクルを終了しない場合は、次のミドルウェア関数に制御を渡すために `next()` を呼び出す必要があります。 そうでなければ、リクエストはハングアップのままになります。
+
+Express アプリケーションでは、次のタイプのミドルウェアを使用できます。
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+アプリケーションレベルおよびルーターレベルのミドルウェアは、任意のマウントパスでロードできます。
+また、一連のミドルウェア関数を一緒にロードして、マウントポイントでミドルウェアシステムのサブスタックを作成することもできます。
+
+## アプリケーションレベルのミドルウェア
+
+`app.use()` と `app()` を使用して、アプリケーションレベルのミドルウェアを [app object](/en/5x/api#app) のインスタンスにバインドします。 ETHOD()関数。`METHOD`はミドルウェア関数が小文字で処理するHTTPメソッドです(GET、PUT、POSTなど)。
+
+この例では、マウントパスのないミドルウェア関数を示します。 この関数はアプリがリクエストを受け取るたびに実行されます。
+
+```js
+const express = require('express');
+const app = expresss();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+この例では、`/user/:id` パスにマウントされたミドルウェア関数を示します。 関数は `/user/:id` パス上の任意のタイプの
+HTTP リクエストに対して実行されます。
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+この例ではルートとハンドラ関数(ミドルウェアシステム)を示します。 関数は`/user/:id`パスへのGETリクエストを処理します。
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+次に、マウントパスを持つ一連のミドルウェア関数をマウントポイントにロードする例を示します。
+これは `/user/:id` パスにHTTPリクエスト情報を出力するミドルウェアのサブスタックを示しています。
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+ルートハンドラを使用すると、パスに複数のルートを定義できます。 下の例では、`/user/:id`パスへのGETリクエストに対する2つのルートを定義しています。 2番目のルートは問題を引き起こすことはありませんが、最初のルートはリクエスト応答サイクルを終了するため、呼び出されることはありません。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+他のミドルウェア関数をルータのミドルウェアスタックからスキップするには、次のルートに制御を渡すために `next('route')` を呼び出します。
+
+<Alert type="情報">
+
+`next('route')` は、
+`app.METHOD()` または `router.METHOD()` 関数を使用してロードされたミドルウェア関数でのみ動作します。
+
+</Alert>
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+ミドルウェアは、再利用可能な配列で宣言することもできます。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを持つ配列を示しています。
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## ルーターレベルのミドルウェア
+
+ルータレベルのミドルウェアは、`express.Router()`のインスタンスにバインドされている場合を除き、アプリケーションレベルのミドルウェアと同じ方法で動作します。
+
+```js
+const router = express.Router();
+```
+
+`router.use()`と`router.METHOD()`関数を使ってルーターレベルのミドルウェアをロードします。
+
+次のコード例は、ルーターレベルのミドルウェアを使用して、アプリケーションレベルのミドルウェアに対して上記のミドルウェアシステムを複製します。
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+ルーターのミドルウェア関数の残りをスキップするには、`next('router')`
+を呼び出してルーターインスタンスからコントロールを渡します。
+
+この例では、`/user/:id`パスへのGETリクエストを処理するミドルウェアサブスタックを示します。
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## エラー処理のミドルウェア
+
+<Alert type="アラート">
+
+エラー処理ミドルウェアは常に\_4つの引数を取ります。 エラー処理ミドルウェア関数として
+識別するには、4つの引数を指定する必要があります。 `next`
+オブジェクトを使用しなくても、署名を維持するために指定する必要があります。 Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+他のミドルウェア関数と同じ方法でエラー処理ミドルウェア関数を定義します 3 つの代わりに 4 つの引数を指定する場合を除き、特に \`(err, req, res, next) というシグネチャを使用します。
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+エラー処理ミドルウェアの詳細については、[Error handling](/en/guide/error-handling)を参照してください。
+
+## 組み込みのミドルウェア
+
+バージョン 4.x 以降、Express は [Connect](https://github.com/senchalabs/connect) に依存しなくなりました。 The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express には次のミドルウェア関数が組み込まれています。
+
+- [express.static](/en/5x/api#express.static) は、HTML ファイル、画像などの静的なアセットを提供します。
+- [express.json](/en/5x/api#express.json) は、JSON ペイロードで受信したリクエストを解析します。 \*\*注意: Express 4.16.0+で利用可能
+- [express.urlencoded](/en/5x/api#express.urlencoded) は、URLエンコードされたペイロードで受信するリクエストを解析します。 \*\*注意: Express 4.16.0+で利用可能
+
+## サードパーティのミドルウェア
+
+サードパーティ製ミドルウェアを使用して、Express アプリに機能を追加します。
+
+必要な機能のためにNode.jsモジュールをインストールし、アプリケーション・レベルまたはルータレベルでアプリケーションにロードします。
+
+次の例は、cookie-parser関数`cookie-parser`のインストールとロードを示しています。
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// cookie-parsing middleware
+app.use(cookieParser());
+```
+
+Expressで一般的に使用されるサードパーティミドルウェア関数の部分的なリストについては、[サードパーティミドルウェア](../resources/middleware)を参照してください。
diff --git a/src/content/docs/ja/5x/guide/using-template-engines.mdx b/src/content/docs/ja/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..acc079ae84
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Express でテンプレートエンジンを使用する
+description: Pug、Handlebars、EJSなどのテンプレートエンジンをExpress.jsで統合して使用し、動的なHTMLページを効率的にレンダリングする方法をご覧ください。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_template engine_ を使用すると、アプリケーションで静的なテンプレート ファイルを使用できます。 実行時に、テンプレートエンジンはテンプレートファイルの
+変数を実際の値に置き換えます。 をクリックして、テンプレートをクライアントに送信する HTML ファイルに変換します。
+このアプローチにより、HTML ページのデザインが容易になります。
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+テンプレートファイルをレンダリングするには、ジェネレータが作成したデフォルトの `app.js` で、次の[アプリケーション設定プロパティ](/en/4x/api#app.set)を設定します。
+
+- `views` テンプレートファイルがあるディレクトリ。 例: `app.set('views', './views')` 。
+  デフォルトはアプリケーションのルートディレクトリにある `views` ディレクトリです。
+- `viewengine` を使用するテンプレートエンジン。 たとえば、Pugテンプレートエンジンを使用するには、`app.set('view engine', 'pug')`を使います。
+
+次に、対応するテンプレートエンジン npm パッケージをインストールします。例えば、Pug をインストールする場合:
+
+```bash
+$ npm install pig --save
+```
+
+<Alert type="アラート">
+Pug のような Express 準拠のテンプレートエンジンは、 `__express(filePath, options, callback)` という名前の関数、 `res.render()` がテンプレートコードのレンダリングを呼び出す
+をエクスポートします。
+
+一部のテンプレートエンジンはこの規約に従っていません。 [@ladjs/integrate](https://www.npmjs.com/package/@ladjs/consolidate)
+ライブラリは、一般的な Node.js テンプレートエンジンのすべてをマッピングすることによって、この規則に従っており、したがって、Express 内でシームレスに動作します。
+
+</Alert>
+
+ビューエンジンが設定された後、アプリケーションにエンジンを指定したりテンプレートエンジンモジュールをロードしたりする必要はありません。
+Express はモジュールを内部的にロードします。例:
+
+```js
+app.set('view engine', 'pug');
+```
+
+次に、`views`ディレクトリに`index.pug`という名前のパグテンプレートファイルを作成します。
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+`index.pug` ファイルをレンダリングするルートを作成します。 If the `view engine` property is not set,
+you must specify the extension of the `view` file. そうでなければ、それを省略することができます。
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+ホームページへのリクエストを行うと、 `index.pug` ファイルは HTML としてレンダリングされます。
+
+ビューエンジンキャッシュはテンプレートの出力の内容をキャッシュせず、元のテンプレート自体のみキャッシュします。 キャッシュがオンの場合でも、ビューはリクエストごとに再レンダリングされます。
diff --git a/src/content/docs/ja/5x/guide/writing-middleware.mdx b/src/content/docs/ja/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..22e7a1f6d3
--- /dev/null
+++ b/src/content/docs/ja/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Express アプリで使用するミドルウェアを書く
+description: Express.jsアプリケーション用にカスタムミドルウェア関数を作成する方法を学びます。例や、リクエストとレスポンスの処理を強化するためのベストプラクティスなどです。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ 関数は、[request object](/en/5x/api#req) (`req`) にアクセスできる関数です。 [response object](/en/5x/api#res) (`res`)とアプリケーションのリクエストレスポンスサイクルの中の `next` 関数。 `next` 関数はExpressルータ内の関数で、呼び出されたときに現在のミドルウェアを継承してミドルウェアを実行します。
+
+ミドルウェア機能は以下のタスクを実行できます。
+
+- 任意のコードを実行します。
+- リクエストとレスポンスオブジェクトに変更を加えます。
+- リクエストレスポンスサイクルを終了します。
+- スタック内の次のミドルウェアを呼び出します。
+
+現在のミドルウェア関数がリクエスト応答サイクルを終了しない場合は、次のミドルウェア関数に制御を渡すために `next()` を呼び出す必要があります。 そうでなければ、リクエストはハングアップのままになります。
+
+次の図はミドルウェア関数呼び出しの要素を示しています。
+
+![Elements of a middleware function call](/images/express-mw.png)
+
+Express 5以降、Promiseを返すミドルウェア関数はエラーの拒否またはスロー時に「next(value)」を呼び出します。 `next`は、拒否された値またはスローされたエラーで呼び出されます。
+
+## 例
+
+以下は、簡単な「Hello World」エクスプレスアプリケーションの例です。
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### ミドルウェア関数 myLogger
+
+以下は、「myLogger」というミドルウェア関数の簡単な例です。 この関数は、アプリへのリクエストがそれを通過したときに
+"LOGGED" を出力します。 ミドルウェア関数は、`myLogger`という名前の
+変数に割り当てられます。
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="アラート">
+
+上記の `next()` の呼び出しに注目してください。 この関数を呼び出すと、
+アプリケーションで次のミドルウェア関数が呼び出されます。 `next()`関数はノードの一部ではありません。 sまたはExpress APIはミドルウェア関数に渡される3番目の
+引数です。 `next()`関数には、
+という名前が付けられますが、慣習的には常に「next」という名前が付けられています。 混乱を避けるため、常にこの規約を使用してください。
+
+</Alert>
+
+ミドルウェア関数をロードするには、ミドルウェア関数を指定して `app.use()` を呼び出します。
+例えば、次のコードはルートパス(/)の前に`myLogger`ミドルウェア関数をロードします。
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+アプリがリクエストを受け取るたびに、「LOGGED」というメッセージが端末に出力されます。
+
+ミドルウェアのロード順序は重要です。最初にロードされるミドルウェア関数も最初に実行されます。
+
+ルートパスの後に`myLogger`がロードされている場合、リクエストは到達せず、アプリは"LOGGED"を出力しません。 なぜなら、ルートパスのルートハンドラは、リクエスト応答サイクルを終了するからです。
+
+ミドルウェア関数 `myLogger` は単にメッセージを出力します。 次に、`next()`関数を呼び出すことで、スタック内の次のミドルウェア関数にリクエストを渡します。
+
+### ミドルウェア関数requestTime
+
+次に、"requestTime" というミドルウェア関数を作成し、リクエストオブジェクトに `requestTime`
+というプロパティを追加します。
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+アプリは `requestTime` ミドルウェア関数を使用します。 また、ルートのコールバック関数はミドルウェア関数が`req`（リクエストオブジェクト）に追加するプロパティを使用します。
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+アプリのルートにリクエストを送信すると、アプリはブラウザにリクエストのタイムスタンプを表示するようになりました。
+
+### ミドルウェア関数 validateCookies
+
+最後に、入力されたクッキーを検証するミドルウェア機能を作成し、クッキーが無効な場合に400回のレスポンスを送信します。
+
+ここでは、外部非同期サービスで Cookie を検証する機能の例を示します。
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+ここでは、[`cookie-parser`](/en/resources/middleware/cookie-parser) ミドルウェアを使用して、`req`オブジェクトから入ってくるCookieを解析し、それを私たちの`cookieValidator`関数に渡します。 `validateCookies`ミドルウェアは、拒否時に自動的にエラーハンドラをトリガーするPromiseを返します。
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="アラート">
+
+`await cookieValidator(req.cookies)`の後に`next()`が呼び出されることに注意してください。 これにより、
+`cookieValidator` が解決した場合、スタック内の次のミドルウェアが呼ばれます。 If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+リクエストオブジェクト、レスポンスオブジェクト、スタック内の次のミドルウェア関数、そしてノード全体にアクセスできるためです。 s API、ミドルウェア関数の可能性は無限大です。
+
+Express ミドルウェアの詳細については、[Express ミドルウェアを使用する](/en/guide/using-middleware)を参照してください。
+
+## 設定可能なミドルウェア
+
+ミドルウェアの設定が必要な場合は、optionsオブジェクトや他のパラメータを受け付ける関数をエクスポートしてください。 入力パラメータに基づいてミドルウェアの実装を返します。
+
+ファイル: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+ミドルウェアを以下のように使用できるようになりました。
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+構成可能なミドルウェアの例については、 [cookie-session](https://github.com/expressjs/cookie-session) と [compression](https://github.com/expressjs/compression) を参照してください。
diff --git a/src/content/docs/ja/5x/starter/basic-routing.mdx b/src/content/docs/ja/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..a6e98519ec
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: 基本ルーティング
+description: Express.jsアプリケーションでルーティングの基礎を学びます。ルートの定義、HTTPメソッドの処理、Webサーバーのルートハンドラの作成などです。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ は、アプリケーションが特定のエンドポイントに対してどのように応答するかを決定することを指します。 これはURI(またはパス)と特定のHTTPリクエストメソッド(GET、POSTなど)です。
+
+各ルートは、ルートが一致したときに実行される、1つまたは複数のハンドラ関数を持つことができます。
+
+ルート定義は以下の構造をとります:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+場所:
+
+- `app` は `express` のインスタンスです。
+- `METHOD` は [HTTP リクエストメソッド](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods) の小文字です。
+- `PATH` はサーバー上のパスです。
+- `HANDLER` はルートが一致したときに実行される関数です。
+
+<Alert type="アラート">
+
+このチュートリアルでは、`app` という名前の `express` インスタンスが作成され、サーバーが
+動作していることを前提としています。 アプリの作成に慣れていない場合は、Hello world
+exampleを参照してください。
+
+</Alert>
+
+以下の例は、単純なルートの定義を示しています。
+
+ホームページの「Hello World!」に返信:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+ルートルート (`/`) の POST リクエストに応答します。アプリケーションのホームページ:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+`/user`ルートにPUTリクエストに応答します：
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+`/user`ルートへのDELETEリクエストに対応:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/ja/5x/starter/examples.mdx b/src/content/docs/ja/5x/starter/examples.mdx
new file mode 100644
index 0000000000..f95e9eeba1
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: エクスプレス例
+description: さまざまなユースケース、インテグレーション、高度な構成を網羅した Express.jsアプリケーション例のコレクションをご覧ください。プロジェクトの学習と構築に役立ちます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+このページには、Express を使用した例のリストがあります。
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - ログインとパスワードによる認証
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - HTTP コンテンツネゴシエーション
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - クッキーベースのセッションの操作
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - クッキーの操作
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - クライアントへのファイルの転送
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - 埋め込みJavaScriptテンプレートの操作 (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - エラーページの作成
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - エラーミドルウェアの操作
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - シンプルなリクエストハンドラ。
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown as template engine.
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - 複数のエクスプレスルーターでの作業
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - MVCスタイル コントローラ
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - オンラインユーザーアクティビティを`オンライン`と`redis`パッケージで追跡
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - ルートパラメータの操作
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - 同じリソースに対する複数の HTTP 操作
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - 地図を使ってルートを整理する
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - route middleware の操作
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - 各リソースごとにルートを整理する
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - ユーザーセッション
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - 静的ファイルの提供
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - 仮想ホストでの作業
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - ビューを動的にレンダリングする
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - ミドルウェア呼び出し間でリクエストオブジェクトにデータを保存する
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Simple API service
+
+## その他の例
+
+これらは、より広範な統合を伴ういくつかの追加の例です。
+
+<Alert type="警告">
+
+この情報は、
+Expressjsチームがメンテナンスしていないサードパーティのサイト、製品、またはモジュールを指します。 ここでの掲載は、
+Expressjsプロジェクトチームの推奨または推奨を構成するものではありません。
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - ORMとしてExpressとNext.jsを使用したフルスタックアプリ [Prisma](https://www.npmjs.com/package/prisma)
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - ORMとして [Prisma](https://www.npmjs.com/package/prisma) を使用する Express をTypeScript で REST API
diff --git a/src/content/docs/ja/5x/starter/faq.md b/src/content/docs/ja/5x/starter/faq.md
new file mode 100644
index 0000000000..89d34a303a
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Express.jsについてよく寄せられる質問の答えを見つけましょう。その中には、アプリケーション構造、モデル、認証、テンプレートエンジン、エラー処理などのトピックが含まれます。
+---
+
+## アプリケーションを構成するにはどうすればいいですか?
+
+この質問には決定的な答えはありません。 The answer depends
+on the scale of your application and the team that is involved. 可能な限り
+柔軟性を持たせるために、Expressは構造的な仮定をしません。
+
+ルートやその他のアプリケーション固有のロジックは、任意のディレクトリ構造において、
+好きな数のファイルに保存することができます。 View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+また、Express 用のサードパーティの拡張機能もあり、これらのパターンのいくつかを簡素化します。
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## モデルを定義するにはどうすればいいですか?
+
+Express にはデータベースという概念はありません。 このコンセプトは
+サードパーティ製の Node モジュールに残されており、ほぼすべてのデータベースと
+インターフェイスを使用できます。
+
+モデルを中心とした Express ベースのフレームワークについては [LoopBack](http://loopback.io) を参照してください。
+
+## どのようにユーザーを認証できますか?
+
+Authentication is another opinionated area that Express does not
+venture into. 任意の認証スキームを使用できます。
+単純なユーザー名/パスワードスキームについては、[この例](https://github.com/expressjs/express/tree/master/examples/auth)を参照してください。
+
+## Expressはどのテンプレートエンジンをサポートしていますか?
+
+Express は、\`(path, local, callback) 署名に適合するテンプレートエンジンをサポートしています。
+テンプレートエンジンインターフェイスとキャッシュを正規化するには、
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+プロジェクトをサポートしてください。 リストされていないテンプレートエンジンは引き続きExpress 署名をサポートする可能性があります。
+
+詳しくは、[Expressでテンプレートエンジンを使用する](/en/guide/using-template-engines)を参照してください。
+
+## 404応答はどのように処理すればいいですか?
+
+Expressでは404応答はエラーの結果ではないため、
+エラーハンドラミドルウェアはそれらを捕捉しません。 This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+`express.Router()`
+のインスタンスで実行時にルートを動的に追加することで、ルートはミドルウェア関数に取って代わられません。
+
+## エラーハンドラの設定方法は?
+
+他のミドルウェアと同じ方法でエラー処理ミドルウェア
+を定義します。ただし、3つではなく4つの引数を使用します。 具体的にはシグネチャ`(err, req, res, next)`を指定します。
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+詳細については、[Error handling](/en/guide/error-handling)を参照してください。
+
+## プレーンHTMLをレンダリングするにはどうすればいいですか?
+
+違います！ `res.render()`関数でHTMLを「レンダリング」する必要はありません。
+特定のファイルがある場合は、 `res.sendFile()` 関数を使用します。
+ディレクトリから多くのアセットを提供している場合は、`express.static()`
+ミドルウェア関数を使用してください。
+
+## Express にはどのバージョンの Node.js が必要ですか?
+
+- [Express 4.x](/en/4x/api) では、Node.js 0.10 以上が必要です。
+- Express 5.x](/en/5x/api) ではNode.js 18 以上が必要です。
diff --git a/src/content/docs/ja/5x/starter/generator.mdx b/src/content/docs/ja/5x/starter/generator.mdx
new file mode 100644
index 0000000000..13c433e806
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express アプリケーションジェネレーター
+description: Expressアプリケーションジェネレータツールを使用して、Express.jsアプリケーション用のスケルトンを迅速に作成し、セットアップと構成を合理化する方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+アプリケーションジェネレータツール`express-generator`を使用して、アプリケーションスケルトンを素早く作成します。
+
+アプリケーションジェネレータは `npx` コマンド (Node.js 8.2.0で利用可能) で実行できます。
+
+```bash
+$ npx express-generator
+```
+
+以前のNodeバージョンの場合は、アプリケーションジェネレータをグローバルnpmパッケージとしてインストールしてから起動します。
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+`-h` オプションでコマンドオプションを表示します。
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+例えば、次のように、_myapp_ という名前の Express アプリケーションを作成します。 アプリは現在の作業ディレクトリの _myapp_ というフォルダに作成され、ビューエンジンは <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a> に設定されます。
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+次に依存関係をインストール:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+MacOS または Linux では、次のコマンドでアプリを実行します。
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+Windows コマンドプロンプトでは、次のコマンドを使用します。
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+Windows PowerShell では、次のコマンドを使用します。
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+次に、ブラウザに`http://localhost:3000/`を読み込んでアプリにアクセスします。
+
+生成されたアプリには、次のディレクトリ構造があります。
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="情報">
+
+ジェネレータによって作成されたアプリ構造は、Express アプリケーションを構成するための多くの方法の1つに過ぎません。
+自由にこの構造を使用するか、あなたのニーズに最適に変更してください。
+
+</Alert>
diff --git a/src/content/docs/ja/5x/starter/hello-world.mdx b/src/content/docs/ja/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..369821bf38
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Express.jsを始めるには、シンプルな「Hello World」アプリケーションを構築しましょう。初心者向けの基本的なセットアップとサーバー作成を説明します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="情報">
+
+以下に埋め込まれているのは、基本的に作成できる最も簡単なExpressアプリです。 It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+このアプリはサーバーを起動し、接続のためにポート3000をリッスンします。 アプリはルート URL (`/`) または _route_ にリクエスト
+を返します。 他のすべてのパスについては、**404 Not Found**で応答します。
+
+## ローカルで実行中
+
+最初に `myapp` という名前のディレクトリを作成し、変更して `npm init` を実行します。 Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+`myapp` ディレクトリで、`app.js`という名前のファイルを作成し、上の例からコードをコピーします。
+
+<Alert type="アラート">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+次のコマンドでアプリを実行します。
+
+```bash
+$ node app.js
+```
+
+次に、ブラウザーに `http://localhost:3000/` をロードして出力を確認します。
diff --git a/src/content/docs/ja/5x/starter/installing.mdx b/src/content/docs/ja/5x/starter/installing.mdx
new file mode 100644
index 0000000000..ff591af0bb
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: インストール中
+description: プロジェクトディレクトリの設定やnpmとの依存関係の管理など、Node.js 環境で Express.js をインストールする方法を学びます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+始める前に、 [Node.js](https://nodejs.org/) 18 以上のインストールがあることを確認してください。 次に、アプリケーションのディレクトリを作成し、その中に移動します。
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+`npm init` コマンドを使用して、アプリケーション用の `package.json` ファイルを作成します。
+`package.json` がどのように動作するかについては、[npm の package.json handling](https://docs.npmjs.com/files/package.json) を参照してください。
+
+```bash
+npm init
+```
+
+このコマンドを実行すると、アプリケーションの名前やバージョンなど、さまざまなものが表示されます。
+今のところ、RETURNを押すと、ほとんどのデフォルトを受け入れることができます。以下の例外があります。
+
+```
+エントリ ポイント: (index.js)
+```
+
+`app.js`、またはメインファイルの名前を何でも入力します。 `index.js`にしたい場合は、RETURNを押して、推奨されるデフォルトのファイル名を受け入れます。
+
+次に、Expressを`myapp`ディレクトリにインストールし、依存関係リストに保存します。 例:
+
+```bash
+npm install Express
+```
+
+Express を一時的にインストールし、依存関係リストに追加しないでください。
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/ja/5x/starter/static-files.mdx b/src/content/docs/ja/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..b72aad560c
--- /dev/null
+++ b/src/content/docs/ja/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Express での静的ファイルの提供
+description: 組み込みの 'static' ミドルウェアを使用して、Express.js アプリケーションで画像、CSS、JavaScript などの静的ファイルを提供する方法を理解します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+画像、CSSファイル、JavaScriptファイルなどの静的ファイルを提供するには、Express で組み込まれているミドルウェア関数「express.static」を使用します。
+
+関数の署名は次のとおりです:
+
+```js
+express.static(root, [options]);
+```
+
+`root` 引数は、静的アセットを提供するルートディレクトリを指定します。
+引数 `options` の詳細については、 [express.static](/en/5x/api#express.static) を参照してください。
+
+例えば、`public`という名前のディレクトリに画像、CSSファイル、JavaScriptファイルを表示するには、次のコードを使用します。
+
+```js
+app.use(express.static('public'));
+```
+
+`public` ディレクトリにあるファイルを読み込むことができます。
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="情報">
+
+Express は静的ディレクトリからの相対的なファイルを検索するので、静的ディレクトリ
+の名前は URL の一部ではありません。
+
+</Alert>
+
+複数の静的アセットディレクトリを使用するには、`express.static` ミドルウェア関数を複数回呼び出します。
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express は、`express.static` ミドルウェア関数で静的ディレクトリを設定する順序でファイルを検索します。
+
+<Alert type="情報">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+\`expressで提供されるファイルに対して、仮想パスプレフィックス(ファイルシステム内にパスが実際に存在しない場所)を作成します。 以下に示すように、staticディレクトリの[mount path](/en/5x/api#app.use)を指定します。
+
+```js
+app.use('/static', express.static('public'));
+```
+
+`/static` というプレフィックスから、 `public` ディレクトリにあるファイルをロードできます。
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+しかし、`express.static`関数に与えるパスは、`node`プロセスを起動したディレクトリからの相対パスです。 expressアプリを別のディレクトリから実行する場合、提供したいディレクトリの絶対パスを使用する方が安全です:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+`serve-static` 関数とそのオプションの詳細については、 [serve-static](/en/resources/middleware/serve-static) を参照してください。
diff --git a/src/content/docs/ko/4x/advanced/developing-template-engines.md b/src/content/docs/ko/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/ko/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/ko/4x/guide/behind-proxies.mdx b/src/content/docs/ko/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/ko/4x/guide/debugging.mdx b/src/content/docs/ko/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/ko/4x/guide/error-handling.mdx b/src/content/docs/ko/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/ko/4x/guide/overriding-express-api.md b/src/content/docs/ko/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/ko/4x/guide/routing.mdx b/src/content/docs/ko/4x/guide/routing.mdx
new file mode 100644
index 0000000000..930e7b8438
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/5x/api#app.METHOD). You can also use [app.all()](/en/5x/api#app.all) to handle all HTTP methods and [app.use()](/en/5x/api#app.use) to
+specify middleware as the callback function (See [Using middleware](/en/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/5x/api#app.METHOD).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
+
+<Alert type="alert">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="alert">
+
+In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route
+paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+### Route paths based on strings
+
+This route path will match requests to the root route, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+This route path will match requests to `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+This route path will match requests to `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Route paths based on string patterns
+
+<Alert type="alert">
+
+The string patterns in Express 5 no longer work. Please refer to the migration
+guide for more information.
+
+</Alert>
+
+This route path will match `acd` and `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+This route path will match `/abe` and `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Route paths based on regular expressions
+
+This route path will match anything with an "a" in it.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alert">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
+
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warning">
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\`
+characters with an additional backslash, for example `\d+`.
+
+</Alert>
+
+<Alert type="warning">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                        | Description                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/5x/api#res.end)               | End the response process.                                                             |
+| [res.json()](/en/5x/api#res.json)             | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirect a request.                                                                   |
+| [res.render()](/en/5x/api#res.render)         | Render a view template.                                                               |
+| [res.send()](/en/5x/api#res.send)             | Send a response of various types.                                                     |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/5x/api#router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/ko/4x/guide/using-middleware.mdx b/src/content/docs/ko/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/ko/4x/guide/using-template-engines.mdx b/src/content/docs/ko/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/ko/4x/guide/writing-middleware.mdx b/src/content/docs/ko/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..3849cfe1fa
--- /dev/null
+++ b/src/content/docs/ko/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+<div class="table-scroller">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">HTTP method for which the middleware function applies.</div>
+
+<div class="callout" id="callout2">
+  Path (route) for which the middleware function applies.
+</div>
+
+<div class="callout" id="callout3">
+  The middleware function.
+</div>
+
+<div class="callout" id="callout4">
+  Callback argument to the middleware function, called "next" by convention.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">response</a> argument to the middleware function, called "res" by
+  convention.
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">request</a> argument to the middleware function, called "req" by convention.</div>
+</td>
+</tr>
+</table>
+</div>
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/ko/4x/starter/basic-routing.mdx b/src/content/docs/ko/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..73c12f3893
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the Hello world
+example.
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/ko/4x/starter/examples.mdx b/src/content/docs/ko/4x/starter/examples.mdx
new file mode 100644
index 0000000000..6685b9cbe4
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+  This information refers to third-party sites, products, or modules that are not maintained by the
+  Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+  Expressjs project team.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/ko/4x/starter/faq.md b/src/content/docs/ko/4x/starter/faq.md
new file mode 100644
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/ko/4x/starter/generator.mdx b/src/content/docs/ko/4x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/ko/4x/starter/hello-world.mdx b/src/content/docs/ko/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/ko/4x/starter/installing.mdx b/src/content/docs/ko/4x/starter/installing.mdx
new file mode 100644
index 0000000000..fc66c7f9df
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 0.10 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="info">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Then, afterwards, running `npm install` in the app directory will automatically
+install modules in the dependencies list.
+
+</Alert>
diff --git a/src/content/docs/ko/4x/starter/static-files.mdx b/src/content/docs/ko/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..98855e0d05
--- /dev/null
+++ b/src/content/docs/ko/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/ko/5x/advanced/developing-template-engines.md b/src/content/docs/ko/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/ko/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/ko/5x/guide/behind-proxies.mdx b/src/content/docs/ko/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/ko/5x/guide/debugging.mdx b/src/content/docs/ko/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/ko/5x/guide/error-handling.mdx b/src/content/docs/ko/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/ko/5x/guide/overriding-express-api.md b/src/content/docs/ko/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/ko/5x/guide/routing.mdx b/src/content/docs/ko/5x/guide/routing.mdx
new file mode 100644
index 0000000000..930e7b8438
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/5x/api#app.METHOD). You can also use [app.all()](/en/5x/api#app.all) to handle all HTTP methods and [app.use()](/en/5x/api#app.use) to
+specify middleware as the callback function (See [Using middleware](/en/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/5x/api#app.METHOD).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
+
+<Alert type="alert">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="alert">
+
+In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route
+paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+### Route paths based on strings
+
+This route path will match requests to the root route, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+This route path will match requests to `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+This route path will match requests to `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Route paths based on string patterns
+
+<Alert type="alert">
+
+The string patterns in Express 5 no longer work. Please refer to the migration
+guide for more information.
+
+</Alert>
+
+This route path will match `acd` and `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+This route path will match `/abe` and `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Route paths based on regular expressions
+
+This route path will match anything with an "a" in it.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alert">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
+
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warning">
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\`
+characters with an additional backslash, for example `\d+`.
+
+</Alert>
+
+<Alert type="warning">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                        | Description                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/5x/api#res.end)               | End the response process.                                                             |
+| [res.json()](/en/5x/api#res.json)             | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirect a request.                                                                   |
+| [res.render()](/en/5x/api#res.render)         | Render a view template.                                                               |
+| [res.send()](/en/5x/api#res.send)             | Send a response of various types.                                                     |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/5x/api#router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/ko/5x/guide/using-middleware.mdx b/src/content/docs/ko/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/ko/5x/guide/using-template-engines.mdx b/src/content/docs/ko/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/ko/5x/guide/writing-middleware.mdx b/src/content/docs/ko/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..507c3ac06a
--- /dev/null
+++ b/src/content/docs/ko/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+![Elements of a middleware function call](/images/express-mw.png)
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/ko/5x/starter/basic-routing.mdx b/src/content/docs/ko/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..73c12f3893
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the Hello world
+example.
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/ko/5x/starter/examples.mdx b/src/content/docs/ko/5x/starter/examples.mdx
new file mode 100644
index 0000000000..69f410e908
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+This page contains list of examples using Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+
+This information refers to third-party sites, products, or modules that are not maintained by the
+Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+Expressjs project team.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/ko/5x/starter/faq.md b/src/content/docs/ko/5x/starter/faq.md
new file mode 100644
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/ko/5x/starter/generator.mdx b/src/content/docs/ko/5x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/ko/5x/starter/hello-world.mdx b/src/content/docs/ko/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/ko/5x/starter/installing.mdx b/src/content/docs/ko/5x/starter/installing.mdx
new file mode 100644
index 0000000000..f6dc8220d4
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 18 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/ko/5x/starter/static-files.mdx b/src/content/docs/ko/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..98855e0d05
--- /dev/null
+++ b/src/content/docs/ko/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/pt-br/4x/advanced/developing-template-engines.md b/src/content/docs/pt-br/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..8b379a6f50
--- /dev/null
+++ b/src/content/docs/pt-br/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Desenvolvendo modelos de motores para Express
+description: Aprenda a desenvolver motores de modelos personalizados para Express.js usando app.engine(), com exemplos sobre como criar e integrar sua própria lógica de renderização de templates.
+---
+
+Use o método `app.engine(ext, callback)` para criar o seu próprio motor de templates. `ext` refere-se à extensão de arquivo, e `callback` é a função template engine que aceita os seguintes itens como parâmetros: a localização do arquivo, o objeto de opções e a função de retorno de chamada.
+
+O código a seguir é um exemplo de implementação de um mecanismo muito simples de template para renderizar arquivos `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Seu aplicativo poderá renderizar arquivos `.ntl`. Crie um arquivo chamado `index.ntl` no diretório `views` com o seguinte conteúdo.
+
+```pug
+#title#
+#message#
+```
+
+Em seguida, crie a seguinte rota no seu app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando você fizer uma solicitação à página inicial, `index.ntl` será processado como HTML.
diff --git a/src/content/docs/pt-br/4x/guide/behind-proxies.mdx b/src/content/docs/pt-br/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..e6a72e5cad
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/behind-proxies.mdx
@@ -0,0 +1,103 @@
+---
+title: Expresso atrás dos proxies
+description: Aprenda a configurar os aplicativos Express.js para funcionar corretamente atrás de proxies reversas, incluindo o uso do proxy confiável para manipular endereços IP do cliente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Ao executar um app Expresso atrás de um proxy reverso, alguns das APIs Express podem retornar valores diferentes do esperado. A fim de se ajustar para isto, a configuração do aplicativo `trust proxy` pode ser usada para expor informações fornecidas pelo proxy reverso na API Express. O problema mais comum é expressar APIs que expõem o endereço IP do cliente pode mostrar um endereço IP interno do proxy inverso.
+
+<Alert type="informações">
+
+Ao configurar a configuração `proxy confiável`, é importante entender a configuração exata do proxy reverso
+. Como esta configuração confiará nos valores fornecidos na solicitação, é importante que
+a combinação da configuração no Express corresponda a como o proxy reverso funciona.
+
+</Alert>
+
+A configuração do aplicativo 'proxy confiável' pode ser definida para um dos valores listados na tabela a seguir.
+
+<table class="Docável" border="1" markdown="1">
+  <thead><tr><th>Digite</th><th>Valor</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Se `true`, o endereço IP do cliente é entendido como a entrada mais à esquerda no cabeçalho `X-Forwarded-For`.
+
+Se `false`, o aplicativo é entendido como diretamente virado para o cliente e o endereço IP do cliente é derivado de `req.socket.remoteAddress`. Esta é a configuração padrão.
+
+<Alert type="advertência">
+Ao definir como `true`, é importante garantir que o último proxy reverso confiável esteja removendo/substituindo todos os seguintes cabeçalhos HTTP: `X-Forwarded-for`, `X-Forwarded-Host` e `X-Forwarded-Proto`, caso contrário, pode ser possível que o cliente forneça qualquer valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>endereços IP</td>
+<td markdown="1">
+Um endereço IP, subnet ou uma matriz de endereços IP e subnets para confiar como sendo um proxy reverso. A seguinte lista mostra os nomes das sub-redes pré-configuradas:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Você pode definir endereços IP das seguintes maneiras:
+
+```js
+app.set('trust proxy', 'loopback'); // especifica um subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // especifica um subnet e um aplicativo de endereço
+. et('proxy de confiança', 'loopback, linklocal, uniquelocal'); // especificar múltiplas subnets como CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // especificar várias subnets como um array
+```
+
+Quando especificado, os endereços IP ou as subredes são excluídos do processo de determinação de endereço, e o endereço IP não confiável mais próximo do servidor de aplicativos é definido como o endereço IP do cliente. Isto funciona verificando se 'req.socket.remoteAddress' é confiável. Em caso afirmativo, então cada endereço em `X-Forwarded-For` é verificado da direita para a esquerda até o primeiro endereço não confiável.
+
+</td>
+    </tr>
+    <tr>
+      <td>Número</td>
+<td markdown="1">
+Use o endereço que, no máximo, está fora do número de hops do aplicativo Express. `req.socket.remoteAddress` é o primeiro hop, e o resto é procurado no cabeçalho `X-Forwarded-for` da direita para a esquerda. Um valor de `0` significa que o primeiro endereço não confiável seria `req.socket.remoteAddress`, ou seja, não há um proxy reverso.
+
+<Alert type="advertência">
+Ao usar esta configuração, é importante garantir que não haja vários, caminhos de comprimento diferente para o aplicativo Express, para que o cliente possa ser menor que o número configurado de saltos de distância, caso contrário, poderá ser possível que o cliente forneça qualquer valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Função</td>
+<td markdown="1">
+Execução de confiança personalizada.
+
+```js
+app.set('proxy de confiança', (ip) => {
+  if (ip === '127.0.0.1' ├ip === '123.123.123. 23')
+    return true; // IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Habilitar `trust proxy` terá o seguinte impacto:
+
+<ul>
+  <li markdown="1">
+    O valor de [req.hostname](/en/api#req.hostname) é derivado do valor definido no cabeçalho
+    `X-Forwarded-Host`, que pode ser configurado pelo cliente ou pelo proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` pode ser configurado pelo proxy reverso para dizer ao aplicativo se ele é
+    `https` ou `http` ou até mesmo um nome inválido. Este valor é refletido por
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Os valores [req.ip](/en/api#req.ip) e [req.ips](/en/api#req.ips) são preenchidos com base no
+    cabeçalho do socket e `X-Forwarded-For`, iniciando no primeiro endereço não confiável.
+  </li>
+</ul>
+
+A configuração `trust proxy` é implementada usando o pacote [proxy-addr](https://www.npmjs.com/package/proxy-addr). Para obter mais informações, consulte a documentação.
diff --git a/src/content/docs/pt-br/4x/guide/debugging.mdx b/src/content/docs/pt-br/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..66690a4946
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Expresso de depuração
+description: Aprenda a habilitar e usar logs de depuração nos aplicativos Express.js definindo a variável de ambiente DEBUG para melhorar a solução de problemas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para ver todos os logs internos usados no Express, defina a variável de ambiente `DEBUG` para
+`express:*` ao iniciar seu aplicativo.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+No Windows, use o comando correspondente.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Executar este comando no aplicativo padrão gerado pelo [gerador expresso](/en/starter/generator) imprime a seguinte saída:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Quando um pedido for feito ao aplicativo, você verá os logs especificados no código Expresso:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Para ver os logs apenas da implementação do roteador, defina o valor de `DEBUG` para `express:router`. Da mesma forma, para ver apenas os logs da implementação do aplicativo, defina o valor de `DEBUG` para `express:application`, e assim por diante.
+
+## Aplicações geradas por `express`
+
+Uma aplicação gerada pelo comando `express` usa o módulo `debug` e seu namespace de depuração é escopo para o nome da aplicação.
+
+Por exemplo, se você gerou o app com `$ express sample-app`, você pode ativar as instruções de depuração com o seguinte comando:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+Você pode especificar mais de um namespace de depuração atribuindo uma lista de nomes separada por vírgulas:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Opções avançadas
+
+Ao executar através do Node.js, você pode definir algumas variáveis de ambiente que irão mudar o comportamento do log de depuração:
+
+| Nome:               | Objetivo                                                 |
+| ------------------- | -------------------------------------------------------- |
+| `DEBUG`             | Habilita/desabilita namespace específicos de depuração.  |
+| `DEBUG_COLORS`      | Usar ou não cores na saída de depuração.                 |
+| DEBUG_DEPTH\`       | Profundidade da inspeção de objeto.                      |
+| `DEBUG_FD`          | Descritor de arquivo para escrever a saída de depuração. |
+| `DEBUG_SHOW_HIDDEN` | Mostra propriedades ocultas em objetos inspecionados.    |
+
+<Alert type="informações">
+
+As variáveis de ambiente começando com `DEBUG_` acabam sendo convertidas em um objeto de Opções
+que é usado com formatos `%o`/`%O`. Veja a documentação do Node.js sobre
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) para a lista
+completa.
+
+</Alert>
diff --git a/src/content/docs/pt-br/4x/guide/error-handling.mdx b/src/content/docs/pt-br/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..0cd431d89c
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Tratamento de erros
+description: Entenda como o Express.js lida com erros em código síncrono e assíncrono e aprenda a implementar erro personalizado de manipulação de intermediários para seus aplicativos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Tratamento de erros_ refere-se a como as capturas Expressas e processa erros que
+ocorrem de forma sincronizada e assíncrona. Expresso vem com um erro padrão
+manipulador para que você não precise escrever seu próprio para começar.
+
+## Capturando Erros
+
+É importante garantir que Expresso pegue todos os erros que ocorrem enquanto
+rodando manipuladores de rotas e intermediários.
+
+Erros que ocorrem no código síncrono dentro dos manipuladores de rota e middleware
+não exigem trabalho extra. If synchronous code throws an error, then Express will
+catch and process it. Por exemplo:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Expresso irá pegar isso sozinho.
+});
+```
+
+Para erros retornados de funções assíncronas, invocados pelos manipuladores de rota
+e intermediário, você deve passá-los para a função `next()`, onde o Express irá capturá-los a
+e processá-los. Por exemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-existente', (err, data) => {
+    if (err) {
+      next(err); // Passa os erros para o Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+Começando pelo Express 5, roteadores e intermediários que retornam um Promise
+chamarão `next(value)` automaticamente quando eles rejeitarem ou lançarem um erro.
+Por exemplo:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Se `getUserById` lança um erro ou rejeita, `next` será chamado com
+o erro lançado ou o valor rejeitado. Se nenhum valor rejeitado for fornecido, `next`
+será chamado com um objeto de erro padrão fornecido pelo roteador Express.
+
+Se você passar qualquer coisa para a função `next()` (exceto a string `'route'`),
+Expressa que a requisição atual é um erro e irá pular quaisquer funções
+restantes que não sejam de manipulação de erros e middleware.
+
+Se o callback em uma sequência não fornecer dados, somente erros, você pode simplificar
+este código da seguinte forma:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+No exemplo acima, `next` é fornecido como o callback para `fs.writeFile`,
+que é chamado com ou sem erros. Se não houver erro, o segundo receptor
+é executado, caso contrário as pegadas do Express e processa o erro.
+
+Você deve capturar os erros que ocorrem em código assíncrono invocado pelos manipuladores da rota ou
+middleware e passá-los para o Expresso para processamento. Por exemplo:
+
+```js
+app.get('/', (q, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      ext(err);
+    }
+  }, 100);
+});
+```
+
+O exemplo acima usa um bloco `tentar... catch` para capturar erros no código assíncrono
+e passá-los para o Express. Se o bloco `tentar...catch`
+fosse omitido, Express não pegaria o erro, uma vez que ele não faz parte do código de manipulador
+síncrono.
+
+Use promessas para evitar a sobrecarga do bloco `tentar... capturar` ou ao usar funções
+que retornam promessas. Por exemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    . hen(() => {
+      joga novo Error('BROKEN');
+    })
+    . atch(next); // Erros serão passados para o Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+Você também pode usar uma cadeia de manipuladores para confiar em erro síncrono
+de recuperação, reduzindo o código assíncrono a algo trivial. Por exemplo:
+
+```js
+app.get('/', [
+  função (req, res, ext) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = data;
+      ext(err);
+    });
+  },
+  função (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+O exemplo acima tem algumas declarações triviais da chamada `readFile`
+. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Então, o exemplo acima tenta processar os dados. Se isso falhar, o manipulador de erro
+síncrono irá pegá-lo. Se você tivesse feito este processamento dentro do
+o callback `readFile`, então o aplicativo poderia sair e o erro Express
+manipuladores não executariam.
+
+Seja qual for o método que você usar, se você quer que os manipuladores de erro Expressos sejam chamados para dentro e o aplicativo
+para sobreviver, você deve garantir que o Expresso receba o erro.
+
+## O manipulador de erro padrão
+
+Expresso vem com um manipulador de erro embutido que cuida de quaisquer erros que possam ser encontrados no aplicativo. Esta função de middleware com erros padrão é adicionada no final da função middleware stack.
+
+Se você passar um erro para `next()` e não lidar com ele em um erro personalizado
+handler, será tratado pelo manipulador de erro embutido; o erro será
+escrito no cliente com o rastreamento de pilha. O rastreamento da pilha não está incluído
+no ambiente de produção.
+
+<Alert type="informações">
+
+Defina a variável de ambiente `NODE_ENV` como `production`, para executar o aplicativo em modo de produção.
+
+</Alert>
+
+Quando um erro é escrito, a seguinte informação é adicionada a
+resposta:
+
+- O `res.statusCode` é definido em `err.status` (ou `err.statusCode`). Se
+  este valor estiver fora do intervalo de 4xx ou 5xx, ele será definido como 500.
+- A mensagem 'res.statusMessage' é definida de acordo com o código de status.
+- O corpo será o HTML da mensagem do código de status quando em produção
+  ambiente, caso contrário será `err.stack`.
+- Qualquer cabeçalho especificado em um objeto `err.headers`.
+
+Se você chamar `next()` com um erro depois que você começou a escrever a
+resposta (por exemplo, se você encontrar um erro ao transmitir a resposta
+ao cliente), o Express default error handler fecha a conexão
+e falha na solicitação.
+
+Então, quando você adicionar um manipulador de erro personalizado, você deve delegar para
+o manipulador de erro padrão Express, quando os cabeçalhos
+já foram enviados para o cliente:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Observe que o manipulador de erro padrão pode ser acionado se você chamar `next()` com um erro
+no seu código mais de uma vez. Mesmo que um erro personalizado de manipulação de middleware esteja no lugar.
+
+Outro erro de manipulação de middleware pode ser encontrado em [Express middleware](/en/resources/middleware).
+
+## Escrevendo manipuladores de erros
+
+Definir funções intermediárias de manipulação de erros da mesma forma que outras funções de middleware,
+exceto funções de manipulação de erro possuem quatro argumentos ao invés de três:
+`(err, req, res, next)`. Por exemplo:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo quebrado!');
+});
+```
+
+Você define o middleware de erro duramente, depois de outro `app.use()` e roteia chamadas; por exemplo:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extendido: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // lógica
+});
+```
+
+As respostas de dentro de uma função middleware podem estar em qualquer formato, como uma página de erro HTML, uma mensagem simples ou uma string JSON.
+
+Para fins de estrutura organizacional (e de nível superior), você pode definir
+várias funções de middleware com manipulação de erros, tanto quanto você poderia com funções de intermediário
+regulares. Por exemplo, para definir um manipulador de erro
+para solicitações feitas usando `XHR` e aqueles sem:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extendido: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, ext) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Também neste exemplo, `clientErrorHandler` é definido como segue; neste caso, o erro é explicitamente passado para o próximo.
+
+Observe que quando _não_ estiver chamando "próximo" em uma função de manipulação de erros, você é responsável por escrever (e terminar) a resposta. Caso contrário, esses pedidos ficarão "pendentes" e não serão elegíveis para a recolha de lixo.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Algo falhou!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementar a função "catch-all" `errorHandler` da seguinte forma (por exemplo):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Se você tiver um gerenciador de rotas com múltiplas funções de retorno de chamada, você pode usar o parâmetro `rota` para pular para o próximo manipulador de rota. Por exemplo:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user. asPaid) {
+      // continue lidando com esta requisição
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent. ind((err, doc) => {
+      se (err) retornar next(err);
+      res. son(doc);
+    });
+  }
+);
+```
+
+Neste exemplo, o manipulador `getPaidContent` será ignorado, mas quaisquer manipuladores restantes em `app` para `/a_route_behind_paywall` continuariam sendo executados.
+
+<Alert type="informações">
+
+Chama para `next()` e `next(err)` indicam que o manipulador atual está completo e em que estado.
+`next(err)` pulará todos os manipuladores restantes na cadeia, exceto aqueles que estão configurados para
+lidar com erros conforme descrito acima.
+
+</Alert>
diff --git a/src/content/docs/pt-br/4x/guide/overriding-express-api.md b/src/content/docs/pt-br/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..d5ceef01af
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Sobrescrevendo a API Expresso
+description: Descubra como personalizar e estender a API do Express.js substituindo métodos e propriedades nos objetos de solicitação e resposta usando protótipos.
+---
+
+A API do Expresso consiste de vários métodos e propriedades nos objetos de solicitação e resposta. Estas são herdadas pelo protótipo. Há dois pontos de extensão para a API Express:
+
+1. Os protótipos globais em `express.request` e `express.response`.
+2. Protótipos específicos de aplicativo em `app.request` e `app.response`.
+
+Alterar os protótipos globais afetará todos os aplicativos do Express carregados no mesmo processo. Se desejar, alterações podem ser feitas especificamente no aplicativo, alterando apenas os protótipos específicos do aplicativo após criar um novo aplicativo.
+
+## Métodos
+
+Você pode substituir a assinatura e o comportamento dos métodos existentes com o seu próprio, atribuindo uma função personalizada.
+
+A seguir é um exemplo de substituição do comportamento de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+A implementação acima altera completamente a assinatura original de `res.sendStatus`. Agora aceita um código de estado, um tipo de codificação e a mensagem a ser enviada ao cliente.
+
+O método sobrescrito agora pode ser usado dessa maneira:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## propriedades
+
+As propriedades da API Expresso também são:
+
+1. Propriedades atribuídas (ex: `req.baseUrl`, `req.originalUrl`)
+2. Definido como getters (ex: `req.secure`, `req.ip`)
+
+Uma vez que as propriedades da categoria 1 são dinamicamente atribuídas aos objetos `request` e `response` no contexto do ciclo atual de resposta de solicitação, seu comportamento não pode ser substituído.
+
+As propriedades da categoria 2 podem ser substituídas usando a API de extensões de API Express.
+
+O código a seguir reescreve como o valor de `req.ip` deve ser derivado. Agora, ele simplesmente retorna o valor do cabeçalho de solicitação `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Protótipo
+
+Para fornecer a API Express, os objetos de solicitação/resposta passados para Express (via `app(req, res)`, por exemplo) precisam herdar do mesmo tipo de cadeia. Por padrão, isto é `http.IncomingRequest.prototype` para a solicitação e `http.ServerResponse.prototype` para a resposta.
+
+Se necessário, recomenda-se que isso seja feito apenas a nível da aplicação, e não a nível global. Além disso, tenha cuidado para que o protótipo usado corresponda à funcionalidade o mais próximo possível dos protótipos padrão.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/pt-br/4x/guide/routing.mdx b/src/content/docs/pt-br/4x/guide/routing.mdx
new file mode 100644
index 0000000000..52f12d9985
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Roteamento
+description: Aprenda a definir e usar rotas em aplicações Express.js, incluindo métodos de rota, caminhos de rota, parâmetros e usando o roteador para roteamento modular.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refere-se a como os endpoints de um aplicativo (URIs) respondem às solicitações do cliente.
+Para uma introdução ao roteamento, veja [Roteamento básico](/en/starter/basic-routing).
+
+Você define roteamento usando métodos do objeto Express `app` que correspondem aos métodos HTTP;
+por exemplo, `app. et()` para lidar com solicitações GET e `app.post` para lidar com solicitações POST. Para obter uma lista completa,
+ver [app.METHOD](/en/5x/api#app.METHOD). Você também pode usar o [app.all()](/en/5x/api#app.all) para lidar com todos os métodos HTTP e [app. se()](/en/5x/api#app.use) para
+especifique middleware como função de retorno de chamada (Veja [Usando middleware](/en/guide/using-middleware) para detalhes).
+
+Esses métodos de roteamento especificam uma função de callback (às vezes chamada de "funções de manipulador") chamada quando a aplicação recebe uma solicitação para a rota especificada (endpoint) e método HTTP. Em outras palavras, o aplicativo "listas" para solicitações que correspondem com a(s) rota(s) e método(s) especificado(s), e quando ela detecta uma correspondência, ela chama a função de retorno de chamada especificado.
+
+Na verdade, os métodos de roteamento podem ter mais de uma função de callback como argumentos.
+Com múltiplas funções de callback, é importante fornecer `next` como um argumento para a função de callback e então chamar `next()` dentro do corpo da função para liberar o controle
+para a próxima callback.
+
+O código a seguir é um exemplo de uma rota muito básica.
+
+```js
+const express = require('express');
+const app = express();
+
+// responda com "olá mundo" quando for feita uma solicitação GET para a página inicial
+app.et('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Métodos de rota
+
+Um método de route é derivado de um dos métodos HTTP e é anexado a uma instância da classe 'express'.
+
+O código a seguir é um exemplo de rotas que são definidas para os métodos `GET` e `POST` para a raiz do aplicativo.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Expresso suporta métodos que correspondem a todos os métodos de requisição HTTP: `get`, `post`, e assim por diante.
+Para uma lista completa, consulte [app.METHOD](/en/5x/api#app.METHOD).
+
+Há um método de roteamento especial, `app.all()`, usado para carregar funções de middleware em um caminho para os métodos de requisição HTTP. Por exemplo, o seguinte manipulador é executado para solicitações para a rota `"/secre"` usando `GET`, `POST`, `PUT`, `DELETE`, ou qualquer outro método de solicitação HTTP suportado no [módulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Acessando a seção secreta ...');
+  next(); // passe o controle para o próximo manipulador
+});
+```
+
+## Caminho da rota
+
+Roteamento, em combinação com um método de solicitação, defina os pontos de extremidade em que as solicitações podem ser feitas. Caminhos de rota podem ser frases, padrões de strings ou expressões regulares.
+
+<Alert type="alerta">
+
+Expresso 5, os caracteres `? , `+`, `\*`, `[]`, e `()\` são tratados de forma diferente da versão
+4, por favor, revise o [guia de migração](/en/guide/migrating-5#path-syntax) para mais informações.
+
+</Alert>
+
+<Alert type="alerta">
+
+No modo expresso 4, caracteres de expressão regular como `$` precisam ser escapados com um `\`.
+
+</Alert>
+
+<Alert type="informações">
+
+Expresso usa [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) para corresponder à rota
+caminhos; veja a documentação pay-to-regexp para todas as possibilidades em definir caminhos da rota.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) é uma ferramenta útil para
+testar rotas Express, embora não suporte correspondência de padrões.
+
+</Alert>
+
+<Alert type="warning">strings de consulta não fazem parte do caminho de rota.</Alert>
+
+### Caminhos de rota baseados em strings
+
+Este caminho de rota irá corresponder a solicitações para a rota raiz, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Esse caminho de rota irá corresponder a solicitações para `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Este caminho de rota irá corresponder a solicitações para `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Caminhos de rota baseados em padrões string
+
+<Alert type="alerta">
+
+Os padrões de string no Express 5 não funcionam mais. Por favor, consulte o [guia de migração
+] (/en/guide/migrating-5#path-syntax) para obter mais informações.
+
+</Alert>
+
+Este caminho de rota corresponderá a 'acd' e 'abcd'.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Esse caminho de rota corresponderá a `abcd`, `abbcd`, `abbbcd`, e assim por diante.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Esse caminho de rota irá coincidir com `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, e assim por diante.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Esta rota de rota irá corresponder a `/abe` e `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Caminho baseado em expressões regulares
+
+Este caminho de rota combinará com qualquer coisa com "a" nele.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Esse caminho de rota irá coincidir com `borboleta` e `dragonfly`, mas não com `borboleta`, `dragonflyman`, e assim por diante.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parâmetros de rota
+
+Parâmetros de rota são denominados segmentos de URL que são usados para capturar os valores especificados em sua posição na URL. Os valores capturados são preenchidos no objeto `req.params`, com o nome do parâmetro de rota especificado no caminho como suas respectivas chaves.
+
+```
+Caminho da rota: /users/:userId/books/:bookId
+Solicitação URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Para definir rotas com parâmetros de rota, simplesmente especifique os parâmetros de rota no caminho da rota, conforme mostrado abaixo.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alerta">
+
+O nome dos parâmetros de rota deve ser composto de "palavra caracteres" ([A-Za-z0-9_]).
+
+</Alert>
+
+Como o hífen (`-`) e o ponto (`.`) são interpretados literalmente, eles podem ser usados juntamente com parâmetros de rota para fins úteis.
+
+```
+Caminho da rota: /fvots/:from-:to
+Solicitação URL: http://localhost:3000/fvots/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Caminho da rota: /plantae/:genus.:species
+Solicitação URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "espécies": "persica" }
+```
+
+<Alert type="alerta">
+
+Expresso 5, Regexp caracteres não são suportados nos caminhos de rota, para mais informações por favor
+consulte o [guia de migração](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Para ter mais controle sobre a string exata que pode ser combinada por um parâmetro de rota, você pode acrescentar uma expressão regular entre parênteses (`()`):
+
+```
+Caminho da rota: /user/:userId(\d+)
+Solicitar URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="advertência">
+
+Porque a expressão regular geralmente faz parte de uma cadeia literal, certifique-se de escapar de quaisquer caracteres `\`
+com uma barra invertida adicional, por exemplo `\d+`.
+
+</Alert>
+
+<Alert type="advertência">
+No Expresso 4.x, <a href="https://github.com/expressjs/express/issues/2495">o caractere `*` em expressões regulares não é interpretado da maneira habitual</a>. Como uma alternativa, use `{0,}` em vez de `*`. Isso provavelmente será corrigido no Express 5.
+</Alert>
+
+## Manipuladores de rota
+
+Você pode fornecer várias funções de retorno de chamada que se comportam como [middleware](/en/guide/using-middleware) para lidar com uma solicitação. A única exceção é que esses callbacks podem invocar `next('route')` para ignorar as chamadas restantes da rota. Você pode usar este mecanismo para impor pré-condições em uma rota, então passe controle para rotas subsequentes se não houver motivo para prosseguir com a rota atual.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('rota');
+  }
+  res.end(`Usuário ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('ID especial para o ID de usuário 0');
+});
+```
+
+Neste exemplo:
+
+- `GET /user/5` → tratado pela primeira rota → envia "Usuário 5"
+- `GET /user/0` → primeira rota chama `next('rote')`, pulando para a próxima rota `/user/:id` correspondente
+
+Os manipuladores de rotas podem estar na forma de uma função, um array de funções ou combinações de ambos, como mostrado nos exemplos a seguir.
+
+Uma única função de retorno de chamada pode manipular uma rota. Por exemplo:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Olá de A!');
+});
+```
+
+Mais de uma função de retorno de chamada pode manipular uma rota (certifique-se de especificar o objeto `next`). Por exemplo:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('a resposta será enviada pela próxima função. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Olá de B!');
+  }
+);
+```
+
+Um array de funções de retorno de chamada pode lidar com uma rota. Por exemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Olá de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Uma combinação de funções independentes e matrizes de funções pode lidar com uma rota. Por exemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+aplicativo.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('a resposta será enviada pela próxima função. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Olá de D!');
+  }
+);
+```
+
+## Métodos de resposta
+
+Os métodos no objeto de resposta ('res') na tabela a seguir podem enviar uma resposta para o cliente e encerrar o ciclo de resposta de solicitação. Se nenhum destes métodos for chamado de um manipulador de redes, a solicitação do cliente será deixada em suspenso.
+
+| Método                                        | Descrição:                                                                                          |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Solicite que um arquivo seja baixado.                                                               |
+| [res.end()](/en/5x/api#res.end)               | Encerrar o processo de resposta.                                                                    |
+| [res.json()](/en/5x/api#res.json)             | Enviar uma resposta JSON.                                                                           |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envie uma resposta JSON com suporte a JSONP.                                                        |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirecionar uma requisição.                                                                        |
+| [res.render()](/en/5x/api#res.render)         | Renderizar um modelo de visão.                                                                      |
+| [res.send()](/en/5x/api#res.send)             | Envie uma resposta de vários tipos.                                                                 |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Envia um arquivo como uma transmissão octet.                                                        |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Defina o código de status da resposta e envie sua representação de string como o corpo da resposta. |
+
+## app.route()
+
+Você pode criar manipuladores de rotas em cadeia para um caminho de rota usando `app.route()`.
+Como o caminho é especificado em um único local, é útil criar rotas modulares, assim como reduzir a redundância e os tipos. Para obter mais informações sobre rotas, consulte: [documentação de roteador](/en/5x/api#router).
+
+Aqui está um exemplo de manipuladores de rota encadeados que são definidos usando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Recebe um livro aleatório');
+  })
+  .ost((req, res) => {
+    res.send('Adicionar um livro');
+  })
+  .ut((req, res) => {
+    res.send('Atualizar o livro');
+  });
+```
+
+## expressão.Roteador
+
+Use a classe 'express.Router' para criar módulo, manipuladores de rotas montáveis. Uma instância `Router` é um sistema completo de middleware e roteamento; por este motivo, é muitas vezes referido como um "mini-app".
+
+O exemplo a seguir cria um roteador como um módulo, carrega uma função middleware nele define algumas rotas e monta o módulo do roteador em um caminho no aplicativo principal.
+
+Crie um arquivo de roteador chamado `birds.js` no diretório de aplicativos, com o seguinte conteúdo:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Em seguida, carregue o módulo do roteador no aplicativo:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+O aplicativo agora poderá lidar com pedidos para `/birds` e `/birds/about`, Além de chamar a função middleware `timeLog` que é específica da rota.
+
+Mas se a rota pai `/birds` tiver parâmetros de caminho, ela não será acessível por padrão nas sub-rotas. Para torná-lo acessível, você precisará passar a opção `mergeParams` para o construtor do roteador [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/pt-br/4x/guide/using-middleware.mdx b/src/content/docs/pt-br/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..c71cab0e42
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usando o middleware
+description: Aprenda a usar o middleware em aplicativos do Express.js, incluindo o nível de aplicativos e o middleware, manipulação de erros e integração de intermediários de terceiros.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express é uma web framework de roteamento e middleware que tem a funcionalidade mínima de sua própria funcionalidade: Um aplicativo Express é essencialmente uma série de chamadas de função middleware.
+
+Middleware\_ são funções que têm acesso ao [objeto de requisição](/en/5x/api#req) (`req`), a [objeto de resposta](/en/5x/api#res) (`res`) e a próxima função de middleware no ciclo de resposta de solicitação do aplicativo. A próxima função de middleware é comumente denotada por uma variável chamada `next`.
+
+As funções do Middleware podem executar as seguintes tarefas:
+
+- Execute qualquer código.
+- Fazer alterações na solicitação e nos objetos de resposta.
+- Encerrar o ciclo de solicitação-resposta.
+- Chame a próxima função middleware na pilha.
+
+Se a função middleware atual não encerra o ciclo de resposta de solicitação, ela deve chamar `next()` para passar o controle para a próxima função middleware. Caso contrário, o pedido ficará pendurado.
+
+Um aplicativo Express pode usar os seguintes tipos de middleware:
+
+- [Meio do aplicativo](#middleware.application)
+- [Meio do roteador](#middleware.router)
+- [Middleware com erro](#middleware.error-handling)
+- [middleware](#middleware.built-in)
+- [Middleware de terceiros](#middleware.third-party)
+
+Você pode carregar o nível de aplicação e middleware de nível de roteador com um caminho de montagem opcional.
+Você também pode carregar uma série de funções intermediárias juntas, o que cria uma sub-pilha do sistema intermediário em um ponto de montagem.
+
+## Midddleware no nível de aplicação
+
+Vincular aplicativo de nível middleware a uma instância do [objeto de aplicativo](/en/5x/api#app) usando o `app.use()` e `app. Funções ETHOD()`, onde `METHOD` é o método HTTP da solicitação que a função middleware lida (como GET, PUT, ou POST) em minúsculas.
+
+Este exemplo mostra uma função middleware sem caminho de montagem. A função é executada toda vez que o aplicativo recebe uma solicitação.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Este exemplo mostra uma função middleware montada no caminho `/user/:id`. A função é executada para qualquer tipo de solicitação HTTP
+no caminho `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Tipo de requisição:', req.method);
+  next();
+});
+```
+
+Este exemplo mostra uma rota e sua função de manipulador (sistema de middleware). A função lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Aqui está um exemplo de carregar uma série de funções intermediárias em um ponto de montagem, com um caminho de montagem.
+Isto ilustra um sub-stack de middleware que imprime informação de solicitação para qualquer tipo de solicitação de HTTP no caminho `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Solicitação de URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => console {
+    . og('Tipo de requisição:', req.method);
+    next();
+  }
+
+```
+
+Os gerenciadores de rotas permitem que você defina várias rotas para um caminho. O exemplo abaixo define duas rotas para solicitações GET para o caminho `/user/:id`. A segunda via não causará quaisquer problemas, mas nunca será chamada, porque a primeira via termina o ciclo de resposta aos pedidos.
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res.end('Informações do usuário');
+  }
+);
+
+// manipulador para o caminho /user/:id, que imprime o ID do usuário
+aplicativo.et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Para ignorar o resto das funções de middleware a partir de uma pilha de middleware do roteador, chame `next('route')` para passar o controle para a próxima rota.
+
+<Alert type="informações">
+
+`next('rota')` funcionará apenas em funções de middleware que foram carregadas usando as funções
+`app.METHOD()` ou `router.METHOD()`.
+
+</Alert>
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+O Middleware também pode ser declarado em um array para reutilizabilidade.
+
+Este exemplo mostra um array com um sub-stack de middleware que lida com requisições GET para o caminho `/user/:id`
+
+```js
+function logOriginalUrl(req, res, próximo) {
+  console.log('Solicitação URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, ext) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('Usuário Info');
+});
+```
+
+## Midddleware nível de roteamento
+
+O middleware de roteador funciona da mesma maneira que o middleware no nível de aplicativo, exceto que está vinculado a uma instância de `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Carregue o middleware no nível de roteador usando as funções `router.use()` e `router.METHOD()`.
+
+O código a seguir replica o sistema middleware que é mostrado acima para o middleware no nível de aplicativos, usando o middleware no nível de roteador:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+Para ignorar o resto das funções de middleware do roteador, chame `next('router')`
+para passar o controle de volta para fora da instância do roteador.
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = expressos.
+
+// prefixa o roteador com uma verificação e resgate quando necessário
+roteador. se((req, res, ext) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa o roteador e 401 tudo que cai através do app
+. se('/admin', roteador, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Midddleware com erro manipulado
+
+<Alert type="alerta">
+
+O middleware com erros de manipulação sempre toma _quatro_ argumentos. Você deve fornecer quatro argumentos para
+identificá-lo como uma função de middleware manipulação de erros. Mesmo se você não precisar usar o objeto `next`
+, você deve especificá-lo para manter a assinatura. Caso contrário, o objeto `próximo` será
+interpretado como um middleware regular e irá falhar em lidar com erros.
+
+</Alert>
+
+Definir funções intermediárias de manipulação de erros da mesma forma que outras funções de middleware, exceto quatro argumentos em vez de três, especificamente com a assinatura `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo quebrado!');
+});
+```
+
+Para detalhes sobre o middleware, consulte: [Error handling](/en/guide/error-handling).
+
+## Midddleware integrado
+
+A partir da versão 4.x, o Express não depende mais do [Connect](https://github.com/senchalabs/connect). O middleware
+funções que foram previamente incluídas com Express estão agora em módulos separados; consulte [a lista de funções de middleware](https://github.com/senchalabs/connect#middleware).
+
+O Express tem as seguintes funções de middleware incorporadas:
+
+- [express.static](/en/5x/api#express.static) serve como arquivos estáticos, como arquivos HTML, imagens e assim por diante.
+- [express.json](/en/5x/api#express.json) analisa solicitações recebidas com carga JSON. **NOTA: Disponível com Expresso 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analisa solicitações recebidas com payloads codificados por URL. **NOTA: Disponível com Expresso 4.16.0+**
+
+## Midddleware de terceiros
+
+Usar middleware de terceiros para adicionar funcionalidades a aplicativos Express.
+
+Instale o módulo Node.js para a funcionalidade requerida e, em seguida, carregue-o em seu aplicativo ao nível do aplicativo ou no nível do roteador.
+
+O exemplo a seguir ilustra a instalação e o carregamento da função middleware de análise de cookie-parser\`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// carrega o middleware
+app.use(cookieParser());
+```
+
+Para uma lista parcial de funções intermediárias de terceiros que são comumente usadas com Express, veja: [middleware de terceiros](../resources/middleware).
diff --git a/src/content/docs/pt-br/4x/guide/using-template-engines.mdx b/src/content/docs/pt-br/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..a213cb8b94
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Usando mecanismos de template com o Express
+description: Descubra como integrar e usar mecanismos de modelos como Pug, Handlebars, e EJS com Express.js para renderizar páginas HTML dinâmicas de forma eficiente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um _motor de template_ permite que você use arquivos de template estáticos na sua aplicação. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+Esta abordagem torna mais fácil projetar uma página HTML.
+
+O [gerador de aplicação Expressa](/en/starter/generator) usa [Pug](https://pugjs.org/api/getting-started.html) como seu padrão, mas também apoia [Handlebars](https://www.npmjs.com/package/handlebars), e [EJS](https://www.npmjs.com/package/ejs), entre outros.
+
+Para renderizar arquivos de template, defina as seguintes [propriedades de configuração da aplicação](/en/4x/api#app.set), no `app.js` padrão criado pelo gerador:
+
+- `views`, o diretório onde se localizam os arquivos de template. Ex: `app.set('views', './views')`.
+  Isto é padrão para o diretório `views` no diretório raiz do aplicativo.
+- `ver engenho`, o mecanismo de modelos a ser usado. Por exemplo, para usar o motor de template Pug: `app.set('engenharia de visualização', 'pug')`.
+
+Então instale o correspondente mecanismo de template do npm pacote; por exemplo, para instalar o Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alerta">
+Mecanismos de template compatíveis com o código, como Pug exporta uma função chamada `__express(filePath, opções, callback)`,
+que `res.render()` chama para renderizar o código de template.
+
+Alguns motores de modelos não seguem esta convenção. A biblioteca [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+segue esta convenção mapeando todos os mecanismos de modelo populares de Node.js e, portanto, funciona perfeitamente dentro do Express.
+
+</Alert>
+
+Depois que o motor de visualização estiver definido, você não precisa especificar o motor ou carregar o módulo de mecanismo de modelo no seu aplicativo;
+Expresso carrega o módulo internamente, por exemplo:
+
+```js
+app.set('mecanismo de visão', 'pug');
+```
+
+Em seguida, crie um arquivo de template Pug chamado `index.pug` no diretório `views`, com o seguinte conteúdo:
+
+```pug
+html
+  head
+    title= title
+  corpo
+    h1= mensagem
+```
+
+Crie uma rota para renderizar o arquivo `index.pug`. Se a propriedade `view engine` não estiver definida,
+você deve especificar a extensão do arquivo `view`. Caso contrário, você pode omitir.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Ei', message: 'Olá lá!' });
+});
+```
+
+Quando você faz uma solicitação à página inicial, o arquivo `index.pug` será processado como HTML.
+
+O cache do motor de exibição não armazena o conteúdo da saída do modelo, apenas o modelo subjacente em si. A visualização ainda é renderizada novamente com todas as requisições, mesmo que o cache esteja ativo.
diff --git a/src/content/docs/pt-br/4x/guide/writing-middleware.mdx b/src/content/docs/pt-br/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..6b78dbab89
--- /dev/null
+++ b/src/content/docs/pt-br/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Escrever middleware para uso nos aplicativos Express
+description: Aprenda a escrever funções de middleware personalizadas para aplicativos Express.js, incluindo exemplos e melhores práticas para melhorar a resolução de pedidos e respostas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Middleware\_ são funções que têm acesso ao [objeto de requisição](/en/5x/api#req) (`req`), a [objeto de resposta](/en/5x/api#res) (`res`) e a função `next` no ciclo de resposta de solicitação do aplicativo. A função `próxima` é uma função no roteador Expresso que, quando invocado, executa o intermediário sucedendo ao intermediário atual.
+
+As funções do Middleware podem executar as seguintes tarefas:
+
+- Execute qualquer código.
+- Fazer alterações na solicitação e nos objetos de resposta.
+- Encerrar o ciclo de solicitação-resposta.
+- Chame o próximo middleware na pilha.
+
+Se a função middleware atual não encerra o ciclo de resposta de solicitação, ela deve chamar `next()` para passar o controle para a próxima função middleware. Caso contrário, o pedido ficará pendurado.
+
+A figura a seguir mostra os elementos de uma chamada de função middleware:
+
+<div class="table-scroller">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elementos de uma chamada de função middleware" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">método HTTP para o qual se aplicam as funções middleware.</div>
+
+<div class="callout" id="callout2">
+  Caminho (rota) para o qual a função middleware se aplica.
+</div>
+
+<div class="callout" id="callout3">
+  A função middleware.
+</div>
+
+<div class="callout" id="callout4">
+  Argumento de retorno para a função middleware, chamado "próximo" por convenção.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">resposta</a> argumento para a função middleware, chamada de "res"
+  pela convenção .
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">request</a> argumento para a função middleware, chamado de "req" pela convenção.</div>
+</td>
+</tr>
+</table>
+</div>
+
+Começando com as funções de middleware Express, funções de intermediário que retornam uma Promessa chamarão `próximo(valor)` quando eles rejeitarem ou lançarem um erro. `next` será chamado com o valor rejeitado ou o erro lançado.
+
+## Exemplo
+
+Aqui está um exemplo de uma aplicação simples "Hello World" Express.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Função Middleware myLogger
+
+Aqui está um exemplo simples de uma função de middleware chamada "myLogger". Essa função apenas imprime
+"LOGGGED" quando uma solicitação para o aplicativo passa por ela. A função middleware está atribuída a uma variável
+chamada `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGGED');
+  next();
+};
+```
+
+<Alert type="alerta">
+
+Observe a chamada acima para `next()`. Chamar esta função chama a próxima função de middleware em
+o aplicativo. A função `next()` não é parte do Node. s ou API Expressa, mas é o terceiro argumento
+que é passado para a função middleware. A função `next()` pode ser nomeada qualquer coisa,
+mas por convenção é sempre chamada de "next". Para evitar confusões, utilize sempre esta convenção.
+
+</Alert>
+
+Para carregar a função middleware, chame `app.use()`, especificando a função middleware.
+Por exemplo, o código a seguir carrega a função `myLogger` middleware antes da rota para o caminho raiz (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Toda vez que o aplicativo recebe uma solicitação, ele imprime a mensagem "LOGGED" no terminal.
+
+A ordem do carregamento do middleware é importante: as funções de middleware que são carregadas primeiro também são executadas primeiro.
+
+Se o `myLogger` é carregado após a rota para o caminho raiz, a solicitação nunca chega a ela e o aplicativo não imprime "LOGGED", porque o gerenciador de rotas do caminho raiz termina o ciclo de resposta-requisição.
+
+A função middleware `myLogger` simplesmente imprime uma mensagem, então passa a requisição para a próxima função de middleware na pilha chamando a função `next()`.
+
+### Tempo de solicitação de função Middleware
+
+Em seguida, vamos criar uma função middleware chamada "requestTime" e adicionar uma propriedade chamada `requestTime`
+ao objeto solicitado.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+O aplicativo agora usa a função middleware `requestTime`. Além disso, a função de retorno de chamada da rota raiz usa a propriedade que a função middleware adiciona a `req` (o objeto de solicitação).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+aplicativo.et('/', (req, res) => {
+  let responseText = 'Olá Mundo!<br>';
+  responseText += `<small>Solicitado em: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Quando você faz uma solicitação na raiz do aplicativo, o aplicativo agora mostra a marcação de hora da sua solicitação no navegador.
+
+### Função Middleware validateCookies
+
+Finalmente, vamos criar uma função de middleware que valida os cookies recebidos e envia uma resposta de 400 se cookies forem inválidos.
+
+Aqui está uma função de exemplo que valida cookies com um serviço assíncrono externo.
+
+```js
+função assíncrona cookieValidator(cookies) {
+  tente {
+    aguarde externamenteCookie(cookies.testCookie);
+  } pesque {
+    throw new Error('Cookies inválidos');
+  }
+}
+```
+
+Aqui, usamos o [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware para analisar cookies recebidos do objeto `req` e passá-los para a nossa função `cookieValidator`. O middleware 'validateCookies' retorna a promessa de que, após a rejeição, irá automaticamente acionar o nosso manipulador de erros.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+função async validateCookies(req, res, next) {
+  aguarde cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// manipulador de erro
+. se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alerta">
+
+Observe como `next()` é chamado depois `await cookieValidator(req.cookies)`. Isto garante que se
+`cookieValidator` resolver, o próximo middleware na pilha será chamado. Se você passar qualquer coisa
+para a função `next()` (exceto a string `'route'` ou `'router'`), Expresse que a solicitação
+atual é um erro e pulará quaisquer funções que ainda não sejam de manipulação de erros e de middleware
+.
+
+</Alert>
+
+Como você tem acesso ao objeto de solicitação, o objeto de resposta, a próxima função de middleware na pilha, e todo o nó. s API, as possibilidades com funções de middleware são infinitas.
+
+Para mais informações sobre Express middleware, veja: [Usando Express middleware](/en/guide/using-middleware).
+
+## middleware configurável
+
+Se precisar de seu middleware para ser configurável, exporte uma função que aceite um objeto de opções ou outros parâmetros, que então retorna a implementação intermediária com base nos parâmetros de entrada.
+
+Arquivo: `meu-middleware.js`
+
+```js
+Módulo xports = função (opcions) {
+  return function (req, next) {
+    // Implementa a função middleware baseada no objeto de opções
+    next();
+  };
+};
+```
+
+O middleware agora pode ser usado como mostrado abaixo.
+
+```js
+const mw = require('./meu-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Consulte [cookie-session](https://github.com/expressjs/cookie-session) e [compression](https://github.com/expressjs/compression) para ver exemplos de intermediário configurável.
diff --git a/src/content/docs/pt-br/4x/starter/basic-routing.mdx b/src/content/docs/pt-br/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..6dced5a72b
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Roteamento básico
+description: Aprenda os fundamentos do roteamento em aplicações Express.js, incluindo como definir rotas, lidar com métodos HTTP e criar manipuladores de rotas para seu servidor web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refere-se a determinar como uma aplicação responde a uma solicitação do cliente para um ponto final específico, que é um URI (ou caminho) e um método de requisição HTTP específico (GET, POST, e assim por diante).
+
+Cada rota pode ter uma ou mais funções de manipulador, que são executadas quando a rota é correspondente.
+
+A definição de rota aceita a seguinte estrutura:
+
+```js
+app.METHOD(PATH, MUITO);
+```
+
+Onde:
+
+- `app` é uma instância de `express`.
+- `METHOD` é um [método de solicitação HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), em minúsculas.
+- O `PATH` é um caminho no servidor.
+- `HANDLER` é a função executada quando a rota é correspondente.
+
+<Alert type="alerta">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Se você não estiver familiarizado com a criação de um aplicativo e iniciando-o, consulte Olá mundo
+exemplo.
+
+</Alert>
+
+Os exemplos seguintes ilustram a definição de rotas simples.
+
+Responda com `Olá Mundo!` na página inicial:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Olá Mundo!');
+});
+```
+
+Responder a uma solicitação POST na rota raiz (`/`), a página inicial do aplicativo:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Tem uma solicitação POST');
+});
+```
+
+Responda a uma solicitação PUT para a rota `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Tem uma solicitação de PUT em/user');
+});
+```
+
+Responder a uma solicitação de DELETE para a rota `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Tem uma solicitação de DELETE em/user');
+});
+```
+
+Para mais detalhes sobre roteamento, consulte o [guia de roteamento](/en/guide/routing).
diff --git a/src/content/docs/pt-br/4x/starter/examples.mdx b/src/content/docs/pt-br/4x/starter/examples.mdx
new file mode 100644
index 0000000000..ff0c62c56f
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Exemplos expressos
+description: Explore uma coleção de exemplos de aplicativos do Express.js cobrindo vários casos de uso, integrações e configurações avançadas para ajudá-lo a aprender e construir seus projetos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Autenticação com login e senha
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - negociação de conteúdo HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Trabalhando com sessões baseadas em cookies
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Trabalhando com cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transferindo arquivos para o cliente
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Trabalhando com template JavaScript embutido (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Criando páginas de erro
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Trabalhando com um middleware de erro
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Manipulador de requisições simples
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown como mecanismo de modelo
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Trabalhando com vários roteadores Expressos
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - controladores do estilo MVC
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Rastreando atividade de usuário online com pacotes `online` e `redis`
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Trabalhando com parâmetros de rotas
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Várias operações HTTP no mesmo recurso
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organização de rotas usando um mapa
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Trabalhando com sistema de middleware
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizando rotas por recurso
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Pesquisa API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - Sessões de usuário
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Servendo arquivos estáticos
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Trabalhando com hosts virtuais
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Renderizando visualizações dinamicamente
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Salvando dados no objeto da solicitação entre chamadas de middleware
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Serviço de API simples
+
+## Exemplos adicionais
+
+Estes são alguns exemplos adicionais com integrações mais extensas.
+
+<Alert type="advertência">
+  Esta informação refere-se a sites de terceiros, produtos ou módulos que não são mantidos pela
+  equipe Expressjs. Listar aqui não constitui um endosso ou recomendação da equipe de projeto
+  Expressjs.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Aplicativo Fullstack com Express and Next.js usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - API REST com Express in TypeScript usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
diff --git a/src/content/docs/pt-br/4x/starter/faq.md b/src/content/docs/pt-br/4x/starter/faq.md
new file mode 100644
index 0000000000..8af6c95239
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: Perguntas Frequentes
+description: Encontre respostas para perguntas frequentes sobre Express.js, incluindo tópicos sobre a estrutura do aplicativo, modelos, autenticação, mecanismos de modelo, tratamento de erros e muito mais.
+---
+
+## Como eu devo estruturar meu aplicativo?
+
+Não há uma resposta definitiva a esta questão. A resposta depende
+da escala do seu aplicativo e da equipe que está envolvida. Para ser o mais flexível possível,
+flexível, Express não faz suposições em termos de estrutura.
+
+Rotas e outras lógicas específicas do aplicativo podem viver em quantos arquivos
+você quiser, em qualquer estrutura de diretório que preferir. View the following
+examples for inspiration:
+
+- [Lista de rotas](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mapa de rotas](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Além disso, existem extensões para o Express, que simplificam alguns desses padrões:
+
+- [Roteamento de recursos](https://github.com/expressjs/express-resource)
+
+## Como faço para definir modelos?
+
+Expresso não tem noção de um banco de dados. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+Veja [LoopBack](http://loopback.io) para um framework baseado em Express que é centralizado em torno de modelos.
+
+## Como posso autenticar os usuários?
+
+Authentication is another opinionated area that Express does not
+venture into. Você pode usar qualquer esquema de autenticação desejado.
+Para um esquema simples de nome de usuário/senha, consulte [este exemplo](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quais mecanismos de template suporta o Expresso?
+
+Expresso suporta qualquer mecanismo de modelos que esteja em conformidade com a assinatura `(caminho, moradores, callback)`.
+Para normalizar interfaces do motor de modelos e cache de cache, veja o projeto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+para suporte. Motores de modelos não listados ainda podem suportar a assinatura Express.
+
+Para obter mais informações, consulte [Usando mecanismos de modelo com Express](/en/guide/using-template-engines).
+
+## Como lidamos com 404 respostas?
+
+Em Express, respostas 404 não são resultado de um erro, então
+o middleware de erro não as capturará. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Adicione rotas dinamicamente em tempo de execução em uma instância de `express.Router()`
+para que as rotas não sejam substituídas por uma função middleware.
+
+## Como faço para configurar um manipulador de erro?
+
+Você define o middleware com erros de manipulação da mesma forma que outros middleware,
+exceto com quatro argumentos em vez de três; especificamente com a assinatura `(err, req, res, próxima)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para obter mais informações, consulte [Manipulação de erro](/en/guide/error-handling).
+
+## Como faço para tornar HTML simples?
+
+Você não! Não há necessidade de "render" HTML com a função `res.render()`.
+Se você tiver um arquivo específico, use a função `res.sendFile()`.
+Se você estiver servindo muitos assets de um diretório, use a função `express.static()`
+middleware.
+
+## Qual versão do Node.js requer o Expresso?
+
+- [Expresso 4.x](/en/4x/api) requer Node.js 0.10 ou superior.
+- [Express 5.x](/en/5x/api) requer Node.js 18 ou superior.
diff --git a/src/content/docs/pt-br/4x/starter/generator.mdx b/src/content/docs/pt-br/4x/starter/generator.mdx
new file mode 100644
index 0000000000..44d8308549
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/generator.mdx
@@ -0,0 +1,127 @@
+---
+title: Gerador de aplicação expressa
+description: Aprenda a usar a ferramenta gerador de aplicativo Express para criar rapidamente um esqueleto para seus aplicativos Express.js, otimização de configuração e configuração.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use a ferramenta de gerador de aplicação, `express-generator`, para criar rapidamente um esqueleto de aplicação.
+
+Você pode executar o gerador de aplicação com o comando `npx` (disponível em Node.js 8.2.0).
+
+```bash
+$ gerador de expressão npx
+```
+
+Para versões anteriores do Nó, instale o gerador de aplicativo como um pacote npm global e, em seguida, inicie-o:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Exibe as opções de comando com a opção '-h':
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opções:
+
+    -h, --help mostra informação de uso
+        --version mostra o número da versão
+    -e, --ejs add ejs engine suporte
+        --hbs add handlebars engine support
+        --pug add pug engine support
+    -H, --hogan adiciona hogan. s mecanismo suporta
+        --no-view gera sem o mecanismo de exibição
+    -v, --view <engine> add view <engine> support (ejs├hbs─jsėjade├jade├pug├twig├vash) (o padrão é jade)
+    -c, --css <engine>  add stylesheet <engine> (menos:stylus➲ bússola) (o padrão é sem css)
+        --git add . itignore
+    -f, --force força em diretório não-vazio
+```
+
+Por exemplo, o seguinte cria um aplicativo Expresso chamado _myapp_. O aplicativo será criado em uma pasta chamada _myapp_ no diretório de trabalho atual e o mecanismo de visualização será definido para <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug meuapp
+
+   create : meuapp
+   create : myapp/package.json
+   create : myapp/app. s
+   criam : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   criar: meuapp/rotas/usuários. s
+   cria : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   cria : myapp/views
+   criar : myapp/views/index. ug
+   criar : myapp/views/layout.pug
+   criar : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Em seguida, instale dependências:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+No MacOS ou Linux, execute o aplicativo com este comando:
+
+```bash
+$ DEBUG=meuapp:* npm start
+```
+
+No prompt de comando Windows, use este comando:
+
+```bash
+> definir DEBUG=myapp:* & npm start
+```
+
+No Windows PowerShell, use este comando:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Em seguida, carregue `http://localhost:3000/` no seu navegador para acessar o aplicativo.
+
+O aplicativo gerado possui a seguinte estrutura de diretórios:
+
+```bash
+.
+── app.js
+─── bin
+├── www
+package. son
+── public
+── imagens
+├── javascripts
+├── stylesheets
+── style styesheets
+ ─ style. ss
+── rotas
+├── index.js
+─── usuarios
+. s
+── visões
+    erros de ── . ug
+    ── index.pug
+    ── layout.pug
+
+diretórios e 9 arquivos
+```
+
+<Alert type="informações">
+
+A estrutura do aplicativo criada pelo gerador é apenas uma das muitas maneiras de estruturar aplicativos Express.
+Sinta-se livre para usar esta estrutura ou modificá-la para atender às suas necessidades.
+
+</Alert>
diff --git a/src/content/docs/pt-br/4x/starter/hello-world.mdx b/src/content/docs/pt-br/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..3410dc5564
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Olá, exemplo do mundo
+description: Comece com o Express.js construindo uma simples aplicação 'Hello World'', demonstrando a configuração básica e a criação de servidor para iniciantes.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="informações">
+
+Embutido abaixo é essencialmente o aplicativo Expresso mais simples que você pode criar. É um único aplicativo de arquivo
+&mdash; _não_ o que você obteria se usar o [Express generator](/en/starter/generator), que
+cria o andaime para um aplicativo completo com vários arquivos JavaScript, modelos Jade e subdiretórios
+para vários fins.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Olá Mundo!');
+});
+
+app.listen(port, () => {
+  console.log(`Exemplo app escutando na porta ${port}`);
+});
+```
+
+Este aplicativo inicia um servidor e escuta na porta 3000 para conexões. O aplicativo responde com "Olá Mundo!" para solicitações
+para a URL raiz (`/`) ou _route_. Para todos os outros caminhos, responderá com um **404 Não Encontrado**.
+
+## Executando localmente
+
+Primeiro, crie um diretório chamado `myapp`, mude para ele e execute `npm init`. Em seguida, instale `express` como uma dependência, conforme o [guia de instalação](/en/starter/installing).
+
+No diretório `myapp`, crie um arquivo chamado `app.js` e copie o código do exemplo acima.
+
+<Alert type="alerta">
+
+O `req` (requisição) e `res` (resposta) são exatamente os mesmos objetos que o Node fornece, para que você possa
+invocar `req. ipe()`, `req.on('data', callback)`, e qualquer outra coisa que você faria sem o Express
+envolvido.
+
+</Alert>
+
+Execute o aplicativo com o seguinte comando:
+
+```bash
+$ node app.js
+```
+
+Em seguida, carregue `http://localhost:3000/` em um navegador para ver a saída.
diff --git a/src/content/docs/pt-br/4x/starter/installing.mdx b/src/content/docs/pt-br/4x/starter/installing.mdx
new file mode 100644
index 0000000000..3f45b5d840
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/installing.mdx
@@ -0,0 +1,49 @@
+---
+title: Instalando
+description: Aprenda a instalar o Express.js no seu ambiente Node.js, incluindo a configuração do diretório do seu projeto e o gerenciamento de dependências com npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Antes de começar, certifique-se de ter [Node.js](https://nodejs.org/) 0.10 ou superior instalado. Em seguida, crie um diretório para a sua aplicação e navegue até ele.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use o comando `npm init` para criar um arquivo `package.json` para sua aplicação.
+Para obter mais informações sobre como funciona o arquivo `package.json`, veja [Especificações da manipulação do package.json do npm](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Este comando avisa você para várias coisas, como o nome e a versão de seu aplicativo.
+Por enquanto, você simplesmente pode clicar em RETURN para aceitar os padrões para a maioria deles, com a seguinte exceção:
+
+```
+ponto de entrada: (index.js)
+```
+
+Digite `app.js`, ou o que quiser que o nome do arquivo principal seja. Se você quer que seja `index.js`, pressione RETURN para aceitar o nome de arquivo padrão sugerido.
+
+Agora, instale o Express no diretório `myapp` e salve-o na lista de dependências. Por exemplo:
+
+```bash
+Instalação npm expressiva
+```
+
+Para instalar o Express temporariamente e não adicioná-lo à lista de dependências:
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="informações">
+
+Por padrão com a versão npm 5.0+, `npm install` adiciona o módulo à lista de `dependências` no pacote
+. arquivo son`; com versões anteriores do npm, você deve especificar a opção `--save`explicitamente. Então, depois, executar`npm install\` no diretório de aplicativos irá automaticamente
+instalar módulos na lista de dependências.
+
+</Alert>
diff --git a/src/content/docs/pt-br/4x/starter/static-files.mdx b/src/content/docs/pt-br/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..dcd21f0ab2
--- /dev/null
+++ b/src/content/docs/pt-br/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servindo arquivos estáticos no Express
+description: Entenda como servir arquivos estáticos como imagens, CSS e JavaScript em aplicativos Express.js usando o middleware "static".
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para servir arquivos estáticos como imagens, arquivos CSS e arquivos JavaScript, use a função `express.static` middleware embutida no Express.
+
+A assinatura da função é:
+
+```js
+express.static(root, [options]);
+```
+
+O argumento `root` especifica o diretório raiz do qual se destinam os assets estáticos.
+Para obter mais informações sobre o argumento `options`, consulte [express.static](/en/5x/api#express.static).
+
+Por exemplo, use o seguinte código para servir imagens, arquivos CSS e arquivos JavaScript em um diretório chamado `public`:
+
+```js
+app.use(express.static('público'));
+```
+
+Agora, você pode carregar os arquivos que estão no diretório `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="informações">
+
+Expresso procura os arquivos relativos ao diretório estático, então o nome do diretório estático
+não faz parte do URL.
+
+</Alert>
+
+Para usar vários diretórios de ativos estáticos, chame a função `express.static` middleware várias vezes:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Expresso olha os arquivos na ordem em que você definiu os diretórios estáticos com a função de middleware `express.static`.
+
+<Alert type="informações">
+
+Para melhores resultados, use um proxy
+reverso cache para melhorar o desempenho do
+servindo ativos estáticos.
+
+</Alert>
+
+Para criar um prefixo de caminho virtual (onde o caminho não existe realmente no sistema de arquivos) para arquivos que são servidos pelo `express. função tática`, [especifique um caminho de montagem](/en/5x/api#app.use) para o diretório estático, conforme mostrado abaixo:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Agora, você pode carregar os arquivos que estão no diretório `public` a partir do prefixo de caminho `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+No entanto, o caminho que você fornece para a função `express.static` é relativo ao diretório de onde você inicia seu processo `node`. Se você executar o aplicativo expresso a partir de outro diretório, é mais seguro usar o caminho absoluto do diretório que você deseja servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Para mais detalhes sobre a função `serve-static` e suas opções, consulte [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/pt-br/5x/advanced/developing-template-engines.md b/src/content/docs/pt-br/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..8b379a6f50
--- /dev/null
+++ b/src/content/docs/pt-br/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Desenvolvendo modelos de motores para Express
+description: Aprenda a desenvolver motores de modelos personalizados para Express.js usando app.engine(), com exemplos sobre como criar e integrar sua própria lógica de renderização de templates.
+---
+
+Use o método `app.engine(ext, callback)` para criar o seu próprio motor de templates. `ext` refere-se à extensão de arquivo, e `callback` é a função template engine que aceita os seguintes itens como parâmetros: a localização do arquivo, o objeto de opções e a função de retorno de chamada.
+
+O código a seguir é um exemplo de implementação de um mecanismo muito simples de template para renderizar arquivos `.ntl`.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Seu aplicativo poderá renderizar arquivos `.ntl`. Crie um arquivo chamado `index.ntl` no diretório `views` com o seguinte conteúdo.
+
+```pug
+#title#
+#message#
+```
+
+Em seguida, crie a seguinte rota no seu app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+Quando você fizer uma solicitação à página inicial, `index.ntl` será processado como HTML.
diff --git a/src/content/docs/pt-br/5x/guide/behind-proxies.mdx b/src/content/docs/pt-br/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..e6a72e5cad
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/behind-proxies.mdx
@@ -0,0 +1,103 @@
+---
+title: Expresso atrás dos proxies
+description: Aprenda a configurar os aplicativos Express.js para funcionar corretamente atrás de proxies reversas, incluindo o uso do proxy confiável para manipular endereços IP do cliente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Ao executar um app Expresso atrás de um proxy reverso, alguns das APIs Express podem retornar valores diferentes do esperado. A fim de se ajustar para isto, a configuração do aplicativo `trust proxy` pode ser usada para expor informações fornecidas pelo proxy reverso na API Express. O problema mais comum é expressar APIs que expõem o endereço IP do cliente pode mostrar um endereço IP interno do proxy inverso.
+
+<Alert type="informações">
+
+Ao configurar a configuração `proxy confiável`, é importante entender a configuração exata do proxy reverso
+. Como esta configuração confiará nos valores fornecidos na solicitação, é importante que
+a combinação da configuração no Express corresponda a como o proxy reverso funciona.
+
+</Alert>
+
+A configuração do aplicativo 'proxy confiável' pode ser definida para um dos valores listados na tabela a seguir.
+
+<table class="Docável" border="1" markdown="1">
+  <thead><tr><th>Digite</th><th>Valor</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+Se `true`, o endereço IP do cliente é entendido como a entrada mais à esquerda no cabeçalho `X-Forwarded-For`.
+
+Se `false`, o aplicativo é entendido como diretamente virado para o cliente e o endereço IP do cliente é derivado de `req.socket.remoteAddress`. Esta é a configuração padrão.
+
+<Alert type="advertência">
+Ao definir como `true`, é importante garantir que o último proxy reverso confiável esteja removendo/substituindo todos os seguintes cabeçalhos HTTP: `X-Forwarded-for`, `X-Forwarded-Host` e `X-Forwarded-Proto`, caso contrário, pode ser possível que o cliente forneça qualquer valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>endereços IP</td>
+<td markdown="1">
+Um endereço IP, subnet ou uma matriz de endereços IP e subnets para confiar como sendo um proxy reverso. A seguinte lista mostra os nomes das sub-redes pré-configuradas:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+Você pode definir endereços IP das seguintes maneiras:
+
+```js
+app.set('trust proxy', 'loopback'); // especifica um subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // especifica um subnet e um aplicativo de endereço
+. et('proxy de confiança', 'loopback, linklocal, uniquelocal'); // especificar múltiplas subnets como CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // especificar várias subnets como um array
+```
+
+Quando especificado, os endereços IP ou as subredes são excluídos do processo de determinação de endereço, e o endereço IP não confiável mais próximo do servidor de aplicativos é definido como o endereço IP do cliente. Isto funciona verificando se 'req.socket.remoteAddress' é confiável. Em caso afirmativo, então cada endereço em `X-Forwarded-For` é verificado da direita para a esquerda até o primeiro endereço não confiável.
+
+</td>
+    </tr>
+    <tr>
+      <td>Número</td>
+<td markdown="1">
+Use o endereço que, no máximo, está fora do número de hops do aplicativo Express. `req.socket.remoteAddress` é o primeiro hop, e o resto é procurado no cabeçalho `X-Forwarded-for` da direita para a esquerda. Um valor de `0` significa que o primeiro endereço não confiável seria `req.socket.remoteAddress`, ou seja, não há um proxy reverso.
+
+<Alert type="advertência">
+Ao usar esta configuração, é importante garantir que não haja vários, caminhos de comprimento diferente para o aplicativo Express, para que o cliente possa ser menor que o número configurado de saltos de distância, caso contrário, poderá ser possível que o cliente forneça qualquer valor.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Função</td>
+<td markdown="1">
+Execução de confiança personalizada.
+
+```js
+app.set('proxy de confiança', (ip) => {
+  if (ip === '127.0.0.1' ├ip === '123.123.123. 23')
+    return true; // IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Habilitar `trust proxy` terá o seguinte impacto:
+
+<ul>
+  <li markdown="1">
+    O valor de [req.hostname](/en/api#req.hostname) é derivado do valor definido no cabeçalho
+    `X-Forwarded-Host`, que pode ser configurado pelo cliente ou pelo proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` pode ser configurado pelo proxy reverso para dizer ao aplicativo se ele é
+    `https` ou `http` ou até mesmo um nome inválido. Este valor é refletido por
+    [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    Os valores [req.ip](/en/api#req.ip) e [req.ips](/en/api#req.ips) são preenchidos com base no
+    cabeçalho do socket e `X-Forwarded-For`, iniciando no primeiro endereço não confiável.
+  </li>
+</ul>
+
+A configuração `trust proxy` é implementada usando o pacote [proxy-addr](https://www.npmjs.com/package/proxy-addr). Para obter mais informações, consulte a documentação.
diff --git a/src/content/docs/pt-br/5x/guide/debugging.mdx b/src/content/docs/pt-br/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..66690a4946
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Expresso de depuração
+description: Aprenda a habilitar e usar logs de depuração nos aplicativos Express.js definindo a variável de ambiente DEBUG para melhorar a solução de problemas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para ver todos os logs internos usados no Express, defina a variável de ambiente `DEBUG` para
+`express:*` ao iniciar seu aplicativo.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+No Windows, use o comando correspondente.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Executar este comando no aplicativo padrão gerado pelo [gerador expresso](/en/starter/generator) imprime a seguinte saída:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+Quando um pedido for feito ao aplicativo, você verá os logs especificados no código Expresso:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+Para ver os logs apenas da implementação do roteador, defina o valor de `DEBUG` para `express:router`. Da mesma forma, para ver apenas os logs da implementação do aplicativo, defina o valor de `DEBUG` para `express:application`, e assim por diante.
+
+## Aplicações geradas por `express`
+
+Uma aplicação gerada pelo comando `express` usa o módulo `debug` e seu namespace de depuração é escopo para o nome da aplicação.
+
+Por exemplo, se você gerou o app com `$ express sample-app`, você pode ativar as instruções de depuração com o seguinte comando:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+Você pode especificar mais de um namespace de depuração atribuindo uma lista de nomes separada por vírgulas:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Opções avançadas
+
+Ao executar através do Node.js, você pode definir algumas variáveis de ambiente que irão mudar o comportamento do log de depuração:
+
+| Nome:               | Objetivo                                                 |
+| ------------------- | -------------------------------------------------------- |
+| `DEBUG`             | Habilita/desabilita namespace específicos de depuração.  |
+| `DEBUG_COLORS`      | Usar ou não cores na saída de depuração.                 |
+| DEBUG_DEPTH\`       | Profundidade da inspeção de objeto.                      |
+| `DEBUG_FD`          | Descritor de arquivo para escrever a saída de depuração. |
+| `DEBUG_SHOW_HIDDEN` | Mostra propriedades ocultas em objetos inspecionados.    |
+
+<Alert type="informações">
+
+As variáveis de ambiente começando com `DEBUG_` acabam sendo convertidas em um objeto de Opções
+que é usado com formatos `%o`/`%O`. Veja a documentação do Node.js sobre
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) para a lista
+completa.
+
+</Alert>
diff --git a/src/content/docs/pt-br/5x/guide/error-handling.mdx b/src/content/docs/pt-br/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..0cd431d89c
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Tratamento de erros
+description: Entenda como o Express.js lida com erros em código síncrono e assíncrono e aprenda a implementar erro personalizado de manipulação de intermediários para seus aplicativos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Tratamento de erros_ refere-se a como as capturas Expressas e processa erros que
+ocorrem de forma sincronizada e assíncrona. Expresso vem com um erro padrão
+manipulador para que você não precise escrever seu próprio para começar.
+
+## Capturando Erros
+
+É importante garantir que Expresso pegue todos os erros que ocorrem enquanto
+rodando manipuladores de rotas e intermediários.
+
+Erros que ocorrem no código síncrono dentro dos manipuladores de rota e middleware
+não exigem trabalho extra. If synchronous code throws an error, then Express will
+catch and process it. Por exemplo:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Expresso irá pegar isso sozinho.
+});
+```
+
+Para erros retornados de funções assíncronas, invocados pelos manipuladores de rota
+e intermediário, você deve passá-los para a função `next()`, onde o Express irá capturá-los a
+e processá-los. Por exemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.eadFile('/file-does-not-existente', (err, data) => {
+    if (err) {
+      next(err); // Passa os erros para o Express.
+    } else {
+      res.end(data);
+    }
+  });
+});
+```
+
+Começando pelo Express 5, roteadores e intermediários que retornam um Promise
+chamarão `next(value)` automaticamente quando eles rejeitarem ou lançarem um erro.
+Por exemplo:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+Se `getUserById` lança um erro ou rejeita, `next` será chamado com
+o erro lançado ou o valor rejeitado. Se nenhum valor rejeitado for fornecido, `next`
+será chamado com um objeto de erro padrão fornecido pelo roteador Express.
+
+Se você passar qualquer coisa para a função `next()` (exceto a string `'route'`),
+Expressa que a requisição atual é um erro e irá pular quaisquer funções
+restantes que não sejam de manipulação de erros e middleware.
+
+Se o callback em uma sequência não fornecer dados, somente erros, você pode simplificar
+este código da seguinte forma:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+No exemplo acima, `next` é fornecido como o callback para `fs.writeFile`,
+que é chamado com ou sem erros. Se não houver erro, o segundo receptor
+é executado, caso contrário as pegadas do Express e processa o erro.
+
+Você deve capturar os erros que ocorrem em código assíncrono invocado pelos manipuladores da rota ou
+middleware e passá-los para o Expresso para processamento. Por exemplo:
+
+```js
+app.get('/', (q, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      ext(err);
+    }
+  }, 100);
+});
+```
+
+O exemplo acima usa um bloco `tentar... catch` para capturar erros no código assíncrono
+e passá-los para o Express. Se o bloco `tentar...catch`
+fosse omitido, Express não pegaria o erro, uma vez que ele não faz parte do código de manipulador
+síncrono.
+
+Use promessas para evitar a sobrecarga do bloco `tentar... capturar` ou ao usar funções
+que retornam promessas. Por exemplo:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    . hen(() => {
+      joga novo Error('BROKEN');
+    })
+    . atch(next); // Erros serão passados para o Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+Você também pode usar uma cadeia de manipuladores para confiar em erro síncrono
+de recuperação, reduzindo o código assíncrono a algo trivial. Por exemplo:
+
+```js
+app.get('/', [
+  função (req, res, ext) {
+    fs. eadFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals. ata = data;
+      ext(err);
+    });
+  },
+  função (req, res) {
+    res. ocals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+O exemplo acima tem algumas declarações triviais da chamada `readFile`
+. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Então, o exemplo acima tenta processar os dados. Se isso falhar, o manipulador de erro
+síncrono irá pegá-lo. Se você tivesse feito este processamento dentro do
+o callback `readFile`, então o aplicativo poderia sair e o erro Express
+manipuladores não executariam.
+
+Seja qual for o método que você usar, se você quer que os manipuladores de erro Expressos sejam chamados para dentro e o aplicativo
+para sobreviver, você deve garantir que o Expresso receba o erro.
+
+## O manipulador de erro padrão
+
+Expresso vem com um manipulador de erro embutido que cuida de quaisquer erros que possam ser encontrados no aplicativo. Esta função de middleware com erros padrão é adicionada no final da função middleware stack.
+
+Se você passar um erro para `next()` e não lidar com ele em um erro personalizado
+handler, será tratado pelo manipulador de erro embutido; o erro será
+escrito no cliente com o rastreamento de pilha. O rastreamento da pilha não está incluído
+no ambiente de produção.
+
+<Alert type="informações">
+
+Defina a variável de ambiente `NODE_ENV` como `production`, para executar o aplicativo em modo de produção.
+
+</Alert>
+
+Quando um erro é escrito, a seguinte informação é adicionada a
+resposta:
+
+- O `res.statusCode` é definido em `err.status` (ou `err.statusCode`). Se
+  este valor estiver fora do intervalo de 4xx ou 5xx, ele será definido como 500.
+- A mensagem 'res.statusMessage' é definida de acordo com o código de status.
+- O corpo será o HTML da mensagem do código de status quando em produção
+  ambiente, caso contrário será `err.stack`.
+- Qualquer cabeçalho especificado em um objeto `err.headers`.
+
+Se você chamar `next()` com um erro depois que você começou a escrever a
+resposta (por exemplo, se você encontrar um erro ao transmitir a resposta
+ao cliente), o Express default error handler fecha a conexão
+e falha na solicitação.
+
+Então, quando você adicionar um manipulador de erro personalizado, você deve delegar para
+o manipulador de erro padrão Express, quando os cabeçalhos
+já foram enviados para o cliente:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Observe que o manipulador de erro padrão pode ser acionado se você chamar `next()` com um erro
+no seu código mais de uma vez. Mesmo que um erro personalizado de manipulação de middleware esteja no lugar.
+
+Outro erro de manipulação de middleware pode ser encontrado em [Express middleware](/en/resources/middleware).
+
+## Escrevendo manipuladores de erros
+
+Definir funções intermediárias de manipulação de erros da mesma forma que outras funções de middleware,
+exceto funções de manipulação de erro possuem quatro argumentos ao invés de três:
+`(err, req, res, next)`. Por exemplo:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo quebrado!');
+});
+```
+
+Você define o middleware de erro duramente, depois de outro `app.use()` e roteia chamadas; por exemplo:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.rlencoded({
+    extendido: true,
+  })
+);
+app.use(bodyParser.json());
+app.se(methodOverride());
+app.use((err, req, res, next) => {
+  // lógica
+});
+```
+
+As respostas de dentro de uma função middleware podem estar em qualquer formato, como uma página de erro HTML, uma mensagem simples ou uma string JSON.
+
+Para fins de estrutura organizacional (e de nível superior), você pode definir
+várias funções de middleware com manipulação de erros, tanto quanto você poderia com funções de intermediário
+regulares. Por exemplo, para definir um manipulador de erro
+para solicitações feitas usando `XHR` e aqueles sem:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.se(
+  bodyParser.urlencoded({
+    extendido: true,
+  })
+);
+app.se(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, ext) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Também neste exemplo, `clientErrorHandler` é definido como segue; neste caso, o erro é explicitamente passado para o próximo.
+
+Observe que quando _não_ estiver chamando "próximo" em uma função de manipulação de erros, você é responsável por escrever (e terminar) a resposta. Caso contrário, esses pedidos ficarão "pendentes" e não serão elegíveis para a recolha de lixo.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).end({ error: 'Algo falhou!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implementar a função "catch-all" `errorHandler` da seguinte forma (por exemplo):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Se você tiver um gerenciador de rotas com múltiplas funções de retorno de chamada, você pode usar o parâmetro `rota` para pular para o próximo manipulador de rota. Por exemplo:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user. asPaid) {
+      // continue lidando com esta requisição
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent. ind((err, doc) => {
+      se (err) retornar next(err);
+      res. son(doc);
+    });
+  }
+);
+```
+
+Neste exemplo, o manipulador `getPaidContent` será ignorado, mas quaisquer manipuladores restantes em `app` para `/a_route_behind_paywall` continuariam sendo executados.
+
+<Alert type="informações">
+
+Chama para `next()` e `next(err)` indicam que o manipulador atual está completo e em que estado.
+`next(err)` pulará todos os manipuladores restantes na cadeia, exceto aqueles que estão configurados para
+lidar com erros conforme descrito acima.
+
+</Alert>
diff --git a/src/content/docs/pt-br/5x/guide/overriding-express-api.md b/src/content/docs/pt-br/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..d5ceef01af
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Sobrescrevendo a API Expresso
+description: Descubra como personalizar e estender a API do Express.js substituindo métodos e propriedades nos objetos de solicitação e resposta usando protótipos.
+---
+
+A API do Expresso consiste de vários métodos e propriedades nos objetos de solicitação e resposta. Estas são herdadas pelo protótipo. Há dois pontos de extensão para a API Express:
+
+1. Os protótipos globais em `express.request` e `express.response`.
+2. Protótipos específicos de aplicativo em `app.request` e `app.response`.
+
+Alterar os protótipos globais afetará todos os aplicativos do Express carregados no mesmo processo. Se desejar, alterações podem ser feitas especificamente no aplicativo, alterando apenas os protótipos específicos do aplicativo após criar um novo aplicativo.
+
+## Métodos
+
+Você pode substituir a assinatura e o comportamento dos métodos existentes com o seu próprio, atribuindo uma função personalizada.
+
+A seguir é um exemplo de substituição do comportamento de [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+A implementação acima altera completamente a assinatura original de `res.sendStatus`. Agora aceita um código de estado, um tipo de codificação e a mensagem a ser enviada ao cliente.
+
+O método sobrescrito agora pode ser usado dessa maneira:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## propriedades
+
+As propriedades da API Expresso também são:
+
+1. Propriedades atribuídas (ex: `req.baseUrl`, `req.originalUrl`)
+2. Definido como getters (ex: `req.secure`, `req.ip`)
+
+Uma vez que as propriedades da categoria 1 são dinamicamente atribuídas aos objetos `request` e `response` no contexto do ciclo atual de resposta de solicitação, seu comportamento não pode ser substituído.
+
+As propriedades da categoria 2 podem ser substituídas usando a API de extensões de API Express.
+
+O código a seguir reescreve como o valor de `req.ip` deve ser derivado. Agora, ele simplesmente retorna o valor do cabeçalho de solicitação `Client-IP`.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Protótipo
+
+Para fornecer a API Express, os objetos de solicitação/resposta passados para Express (via `app(req, res)`, por exemplo) precisam herdar do mesmo tipo de cadeia. Por padrão, isto é `http.IncomingRequest.prototype` para a solicitação e `http.ServerResponse.prototype` para a resposta.
+
+Se necessário, recomenda-se que isso seja feito apenas a nível da aplicação, e não a nível global. Além disso, tenha cuidado para que o protótipo usado corresponda à funcionalidade o mais próximo possível dos protótipos padrão.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/pt-br/5x/guide/routing.mdx b/src/content/docs/pt-br/5x/guide/routing.mdx
new file mode 100644
index 0000000000..52f12d9985
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Roteamento
+description: Aprenda a definir e usar rotas em aplicações Express.js, incluindo métodos de rota, caminhos de rota, parâmetros e usando o roteador para roteamento modular.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refere-se a como os endpoints de um aplicativo (URIs) respondem às solicitações do cliente.
+Para uma introdução ao roteamento, veja [Roteamento básico](/en/starter/basic-routing).
+
+Você define roteamento usando métodos do objeto Express `app` que correspondem aos métodos HTTP;
+por exemplo, `app. et()` para lidar com solicitações GET e `app.post` para lidar com solicitações POST. Para obter uma lista completa,
+ver [app.METHOD](/en/5x/api#app.METHOD). Você também pode usar o [app.all()](/en/5x/api#app.all) para lidar com todos os métodos HTTP e [app. se()](/en/5x/api#app.use) para
+especifique middleware como função de retorno de chamada (Veja [Usando middleware](/en/guide/using-middleware) para detalhes).
+
+Esses métodos de roteamento especificam uma função de callback (às vezes chamada de "funções de manipulador") chamada quando a aplicação recebe uma solicitação para a rota especificada (endpoint) e método HTTP. Em outras palavras, o aplicativo "listas" para solicitações que correspondem com a(s) rota(s) e método(s) especificado(s), e quando ela detecta uma correspondência, ela chama a função de retorno de chamada especificado.
+
+Na verdade, os métodos de roteamento podem ter mais de uma função de callback como argumentos.
+Com múltiplas funções de callback, é importante fornecer `next` como um argumento para a função de callback e então chamar `next()` dentro do corpo da função para liberar o controle
+para a próxima callback.
+
+O código a seguir é um exemplo de uma rota muito básica.
+
+```js
+const express = require('express');
+const app = express();
+
+// responda com "olá mundo" quando for feita uma solicitação GET para a página inicial
+app.et('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Métodos de rota
+
+Um método de route é derivado de um dos métodos HTTP e é anexado a uma instância da classe 'express'.
+
+O código a seguir é um exemplo de rotas que são definidas para os métodos `GET` e `POST` para a raiz do aplicativo.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Expresso suporta métodos que correspondem a todos os métodos de requisição HTTP: `get`, `post`, e assim por diante.
+Para uma lista completa, consulte [app.METHOD](/en/5x/api#app.METHOD).
+
+Há um método de roteamento especial, `app.all()`, usado para carregar funções de middleware em um caminho para os métodos de requisição HTTP. Por exemplo, o seguinte manipulador é executado para solicitações para a rota `"/secre"` usando `GET`, `POST`, `PUT`, `DELETE`, ou qualquer outro método de solicitação HTTP suportado no [módulo http](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Acessando a seção secreta ...');
+  next(); // passe o controle para o próximo manipulador
+});
+```
+
+## Caminho da rota
+
+Roteamento, em combinação com um método de solicitação, defina os pontos de extremidade em que as solicitações podem ser feitas. Caminhos de rota podem ser frases, padrões de strings ou expressões regulares.
+
+<Alert type="alerta">
+
+Expresso 5, os caracteres `? , `+`, `\*`, `[]`, e `()\` são tratados de forma diferente da versão
+4, por favor, revise o [guia de migração](/en/guide/migrating-5#path-syntax) para mais informações.
+
+</Alert>
+
+<Alert type="alerta">
+
+No modo expresso 4, caracteres de expressão regular como `$` precisam ser escapados com um `\`.
+
+</Alert>
+
+<Alert type="informações">
+
+Expresso usa [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) para corresponder à rota
+caminhos; veja a documentação pay-to-regexp para todas as possibilidades em definir caminhos da rota.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) é uma ferramenta útil para
+testar rotas Express, embora não suporte correspondência de padrões.
+
+</Alert>
+
+<Alert type="warning">strings de consulta não fazem parte do caminho de rota.</Alert>
+
+### Caminhos de rota baseados em strings
+
+Este caminho de rota irá corresponder a solicitações para a rota raiz, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+Esse caminho de rota irá corresponder a solicitações para `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+Este caminho de rota irá corresponder a solicitações para `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Caminhos de rota baseados em padrões string
+
+<Alert type="alerta">
+
+Os padrões de string no Express 5 não funcionam mais. Por favor, consulte o [guia de migração
+] (/en/guide/migrating-5#path-syntax) para obter mais informações.
+
+</Alert>
+
+Este caminho de rota corresponderá a 'acd' e 'abcd'.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+Esse caminho de rota corresponderá a `abcd`, `abbcd`, `abbbcd`, e assim por diante.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+Esse caminho de rota irá coincidir com `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, e assim por diante.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+Esta rota de rota irá corresponder a `/abe` e `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Caminho baseado em expressões regulares
+
+Este caminho de rota combinará com qualquer coisa com "a" nele.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+Esse caminho de rota irá coincidir com `borboleta` e `dragonfly`, mas não com `borboleta`, `dragonflyman`, e assim por diante.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Parâmetros de rota
+
+Parâmetros de rota são denominados segmentos de URL que são usados para capturar os valores especificados em sua posição na URL. Os valores capturados são preenchidos no objeto `req.params`, com o nome do parâmetro de rota especificado no caminho como suas respectivas chaves.
+
+```
+Caminho da rota: /users/:userId/books/:bookId
+Solicitação URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+Para definir rotas com parâmetros de rota, simplesmente especifique os parâmetros de rota no caminho da rota, conforme mostrado abaixo.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alerta">
+
+O nome dos parâmetros de rota deve ser composto de "palavra caracteres" ([A-Za-z0-9_]).
+
+</Alert>
+
+Como o hífen (`-`) e o ponto (`.`) são interpretados literalmente, eles podem ser usados juntamente com parâmetros de rota para fins úteis.
+
+```
+Caminho da rota: /fvots/:from-:to
+Solicitação URL: http://localhost:3000/fvots/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Caminho da rota: /plantae/:genus.:species
+Solicitação URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "espécies": "persica" }
+```
+
+<Alert type="alerta">
+
+Expresso 5, Regexp caracteres não são suportados nos caminhos de rota, para mais informações por favor
+consulte o [guia de migração](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+Para ter mais controle sobre a string exata que pode ser combinada por um parâmetro de rota, você pode acrescentar uma expressão regular entre parênteses (`()`):
+
+```
+Caminho da rota: /user/:userId(\d+)
+Solicitar URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="advertência">
+
+Porque a expressão regular geralmente faz parte de uma cadeia literal, certifique-se de escapar de quaisquer caracteres `\`
+com uma barra invertida adicional, por exemplo `\d+`.
+
+</Alert>
+
+<Alert type="advertência">
+No Expresso 4.x, <a href="https://github.com/expressjs/express/issues/2495">o caractere `*` em expressões regulares não é interpretado da maneira habitual</a>. Como uma alternativa, use `{0,}` em vez de `*`. Isso provavelmente será corrigido no Express 5.
+</Alert>
+
+## Manipuladores de rota
+
+Você pode fornecer várias funções de retorno de chamada que se comportam como [middleware](/en/guide/using-middleware) para lidar com uma solicitação. A única exceção é que esses callbacks podem invocar `next('route')` para ignorar as chamadas restantes da rota. Você pode usar este mecanismo para impor pré-condições em uma rota, então passe controle para rotas subsequentes se não houver motivo para prosseguir com a rota atual.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.d === '0') {
+    return next('rota');
+  }
+  res.end(`Usuário ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('ID especial para o ID de usuário 0');
+});
+```
+
+Neste exemplo:
+
+- `GET /user/5` → tratado pela primeira rota → envia "Usuário 5"
+- `GET /user/0` → primeira rota chama `next('rote')`, pulando para a próxima rota `/user/:id` correspondente
+
+Os manipuladores de rotas podem estar na forma de uma função, um array de funções ou combinações de ambos, como mostrado nos exemplos a seguir.
+
+Uma única função de retorno de chamada pode manipular uma rota. Por exemplo:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Olá de A!');
+});
+```
+
+Mais de uma função de retorno de chamada pode manipular uma rota (certifique-se de especificar o objeto `next`). Por exemplo:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.og('a resposta será enviada pela próxima função. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Olá de B!');
+  }
+);
+```
+
+Um array de funções de retorno de chamada pode lidar com uma rota. Por exemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.end('Olá de C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+Uma combinação de funções independentes e matrizes de funções pode lidar com uma rota. Por exemplo:
+
+```js
+const cb0 = function (req, res, next) {
+  console.og('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.og('CB1');
+  next();
+};
+
+aplicativo.et(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.og('a resposta será enviada pela próxima função. .');
+    next();
+  },
+  (req, res) => {
+    res.end('Olá de D!');
+  }
+);
+```
+
+## Métodos de resposta
+
+Os métodos no objeto de resposta ('res') na tabela a seguir podem enviar uma resposta para o cliente e encerrar o ciclo de resposta de solicitação. Se nenhum destes métodos for chamado de um manipulador de redes, a solicitação do cliente será deixada em suspenso.
+
+| Método                                        | Descrição:                                                                                          |
+| --------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Solicite que um arquivo seja baixado.                                                               |
+| [res.end()](/en/5x/api#res.end)               | Encerrar o processo de resposta.                                                                    |
+| [res.json()](/en/5x/api#res.json)             | Enviar uma resposta JSON.                                                                           |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Envie uma resposta JSON com suporte a JSONP.                                                        |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirecionar uma requisição.                                                                        |
+| [res.render()](/en/5x/api#res.render)         | Renderizar um modelo de visão.                                                                      |
+| [res.send()](/en/5x/api#res.send)             | Envie uma resposta de vários tipos.                                                                 |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Envia um arquivo como uma transmissão octet.                                                        |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Defina o código de status da resposta e envie sua representação de string como o corpo da resposta. |
+
+## app.route()
+
+Você pode criar manipuladores de rotas em cadeia para um caminho de rota usando `app.route()`.
+Como o caminho é especificado em um único local, é útil criar rotas modulares, assim como reduzir a redundância e os tipos. Para obter mais informações sobre rotas, consulte: [documentação de roteador](/en/5x/api#router).
+
+Aqui está um exemplo de manipuladores de rota encadeados que são definidos usando `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Recebe um livro aleatório');
+  })
+  .ost((req, res) => {
+    res.send('Adicionar um livro');
+  })
+  .ut((req, res) => {
+    res.send('Atualizar o livro');
+  });
+```
+
+## expressão.Roteador
+
+Use a classe 'express.Router' para criar módulo, manipuladores de rotas montáveis. Uma instância `Router` é um sistema completo de middleware e roteamento; por este motivo, é muitas vezes referido como um "mini-app".
+
+O exemplo a seguir cria um roteador como um módulo, carrega uma função middleware nele define algumas rotas e monta o módulo do roteador em um caminho no aplicativo principal.
+
+Crie um arquivo de roteador chamado `birds.js` no diretório de aplicativos, com o seguinte conteúdo:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Em seguida, carregue o módulo do roteador no aplicativo:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+O aplicativo agora poderá lidar com pedidos para `/birds` e `/birds/about`, Além de chamar a função middleware `timeLog` que é específica da rota.
+
+Mas se a rota pai `/birds` tiver parâmetros de caminho, ela não será acessível por padrão nas sub-rotas. Para torná-lo acessível, você precisará passar a opção `mergeParams` para o construtor do roteador [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/pt-br/5x/guide/using-middleware.mdx b/src/content/docs/pt-br/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..c71cab0e42
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Usando o middleware
+description: Aprenda a usar o middleware em aplicativos do Express.js, incluindo o nível de aplicativos e o middleware, manipulação de erros e integração de intermediários de terceiros.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express é uma web framework de roteamento e middleware que tem a funcionalidade mínima de sua própria funcionalidade: Um aplicativo Express é essencialmente uma série de chamadas de função middleware.
+
+Middleware\_ são funções que têm acesso ao [objeto de requisição](/en/5x/api#req) (`req`), a [objeto de resposta](/en/5x/api#res) (`res`) e a próxima função de middleware no ciclo de resposta de solicitação do aplicativo. A próxima função de middleware é comumente denotada por uma variável chamada `next`.
+
+As funções do Middleware podem executar as seguintes tarefas:
+
+- Execute qualquer código.
+- Fazer alterações na solicitação e nos objetos de resposta.
+- Encerrar o ciclo de solicitação-resposta.
+- Chame a próxima função middleware na pilha.
+
+Se a função middleware atual não encerra o ciclo de resposta de solicitação, ela deve chamar `next()` para passar o controle para a próxima função middleware. Caso contrário, o pedido ficará pendurado.
+
+Um aplicativo Express pode usar os seguintes tipos de middleware:
+
+- [Meio do aplicativo](#middleware.application)
+- [Meio do roteador](#middleware.router)
+- [Middleware com erro](#middleware.error-handling)
+- [middleware](#middleware.built-in)
+- [Middleware de terceiros](#middleware.third-party)
+
+Você pode carregar o nível de aplicação e middleware de nível de roteador com um caminho de montagem opcional.
+Você também pode carregar uma série de funções intermediárias juntas, o que cria uma sub-pilha do sistema intermediário em um ponto de montagem.
+
+## Midddleware no nível de aplicação
+
+Vincular aplicativo de nível middleware a uma instância do [objeto de aplicativo](/en/5x/api#app) usando o `app.use()` e `app. Funções ETHOD()`, onde `METHOD` é o método HTTP da solicitação que a função middleware lida (como GET, PUT, ou POST) em minúsculas.
+
+Este exemplo mostra uma função middleware sem caminho de montagem. A função é executada toda vez que o aplicativo recebe uma solicitação.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+Este exemplo mostra uma função middleware montada no caminho `/user/:id`. A função é executada para qualquer tipo de solicitação HTTP
+no caminho `/user/:id`.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Tipo de requisição:', req.method);
+  next();
+});
+```
+
+Este exemplo mostra uma rota e sua função de manipulador (sistema de middleware). A função lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Aqui está um exemplo de carregar uma série de funções intermediárias em um ponto de montagem, com um caminho de montagem.
+Isto ilustra um sub-stack de middleware que imprime informação de solicitação para qualquer tipo de solicitação de HTTP no caminho `/user/:id`.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Solicitação de URL:', req. riginalUrl);
+    next();
+  },
+  (req, res, next) => console {
+    . og('Tipo de requisição:', req.method);
+    next();
+  }
+
+```
+
+Os gerenciadores de rotas permitem que você defina várias rotas para um caminho. O exemplo abaixo define duas rotas para solicitações GET para o caminho `/user/:id`. A segunda via não causará quaisquer problemas, mas nunca será chamada, porque a primeira via termina o ciclo de resposta aos pedidos.
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.arams.id);
+    next();
+  },
+  (req, res, next) => {
+    res.end('Informações do usuário');
+  }
+);
+
+// manipulador para o caminho /user/:id, que imprime o ID do usuário
+aplicativo.et('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+Para ignorar o resto das funções de middleware a partir de uma pilha de middleware do roteador, chame `next('route')` para passar o controle para a próxima rota.
+
+<Alert type="informações">
+
+`next('rota')` funcionará apenas em funções de middleware que foram carregadas usando as funções
+`app.METHOD()` ou `router.METHOD()`.
+
+</Alert>
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+O Middleware também pode ser declarado em um array para reutilizabilidade.
+
+Este exemplo mostra um array com um sub-stack de middleware que lida com requisições GET para o caminho `/user/:id`
+
+```js
+function logOriginalUrl(req, res, próximo) {
+  console.log('Solicitação URL:', req.riginalUrl);
+  next();
+}
+
+function logMethod(req, res, ext) {
+  console.log('Request Type:', req.ethod);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.et('/user/:id', logStuff, (req, res, next) => {
+  res.send('Usuário Info');
+});
+```
+
+## Midddleware nível de roteamento
+
+O middleware de roteador funciona da mesma maneira que o middleware no nível de aplicativo, exceto que está vinculado a uma instância de `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Carregue o middleware no nível de roteador usando as funções `router.use()` e `router.METHOD()`.
+
+O código a seguir replica o sistema middleware que é mostrado acima para o middleware no nível de aplicativos, usando o middleware no nível de roteador:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+Para ignorar o resto das funções de middleware do roteador, chame `next('router')`
+para passar o controle de volta para fora da instância do roteador.
+
+Este exemplo mostra uma sub-pilha de middleware que lida com requisições GET para o caminho `/user/:id`.
+
+```js
+const express = require('express');
+const app = express();
+const router = expressos.
+
+// prefixa o roteador com uma verificação e resgate quando necessário
+roteador. se((req, res, ext) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router. et('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// usa o roteador e 401 tudo que cai através do app
+. se('/admin', roteador, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Midddleware com erro manipulado
+
+<Alert type="alerta">
+
+O middleware com erros de manipulação sempre toma _quatro_ argumentos. Você deve fornecer quatro argumentos para
+identificá-lo como uma função de middleware manipulação de erros. Mesmo se você não precisar usar o objeto `next`
+, você deve especificá-lo para manter a assinatura. Caso contrário, o objeto `próximo` será
+interpretado como um middleware regular e irá falhar em lidar com erros.
+
+</Alert>
+
+Definir funções intermediárias de manipulação de erros da mesma forma que outras funções de middleware, exceto quatro argumentos em vez de três, especificamente com a assinatura `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo quebrado!');
+});
+```
+
+Para detalhes sobre o middleware, consulte: [Error handling](/en/guide/error-handling).
+
+## Midddleware integrado
+
+A partir da versão 4.x, o Express não depende mais do [Connect](https://github.com/senchalabs/connect). O middleware
+funções que foram previamente incluídas com Express estão agora em módulos separados; consulte [a lista de funções de middleware](https://github.com/senchalabs/connect#middleware).
+
+O Express tem as seguintes funções de middleware incorporadas:
+
+- [express.static](/en/5x/api#express.static) serve como arquivos estáticos, como arquivos HTML, imagens e assim por diante.
+- [express.json](/en/5x/api#express.json) analisa solicitações recebidas com carga JSON. **NOTA: Disponível com Expresso 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) analisa solicitações recebidas com payloads codificados por URL. **NOTA: Disponível com Expresso 4.16.0+**
+
+## Midddleware de terceiros
+
+Usar middleware de terceiros para adicionar funcionalidades a aplicativos Express.
+
+Instale o módulo Node.js para a funcionalidade requerida e, em seguida, carregue-o em seu aplicativo ao nível do aplicativo ou no nível do roteador.
+
+O exemplo a seguir ilustra a instalação e o carregamento da função middleware de análise de cookie-parser\`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// carrega o middleware
+app.use(cookieParser());
+```
+
+Para uma lista parcial de funções intermediárias de terceiros que são comumente usadas com Express, veja: [middleware de terceiros](../resources/middleware).
diff --git a/src/content/docs/pt-br/5x/guide/using-template-engines.mdx b/src/content/docs/pt-br/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..a213cb8b94
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Usando mecanismos de template com o Express
+description: Descubra como integrar e usar mecanismos de modelos como Pug, Handlebars, e EJS com Express.js para renderizar páginas HTML dinâmicas de forma eficiente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Um _motor de template_ permite que você use arquivos de template estáticos na sua aplicação. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+Esta abordagem torna mais fácil projetar uma página HTML.
+
+O [gerador de aplicação Expressa](/en/starter/generator) usa [Pug](https://pugjs.org/api/getting-started.html) como seu padrão, mas também apoia [Handlebars](https://www.npmjs.com/package/handlebars), e [EJS](https://www.npmjs.com/package/ejs), entre outros.
+
+Para renderizar arquivos de template, defina as seguintes [propriedades de configuração da aplicação](/en/4x/api#app.set), no `app.js` padrão criado pelo gerador:
+
+- `views`, o diretório onde se localizam os arquivos de template. Ex: `app.set('views', './views')`.
+  Isto é padrão para o diretório `views` no diretório raiz do aplicativo.
+- `ver engenho`, o mecanismo de modelos a ser usado. Por exemplo, para usar o motor de template Pug: `app.set('engenharia de visualização', 'pug')`.
+
+Então instale o correspondente mecanismo de template do npm pacote; por exemplo, para instalar o Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alerta">
+Mecanismos de template compatíveis com o código, como Pug exporta uma função chamada `__express(filePath, opções, callback)`,
+que `res.render()` chama para renderizar o código de template.
+
+Alguns motores de modelos não seguem esta convenção. A biblioteca [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+segue esta convenção mapeando todos os mecanismos de modelo populares de Node.js e, portanto, funciona perfeitamente dentro do Express.
+
+</Alert>
+
+Depois que o motor de visualização estiver definido, você não precisa especificar o motor ou carregar o módulo de mecanismo de modelo no seu aplicativo;
+Expresso carrega o módulo internamente, por exemplo:
+
+```js
+app.set('mecanismo de visão', 'pug');
+```
+
+Em seguida, crie um arquivo de template Pug chamado `index.pug` no diretório `views`, com o seguinte conteúdo:
+
+```pug
+html
+  head
+    title= title
+  corpo
+    h1= mensagem
+```
+
+Crie uma rota para renderizar o arquivo `index.pug`. Se a propriedade `view engine` não estiver definida,
+você deve especificar a extensão do arquivo `view`. Caso contrário, você pode omitir.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Ei', message: 'Olá lá!' });
+});
+```
+
+Quando você faz uma solicitação à página inicial, o arquivo `index.pug` será processado como HTML.
+
+O cache do motor de exibição não armazena o conteúdo da saída do modelo, apenas o modelo subjacente em si. A visualização ainda é renderizada novamente com todas as requisições, mesmo que o cache esteja ativo.
diff --git a/src/content/docs/pt-br/5x/guide/writing-middleware.mdx b/src/content/docs/pt-br/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..52afbbf6ba
--- /dev/null
+++ b/src/content/docs/pt-br/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Escrever middleware para uso nos aplicativos Express
+description: Aprenda a escrever funções de middleware personalizadas para aplicativos Express.js, incluindo exemplos e melhores práticas para melhorar a resolução de pedidos e respostas.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Middleware\_ são funções que têm acesso ao [objeto de requisição](/en/5x/api#req) (`req`), a [objeto de resposta](/en/5x/api#res) (`res`) e a função `next` no ciclo de resposta de solicitação do aplicativo. A função `próxima` é uma função no roteador Expresso que, quando invocado, executa o intermediário sucedendo ao intermediário atual.
+
+As funções do Middleware podem executar as seguintes tarefas:
+
+- Execute qualquer código.
+- Fazer alterações na solicitação e nos objetos de resposta.
+- Encerrar o ciclo de solicitação-resposta.
+- Chame o próximo middleware na pilha.
+
+Se a função middleware atual não encerra o ciclo de resposta de solicitação, ela deve chamar `next()` para passar o controle para a próxima função middleware. Caso contrário, o pedido ficará pendurado.
+
+A figura a seguir mostra os elementos de uma chamada de função middleware:
+
+![Elementos de uma chamada de função middleware](/images/express-mw.png)
+
+Começando com as funções de middleware Express, funções de intermediário que retornam uma Promessa chamarão `próximo(valor)` quando eles rejeitarem ou lançarem um erro. `next` será chamado com o valor rejeitado ou o erro lançado.
+
+## Exemplo
+
+Aqui está um exemplo de uma aplicação simples "Hello World" Express.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Função Middleware myLogger
+
+Aqui está um exemplo simples de uma função de middleware chamada "myLogger". Essa função apenas imprime
+"LOGGGED" quando uma solicitação para o aplicativo passa por ela. A função middleware está atribuída a uma variável
+chamada `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGGED');
+  next();
+};
+```
+
+<Alert type="alerta">
+
+Observe a chamada acima para `next()`. Chamar esta função chama a próxima função de middleware em
+o aplicativo. A função `next()` não é parte do Node. s ou API Expressa, mas é o terceiro argumento
+que é passado para a função middleware. A função `next()` pode ser nomeada qualquer coisa,
+mas por convenção é sempre chamada de "next". Para evitar confusões, utilize sempre esta convenção.
+
+</Alert>
+
+Para carregar a função middleware, chame `app.use()`, especificando a função middleware.
+Por exemplo, o código a seguir carrega a função `myLogger` middleware antes da rota para o caminho raiz (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.og('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Toda vez que o aplicativo recebe uma solicitação, ele imprime a mensagem "LOGGED" no terminal.
+
+A ordem do carregamento do middleware é importante: as funções de middleware que são carregadas primeiro também são executadas primeiro.
+
+Se o `myLogger` é carregado após a rota para o caminho raiz, a solicitação nunca chega a ela e o aplicativo não imprime "LOGGED", porque o gerenciador de rotas do caminho raiz termina o ciclo de resposta-requisição.
+
+A função middleware `myLogger` simplesmente imprime uma mensagem, então passa a requisição para a próxima função de middleware na pilha chamando a função `next()`.
+
+### Tempo de solicitação de função Middleware
+
+Em seguida, vamos criar uma função middleware chamada "requestTime" e adicionar uma propriedade chamada `requestTime`
+ao objeto solicitado.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+O aplicativo agora usa a função middleware `requestTime`. Além disso, a função de retorno de chamada da rota raiz usa a propriedade que a função middleware adiciona a `req` (o objeto de solicitação).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.equestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+aplicativo.et('/', (req, res) => {
+  let responseText = 'Olá Mundo!<br>';
+  responseText += `<small>Solicitado em: ${req.requestTime}</small>`;
+  res.end(responseText);
+});
+
+app.listen(3000);
+```
+
+Quando você faz uma solicitação na raiz do aplicativo, o aplicativo agora mostra a marcação de hora da sua solicitação no navegador.
+
+### Função Middleware validateCookies
+
+Finalmente, vamos criar uma função de middleware que valida os cookies recebidos e envia uma resposta de 400 se cookies forem inválidos.
+
+Aqui está uma função de exemplo que valida cookies com um serviço assíncrono externo.
+
+```js
+função assíncrona cookieValidator(cookies) {
+  tente {
+    aguarde externamenteCookie(cookies.testCookie);
+  } pesque {
+    throw new Error('Cookies inválidos');
+  }
+}
+```
+
+Aqui, usamos o [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware para analisar cookies recebidos do objeto `req` e passá-los para a nossa função `cookieValidator`. O middleware 'validateCookies' retorna a promessa de que, após a rejeição, irá automaticamente acionar o nosso manipulador de erros.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('. cookieValidator');
+
+const app = express();
+
+função async validateCookies(req, res, next) {
+  aguarde cookieValidator(req. ookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// manipulador de erro
+. se((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alerta">
+
+Observe como `next()` é chamado depois `await cookieValidator(req.cookies)`. Isto garante que se
+`cookieValidator` resolver, o próximo middleware na pilha será chamado. Se você passar qualquer coisa
+para a função `next()` (exceto a string `'route'` ou `'router'`), Expresse que a solicitação
+atual é um erro e pulará quaisquer funções que ainda não sejam de manipulação de erros e de middleware
+.
+
+</Alert>
+
+Como você tem acesso ao objeto de solicitação, o objeto de resposta, a próxima função de middleware na pilha, e todo o nó. s API, as possibilidades com funções de middleware são infinitas.
+
+Para mais informações sobre Express middleware, veja: [Usando Express middleware](/en/guide/using-middleware).
+
+## middleware configurável
+
+Se precisar de seu middleware para ser configurável, exporte uma função que aceite um objeto de opções ou outros parâmetros, que então retorna a implementação intermediária com base nos parâmetros de entrada.
+
+Arquivo: `meu-middleware.js`
+
+```js
+Módulo xports = função (opcions) {
+  return function (req, next) {
+    // Implementa a função middleware baseada no objeto de opções
+    next();
+  };
+};
+```
+
+O middleware agora pode ser usado como mostrado abaixo.
+
+```js
+const mw = require('./meu-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Consulte [cookie-session](https://github.com/expressjs/cookie-session) e [compression](https://github.com/expressjs/compression) para ver exemplos de intermediário configurável.
diff --git a/src/content/docs/pt-br/5x/starter/basic-routing.mdx b/src/content/docs/pt-br/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..6dced5a72b
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Roteamento básico
+description: Aprenda os fundamentos do roteamento em aplicações Express.js, incluindo como definir rotas, lidar com métodos HTTP e criar manipuladores de rotas para seu servidor web.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refere-se a determinar como uma aplicação responde a uma solicitação do cliente para um ponto final específico, que é um URI (ou caminho) e um método de requisição HTTP específico (GET, POST, e assim por diante).
+
+Cada rota pode ter uma ou mais funções de manipulador, que são executadas quando a rota é correspondente.
+
+A definição de rota aceita a seguinte estrutura:
+
+```js
+app.METHOD(PATH, MUITO);
+```
+
+Onde:
+
+- `app` é uma instância de `express`.
+- `METHOD` é um [método de solicitação HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), em minúsculas.
+- O `PATH` é um caminho no servidor.
+- `HANDLER` é a função executada quando a rota é correspondente.
+
+<Alert type="alerta">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. Se você não estiver familiarizado com a criação de um aplicativo e iniciando-o, consulte Olá mundo
+exemplo.
+
+</Alert>
+
+Os exemplos seguintes ilustram a definição de rotas simples.
+
+Responda com `Olá Mundo!` na página inicial:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Olá Mundo!');
+});
+```
+
+Responder a uma solicitação POST na rota raiz (`/`), a página inicial do aplicativo:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Tem uma solicitação POST');
+});
+```
+
+Responda a uma solicitação PUT para a rota `/user`:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Tem uma solicitação de PUT em/user');
+});
+```
+
+Responder a uma solicitação de DELETE para a rota `/user`:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Tem uma solicitação de DELETE em/user');
+});
+```
+
+Para mais detalhes sobre roteamento, consulte o [guia de roteamento](/en/guide/routing).
diff --git a/src/content/docs/pt-br/5x/starter/examples.mdx b/src/content/docs/pt-br/5x/starter/examples.mdx
new file mode 100644
index 0000000000..d7c62b03ab
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Exemplos expressos
+description: Explore uma coleção de exemplos de aplicativos do Express.js cobrindo vários casos de uso, integrações e configurações avançadas para ajudá-lo a aprender e construir seus projetos.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Esta página contém a lista de exemplos usando o Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Autenticação com login e senha
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - negociação de conteúdo HTTP
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Trabalhando com sessões baseadas em cookies
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Trabalhando com cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transferindo arquivos para o cliente
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Trabalhando com template JavaScript embutido (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Criando páginas de erro
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Trabalhando com um middleware de erro
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Manipulador de requisições simples
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown como mecanismo de modelo
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Trabalhando com vários roteadores Expressos
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - controladores do estilo MVC
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Rastreando atividade de usuário online com pacotes `online` e `redis`
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Trabalhando com parâmetros de rotas
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Várias operações HTTP no mesmo recurso
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organização de rotas usando um mapa
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Trabalhando com sistema de middleware
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizando rotas por recurso
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Pesquisa API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - Sessões de usuário
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Servendo arquivos estáticos
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Trabalhando com hosts virtuais
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Renderizando visualizações dinamicamente
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Salvando dados no objeto da solicitação entre chamadas de middleware
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Serviço de API simples
+
+## Exemplos adicionais
+
+Estes são alguns exemplos adicionais com integrações mais extensas.
+
+<Alert type="advertência">
+
+Esta informação refere-se a sites de terceiros, produtos ou módulos que não são mantidos pela equipe
+Expressjs. Listar aqui não constitui um endosso ou recomendação da equipe de projeto
+Expressjs.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Aplicativo Fullstack com Express and Next.js usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - API REST com Express in TypeScript usando [Prisma](https://www.npmjs.com/package/prisma) como ORM
diff --git a/src/content/docs/pt-br/5x/starter/faq.md b/src/content/docs/pt-br/5x/starter/faq.md
new file mode 100644
index 0000000000..8af6c95239
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: Perguntas Frequentes
+description: Encontre respostas para perguntas frequentes sobre Express.js, incluindo tópicos sobre a estrutura do aplicativo, modelos, autenticação, mecanismos de modelo, tratamento de erros e muito mais.
+---
+
+## Como eu devo estruturar meu aplicativo?
+
+Não há uma resposta definitiva a esta questão. A resposta depende
+da escala do seu aplicativo e da equipe que está envolvida. Para ser o mais flexível possível,
+flexível, Express não faz suposições em termos de estrutura.
+
+Rotas e outras lógicas específicas do aplicativo podem viver em quantos arquivos
+você quiser, em qualquer estrutura de diretório que preferir. View the following
+examples for inspiration:
+
+- [Lista de rotas](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Mapa de rotas](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Além disso, existem extensões para o Express, que simplificam alguns desses padrões:
+
+- [Roteamento de recursos](https://github.com/expressjs/express-resource)
+
+## Como faço para definir modelos?
+
+Expresso não tem noção de um banco de dados. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+Veja [LoopBack](http://loopback.io) para um framework baseado em Express que é centralizado em torno de modelos.
+
+## Como posso autenticar os usuários?
+
+Authentication is another opinionated area that Express does not
+venture into. Você pode usar qualquer esquema de autenticação desejado.
+Para um esquema simples de nome de usuário/senha, consulte [este exemplo](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Quais mecanismos de template suporta o Expresso?
+
+Expresso suporta qualquer mecanismo de modelos que esteja em conformidade com a assinatura `(caminho, moradores, callback)`.
+Para normalizar interfaces do motor de modelos e cache de cache, veja o projeto
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+para suporte. Motores de modelos não listados ainda podem suportar a assinatura Express.
+
+Para obter mais informações, consulte [Usando mecanismos de modelo com Express](/en/guide/using-template-engines).
+
+## Como lidamos com 404 respostas?
+
+Em Express, respostas 404 não são resultado de um erro, então
+o middleware de erro não as capturará. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Adicione rotas dinamicamente em tempo de execução em uma instância de `express.Router()`
+para que as rotas não sejam substituídas por uma função middleware.
+
+## Como faço para configurar um manipulador de erro?
+
+Você define o middleware com erros de manipulação da mesma forma que outros middleware,
+exceto com quatro argumentos em vez de três; especificamente com a assinatura `(err, req, res, próxima)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+Para obter mais informações, consulte [Manipulação de erro](/en/guide/error-handling).
+
+## Como faço para tornar HTML simples?
+
+Você não! Não há necessidade de "render" HTML com a função `res.render()`.
+Se você tiver um arquivo específico, use a função `res.sendFile()`.
+Se você estiver servindo muitos assets de um diretório, use a função `express.static()`
+middleware.
+
+## Qual versão do Node.js requer o Expresso?
+
+- [Expresso 4.x](/en/4x/api) requer Node.js 0.10 ou superior.
+- [Express 5.x](/en/5x/api) requer Node.js 18 ou superior.
diff --git a/src/content/docs/pt-br/5x/starter/generator.mdx b/src/content/docs/pt-br/5x/starter/generator.mdx
new file mode 100644
index 0000000000..44d8308549
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/generator.mdx
@@ -0,0 +1,127 @@
+---
+title: Gerador de aplicação expressa
+description: Aprenda a usar a ferramenta gerador de aplicativo Express para criar rapidamente um esqueleto para seus aplicativos Express.js, otimização de configuração e configuração.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use a ferramenta de gerador de aplicação, `express-generator`, para criar rapidamente um esqueleto de aplicação.
+
+Você pode executar o gerador de aplicação com o comando `npx` (disponível em Node.js 8.2.0).
+
+```bash
+$ gerador de expressão npx
+```
+
+Para versões anteriores do Nó, instale o gerador de aplicativo como um pacote npm global e, em seguida, inicie-o:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Exibe as opções de comando com a opção '-h':
+
+```bash
+$ express -h
+
+  Uso: express [options] [dir]
+
+  Opções:
+
+    -h, --help mostra informação de uso
+        --version mostra o número da versão
+    -e, --ejs add ejs engine suporte
+        --hbs add handlebars engine support
+        --pug add pug engine support
+    -H, --hogan adiciona hogan. s mecanismo suporta
+        --no-view gera sem o mecanismo de exibição
+    -v, --view <engine> add view <engine> support (ejs├hbs─jsėjade├jade├pug├twig├vash) (o padrão é jade)
+    -c, --css <engine>  add stylesheet <engine> (menos:stylus➲ bússola) (o padrão é sem css)
+        --git add . itignore
+    -f, --force força em diretório não-vazio
+```
+
+Por exemplo, o seguinte cria um aplicativo Expresso chamado _myapp_. O aplicativo será criado em uma pasta chamada _myapp_ no diretório de trabalho atual e o mecanismo de visualização será definido para <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug meuapp
+
+   create : meuapp
+   create : myapp/package.json
+   create : myapp/app. s
+   criam : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index. s
+   criar: meuapp/rotas/usuários. s
+   cria : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style. ss
+   cria : myapp/views
+   criar : myapp/views/index. ug
+   criar : myapp/views/layout.pug
+   criar : myapp/views/error. ug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Em seguida, instale dependências:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+No MacOS ou Linux, execute o aplicativo com este comando:
+
+```bash
+$ DEBUG=meuapp:* npm start
+```
+
+No prompt de comando Windows, use este comando:
+
+```bash
+> definir DEBUG=myapp:* & npm start
+```
+
+No Windows PowerShell, use este comando:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Em seguida, carregue `http://localhost:3000/` no seu navegador para acessar o aplicativo.
+
+O aplicativo gerado possui a seguinte estrutura de diretórios:
+
+```bash
+.
+── app.js
+─── bin
+├── www
+package. son
+── public
+── imagens
+├── javascripts
+├── stylesheets
+── style styesheets
+ ─ style. ss
+── rotas
+├── index.js
+─── usuarios
+. s
+── visões
+    erros de ── . ug
+    ── index.pug
+    ── layout.pug
+
+diretórios e 9 arquivos
+```
+
+<Alert type="informações">
+
+A estrutura do aplicativo criada pelo gerador é apenas uma das muitas maneiras de estruturar aplicativos Express.
+Sinta-se livre para usar esta estrutura ou modificá-la para atender às suas necessidades.
+
+</Alert>
diff --git a/src/content/docs/pt-br/5x/starter/hello-world.mdx b/src/content/docs/pt-br/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..3410dc5564
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Olá, exemplo do mundo
+description: Comece com o Express.js construindo uma simples aplicação 'Hello World'', demonstrando a configuração básica e a criação de servidor para iniciantes.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="informações">
+
+Embutido abaixo é essencialmente o aplicativo Expresso mais simples que você pode criar. É um único aplicativo de arquivo
+&mdash; _não_ o que você obteria se usar o [Express generator](/en/starter/generator), que
+cria o andaime para um aplicativo completo com vários arquivos JavaScript, modelos Jade e subdiretórios
+para vários fins.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.end('Olá Mundo!');
+});
+
+app.listen(port, () => {
+  console.log(`Exemplo app escutando na porta ${port}`);
+});
+```
+
+Este aplicativo inicia um servidor e escuta na porta 3000 para conexões. O aplicativo responde com "Olá Mundo!" para solicitações
+para a URL raiz (`/`) ou _route_. Para todos os outros caminhos, responderá com um **404 Não Encontrado**.
+
+## Executando localmente
+
+Primeiro, crie um diretório chamado `myapp`, mude para ele e execute `npm init`. Em seguida, instale `express` como uma dependência, conforme o [guia de instalação](/en/starter/installing).
+
+No diretório `myapp`, crie um arquivo chamado `app.js` e copie o código do exemplo acima.
+
+<Alert type="alerta">
+
+O `req` (requisição) e `res` (resposta) são exatamente os mesmos objetos que o Node fornece, para que você possa
+invocar `req. ipe()`, `req.on('data', callback)`, e qualquer outra coisa que você faria sem o Express
+envolvido.
+
+</Alert>
+
+Execute o aplicativo com o seguinte comando:
+
+```bash
+$ node app.js
+```
+
+Em seguida, carregue `http://localhost:3000/` em um navegador para ver a saída.
diff --git a/src/content/docs/pt-br/5x/starter/installing.mdx b/src/content/docs/pt-br/5x/starter/installing.mdx
new file mode 100644
index 0000000000..b01c680fef
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Instalando
+description: Aprenda a instalar o Express.js no seu ambiente Node.js, incluindo a configuração do diretório do seu projeto e o gerenciamento de dependências com npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Antes de começar, certifique-se de ter [Node.js](https://nodejs.org/) 18 ou superior instalado. Em seguida, crie um diretório para a sua aplicação e navegue até ele.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use o comando `npm init` para criar um arquivo `package.json` para sua aplicação.
+Para obter mais informações sobre como funciona o arquivo `package.json`, veja [Especificações da manipulação do package.json do npm](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+Este comando avisa você para várias coisas, como o nome e a versão de seu aplicativo.
+Por enquanto, você simplesmente pode clicar em RETURN para aceitar os padrões para a maioria deles, com a seguinte exceção:
+
+```
+ponto de entrada: (index.js)
+```
+
+Digite `app.js`, ou o que quiser que o nome do arquivo principal seja. Se você quer que seja `index.js`, pressione RETURN para aceitar o nome de arquivo padrão sugerido.
+
+Agora, instale o Express no diretório `myapp` e salve-o na lista de dependências. Por exemplo:
+
+```bash
+Instalação npm expressiva
+```
+
+Para instalar o Express temporariamente e não adicioná-lo à lista de dependências:
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/pt-br/5x/starter/static-files.mdx b/src/content/docs/pt-br/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..dcd21f0ab2
--- /dev/null
+++ b/src/content/docs/pt-br/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Servindo arquivos estáticos no Express
+description: Entenda como servir arquivos estáticos como imagens, CSS e JavaScript em aplicativos Express.js usando o middleware "static".
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Para servir arquivos estáticos como imagens, arquivos CSS e arquivos JavaScript, use a função `express.static` middleware embutida no Express.
+
+A assinatura da função é:
+
+```js
+express.static(root, [options]);
+```
+
+O argumento `root` especifica o diretório raiz do qual se destinam os assets estáticos.
+Para obter mais informações sobre o argumento `options`, consulte [express.static](/en/5x/api#express.static).
+
+Por exemplo, use o seguinte código para servir imagens, arquivos CSS e arquivos JavaScript em um diretório chamado `public`:
+
+```js
+app.use(express.static('público'));
+```
+
+Agora, você pode carregar os arquivos que estão no diretório `public`:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="informações">
+
+Expresso procura os arquivos relativos ao diretório estático, então o nome do diretório estático
+não faz parte do URL.
+
+</Alert>
+
+Para usar vários diretórios de ativos estáticos, chame a função `express.static` middleware várias vezes:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Expresso olha os arquivos na ordem em que você definiu os diretórios estáticos com a função de middleware `express.static`.
+
+<Alert type="informações">
+
+Para melhores resultados, use um proxy
+reverso cache para melhorar o desempenho do
+servindo ativos estáticos.
+
+</Alert>
+
+Para criar um prefixo de caminho virtual (onde o caminho não existe realmente no sistema de arquivos) para arquivos que são servidos pelo `express. função tática`, [especifique um caminho de montagem](/en/5x/api#app.use) para o diretório estático, conforme mostrado abaixo:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Agora, você pode carregar os arquivos que estão no diretório `public` a partir do prefixo de caminho `/static`.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+No entanto, o caminho que você fornece para a função `express.static` é relativo ao diretório de onde você inicia seu processo `node`. Se você executar o aplicativo expresso a partir de outro diretório, é mais seguro usar o caminho absoluto do diretório que você deseja servir:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+Para mais detalhes sobre a função `serve-static` e suas opções, consulte [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/zh-tw/4x/advanced/developing-template-engines.md b/src/content/docs/zh-tw/4x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/zh-tw/4x/guide/behind-proxies.mdx b/src/content/docs/zh-tw/4x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/zh-tw/4x/guide/debugging.mdx b/src/content/docs/zh-tw/4x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/4x/guide/error-handling.mdx b/src/content/docs/zh-tw/4x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/4x/guide/overriding-express-api.md b/src/content/docs/zh-tw/4x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/zh-tw/4x/guide/routing.mdx b/src/content/docs/zh-tw/4x/guide/routing.mdx
new file mode 100644
index 0000000000..930e7b8438
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/5x/api#app.METHOD). You can also use [app.all()](/en/5x/api#app.all) to handle all HTTP methods and [app.use()](/en/5x/api#app.use) to
+specify middleware as the callback function (See [Using middleware](/en/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/5x/api#app.METHOD).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
+
+<Alert type="alert">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="alert">
+
+In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route
+paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+### Route paths based on strings
+
+This route path will match requests to the root route, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+This route path will match requests to `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+This route path will match requests to `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Route paths based on string patterns
+
+<Alert type="alert">
+
+The string patterns in Express 5 no longer work. Please refer to the migration
+guide for more information.
+
+</Alert>
+
+This route path will match `acd` and `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+This route path will match `/abe` and `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Route paths based on regular expressions
+
+This route path will match anything with an "a" in it.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alert">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
+
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warning">
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\`
+characters with an additional backslash, for example `\d+`.
+
+</Alert>
+
+<Alert type="warning">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                        | Description                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/5x/api#res.end)               | End the response process.                                                             |
+| [res.json()](/en/5x/api#res.json)             | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirect a request.                                                                   |
+| [res.render()](/en/5x/api#res.render)         | Render a view template.                                                               |
+| [res.send()](/en/5x/api#res.send)             | Send a response of various types.                                                     |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/5x/api#router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/zh-tw/4x/guide/using-middleware.mdx b/src/content/docs/zh-tw/4x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/zh-tw/4x/guide/using-template-engines.mdx b/src/content/docs/zh-tw/4x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/zh-tw/4x/guide/writing-middleware.mdx b/src/content/docs/zh-tw/4x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..3849cfe1fa
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/guide/writing-middleware.mdx
@@ -0,0 +1,239 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+<div class="table-scroller">
+<table id="mw-fig">
+<tr>
+<td id="mw-fig-imgcell">
+<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
+</td>
+<td class="mw-fig-callouts">
+<div class="callout" id="callout1">HTTP method for which the middleware function applies.</div>
+
+<div class="callout" id="callout2">
+  Path (route) for which the middleware function applies.
+</div>
+
+<div class="callout" id="callout3">
+  The middleware function.
+</div>
+
+<div class="callout" id="callout4">
+  Callback argument to the middleware function, called "next" by convention.
+</div>
+
+<div class="callout" id="callout5">
+  HTTP <a href="/en/5x/api#res">response</a> argument to the middleware function, called "res" by
+  convention.
+</div>
+
+<div class="callout" id="callout6">HTTP <a href="/en/5x/api#req">request</a> argument to the middleware function, called "req" by convention.</div>
+</td>
+</tr>
+</table>
+</div>
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/zh-tw/4x/starter/basic-routing.mdx b/src/content/docs/zh-tw/4x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..73c12f3893
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the Hello world
+example.
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/zh-tw/4x/starter/examples.mdx b/src/content/docs/zh-tw/4x/starter/examples.mdx
new file mode 100644
index 0000000000..6685b9cbe4
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/examples.mdx
@@ -0,0 +1,45 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+- [auth](https://github.com/expressjs/express/tree/4.x/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/4.x/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/4.x/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/4.x/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/4.x/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/4.x/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/4.x/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/4.x/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/4.x/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/4.x/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/4.x/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/4.x/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/4.x/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/4.x/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/4.x/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/4.x/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/4.x/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/4.x/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/4.x/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/4.x/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/4.x/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/4.x/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/4.x/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/4.x/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/4.x/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+  This information refers to third-party sites, products, or modules that are not maintained by the
+  Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+  Expressjs project team.
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/zh-tw/4x/starter/faq.md b/src/content/docs/zh-tw/4x/starter/faq.md
new file mode 100644
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/zh-tw/4x/starter/generator.mdx b/src/content/docs/zh-tw/4x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/4x/starter/hello-world.mdx b/src/content/docs/zh-tw/4x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/zh-tw/4x/starter/installing.mdx b/src/content/docs/zh-tw/4x/starter/installing.mdx
new file mode 100644
index 0000000000..fc66c7f9df
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/installing.mdx
@@ -0,0 +1,50 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 0.10 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
+
+<Alert type="info">
+
+By default with version npm 5.0+, `npm install` adds the module to the `dependencies` list in the
+`package.json` file; with earlier versions of npm, you must specify the `--save` option
+explicitly. Then, afterwards, running `npm install` in the app directory will automatically
+install modules in the dependencies list.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/4x/starter/static-files.mdx b/src/content/docs/zh-tw/4x/starter/static-files.mdx
new file mode 100644
index 0000000000..98855e0d05
--- /dev/null
+++ b/src/content/docs/zh-tw/4x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/docs/zh-tw/5x/advanced/developing-template-engines.md b/src/content/docs/zh-tw/5x/advanced/developing-template-engines.md
new file mode 100644
index 0000000000..6e9710fbc5
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/advanced/developing-template-engines.md
@@ -0,0 +1,43 @@
+---
+title: Developing template engines for Express
+description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
+---
+
+Use the `app.engine(ext, callback)` method to create your own template engine. `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
+
+The following code is an example of implementing a very simple template engine for rendering `.ntl` files.
+
+```js
+const fs = require('fs'); // this engine requires the fs module
+app.engine('ntl', (filePath, options, callback) => {
+  // define the template engine
+  fs.readFile(filePath, (err, content) => {
+    if (err) return callback(err);
+    // this is an extremely simple template engine
+    const rendered = content
+      .toString()
+      .replace('#title#', `<title>${options.title}</title>`)
+      .replace('#message#', `<h1>${options.message}</h1>`);
+    return callback(null, rendered);
+  });
+});
+app.set('views', './views'); // specify the views directory
+app.set('view engine', 'ntl'); // register the template engine
+```
+
+Your app will now be able to render `.ntl` files. Create a file named `index.ntl` in the `views` directory with the following content.
+
+```pug
+#title#
+#message#
+```
+
+Then, create the following route in your app.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, `index.ntl` will be rendered as HTML.
diff --git a/src/content/docs/zh-tw/5x/guide/behind-proxies.mdx b/src/content/docs/zh-tw/5x/guide/behind-proxies.mdx
new file mode 100644
index 0000000000..d96970dd67
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/behind-proxies.mdx
@@ -0,0 +1,102 @@
+---
+title: Express behind proxies
+description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
+
+<Alert type="info">
+
+When configuring the `trust proxy` setting, it is important to understand the exact setup of the
+reverse proxy. Since this setting will trust values provided in the request, it is important that
+the combination of the setting in Express matches how the reverse proxy operates.
+
+</Alert>
+
+The application setting `trust proxy` may be set to one of the values listed in the following table.
+
+<table class="doctable" border="1" markdown="1">
+  <thead><tr><th>Type</th><th>Value</th></tr></thead>
+  <tbody>
+    <tr>
+      <td>Boolean</td>
+<td markdown="1">
+If `true`, the client's IP address is understood as the left-most entry in the `X-Forwarded-For` header.
+
+If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
+
+<Alert type="warning">
+When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>IP addresses</td>
+<td markdown="1">
+An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
+
+- loopback - `127.0.0.1/8`, `::1/128`
+- linklocal - `169.254.0.0/16`, `fe80::/10`
+- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
+
+You can set IP addresses in any of the following ways:
+
+```js
+app.set('trust proxy', 'loopback'); // specify a single subnet
+app.set('trust proxy', 'loopback, 123.123.123.123'); // specify a subnet and an address
+app.set('trust proxy', 'loopback, linklocal, uniquelocal'); // specify multiple subnets as CSV
+app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']); // specify multiple subnets as an array
+```
+
+When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
+
+</td>
+    </tr>
+    <tr>
+      <td>Number</td>
+<td markdown="1">
+Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
+
+<Alert type="warning">
+When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
+</Alert>
+</td>
+    </tr>
+    <tr>
+      <td>Function</td>
+<td markdown="1">
+Custom trust implementation.
+
+```js
+app.set('trust proxy', (ip) => {
+  if (ip === '127.0.0.1' || ip === '123.123.123.123')
+    return true; // trusted IPs
+  else return false;
+});
+```
+
+</td>
+    </tr>
+  </tbody>
+</table>
+
+Enabling `trust proxy` will have the following impact:
+
+<ul>
+  <li markdown="1">
+    The value of [req.hostname](/en/api#req.hostname) is derived from the value set in the
+    `X-Forwarded-Host` header, which can be set by the client or by the proxy.
+  </li>
+  <li markdown="1">
+    `X-Forwarded-Proto` can be set by the reverse proxy to tell the app whether it is `https` or
+    `http` or even an invalid name. This value is reflected by [req.protocol](/en/api#req.protocol).
+  </li>
+  <li markdown="1">
+    The [req.ip](/en/api#req.ip) and [req.ips](/en/api#req.ips) values are populated based on the
+    socket address and `X-Forwarded-For` header, starting at the first untrusted address.
+  </li>
+</ul>
+
+The `trust proxy` setting is implemented using the [proxy-addr](https://www.npmjs.com/package/proxy-addr) package. For more information, see its documentation.
diff --git a/src/content/docs/zh-tw/5x/guide/debugging.mdx b/src/content/docs/zh-tw/5x/guide/debugging.mdx
new file mode 100644
index 0000000000..a7750f5427
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/debugging.mdx
@@ -0,0 +1,124 @@
+---
+title: Debugging Express
+description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To see all the internal logs used in Express, set the `DEBUG` environment variable to
+`express:*` when launching your app.
+
+```bash
+$ DEBUG=express:* node index.js
+```
+
+On Windows, use the corresponding command.
+
+```bash
+> $env:DEBUG = "express:*"; node index.js
+```
+
+Running this command on the default app generated by the [express generator](/en/starter/generator) prints the following output:
+
+```bash
+$ DEBUG=express:* node ./bin/www
+  express:router:route new / +0ms
+  express:router:layer new / +1ms
+  express:router:route get / +1ms
+  express:router:layer new / +0ms
+  express:router:route new / +1ms
+  express:router:layer new / +0ms
+  express:router:route get / +0ms
+  express:router:layer new / +0ms
+  express:application compile etag weak +1ms
+  express:application compile query parser extended +0ms
+  express:application compile trust proxy false +0ms
+  express:application booting in development mode +1ms
+  express:router use / query +0ms
+  express:router:layer new / +0ms
+  express:router use / expressInit +0ms
+  express:router:layer new / +0ms
+  express:router use / favicon +1ms
+  express:router:layer new / +0ms
+  express:router use / logger +0ms
+  express:router:layer new / +0ms
+  express:router use / jsonParser +0ms
+  express:router:layer new / +1ms
+  express:router use / urlencodedParser +0ms
+  express:router:layer new / +0ms
+  express:router use / cookieParser +0ms
+  express:router:layer new / +0ms
+  express:router use / stylus +90ms
+  express:router:layer new / +0ms
+  express:router use / serveStatic +0ms
+  express:router:layer new / +0ms
+  express:router use / router +0ms
+  express:router:layer new / +1ms
+  express:router use /users router +0ms
+  express:router:layer new /users +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+  express:router use / &lt;anonymous&gt; +0ms
+  express:router:layer new / +0ms
+```
+
+When a request is then made to the app, you will see the logs specified in the Express code:
+
+```bash
+  express:router dispatching GET / +4h
+  express:router query  : / +2ms
+  express:router expressInit  : / +0ms
+  express:router favicon  : / +0ms
+  express:router logger  : / +1ms
+  express:router jsonParser  : / +0ms
+  express:router urlencodedParser  : / +1ms
+  express:router cookieParser  : / +0ms
+  express:router stylus  : / +0ms
+  express:router serveStatic  : / +2ms
+  express:router router  : / +2ms
+  express:router dispatching GET / +1ms
+  express:view lookup "index.pug" +338ms
+  express:view stat "/projects/example/views/index.pug" +0ms
+  express:view render "/projects/example/views/index.pug" +1ms
+```
+
+To see the logs only from the router implementation, set the value of `DEBUG` to `express:router`. Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
+
+## Applications generated by `express`
+
+An application generated by the `express` command uses the `debug` module and its debug namespace is scoped to the name of the application.
+
+For example, if you generated the app with `$ express sample-app`, you can enable the debug statements with the following command:
+
+```bash
+$ DEBUG=sample-app:* node ./bin/www
+```
+
+You can specify more than one debug namespace by assigning a comma-separated list of names:
+
+```bash
+$ DEBUG=http,mail,express:* node index.js
+```
+
+## Advanced options
+
+When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
+
+| Name                | Purpose                                           |
+| ------------------- | ------------------------------------------------- |
+| `DEBUG`             | Enables/disables specific debugging namespaces.   |
+| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
+| `DEBUG_DEPTH`       | Object inspection depth.                          |
+| `DEBUG_FD`          | File descriptor to write debug output to.         |
+| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
+
+<Alert type="info">
+
+The environment variables beginning with `DEBUG_` end up being converted into an Options object
+that gets used with `%o`/`%O` formatters. See the Node.js documentation for
+[`util.inspect()`](https://nodejs.org/api/util#util_util_inspect_object_options) for the complete
+list.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/5x/guide/error-handling.mdx b/src/content/docs/zh-tw/5x/guide/error-handling.mdx
new file mode 100644
index 0000000000..e34218f841
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/error-handling.mdx
@@ -0,0 +1,312 @@
+---
+title: Error Handling
+description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Error Handling_ refers to how Express catches and processes errors that
+occur both synchronously and asynchronously. Express comes with a default error
+handler so you don't need to write your own to get started.
+
+## Catching Errors
+
+It's important to ensure that Express catches all errors that occur while
+running route handlers and middleware.
+
+Errors that occur in synchronous code inside route handlers and middleware
+require no extra work. If synchronous code throws an error, then Express will
+catch and process it. For example:
+
+```js
+app.get('/', (req, res) => {
+  throw new Error('BROKEN'); // Express will catch this on its own.
+});
+```
+
+For errors returned from asynchronous functions invoked by route handlers
+and middleware, you must pass them to the `next()` function, where Express will
+catch and process them. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  fs.readFile('/file-does-not-exist', (err, data) => {
+    if (err) {
+      next(err); // Pass errors to Express.
+    } else {
+      res.send(data);
+    }
+  });
+});
+```
+
+Starting with Express 5, route handlers and middleware that return a Promise
+will call `next(value)` automatically when they reject or throw an error.
+For example:
+
+```js
+app.get('/user/:id', async (req, res, next) => {
+  const user = await getUserById(req.params.id);
+  res.send(user);
+});
+```
+
+If `getUserById` throws an error or rejects, `next` will be called with either
+the thrown error or the rejected value. If no rejected value is provided, `next`
+will be called with a default Error object provided by the Express router.
+
+If you pass anything to the `next()` function (except the string `'route'`),
+Express regards the current request as being an error and will skip any
+remaining non-error handling routing and middleware functions.
+
+If the callback in a sequence provides no data, only errors, you can simplify
+this code as follows:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.writeFile('/inaccessible-path', 'data', next);
+  },
+  function (req, res) {
+    res.send('OK');
+  },
+]);
+```
+
+In the above example, `next` is provided as the callback for `fs.writeFile`,
+which is called with or without errors. If there is no error, the second
+handler is executed, otherwise Express catches and processes the error.
+
+You must catch errors that occur in asynchronous code invoked by route handlers or
+middleware and pass them to Express for processing. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  setTimeout(() => {
+    try {
+      throw new Error('BROKEN');
+    } catch (err) {
+      next(err);
+    }
+  }, 100);
+});
+```
+
+The above example uses a `try...catch` block to catch errors in the
+asynchronous code and pass them to Express. If the `try...catch`
+block were omitted, Express would not catch the error since it is not part of the synchronous
+handler code.
+
+Use promises to avoid the overhead of the `try...catch` block or when using functions
+that return promises. For example:
+
+```js
+app.get('/', (req, res, next) => {
+  Promise.resolve()
+    .then(() => {
+      throw new Error('BROKEN');
+    })
+    .catch(next); // Errors will be passed to Express.
+});
+```
+
+Since promises automatically catch both synchronous errors and rejected promises,
+you can simply provide `next` as the final catch handler and Express will catch errors,
+because the catch handler is given the error as the first argument.
+
+You could also use a chain of handlers to rely on synchronous error
+catching, by reducing the asynchronous code to something trivial. For example:
+
+```js
+app.get('/', [
+  function (req, res, next) {
+    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
+      res.locals.data = data;
+      next(err);
+    });
+  },
+  function (req, res) {
+    res.locals.data = res.locals.data.split(',')[1];
+    res.send(res.locals.data);
+  },
+]);
+```
+
+The above example has a couple of trivial statements from the `readFile`
+call. If `readFile` causes an error, then it passes the error to Express, otherwise you
+quickly return to the world of synchronous error handling in the next handler
+in the chain. Then, the example above tries to process the data. If this fails, then the
+synchronous error handler will catch it. If you had done this processing inside
+the `readFile` callback, then the application might exit and the Express error
+handlers would not run.
+
+Whichever method you use, if you want Express error handlers to be called in and the
+application to survive, you must ensure that Express receives the error.
+
+## The default error handler
+
+Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
+
+If you pass an error to `next()` and you do not handle it in a custom error
+handler, it will be handled by the built-in error handler; the error will be
+written to the client with the stack trace. The stack trace is not included
+in the production environment.
+
+<Alert type="info">
+
+Set the environment variable `NODE_ENV` to `production`, to run the app in production mode.
+
+</Alert>
+
+When an error is written, the following information is added to the
+response:
+
+- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
+  this value is outside the 4xx or 5xx range, it will be set to 500.
+- The `res.statusMessage` is set according to the status code.
+- The body will be the HTML of the status code message when in production
+  environment, otherwise will be `err.stack`.
+- Any headers specified in an `err.headers` object.
+
+If you call `next()` with an error after you have started writing the
+response (for example, if you encounter an error while streaming the
+response to the client), the Express default error handler closes the
+connection and fails the request.
+
+So when you add a custom error handler, you must delegate to
+the default Express error handler, when the headers
+have already been sent to the client:
+
+```js
+function errorHandler(err, req, res, next) {
+  if (res.headersSent) {
+    return next(err);
+  }
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+Note that the default error handler can get triggered if you call `next()` with an error
+in your code more than once, even if custom error handling middleware is in place.
+
+Other error handling middleware can be found at [Express middleware](/en/resources/middleware).
+
+## Writing error handlers
+
+Define error-handling middleware functions in the same way as other middleware functions,
+except error-handling functions have four arguments instead of three:
+`(err, req, res, next)`. For example:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+You define error-handling middleware last, after other `app.use()` and routes calls; for example:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use((err, req, res, next) => {
+  // logic
+});
+```
+
+Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
+
+For organizational (and higher-level framework) purposes, you can define
+several error-handling middleware functions, much as you would with
+regular middleware functions. For example, to define an error-handler
+for requests made by using `XHR` and those without:
+
+```js
+const bodyParser = require('body-parser');
+const methodOverride = require('method-override');
+
+app.use(
+  bodyParser.urlencoded({
+    extended: true,
+  })
+);
+app.use(bodyParser.json());
+app.use(methodOverride());
+app.use(logErrors);
+app.use(clientErrorHandler);
+app.use(errorHandler);
+```
+
+In this example, the generic `logErrors` might write request and
+error information to `stderr`, for example:
+
+```js
+function logErrors(err, req, res, next) {
+  console.error(err.stack);
+  next(err);
+}
+```
+
+Also in this example, `clientErrorHandler` is defined as follows; in this case, the error is explicitly passed along to the next one.
+
+Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
+
+```js
+function clientErrorHandler(err, req, res, next) {
+  if (req.xhr) {
+    res.status(500).send({ error: 'Something failed!' });
+  } else {
+    next(err);
+  }
+}
+```
+
+Implement the "catch-all" `errorHandler` function as follows (for example):
+
+```js
+function errorHandler(err, req, res, next) {
+  res.status(500);
+  res.render('error', { error: err });
+}
+```
+
+If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
+
+```js
+app.get(
+  '/a_route_behind_paywall',
+  (req, res, next) => {
+    if (!req.user.hasPaid) {
+      // continue handling this request
+      next('route');
+    } else {
+      next();
+    }
+  },
+  (req, res, next) => {
+    PaidContent.find((err, doc) => {
+      if (err) return next(err);
+      res.json(doc);
+    });
+  }
+);
+```
+
+In this example, the `getPaidContent` handler will be skipped but any remaining handlers in `app` for `/a_route_behind_paywall` would continue to be executed.
+
+<Alert type="info">
+
+Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.
+`next(err)` will skip all remaining handlers in the chain except for those that are set up to
+handle errors as described above.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/5x/guide/overriding-express-api.md b/src/content/docs/zh-tw/5x/guide/overriding-express-api.md
new file mode 100644
index 0000000000..f5281a58f5
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/overriding-express-api.md
@@ -0,0 +1,68 @@
+---
+title: Overriding the Express API
+description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
+---
+
+The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
+
+1. The global prototypes at `express.request` and `express.response`.
+2. App-specific prototypes at `app.request` and `app.response`.
+
+Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
+
+## Methods
+
+You can override the signature and behavior of existing methods with your own, by assigning a custom function.
+
+Following is an example of overriding the behavior of [res.sendStatus](/en/4x/api#res.sendStatus).
+
+```js
+app.response.sendStatus = function (statusCode, type, message) {
+  // code is intentionally kept simple for demonstration purpose
+  return this.contentType(type).status(statusCode).send(message);
+};
+```
+
+The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
+
+The overridden method may now be used this way:
+
+```js
+res.sendStatus(404, 'application/json', '{"error":"resource not found"}');
+```
+
+## Properties
+
+Properties in the Express API are either:
+
+1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
+2. Defined as getters (ex: `req.secure`, `req.ip`)
+
+Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
+
+Properties under category 2 can be overwritten using the Express API extensions API.
+
+The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
+
+```js
+Object.defineProperty(app.request, 'ip', {
+  configurable: true,
+  enumerable: true,
+  get() {
+    return this.get('Client-IP');
+  },
+});
+```
+
+## Prototype
+
+In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
+
+Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
+
+```js
+// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
+// for the given app reference
+Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype);
+Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype);
+```
diff --git a/src/content/docs/zh-tw/5x/guide/routing.mdx b/src/content/docs/zh-tw/5x/guide/routing.mdx
new file mode 100644
index 0000000000..930e7b8438
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/routing.mdx
@@ -0,0 +1,418 @@
+---
+title: Routing
+description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
+For an introduction to routing, see [Basic routing](/en/starter/basic-routing).
+
+You define routing using methods of the Express `app` object that correspond to HTTP methods;
+for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
+see [app.METHOD](/en/5x/api#app.METHOD). You can also use [app.all()](/en/5x/api#app.all) to handle all HTTP methods and [app.use()](/en/5x/api#app.use) to
+specify middleware as the callback function (See [Using middleware](/en/guide/using-middleware) for details).
+
+These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
+
+In fact, the routing methods can have more than one callback function as arguments.
+With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
+to the next callback.
+
+The following code is an example of a very basic route.
+
+```js
+const express = require('express');
+const app = express();
+
+// respond with "hello world" when a GET request is made to the homepage
+app.get('/', (req, res) => {
+  res.send('hello world');
+});
+```
+
+## Route methods
+
+A route method is derived from one of the HTTP methods, and is attached to an instance of the `express` class.
+
+The following code is an example of routes that are defined for the `GET` and the `POST` methods to the root of the app.
+
+```js
+// GET method route
+app.get('/', (req, res) => {
+  res.send('GET request to the homepage');
+});
+
+// POST method route
+app.post('/', (req, res) => {
+  res.send('POST request to the homepage');
+});
+```
+
+Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
+For a full list, see [app.METHOD](/en/5x/api#app.METHOD).
+
+There is a special routing method, `app.all()`, used to load middleware functions at a path for _all_ HTTP request methods. For example, the following handler is executed for requests to the route `"/secret"` whether using `GET`, `POST`, `PUT`, `DELETE`, or any other HTTP request method supported in the [http module](https://nodejs.org/api/http.html#http_http_methods).
+
+```js
+app.all('/secret', (req, res, next) => {
+  console.log('Accessing the secret section ...');
+  next(); // pass control to the next handler
+});
+```
+
+## Route paths
+
+Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
+
+<Alert type="alert">
+
+In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version
+4, please review the [migration guide](/en/guide/migrating-5#path-syntax) for more information.
+
+</Alert>
+
+<Alert type="alert">
+
+In express 4, regular expression characters such as `$` need to be escaped with a `\`.
+
+</Alert>
+
+<Alert type="info">
+
+Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route
+paths; see the path-to-regexp documentation for all the possibilities in defining route paths.
+[Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for
+testing basic Express routes, although it does not support pattern matching.
+
+</Alert>
+
+<Alert type="warning">Query strings are not part of the route path.</Alert>
+
+### Route paths based on strings
+
+This route path will match requests to the root route, `/`.
+
+```js
+app.get('/', (req, res) => {
+  res.send('root');
+});
+```
+
+This route path will match requests to `/about`.
+
+```js
+app.get('/about', (req, res) => {
+  res.send('about');
+});
+```
+
+This route path will match requests to `/random.text`.
+
+```js
+app.get('/random.text', (req, res) => {
+  res.send('random.text');
+});
+```
+
+### Route paths based on string patterns
+
+<Alert type="alert">
+
+The string patterns in Express 5 no longer work. Please refer to the migration
+guide for more information.
+
+</Alert>
+
+This route path will match `acd` and `abcd`.
+
+```js
+app.get('/ab?cd', (req, res) => {
+  res.send('ab?cd');
+});
+```
+
+This route path will match `abcd`, `abbcd`, `abbbcd`, and so on.
+
+```js
+app.get('/ab+cd', (req, res) => {
+  res.send('ab+cd');
+});
+```
+
+This route path will match `abcd`, `abxcd`, `abRANDOMcd`, `ab123cd`, and so on.
+
+```js
+app.get('/ab*cd', (req, res) => {
+  res.send('ab*cd');
+});
+```
+
+This route path will match `/abe` and `/abcde`.
+
+```js
+app.get('/ab(cd)?e', (req, res) => {
+  res.send('ab(cd)?e');
+});
+```
+
+### Route paths based on regular expressions
+
+This route path will match anything with an "a" in it.
+
+```js
+app.get(/a/, (req, res) => {
+  res.send('/a/');
+});
+```
+
+This route path will match `butterfly` and `dragonfly`, but not `butterflyman`, `dragonflyman`, and so on.
+
+```js
+app.get(/.*fly$/, (req, res) => {
+  res.send('/.*fly$/');
+});
+```
+
+## Route parameters
+
+Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
+
+```
+Route path: /users/:userId/books/:bookId
+Request URL: http://localhost:3000/users/34/books/8989
+req.params: { "userId": "34", "bookId": "8989" }
+```
+
+To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
+
+```js
+app.get('/users/:userId/books/:bookId', (req, res) => {
+  res.send(req.params);
+});
+```
+
+<Alert type="alert">
+
+The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
+
+</Alert>
+
+Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
+
+```
+Route path: /flights/:from-:to
+Request URL: http://localhost:3000/flights/LAX-SFO
+req.params: { "from": "LAX", "to": "SFO" }
+```
+
+```
+Route path: /plantae/:genus.:species
+Request URL: http://localhost:3000/plantae/Prunus.persica
+req.params: { "genus": "Prunus", "species": "persica" }
+```
+
+<Alert type="alert">
+
+In express 5, Regexp characters are not supported in route paths, for more information please
+refer to the [migration guide](/en/guide/migrating-5#path-syntax).
+
+</Alert>
+
+To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
+
+```
+Route path: /user/:userId(\d+)
+Request URL: http://localhost:3000/user/42
+req.params: {"userId": "42"}
+```
+
+<Alert type="warning">
+
+Because the regular expression is usually part of a literal string, be sure to escape any `\`
+characters with an additional backslash, for example `\d+`.
+
+</Alert>
+
+<Alert type="warning">
+In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
+</Alert>
+
+## Route handlers
+
+You can provide multiple callback functions that behave like [middleware](/en/guide/using-middleware) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  if (req.params.id === '0') {
+    return next('route');
+  }
+  res.send(`User ${req.params.id}`);
+});
+
+app.get('/user/:id', (req, res) => {
+  res.send('Special handler for user ID 0');
+});
+```
+
+In this example:
+
+- `GET /user/5` → handled by first route → sends "User 5"
+- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
+
+Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
+
+A single callback function can handle a route. For example:
+
+```js
+app.get('/example/a', (req, res) => {
+  res.send('Hello from A!');
+});
+```
+
+More than one callback function can handle a route (make sure you specify the `next` object). For example:
+
+```js
+app.get(
+  '/example/b',
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from B!');
+  }
+);
+```
+
+An array of callback functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+const cb2 = function (req, res) {
+  res.send('Hello from C!');
+};
+
+app.get('/example/c', [cb0, cb1, cb2]);
+```
+
+A combination of independent functions and arrays of functions can handle a route. For example:
+
+```js
+const cb0 = function (req, res, next) {
+  console.log('CB0');
+  next();
+};
+
+const cb1 = function (req, res, next) {
+  console.log('CB1');
+  next();
+};
+
+app.get(
+  '/example/d',
+  [cb0, cb1],
+  (req, res, next) => {
+    console.log('the response will be sent by the next function ...');
+    next();
+  },
+  (req, res) => {
+    res.send('Hello from D!');
+  }
+);
+```
+
+## Response methods
+
+The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
+
+| Method                                        | Description                                                                           |
+| --------------------------------------------- | ------------------------------------------------------------------------------------- |
+| [res.download()](/en/5x/api#res.download)     | Prompt a file to be downloaded.                                                       |
+| [res.end()](/en/5x/api#res.end)               | End the response process.                                                             |
+| [res.json()](/en/5x/api#res.json)             | Send a JSON response.                                                                 |
+| [res.jsonp()](/en/5x/api#res.jsonp)           | Send a JSON response with JSONP support.                                              |
+| [res.redirect()](/en/5x/api#res.redirect)     | Redirect a request.                                                                   |
+| [res.render()](/en/5x/api#res.render)         | Render a view template.                                                               |
+| [res.send()](/en/5x/api#res.send)             | Send a response of various types.                                                     |
+| [res.sendFile()](/en/5x/api#res.sendFile)     | Send a file as an octet stream.                                                       |
+| [res.sendStatus()](/en/5x/api#res.sendStatus) | Set the response status code and send its string representation as the response body. |
+
+## app.route()
+
+You can create chainable route handlers for a route path by using `app.route()`.
+Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/en/5x/api#router).
+
+Here is an example of chained route handlers that are defined by using `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+## express.Router
+
+Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
+
+Create a router file named `birds.js` in the app directory, with the following content:
+
+```js
+const express = require('express');
+const router = express.Router();
+
+// middleware that is specific to this router
+const timeLog = (req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+};
+router.use(timeLog);
+
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+const birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to `/birds` and `/birds/about`, as well as call the `timeLog` middleware function that is specific to the route.
+
+But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/en/5x/api#app.use).
+
+```js
+const router = express.Router({ mergeParams: true });
+```
diff --git a/src/content/docs/zh-tw/5x/guide/using-middleware.mdx b/src/content/docs/zh-tw/5x/guide/using-middleware.mdx
new file mode 100644
index 0000000000..36f8034ef2
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/using-middleware.mdx
@@ -0,0 +1,299 @@
+---
+title: Using middleware
+description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is a routing and middleware web framework that has minimal functionality of its own: An Express application is essentially a series of middleware function calls.
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware function in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+An Express application can use the following types of middleware:
+
+- [Application-level middleware](#middleware.application)
+- [Router-level middleware](#middleware.router)
+- [Error-handling middleware](#middleware.error-handling)
+- [Built-in middleware](#middleware.built-in)
+- [Third-party middleware](#middleware.third-party)
+
+You can load application-level and router-level middleware with an optional mount path.
+You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
+
+## Application-level middleware
+
+Bind application-level middleware to an instance of the [app object](/en/5x/api#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
+
+This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
+
+```js
+const express = require('express');
+const app = express();
+
+app.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+```
+
+This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
+HTTP request on the `/user/:id` path.
+
+```js
+app.use('/user/:id', (req, res, next) => {
+  console.log('Request Type:', req.method);
+  next();
+});
+```
+
+This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
+
+```js
+app.get('/user/:id', (req, res, next) => {
+  res.send('USER');
+});
+```
+
+Here is an example of loading a series of middleware functions at a mount point, with a mount path.
+It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
+
+```js
+app.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+```
+
+Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('ID:', req.params.id);
+    next();
+  },
+  (req, res, next) => {
+    res.send('User Info');
+  }
+);
+
+// handler for the /user/:id path, which prints the user ID
+app.get('/user/:id', (req, res, next) => {
+  res.send(req.params.id);
+});
+```
+
+To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
+
+<Alert type="info">
+
+`next('route')` will work only in middleware functions that were loaded by using the
+`app.METHOD()` or `router.METHOD()` functions.
+
+</Alert>
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+app.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next route
+    if (req.params.id === '0') next('route');
+    // otherwise pass the control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // send a regular response
+    res.send('regular');
+  }
+);
+
+// handler for the /user/:id path, which sends a special response
+app.get('/user/:id', (req, res, next) => {
+  res.send('special');
+});
+```
+
+Middleware can also be declared in an array for reusability.
+
+This example shows an array with a middleware sub-stack that handles GET requests to the `/user/:id` path
+
+```js
+function logOriginalUrl(req, res, next) {
+  console.log('Request URL:', req.originalUrl);
+  next();
+}
+
+function logMethod(req, res, next) {
+  console.log('Request Type:', req.method);
+  next();
+}
+
+const logStuff = [logOriginalUrl, logMethod];
+app.get('/user/:id', logStuff, (req, res, next) => {
+  res.send('User Info');
+});
+```
+
+## Router-level middleware
+
+Router-level middleware works in the same way as application-level middleware, except it is bound to an instance of `express.Router()`.
+
+```js
+const router = express.Router();
+```
+
+Load router-level middleware by using the `router.use()` and `router.METHOD()` functions.
+
+The following example code replicates the middleware system that is shown above for application-level middleware, by using router-level middleware:
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// a middleware function with no mount path. This code is executed for every request to the router
+router.use((req, res, next) => {
+  console.log('Time:', Date.now());
+  next();
+});
+
+// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
+router.use(
+  '/user/:id',
+  (req, res, next) => {
+    console.log('Request URL:', req.originalUrl);
+    next();
+  },
+  (req, res, next) => {
+    console.log('Request Type:', req.method);
+    next();
+  }
+);
+
+// a middleware sub-stack that handles GET requests to the /user/:id path
+router.get(
+  '/user/:id',
+  (req, res, next) => {
+    // if the user ID is 0, skip to the next router
+    if (req.params.id === '0') next('route');
+    // otherwise pass control to the next middleware function in this stack
+    else next();
+  },
+  (req, res, next) => {
+    // render a regular page
+    res.render('regular');
+  }
+);
+
+// handler for the /user/:id path, which renders a special page
+router.get('/user/:id', (req, res, next) => {
+  console.log(req.params.id);
+  res.render('special');
+});
+
+// mount the router on the app
+app.use('/', router);
+```
+
+To skip the rest of the router's middleware functions, call `next('router')`
+to pass control back out of the router instance.
+
+This example shows a middleware sub-stack that handles GET requests to the `/user/:id` path.
+
+```js
+const express = require('express');
+const app = express();
+const router = express.Router();
+
+// predicate the router with a check and bail out when needed
+router.use((req, res, next) => {
+  if (!req.headers['x-auth']) return next('router');
+  next();
+});
+
+router.get('/user/:id', (req, res) => {
+  res.send('hello, user!');
+});
+
+// use the router and 401 anything falling through
+app.use('/admin', router, (req, res) => {
+  res.sendStatus(401);
+});
+```
+
+## Error-handling middleware
+
+<Alert type="alert">
+
+Error-handling middleware always takes _four_ arguments. You must provide four arguments to
+identify it as an error-handling middleware function. Even if you don't need to use the `next`
+object, you must specify it to maintain the signature. Otherwise, the `next` object will be
+interpreted as regular middleware and will fail to handle errors.
+
+</Alert>
+
+Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For details about error-handling middleware, see: [Error handling](/en/guide/error-handling).
+
+## Built-in middleware
+
+Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). The middleware
+functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
+
+Express has the following built-in middleware functions:
+
+- [express.static](/en/5x/api#express.static) serves static assets such as HTML files, images, and so on.
+- [express.json](/en/5x/api#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
+- [express.urlencoded](/en/5x/api#express.urlencoded) parses incoming requests with URL-encoded payloads. **NOTE: Available with Express 4.16.0+**
+
+## Third-party middleware
+
+Use third-party middleware to add functionality to Express apps.
+
+Install the Node.js module for the required functionality, then load it in your app at the application level or at the router level.
+
+The following example illustrates installing and loading the cookie-parsing middleware function `cookie-parser`.
+
+```bash
+$ npm install cookie-parser
+```
+
+```js
+const express = require('express');
+const app = express();
+const cookieParser = require('cookie-parser');
+
+// load the cookie-parsing middleware
+app.use(cookieParser());
+```
+
+For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware).
diff --git a/src/content/docs/zh-tw/5x/guide/using-template-engines.mdx b/src/content/docs/zh-tw/5x/guide/using-template-engines.mdx
new file mode 100644
index 0000000000..31edcdde82
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/using-template-engines.mdx
@@ -0,0 +1,63 @@
+---
+title: Using template engines with Express
+description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
+variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
+This approach makes it easier to design an HTML page.
+
+The [Express application generator](/en/starter/generator) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
+
+To render template files, set the following [application setting properties](/en/4x/api#app.set), in the default `app.js` created by the generator:
+
+- `views`, the directory where the template files are located. Eg: `app.set('views', './views')`.
+  This defaults to the `views` directory in the application root directory.
+- `view engine`, the template engine to use. For example, to use the Pug template engine: `app.set('view engine', 'pug')`.
+
+Then install the corresponding template engine npm package; for example to install Pug:
+
+```bash
+$ npm install pug --save
+```
+
+<Alert type="alert">
+Express-compliant template engines such as Pug export a function named `__express(filePath, options, callback)`,
+which `res.render()` calls to render the template code.
+
+Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
+library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
+
+</Alert>
+
+After the view engine is set, you don't have to specify the engine or load the template engine module in your app;
+Express loads the module internally, for example:
+
+```js
+app.set('view engine', 'pug');
+```
+
+Then, create a Pug template file named `index.pug` in the `views` directory, with the following content:
+
+```pug
+html
+  head
+    title= title
+  body
+    h1= message
+```
+
+Create a route to render the `index.pug` file. If the `view engine` property is not set,
+you must specify the extension of the `view` file. Otherwise, you can omit it.
+
+```js
+app.get('/', (req, res) => {
+  res.render('index', { title: 'Hey', message: 'Hello there!' });
+});
+```
+
+When you make a request to the home page, the `index.pug` file will be rendered as HTML.
+
+The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/src/content/docs/zh-tw/5x/guide/writing-middleware.mdx b/src/content/docs/zh-tw/5x/guide/writing-middleware.mdx
new file mode 100644
index 0000000000..507c3ac06a
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/guide/writing-middleware.mdx
@@ -0,0 +1,209 @@
+---
+title: Writing middleware for use in Express apps
+description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Middleware_ functions are functions that have access to the [request object](/en/5x/api#req) (`req`), the [response object](/en/5x/api#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
+
+Middleware functions can perform the following tasks:
+
+- Execute any code.
+- Make changes to the request and the response objects.
+- End the request-response cycle.
+- Call the next middleware in the stack.
+
+If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
+
+The following figure shows the elements of a middleware function call:
+
+![Elements of a middleware function call](/images/express-mw.png)
+
+Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
+
+## Example
+
+Here is an example of a simple "Hello World" Express application.
+The remainder of this article will define and add three middleware functions to the application:
+one called `myLogger` that prints a simple log message, one called `requestTime` that
+displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
+
+```js
+const express = require('express');
+const app = express();
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+### Middleware function myLogger
+
+Here is a simple example of a middleware function called "myLogger". This function just prints
+"LOGGED" when a request to the app passes through it. The middleware function is assigned to a
+variable named `myLogger`.
+
+```js
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+```
+
+<Alert type="alert">
+
+Notice the call above to `next()`. Calling this function invokes the next middleware function in
+the app. The `next()` function is not a part of the Node.js or Express API, but is the third
+argument that is passed to the middleware function. The `next()` function could be named anything,
+but by convention it is always named "next". To avoid confusion, always use this convention.
+
+</Alert>
+
+To load the middleware function, call `app.use()`, specifying the middleware function.
+For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
+
+```js
+const express = require('express');
+const app = express();
+
+const myLogger = function (req, res, next) {
+  console.log('LOGGED');
+  next();
+};
+
+app.use(myLogger);
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(3000);
+```
+
+Every time the app receives a request, it prints the message "LOGGED" to the terminal.
+
+The order of middleware loading is important: middleware functions that are loaded first are also executed first.
+
+If `myLogger` is loaded after the route to the root path, the request never reaches it and the app doesn't print "LOGGED", because the route handler of the root path terminates the request-response cycle.
+
+The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
+
+### Middleware function requestTime
+
+Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
+to the request object.
+
+```js
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+```
+
+The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
+
+```js
+const express = require('express');
+const app = express();
+
+const requestTime = function (req, res, next) {
+  req.requestTime = Date.now();
+  next();
+};
+
+app.use(requestTime);
+
+app.get('/', (req, res) => {
+  let responseText = 'Hello World!<br>';
+  responseText += `<small>Requested at: ${req.requestTime}</small>`;
+  res.send(responseText);
+});
+
+app.listen(3000);
+```
+
+When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
+
+### Middleware function validateCookies
+
+Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
+
+Here's an example function that validates cookies with an external async service.
+
+```js
+async function cookieValidator(cookies) {
+  try {
+    await externallyValidateCookie(cookies.testCookie);
+  } catch {
+    throw new Error('Invalid cookies');
+  }
+}
+```
+
+Here, we use the [`cookie-parser`](/en/resources/middleware/cookie-parser) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
+
+```js
+const express = require('express');
+const cookieParser = require('cookie-parser');
+const cookieValidator = require('./cookieValidator');
+
+const app = express();
+
+async function validateCookies(req, res, next) {
+  await cookieValidator(req.cookies);
+  next();
+}
+
+app.use(cookieParser());
+
+app.use(validateCookies);
+
+// error handler
+app.use((err, req, res, next) => {
+  res.status(400).send(err.message);
+});
+
+app.listen(3000);
+```
+
+<Alert type="alert">
+
+Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if
+`cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything
+to the `next()` function (except the string `'route'` or `'router'`), Express regards the current
+request as being an error and will skip any remaining non-error handling routing and middleware
+functions.
+
+</Alert>
+
+Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
+
+For more information about Express middleware, see: [Using Express middleware](/en/guide/using-middleware).
+
+## Configurable middleware
+
+If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
+
+File: `my-middleware.js`
+
+```js
+module.exports = function (options) {
+  return function (req, res, next) {
+    // Implement the middleware function based on the options object
+    next();
+  };
+};
+```
+
+The middleware can now be used as shown below.
+
+```js
+const mw = require('./my-middleware.js');
+
+app.use(mw({ option1: '1', option2: '2' }));
+```
+
+Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/src/content/docs/zh-tw/5x/starter/basic-routing.mdx b/src/content/docs/zh-tw/5x/starter/basic-routing.mdx
new file mode 100644
index 0000000000..73c12f3893
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/basic-routing.mdx
@@ -0,0 +1,67 @@
+---
+title: Basic routing
+description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
+
+Each route can have one or more handler functions, which are executed when the route is matched.
+
+Route definition takes the following structure:
+
+```js
+app.METHOD(PATH, HANDLER);
+```
+
+Where:
+
+- `app` is an instance of `express`.
+- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
+- `PATH` is a path on the server.
+- `HANDLER` is the function executed when the route is matched.
+
+<Alert type="alert">
+
+This tutorial assumes that an instance of `express` named `app` is created and the server is
+running. If you are not familiar with creating an app and starting it, see the Hello world
+example.
+
+</Alert>
+
+The following examples illustrate defining simple routes.
+
+Respond with `Hello World!` on the homepage:
+
+```js
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+```
+
+Respond to a POST request on the root route (`/`), the application's home page:
+
+```js
+app.post('/', (req, res) => {
+  res.send('Got a POST request');
+});
+```
+
+Respond to a PUT request to the `/user` route:
+
+```js
+app.put('/user', (req, res) => {
+  res.send('Got a PUT request at /user');
+});
+```
+
+Respond to a DELETE request to the `/user` route:
+
+```js
+app.delete('/user', (req, res) => {
+  res.send('Got a DELETE request at /user');
+});
+```
+
+For more details about routing, see the [routing guide](/en/guide/routing).
diff --git a/src/content/docs/zh-tw/5x/starter/examples.mdx b/src/content/docs/zh-tw/5x/starter/examples.mdx
new file mode 100644
index 0000000000..69f410e908
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/examples.mdx
@@ -0,0 +1,49 @@
+---
+title: Express examples
+description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+This page contains list of examples using Express.
+
+- [auth](https://github.com/expressjs/express/tree/master/examples/auth) - Authentication with login and password
+- [content-negotiation](https://github.com/expressjs/express/tree/master/examples/content-negotiation) - HTTP content negotiation
+- [cookie-sessions](https://github.com/expressjs/express/tree/master/examples/cookie-sessions) - Working with cookie-based sessions
+- [cookies](https://github.com/expressjs/express/tree/master/examples/cookies) - Working with cookies
+- [downloads](https://github.com/expressjs/express/tree/master/examples/downloads) - Transferring files to client
+- [ejs](https://github.com/expressjs/express/tree/master/examples/ejs) - Working with Embedded JavaScript templating (ejs)
+- [error-pages](https://github.com/expressjs/express/tree/master/examples/error-pages) - Creating error pages
+- [error](https://github.com/expressjs/express/tree/master/examples/error) - Working with error middleware
+- [hello-world](https://github.com/expressjs/express/tree/master/examples/hello-world) - Simple request handler
+- [markdown](https://github.com/expressjs/express/tree/master/examples/markdown) - Markdown as template engine
+- [multi-router](https://github.com/expressjs/express/tree/master/examples/multi-router) - Working with multiple Express routers
+- [mvc](https://github.com/expressjs/express/tree/master/examples/mvc) - MVC-style controllers
+- [online](https://github.com/expressjs/express/tree/master/examples/online) - Tracking online user activity with `online` and `redis` packages
+- [params](https://github.com/expressjs/express/tree/master/examples/params) - Working with route parameters
+- [resource](https://github.com/expressjs/express/tree/master/examples/resource) - Multiple HTTP operations on the same resource
+- [route-map](https://github.com/expressjs/express/tree/master/examples/route-map) - Organizing routes using a map
+- [route-middleware](https://github.com/expressjs/express/tree/master/examples/route-middleware) - Working with route middleware
+- [route-separation](https://github.com/expressjs/express/tree/master/examples/route-separation) - Organizing routes per each resource
+- [search](https://github.com/expressjs/express/tree/master/examples/search) - Search API
+- [session](https://github.com/expressjs/express/tree/master/examples/session) - User sessions
+- [static-files](https://github.com/expressjs/express/tree/master/examples/static-files) - Serving static files
+- [vhost](https://github.com/expressjs/express/tree/master/examples/vhost) - Working with virtual hosts
+- [view-constructor](https://github.com/expressjs/express/tree/master/examples/view-constructor) - Rendering views dynamically
+- [view-locals](https://github.com/expressjs/express/tree/master/examples/view-locals) - Saving data in request object between middleware calls
+- [web-service](https://github.com/expressjs/express/tree/master/examples/web-service) - Simple API service
+
+## Additional examples
+
+These are some additional examples with more extensive integrations.
+
+<Alert type="warning">
+
+This information refers to third-party sites, products, or modules that are not maintained by the
+Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+Expressjs project team.
+
+</Alert>
+
+- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
+- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
diff --git a/src/content/docs/zh-tw/5x/starter/faq.md b/src/content/docs/zh-tw/5x/starter/faq.md
new file mode 100644
index 0000000000..1adcb7be0e
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/faq.md
@@ -0,0 +1,90 @@
+---
+title: FAQ
+description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
+---
+
+## How should I structure my application?
+
+There is no definitive answer to this question. The answer depends
+on the scale of your application and the team that is involved. To be as
+flexible as possible, Express makes no assumptions in terms of structure.
+
+Routes and other application-specific logic can live in as many files
+as you wish, in any directory structure you prefer. View the following
+examples for inspiration:
+
+- [Route listings](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-L47)
+- [Route map](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
+- [MVC style controllers](https://github.com/expressjs/express/tree/master/examples/mvc)
+
+Also, there are third-party extensions for Express, which simplify some of these patterns:
+
+- [Resourceful routing](https://github.com/expressjs/express-resource)
+
+## How do I define models?
+
+Express has no notion of a database. This concept is
+left up to third-party Node modules, allowing you to
+interface with nearly any database.
+
+See [LoopBack](http://loopback.io) for an Express-based framework that is centered around models.
+
+## How can I authenticate users?
+
+Authentication is another opinionated area that Express does not
+venture into. You may use any authentication scheme you wish.
+For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
+
+## Which template engines does Express support?
+
+Express supports any template engine that conforms with the `(path, locals, callback)` signature.
+To normalize template engine interfaces and caching, see the
+[consolidate.js](https://github.com/visionmedia/consolidate.js)
+project for support. Unlisted template engines might still support the Express signature.
+
+For more information, see [Using template engines with Express](/en/guide/using-template-engines).
+
+## How do I handle 404 responses?
+
+In Express, 404 responses are not the result of an error, so
+the error-handler middleware will not capture them. This behavior is
+because a 404 response simply indicates the absence of additional work to do;
+in other words, Express has executed all middleware functions and routes,
+and found that none of them responded. All you need to
+do is add a middleware function at the very bottom of the stack (below all other functions)
+to handle a 404 response:
+
+```js
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+```
+
+Add routes dynamically at runtime on an instance of `express.Router()`
+so the routes are not superseded by a middleware function.
+
+## How do I setup an error handler?
+
+You define error-handling middleware in the same way as other middleware,
+except with four arguments instead of three; specifically with the signature `(err, req, res, next)`:
+
+```js
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+For more information, see [Error handling](/en/guide/error-handling).
+
+## How do I render plain HTML?
+
+You don't! There's no need to "render" HTML with the `res.render()` function.
+If you have a specific file, use the `res.sendFile()` function.
+If you are serving many assets from a directory, use the `express.static()`
+middleware function.
+
+## What version of Node.js does Express require?
+
+- [Express 4.x](/en/4x/api) requires Node.js 0.10 or higher.
+- [Express 5.x](/en/5x/api) requires Node.js 18 or higher.
diff --git a/src/content/docs/zh-tw/5x/starter/generator.mdx b/src/content/docs/zh-tw/5x/starter/generator.mdx
new file mode 100644
index 0000000000..4f22665f43
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/generator.mdx
@@ -0,0 +1,125 @@
+---
+title: Express application generator
+description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Use the application generator tool, `express-generator`, to quickly create an application skeleton.
+
+You can run the application generator with the `npx` command (available in Node.js 8.2.0).
+
+```bash
+$ npx express-generator
+```
+
+For earlier Node versions, install the application generator as a global npm package and then launch it:
+
+```bash
+$ npm install -g express-generator
+$ express
+```
+
+Display the command options with the `-h` option:
+
+```bash
+$ express -h
+
+  Usage: express [options] [dir]
+
+  Options:
+
+    -h, --help          output usage information
+        --version       output the version number
+    -e, --ejs           add ejs engine support
+        --hbs           add handlebars engine support
+        --pug           add pug engine support
+    -H, --hogan         add hogan.js engine support
+        --no-view       generate without view engine
+    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
+    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
+        --git           add .gitignore
+    -f, --force         force on non-empty directory
+```
+
+For example, the following creates an Express app named _myapp_. The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
+
+```bash
+$ express --view=pug myapp
+
+   create : myapp
+   create : myapp/package.json
+   create : myapp/app.js
+   create : myapp/public
+   create : myapp/public/javascripts
+   create : myapp/public/images
+   create : myapp/routes
+   create : myapp/routes/index.js
+   create : myapp/routes/users.js
+   create : myapp/public/stylesheets
+   create : myapp/public/stylesheets/style.css
+   create : myapp/views
+   create : myapp/views/index.pug
+   create : myapp/views/layout.pug
+   create : myapp/views/error.pug
+   create : myapp/bin
+   create : myapp/bin/www
+```
+
+Then install dependencies:
+
+```bash
+$ cd myapp
+$ npm install
+```
+
+On MacOS or Linux, run the app with this command:
+
+```bash
+$ DEBUG=myapp:* npm start
+```
+
+On Windows Command Prompt, use this command:
+
+```bash
+> set DEBUG=myapp:* & npm start
+```
+
+On Windows PowerShell, use this command:
+
+```bash
+PS> $env:DEBUG='myapp:*'; npm start
+```
+
+Then, load `http://localhost:3000/` in your browser to access the app.
+
+The generated app has the following directory structure:
+
+```bash
+.
+├── app.js
+├── bin
+│   └── www
+├── package.json
+├── public
+│   ├── images
+│   ├── javascripts
+│   └── stylesheets
+│       └── style.css
+├── routes
+│   ├── index.js
+│   └── users.js
+└── views
+    ├── error.pug
+    ├── index.pug
+    └── layout.pug
+
+7 directories, 9 files
+```
+
+<Alert type="info">
+
+The app structure created by the generator is just one of many ways to structure Express apps.
+Feel free to use this structure or modify it to best suit your needs.
+
+</Alert>
diff --git a/src/content/docs/zh-tw/5x/starter/hello-world.mdx b/src/content/docs/zh-tw/5x/starter/hello-world.mdx
new file mode 100644
index 0000000000..63821ba16e
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/hello-world.mdx
@@ -0,0 +1,54 @@
+---
+title: Hello world example
+description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="info">
+
+Embedded below is essentially the simplest Express app you can create. It is a single file app
+&mdash; _not_ what you'd get if you use the [Express generator](/en/starter/generator), which
+creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and
+sub-directories for various purposes.
+
+</Alert>
+
+```js
+const express = require('express');
+const app = express();
+const port = 3000;
+
+app.get('/', (req, res) => {
+  res.send('Hello World!');
+});
+
+app.listen(port, () => {
+  console.log(`Example app listening on port ${port}`);
+});
+```
+
+This app starts a server and listens on port 3000 for connections. The app responds with "Hello World!" for requests
+to the root URL (`/`) or _route_. For every other path, it will respond with a **404 Not Found**.
+
+## Running Locally
+
+First create a directory named `myapp`, change to it and run `npm init`. Then, install `express` as a dependency, as per the [installation guide](/en/starter/installing).
+
+In the `myapp` directory, create a file named `app.js` and copy the code from the example above.
+
+<Alert type="alert">
+
+The `req` (request) and `res` (response) are the exact same objects that Node provides, so you can
+invoke `req.pipe()`, `req.on('data', callback)`, and anything else you would do without Express
+involved.
+
+</Alert>
+
+Run the app with the following command:
+
+```bash
+$ node app.js
+```
+
+Then, load `http://localhost:3000/` in a browser to see the output.
diff --git a/src/content/docs/zh-tw/5x/starter/installing.mdx b/src/content/docs/zh-tw/5x/starter/installing.mdx
new file mode 100644
index 0000000000..f6dc8220d4
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/installing.mdx
@@ -0,0 +1,41 @@
+---
+title: Installing
+description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Before you begin, make sure you have [Node.js](https://nodejs.org/) 18 or higher installed. Then, create a directory for your application and navigate into it.
+
+```bash
+mkdir myapp
+cd myapp
+```
+
+Use the `npm init` command to create a `package.json` file for your application.
+For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
+
+```bash
+npm init
+```
+
+This command prompts you for a number of things, such as the name and version of your application.
+For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
+
+```
+entry point: (index.js)
+```
+
+Enter `app.js`, or whatever you want the name of the main file to be. If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
+
+Now, install Express in the `myapp` directory and save it in the dependencies list. For example:
+
+```bash
+npm install express
+```
+
+To install Express temporarily and not add it to the dependencies list:
+
+```bash
+npm install express --no-save
+```
diff --git a/src/content/docs/zh-tw/5x/starter/static-files.mdx b/src/content/docs/zh-tw/5x/starter/static-files.mdx
new file mode 100644
index 0000000000..98855e0d05
--- /dev/null
+++ b/src/content/docs/zh-tw/5x/starter/static-files.mdx
@@ -0,0 +1,82 @@
+---
+title: Serving static files in Express
+description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
+
+The function signature is:
+
+```js
+express.static(root, [options]);
+```
+
+The `root` argument specifies the root directory from which to serve static assets.
+For more information on the `options` argument, see [express.static](/en/5x/api#express.static).
+
+For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
+
+```js
+app.use(express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory:
+
+```text
+http://localhost:3000/images/kitten.jpg
+http://localhost:3000/css/style.css
+http://localhost:3000/js/app.js
+http://localhost:3000/images/bg.png
+http://localhost:3000/hello.html
+```
+
+<Alert type="info">
+
+Express looks up the files relative to the static directory, so the name of the static directory
+is not part of the URL.
+
+</Alert>
+
+To use multiple static assets directories, call the `express.static` middleware function multiple times:
+
+```js
+app.use(express.static('public'));
+app.use(express.static('files'));
+```
+
+Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
+
+<Alert type="info">
+
+For best results, use a reverse
+proxy cache to improve performance of
+serving static assets.
+
+</Alert>
+
+To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/en/5x/api#app.use) for the static directory, as shown below:
+
+```js
+app.use('/static', express.static('public'));
+```
+
+Now, you can load the files that are in the `public` directory from the `/static` path prefix.
+
+```text
+http://localhost:3000/static/images/kitten.jpg
+http://localhost:3000/static/css/style.css
+http://localhost:3000/static/js/app.js
+http://localhost:3000/static/images/bg.png
+http://localhost:3000/static/hello.html
+```
+
+However, the path that you provide to the `express.static` function is relative to the directory from where you launch your `node` process. If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
+
+```js
+const path = require('path');
+app.use('/static', express.static(path.join(__dirname, 'public')));
+```
+
+For more details about the `serve-static` function and its options, see [serve-static](/en/resources/middleware/serve-static).
diff --git a/src/content/pages/de/advanced/best-practice-performance.md b/src/content/pages/de/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..615d160130
--- /dev/null
+++ b/src/content/pages/de/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Best Practices: Leistung und Zuverlässigkeit'
+description: Entdecken Sie Performance und Zuverlässigkeits-Best Practices für Express-Apps in der Produktion, die Code-Optimierungen und Umgebungs-Setups für optimale Performance abdecken.
+---
+
+Dieser Artikel befasst sich mit der Leistungsfähigkeit und der Zuverlässigkeit der besten Verfahren für Express-Anwendungen, die in der Produktion eingesetzt werden.
+
+Dieses Thema fällt eindeutig in die "Devops"-Welt, die sowohl traditionelle Entwicklung als auch Operationen umfasst. Dementsprechend sind die Informationen in zwei Teile aufgeteilt:
+
+- Dinge in Ihrem Code zu tun (dev part):
+  - [Benutze gzip Kompression](#use-gzip-compression)
+  - [Keine synchronen Funktionen](#dont-use-synchronous-functions)
+  - [Logging korrekt](#do-logging-correctly)
+  - [Ausnahmen richtig behandeln](#handle-exceptions-properly)
+- Dinge zu tun in Ihrer Umgebung / in Ihrer Umgebung (der Ops-Teil):
+  - [Setze NODE_ENV auf "Produktion"](#set-node_env-to-production)
+  - [Stelle sicher, dass deine App automatisch neu startet](#ensure-your-app-automatically-restarts)
+  - [Starte deine App in einem Cluster](#run-your-app-in-a-cluster)
+  - [Cache-Anfrageergebnisse](#cache-request-results)
+  - [Lastausgleich verwenden](#use-a-load-balancer)
+  - [Reverse Proxy](#use-a-reverse-proxy) verwenden
+
+## Dinge in deinem Code zu tun
+
+Hier sind einige Dinge, die Sie in Ihrem Code tun können, um die Leistung Ihrer Anwendung zu verbessern:
+
+- [Benutze gzip Kompression](#use-gzip-compression)
+- [Keine synchronen Funktionen](#dont-use-synchronous-functions)
+- [Logging korrekt](#do-logging-correctly)
+- [Ausnahmen richtig behandeln](#handle-exceptions-properly)
+
+### Gzip Komprimierung verwenden
+
+Gzip-Komprimierung kann die Reaktionskörper erheblich verringern und damit die Geschwindigkeit einer Web-App erhöhen. Benutzen Sie die [compression](https://www.npmjs.com/package/compression) Middleware für gzip Komprimierung in Ihrer Express-App. Zum Beispiel:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+Für eine stark frequentierte Website in der Produktion, der beste Weg zur Komprimierung ist die Implementierung auf umgekehrter Proxyebene (siehe [Reverse Proxy](#use-a-reverse-proxy)) . In diesem Fall brauchen Sie keine Komprimierungsmittelware. Details zum Aktivieren der gzip-Komprimierung in Nginx finden Sie unter [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) in der Nginx-Dokumentation.
+
+### Keine synchronen Funktionen verwenden
+
+Synchronische Funktionen und Methoden binden den Ausführungsprozess bis sie zurückkehren. Ein einzelner Aufruf einer synchronen Funktion kann in ein paar Mikrosekunden oder Millisekunden zurückgegeben werden auf Websites mit hohem Traffic jedoch tragen diese Anrufe dazu bei, die Performance der App zu reduzieren. Vermeiden Sie ihren Einsatz in der Produktion.
+
+Obwohl Node und viele Module synchrone und asynchrone Versionen ihrer Funktionen liefern, verwenden Sie immer die asynchrone Version in der Produktion. Die einzige Zeit, in der eine synchrone Funktion gerechtfertigt werden kann, ist beim ersten Start.
+
+Du kannst das `--trace-sync-io` Kommandozeilen-Flag verwenden, um eine Warnung und einen Stack-Trace zu drucken, wann immer deine Anwendung eine synchrone API verwendet. Natürlich möchten Sie dies nicht in der Produktion verwenden, sondern vielmehr sicherstellen, dass Ihr Code produktionsbereit ist. Weitere Informationen finden Sie in der [Knoten Kommandozeilenoptionen Dokumentation](https://nodejs.org/api/cli#cli_trace_sync_io) .
+
+### Logging korrekt
+
+Im Allgemeinen gibt es zwei Gründe für die Protokollierung aus Ihrer App: Für das Debuggen und für die Protokollierung von App-Aktivitäten (im Wesentlichen alles andere). Die Verwendung von `console.log()` oder `console.error()` zum Drucken von Logmeldungen an das Terminal ist gängige Praxis in der Entwicklung. Aber [diese Funktionen sind synchronisiert](https://nodejs.org/api/console#console), wenn das Ziel ein Terminal oder eine Datei ist so dass sie nicht für die Produktion geeignet sind, es sei denn, Sie rollen die Ausgabe zu einem anderen Programm.
+
+#### Zum Debuggen
+
+Wenn du zum Debuggen loggst, benutze anstelle von `console.log()` ein spezielles Debugging-Modul wie [debug](https://www.npmjs.com/package/debug). Dieses Modul ermöglicht es Ihnen, die DEBUG Umgebungsvariable zu verwenden, um zu kontrollieren, welche Debug-Meldungen an `console.error()` gesendet werden, falls vorhanden. Um deine App rein asynchron zu halten, solltest du trotzdem `console.error()` zu einem anderen Programm weiterleiten. Aber dann bist du nicht wirklich in der Produktion zu debuggen, oder?
+
+#### Für App-Aktivitäten
+
+Wenn Sie App-Aktivitäten protokollieren (zum Beispiel Traffic oder API-Aufrufe), anstatt „Konsole“. og()\`, verwende eine Logging-Bibliothek wie [Pino](https://www.npmjs.com/package/pino), die schnellste und effizienteste verfügbare Option.
+
+### Ausnahmen richtig handhaben
+
+Knoten-Apps stürzen ab, wenn sie auf eine nicht gefangene Ausnahme stoßen. Wenn Sie Ausnahmen nicht bearbeiten und entsprechende Maßnahmen ergreifen, wird Ihre Express-App zum Absturz bringen und offline gehen. Wenn du dem Rat folgst [Stelle sicher, dass deine App automatisch neu startet](#ensure-your-app-automatically-restarts) unten, dann wird deine App von einem Absturz erholt. Glücklicherweise haben Express-Apps in der Regel eine kurze Startzeit. Nichtsdestotrotz wollen Sie einen Absturz vermeiden, und dazu müssen Sie die Ausnahmen ordentlich behandeln.
+
+Um sicherzustellen, dass Sie mit allen Ausnahmen umgehen, verwenden Sie folgende Techniken:
+
+- [Versuchscatch](#use-try-catch)
+- [Versprechungen verwenden](#use-promises)
+
+Bevor Sie in diese Themen eintauchen, sollten Sie ein grundlegendes Verständnis von Node/Express-Fehlerbehandlung haben: Verwendung von Fehler-First Callbacks und Verbreitung von Fehlern in Middleware. Knoten verwendet eine "error-first callback"-Konvention um Fehler aus asynchronen Funktionen zurückzugeben, wobei der erste Parameter der Callback-Funktion das Fehlerobjekt ist, gefolgt von Ergebnisdaten in folgenden Parametern. Um keinen Fehler anzugeben, übergeben Sie Null als ersten Parameter. Die Callback-Funktion muss entsprechend der ersten Callback-Konvention folgen, um den Fehler sinnvoll zu bearbeiten. Und in Express ist es am besten, die next() Funktion zu nutzen, um Fehler über die Middleware-Kette zu verbreiten.
+
+Für mehr über die Grundlagen der Fehlerbehandlung, siehe:
+
+- [Fehler beim Umgang mit Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Versuchsfang verwenden
+
+Try-catch ist eine JavaScript-Sprachkonstruktion, die Sie verwenden können, um Ausnahmen im synchronen Code zu fangen. Verwenden Sie zum Beispiel den versuchen Catch, um JSON-Parsing-Fehler wie unten gezeigt zu behandeln.
+
+Hier ist ein Beispiel für die Verwendung von "try-catch", um eine mögliche Prozessabsturzausnahme zu bewältigen.
+Diese Middleware-Funktion akzeptiert einen Abfragefeldparameter namens "params", das ein JSON-Objekt ist.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+Der Versuch funktioniert jedoch nur für synchrone Code. Da die Knotenplattform primär asynchron ist (insbesondere in einer Produktionsumgebung), wird der Versuch nicht viele Ausnahmen fangen.
+
+#### Versprechen verwenden
+
+Wenn ein Fehler in einer `async` Funktion ausgelöst wird oder ein abgelehntes Versprechen in einer `async` Funktion erwartet wird, diese Fehler werden an den Fehlerhandler übergeben, als ob `next(err)` aufgerufen würde
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Außerdem können Sie asynchrone Funktionen für Ihre Middleware verwenden und der Router verarbeitet Fehler, wenn das Versprechen fehlschlägt, zum Beispiel:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+Best Practices ist es, Fehler so nah wie möglich an der Website zu behandeln. So während dies jetzt im Router behandelt wird, ist es am besten, den Fehler in der Middleware zu fangen und ihn zu bearbeiten, ohne sich auf eine separate Middleware zu verlassen.
+
+#### Was nicht zu tun
+
+Eine Sache, die du _nicht_ tun solltest ist, auf das `uncaptException` Event zu hören emittiert, wenn eine Ausnahme den ganzen Weg zurück zur Ereignis-Schleife weht. Das Hinzufügen eines Ereignis-Listeners für `uncaughtException` ändert das Standardverhalten des Prozesses, der auf eine Ausnahme stößt; wird der Prozess trotz der Ausnahme weiterhin laufen. Dies könnte nach einer guten Möglichkeit klingen, um zu verhindern, dass Ihre App abstürzt, aber die Anwendung nach einer nicht gefangenen Ausnahme weiterhin zu laufen ist eine gefährliche Praxis und wird nicht empfohlen, weil der Zustand des Prozesses unzuverlässig und unberechenbar wird.
+
+Zusätzlich wird die Verwendung von `uncaughtException` offiziell als [crude]anerkannt (https://nodejs.org/api/process#process_event_uncaughtexception). Also ist das Hören auf `uncaughtException` eine schlechte Idee. Aus diesem Grund empfehlen wir Dinge wie mehrere Prozesse und Supervisoren: Absturz und Neustart sind oft der zuverlässigste Weg, um einen Fehler zu beheben.
+
+Wir empfehlen auch nicht [domains]zu verwenden (https://nodejs.org/api/domain). Es löst das Problem im Allgemeinen nicht und ist ein veraltetes Modul.
+
+## Dinge zu tun in Ihrer Umgebung / Einrichtung
+
+Hier sind einige Dinge, die Sie in Ihrer Systemumgebung tun können, um die Leistung Ihrer App zu verbessern:
+
+- [Setze NODE_ENV auf "Produktion"](#set-node_env-to-production)
+- [Stelle sicher, dass deine App automatisch neu startet](#ensure-your-app-automatically-restarts)
+- [Starte deine App in einem Cluster](#run-your-app-in-a-cluster)
+- [Cache-Anfrageergebnisse](#cache-request-results)
+- [Lastausgleich verwenden](#use-a-load-balancer)
+- [Reverse Proxy](#use-a-reverse-proxy) verwenden
+
+### Knoten_ENV auf "Produktion" setzen
+
+Die NODE_ENV Umgebungsvariable spezifiziert die Umgebung, in der eine Anwendung ausgeführt wird (normalerweise Entwicklung oder Produktion). Eines der einfachsten Dinge, die Sie tun können, um die Leistung zu verbessern, ist, NODE_ENV auf `production` zu setzen.
+
+Setze NODE_ENV auf "production" makes Express:
+
+- Cache-Ansichtsvorlagen.
+- Cache-CSS-Dateien, die aus CSS-Erweiterungen generiert wurden.
+- Weniger ausführliche Fehlermeldungen generieren.
+
+[Tests deuten an](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/), dass dies die Leistung der App um einen Faktor von drei verbessern kann!
+
+Wenn Sie umweltspezifischen Code schreiben müssen, können Sie den Wert von NODE_ENV mit `process.env.NODE_ENV` überprüfen. Beachten Sie, dass die Überprüfung des Wertes einer Umgebungsvariable eine Leistungsstrafe verursacht und daher sparsam durchgeführt werden sollte.
+
+In der Entwicklung setzst du in der Regel Umgebungsvariablen in deiner interaktiven Shell ein, indem du `export` oder deine `.bash_profile` Datei verwendest. Aber im Allgemeinen sollten Sie das nicht auf einem Produktionsserver tun; stattdessen sollten Sie das Init-System Ihres Betriebssystems (System) verwenden. Der nächste Abschnitt enthält weitere Details zur Verwendung Ihres Init-Systems im Allgemeinen aber das Setzen von `NODE_ENV` ist so wichtig für die Leistung (und einfach zu tun), dass es hier hervorgehoben wird.
+
+Mit dem System verwenden Sie die `Environment` Direktive in Ihrer Einheitendatei. Zum Beispiel:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+Weitere Informationen finden Sie unter [Umgebungsvariablen in systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Stellen Sie sicher, dass Ihre App automatisch neu gestartet wird
+
+In der Produktion wollen Sie nicht, dass Ihre Bewerbung offline ist. Dies bedeutet, dass Sie sicherstellen müssen, dass es sowohl neu gestartet wird, wenn die App abstürzt als auch wenn der Server selbst abstürzt. Obwohl Sie hoffen, dass keines dieser Ereignisse eintritt, müssen Sie realistischerweise beide Eventualitäten berücksichtigen von:
+
+- Verwendung eines Prozess-Managers, um die App (und den Knoten) neu zu starten, wenn sie abstürzt.
+- Verwendung des von Ihrem Betriebssystem zur Verfügung gestellten Init-Systems, um den Prozessmanager beim Absturz des Betriebssystems neu zu starten. Es ist auch möglich, das Init-System ohne Prozessmanager zu verwenden.
+
+Knotenapplikationen stürzen ab, wenn sie eine nicht gefangene Ausnahme erleben. Das Wichtigste, was Sie tun müssen, ist, sicherzustellen, dass Ihre App gut getestet ist und alle Ausnahmen handhabt (siehe [Ausnahmen ordnungsgemäß behandeln](#handle-exceptions-properly) für Details). Aber als Fail-Safe setzen Sie einen Mechanismus, um sicherzustellen, dass wenn und wenn Ihre App abstürzt, automatisch neu gestartet wird.
+
+#### Prozessmanager verwenden
+
+In der Entwicklung hast du deine App einfach von der Kommandozeile aus mit `node server.js` oder etwas Ähnlichem gestartet. Aber dies in der Produktion zu tun, ist ein Rezept für eine Katastrophe. Wenn die App abstürzt, wird sie offline sein, bis Sie sie neu starten. Um sicherzustellen, dass Ihre App neu gestartet wird, wenn sie abstürzt, verwenden Sie einen Prozessmanager. Ein Prozessmanager ist ein "Container" für Anwendungen, die den Einsatz erleichtern, eine hohe Verfügbarkeit bieten und Ihnen die Verwaltung der Anwendung zur Laufzeit ermöglichen.
+
+Zusätzlich zum Neustart Ihrer App bei einem Absturz kann ein Prozessmanager Sie aktivieren:
+
+- Gewinnen Sie Einblicke in Laufzeitleistung und Ressourcenverbrauch.
+- Ändern Sie die Einstellungen dynamisch, um die Leistung zu verbessern.
+- Steuerung Clustering (pm2).
+
+Historisch war es beliebt, einen Node.js Prozessmanager wie [PM2](https://github.com/Unitech/pm2) zu verwenden. Lesen Sie deren Dokumentation, wenn Sie dies tun möchten. Wir empfehlen jedoch, Ihr Init-System für das Prozessmanagement zu verwenden.
+
+#### Init-System verwenden
+
+Die nächste Ebene der Zuverlässigkeit besteht darin, sicherzustellen, dass Ihre App beim Neustart des Servers neu gestartet wird. Systeme können aus verschiedenen Gründen immer noch heruntergehen. Um sicherzustellen, dass Ihre App neu gestartet wird, wenn der Server abstürzt, verwenden Sie das Init-System, das in Ihr Betriebssystem integriert wurde. Das heute verwendete Hauptinitsystem ist [systemd](https://wiki.debian.org/systemd).
+
+Es gibt zwei Möglichkeiten, Init-Systeme mit Ihrer Express-App zu verwenden:
+
+- Führen Sie Ihre App in einem Prozessmanager aus und installieren Sie den Prozessmanager als Service mit dem Init-System. Der Prozessmanager startet Ihre App neu, wenn die App abstürzt, und das Init-System startet den Prozessmanager beim Neustart des Betriebssystems neu. Dies ist der empfohlene Ansatz.
+- Führen Sie Ihre App (und Ihren Knoten) direkt mit dem Init-System aus. Das ist etwas einfacher, aber Sie haben nicht die zusätzlichen Vorteile eines Prozessmanagers.
+
+##### Systemd
+
+Systemd ist ein Linux System und Service Manager. Die meisten großen Linux-Distributionen haben System als Standard-Init-System übernommen.
+
+Eine Systemd-Service-Konfigurationsdatei heißt _unit file_, mit einem Dateinamen endet in `.service`. Hier ist eine Beispiel-Einheitsdatei, um eine Knoten-App direkt zu verwalten. Ersetzen Sie die Werte in `<angle brackets>` für Ihr System und App:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Weitere Informationen zum System finden Sie unter [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Starte deine App in einem Cluster
+
+In einem Multi-Core-System können Sie die Leistung einer Knoten-App um ein Vielfaches erhöhen, indem Sie einen Cluster von Prozessen starten. Ein Cluster führt mehrere Instanzen der App aus, idealerweise eine Instanz auf jedem CPU-Core, wodurch die Last und Aufgaben auf die Instanzen verteilt werden.
+
+![Balance zwischen Anwendungsinstanzen mit der Cluster-API](/images/clustering.png)
+
+WICHTIG: Da die App-Instanzen als separate Prozesse laufen, teilen sie nicht den gleichen Speicherplatz. Das heißt, Objekte sind lokal für jede Instanz der App. Daher können Sie den Status im Anwendungscode nicht beibehalten. Du kannst jedoch einen Speicherdatenspeicher wie [Redis](http://redis.io/) verwenden, um Sitzungsdaten und -status zu speichern. Dieser Vorbehalt bezieht sich im Wesentlichen auf alle Formen der horizontalen Skalierung, sei es beim Clustering mit mehreren Prozessen oder mehreren physischen Servern.
+
+In geclusterten Apps können Worker-Prozesse individuell abstürzen, ohne den Rest der Prozesse zu beeinträchtigen. Abgesehen von den Leistungsvorteilen ist die Fehlerisolierung ein weiterer Grund, einen Cluster von App-Prozessen auszuführen. Immer wenn ein Worker-Prozess abstürzt, vergewissern Sie sich, das Ereignis zu protokollieren und einen neuen Prozess mit cluster.fork() zu erzeugen.
+
+#### Cluster-Modul des Knotens
+
+Clustering wird mit Knotens [Cluster-Modul](https://nodejs.org/api/cluster) ermöglicht. Dies ermöglicht es einem Master-Prozess, Worker-Prozesse zu generieren und eingehende Verbindungen unter den Arbeitern zu verteilen.
+
+#### PM2 verwenden
+
+Wenn Sie Ihre Anwendung mit PM2 bereitstellen, können Sie die Vorteile des Clustering _without out_ Ändern Ihres Anwendungscodes nutzen. Du solltest sicherstellen, dass deine [Anwendung zustandslos ist](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) zuerst , was bedeutet, dass keine lokalen Daten im Prozess gespeichert werden (wie Sessions, Websocket-Verbindungen und dergleichen).
+
+Wenn du eine Anwendung mit PM2 ausführst, kannst du den **Cluster-Modus** aktivieren, um ihn in einem Cluster mit einer Anzahl von Instanzen deiner Wahl auszuführen zum Beispiel die übereinstimmende Anzahl der verfügbaren CPUs. Du kannst die Anzahl der Prozesse im Cluster manuell mit dem Kommandozeilenwerkzeug `pm2` ändern, ohne die App zu stoppen.
+
+Um den Cluster-Modus zu aktivieren, starten Sie Ihre Anwendung so:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+Dies kann auch innerhalb einer PM2-Prozessdatei konfiguriert werden (`ecosystem.config. s` oder ähnlich) indem `exec_mode` auf `cluster` und `instances` auf die Anzahl der zu startenden Arbeiter gesetzt wird.
+
+Nach dem Ausführen kann die Anwendung so skaliert werden:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+Weitere Informationen zum Clustering mit PM2 finden Sie unter [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in der PM2-Dokumentation.
+
+### Cache-Abfrageergebnisse
+
+Eine weitere Strategie zur Verbesserung der Leistung in der Produktion ist das Cache-Ergebnis von Anfragen so dass Ihre App die Operation nicht wiederholt, um dieselbe Anfrage wiederholt zu bedienen.
+
+Benutze einen Caching-Server wie [Varnish](https://www.varnish-cache.org/) oder [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (siehe auch [Nginx Caching](https://serversforhackers.com/nginx-caching/)) um die Geschwindigkeit und Leistung deiner App deutlich zu verbessern.
+
+### Lastausgleich verwenden
+
+Egal wie optimiert eine App ist, eine einzelne Instanz kann nur eine begrenzte Menge an Last und Traffic verwalten. Eine Möglichkeit, eine App zu skalieren, besteht darin, mehrere Instanzen davon auszuführen und den Traffic über einen Lastausgleicher zu verteilen. Das Einrichten eines Lastausgleichs kann die Leistung und Geschwindigkeit Ihrer App verbessern und es ermöglichen, mehr zu skalieren, als mit einer einzigen Instanz möglich ist.
+
+Ein Loadbalancer ist in der Regel ein Reverse-Proxy, der den Datenverkehr zu und von mehreren Anwendungsinstanzen und Servern regelt. Mit [Nginx](https://nginx.org/en/docs/http/load_balancing) oder [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts) können Sie ganz einfach einen Lastausgleich für Ihre App einrichten.
+
+Bei Loadbalancing müssen Sie eventuell sicherstellen, dass Anforderungen, die mit einer bestimmten Session-ID in Verbindung stehen, mit dem Prozess verbunden sind, der sie verursacht hat. Dies ist _session_, oder _sticky sessions_, bekannt und kann durch den oben genannten Vorschlag angesprochen werden, um einen Datenspeicher wie Redis für Sitzungsdaten (je nach Anwendung) zu verwenden. Für eine Diskussion siehe [Mehrere Knoten verwenden](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Reverse-Proxy verwenden
+
+Ein Reverse Proxy sitzt vor einer Web-App und führt unterstützende Operationen auf den Anfragen aus, abgesehen von der Weiterleitung von Anfragen an die App. Es kann Fehlerseiten, Komprimierung, Caching, Servieren von Dateien und laden Balancing unter anderem.
+
+Die Übergabe von Aufgaben, die keine Kenntnisse des Anwendungszustands an einen Reverse Proxy erfordern, gibt Express frei, spezielle Anwendungsaufgaben durchzuführen. Aus diesem Grund wird empfohlen, Express in der Produktion hinter einem umgekehrten Proxy wie [Nginx](https://www.nginx.org/) oder [HAProxy](https://www.haproxy.org/) auszuführen.
diff --git a/src/content/pages/de/advanced/best-practice-security.mdx b/src/content/pages/de/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..08ecbd91ab
--- /dev/null
+++ b/src/content/pages/de/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Beste Produktionspraktiken: Sicherheit'
+description: Entdecken Sie wichtige Sicherheits-Best Practices für Express-Apps in der Produktion, einschließlich der Verwendung von TLS, Eingabe-Validierung, sichere Cookies und der Vermeidung von Schwachstellen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Der Begriff _"production"_ bezieht sich auf die Stufe im Software-Lebenszyklus, wenn eine Anwendung oder API allgemein für Endbenutzer oder Verbraucher verfügbar ist. Im Gegensatz dazu, in der _"development"_ Bühne, Sie immer noch aktiv schreiben und Test-Code, und die Anwendung ist nicht offen für externen Zugriff. Die entsprechenden Systemumgebungen werden als _production_ bzw. _development_ Umgebungen bezeichnet.
+
+Entwicklungs- und Produktionsumgebungen sind in der Regel unterschiedlich aufgebaut und haben sehr unterschiedliche Anforderungen. Was in der Entwicklung gut ist, kann in der Produktion nicht akzeptabel sein. In einer Entwicklungsumgebung könnte es sein, dass Sie ausführliche Protokollierung von Fehlern zum Debuggen wünschen während das gleiche Verhalten kann zu einem Sicherheitsbedenken in einer Produktionsumgebung werden. Und in der Entwicklung müssen Sie sich keine Sorgen um Skalierbarkeit, Zuverlässigkeit und Leistung machen, während diese Bedenken in der Produktion entscheidend werden.
+
+<Alert type="info">
+
+Wenn Sie glauben, dass Sie eine Sicherheitslücke in Express entdeckt haben, lesen Sie bitte Sicherheits-
+Richtlinien und Prozeduren.
+
+</Alert>
+
+Best Practices für Express-Anwendungen in der Produktion beinhalten:
+
+- [Beste Produktionspraktiken: Sicherheit](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Veraltete oder verwundbare Versionen von Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Benutze TLS](#use-tls)
+  - [Nicht auf Benutzereingabe vertrauen](#do-not-trust-user-input)
+    - [Verhindere offene Weiterleitungen](#prevent-open-redirects)
+  - [Helm verwenden](#use-helmet)
+  - [Fingerabdruck reduzieren](#reduce-fingerprinting)
+  - [Cookies sicher verwenden](#use-cookies-securely)
+    - [Benutze nicht den Standard-Sitzungs-Cookie Name](#dont-use-the-default-session-cookie-name)
+    - [Cookie Sicherheitseinstellungen setzen](#set-cookie-security-options)
+  - [Verhindere Brute-Force-Angriffe gegen Autorisierung](#prevent-brute-force-attacks-against-authorization)
+  - [Vergewissern Sie sich, dass Ihre Abhängigkeiten sicher sind](#ensure-your-dependencies-are-secure)
+    - [Vermeide andere bekannte Schwachstellen aus](#avoid-other-known-vulnerabilities)
+  - [Zusätzliche Überlegungen](#additional-considerations)
+
+## Veraltete oder verwundbare Versionen von Express nicht verwenden
+
+Express 2.x und 3.x werden nicht mehr gewartet. Sicherheits- und Leistungsprobleme in diesen Versionen werden nicht behoben. Verwenden Sie sie nicht! Wenn Sie nicht auf Version 4 umgezogen sind, folgen Sie der [Migrationsanleitung](/en/guide/migrating-4) oder überlegen Sie [Handelsunterstützungsoptionen](/en/support#commercial-support-options).
+
+Vergewissern Sie sich auch, dass Sie keine der verwundbaren Express-Versionen auf der [Seite für Sicherheitsupdates ] verwenden (/en/advanced/security-updates). Wenn Sie dies tun, aktualisieren Sie auf eine der stabilen Releases, vorzugsweise die neuste.
+
+## TLS verwenden
+
+Wenn Ihre App sensible Daten behandelt oder übermittelt, verwenden Sie [Transport-Layer-Sicherheit](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) um die Verbindung und die Daten zu sichern. Diese Technologie verschlüsselt Daten, bevor sie vom Client an den Server gesendet werden, und verhindert so einige häufige (und einfache) Hacks. Obwohl Ajax und POST Anfragen möglicherweise nicht sichtbar sind und im Browser "versteckt" zu sein scheinen, ihr Netzwerkverkehr ist anfällig für [Paket-Sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) und [Man-in-the-middle-Angriffe](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+Sie können mit der Verschlüsselung Secure Socket Layer (SSL) vertraut sein. [TLS ist einfach die nächste Weiterentwicklung von SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). Mit anderen Worten: Wenn Sie SSL zuvor verwendet haben, sollten Sie ein Upgrade auf TLS in Betracht ziehen. Im Allgemeinen empfehlen wir Nginx mit TLS umzugehen. Für eine gute Referenz zum Konfigurieren von TLS auf Nginx (und anderen Servern) siehe [Empfohlene Server-Konfigurationen (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Ein praktisches Werkzeug, um ein kostenloses TLS-Zertifikat zu erhalten, ist [Let's Encrypt](https://letsencrypt.org/about/), ein kostenloses und automatisiertes TLS-Zertifikat und offene Zertifizierungsstelle (CA) zur Verfügung gestellt von der [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## Benutzereingabe nicht vertrauen
+
+Eine der wichtigsten Sicherheitsanforderungen für Webanwendungen ist die korrekte Validierung und Handhabung von Benutzereingaben. Das kommt in vielen Formen, und wir werden hier nicht alle abdecken.
+Letztlich liegt die Verantwortung für die Validierung und korrekte Handhabung der Benutzereingaben, die Ihre Anwendung akzeptiert, bei Ihnen.
+
+### Offene Weiterleitungen verhindern
+
+Ein Beispiel für potenziell gefährliche Benutzereingaben ist eine _open redirect_, wo eine Anwendung akzeptiert eine URL als Benutzereingabe (oft in der URL-Abfrage, zum Beispiel "? rl=https://Beispiel. om`) und verwendet `res.redirect`um den`location\` Header und
+einen 3xx Status zu setzen.
+
+Eine Anwendung muss überprüfen, dass sie eine Umleitung auf die eingehende URL unterstützt, um zu vermeiden, dass Benutzer an böswillige Links wie Phishing-Websites geschickt werden unter anderem Risiken.
+
+Hier ist ein Beispiel für die Überprüfung von URLs, bevor `res.redirect` oder `res.location`:
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.uery.url).host !== 'example.com') {
+      return res.status(400).nd(`Nicht unterstützte Weiterleitung zum Host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.tatus(400).end(`Ungültige Url: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Helm verwenden
+
+[Helmet][helmet] kann helfen, Ihre App vor einigen bekannten Web-Verwundbarkeiten zu schützen, indem Sie HTTP-Header entsprechend setzen.
+
+Helmet ist eine Middleware-Funktion, die sicherheitsrelevante HTTP-Antwort-Header festlegt. Helm setzt standardmäßig folgende Kopfzeilen:
+
+- `Content-Security-Policy`: Eine mächtige Zulassungsliste dessen, was auf deiner Seite passieren kann, die viele Angriffe mildert
+- `Cross-Origin-Opener-Policy`: Hilft dabei, Ihre Seite zu isolieren
+- `Cross-Origin-Resource-Policy`: Blockiert andere vom Laden deiner Ressourcen Cross-origin
+- `Origin-Agent-Cluster`: Ändert die Prozess-Isolation in originalbasierte
+- `Referrer-Policy`: Steuert den [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) Header
+- "Strict-Transport-Sicherheit": Bedeutet Browser, HTTPS vorzuziehen
+- `X-Content-Type-Optionen`: Vermeiden [MIME Sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Steuert DNS-Vorabholung
+- `X-Download-Optionen`: Erzwingt Downloads zu speichern (nur im Internet Explorer)
+- `X-Frame-Optionen`: Legacy-Header, der [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) Angriffe mildert
+- `X-Permitted-Cross-Domain-Policies`: Kontrolliert Domainübergreifendes Verhalten für Adobe-Produkte wie Acrobat
+- `X-Powered-By`: Info über den Webserver. Entfernt, weil es bei einfachen Angriffen verwendet werden kann
+- `X-XSS-Protection`: Legacy-Header, der versucht, [XSS-Angriffs](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), zu mildern, aber die Dinge verschlimmert, also deaktiviert Helm ihn
+
+Jeder Header kann konfiguriert oder deaktiviert werden. Um mehr darüber zu erfahren, gehen Sie bitte auf [seine Dokumentations-Website][helmet].
+
+Helm wie jedes andere Modul installieren:
+
+```bash
+$ npm install helmet
+```
+
+Dann verwenden Sie es in Ihrem Code:
+
+```js
+// ...
+
+const helmet = require('helm');
+app.use(helmet());
+
+// ...
+```
+
+## Fingerabdruck verringern
+
+Es kann helfen, eine zusätzliche Sicherheitsschicht zu bieten, um die Fähigkeit von Angreifern zu verringern,
+die Software zu ermitteln, die ein Server benutzt bekannt als "Fingerabdruck". Obwohl es selbst kein Sicherheitsproblem ist, verbessert
+die Reduzierung der Fingerabdrücke einer Anwendung seine allgemeine Sicherheitsauffassung.
+Server-Software kann durch Quirks Fingerabdrücke in der Art und Weise abgerufen werden, wie sie auf bestimmte Anfragen reagiert, zum Beispiel in
+den HTTP-Antwort-Headern.
+
+Standardmäßig sendet Express den `X-Powered-By` Antwort-Header, den Sie
+deaktivieren können mit der `app.disable()` Methode:
+
+```js
+app.disable('x-Powered by ');
+```
+
+<Alert type="info">
+
+Das Deaktivieren des `X-Powered-By-Header` hindert einen anspruchsvollen Angreifer nicht daran,
+zu ermitteln, dass eine App Express ausführt. It may discourage a casual exploit, but there are other ways to
+determine an app is running Express.
+
+</Alert>
+
+Express sendet auch eigene formatierte "404 Not Found"-Nachrichten und Formatierungsfehler
+Antwortmitteilungen. Diese können von
+geändert werden [füge deinen eigenen nicht gefundenen Handler hinzu](/en/starter/faq#how-do-i-handle-404-responses)
+und
+[deinen eigenen Fehler zu schreiben](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// letzten app.use Aufrufe direkt vor app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404). end("Tut uns leid, das kann nicht gefunden werden!");
+});
+
+// Custom Error handler
+app. se(err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Etwas kaputt!');
+});
+```
+
+## Cookies sicher verwenden
+
+Um sicherzustellen, dass Cookies nicht Ihre App zum Ausnutzen öffnen, verwenden Sie nicht den standardmäßigen Session-Cookie-Namen und setzen Sie die Cookie-Sicherheitsoptionen entsprechend ein.
+
+Es gibt zwei zentrale Middleware-Cookie-Sitzungsmodule:
+
+- [express-session](https://www.npmjs.com/package/express-session), die `express.session` Middleware in Express 3.x ersetzt.
+- [cookie-session](https://www.npmjs.com/package/cookie-session), die die in Express 3.x integrierte Middleware `express.cookieSession` ersetzt.
+
+Der Hauptunterschied zwischen diesen beiden Modulen liegt darin, wie sie Cookie-Sitzungsdaten speichern. Die [express-session](https://www.npmjs.com/package/express-session) Middleware speichert Sitzungsdaten auf dem Server; sie speichert die Session-ID nur im Cookie selbst, nicht im Sitzungsdatum. Standardmäßig verwendet er Speicher im Speicher und ist nicht für eine Produktionsumgebung konzipiert. In der Produktion müssen Sie einen skalierbaren Session-Shop einrichten; siehe die Liste der [kompatiblen Session-Shops](https://github.com/expressjs/session#compatible-session-stores).
+
+Im Gegensatz dazu implementiert [cookie-session](https://www.npmjs.com/package/cookie-session) Middleware Cookie unterstützten Speicher: Es serialisiert die gesamte Sitzung auf das Cookie und nicht nur auf eine Sitzungsschlüssel. Verwenden Sie es nur, wenn Session-Daten relativ klein sind und leicht als primitive Werte kodiert werden (statt Objekte). Obwohl Browser mindestens 4096 Bytes pro Cookie unterstützen sollen, um sicherzustellen, dass Sie das Limit nicht überschreiten, nicht größer als 4093 Bytes pro Domain. Beachten Sie auch, dass die Cookie-Daten für den Kunden sichtbar sind, Wenn es also einen Grund gibt, es sicher oder undurchsichtig zu halten, dann könnte `express-session` eine bessere Wahl sein.
+
+### Nicht den Standard-Sitzungs-Cookie-Namen verwenden
+
+Die Verwendung des Standard-Sitzungs-Cookie-Namens kann Ihre App für Angriffe öffnen. Das Sicherheitsproblem ähnelt `X-Powered-By`: Ein potenzieller Angreifer kann es verwenden, um den Server und die Zielangriffe entsprechend zu Fingerabdruck zu verwenden.
+
+Um dieses Problem zu vermeiden, verwenden Sie generische Cookie-Namen; zum Beispiel [express-session](https://www.npmjs.com/package/express-session) Middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.se(
+  session({
+    secret: 's3Cur3',
+    Name: 'sessionId',
+  })
+);
+```
+
+### Cookie-Sicherheitsoptionen festlegen
+
+Legen Sie die folgenden Cookie-Optionen fest, um die Sicherheit zu verbessern:
+
+- `secure` - Stellt sicher, dass der Browser das Cookie nur über HTTPS sendet.
+- `httpOnly` - Stellt sicher, dass das Cookie nur über HTTP(S), nicht über Client-JavaScript, gesendet wird. Dies hilft beim Schutz vor Site-übergreifenden Skripting-Attacken.
+- `domain` - gibt die Domain des Cookie an; verwenden Sie sie um sie mit der Domain des Servers zu vergleichen, auf dem die URL angefordert wird. Wenn sie übereinstimmen, überprüfen Sie als nächstes das Pfad-Attribut.
+- `path` - zeigt den Pfad des Cookie; verwenden Sie ihn um mit dem Abfragepfad zu vergleichen. Wenn dies und Domäne übereinstimmen, dann senden Sie das Cookie in der Anfrage.
+- `expires` - verwenden Sie, um das Ablaufdatum für persistente Cookies festzulegen.
+
+Hier ist ein Beispiel mit [cookie-session](https://www.npmjs.com/package/cookie-session) Middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date. ow() + 60 * 60 * 1000); // 1 Stunde
+App. se(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    Cookie: {
+      Secre: true
+      httpOnly: true
+      domain: 'example. om',
+      Pfad: 'foo/bar',
+      läuft ab: expiryDate,
+    },
+  })
+);
+```
+
+## Brute-Force-Angriffe gegen Autorisierung verhindern
+
+Stellen Sie sicher, dass Login-Endpunkte geschützt sind, um private Daten sicherer zu machen.
+
+Eine einfache und leistungsstarke Technik ist es, Autorisierungsversuche mit zwei Metriken zu blockieren:
+
+1. Die Anzahl der aufeinanderfolgenden fehlgeschlagenen Versuche mit dem gleichen Benutzernamen und der gleichen IP-Adresse.
+2. Die Anzahl fehlgeschlagener Versuche einer IP-Adresse über einen längeren Zeitraum. Zum Beispiel blockieren Sie eine IP-Adresse, wenn sie 100 fehlgeschlagene Versuche an einem Tag macht.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) Paket stellt Werkzeuge zur Verfügung, um diese Technik einfach und schnell zu machen. Du findest [ein Beispiel für brutalen Schutz in der Dokumentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Stellen Sie sicher, dass Ihre Abhängigkeiten sicher sind
+
+Die Verwendung von npm zur Verwaltung der Abhängigkeiten Ihrer Anwendung ist mächtig und komfortabel. Aber die Pakete, die Sie verwenden, können kritische Sicherheitslücken enthalten, die auch Ihre Anwendung betreffen könnten. Die Sicherheit Ihrer App ist nur so stark wie der "schwächste Link" in Ihren Abhängigkeiten.
+
+Seit npm@6 überprüft npm automatisch jede Installationsanforderung. Außerdem kannst du `npm audit` verwenden, um deinen Abhängigkeitsbaum zu analysieren.
+
+```bash
+$ npm Audit
+```
+
+Wenn du sicherer bleiben möchtest, bedenke [Snyk](https://snyk.io/).
+
+Snyk bietet sowohl ein [Kommandozeilenwerkzeug](https://www.npmjs.com/package/snyk) als auch eine [Github-Integration](https://snyk.io/docs/github), die Ihre Anwendung auf [Snyk's Open-Source-Verwundbarkeitsdatenbank] (https://snyk.io/vuln/) auf bekannte Verwundbarkeiten in Ihren Abhängigkeiten überprüft. Installieren Sie das CLI wie folgt:
+
+```bash
+$ npm Installation -g snyk
+$ cd your-app
+```
+
+Verwenden Sie diesen Befehl, um Ihre Anwendung auf Schwachstellen zu testen:
+
+```bash
+$ Snyk-Test
+```
+
+### Vermeiden Sie andere bekannte Schwachstellen
+
+Halten Sie Ausschau nach [Node Security Project](https://npmjs.com/advisories) oder [Snyk](https://snyk.io/vuln/) Ankündigungen, die Express oder andere Module, die Ihre App verwendet, beeinflussen können. Im Allgemeinen sind diese Datenbanken ausgezeichnete Ressourcen für Wissen und Werkzeuge rund um die Knotensicherheit.
+
+Schließlich können Express-Apps&mdash;wie alle anderen Web-Apps&mdash;anfällig für eine Vielzahl webbasierter Angriffe sein. Vertrauen Sie sich mit bekannten [Web-Verwundbarkeiten](https://www.owasp.org/www-project-top-ten/) und ergreifen Sie Vorsichtsmaßnahmen, um sie zu vermeiden.
+
+## Zusätzliche Überlegungen
+
+Hier sind einige weitere Empfehlungen der ausgezeichneten [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Empfehlen Sie diesen Blog-Beitrag für alle Details zu diesen Empfehlungen:
+
+- Immer die Benutzereingabe filtern und bereinigen, um gegen Site-übergreifendes Skripting (XSS) und Injektionsangriffe zu schützen.
+- Verteidigen Sie gegen SQL-Injektionsangriffe durch parametrierte Abfragen oder vorbereitete Anweisungen.
+- Benutzen Sie das Open-Source [sqlmap](http://sqlmap.org/) Werkzeug, um Verwundbarkeiten in Ihrer App zu erkennen.
+- Verwenden Sie die Werkzeuge [nmap](https://nmap.org/) und [sslyze](https://github.com/nabla-c0d3/sslyze) um die Konfiguration Ihrer SSL-Chiffren zu testen, Schlüssel, Neuverhandlung sowie die Gültigkeit Ihres Zertifikats.
+- Verwende [safe-regex](https://www.npmjs.com/package/safe-regex), um sicherzustellen, dass deine regulären Ausdrücke nicht anfällig für [reguläre Ausdrucksverweigerung des Dienstes](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) Angriffe sind.
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/de/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/de/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..df8006c126
--- /dev/null
+++ b/src/content/pages/de/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Gesundheitschecks und anmutiges Herunterfahren
+description: Erfahren Sie, wie Sie Gesundheitschecks und anmutiges Herunterfahren in Express-Apps implementieren können, um die Zuverlässigkeit zu verbessern, den Einsatz zu verwalten und sich mit Lastausgleichern wie Kubernetes zu integrieren.
+---
+
+## Angemessenes Herunterfahren
+
+Wenn Sie eine neue Version Ihrer Anwendung bereitstellen, müssen Sie die vorherige Version ersetzen. Der von Ihnen verwendete Prozessmanager sendet zuerst ein SIGTERM-Signal an die Anwendung, um zu benachrichtigen, dass es beendet wird. Sobald die Anwendung dieses Signal erhält, sollte sie aufhören, neue Anfragen anzunehmen, alle laufenden Anfragen zu beenden, die verwendeten Ressourcen aufräumen, einschließlich Datenbankverbindungen und Dateisperren dann beenden.
+
+### Beispiel
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Gesundheitschecks
+
+Ein Lastausgleicher verwendet Gesundheitsprüfungen, um festzustellen, ob eine Anwendungsinstanz gesund ist und Anfragen annehmen kann. Zum Beispiel [Kubernetes hat zwei Gesundheitschecke](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- 'liveness', das bestimmt, wann ein Container neu gestartet werden soll.
+- `readiness`, das bestimmt, wann ein Container bereit ist, den Verkehr zu akzeptieren. Wenn ein Pod nicht bereit ist, wird er aus den Lastausgleichern entfernt.
diff --git a/src/content/pages/de/advanced/security-updates.mdx b/src/content/pages/de/advanced/security-updates.mdx
new file mode 100644
index 0000000000..7e16278b93
--- /dev/null
+++ b/src/content/pages/de/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Sicherheitsupdates
+description: Überprüfen Sie die neuesten Sicherheitsupdates und Patches für Express.js, einschließlich detaillierter Verwundbarkeitslisten für verschiedene Versionen, um eine sichere Anwendung zu pflegen.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="warnung">
+
+Verwundbarkeiten von Node.js wirken sich direkt auf Express aus. Daher achte auf Node.js
+Verwundbarkeit und stelle sicher, dass du die neueste
+stabile Version von Node.js verwendest.
+
+</Alert>
+
+Die folgende Liste listet die Express Verwundbarkeiten auf, die in der angegebenen Versionsaktualisierung behoben wurden.
+
+<Alert type="info">
+
+Wenn Sie glauben, dass Sie eine Sicherheitslücke in Express entdeckt haben, lesen Sie bitte Sicherheits-
+Richtlinien und Prozeduren.
+
+</Alert>
+
+## 4,x
+
+- 4.21.2
+  - Die Abhängigkeit `path-to-regexp` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - Die Abhängigkeit `cookie` wurde aktualisiert, um eine [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x) zu adressieren. Dies kann deine Anwendung beeinflussen, wenn du `res.cookie` verwendest.
+- 4.20.0
+  - XSS-Verwundbarkeit in `res.redirect` behoben ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - Die Abhängigkeit `serve-static` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - Die Abhängigkeit `send` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - Die Abhängigkeit `path-to-regexp` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - Die Abhängigkeit `body-parser` wurde aktualisiert, um einen [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), dies kann deine Anwendung beeinflussen, wenn du url enconding aktiviert hast.
+- 4.19.0, 4.19.1
+  - Behoben der offenen Weiterleitungsverwundbarkeit in `res.location` und `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - Die Abhängigkeit `qs` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://github.com/advisories/GHSA-hrpp-h998-j3pp). Dies kann Ihre Anwendung beeinflussen, wenn die folgenden APIs verwendet werden: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - Die Abhängigkeit `forwarded` wurde aktualisiert, um eine [vulnerability]Adresse zu senden (https://npmjs.com/advisories/527). Dies kann Ihre Anwendung beeinflussen, wenn die folgenden APIs verwendet werden: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - Die Abhängigkeit `mime` wurde aktualisiert, um eine [vulnerability](https://npmjs.com/advisories/535), aber dieses Problem wirkt sich nicht auf Express aus.
+  - Die Abhängigkeit `send` wurde aktualisiert, um einen Schutz gegen eine [Node.js 8.5.0 Verwundbarkeit](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/) zu bieten. Dies wirkt sich nur auf die Ausführung von Express auf der speziellen Node.js Version 8.5.0 aus.
+- 4.15.5
+  - Die Abhängigkeit `debug` wurde aktualisiert, um eine [vulnerability](https://snyk.io/vuln/npm:debug:20170905), aber dieses Problem wirkt sich nicht auf Express aus.
+  - Die Abhängigkeit `fresh` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://npmjs.com/advisories/526). Dies wird deine Anwendung beeinflussen, wenn die folgenden APIs verwendet werden: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - Die Abhängigkeit `ms` wurde aktualisiert, um eine [vulnerability]zu adressieren (https://snyk.io/vuln/npm:ms:20170412). Dies kann Ihre Anwendung beeinflussen, wenn die nicht vertrauenswürdige Eingabe an die Option `maxAge` in der folgenden APIs übergeben wird: `express.static`, `res.sendfile` und `res.sendFile`.
+- 4.15.2
+  - Die Abhängigkeit `qs` wurde aktualisiert, um eine [vulnerability](https://snyk.io/vuln/npm:qs:20170213), aber dieses Problem wirkt sich nicht auf Express aus. Die Aktualisierung auf 4.15.2 ist eine gute Praxis, aber nicht erforderlich, um die Verwundbarkeit zu beheben.
+- 4.11.1
+  - Verwundbarkeit der Root-Pfad-Offenlegung in `express.static`, `res.sendfile` und `res.sendFile` behoben
+- 4.10.7
+  - Behoben der offenen Weiterleitungsverwundbarkeit in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Fehlerbehebung von Verzeichnisüberschreitungen in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 kann `fd`s in bestimmten Situationen lecken, die `express.static` und `res.sendfile` betreffen. Schädliche Anfragen könnten `fd`s zu Leck führen und letztendlich zu `EMFILE` Fehlern und Serverunreaktion.
+- 4.8.0
+  - Sparse Arrays mit extrem hohen Indizes im Query-String könnten dazu führen, dass der Prozess aus dem Speicher geht und der Server abstürzt.
+  - Extrem verschachtelte Query-String-Objekte könnten dazu führen, dass der Prozess blockiert und der Server vorübergehend nicht reagiert.
+
+## 3,x
+
+<Alert type="warnung">
+**Express 3.x IST END-OF-OF-LEBEN UND KEINE LIEFERANTEN**
+
+Bekannte und unbekannte Sicherheits- und Leistungsprobleme in 3.x wurden seit dem letzten Update (1. August 2015) nicht behoben. Es wird dringend empfohlen, die neueste Version von Express zu verwenden.
+
+Wenn du nicht in der Lage bist nach 3.x zu aktualisieren, erwäge bitte [Kommerzielle Support-Optionen](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Verwundbarkeit der Root-Pfad-Offenlegung in `express.static`, `res.sendfile` und `res.sendFile` behoben
+- 3.19.0
+  - Behoben der offenen Weiterleitungsverwundbarkeit in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Fehlerbehebung von Verzeichnisüberschreitungen in `express.static`.
+- 3.16.6
+  - Node.js 0.10 kann `fd`s in bestimmten Situationen lecken, die `express.static` und `res.sendfile` betreffen. Schädliche Anfragen könnten `fd`s zu Leck führen und letztendlich zu `EMFILE` Fehlern und Serverunreaktion.
+- 3.16.0
+  - Sparse Arrays, die extrem hohe Indizes im Query-String haben, könnten dazu führen, dass der Prozess aus dem Speicher geht und den Server abstürzt.
+  - Extrem verschachtelte Query-String-Objekte könnten dazu führen, dass der Prozess blockiert und der Server vorübergehend nicht reagiert.
+- 3.3.0
+  - Die 404-Reaktion eines nicht unterstützten Methodenversuchs war anfällig für Site-übergreifende Skripting-Attacken.
diff --git a/src/content/pages/de/guide/database-integration.mdx b/src/content/pages/de/guide/database-integration.mdx
new file mode 100644
index 0000000000..1c7a04d8d8
--- /dev/null
+++ b/src/content/pages/de/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Datenbankintegration
+description: Erfahren Sie, wie Sie verschiedene Datenbanken mit Express.js Anwendungen integrieren können, einschließlich der Einrichtung von Beispielen für MongoDB, MySQL, PostgreSQL und mehr.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Hinzufügen der Möglichkeit, Datenbanken mit Express-Apps zu verbinden, ist nur eine Frage des Laden eines geeigneten Node.js Treibers für die Datenbank in Ihrer App. Dieses Dokument erklärt kurz wie Sie einige der beliebtesten Node.js-Module für Datenbanksysteme in Ihrer Express-App hinzufügen und nutzen:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="warnung">
+
+Diese Datenbanktreiber sind unter vielen verfügbar. Für andere Optionen suchen Sie auf der
+[npm](https://www.npmjs.com/) Seite.
+
+</Alert>
+
+## Cassandra
+
+**Modul**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installation
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Beispiel
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.xecute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Modul**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Installation
+
+```bash
+$ npm install couchbase
+```
+
+### Beispiel
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// Ein Dokument zu einem Bucket
+bucket hinzufügen. nsert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console. og(result);
+  }
+});
+
+// alle Dokumente mit Schuhgröße 13
+const n1ql = 'SELECT d. FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery. romString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Modul**: [nano](https://github.com/dscape/nano)
+
+### Installation
+
+```bash
+$ npm install nano
+```
+
+### Beispiel
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db. se('books');
+
+// Fügen Sie ein Buchdokument in die Datenbank
+Bücher ein. nsert({ name: 'The Art of War' }, null, (err, body) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console. og(body);
+  }
+});
+
+// Eine Liste aller Bücher
+herunterladen. ist((err, body) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Modul**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Installation
+
+```bash
+$ npm Level Level Level down
+```
+
+### Beispiel
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.ut('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.et('name', (err, value) => {
+    if (err) return console.og('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Modul**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Installation
+
+```bash
+$ npm install mysql
+```
+
+### Beispiel
+
+```js
+const mysql = require('mysql');
+const connection = mysql.reateConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  Passwort: 's3kreee7',
+  Datenbank: 'my_db',
+});
+
+Verbindung.onnect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, Zeilen, Felder) => {
+  if (err) throw err;
+
+  console.og('Die Lösung ist: ', Zeilen[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Modul**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installation
+
+```bash
+$ npm install mongodb
+```
+
+### Beispiel (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.ollection('Säuge')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(Ergebnis);
+    });
+});
+```
+
+### Beispiel (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.b('animals');
+
+  db.collection('Säugetier')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(Ergebnis);
+    });
+});
+```
+
+Wenn du einen Objektmodelltreiber für MongoDB möchtest, schau dir [Mongoose]an (https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Modul**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installation
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Beispiel
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.asic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .un('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].et('count'));
+    })
+    .catch((error) => {
+      Konsole.og(error);
+    });
+});
+```
+
+## Jürgen
+
+**Modul**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installation
+
+HINWEIS: [Siehe die Installationsvoraussetzungen](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm oracledb installieren
+```
+
+### Beispiel
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  Passwort: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = wait oracledb. etConnection(config);
+
+    const result = warten conn. xecute('wählen Sie * von Mitarbeitern, bei denen staffe_id = :id', [empId]);
+
+    Konsole. og(result.rows[0]);
+  } catch (err) {
+    Konsole. og('Ouch! , Fehler);
+  } Endlich {
+    if (conn) {
+      // conn assignment worked, müssen Sie
+      warten Konn. lose();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Modul**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installation
+
+```bash
+$ npm install pg-promise
+```
+
+### Beispiel
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .hen((data) => {
+    console.log('DATA:', data.value);
+  })
+  .atch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Modul**: [redis](https://github.com/mranney/node_redis)
+
+### Installation
+
+```bash
+$ npm install redis
+```
+
+### Beispiel
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.et('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.set(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.keys('hash key', (err, replies) => {
+  console.log(`${replies.length} Antworten:`);
+
+  Antworten.orEach((reply, i) => {
+    Konsole.og(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL-Server
+
+**Modul**: [tedious](https://github.com/tediousjs/tedious)
+
+### Installation
+
+```bash
+$ npm install tedious
+```
+
+### Beispiel
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious'). quest;
+
+const config = {
+  server: 'localhost',
+  Authentifizierung: {
+    type: 'default',
+    Optionen: {
+      userName: 'your_username', // Aktualisiere mich
+      Passwort: 'your_password', // Aktualisiere mich
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+Verbindung. n('connect', (err) => {
+  if (err) {
+    console. og(err);
+  } else {
+    executeStatement();
+  }
+});
+
+Funktion executeStatement() {
+  request = new Request("select 123, 'Hallo world'", (err, rowCount) => {
+    if (err) {
+      console. og(err);
+    } else {
+      console. og(`${rowCount} Zeilen`);
+    }
+    Verbindung. lose();
+  });
+
+  request.on('row', (columns) => {
+    columns. orEach((column) => {
+      if (column.value === null) {
+        console. og('NULL');
+      } else {
+        console.log(column. alue);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Modul**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installation
+
+```bash
+$ npm install sqlite3
+```
+
+### Beispiel
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db. un('CREATE TABLE lorem (info TEXT)');
+  const stmt = db. repare('INSERT INTO lorem VALUES (?)');
+
+  für (let i = 0; i < 10; i++) {
+    stmt. un(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db. ach('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    Konsole. og(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Modul**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installation
+
+```bash
+$ npm elasticsearch installieren
+```
+
+### Beispiel
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .earch({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          Felder: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .hen(
+    (Antwort) => {
+      const hits = response.hits.its;
+    },
+    (error) => {
+      console.race(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/de/guide/migrating-4.mdx b/src/content/pages/de/guide/migrating-4.mdx
new file mode 100644
index 0000000000..28a5f90f56
--- /dev/null
+++ b/src/content/pages/de/guide/migrating-4.mdx
@@ -0,0 +1,666 @@
+---
+title: Umzug nach Express 4
+description: Eine Anleitung zur Migration Ihrer Express.js Anwendungen von Version 3 auf 4, die Änderungen in Middleware, Routing und wie Sie Ihre Codebase effektiv aktualisieren können.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 ist ein brillanter Wechsel von Express 3. Das bedeutet, dass eine bestehende Express 3-App _nicht_ funktioniert, wenn Sie die Express-Version in ihren Abhängigkeiten aktualisieren.
+
+Dieser Artikel Covers:
+
+<ul class="doklist">
+  <li>
+    <a href="#changes">Änderungen in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">Ein Beispiel</a> für die Migration einer Express 3 App auf Express
+    4.
+  </li>
+  <li>
+    <a href="#app-gen">Upgrade auf den Express 4 App-Generator</a>.
+  </li>
+</ul>
+
+## Änderungen in Express 4
+
+Es gibt mehrere bedeutende Änderungen in Express 4:
+
+<ul class="doklist">
+  <li>
+    <a href="#core-changes">Änderungen des Express-Core- und Middleware-Systems.</a> Die
+    Abhängigkeiten von Connect und eingebauter Middleware wurden entfernt, daher müssen Sie selbst
+    Middleware hinzufügen.
+  </li>
+  <li>
+    <a href="#routing">Änderungen am Routingsystem.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Verschiedene andere Änderungen.</a>
+  </li>
+</ul>
+
+Siehe auch:
+
+- [Neue Features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migration von 3.x auf 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Änderungen am Express-Kern- und Middleware-System
+
+Express 4 hängt nicht mehr von Verbindung ab und entfernt alle eingebauten
+Middleware aus seinem Kern, mit Ausnahme der `express.static` Funktion. Das bedeutet, dass
+Express jetzt ein unabhängiges Routing- und Middleware-Web-Framework ist und
+Express-Versionierung und Releases sind nicht von Middleware-Updates betroffen.
+
+Ohne integrierte Middleware müssen Sie explizit alle
+Middleware hinzufügen, die für den Betrieb Ihrer App erforderlich ist. Folgen Sie einfach diesen Schritten:
+
+1. Modul installieren: `npm install --save <module-name>`
+2. Benötige in deiner App das Modul: `require('module-name')`
+3. Verwenden Sie das Modul entsprechend seiner Dokumentation: `app.use( ... )`
+
+Die folgende Tabelle listet Express 3 Middleware und ihre Amtskollegen in Express 4 auf.
+
+<table class="doktierbar" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">Körper-Parser</a> +
+      <a href="https://github.com/expressjs/multer">Multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express .compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">Komprimierung</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">Cookie-Sitzung</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">Cookie-Parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">Morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">Express-Session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">Servierfavicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">Antwortzeit</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">Methodenüberschreibung</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">Verbindungs-Timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">Servierindex</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">Servierstatische</a>
+    </td>
+  </tr>
+</table>
+
+Hier ist die [vollständige Liste](https://github.com/senchalabs/connect#middleware) von Express 4 Middleware.
+
+In den meisten Fällen können Sie einfach die alte Version 3 Middleware durch
+dessen Express 4 Gegenstück ersetzen. Details hierzu finden Sie in der Moduldokumentation in
+GitHub.
+
+#### `app.use` akzeptiert Parameter
+
+In Version 4 können Sie mit einem Variablen-Parameter den Pfad definieren, in dem Middleware-Funktionen geladen werden, dann den Wert des Parameters aus dem Route-Handler lesen.
+Zum Beispiel:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### Das Routingsystem
+
+Apps laden nun implizit Routing Middleware damit Sie sich keine
+Sorgen mehr darüber machen müssen, in welcher Reihenfolge Middleware in Bezug auf
+der `router` Middleware geladen wird.
+
+Die Art und Weise, wie Sie Routen definieren, ist unverändert, aber das Routensystem hat zwei
+neue Funktionen, um Ihre Routen zu organisieren:
+
+- Eine neue Methode, `app.route()`, um verkettete Routenhandler für einen Routenpfad zu erstellen.
+- Eine neue Klasse, `express.Router`, um modulare montierbare Routenhandler zu erstellen.
+
+#### `app.route()` Methode
+
+Die neue Methode `app.route()` ermöglicht es dir, verkettete Routenhandler
+für einen Routenpfad zu erstellen. Da der Weg an einem einzigen Ort angegeben ist, ist die Schaffung modularer Routen hilfreich, ebenso wie die Reduzierung von Redundanz und Typos. Weitere
+Informationen über Routen finden Sie unter [`Router()` Dokumentation](/en/4x/api#router).
+
+Hier ist ein Beispiel für verkettete Routenhandler, die durch die Funktion `app.route()` definiert werden.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res. end('Holt ein zufälliges Buch');
+  })
+  . ost(req, res) => {
+    res.send('Add a book');
+  })
+  . ut((req, res) => {
+    res.send('Buch aktualisieren');
+});
+```
+
+#### `express.Router` Klasse
+
+Die andere Funktion, die hilft, Routen zu organisieren, ist eine neue Klasse,
+`express.Router`, die Sie verwenden können, um modulare montierbare
+Routenhandler zu erstellen. Eine `Router`-Instanz ist ein komplettes Middleware- und
+\-Routing-System. Aus diesem Grund wird sie oft als "Mini-App" bezeichnet.
+
+Das folgende Beispiel erzeugt einen Router als Modul, lädt Middleware in
+, definiert einige Routen und mountet sie auf einem Pfad in der Hauptanwendung.
+
+Erstelle zum Beispiel eine Router-Datei namens `birds.js` im App-Verzeichnis,
+mit folgendem Inhalt:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// Middleware spezifisch für diesen
+Router. se(req, res, next) => {
+  console.log('Time: ', Datum. ow());
+  next();
+});
+// die Startseite Route
+definieren. et('/', (req, res) => {
+  res.send('Birds home page');
+});
+// über Route
+definieren. et('/about', (req, res) => {
+  res.send('Über Vögel');
+});
+
+module.exports = router;
+```
+
+Laden Sie dann das Router-Modul in der App:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', Vögel);
+```
+
+Die App wird nun in der Lage sein, Anfragen an die `/birds` und
+`/birds/about` Pfade zu bearbeiten, und ruft die "timeLog"
+Middleware auf, die spezifisch für die Route ist.
+
+### Andere Änderungen
+
+Die folgende Tabelle listet weitere kleine, aber wichtige Änderungen in Express 4 auf:
+
+<table class="doktierbar" border="1">
+  <tr>
+    <th>Objekt</th>
+    <th>Beschreibung</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>
+      Express 4 benötigt Node.js 0.10.x oder höher und hat die Unterstützung für Node.js 0.8.x
+      fallen gelassen.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      Das `http` Modul wird nicht mehr benötigt, außer du musst direkt mit ihm
+      (socket.io/SPDY/HTTPS) arbeiten. Die App kann über die Funktion `app.listen()` gestartet
+      werden.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      Die Funktion `app.configure()` wurde entfernt. Benutze die Funktion `process.env.NODE_ENV`
+      oder `app.get('env')` um die Umgebung zu erkennen und die App entsprechend zu konfigurieren.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">Die Eigenschaft `json spaces` ist standardmäßig in Express 4 deaktiviert.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Benutze `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()` und
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">Es werden keine relativen URLs mehr aufgelöst.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">War ein Array; jetzt ein Objekt.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">War eine Funktion; jetzt ein Objekt.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">In `res.headersSent` geändert.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Jetzt als `app.mountpath` verfügbar.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">Entfernt.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Entfernt.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      Die Funktionalität ist nun auf das Setzen des grundlegenden Cookie-Wertes beschränkt. Benutze
+      `res.cookie()` für hinzugefügte Funktionalität.
+    </td>
+  </tr>
+</table>
+
+## Beispiel-App-Migration
+
+Hier ist ein Beispiel für die Migration einer Express-3-Anwendung auf Express 4.
+Die Dateien von Interesse sind `app.js` und `package.json`.
+
+### Version 3 App
+
+#### `app.js`
+
+Betrachten Sie eine Express v.3 Anwendung mit der folgenden `app.js` Datei:
+
+```js
+var express = require('express ');
+var routes = require('./routes');
+var user = require('. routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// alle Umgebungen
+app.et('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.ession({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.tatic(path.join(__dirname, 'public')));
+
+// Entwicklung nur
+if (app.get('env') === 'development') {
+  app.se(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.reateServer(app).listen(app.get('port'), () => {
+  console.log('Express Server, der auf Port ' + app.get('port'));
+});
+```
+
+#### "package.json"
+
+The accompanying version 3 `package.json` file might look
+something like this:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dependencies": {
+    "express": "3. 2.0",
+    "Pug": "*"
+  }
+}
+```
+
+### Verarbeiten
+
+Beginnen Sie den Migrationsprozess, indem Sie die benötigte Middleware für die
+Express 4 App installieren und Express und Pug mit folgendem Befehl auf ihre jeweils neueste
+Version aktualisieren:
+
+```bash
+$ npm installieren serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Folgende Änderungen an `app.js` vornehmen:
+
+1. Die integrierten Express-Middleware-Funktionen `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` und
+   `express.errorHandler` sind nicht mehr verfügbar auf dem
+   `express` Objekt. Sie müssen ihre Alternativen
+   manuell installieren und in der App laden.
+
+2. Du musst die `app.router` Funktion nicht mehr laden.
+   Es ist kein gültiges Express 4 App-Objekt, also entferne den
+   `app.use(app.router);` Code.
+
+3. Stellen Sie sicher, dass die Middleware-Funktionen in der richtigen Reihenfolge geladen werden - laden Sie `errorHandler` nach dem Laden der App-Routen.
+
+### Version 4 App
+
+#### "package.json"
+
+Das Ausführen des obigen `npm` Befehls wird `package.json` wie folgt aktualisieren:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1. ",
+    "express ": "^4.8.0",
+    "express-session": "^1. .2",
+    "pug": "^2.0.0",
+    "method-override": "^2. .2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1. ",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Entferne dann ungültigen Code, lade die benötigte Middleware und führe bei Bedarf andere
+Änderungen durch. Die `app.js` Datei wird folgendermaßen aussehen:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('. routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// alle Umgebungen
+app. et('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app. se(methodOverride());
+app. se(
+  session({
+    resave: true,
+    saveUninitialized: true
+    Geheimnis: 'uwotm8',
+  })
+);
+App. se(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes. ndex);
+app.get('/users', user.list);
+
+// Fehler beim Umgang mit Middleware sollten nach dem Laden der Routen
+geladen werden, wenn (app. et('env') === 'development') {
+  app. se(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app. et('port'), () => {
+  console.log('Express Server, der auf Port ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+Wenn du nicht direkt mit dem `http` Modul (socket.io/SPDY/HTTPS) arbeiten musst, ist das Laden nicht erforderlich, und die App kann einfach auf diese Weise gestartet werden:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express Server, der auf Port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### App ausführen
+
+Der Migrationsprozess ist abgeschlossen und die App ist nun eine
+Express 4 App. Um die App zu bestätigen, starten Sie die App mit dem folgenden Befehl:
+
+```bash
+$ Knoten .
+```
+
+Laden Sie [http://localhost:3000](http://localhost:3000)
+und sehen Sie die Startseite von Express 4 an.
+
+## Upgrade auf den Express 4 App-Generator
+
+Das Kommandozeilen-Werkzeug, um eine Express-App zu generieren, ist immer noch
+`Express`, aber um auf die neue Version zu aktualisieren Sie müssen
+den Express 3 App-Generator deinstallieren und dann den neuen
+`express-generator` installieren.
+
+### Installiere
+
+Wenn Sie bereits den Express 3 App-Generator auf Ihrem System installiert haben,
+müssen Sie ihn deinstallieren:
+
+```bash
+$ npm Deinstallation -g Express
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Jetzt den neuen Generator installieren:
+
+```bash
+$ npm Installation -g express-generator
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Jetzt wird der Befehl `Express` auf Ihrem System auf den
+Express 4 Generator aktualisiert.
+
+### Änderungen am App-Generator
+
+Befehlsoptionen und -verwendung bleiben weitgehend gleich, mit den folgenden Ausnahmen:
+
+- Die Option `--sessions` wurde entfernt.
+- Die `--jshtml` Option wurde entfernt.
+- `--hogan` Option hinzugefügt, um [Hogan.js]zu unterstützen (http://twitter.github.io/hogan.js/).
+
+### Beispiel
+
+Führen Sie den folgenden Befehl aus, um eine Express 4 App zu erstellen:
+
+```bash
+$ Express App 4
+```
+
+Wenn du dir den Inhalt der `app4/app.js` Datei anschaust, wirst du
+bemerken, dass alle Middleware-Funktionen (außer `express. tatic`), die für
+benötigt werden, wird die App als unabhängige Module geladen, und die `router` Middleware
+nicht mehr explizit in der App geladen wird.
+
+Du wirst auch bemerken, dass die `app.js` Datei jetzt ein Knoten ist. s Modul im Gegensatz zu der Standalone-App, die vom alten Generator erzeugt wurde.
+
+Nach der Installation der Abhängigkeiten starten Sie die App mit dem folgenden Befehl:
+
+```bash
+$ npm Start
+```
+
+Wenn du das `npm start`-Skript im `package betrachtest. son-Datei,
+wirst du bemerken, dass der eigentliche Befehl, der die App startet,
+`node ist. bin/www`, die zuvor `node app.js\`
+in Express 3 war.
+
+Because the `app.js` file that was generated by the Express 4 generator
+is now a Node.js module, it can no longer be started independently as an app
+(unless you modify the code). Das Modul muss in einer Node.js-Datei
+geladen und über die Node.js-Datei gestartet werden. Die Node.js Datei ist in diesem Fall `./bin/www`
+.
+
+Weder das `bin` Verzeichnis noch die erweiterungslose `www`
+Datei ist zwingend erforderlich, um eine Express-App zu erstellen oder die App zu starten. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+Um das `www`-Verzeichnis loszuwerden und die Dinge auf die "Express 3 Wege" zu halten, lösche
+die Zeile, die `module. xports = app;` am Ende der
+`app.js` Datei einfügen und den folgenden Code dort einfügen:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express Server, der auf Port ' + server.address().port);
+});
+```
+
+Stelle sicher, dass du das `debug` Modul oben in der `app.js` Datei unter Verwendung des folgenden Codes lädst:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Als nächstes ändere `"start": "node ./bin/www"` in der Datei `package.json` zu `"start": "node app.js"`.
+
+Du hast nun die Funktionalität von `./bin/www` zurück auf
+`app.js` verschoben. Diese Änderung wird nicht empfohlen, aber die Übung hilft dir
+zu verstehen, wie das `. bin/www` Datei funktioniert und warum die `app.js` Datei
+nicht mehr alleine startet.
diff --git a/src/content/pages/de/guide/migrating-5.mdx b/src/content/pages/de/guide/migrating-5.mdx
new file mode 100644
index 0000000000..50207306e2
--- /dev/null
+++ b/src/content/pages/de/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Umzug nach Express 5
+description: Eine umfassende Anleitung zur Migration Ihrer Express.js-Anwendungen von Version 4 auf 5, die aufwändige Änderungen, veraltete Methoden und neue Verbesserungen enthält.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 unterscheidet sich nicht sehr von Express 4; obwohl es die gleiche grundlegende API hat, gibt es immer noch Änderungen, die die Kompatibilität mit der vorherigen Version stören. Daher könnte eine Anwendung mit Express 4 nicht funktionieren, wenn Sie sie auf Express 5 aktualisieren.
+
+Um diese Version zu installieren, benötigen Sie eine Node.js Version 18 oder höher. Führen Sie dann den folgenden Befehl in Ihrem Anwendungsverzeichnis aus:
+
+```sh
+npm "express@5" installieren
+```
+
+Sie können dann Ihre automatisierten Tests durchführen, um zu sehen, was fehlschlägt, und Probleme gemäß den unten aufgeführten Updates beheben. Nach dem Beheben von Testfehlern führen Sie Ihre App aus, um zu sehen, welche Fehler auftreten. Sie werden sofort erfahren, ob die App Methoden oder Eigenschaften verwendet, die nicht unterstützt werden.
+
+## Express 5 Codemoden
+
+Um Ihnen zu helfen, Ihren Expressserver zu migrieren Wir haben eine Reihe von Codemods erstellt, die Ihnen helfen, Ihren Code automatisch auf die neueste Version von Express zu aktualisieren.
+
+Führen Sie den folgenden Befehl aus, um alle verfügbaren Codemods auszuführen:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+Wenn du eine bestimmte Codemod ausführen möchtest, kannst du folgenden Befehl ausführen:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+Du findest die Liste der verfügbaren Codemoden [here](https://codemod.link/express).
+
+## Änderungen in Express 5
+
+**Entfernte Methoden und Eigenschaften**
+
+<ul class="doklist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Pluralisierte Methodennamen</a>
+  </li>
+  <li>
+    <a href="#leading">Führe Doppelpunkt im Namensargument zu app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(name)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') und res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(Körper, Status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">Express:Router Debug Logs</a>
+  </li>
+</ul>
+
+**Geändert**
+
+<ul class="doklist">
+  <li>
+    <a href="#path-syntax">Pfad-Routenpassender Syntax</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">abgelehnte Versprechungen von Middleware und Handler</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static Punktdateien</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Verbesserungen**
+
+<ul class="doklist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Brotli Kodierungsunterstützung</a>
+  </li>
+</ul>
+
+## Entfernte Methoden und Eigenschaften
+
+Wenn du eine dieser Methoden oder Eigenschaften in deiner App verwendest, stürzt sie ab. Also müssen Sie Ihre App nach dem Update auf Version 5 ändern.
+
+### app.del()
+
+Express 5 unterstützt nicht mehr die `app.del()` Funktion. Wenn Sie diese Funktion verwenden, wird ein Fehler geworfen. Um HTTP DELETE Routen zu registrieren, benutze stattdessen die `app.delete()` Funktion.
+
+Anfangs wurde `del` anstelle von `delete` verwendet, da `delete` ein reserviertes Schlüsselwort in JavaScript ist. Jedoch können ECMAScript 6, `delete` und andere reservierte Schlüsselwörter legal als Eigenschaftsnamen verwendet werden.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @express js/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.elete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+Die Signatur `app.param(fn)` wurde verwendet, um das Verhalten der `app.param(name, fn)` Funktion zu ändern. Es ist seit v4.11.0 veraltet und Express 5 unterstützt es überhaupt nicht mehr.
+
+### Pluralisierte Methodennamen
+
+Die folgenden Methodennamen wurden pluralisiert. In Express 4 führte die Verwendung der alten Methoden zu einer Deprecation Warnung. Express 5 unterstützt sie nicht mehr:
+
+`req.acceptsCharset()` wird durch `req.acceptsCharsets()` ersetzt.
+
+`req.acceptsEncoding()` wird durch `req.acceptsEncodings()` ersetzt.
+
+`req.acceptsLanguage()` wird durch `req.acceptsLanguages()` ersetzt.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.cceptsEncoding('br');
+  req.acceptsLanguage('de');
+
+  // ...
+});
+
+// v5
+app.ll('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('de');
+
+  // ...
+});
+```
+
+### Führender Doppelpunkt (:) im Namen von app.param(name, fn)
+
+Ein führendes Doppelzeichen (:) im Namen der `app. aram(name, fn)` Funktion ist ein Überbleibsel von Express 3, und um der Abwärtskompatibilität willen hat Express 4 sie mit einer Veraltungsmeldung unterstützt. Express 5 ignoriert es stillschweigend und verwendet den Namensparameter, ohne ihn mit einem Doppelpunkt zu präfixieren.
+
+Dies sollte deinen Code nicht beeinflussen, wenn du der Express-4-Dokumentation von [app.param]folgst (/en/4x/api#app.param), da es keine Erwähnung des führenden Doppelpunkts.
+
+### req.param(Name)
+
+Diese potenziell verwirrende und gefährliche Methode zum Abrufen von Formulardaten wurde entfernt. Sie müssen nun gezielt nach dem übermittelten Parameternamen im `req.params`, `req.body` oder `req.query` Objekt suchen.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.aram('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.d;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, Status)
+
+Express 5 unterstützt nicht mehr die Signatur `res.json(obj, status)`. Setze stattdessen den Status und verkette ihn auf die Methode `res.json()` wie folgt: `res.status(status).json(obj)`.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 unterstützt nicht mehr die Signatur `res.jsonp(obj, status)`. Setze stattdessen den Status und verkette ihn auf die `res.jsonp()` Methode wie folgt: `res.status(status).jsonp(obj)`.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, Status)
+
+Express 5 unterstützt nicht mehr die Signatur `res.redirect(url, status)`. Verwenden Sie stattdessen die folgende Signatur: `res.redirect(status, url)`.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') und res.location('back')
+
+Express 5 unterstützt nicht mehr den magischen String `back` in den Methoden `res.redirect()` und `res.location()`. Verwenden Sie stattdessen den `req.get('Referrer') || '/'` Wert, um zurück zur vorherigen Seite zu leiten. In Express 4 wurden die Methoden `res.redirect('back')` und `res.location('back')` veraltet.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(Körper, Status)
+
+Express 5 unterstützt nicht mehr die Signatur `res.send(obj, status)`. Setze stattdessen den Status und verkette ihn auf die Methode `res.send()` wie folgt: `res.status(status).send(obj)`.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(Status)
+
+Express 5 unterstützt nicht mehr die Signatur `res.send(status)`, wobei `status` eine Zahl ist. Verwenden Sie stattdessen die `res. endStatus(statusCode)` Funktion, die den HTTP-Antwort-Header-Statuscode setzt und die Textversion des Codes sendet: "Nicht gefunden", "Interner Server-Fehler", und so weiter.
+Wenn Sie eine Nummer mit Hilfe der `res senden müssen. end()` Funktion, zitiert die Zahl, um sie in einen String zu konvertieren, so dass Express es nicht als Versuch interpretiert, die nicht unterstützte alte Signatur zu verwenden.
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+Die `res.sendfile()` Funktion wurde durch eine camel-cased Version `res.sendFile()` in Express 5 ersetzt.
+
+**Hinweis:** In Express 5, `res. endFile()` verwendet das Paket `mime-types` für MIME Typenerkennung, welches verschiedene Content-Type Werte als Express 4 für mehrere gängige Dateitypen zurückgibt:
+
+- JavaScript-Dateien (.js): Jetzt "text/javascript" statt "application/javascript"
+- JSON-Dateien (.json): jetzt "application/json" statt "text/json"
+- CSS-Dateien (.css): Jetzt "text/css" statt "text/plain"
+- XML-Dateien (.xml): jetzt "application/xml" statt "text/xml"
+- Schriftdateien (.woff): Jetzt "font/woff" statt "application/font-woff"
+- SVG-Dateien (.svg): jetzt "image/svg+xml" statt "application/svg+xml"
+
+<Alert type="info">
+Sie können die veralteten Signaturen durch folgenden Befehl ersetzen:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+Die Signatur `router.param(fn)` wurde verwendet, um das Verhalten der `router.param(name, fn)` Funktion zu ändern. Es ist seit v4.11.0 veraltet und Express 5 unterstützt es überhaupt nicht mehr.
+
+### express.static.mime
+
+In Express 5 ist `mime` nicht mehr eine exportierte Eigenschaft des `static` Feldes.
+Benutze das [`mime-types` package](https://github.com/jshttp/mime-types), um mit MIME Werte zu arbeiten.
+
+**Wichtig:** Diese Änderung beeinflusst nicht nur die direkte Verwendung von `express.static.mime`, sondern auch andere Express-Methoden, die auf die Erkennung des MIME-Typs angewiesen sind, wie `res.sendFile()`. Die folgenden MIME-Typen haben sich von Express 4 geändert:
+
+- JavaScript-Dateien (.js): Jetzt als "text/javascript" anstelle von "application/javascript"
+- JSON-Dateien (.json): Jetzt als "application/json" anstelle von "text/json"
+- CSS-Dateien (.css): Jetzt als "text/css" anstelle von "text/plain"
+- HTML-Dateien (): Wird nun als "text/html; charset=utf-8" anstelle von "text/html" ausgegeben.
+- XML-Dateien (.xml): Jetzt als "application/xml" anstelle von "text/xml"
+- Schriftdateien (.woff): Jetzt als "font/woff" anstelle von "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:router Debug-Logs
+
+In Express 5 wird die Router-Handhabungslogik durch eine Abhängigkeit ausgeführt. Daher sind die
+Debug-Logs für den Router nicht mehr unter dem `express :` Namensraum verfügbar.
+In v4 waren die Protokolle unter den Namensräumen `express:router`, `express:router:layer`,
+und `express:router:route` verfügbar. Alle diese wurden unter den Namensraum `express:*` aufgenommen.
+In v5.1+ sind die Logs unter den Namensräumen `router`, `router:layer` und `router:route` verfügbar.
+Die Logs von `router:layer` und `router:route` sind im Namensraum `router:*` enthalten.
+Um das selbe Detail der Debug-Protokollierung mit `express:*` in v4 zu erreichen, benutze eine Verbindung von
+`express:*`, `router` und `router:*`.
+
+```sh
+
+DEBUG=Express:* node index.js
+
+
+DEBUG=Express:*,router,router:* node index.js
+```
+
+## Geändert
+
+### Pfad Route übereinstimmende Syntax
+
+Syntax für Pfadrouten ist, wenn als erster Parameter `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()` und `router.use()` APIs angegeben wird. Die folgenden Änderungen wurden vorgenommen, wie der Pfad-String auf eine eingehende Anfrage abgestimmt wird:
+
+- Das Platzhalter `*` muss einen Namen haben, passend zum Verhalten der Parameter `:`, verwende `/*splat` statt `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="info">
+`*splat` entspricht jedem Pfad ohne den Wurzelpfad. Wenn du den Wurzelpfad auch `/` anpassen musst, kannst du `/{*splat}` verwenden, indem du den Platzhalter in Klammern verpackst.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- Das optionale Zeichen `?` wird nicht mehr unterstützt, verwende stattdessen Klammern.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Regexp Zeichen werden nicht unterstützt. Zum Beispiel:
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+sollte geändert werden:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Einige Zeichen wurden reserviert, um Verwirrung während des Upgrades zu vermeiden (`()[]?+!`), verwenden Sie `\` um sie zu maskieren.
+- Parameternamen unterstützen nun gültige JavaScript-Identifikatoren oder zitiert wie `:"this`.
+
+### Abgelehnte Versprechen von Middleware und Handlern
+
+Fordern Sie Middleware und Handler an, die abgelehnte Versprechungen zurückgeben, werden nun durch die Weiterleitung des zurückgewiesenen Wertes als `Error` an die Fehlerbehandlung Middleware behandelt. Das bedeutet, dass die Verwendung von `async` Funktionen als Middleware und Handler einfacher ist als je zuvor. Wenn ein Fehler in einer `async`-Funktion oder einem abgewiesenen Versprechen geworfen wird, wird `erwartet in einer async-Funktion, diese Fehler werden an den Fehlerhandler übergeben, als ob `next(err)\` aufgerufen würde.
+
+Details darüber, wie Express mit Fehlern umgeht, finden Sie in der [Dokumentation zur Fehlerbehandlung](/en/guide/error-handling).
+
+### express.urlencoded
+
+Die `express.urlencoded` Methode erzeugt standardmäßig die `extended` Option `false`.
+
+### express.static dotfiles
+
+In Express 5 ist die Option `express.static` middleware `dotfiles` nun standardmäßig `"ignore`. Dies ist eine Änderung von Express 4, wo dotfiles standardmäßig bedient wurden. Als Ergebnis sind Dateien in einem Verzeichnis, das mit einem Punkt (`.`) beginnt, wie `. ell-known`, wird nicht mehr erreichbar sein und einen **404 Nicht gefunden** Fehler zurückgeben. Dies kann die Funktionalität, die von der Bereitstellung von Dot-Verzeichnissen abhängt, wie Android App Links und Apple Universal Links, beschädigen.
+
+Beispiel für Break-Code:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Nach der Migration auf Express 5 wird eine Anfrage an `/.well-known/assetlinks.json` zu einem **404 Nicht Found** führen.
+
+Um dies zu beheben, geben Sie bestimmte dot-Verzeichnisse explizit mit der `dotfiles: "allow"` Option aus:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+Mit diesem Ansatz können Sie sicher nur die beabsichtigten dot-Verzeichnisse bedienen und gleichzeitig das standardmäßige sichere Verhalten für andere dotfiles beibehalten, die nicht zugänglich sind.
+
+### app.hören
+
+In Express 5 ruft die `app.listen` Methode die vom Benutzer zur Verfügung gestellte Callback-Funktion auf, wenn der Server ein Fehlerereignis erhält. In Express 4 würden solche Fehler aufgeworfen. Diese Änderung verlagert die Verantwortung für die Fehlerbehandlung auf die Callback-Funktion in Express 5. Wenn ein Fehler auftritt, wird er als Argument an den Callback übergeben.
+Zum Beispiel:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Listening auf ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+Das `app.router` Objekt, das in Express 4 entfernt wurde, hat ein Comeback in Express 5 gemacht. In der neuen Version ist dieses Objekt nur eine Referenz auf den Basis-Express-Router, im Gegensatz zu Express 3, wo eine App sie explizit laden musste.
+
+### req.body
+
+Die Eigenschaft `req.body` gibt `undefined` zurück, wenn der Body nicht analysiert wurde. In Express 4 gibt es standardmäßig `{}` zurück.
+
+### req.host
+
+In Express 4 hat die `req.host` Funktion die Portnummer falsch entfernt, wenn sie vorhanden war. In Express 5 wird die Portnummer beibehalten.
+
+### req.params
+
+Das `req.params` Objekt hat nun einen **null Prototyp** wenn man String Pfade benutzt. Wenn der Pfad jedoch mit einem regulären Ausdruck definiert ist, bleibt `req.params` ein Standardobjekt mit einem normalen Prototyp. Zusätzlich gibt es zwei wichtige Verhaltensänderungen:
+
+**Wildcard-Parameter sind jetzt Arrays:**
+
+Platzhalter (z.B. `/*splat`) erfassen Pfadsegmente als Array anstelle eines einzelnen Strings.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.arams);
+  // => [Objekt: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Unübereinstimmende Parameter werden weggelassen:**
+
+In Express 4 waren unpassende Platzhalter leere Zeichenketten (`''`) und optionale `:` Parameter (mit `?`) hatten einen Schlüssel mit dem Wert `undefiniert`. In Express 5 werden unübertroffene Parameter vollständig aus `req.params` entfernt.
+
+```js
+// v4: unerreichter Platzhalter ist leerer String
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.arams);
+  // => { '0': '' }
+});
+
+// v4: unübertroffener optionaler Parameter ist nicht definiert
+app.et('/:file.:ext?', (req, res) => {
+  // GET /image
+  Konsole.ir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{. ext}', (req, res) => {
+  // GET /image
+  console.dir(req.arams);
+  // => [Objekt: null prototype] { Datei: 'image' }
+});
+```
+
+### req.query
+
+Die Eigenschaft `req.query` ist keine beschreibbare Eigenschaft mehr und ist stattdessen ein Getter. Der Standard-Query-Parser wurde von "extended" auf "simple" geändert.
+
+### res.clearCookie
+
+Die Methode `res.clearCookie` ignoriert die vom Benutzer bereitgestellten `maxAge` und `expires` Optionen.
+
+### res.status
+
+Die `res.status` Methode akzeptiert nur ganze Zahlen im Bereich `100` bis `999`, gefolgt von dem von Knoten definierten Verhalten. , und gibt einen Fehler zurück, wenn der Statuscode keine Ganzzahl ist.
+
+### res.variieren
+
+Das `res.vary` wirft einen Fehler auf, wenn das `field` Argument fehlt. In Express 4, wenn das Argument weggelassen wurde, gab es eine Warnung in der Konsole
+
+## Verbesserungen
+
+### res.render()
+
+Diese Methode erzwingt jetzt asynchrones Verhalten für alle View Engines, Fehler zu vermeiden, die von View Engines verursacht wurden, die eine synchrone Implementierung hatten und die gegen die empfohlene Schnittstelle verstoßen.
+
+### Unterstützung für Brotli Kodierung
+
+Express 5 unterstützt die Kodierung von Brotli für Anfragen von Kunden, die es unterstützen.
diff --git a/src/content/pages/de/resources/glossary.mdx b/src/content/pages/de/resources/glossary.mdx
new file mode 100644
index 0000000000..90f7e204ad
--- /dev/null
+++ b/src/content/pages/de/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Ein umfassendes Glossar mit Begriffen, die sich auf Express.js, Node.js, Middleware, Routing und andere Schlüsselkonzepte beziehen, damit Sie Express verstehen und effektiv nutzen können.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### anwendung
+
+Im Allgemeinen ein oder mehrere Programme, die darauf ausgelegt sind, Operationen für einen bestimmten Zweck durchzuführen. Im Kontext von Express, ein Programm, das die Express-API verwendet, die auf der Node.js-Plattform läuft. Könnte auch auf ein [app object](/en/api#express).
+
+### API
+
+Programmierschnittstelle für Anwendungen. Sprich die Abkürzung aus, wenn sie zum ersten Mal verwendet wird.
+
+### Express
+
+Ein schnelles, unübersichtliches, minimalistisches Webframework für Node.js Anwendungen. Im Allgemeinen wird "Express" von "Express.js" bevorzugt, obwohl letztere akzeptabel ist.
+
+### libuv
+
+Eine mehrplattformunabhängige Unterstützungsbibliothek, die sich auf asynchrone I/O konzentriert, die hauptsächlich für den Einsatz durch Node.js entwickelt wurde.
+
+### Middleware
+
+Eine Funktion, die von der Express-Routing Layer vor dem letzten Request-Handler aufgerufen wird und sitzt somit in der Mitte zwischen einer Rohanforderung und der endgültigen geplanten Route. Ein paar schöne Terminologiepunkte rund um die Middleware:
+
+- `var foo = require('middleware')` heißt _requiring_ oder _using_ ein Node.js Modul. Dann gibt die Anweisung `var mw = foo()` typischerweise die Middleware zurück.
+- `app.use(mw)` heißt _adding the middleware to the global processing stack_.
+- `app.get('/foo', mw, function (req, res) { ... })` heißt _adding the middleware to the "GET /foo" processing stack_.
+
+### Node.js
+
+Eine Softwareplattform, die zur Erstellung skalierbarer Netzwerkanwendungen verwendet wird. Node.js verwendet JavaScript als Skriptsprache und erzielt einen hohen Durchsatz über nicht-blockierende I/O und eine einzige Threading-Ereignisschleife. Siehe [nodejs.org](https://nodejs.org/en/). **Verwende Notiz**: Anfangs "Node.js", danach "Knoten".
+
+### Open-Source, Open-Source
+
+Wenn als Adjektiv verwendet wird, Bindestrich; zum Beispiel: "Dies ist Open-Source-Software." Siehe [Open-Source-Software auf Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Obwohl es üblich ist, diesen Begriff nicht zu überschreiben, verwenden wir die üblichen englischen Regeln für
+und hyphenieren ein Compound Adjektiv.
+
+</Alert>
+
+### anfragen
+
+Eine HTTP-Anfrage. Ein Client sendet eine HTTP-Anfrage an einen Server, der eine Antwort zurückgibt. Die Anfrage muss eine von mehreren [Anfragemethoden](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) wie GET, POST usw. verwenden.
+
+### antwort
+
+Eine HTTP-Antwort. Ein Server gibt dem Client eine HTTP-Antwortmeldung zurück. Die Antwort enthält Vollständigkeitsinformationen über die Anfrage und kann auch angeforderte Inhalte in ihrem Nachrichtentext enthalten.
+
+### routen
+
+Teil einer URL, die eine Ressource identifiziert. In `http://foo.com/products/id`, zum Beispiel, ist "/products/id" die Route.
+
+### router
+
+Siehe [router](/en/api#router) in der API-Referenz.
diff --git a/src/content/pages/de/resources/utils.md b/src/content/pages/de/resources/utils.md
new file mode 100644
index 0000000000..adbeba1591
--- /dev/null
+++ b/src/content/pages/de/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Expresswerkzeuge
+description: Entdecken Sie die Utility-Module von Express.js und Node.js, einschließlich Tools für Cookies, CSRF-Schutz, URL-Parsing, Routing und vieles mehr, um Ihre Anwendungen zu verbessern.
+---
+
+## Express Utility-Funktionen
+
+Die [pillarjs](https://github.com/pillarjs) GitHub Organisation enthält eine Reihe von Modulen
+für Utility-Funktionen, die allgemein nützlich sein können.
+
+| Utility Module                                                 | Beschreibung                                                                                                                                                                                                   |
+| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Erhalten und setzen Sie HTTP(S)-Cookies, die signiert werden können, um Manipulationen mit Hilfe von Keygrip zu verhindern. Kann mit der Node.js HTTP-Bibliothek oder als Express Middleware verwendet werden. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Enthält die Logik hinter der Erstellung und Verifizierung von CSRF-Token. Verwenden Sie dieses Modul, um benutzerdefinierte CSRF Middleware zu erstellen.                                                      |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Funktion, die als letzter Schritt aufgerufen wird, um auf HTTP-Anfrage zu reagieren.                                                                                                                           |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Eine URL mit Cache analysieren.                                                                                                                                                                                |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Verwandeln Sie einen Express-Style Pfadstring wie \`\`/user/:name\` in einen regulären Ausdruck.                                                                                                               |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Behebt einen relativen Pfad gegen einen Wurzelpfad mit Validierung.                                                                                                                                            |
+| [router](https://www.npmjs.com/package/router)                 | Einfacher Middleware-Router.                                                                                                                                                                                   |
+| [send](https://www.npmjs.com/package/send)                     | Bibliothek zum Streamen von Dateien als HTTP-Antwort, mit Unterstützung für partielle Antworten (Bereiche), Konditional-GET-Verhandlung und granulare Ereignisse.                                              |
+
+Weitere HTTP-basierte Module finden Sie unter [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/de/support.md b/src/content/pages/de/support.md
new file mode 100644
index 0000000000..9fd687be5b
--- /dev/null
+++ b/src/content/pages/de/support.md
@@ -0,0 +1,23 @@
+---
+title: Versionsunterstützung
+description: Finden Sie Informationen über den Support-Zeitplan für verschiedene Express.js Versionen, einschließlich der aktuellen Versionen und der End-of-Life-Richtlinien.
+---
+
+Nur die neueste Version einer der wichtigsten Release-Zeilen wird unterstützt.
+
+Versionen, die EOL (Ende des Lebens) _may_ sind, erhalten Updates für kritische Sicherheitslücken, aber das Express-Team bietet keine Garantie und plant keine Korrekturen für festgestellte Probleme zu beheben oder zu veröffentlichen.
+
+| Hauptversion           | Minimale Node.js Version | Support-Startdatum | Support-Enddatum |
+| ---------------------- | ------------------------ | ------------------ | ---------------- |
+| [**v5.x**](/en/5x/api) | 18                       | September 2024     | **Laufend**      |
+| [**v4.x**](/en/4x/api) | 0.10.0                   | April 2014         | **Laufend**      |
+| [**v3.x**](/en/3x/api) | 0.8.0                    | Oktober 2012       | Juli 2015        |
+| [**v2.x**](/2x/)       | 0.4.1                    | März 2011          | Juli 2012        |
+| **v1.x**               | 0.2.0                    | Dezember 2010      | März 2011        |
+| **v0.14.x**            | 0.1.98                   | Dezember 2010      | Dezember 2010    |
+
+## Kommerzielle Support-Optionen
+
+Wenn Sie nicht in der Lage sind, auf eine unterstützte Version von Express zu aktualisieren, wenden Sie sich bitte an einen unserer Partner, um Sicherheitsaktualisierungen zu erhalten:
+
+- [HeroDevs unendlicher Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/en/advanced/best-practice-performance.md b/src/content/pages/en/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..a98c7fcf6a
--- /dev/null
+++ b/src/content/pages/en/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Production best practices: performance and reliability'
+description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
+---
+
+This article discusses performance and reliability best practices for Express applications deployed to production.
+
+This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
+
+- Things to do in your code (the dev part):
+  - [Use gzip compression](#use-gzip-compression)
+  - [Don't use synchronous functions](#dont-use-synchronous-functions)
+  - [Do logging correctly](#do-logging-correctly)
+  - [Handle exceptions properly](#handle-exceptions-properly)
+- Things to do in your environment / setup (the ops part):
+  - [Set NODE_ENV to "production"](#set-node_env-to-production)
+  - [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+  - [Run your app in a cluster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Use a load balancer](#use-a-load-balancer)
+  - [Use a reverse proxy](#use-a-reverse-proxy)
+
+## Things to do in your code
+
+Here are some things you can do in your code to improve your application's performance:
+
+- [Use gzip compression](#use-gzip-compression)
+- [Don't use synchronous functions](#dont-use-synchronous-functions)
+- [Do logging correctly](#do-logging-correctly)
+- [Handle exceptions properly](#handle-exceptions-properly)
+
+### Use gzip compression
+
+Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. For details on enabling gzip compression in Nginx, see [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) in the Nginx documentation.
+
+### Don't use synchronous functions
+
+Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
+
+Although Node and many modules provide synchronous and asynchronous versions of their functions, always use the asynchronous version in production. The only time when a synchronous function can be justified is upon initial startup.
+
+You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli#cli_trace_sync_io) for more information.
+
+### Do logging correctly
+
+In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
+
+#### For debugging
+
+If you're logging for purposes of debugging, then instead of using `console.log()`, use a special debugging module like [debug](https://www.npmjs.com/package/debug). This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
+
+#### For app activity
+
+If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
+
+### Handle exceptions properly
+
+Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
+
+To ensure you handle all exceptions, use the following techniques:
+
+- [Use try-catch](#use-try-catch)
+- [Use promises](#use-promises)
+
+Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
+
+For more on the fundamentals of error handling, see:
+
+- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Use try-catch
+
+Try-catch is a JavaScript language construct that you can use to catch exceptions in synchronous code. Use try-catch, for example, to handle JSON parsing errors as shown below.
+
+Here is an example of using try-catch to handle a potential process-crashing exception.
+This middleware function accepts a query field parameter named "params" that is a JSON object.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+However, try-catch works only for synchronous code. Because the Node platform is primarily asynchronous (particularly in a production environment), try-catch won't catch a lot of exceptions.
+
+#### Use promises
+
+When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+#### What not to do
+
+One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
+
+Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
+
+We also don't recommend using [domains](https://nodejs.org/api/domain). It generally doesn't solve the problem and is a deprecated module.
+
+## Things to do in your environment / setup
+
+Here are some things you can do in your system environment to improve your app's performance:
+
+- [Set NODE_ENV to "production"](#set-node_env-to-production)
+- [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+- [Run your app in a cluster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Use a load balancer](#use-a-load-balancer)
+- [Use a reverse proxy](#use-a-reverse-proxy)
+
+### Set NODE_ENV to "production"
+
+The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
+
+Setting NODE_ENV to "production" makes Express:
+
+- Cache view templates.
+- Cache CSS files generated from CSS extensions.
+- Generate less verbose error messages.
+
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
+
+If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
+
+In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
+
+With systemd, use the `Environment` directive in your unit file. For example:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Ensure your app automatically restarts
+
+In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
+
+- Using a process manager to restart the app (and Node) when it crashes.
+- Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
+
+Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
+
+#### Use a process manager
+
+In development, you started your app simply from the command line with `node server.js` or something similar. But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
+
+In addition to restarting your app when it crashes, a process manager can enable you to:
+
+- Gain insights into runtime performance and resource consumption.
+- Modify settings dynamically to improve performance.
+- Control clustering (pm2).
+
+Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
+
+#### Use an init system
+
+The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
+
+There are two ways to use init systems with your Express app:
+
+- Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
+- Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
+
+##### Systemd
+
+Systemd is a Linux system and service manager. Most major Linux distributions have adopted systemd as their default init system.
+
+A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Run your app in a cluster
+
+In a multi-core system, you can increase the performance of a Node app by many times by launching a cluster of processes. A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
+
+![Balancing between application instances using the cluster API](/images/clustering.png)
+
+IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
+
+In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
+
+#### Using Node's cluster module
+
+Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
+
+#### Using PM2
+
+If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
+
+When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
+
+To enable cluster mode, start your application like so:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
+
+Once running, the application can be scaled like so:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
+
+### Cache request results
+
+Another strategy to improve the performance in production is to cache the result of requests, so that your app does not repeat the operation to serve the same request repeatedly.
+
+Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
+
+### Use a load balancer
+
+No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
+
+A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Use a reverse proxy
+
+A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
+
+Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/src/content/pages/en/advanced/best-practice-security.mdx b/src/content/pages/en/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..5d109db145
--- /dev/null
+++ b/src/content/pages/en/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Production Best Practices: Security'
+description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
+
+Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see [Security
+Policies and Procedures](/en/resources/contributing#security-policies-and-procedures).
+
+</Alert>
+
+Security best practices for Express applications in production include:
+
+- [Production Best Practices: Security](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Use TLS](#use-tls)
+  - [Do not trust user input](#do-not-trust-user-input)
+    - [Prevent open redirects](#prevent-open-redirects)
+  - [Use Helmet](#use-helmet)
+  - [Reduce fingerprinting](#reduce-fingerprinting)
+  - [Use cookies securely](#use-cookies-securely)
+    - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
+    - [Set cookie security options](#set-cookie-security-options)
+  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+  - [Additional considerations](#additional-considerations)
+
+## Don't use deprecated or vulnerable versions of Express
+
+Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/en/guide/migrating-4) or consider [Commercial Support Options](/en/support#commercial-support-options).
+
+Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/en/advanced/security-updates). If you are, update to one of the stable releases, preferably the latest.
+
+## Use TLS
+
+If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## Do not trust user input
+
+For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
+Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
+
+### Prevent open redirects
+
+An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
+return a 3xx status.
+
+An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
+
+Here is an example of checking URLs before using `res.redirect` or `res.location`:
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.query.url).host !== 'example.com') {
+      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.status(400).end(`Invalid url: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Use Helmet
+
+[Helmet][helmet] can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
+
+Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
+
+- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
+- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
+- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
+- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
+- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
+- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
+- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
+- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
+- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
+- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
+- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
+
+Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
+
+Install Helmet like any other module:
+
+```bash
+$ npm install helmet
+```
+
+Then to use it in your code:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Reduce fingerprinting
+
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Though not a security issue itself,
+reducing the ability to fingerprint an application improves its overall security posture.
+Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
+the HTTP response headers.
+
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="info">
+
+Disabling the `X-Powered-By header` does not prevent a sophisticated attacker from determining
+that an app is running Express. It may discourage a casual exploit, but there are other ways to
+determine an app is running Express.
+
+</Alert>
+
+Express also sends its own formatted "404 Not Found" messages and formatter error
+response messages. These can be changed by
+[adding your own not found handler](/en/starter/faq#how-do-i-handle-404-responses)
+and
+[writing your own error handler](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+
+// custom error handler
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+## Use cookies securely
+
+To ensure cookies don't open your app to exploits, don't use the default session cookie name and set cookie security options appropriately.
+
+There are two main middleware cookie session modules:
+
+- [express-session](https://www.npmjs.com/package/express-session) that replaces `express.session` middleware built-in to Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
+
+The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
+
+In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
+
+### Don't use the default session cookie name
+
+Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
+
+To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.use(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Set cookie security options
+
+Set the following cookie options to enhance security:
+
+- `secure` - Ensures the browser only sends the cookie over HTTPS.
+- `httpOnly` - Ensures the cookie is sent only over HTTP(S), not client JavaScript, helping to protect against cross-site scripting attacks.
+- `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
+- `path` - indicates the path of the cookie; use it to compare against the request path. If this and domain match, then send the cookie in the request.
+- `expires` - use to set expiration date for persistent cookies.
+
+Here is an example using [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000); // 1 hour
+app.use(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      domain: 'example.com',
+      path: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## Prevent brute-force attacks against authorization
+
+Make sure login endpoints are protected to make private data more secure.
+
+A simple and powerful technique is to block authorization attempts using two metrics:
+
+1. The number of consecutive failed attempts by the same user name and IP address.
+1. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Ensure your dependencies are secure
+
+Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
+
+Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
+
+```bash
+$ npm audit
+```
+
+If you want to stay more secure, consider [Snyk](https://snyk.io/).
+
+Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Use this command to test your application for vulnerabilities:
+
+```bash
+$ snyk test
+```
+
+### Avoid other known vulnerabilities
+
+Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
+
+Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
+
+## Additional considerations
+
+Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
+
+- Always filter and sanitize user input to protect against cross-site scripting (XSS) and command injection attacks.
+- Defend against SQL injection attacks by using parameterized queries or prepared statements.
+- Use the open-source [sqlmap](http://sqlmap.org/) tool to detect SQL injection vulnerabilities in your app.
+- Use the [nmap](https://nmap.org/) and [sslyze](https://github.com/nabla-c0d3/sslyze) tools to test the configuration of your SSL ciphers, keys, and renegotiation as well as the validity of your certificate.
+- Use [safe-regex](https://www.npmjs.com/package/safe-regex) to ensure your regular expressions are not susceptible to [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacks.
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/en/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/en/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..c060e58605
--- /dev/null
+++ b/src/content/pages/en/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Health Checks and Graceful Shutdown
+description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
+---
+
+## Graceful shutdown
+
+When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+
+### Example
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Health checks
+
+A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, that determines when to restart a container.
+- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
diff --git a/src/content/pages/en/advanced/security-updates.mdx b/src/content/pages/en/advanced/security-updates.mdx
new file mode 100644
index 0000000000..3de8b46feb
--- /dev/null
+++ b/src/content/pages/en/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Security updates
+description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="alert">
+
+Node.js vulnerabilities directly affect Express. Therefore, [keep a watch on Node.js
+vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest
+stable version of Node.js.
+
+</Alert>
+
+The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see [Security
+Policies and Procedures](/en/resources/contributing#security-policies-and-procedures).
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+- 4.20.0
+  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+- 4.19.0, 4.19.1
+  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
+  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
+- 4.15.5
+  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
+  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
+- 4.15.2
+  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
+- 4.11.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 4.10.7
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Fixed directory traversal vulnerabilities in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 4.8.0
+  - Sparse arrays that have extremely high indexes in the query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+
+## 3.x
+
+  <Alert type="warning">
+**Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
+
+Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 3.19.0
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Fixed directory traversal vulnerabilities in `express.static`.
+- 3.16.6
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 3.16.0
+  - Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+- 3.3.0
+  - The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
diff --git a/src/content/pages/en/guide/database-integration.mdx b/src/content/pages/en/guide/database-integration.mdx
new file mode 100644
index 0000000000..b0855e4a2a
--- /dev/null
+++ b/src/content/pages/en/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Database integration
+description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="alert">
+
+These database drivers are among many that are available. For other options, search on the
+[npm](https://www.npmjs.com/) site.
+
+</Alert>
+
+## Cassandra
+
+**Module**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installation
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Example
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.execute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Module**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Installation
+
+```bash
+$ npm install couchbase
+```
+
+### Example
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// add a document to a bucket
+bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+
+// get all documents with shoe size 13
+const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery.fromString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Module**: [nano](https://github.com/dscape/nano)
+
+### Installation
+
+```bash
+$ npm install nano
+```
+
+### Example
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.use('books');
+
+// Insert a book document in the books database
+books.insert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body);
+  }
+});
+
+// Get a list of all books
+books.list((err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Module**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Installation
+
+```bash
+$ npm install level levelup leveldown
+```
+
+### Example
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.put('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.get('name', (err, value) => {
+    if (err) return console.log('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Module**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Installation
+
+```bash
+$ npm install mysql
+```
+
+### Example
+
+```js
+const mysql = require('mysql');
+const connection = mysql.createConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connection.connect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.log('The solution is: ', rows[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Module**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installation
+
+```bash
+$ npm install mongodb
+```
+
+### Example (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+### Example (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.db('animals');
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+If you want an object model driver for MongoDB, look at [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installation
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Example
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .run('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].get('count'));
+    })
+    .catch((error) => {
+      console.log(error);
+    });
+});
+```
+
+## Oracle
+
+**Module**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installation
+
+NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Example
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb.getConnection(config);
+
+    const result = await conn.execute('select * from employees where employee_id = :id', [empId]);
+
+    console.log(result.rows[0]);
+  } catch (err) {
+    console.log('Ouch!', err);
+  } finally {
+    if (conn) {
+      // conn assignment worked, need to close
+      await conn.close();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installation
+
+```bash
+$ npm install pg-promise
+```
+
+### Example
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .then((data) => {
+    console.log('DATA:', data.value);
+  })
+  .catch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Module**: [redis](https://github.com/mranney/node_redis)
+
+### Installation
+
+```bash
+$ npm install redis
+```
+
+### Example
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.set('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.hkeys('hash key', (err, replies) => {
+  console.log(`${replies.length} replies:`);
+
+  replies.forEach((reply, i) => {
+    console.log(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL Server
+
+**Module**: [tedious](https://github.com/tediousjs/tedious)
+
+### Installation
+
+```bash
+$ npm install tedious
+```
+
+### Example
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious').Request;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // update me
+      password: 'your_password', // update me
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection.on('connect', (err) => {
+  if (err) {
+    console.log(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hello world'", (err, rowCount) => {
+    if (err) {
+      console.log(err);
+    } else {
+      console.log(`${rowCount} rows`);
+    }
+    connection.close();
+  });
+
+  request.on('row', (columns) => {
+    columns.forEach((column) => {
+      if (column.value === null) {
+        console.log('NULL');
+      } else {
+        console.log(column.value);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Module**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installation
+
+```bash
+$ npm install sqlite3
+```
+
+### Example
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.run('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.prepare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.run(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.log(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Module**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installation
+
+```bash
+$ npm install elasticsearch
+```
+
+### Example
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .search({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          fields: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .then(
+    (response) => {
+      const hits = response.hits.hits;
+    },
+    (error) => {
+      console.trace(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/en/guide/migrating-4.mdx b/src/content/pages/en/guide/migrating-4.mdx
new file mode 100644
index 0000000000..42a1b63163
--- /dev/null
+++ b/src/content/pages/en/guide/migrating-4.mdx
@@ -0,0 +1,662 @@
+---
+title: Moving to Express 4
+description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 is a breaking change from Express 3. That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
+
+This article covers:
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Changes in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Upgrading to the Express 4 app generator</a>.
+  </li>
+</ul>
+
+## Changes in Express 4
+
+There are several significant changes in Express 4:
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on
+    Connect and built-in middleware were removed, so you must add middleware yourself.
+  </li>
+  <li>
+    <a href="#routing">Changes to the routing system.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Various other changes.</a>
+  </li>
+</ul>
+
+See also:
+
+- [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Changes to Express core and middleware system
+
+Express 4 no longer depends on Connect, and removes all built-in
+middleware from its core, except for the `express.static` function. This means that
+Express is now an independent routing and middleware web framework, and
+Express versioning and releases are not affected by middleware updates.
+
+Without built-in middleware, you must explicitly add all the
+middleware that is required to run your app. Simply follow these steps:
+
+1. Install the module: `npm install --save <module-name>`
+2. In your app, require the module: `require('module-name')`
+3. Use the module according to its documentation: `app.use( ... )`
+
+The following table lists Express 3 middleware and their counterparts in Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compression</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">cookie-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">cookie-parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">response-time</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">method-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">connect-timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">serve-static</a>
+    </td>
+  </tr>
+</table>
+
+Here is the [complete list](https://github.com/senchalabs/connect#middleware) of Express 4 middleware.
+
+In most cases, you can simply replace the old version 3 middleware with
+its Express 4 counterpart. For details, see the module documentation in
+GitHub.
+
+#### `app.use` accepts parameters
+
+In version 4 you can use a variable parameter to define the path where middleware functions are loaded, then read the value of the parameter from the route handler.
+For example:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### The routing system
+
+Apps now implicitly load routing middleware, so you no longer have to
+worry about the order in which middleware is loaded with respect to
+the `router` middleware.
+
+The way you define routes is unchanged, but the routing system has two
+new features to help organize your routes:
+
+- A new method, `app.route()`, to create chainable route handlers for a route path.
+- A new class, `express.Router`, to create modular mountable route handlers.
+
+#### `app.route()` method
+
+The new `app.route()` method enables you to create chainable route handlers
+for a route path. Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
+information about routes, see [`Router()` documentation](/en/4x/api#router).
+
+Here is an example of chained route handlers that are defined by using the `app.route()` function.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+#### `express.Router` class
+
+The other feature that helps to organize routes is a new class,
+`express.Router`, that you can use to create modular mountable
+route handlers. A `Router` instance is a complete middleware and
+routing system; for this reason it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads middleware in
+it, defines some routes, and mounts it on a path on the main app.
+
+For example, create a router file named `birds.js` in the app directory,
+with the following content:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specific to this router
+router.use((req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+});
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to the `/birds` and
+`/birds/about` paths, and will call the `timeLog`
+middleware that is specific to the route.
+
+### Other changes
+
+The following table lists other small but important changes in Express 4:
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Object</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>Express 4 requires Node.js 0.10.x or later and has dropped support for Node.js 0.8.x.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      The `http` module is no longer needed, unless you need to directly work with it
+      (socket.io/SPDY/HTTPS). The app can be started by using the `app.listen()` function.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      The `app.configure()` function has been removed. Use the `process.env.NODE_ENV` or
+      `app.get('env')` function to detect the environment and configure the app accordingly.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      The `json spaces` application property is disabled by default in Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Use `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, and
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">No longer resolves relative URLs.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">Was an array; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Was a function; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Changed to `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Now available as `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      Functionality is now limited to setting the basic cookie value. Use `res.cookie()` for added
+      functionality.
+    </td>
+  </tr>
+</table>
+
+## Example app migration
+
+Here is an example of migrating an Express 3 application to Express 4.
+The files of interest are `app.js` and `package.json`.
+
+### Version 3 app
+
+#### `app.js`
+
+Consider an Express v.3 application with the following `app.js` file:
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.session({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.static(path.join(__dirname, 'public')));
+
+// development only
+if (app.get('env') === 'development') {
+  app.use(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.createServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+The accompanying version 3 `package.json` file might look
+something like this:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "express": "3.12.0",
+    "pug": "*"
+  }
+}
+```
+
+### Process
+
+Begin the migration process by installing the required middleware for the
+Express 4 app and updating Express and Pug to their respective latest
+version with the following command:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Make the following changes to `app.js`:
+
+1. The built-in Express middleware functions `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` and
+   `express.errorHandler` are no longer available on the
+   `express` object. You must install their alternatives
+   manually and load them in the app.
+
+2. You no longer need to load the `app.router` function.
+   It is not a valid Express 4 app object, so remove the
+   `app.use(app.router);` code.
+
+3. Make sure that the middleware functions are loaded in the correct order - load `errorHandler` after loading the app routes.
+
+### Version 4 app
+
+#### `package.json`
+
+Running the above `npm` command will update `package.json` as follows:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1.1",
+    "express": "^4.8.0",
+    "express-session": "^1.7.2",
+    "pug": "^2.0.0",
+    "method-override": "^2.1.2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1.3",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Then, remove invalid code, load the required middleware, and make other
+changes as necessary. The `app.js` file will look like this:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.use(methodOverride());
+app.use(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app.use(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+// error handling middleware should be loaded after the loading the routes
+if (app.get('env') === 'development') {
+  app.use(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+Unless you need to work directly with the `http` module (socket.io/SPDY/HTTPS), loading it is not required, and the app can be simply started this way:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Run the app
+
+The migration process is complete, and the app is now an
+Express 4 app. To confirm, start the app by using the following command:
+
+```bash
+$ node .
+```
+
+Load [http://localhost:3000](http://localhost:3000)
+and see the home page being rendered by Express 4.
+
+## Upgrading to the Express 4 app generator
+
+The command-line tool to generate an Express app is still
+`express`, but to upgrade to the new version, you must uninstall
+the Express 3 app generator and then install the new
+`express-generator`.
+
+### Installing
+
+If you already have the Express 3 app generator installed on your system,
+you must uninstall it:
+
+```bash
+$ npm uninstall -g express
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now install the new generator:
+
+```bash
+$ npm install -g express-generator
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now the `express` command on your system is updated to the
+Express 4 generator.
+
+### Changes to the app generator
+
+Command options and use largely remain the same, with the following exceptions:
+
+- Removed the `--sessions` option.
+- Removed the `--jshtml` option.
+- Added the `--hogan` option to support [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Example
+
+Execute the following command to create an Express 4 app:
+
+```bash
+$ express app4
+```
+
+If you look at the contents of the `app4/app.js` file, you will notice
+that all the middleware functions (except `express.static`) that are required for
+the app are loaded as independent modules, and the `router` middleware
+is no longer explicitly loaded in the app.
+
+You will also notice that the `app.js` file is now a Node.js module, in contrast to the standalone app that was generated by the old generator.
+
+After installing the dependencies, start the app by using the following command:
+
+```bash
+$ npm start
+```
+
+If you look at the `npm start` script in the `package.json` file,
+you will notice that the actual command that starts the app is
+`node ./bin/www`, which used to be `node app.js`
+in Express 3.
+
+Because the `app.js` file that was generated by the Express 4 generator
+is now a Node.js module, it can no longer be started independently as an app
+(unless you modify the code). The module must be loaded in a Node.js file
+and started via the Node.js file. The Node.js file is `./bin/www`
+in this case.
+
+Neither the `bin` directory nor the extensionless `www`
+file is mandatory for creating an Express app or starting the app. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+To get rid of the `www` directory and keep things the "Express 3 way",
+delete the line that says `module.exports = app;` at the end of the
+`app.js` file, then paste the following code in its place:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+Ensure that you load the `debug` module at the top of the `app.js` file by using the following code:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Next, change `"start": "node ./bin/www"` in the `package.json` file to `"start": "node app.js"`.
+
+You have now moved the functionality of `./bin/www` back to
+`app.js`. This change is not recommended, but the exercise helps you
+to understand how the `./bin/www` file works, and why the `app.js` file
+no longer starts on its own.
diff --git a/src/content/pages/en/guide/migrating-5.mdx b/src/content/pages/en/guide/migrating-5.mdx
new file mode 100644
index 0000000000..b93cec072c
--- /dev/null
+++ b/src/content/pages/en/guide/migrating-5.mdx
@@ -0,0 +1,584 @@
+---
+title: Upgrade to Express v5
+description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 is not very different from Express 4; although it maintains the same basic API, there are still changes that break compatibility with the previous version. Therefore, an application built with Express 4 might not work if you update it to use Express 5.
+
+## Installation
+
+To install this version, you need to have a **Node.js version 18 or higher**. Then, execute the following command in your application directory:
+
+```sh
+npm install "express@5"
+```
+
+You can then run your automated tests to see what fails, and fix problems according to the updates listed below. After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
+
+## Express 5 Codemods
+
+To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
+
+Run the following command for run all the codemods available:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+If you want to run a specific codemod, you can run the following command:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+You can find the list of available codemods [here](https://codemod.link/express).
+
+## Removed methods and properties
+
+If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
+
+### app.del()
+
+Express 5 no longer supports the `app.del()` function. If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
+
+Initially, `del` was used instead of `delete`, because `delete` is a reserved keyword in JavaScript. However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+Or you can update your code manually:
+
+```diff
+-app.del('/user/:id', (req, res) => {
++app.delete('/user/:id', (req, res) => {
+   res.send(`DELETE /user/${req.params.id}`);
+ });
+```
+
+### app.param(fn)
+
+The `app.param(fn)` signature was used for modifying the behavior of the `app.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### Pluralized method names
+
+The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
+
+`req.acceptsCharset()` is replaced by `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` is replaced by `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` is replaced by `req.acceptsLanguages()`.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+Or you can update your code manually:
+
+```diff
+ app.all('/', (req, res) => {
+-  req.acceptsCharset('utf-8');
+-  req.acceptsEncoding('br');
+-  req.acceptsLanguage('en');
++  req.acceptsCharsets('utf-8');
++  req.acceptsEncodings('br');
++  req.acceptsLanguages('en');
+
+   // ...
+ });
+```
+
+### Leading colon (:) in the name for app.param(name, fn)
+
+A leading colon character (:) in the name for the `app.param(name, fn)` function is a remnant of Express 3, and for the sake of backwards compatibility, Express 4 supported it with a deprecation notice. Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
+
+This should not affect your code if you follow the Express 4 documentation of [app.param](/en/4x/api#app.param), as it makes no mention of the leading colon.
+
+### req.param(name)
+
+This potentially confusing and dangerous method of retrieving form data has been removed. You will now need to specifically look for the submitted parameter name in the `req.params`, `req.body`, or `req.query` object.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+Or you can update your code manually:
+
+```diff
+ app.post('/user', (req, res) => {
+-  const id = req.param('id');
+-  const body = req.param('body');
+-  const query = req.param('query');
++  const id = req.params.id;
++  const body = req.body;
++  const query = req.query;
+
+   // ...
+ });
+```
+
+### res.json(obj, status)
+
+Express 5 no longer supports the signature `res.json(obj, status)`. Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/status-send-order
+```
+
+Or you can update your code manually:
+
+```diff
+ app.post('/user', (req, res) => {
+-  res.json({ name: 'Ruben' }, 201);
++  res.status(201).json({ name: 'Ruben' });
+ });
+```
+
+### res.jsonp(obj, status)
+
+Express 5 no longer supports the signature `res.jsonp(obj, status)`. Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/status-send-order
+```
+
+Or you can update your code manually:
+
+```diff
+ app.post('/user', (req, res) => {
+-  res.jsonp({ name: 'Ruben' }, 201);
++  res.status(201).jsonp({ name: 'Ruben' });
+ });
+```
+
+### res.redirect(url, status)
+
+Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+Or you can update your code manually:
+
+```diff
+ app.get('/user', (req, res) => {
+-  res.redirect('/users', 301);
++  res.redirect(301, '/users');
+ });
+```
+
+### res.redirect('back') and res.location('back')
+
+Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+Or you can update your code manually:
+
+```diff
+ app.get('/user', (req, res) => {
+-  res.redirect('back');
++  res.redirect(req.get('Referrer') || '/');
+ });
+```
+
+### res.send(body, status)
+
+Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/status-send-order
+```
+
+Or you can update your code manually:
+
+```diff
+ app.get('/user', (req, res) => {
+-  res.send({ name: 'Ruben' }, 200);
++  res.status(200).send({ name: 'Ruben' });
+ });
+```
+
+### res.send(status)
+
+Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
+If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/status-send-order
+```
+
+Or you can update your code manually:
+
+```diff
+ app.get('/user', (req, res) => {
+-  res.send(200);
++  res.sendStatus(200);
+ });
+```
+
+### res.sendfile()
+
+The `res.sendfile()` function has been replaced by a camel-cased version `res.sendFile()` in Express 5.
+
+#### How to update
+
+You can automatically update your code by running the following command:
+
+```sh
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+Or you can update your code manually:
+
+```diff
+ app.get('/user', (req, res) => {
+-  res.sendfile('/path/to/file');
++  res.sendFile('/path/to/file');
+ });
+```
+
+### res.sendFile() options
+
+The `hidden` and `from` options for `res.sendFile()` are no longer supported. Use `dotfiles` and `root` instead.
+
+#### How to update
+
+```diff
+ app.get('/files/:name', (req, res) => {
+-  res.sendFile(req.params.name, { hidden: true, from: '/uploads' });
++  res.sendFile(req.params.name, { dotfiles: 'allow', root: '/uploads' });
+ });
+```
+
+### express.static() options
+
+The `hidden` and `from` options for `express.static()` are no longer supported. Use `dotfiles` and `root` instead. Note that `from` was never documented in the API but was accepted as an alias for `root`. The default value of `dotfiles` is now `"ignore"`.
+
+#### How to update
+
+```diff
+ const express = require('express');
+ const app = express();
+
+-app.use(express.static('public', { hidden: true }));
++app.use(express.static('public', { dotfiles: 'allow' }));
+```
+
+### router.param(fn)
+
+The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### express.static.mime
+
+In Express 5, `mime` is no longer an exported property of the `static` field.
+Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
+
+#### How to update
+
+```diff
+-express.static.mime.lookup('json');
++const mime = require('mime-types');
++mime.lookup('json');
+```
+
+### MIME type changes
+
+Several MIME types have changed due to updates in [`mime-db`](https://github.com/jshttp/mime-db). These changes only affect `express.static()` and `res.sendFile()`. For a full list of changes, see the [`mime-db` changelog](https://github.com/jshttp/mime-db/blob/HEAD/HISTORY.md).
+
+Express 4 uses `mime-db` version **1.52.0**, while Express 5 uses newer versions that reflect updates to IANA and other MIME type specifications. The most notable change is that JavaScript files (`.js`) are now served as `text/javascript` instead of `application/javascript`.
+
+In Express 5, changes to MIME types from `mime-db` updates are not considered breaking changes, so be careful when updating your dependencies as MIME types may change between minor or patch versions.
+
+### express:router debug logs
+
+Router handling logic is now performed by a separate dependency ([`router`](https://github.com/pillarjs/router)) maintained by the Express team, so debug logs have moved to a different namespace. Before Express 5.1, these debug logs did not exist. To get them, update to a recent Express 5 version or update the `router` package in your `package-lock.json`:
+
+| v4                         | v5                                  |
+| -------------------------- | ----------------------------------- |
+| `express:router`           | `router`                            |
+| `express:router:layer`     | `router:layer`                      |
+| `express:router:route`     | `router:route`                      |
+| `express:*` (includes all) | `express:*` + `router` + `router:*` |
+
+#### How to update
+
+```diff
+-DEBUG=express:* node index.js
++DEBUG=express:*,router,router:* node index.js
+```
+
+## Changed
+
+These APIs still exist but their behavior has changed. Review these changes to make sure your app works as expected.
+
+### Path route matching syntax
+
+Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
+
+- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
+
+  ```diff
+  -app.get('/*', async (req, res) => {
+  +app.get('/*splat', async (req, res) => {
+     res.send('ok');
+   });
+  ```
+
+    <Alert type="info">
+
+  `*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
+
+  ```js
+  app.get('/{*splat}', async (req, res) => {
+    res.send('ok');
+  });
+  ```
+
+    </Alert>
+
+- The optional character `?` is no longer supported, use braces instead.
+
+  ```diff
+  -app.get('/:file.:ext?', async (req, res) => {
+  +app.get('/:file{.:ext}', async (req, res) => {
+     res.send('ok');
+   });
+  ```
+
+- Regexp characters are not supported. For example:
+
+  ```diff
+  -app.get('/[discussion|page]/:slug', async (req, res) => {
+  +app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+     res.status(200).send('ok');
+   });
+  ```
+
+- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
+- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
+
+### Rejected promises handled from middleware and handlers
+
+Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
+
+Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling).
+
+#### How to update
+
+You can now use `async/await` directly without manually catching errors. If `getUserById` throws an error or rejects, `next` will be called automatically with the rejected value.
+
+```diff
+-app.get('/user/:id', (req, res, next) => {
+-  getUserById(req.params.id)
+-    .then((user) => res.send(user))
+-    .catch(next);
+-});
++app.get('/user/:id', async (req, res) => {
++  const user = await getUserById(req.params.id);
++  res.send(user);
++});
+```
+
+### express.urlencoded
+
+The `express.urlencoded` method makes the `extended` option `false` by default.
+
+#### How to update
+
+If your application relies on the `extended` behavior, explicitly set it to `true`:
+
+```diff
+-app.use(express.urlencoded());
++app.use(express.urlencoded({ extended: true }));
+```
+
+### express.static dotfiles
+
+The `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. In Express 4, dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links and Apple Universal Links.
+
+#### How to update
+
+Serve specific dot-directories explicitly using the `dotfiles: "allow"` option. This allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles.
+
+```diff
++app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+ app.use(express.static('public'));
+```
+
+### app.listen
+
+In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
+For example:
+
+```js ins={2-4}
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Listening on ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+The `app.router` object, which was removed in Express 4, has made a comeback in Express 5. In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
+
+### req.body
+
+The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
+
+```js del={4} ins={6}
+app.post('/user', (req, res) => {
+  console.dir(req.body);
+  // Express 4
+  // => {}
+  // Express 5
+  // => undefined
+});
+```
+
+### req.host
+
+In Express 4, the `req.host` function incorrectly stripped off the port number if it was present. In Express 5, the port number is maintained.
+
+### req.params
+
+The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
+
+**Wildcard parameters are now arrays:**
+
+Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.params);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Unmatched parameters are omitted:**
+
+In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
+
+```diff
+-// v4: unmatched wildcard is empty string
+-app.get('/*', (req, res) => {
+-  // GET /
+-  console.dir(req.params);
+-  // => { '0': '' }
+-});
+-
+-// v4: unmatched optional param is undefined
+-app.get('/:file.:ext?', (req, res) => {
+-  // GET /image
+-  console.dir(req.params);
+-  // => { file: 'image', ext: undefined }
+-});
+-
++// v5: unmatched optional param is omitted
++app.get('/:file{.:ext}', (req, res) => {
++  // GET /image
++  console.dir(req.params);
++  // => [Object: null prototype] { file: 'image' }
++});
+```
+
+### req.query
+
+The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
+
+```js del={3}
+app.get('/search', (req, res) => {
+  // This is no longer possible in Express 5
+  req.query.page = 1;
+});
+```
+
+### res.clearCookie
+
+The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
+
+```diff
+ app.get('/logout', (req, res) => {
+-  res.clearCookie('session', { maxAge: 0, expires: new Date(0) });
++  res.clearCookie('session');
+ });
+```
+
+### res.status
+
+The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
+
+```js del={2}
+app.get('/user', (req, res) => {
+  res.status(99); // Throws an error
+  res.status(200); // OK
+});
+```
+
+### res.vary
+
+The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console.
+
+```js del={2}
+app.get('/user', (req, res) => {
+  res.vary(); // Throws an error
+  res.vary('Accept'); // OK
+});
+```
+
+## Improvements
+
+These changes don't require any migration steps, but are worth knowing about when upgrading.
+
+### res.render()
+
+This method now enforces asynchronous behavior for all view engines, avoiding bugs caused by view engines that had a synchronous implementation and that violated the recommended interface.
+
+### Brotli encoding support
+
+Middleware like `express.json()`, `express.urlencoded()`, `express.text()`, and `express.raw()` now support Brotli (`Content-Encoding: br`) decompression for incoming request bodies, in addition to `gzip` and `deflate`.
diff --git a/src/content/pages/en/resources/community.mdx b/src/content/pages/en/resources/community.mdx
new file mode 100755
index 0000000000..66dcc87da4
--- /dev/null
+++ b/src/content/pages/en/resources/community.mdx
@@ -0,0 +1,92 @@
+---
+title: Community
+description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
+---
+
+import LogoDisplay from '@components/patterns/LogoDisplay/LogoDisplay.astro';
+
+## Technical committee
+
+The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
+and other issues relevant to the Express project. Each meeting is typically announced in an
+[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
+open to all observers.
+
+The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
+
+Members of the Express technical committee are:
+
+**Active:**
+
+- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
+- [@crandmck](https://github.com/crandmck) - Rand McKinney
+- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
+- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
+- [@sheplu](https://github.com/sheplu) - Jean Burellier
+- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
+- [@jonchurch](https://github.com/jonchurch) - Jon Church
+- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
+
+**Inactive:**
+
+- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
+- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
+- [@jonathanong](https://github.com/jonathanong) - jongleberry
+- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
+- [@troygoode](https://github.com/troygoode) - Troy Goode
+
+## Express is made of many modules
+
+Our vibrant community has created a large variety of extensions,
+[middleware modules](/en/resources/middleware) and higher-level frameworks.
+
+Additionally, the Express community maintains modules in these two GitHub orgs:
+
+- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/en/resources/utils).
+- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
+
+To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
+
+## Issues
+
+If you've come across what you think is a bug, or just want to make
+a feature request open a ticket in the [issue queue](https://github.com/expressjs/express/issues).
+
+## Examples
+
+View dozens of Express application [examples](https://github.com/expressjs/express/tree/master/examples)
+in the repository covering everything from API design and authentication to template engine integration.
+
+## Github Discussions
+
+The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
+
+## Express.js Logo
+
+Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
+
+### Wordmark
+
+<LogoDisplay
+  darkSrc="/images/logos/logo-express-black.svg"
+  lightSrc="/images/logos/logo-express-white.svg"
+  alt="Express.js wordmark"
+/>
+
+### Glyph
+
+<LogoDisplay
+  darkSrc="/images/logos/logo-white.svg"
+  lightSrc="/images/logos/logo-dark.svg"
+  alt="Express.js glyph"
+/>
+
+### Kawaii
+
+This logo was created by [SAWARATSUKI](https://github.com/SAWARATSUKI).
+
+<LogoDisplay
+  darkSrc="/images/logos/express-kawaii.webp"
+  lightSrc="/images/logos/express-kawaii.webp"
+  alt="Express.js kawaii logo"
+/>
diff --git a/src/content/pages/en/resources/contributing.mdx b/src/content/pages/en/resources/contributing.mdx
new file mode 100644
index 0000000000..07fa774af8
--- /dev/null
+++ b/src/content/pages/en/resources/contributing.mdx
@@ -0,0 +1,378 @@
+---
+title: Contributing to Express
+description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express is an [OpenJS Foundation](https://openjsf.org/) project spread across three GitHub organizations: [expressjs](https://github.com/expressjs), [pillarjs](https://github.com/pillarjs), and [jshttp](https://github.com/jshttp). All contributions are welcome, whether it's reporting bugs, improving documentation, or submitting code. The guidelines below describe how the project operates and how you can get involved.
+
+## Technical committee
+
+The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](/en/resources/community/#technical-committee).
+
+## Community contributing guide
+
+{/* SRC: expressjs/discussions docs/GOVERNANCE.md */}
+
+The goal of this document is to create a contribution process that:
+
+- Encourages new contributions.
+- Encourages contributors to remain involved.
+- Avoids unnecessary processes and bureaucracy whenever possible.
+- Creates a transparent decision making process that makes it clear how
+  contributors can be involved in decision making.
+
+### Vocabulary
+
+- A **Contributor** is any individual creating or commenting on an issue or pull request.
+- A **Committer** is a subset of contributors who have been given write access to the repository.
+- A **Project Captain** is the lead maintainer of a repository.
+- A **TC (Technical Committee)** is a group of committers representing the required technical
+  expertise to resolve rare disputes.
+- A **Triager** is a subset of contributors who have been given triage access to the repository.
+
+### Logging Issues
+
+Log an issue for any question or problem you might have. When in doubt, log an issue, and
+any additional policies about what to include will be provided in the responses. The only
+exception is security disclosures which should be sent privately.
+
+Committers may direct you to another repository, ask for additional clarifications, and
+add appropriate metadata before the issue is addressed.
+
+Please be courteous and respectful. Every participant is expected to follow the
+project's Code of Conduct.
+
+### Contributions
+
+Any change to resources in this repository must be through pull requests. This applies to all changes
+to documentation, code, binary files, etc. Even long term committers and TC members must use
+pull requests.
+
+No pull request can be merged without being reviewed.
+
+For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
+contributors in other timezones have time to review. Consideration should also be given to
+weekends and other holiday periods to ensure active committers all have reasonable time to
+become involved in the discussion and review process if they wish.
+
+The default for each contribution is that it is accepted once no committer has an objection.
+During a review, committers may also request that a specific contributor who is most versed in a
+particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
+process for contributions to land. Once all issues brought by committers are addressed it can
+be landed by any committer.
+
+In the case of an objection being raised in a pull request by another committer, all involved
+committers should seek to arrive at a consensus by way of addressing concerns being expressed
+by discussion, compromise on the proposed change, or withdrawal of the proposed change.
+
+If a contribution is controversial and committers cannot agree about how to get it to land
+or if it should land then it should be escalated to the TC. TC members should regularly
+discuss pending contributions in order to find a resolution. It is expected that only a
+small minority of issues be brought to the TC for resolution and that discussion and
+compromise among committers be the default resolution mechanism.
+
+### Becoming a Triager
+
+Anyone can become a triager! Read more about the process of being a triager in
+[the triage process document](https://github.com/expressjs/discussions/blob/HEAD/Triager-Guide.md).
+
+Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
+a new triager. If you are interested in becoming a triager, our best advice is to actively participate
+in the community by helping triaging issues and pull requests. As well we recommend
+to engage in other community activities like attending the TC meetings, and participating in the Slack
+discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
+be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
+
+You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
+if you have questions or need guidance.
+
+### Becoming a Committer
+
+All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
+and added as a committer, and be given write access to the repository.
+
+Committers are expected to follow this policy and continue to send pull requests, go through
+proper review, and have other committers merge their pull requests.
+
+### TC Process
+
+The TC uses a "consensus seeking" process for issues that are escalated to the TC.
+The group tries to find a resolution that has no open objections among TC members.
+If a consensus cannot be reached that has no objections then a majority wins vote
+is called. It is also expected that the majority of decisions made by the TC are via
+a consensus seeking process and that voting is only used as a last-resort.
+
+Resolution may involve returning the issue to project captains with suggestions on
+how to move forward towards a consensus. It is not expected that a meeting of the TC
+will resolve all issues on its agenda during that meeting and may prefer to continue
+the discussion happening among the project captains.
+
+Members can be added to the TC at any time. Any TC member can nominate another committer
+to the TC and the TC uses its standard consensus seeking process to evaluate whether or
+not to add this new member. The TC will consist of a minimum of 3 active members and a
+maximum of 10. If the TC should drop below 5 members the active TC members should nominate
+someone new. If a TC member is stepping down, they are encouraged (but not required) to
+nominate someone to take their place.
+
+TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
+necessary to be effective in the role.
+
+To remain "active" a TC member should have participation within the last 12 months and miss
+no more than six consecutive TC meetings. Our goal is to increase participation, not punish
+people for any lack of participation, this guideline should be only be used as such
+(replace an inactive member with a new active one, for example). Members who do not meet this
+are expected to step down. If A TC member does not step down, an issue can be opened in the
+discussions repo to move them to inactive status. TC members who step down or are removed due
+to inactivity will be moved into inactive status.
+
+Inactive status members can become active members by self nomination if the TC is not already
+larger than the maximum of 10. They will also be given preference if, while at max size, an
+active member steps down.
+
+### Project Captains
+
+The Express TC can designate captains for individual projects/repos in the
+organizations. These captains are responsible for being the primary
+day-to-day maintainers of the repo on a technical and community front.
+Repo captains are empowered with repo ownership and package publication rights.
+When there are conflicts, especially on topics that effect the Express project
+at large, captains are responsible to raise it up to the TC and drive
+those conflicts to resolution. Captains are also responsible for making sure
+community members follow the community guidelines, maintaining the repo
+and the published package, as well as in providing user support.
+
+Like TC members, Repo captains are a subset of committers.
+
+To become a captain for a project the candidate is expected to participate in that
+project for at least 6 months as a committer prior to the request. They should have
+helped with code contributions as well as triaging issues. They are also required to
+have 2FA enabled on both their GitHub and npm accounts.
+
+Any TC member or an existing captain on the **same** repo can nominate another committer
+to the captain role. To do so, they should submit a PR to this document, updating the
+**Active Project Captains** section (while maintaining the sort order) with the project
+name, the nominee's GitHub handle, and their npm username (if different).
+
+- Repos can have as many captains as make sense for the scope of work.
+- A TC member or an existing repo captain **on the same project** can nominate a new captain.
+  Repo captains from other projects should not nominate captains for a different project.
+
+The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
+for comment and/or dissent. When the PR is merged, a TC member will add them to the
+proper GitHub/npm groups.
+
+#### Active Projects and Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
+
+#### Current Initiative Captains
+
+The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
+
+### Inactivity and Emeritus Policy for Any Role
+
+To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
+
+Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
+
+#### Exceptions
+
+Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
+
+#### Inactivity Process
+
+- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
+- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
+
+#### Accountability
+
+- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
+- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
+
+### Developer's Certificate of Origin 1.1
+
+```text
+By making a contribution to this project, I certify that:
+
+ (a) The contribution was created in whole or in part by me and I
+     have the right to submit it under the open source license
+     indicated in the file; or
+
+ (b) The contribution is based upon previous work that, to the best
+     of my knowledge, is covered under an appropriate open source
+     license and I have the right under that license to submit that
+     work with modifications, whether created in whole or in part
+     by me, under the same open source license (unless I am
+     permitted to submit under a different license), as indicated
+     in the file; or
+
+ (c) The contribution was provided directly to me by some other
+     person who certified (a), (b) or (c) and I have not modified
+     it.
+
+ (d) I understand and agree that this project and the contribution
+     are public and that a record of the contribution (including all
+     personal information I submit with it, including my sign-off) is
+     maintained indefinitely and may be redistributed consistent with
+     this project or the open source license(s) involved.
+```
+
+## Collaborator's guide
+
+{/* SRC: expressjs/.github CONTRIBUTING.md */}
+
+### Website Issues
+
+Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
+
+For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
+
+### PRs and Code contributions
+
+- Tests must pass.
+- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
+- If you fix a bug, add a test.
+
+### Branches
+
+Use the `master` branch for bug fixes or minor work that is intended for the
+current release stream.
+
+Use the correspondingly named branch, e.g. `6.x`, for anything intended for
+a future release of Express.
+
+### Steps for contributing
+
+1. Create an issue for the
+   bug you want to fix or the feature that you want to add.
+2. Create your own fork on GitHub, then
+   checkout your fork.
+3. Write your code in your local copy. It's good practice to create a branch for
+   each new issue you work on, although not compulsory.
+4. To run the test suite, first install the dependencies by running `npm install`,
+   then run `npm test`.
+5. Ensure your code is linted by running `npm run lint` -- fix any issue you
+   see listed.
+6. If the tests pass, you can commit your changes to your fork and then create
+   a pull request from there. Make sure to reference your issue from the pull
+   request comments by including the issue number e.g. `#123`.
+
+### Issues which are questions
+
+We will typically close any vague issues or questions that are specific to some
+app you are writing. Please double check the docs and other references before
+being trigger happy with posting a question issue.
+
+Things that will help get your question issue looked at:
+
+- Full and runnable JS code.
+- Clear description of the problem or unexpected behavior.
+- Clear description of the expected result.
+- Steps you have taken to debug it yourself.
+
+If you post a question and do not outline the above items or make it easy for
+us to understand and reproduce your issue, it will be closed.
+
+If your question meets all of the above requirements but you do not believe it needs to be looked at
+by the maintainers
+(for example, if you are just looking for community input) please open it as a discussion topic instead
+of an issue. If you
+are unsure and open an issue, we may move it to discussions if we triage them and decide they do
+not need high
+visibility or maintainer input.
+
+## Security Policies and Procedures
+
+{/* SRC: expressjs/.github SECURITY.md */}
+
+This document outlines security procedures and general policies for the Express
+project.
+
+- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
+- [Disclosure Policy](#disclosure-policy)
+- [Comments on this Policy](#comments-on-this-policy)
+- [The Express Threat Model](#the-express-threat-model)
+
+### Reporting a Bug or Security Vulnerability
+
+<Alert type="info">
+
+Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
+
+</Alert>
+
+The Express team and community take all security vulnerabilities seriously.
+Thank you for improving the security of Express and related projects.
+We appreciate your efforts in responsible disclosure and will make every effort
+to acknowledge your contributions.
+
+A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
+or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
+will acknowledge your report as soon as possible.
+These timelines may extend when our triage
+volunteers are away on holiday, particularly at the end of the year.
+
+After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+
+<Alert type="info">
+
+You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
+
+</Alert>
+
+#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
+
+The preferred way to report security vulnerabilities is through
+[GitHub Security Advisories](https://github.com/advisories).
+This allows us to collaborate on a fix while maintaining the
+confidentiality of the report.
+
+To report a vulnerability
+([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
+
+1. Visit the **Security** tab of the affected repository on GitHub.
+2. Click **Report a vulnerability** and follow the provided steps.
+
+This process applies to any repositories within the Express ecosystem.
+If you are unsure whether a repository falls under this policy,
+feel free to reach out via email.
+
+#### Reporting via Email
+
+If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
+
+To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
+
+The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
+
+#### Third-Party Modules
+
+If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
+
+### Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a
+primary handler. This person will coordinate the fix and release process,
+involving the following steps:
+
+- Confirm the problem and determine the affected versions.
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance. These fixes will be
+  released as fast as possible to npm.
+
+### Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.
+
+### The Express Threat Model
+
+The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
+
+Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
+
+For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
diff --git a/src/content/pages/en/resources/glossary.mdx b/src/content/pages/en/resources/glossary.mdx
new file mode 100644
index 0000000000..d0051b3be5
--- /dev/null
+++ b/src/content/pages/en/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+## application
+
+In general, one or more programs that are designed to carry out operations for a specific purpose. In the context of Express, a program that uses the Express API running on the Node.js platform. Might also refer to an [app object](/en/api#express).
+
+## API
+
+Application programming interface. Spell out the abbreviation when it is first used.
+
+## Express
+
+A fast, un-opinionated, minimalist web framework for Node.js applications. In general, "Express" is preferred to "Express.js," though the latter is acceptable.
+
+## libuv
+
+A multi-platform support library which focuses on asynchronous I/O, primarily developed for use by Node.js.
+
+## middleware
+
+A function that is invoked by the Express routing layer before the final request handler, and thus sits in the middle between a raw request and the final intended route. A few fine points of terminology around middleware:
+
+- `var foo = require('middleware')` is called _requiring_ or _using_ a Node.js module. Then the statement `var mw = foo()` typically returns the middleware.
+- `app.use(mw)` is called _adding the middleware to the global processing stack_.
+- `app.get('/foo', mw, function (req, res) { ... })` is called _adding the middleware to the "GET /foo" processing stack_.
+
+## Node.js
+
+A software platform that is used to build scalable network applications. Node.js uses JavaScript as its scripting language, and achieves high throughput via non-blocking I/O and a single-threaded event loop. See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
+
+## open-source, open source
+
+When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Although it is common not to hyphenate this term, we are using the standard English rules for
+hyphenating a compound adjective.
+
+</Alert>
+
+## request
+
+An HTTP request. A client submits an HTTP request message to a server, which returns a response. The request must use one of several [request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) such as GET, POST, and so on.
+
+## response
+
+An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
+
+## route
+
+Part of a URL that identifies a resource. For example, in `http://foo.com/products/id`, "/products/id" is the route.
+
+## router
+
+See [router](/en/api#router) in the API reference.
diff --git a/src/content/pages/en/resources/index.mdx b/src/content/pages/en/resources/index.mdx
new file mode 100644
index 0000000000..890eb29a75
--- /dev/null
+++ b/src/content/pages/en/resources/index.mdx
@@ -0,0 +1,42 @@
+---
+title: Resources
+description: Explore Express.js resources including community, contributing guidelines, glossary, utilities, and middleware.
+---
+
+import Card from '@components/primitives/Card/Card.astro';
+import { CardList } from '@components/patterns';
+
+Find resources to help you learn, contribute, and connect with the Express.js ecosystem. Whether you're looking to get involved in the community, explore middleware, or understand key concepts, you'll find what you need here.
+
+<CardList gap="6">
+  <a href="/en/resources/community">
+    <Card
+      title="Community"
+      body="Connect with the Express.js community, learn about the technical committee, and get involved in discussions."
+    />
+  </a>
+  <a href="/en/resources/contributing">
+    <Card
+      title="Contributing to Express"
+      body="Find out how to contribute to Express.js, including guidelines for reporting issues and submitting pull requests."
+    />
+  </a>
+  <a href="/en/resources/glossary">
+    <Card
+      title="Glossary"
+      body="A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts."
+    />
+  </a>
+  <a href="/en/resources/utils">
+    <Card
+      title="Utilities"
+      body="Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, and more."
+    />
+  </a>
+  <a href="/en/resources/middleware">
+    <Card
+      title="Middleware"
+      body="Explore middleware modules for Express.js to extend your application with additional functionality."
+    />
+  </a>
+</CardList>
diff --git a/src/content/pages/en/resources/middleware/body-parser.mdx b/src/content/pages/en/resources/middleware/body-parser.mdx
new file mode 100644
index 0000000000..c3182bc22e
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/body-parser.mdx
@@ -0,0 +1,508 @@
+---
+title: body-parser middleware
+description: Node.js body parsing middleware
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.2.2"
+  github="https://github.com/expressjs/body-parser"
+  npm="https://www.npmjs.com/package/body-parser"
+/>
+
+Node.js body parsing middleware.
+
+Parse incoming request bodies in a middleware before your handlers, available
+under the `req.body` property.
+
+**Note** As `req.body`'s shape is based on user-controlled input, all
+properties and values in this object are untrusted and should be validated
+before trusting. For example, `req.body.foo.toString()` may fail in multiple
+ways, for example the `foo` property may not be there or may not be a string,
+and `toString` may not be a function and instead a string or other user input.
+
+[Learn about the anatomy of an HTTP transaction in Node.js](https://nodejs.org/en/learn/http/anatomy-of-an-http-transaction).
+
+_This does not handle multipart bodies_, due to their complex and typically
+large nature. For multipart bodies, you may be interested in the following
+modules:
+
+- [busboy](https://www.npmjs.com/package/busboy#readme) and
+  [connect-busboy](https://www.npmjs.com/package/connect-busboy#readme)
+- [multiparty](https://www.npmjs.com/package/multiparty#readme) and
+  [connect-multiparty](https://www.npmjs.com/package/connect-multiparty#readme)
+- [formidable](https://www.npmjs.com/package/formidable#readme)
+- [multer](https://www.npmjs.com/package/multer#readme)
+
+This module provides the following parsers:
+
+- [JSON body parser](#bodyparserjsonoptions)
+- [Raw body parser](#bodyparserrawoptions)
+- [Text body parser](#bodyparsertextoptions)
+- [URL-encoded form body parser](#bodyparserurlencodedoptions)
+
+Other body parsers you might be interested in:
+
+- [body](https://www.npmjs.com/package/body#readme)
+- [co-body](https://www.npmjs.com/package/co-body#readme)
+
+## Installation
+
+```sh
+$ npm install body-parser
+```
+
+## API
+
+```js
+// Import all parsers
+const bodyParser = require('body-parser');
+
+// Or import individual parsers directly
+const json = require('body-parser/json');
+const urlencoded = require('body-parser/urlencoded');
+const raw = require('body-parser/raw');
+const text = require('body-parser/text');
+```
+
+The `bodyParser` object exposes various factories to create middlewares. All
+middlewares will populate the `req.body` property with the parsed body when
+the `Content-Type` request header matches the `type` option.
+
+The various errors returned by this module are described in the
+[errors section](#errors).
+
+### bodyParser.json([options])
+
+Returns middleware that only parses `json` and only looks at requests where
+the `Content-Type` header matches the `type` option. This parser accepts any
+Unicode encoding of the body and supports automatic inflation of `gzip`,
+`br` (brotli) and `deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`).
+
+#### Options
+
+The `json` function takes an optional `options` object that may contain any of
+the following keys:
+
+##### defaultCharset
+
+Specify the default character set for the json content if the charset is not
+specified in the `Content-Type` header of the request. Defaults to `utf-8`.
+
+##### inflate
+
+When set to `true`, then deflated (compressed) bodies will be inflated; when
+`false`, deflated bodies are rejected. Defaults to `true`.
+
+##### limit
+
+Controls the maximum request body size. If this is a number, then the value
+specifies the number of bytes; if it is a string, the value is passed to the
+[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
+to `'100kb'`.
+
+> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
+
+##### reviver
+
+The `reviver` option is passed directly to `JSON.parse` as the second
+argument. You can find more information on this argument
+[in the MDN documentation about JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse#Example.3A_Using_the_reviver_parameter).
+
+##### strict
+
+When set to `true`, will only accept arrays and objects; when `false` will
+accept anything `JSON.parse` accepts. Defaults to `true`.
+
+##### type
+
+The `type` option is used to determine what media type the middleware will
+parse. This option can be a string, array of strings, or a function. If not a
+function, `type` option is passed directly to the
+[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
+be an extension name (like `json`), a mime type (like `application/json`), or
+a mime type with a wildcard (like `*/*` or `*/json`). If a function, the `type`
+option is called as `fn(req)` and the request is parsed if it returns a truthy
+value. Defaults to `application/json`.
+
+##### verify
+
+The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
+where `buf` is a `Buffer` of the raw request body and `encoding` is the
+encoding of the request. The parsing can be aborted by throwing an error.
+
+### bodyParser.raw([options])
+
+Returns middleware that parses all bodies as a `Buffer` and only looks at
+requests where the `Content-Type` header matches the `type` option. This
+parser supports automatic inflation of `gzip`, `br` (brotli) and `deflate`
+encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`). This will be a `Buffer` object
+of the body.
+
+#### Options
+
+The `raw` function takes an optional `options` object that may contain any of
+the following keys:
+
+##### inflate
+
+When set to `true`, then deflated (compressed) bodies will be inflated; when
+`false`, deflated bodies are rejected. Defaults to `true`.
+
+##### limit
+
+Controls the maximum request body size. If this is a number, then the value
+specifies the number of bytes; if it is a string, the value is passed to the
+[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
+to `'100kb'`.
+
+> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
+
+##### type
+
+The `type` option is used to determine what media type the middleware will
+parse. This option can be a string, array of strings, or a function.
+If not a function, `type` option is passed directly to the
+[type-is](https://www.npmjs.com/package/type-is#readme) library and this
+can be an extension name (like `bin`), a mime type (like
+`application/octet-stream`), or a mime type with a wildcard (like `*/*` or
+`application/*`). If a function, the `type` option is called as `fn(req)`
+and the request is parsed if it returns a truthy value. Defaults to
+`application/octet-stream`.
+
+##### verify
+
+The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
+where `buf` is a `Buffer` of the raw request body and `encoding` is the
+encoding of the request. The parsing can be aborted by throwing an error.
+
+### bodyParser.text([options])
+
+Returns middleware that parses all bodies as a string and only looks at
+requests where the `Content-Type` header matches the `type` option. This
+parser supports automatic inflation of `gzip`, `br` (brotli) and `deflate`
+encodings.
+
+A new `body` string containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`). This will be a string of the
+body.
+
+#### Options
+
+The `text` function takes an optional `options` object that may contain any of
+the following keys:
+
+##### defaultCharset
+
+Specify the default character set for the text content if the charset is not
+specified in the `Content-Type` header of the request. Defaults to `utf-8`.
+
+##### inflate
+
+When set to `true`, then deflated (compressed) bodies will be inflated; when
+`false`, deflated bodies are rejected. Defaults to `true`.
+
+##### limit
+
+Controls the maximum request body size. If this is a number, then the value
+specifies the number of bytes; if it is a string, the value is passed to the
+[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
+to `'100kb'`.
+
+> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
+
+##### type
+
+The `type` option is used to determine what media type the middleware will
+parse. This option can be a string, array of strings, or a function. If not
+a function, `type` option is passed directly to the
+[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
+be an extension name (like `txt`), a mime type (like `text/plain`), or a mime
+type with a wildcard (like `*/*` or `text/*`). If a function, the `type`
+option is called as `fn(req)` and the request is parsed if it returns a
+truthy value. Defaults to `text/plain`.
+
+##### verify
+
+The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
+where `buf` is a `Buffer` of the raw request body and `encoding` is the
+encoding of the request. The parsing can be aborted by throwing an error.
+
+### bodyParser.urlencoded([options])
+
+Returns middleware that only parses `urlencoded` bodies and only looks at
+requests where the `Content-Type` header matches the `type` option. This
+parser accepts only UTF-8 and ISO-8859-1 encodings of the body and supports
+automatic inflation of `gzip`, `br` (brotli) and `deflate` encodings.
+
+A new `body` object containing the parsed data is populated on the `request`
+object after the middleware (i.e. `req.body`). This object will contain
+key-value pairs, where the value can be a string or array (when `extended` is
+`false`), or any type (when `extended` is `true`).
+
+#### Options
+
+The `urlencoded` function takes an optional `options` object that may contain
+any of the following keys:
+
+##### extended
+
+The "extended" syntax allows for rich objects and arrays to be encoded into the
+URL-encoded format, allowing for a JSON-like experience with URL-encoded. For
+more information, please [see the qs
+library](https://www.npmjs.com/package/qs#readme).
+
+Defaults to `false`.
+
+##### inflate
+
+When set to `true`, then deflated (compressed) bodies will be inflated; when
+`false`, deflated bodies are rejected. Defaults to `true`.
+
+##### limit
+
+Controls the maximum request body size. If this is a number, then the value
+specifies the number of bytes; if it is a string, the value is passed to the
+[bytes](https://www.npmjs.com/package/bytes) library for parsing. Defaults
+to `'100kb'`.
+
+> It’s recommended not to configure a very high limit and to use the default value whenever possible. Allowing larger payloads increases memory usage because of the resources required for decoding and transformations, and it can also lead to longer response times as more data is processed. By ‘very high’, we mean values above the default, for example payloads of 5 MB or more can already start to introduce these risks. With the default limits, these issues do not occur.
+
+##### parameterLimit
+
+The `parameterLimit` option controls the maximum number of parameters that
+are allowed in the URL-encoded data. If a request contains more parameters
+than this value, a 413 will be returned to the client. Defaults to `1000`.
+
+##### type
+
+The `type` option is used to determine what media type the middleware will
+parse. This option can be a string, array of strings, or a function. If not
+a function, `type` option is passed directly to the
+[type-is](https://www.npmjs.com/package/type-is#readme) library and this can
+be an extension name (like `urlencoded`), a mime type (like
+`application/x-www-form-urlencoded`), or a mime type with a wildcard (like
+`*/x-www-form-urlencoded`). If a function, the `type` option is called as
+`fn(req)` and the request is parsed if it returns a truthy value. Defaults
+to `application/x-www-form-urlencoded`.
+
+##### verify
+
+The `verify` option, if supplied, is called as `verify(req, res, buf, encoding)`,
+where `buf` is a `Buffer` of the raw request body and `encoding` is the
+encoding of the request. The parsing can be aborted by throwing an error.
+
+##### defaultCharset
+
+The default charset to parse as, if not specified in content-type. Must be
+either `utf-8` or `iso-8859-1`. Defaults to `utf-8`.
+
+##### charsetSentinel
+
+Whether to let the value of the `utf8` parameter take precedence as the charset
+selector. It requires the form to contain a parameter named `utf8` with a value
+of `✓`. Defaults to `false`.
+
+##### interpretNumericEntities
+
+Whether to decode numeric entities such as `&#9786;` when parsing an iso-8859-1
+form. Defaults to `false`.
+
+##### depth
+
+The `depth` option is used to configure the maximum depth of the `qs` library when `extended` is `true`. This allows you to limit the amount of keys that are parsed and can be useful to prevent certain types of abuse. Defaults to `32`. It is recommended to keep this value as low as possible.
+
+## Errors
+
+The middlewares provided by this module create errors using the
+[`http-errors` module](https://www.npmjs.com/package/http-errors). The errors
+will typically have a `status`/`statusCode` property that contains the suggested
+HTTP response code, an `expose` property to determine if the `message` property
+should be displayed to the client, a `type` property to determine the type of
+error without matching against the `message`, and a `body` property containing
+the read body, if available.
+
+The following are the common errors created, though any error can come through
+for various reasons.
+
+### content encoding unsupported
+
+This error will occur when the request had a `Content-Encoding` header that
+contained an encoding but the "inflation" option was set to `false`. The
+`status` property is set to `415`, the `type` property is set to
+`'encoding.unsupported'`, and the `charset` property will be set to the
+encoding that is unsupported.
+
+### entity parse failed
+
+This error will occur when the request contained an entity that could not be
+parsed by the middleware. The `status` property is set to `400`, the `type`
+property is set to `'entity.parse.failed'`, and the `body` property is set to
+the entity value that failed parsing.
+
+### entity verify failed
+
+This error will occur when the request contained an entity that could not be
+failed verification by the defined `verify` option. The `status` property is
+set to `403`, the `type` property is set to `'entity.verify.failed'`, and the
+`body` property is set to the entity value that failed verification.
+
+### request aborted
+
+This error will occur when the request is aborted by the client before reading
+the body has finished. The `received` property will be set to the number of
+bytes received before the request was aborted and the `expected` property is
+set to the number of expected bytes. The `status` property is set to `400`
+and `type` property is set to `'request.aborted'`.
+
+### request entity too large
+
+This error will occur when the request body's size is larger than the "limit"
+option. The `limit` property will be set to the byte limit and the `length`
+property will be set to the request body's length. The `status` property is
+set to `413` and the `type` property is set to `'entity.too.large'`.
+
+### request size did not match content length
+
+This error will occur when the request's length did not match the length from
+the `Content-Length` header. This typically occurs when the request is malformed,
+typically when the `Content-Length` header was calculated based on characters
+instead of bytes. The `status` property is set to `400` and the `type` property
+is set to `'request.size.invalid'`.
+
+### stream encoding should not be set
+
+This error will occur when something called the `req.setEncoding` method prior
+to this middleware. This module operates directly on bytes only and you cannot
+call `req.setEncoding` when using this module. The `status` property is set to
+`500` and the `type` property is set to `'stream.encoding.set'`.
+
+### stream is not readable
+
+This error will occur when the request is no longer readable when this middleware
+attempts to read it. This typically means something other than a middleware from
+this module read the request body already and the middleware was also configured to
+read the same request. The `status` property is set to `500` and the `type`
+property is set to `'stream.not.readable'`.
+
+### too many parameters
+
+This error will occur when the content of the request exceeds the configured
+`parameterLimit` for the `urlencoded` parser. The `status` property is set to
+`413` and the `type` property is set to `'parameters.too.many'`.
+
+### unsupported charset "BOGUS"
+
+This error will occur when the request had a charset parameter in the
+`Content-Type` header, but the `iconv-lite` module does not support it OR the
+parser does not support it. The charset is contained in the message as well
+as in the `charset` property. The `status` property is set to `415`, the
+`type` property is set to `'charset.unsupported'`, and the `charset` property
+is set to the charset that is unsupported.
+
+### unsupported content encoding "bogus"
+
+This error will occur when the request had a `Content-Encoding` header that
+contained an unsupported encoding. The encoding is contained in the message
+as well as in the `encoding` property. The `status` property is set to `415`,
+the `type` property is set to `'encoding.unsupported'`, and the `encoding`
+property is set to the encoding that is unsupported.
+
+### The input exceeded the depth
+
+This error occurs when using `bodyParser.urlencoded` with the `extended` property set to `true` and the input exceeds the configured `depth` option. The `status` property is set to `400`. It is recommended to review the `depth` option and evaluate if it requires a higher value. When the `depth` option is set to `32` (default value), the error will not be thrown.
+
+## Examples
+
+### Express/Connect top-level generic
+
+This example demonstrates adding a generic JSON and URL-encoded parser as a
+top-level middleware, which will parse the bodies of all incoming requests.
+This is the simplest setup.
+
+```js
+const express = require('express');
+const bodyParser = require('body-parser');
+
+const app = express();
+
+// parse application/x-www-form-urlencoded
+app.use(bodyParser.urlencoded());
+
+// parse application/json
+app.use(bodyParser.json());
+
+app.use(function (req, res) {
+  res.setHeader('Content-Type', 'text/plain');
+  res.write('you posted:\n');
+  res.end(String(JSON.stringify(req.body, null, 2)));
+});
+```
+
+### Express route-specific
+
+This example demonstrates adding body parsers specifically to the routes that
+need them. In general, this is the most recommended way to use body-parser with
+Express.
+
+```js
+const express = require('express');
+const bodyParser = require('body-parser');
+
+const app = express();
+
+// create application/json parser
+const jsonParser = bodyParser.json();
+
+// create application/x-www-form-urlencoded parser
+const urlencodedParser = bodyParser.urlencoded();
+
+// POST /login gets urlencoded bodies
+app.post('/login', urlencodedParser, function (req, res) {
+  if (!req.body || !req.body.username) res.sendStatus(400);
+  res.send('welcome, ' + req.body.username);
+});
+
+// POST /api/users gets JSON bodies
+app.post('/api/users', jsonParser, function (req, res) {
+  if (!req.body) res.sendStatus(400);
+  // create user in req.body
+});
+```
+
+### Change accepted type for parsers
+
+All the parsers accept a `type` option which allows you to change the
+`Content-Type` that the middleware will parse.
+
+```js
+const express = require('express');
+const bodyParser = require('body-parser');
+
+const app = express();
+
+// parse various different custom JSON types as JSON
+app.use(bodyParser.json({ type: 'application/*+json' }));
+
+// parse some custom thing into a Buffer
+app.use(bodyParser.raw({ type: 'application/vnd.custom-type' }));
+
+// parse an HTML body into a string
+app.use(bodyParser.text({ type: 'text/html' }));
+```
+
+## License
+
+[MIT](https://github.com/expressjs/body-parser/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.com/package/body-parser
+[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/body-parser/badge
+[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/body-parser
diff --git a/src/content/pages/en/resources/middleware/compression.mdx b/src/content/pages/en/resources/middleware/compression.mdx
new file mode 100644
index 0000000000..f896116e97
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/compression.mdx
@@ -0,0 +1,310 @@
+---
+title: compression middleware
+description: Node.js compression middleware
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="1.8.1"
+  github="https://github.com/expressjs/compression"
+  npm="https://www.npmjs.com/package/compression"
+/>
+
+Node.js compression middleware.
+
+The following compression codings are supported:
+
+- deflate
+- gzip
+- br (brotli)
+
+**Note** Brotli is supported only since Node.js versions v11.7.0 and v10.16.0.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```bash
+$ npm install compression
+```
+
+## API
+
+```js
+var compression = require('compression');
+```
+
+### compression([options])
+
+Returns the compression middleware using the given `options`. The middleware
+will attempt to compress response bodies for all requests that traverse through
+the middleware, based on the given `options`.
+
+This middleware will never compress responses that include a `Cache-Control`
+header with the [`no-transform` directive](https://tools.ietf.org/html/rfc7234#section-5.2.2.4),
+as compressing will transform the body.
+
+#### Options
+
+`compression()` accepts these properties in the options object. In addition to
+those listed below, [zlib](https://nodejs.org/api/zlib.html) options may be
+passed in to the options object or
+[brotli](https://nodejs.org/api/zlib.html#zlib_class_brotlioptions) options.
+
+##### chunkSize
+
+Type: `Number`<br />
+Default: `zlib.constants.Z_DEFAULT_CHUNK`, or `16384`.
+
+See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
+regarding the usage.
+
+##### filter
+
+Type: `Function`
+
+A function to decide if the response should be considered for compression.
+This function is called as `filter(req, res)` and is expected to return
+`true` to consider the response for compression, or `false` to not compress
+the response.
+
+The default filter function uses the [compressible](https://www.npmjs.com/package/compressible)
+module to determine if `res.getHeader('Content-Type')` is compressible.
+
+##### level
+
+Type: `Number`<br />
+Default: `zlib.constants.Z_DEFAULT_COMPRESSION`, or `-1`
+
+The level of zlib compression to apply to responses. A higher level will result
+in better compression, but will take longer to complete. A lower level will
+result in less compression, but will be much faster.
+
+This is an integer in the range of `0` (no compression) to `9` (maximum
+compression). The special value `-1` can be used to mean the "default
+compression level", which is a default compromise between speed and
+compression (currently equivalent to level 6).
+
+- `-1` Default compression level (also `zlib.constants.Z_DEFAULT_COMPRESSION`).
+- `0` No compression (also `zlib.constants.Z_NO_COMPRESSION`).
+- `1` Fastest compression (also `zlib.constants.Z_BEST_SPEED`).
+- `2`
+- `3`
+- `4`
+- `5`
+- `6` (currently what `zlib.constants.Z_DEFAULT_COMPRESSION` points to).
+- `7`
+- `8`
+- `9` Best compression (also `zlib.constants.Z_BEST_COMPRESSION`).
+
+**Note** in the list above, `zlib` is from `zlib = require('zlib')`.
+
+##### memLevel
+
+Type: `Number`<br />
+Default: `zlib.constants.Z_DEFAULT_MEMLEVEL`, or `8`
+
+This specifies how much memory should be allocated for the internal compression
+state and is an integer in the range of `1` (minimum level) and `9` (maximum
+level).
+
+See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
+regarding the usage.
+
+##### brotli
+
+Type: `Object`
+
+This specifies the options for configuring Brotli. See [Node.js documentation](https://nodejs.org/api/zlib.html#class-brotlioptions) for a complete list of available options.
+
+##### strategy
+
+Type: `Number`<br />
+Default: `zlib.constants.Z_DEFAULT_STRATEGY`
+
+This is used to tune the compression algorithm. This value only affects the
+compression ratio, not the correctness of the compressed output, even if it
+is not set appropriately.
+
+- `zlib.constants.Z_DEFAULT_STRATEGY` Use for normal data.
+- `zlib.constants.Z_FILTERED` Use for data produced by a filter (or predictor).
+  Filtered data consists mostly of small values with a somewhat random
+  distribution. In this case, the compression algorithm is tuned to
+  compress them better. The effect is to force more Huffman coding and less
+  string matching; it is somewhat intermediate between `zlib.constants.Z_DEFAULT_STRATEGY`
+  and `zlib.constants.Z_HUFFMAN_ONLY`.
+- `zlib.constants.Z_FIXED` Use to prevent the use of dynamic Huffman codes, allowing
+  for a simpler decoder for special applications.
+- `zlib.constants.Z_HUFFMAN_ONLY` Use to force Huffman encoding only (no string match).
+- `zlib.constants.Z_RLE` Use to limit match distances to one (run-length encoding).
+  This is designed to be almost as fast as `zlib.constants.Z_HUFFMAN_ONLY`, but give
+  better compression for PNG image data.
+
+**Note** in the list above, `zlib` is from `zlib = require('zlib')`.
+
+##### threshold
+
+Type: `Number` or `String`<br />
+Default: `1kb`
+
+The byte threshold for the response body size before compression is considered
+for the response. This is a number of bytes or any string
+accepted by the [bytes](https://www.npmjs.com/package/bytes) module.
+
+**Note** this is only an advisory setting; if the response size cannot be determined
+at the time the response headers are written, then it is assumed the response is
+_over_ the threshold. To guarantee the response size can be determined, be sure
+set a `Content-Length` response header.
+
+##### windowBits
+
+Type: `Number`<br />
+Default: `zlib.constants.Z_DEFAULT_WINDOWBITS`, or `15`
+
+See [Node.js documentation](https://nodejs.org/api/zlib.html#zlib_memory_usage_tuning)
+regarding the usage.
+
+##### enforceEncoding
+
+Type: `String`<br />
+Default: `identity`
+
+This is the default encoding to use when the client does not specify an encoding in the request's [Accept-Encoding](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding) header.
+
+#### .filter
+
+The default `filter` function. This is used to construct a custom filter
+function that is an extension of the default function.
+
+```js
+var compression = require('compression');
+var express = require('express');
+
+var app = express();
+
+app.use(compression({ filter: shouldCompress }));
+
+function shouldCompress(req, res) {
+  if (req.headers['x-no-compression']) {
+    // don't compress responses with this request header
+    return false;
+  }
+
+  // fallback to standard filter function
+  return compression.filter(req, res);
+}
+```
+
+### res.flush
+
+This module adds a `res.flush()` method to force the partially-compressed
+response to be flushed to the client.
+
+## Examples
+
+### express
+
+When using this module with express, simply `app.use` the module as
+high as you like. Requests that pass through the middleware will be compressed.
+
+```js
+var compression = require('compression');
+var express = require('express');
+
+var app = express();
+
+// compress all responses
+app.use(compression());
+
+// add all routes
+```
+
+### Node.js HTTP server
+
+```js
+var compression = require('compression')({ threshold: 0 });
+var http = require('http');
+
+function createServer(fn) {
+  return http.createServer(function (req, res) {
+    compression(req, res, function (err) {
+      if (err) {
+        res.statusCode = err.status || 500;
+        res.end(err.message);
+        return;
+      }
+
+      fn(req, res);
+    });
+  });
+}
+
+var server = createServer(function (req, res) {
+  res.setHeader('Content-Type', 'text/plain');
+  res.end('hello world!');
+});
+
+server.listen(3000, () => {
+  console.log('> Listening at http://localhost:3000');
+});
+```
+
+### Server-Sent Events
+
+Because of the nature of compression this module does not work out of the box
+with server-sent events. To compress content, a window of the output needs to
+be buffered up in order to get good compression. Typically when using server-sent
+events, there are certain block of data that need to reach the client.
+
+You can achieve this by calling `res.flush()` when you need the data written to
+actually make it to the client.
+
+```js
+var compression = require('compression');
+var express = require('express');
+
+var app = express();
+
+// compress responses
+app.use(compression());
+
+// server-sent event stream
+app.get('/events', function (req, res) {
+  res.setHeader('Content-Type', 'text/event-stream');
+  res.setHeader('Cache-Control', 'no-cache');
+
+  // send a ping approx every 2 seconds
+  var timer = setInterval(function () {
+    res.write('data: ping\n\n');
+
+    // !!! this is the important part
+    res.flush();
+  }, 2000);
+
+  res.on('close', function () {
+    clearInterval(timer);
+  });
+});
+```
+
+## Contributing
+
+The Express.js project welcomes all constructive contributions. Contributions take many forms,
+from code for bug fixes and enhancements, to additions and fixes to documentation, additional
+tests, triaging incoming pull requests and issues, and more!
+
+See the [Contributing Guide](https://github.com/expressjs/express/blob/master/Contributing.md) for more technical details on contributing.
+
+## License
+
+[MIT](https://github.com/expressjs/compression/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/compression
+[downloads-url]: https://npmcharts.com/compare/compression?minimal=true
+[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/compression/badge
+[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/compression
+[funding-url]: https://opencollective.com/express
diff --git a/src/content/pages/en/resources/middleware/cookie-parser.mdx b/src/content/pages/en/resources/middleware/cookie-parser.mdx
new file mode 100644
index 0000000000..15d7e4b104
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/cookie-parser.mdx
@@ -0,0 +1,120 @@
+---
+title: cookie-parser middleware
+description: Parse HTTP request cookies
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="1.4.7"
+  github="https://github.com/expressjs/cookie-parser"
+  npm="https://www.npmjs.com/package/cookie-parser"
+/>
+
+Parse `Cookie` header and populate `req.cookies` with an object keyed by the
+cookie names. Optionally you may enable signed cookie support by passing a
+`secret` string, which assigns `req.secret` so it may be used by other
+middleware.
+
+## Installation
+
+```sh
+$ npm install cookie-parser
+```
+
+## API
+
+```js
+var cookieParser = require('cookie-parser');
+```
+
+### cookieParser(secret, options)
+
+Create a new cookie parser middleware function using the given `secret` and
+`options`.
+
+- `secret` a string or array used for signing cookies. This is optional and if
+  not specified, will not parse signed cookies. If a string is provided, this
+  is used as the secret. If an array is provided, an attempt will be made to
+  unsign the cookie with each secret in order.
+- `options` an object that is passed to `cookie.parse` as the second option. See
+  [cookie](https://www.npmjs.org/package/cookie) for more information.
+  - `decode` a function to decode the value of the cookie
+
+The middleware will parse the `Cookie` header on the request and expose the
+cookie data as the property `req.cookies` and, if a `secret` was provided, as
+the property `req.signedCookies`. These properties are name value pairs of the
+cookie name to cookie value.
+
+When `secret` is provided, this module will unsign and validate any signed cookie
+values and move those name value pairs from `req.cookies` into `req.signedCookies`.
+A signed cookie is a cookie that has a value prefixed with `s:`. Signed cookies
+that fail signature validation will have the value `false` instead of the tampered
+value.
+
+In addition, this module supports special "JSON cookies". These are cookie where
+the value is prefixed with `j:`. When these values are encountered, the value will
+be exposed as the result of `JSON.parse`. If parsing fails, the original value will
+remain.
+
+### cookieParser.JSONCookie(str)
+
+Parse a cookie value as a JSON cookie. This will return the parsed JSON value
+if it was a JSON cookie, otherwise, it will return the passed value.
+
+### cookieParser.JSONCookies(cookies)
+
+Given an object, this will iterate over the keys and call `JSONCookie` on each
+value, replacing the original value with the parsed value. This returns the
+same object that was passed in.
+
+### cookieParser.signedCookie(str, secret)
+
+Parse a cookie value as a signed cookie. This will return the parsed unsigned
+value if it was a signed cookie and the signature was valid. If the value was
+not signed, the original value is returned. If the value was signed but the
+signature could not be validated, `false` is returned.
+
+The `secret` argument can be an array or string. If a string is provided, this
+is used as the secret. If an array is provided, an attempt will be made to
+unsign the cookie with each secret in order.
+
+### cookieParser.signedCookies(cookies, secret)
+
+Given an object, this will iterate over the keys and check if any value is a
+signed cookie. If it is a signed cookie and the signature is valid, the key
+will be deleted from the object and added to the new object that is returned.
+
+The `secret` argument can be an array or string. If a string is provided, this
+is used as the secret. If an array is provided, an attempt will be made to
+unsign the cookie with each secret in order.
+
+## Example
+
+```js
+var express = require('express');
+var cookieParser = require('cookie-parser');
+
+var app = express();
+app.use(cookieParser());
+
+app.get('/', function (req, res) {
+  // Cookies that have not been signed
+  console.log('Cookies: ', req.cookies);
+
+  // Cookies that have been signed
+  console.log('Signed Cookies: ', req.signedCookies);
+});
+
+app.listen(8080);
+
+// curl command that sends an HTTP request with two cookies
+// curl http://127.0.0.1:8080 --cookie "Cho=Kim;Greet=Hello"
+```
+
+## License
+
+[MIT](https://github.com/expressjs/cookie-parser/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/cookie-parser
diff --git a/src/content/pages/en/resources/middleware/cookie-session.mdx b/src/content/pages/en/resources/middleware/cookie-session.mdx
new file mode 100644
index 0000000000..82278ce599
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/cookie-session.mdx
@@ -0,0 +1,303 @@
+---
+title: cookie-session middleware
+description: Cookie session middleware
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.1.1"
+  github="https://github.com/expressjs/cookie-session"
+  npm="https://www.npmjs.com/package/cookie-session"
+/>
+
+Simple cookie-based session middleware.
+
+A user session can be stored in two main ways with cookies: on the server or on
+the client. This module stores the session data on the client within a cookie,
+while a module like [express-session](https://www.npmjs.com/package/express-session)
+stores only a session identifier on the client within a cookie and stores the
+session data on the server, typically in a database.
+
+The following points can help you choose which to use:
+
+- `cookie-session` does not require any database / resources on the server side,
+  though the total session data cannot exceed the browser's max cookie size.
+- `cookie-session` can simplify certain load-balanced scenarios.
+- `cookie-session` can be used to store a "light" session and include an identifier
+  to look up a database-backed secondary store to reduce database lookups.
+
+**NOTE** This module does not encrypt the session contents in the cookie, only provides
+signing to prevent tampering. The client will be able to read the session data by
+examining the cookie's value. Secret data should not be set in `req.session` without
+encrypting it, or use a server-side session instead.
+
+**NOTE** This module does not prevent session replay, as the expiration set is that
+of the cookie only; if that is a concern of your application, you can store an expiration
+date in `req.session` object and validate it on the server, and implement any other logic
+to extend the session as your application needs.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install cookie-session
+```
+
+## API
+
+```js
+var cookieSession = require('cookie-session');
+var express = require('express');
+
+var app = express();
+
+app.use(
+  cookieSession({
+    name: 'session',
+    keys: [
+      /* secret keys */
+    ],
+
+    // Cookie Options
+    maxAge: 24 * 60 * 60 * 1000, // 24 hours
+  })
+);
+```
+
+### cookieSession(options)
+
+Create a new cookie session middleware with the provided options. This middleware
+will attach the property `session` to `req`, which provides an object representing
+the loaded session. This session is either a new session if no valid session was
+provided in the request, or a loaded session from the request.
+
+The middleware will automatically add a `Set-Cookie` header to the response if the
+contents of `req.session` were altered. _Note_ that no `Set-Cookie` header will be
+in the response (and thus no session created for a specific user) unless there are
+contents in the session, so be sure to add something to `req.session` as soon as
+you have identifying information to store for the session.
+
+#### Options
+
+Cookie session accepts these properties in the options object.
+
+##### name
+
+The name of the cookie to set, defaults to `session`.
+
+##### keys
+
+The list of keys to use to sign & verify cookie values, or a configured
+[`Keygrip`](https://www.npmjs.com/package/keygrip) instance. Set cookies are always
+signed with `keys[0]`, while the other keys are valid for verification, allowing
+for key rotation. If a `Keygrip` instance is provided, it can be used to
+change signature parameters like the algorithm of the signature.
+
+##### secret
+
+A string which will be used as single key if `keys` is not provided.
+
+##### Cookie Options
+
+Other options are passed to `cookies.get()` and `cookies.set()` allowing you
+to control security, domain, path, and signing among other settings.
+
+The options can also contain any of the following (for the full list, see
+[cookies module documentation](https://www.npmjs.org/package/cookies#readme):
+
+- `maxAge`: a number representing the milliseconds from `Date.now()` for expiry
+- `expires`: a `Date` object indicating the cookie's expiration date (expires at the end of session by default).
+- `path`: a string indicating the path of the cookie (`/` by default).
+- `domain`: a string indicating the domain of the cookie (no default).
+- `partitioned`: a boolean indicating whether to partition the cookie in Chrome for the [CHIPS Update](https://developers.google.com/privacy-sandbox/3pcd/chips) (`false` by default). If this is true, Cookies from embedded sites will be partitioned and only readable from the same top level site from which it was created.
+- `priority`: a string indicating the cookie priority. This can be set to `'low'`, `'medium'`, or `'high'`.
+- `sameSite`: a boolean or string indicating whether the cookie is a "same site" cookie (`false` by default). This can be set to `'strict'`, `'lax'`, `'none'`, or `true` (which maps to `'strict'`).
+- `secure`: a boolean indicating whether the cookie is only to be sent over HTTPS (`false` by default for HTTP, `true` by default for HTTPS). If this is set to `true` and Node.js is not directly over a TLS connection, be sure to read how to [setup Express behind proxies](https://expressjs.com/en/guide/behind-proxies.html) or the cookie may not ever set correctly.
+- `httpOnly`: a boolean indicating whether the cookie is only to be sent over HTTP(S), and not made available to client JavaScript (`true` by default).
+- `signed`: a boolean indicating whether the cookie is to be signed (`true` by default).
+- `overwrite`: a boolean indicating whether to overwrite previously set cookies of the same name (`true` by default).
+
+### req.session
+
+Represents the session for the given request.
+
+#### .isChanged
+
+Is `true` if the session has been changed during the request.
+
+#### .isNew
+
+Is `true` if the session is new.
+
+#### .isPopulated
+
+Determine if the session has been populated with data or is empty.
+
+### req.sessionOptions
+
+Represents the session options for the current request. These options are a
+shallow clone of what was provided at middleware construction and can be
+altered to change cookie setting behavior on a per-request basis.
+
+### Destroying a session
+
+To destroy a session simply set it to `null`:
+
+```js
+req.session = null;
+```
+
+### Saving a session
+
+Since the entire contents of the session is kept in a client-side cookie, the
+session is "saved" by writing a cookie out in a `Set-Cookie` response header.
+This is done automatically if there has been a change made to the session when
+the Node.js response headers are being written to the client and the session
+was not destroyed.
+
+## Examples
+
+### Simple view counter example
+
+```js
+var cookieSession = require('cookie-session');
+var express = require('express');
+
+var app = express();
+
+app.set('trust proxy', 1); // trust first proxy
+
+app.use(
+  cookieSession({
+    name: 'session',
+    keys: ['key1', 'key2'],
+  })
+);
+
+app.get('/', function (req, res, next) {
+  // Update views
+  req.session.views = (req.session.views || 0) + 1;
+
+  // Write response
+  res.end(req.session.views + ' views');
+});
+
+app.listen(3000);
+```
+
+### Per-user sticky max age
+
+```js
+var cookieSession = require('cookie-session');
+var express = require('express');
+
+var app = express();
+
+app.set('trust proxy', 1); // trust first proxy
+
+app.use(
+  cookieSession({
+    name: 'session',
+    keys: ['key1', 'key2'],
+  })
+);
+
+// This allows you to set req.session.maxAge to let certain sessions
+// have a different value than the default.
+app.use(function (req, res, next) {
+  req.sessionOptions.maxAge = req.session.maxAge || req.sessionOptions.maxAge;
+  next();
+});
+
+// ... your logic here ...
+```
+
+### Extending the session expiration
+
+This module does not send a `Set-Cookie` header if the contents of the session
+have not changed. This means that to extend the expiration of a session in the
+user's browser (in response to user activity, for example) some kind of
+modification to the session needs be made.
+
+```js
+var cookieSession = require('cookie-session');
+var express = require('express');
+
+var app = express();
+
+app.use(
+  cookieSession({
+    name: 'session',
+    keys: ['key1', 'key2'],
+  })
+);
+
+// Update a value in the cookie so that the set-cookie will be sent.
+// Only changes every minute so that it's not sent with every request.
+app.use(function (req, res, next) {
+  req.session.nowInMinutes = Math.floor(Date.now() / 60e3);
+  next();
+});
+
+// ... your logic here ...
+```
+
+### Using a custom signature algorithm
+
+This example shows creating a custom `Keygrip` instance as the `keys` option
+to provide keys and additional signature configuration.
+
+```js
+var cookieSession = require('cookie-session');
+var express = require('express');
+var Keygrip = require('keygrip');
+
+var app = express();
+
+app.use(
+  cookieSession({
+    name: 'session',
+    keys: new Keygrip(['key1', 'key2'], 'SHA384', 'base64'),
+  })
+);
+
+// ... your logic here ...
+```
+
+## Usage Limitations
+
+### Max Cookie Size
+
+Because the entire session object is encoded and stored in a cookie, it is
+possible to exceed the maximum cookie size limits on different browsers. The
+[RFC6265 specification](https://tools.ietf.org/html/rfc6265#section-6.1)
+recommends that a browser **SHOULD** allow
+
+> At least 4096 bytes per cookie (as measured by the sum of the length of
+> the cookie's name, value, and attributes)
+
+In practice this limit differs slightly across browsers. See a list of
+[browser limits here](http://browsercookielimits.iain.guru). As a rule
+of thumb **don't exceed 4093 bytes per domain**.
+
+If your session object is large enough to exceed a browser limit when encoded,
+in most cases the browser will refuse to store the cookie. This will cause the
+following requests from the browser to either a) not have any session
+information or b) use old session information that was small enough to not
+exceed the cookie limit.
+
+If you find your session object is hitting these limits, it is best to
+consider if data in your session should be loaded from a database on the
+server instead of transmitted to/from the browser with every request. Or
+move to an [alternative session strategy](https://github.com/expressjs/session#compatible-session-stores)
+
+## License
+
+[MIT](https://github.com/expressjs/cookie-session/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/cookie-session
diff --git a/src/content/pages/en/resources/middleware/cors.mdx b/src/content/pages/en/resources/middleware/cors.mdx
new file mode 100644
index 0000000000..4e7636aed4
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/cors.mdx
@@ -0,0 +1,283 @@
+---
+title: cors middleware
+description: Node.js CORS middleware
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.8.6"
+  github="https://github.com/expressjs/cors"
+  npm="https://www.npmjs.com/package/cors"
+/>
+
+CORS is a [Node.js](https://nodejs.org/en/) middleware for [Express](https://expressjs.com/)/[Connect](https://github.com/senchalabs/connect) that sets [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS) response headers. These headers tell browsers which origins can read responses from your server.
+
+<Alert type="info">
+
+**How CORS Works:** This package sets response headers—it doesn't block requests. CORS is enforced by browsers: they check the headers and decide if JavaScript can read the response. Non-browser clients (curl, Postman, other servers) ignore CORS entirely. See the [MDN CORS guide](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS) for details.
+
+</Alert>
+
+- [Installation](#installation)
+- [Usage](#usage)
+  - [Simple Usage](#simple-usage-enable-all-cors-requests)
+  - [Enable CORS for a Single Route](#enable-cors-for-a-single-route)
+  - [Configuring CORS](#configuring-cors)
+  - [Configuring CORS w/ Dynamic Origin](#configuring-cors-w-dynamic-origin)
+  - [Enabling CORS Pre-Flight](#enabling-cors-pre-flight)
+  - [Customizing CORS Settings Dynamically per Request](#customizing-cors-settings-dynamically-per-request)
+- [Configuration Options](#configuration-options)
+- [Common Misconceptions](#common-misconceptions)
+- [License](#license)
+- [Original Author](#original-author)
+
+## Installation
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/downloading-and-installing-packages-locally):
+
+```sh
+$ npm install cors
+```
+
+## Usage
+
+### Simple Usage (Enable _All_ CORS Requests)
+
+```javascript
+var express = require('express');
+var cors = require('cors');
+var app = express();
+
+// Adds headers: Access-Control-Allow-Origin: *
+app.use(cors());
+
+app.get('/products/:id', function (req, res, next) {
+  res.json({ msg: 'Hello' });
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+### Enable CORS for a Single Route
+
+```javascript
+var express = require('express');
+var cors = require('cors');
+var app = express();
+
+// Adds headers: Access-Control-Allow-Origin: *
+app.get('/products/:id', cors(), function (req, res, next) {
+  res.json({ msg: 'Hello' });
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+### Configuring CORS
+
+See the [configuration options](#configuration-options) for details.
+
+```javascript
+var express = require('express');
+var cors = require('cors');
+var app = express();
+
+var corsOptions = {
+  origin: 'http://example.com',
+  optionsSuccessStatus: 200, // some legacy browsers (IE11, various SmartTVs) choke on 204
+};
+
+// Adds headers: Access-Control-Allow-Origin: http://example.com, Vary: Origin
+app.get('/products/:id', cors(corsOptions), function (req, res, next) {
+  res.json({ msg: 'Hello' });
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+### Configuring CORS w/ Dynamic Origin
+
+This module supports validating the origin dynamically using a function provided
+to the `origin` option. This function will be passed a string that is the origin
+(or `undefined` if the request has no origin), and a `callback` with the signature
+`callback(error, origin)`.
+
+The `origin` argument to the callback can be any value allowed for the `origin`
+option of the middleware, except a function. See the
+[configuration options](#configuration-options) section for more information on all
+the possible value types.
+
+This function is designed to allow the dynamic loading of allowed origin(s) from
+a backing datasource, like a database.
+
+```javascript
+var express = require('express');
+var cors = require('cors');
+var app = express();
+
+var corsOptions = {
+  origin: function (origin, callback) {
+    // db.loadOrigins is an example call to load
+    // a list of origins from a backing database
+    db.loadOrigins(function (error, origins) {
+      callback(error, origins);
+    });
+  },
+};
+
+// Adds headers: Access-Control-Allow-Origin: <matched origin>, Vary: Origin
+app.get('/products/:id', cors(corsOptions), function (req, res, next) {
+  res.json({ msg: 'Hello' });
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+### Enabling CORS Pre-Flight
+
+Certain CORS requests are considered 'complex' and require an initial
+`OPTIONS` request (called the "pre-flight request"). An example of a
+'complex' CORS request is one that uses an HTTP verb other than
+GET/HEAD/POST (such as DELETE) or that uses custom headers. To enable
+pre-flighting, you must add a new OPTIONS handler for the route you want
+to support:
+
+```javascript
+var express = require('express');
+var cors = require('cors');
+var app = express();
+
+app.options('/products/:id', cors()); // preflight for DELETE
+app.del('/products/:id', cors(), function (req, res, next) {
+  res.json({ msg: 'Hello' });
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+You can also enable pre-flight across-the-board like so:
+
+```javascript
+app.options('*', cors()); // include before other routes
+```
+
+NOTE: When using this middleware as an application level middleware (for
+example, `app.use(cors())`), pre-flight requests are already handled for all
+routes.
+
+### Customizing CORS Settings Dynamically per Request
+
+For APIs that require different CORS configurations for specific routes or requests, you can dynamically generate CORS options based on the incoming request. The `cors` middleware allows you to achieve this by passing a function instead of static options. This function is called for each incoming request and must use the callback pattern to return the appropriate CORS options.
+
+The function accepts:
+
+1. **`req`**:
+   - The incoming request object.
+
+2. **`callback(error, corsOptions)`**:
+   - A function used to return the computed CORS options.
+   - **Arguments**:
+     - **`error`**: Pass `null` if there’s no error, or an error object to indicate a failure.
+     - **`corsOptions`**: An object specifying the CORS policy for the current request.
+
+Here’s an example that handles both public routes and restricted, credential-sensitive routes:
+
+```javascript
+var dynamicCorsOptions = function (req, callback) {
+  var corsOptions;
+  if (req.path.startsWith('/auth/connect/')) {
+    // Access-Control-Allow-Origin: http://mydomain.com, Access-Control-Allow-Credentials: true, Vary: Origin
+    corsOptions = {
+      origin: 'http://mydomain.com',
+      credentials: true,
+    };
+  } else {
+    // Access-Control-Allow-Origin: *
+    corsOptions = { origin: '*' };
+  }
+  callback(null, corsOptions);
+};
+
+app.use(cors(dynamicCorsOptions));
+
+app.get('/auth/connect/twitter', function (req, res) {
+  res.send('Hello');
+});
+
+app.get('/public', function (req, res) {
+  res.send('Hello');
+});
+
+app.listen(80, function () {
+  console.log('web server listening on port 80');
+});
+```
+
+## Configuration Options
+
+- `origin`: Configures the **Access-Control-Allow-Origin** CORS header. Possible values:
+  - `Boolean` - set `origin` to `true` to reflect the [request origin](https://datatracker.ietf.org/doc/html/draft-abarth-origin-09), as defined by `req.header('Origin')`, or set it to `false` to disable CORS.
+  - `String` - set `origin` to a specific origin. For example, if you set it to
+    - `"http://example.com"` only requests from "http://example.com" will be allowed.
+    - `"*"` for all domains to be allowed.
+  - `RegExp` - set `origin` to a regular expression pattern which will be used to test the request origin. If it's a match, the request origin will be reflected. For example the pattern `/example\.com$/` will reflect any request that is coming from an origin ending with "example.com".
+  - `Array` - set `origin` to an array of valid origins. Each origin can be a `String` or a `RegExp`. For example `["http://example1.com", /\.example2\.com$/]` will accept any request from "http://example1.com" or from a subdomain of "example2.com".
+  - `Function` - set `origin` to a function implementing some custom logic. The function takes the request origin as the first parameter and a callback (called as `callback(err, origin)`, where `origin` is a non-function value of the `origin` option) as the second.
+- `methods`: Configures the **Access-Control-Allow-Methods** CORS header. Expects a comma-delimited string (ex: 'GET,PUT,POST') or an array (ex: `['GET', 'PUT', 'POST']`).
+- `allowedHeaders`: Configures the **Access-Control-Allow-Headers** CORS header. Expects a comma-delimited string (ex: 'Content-Type,Authorization') or an array (ex: `['Content-Type', 'Authorization']`). If not specified, defaults to reflecting the headers specified in the request's **Access-Control-Request-Headers** header.
+- `exposedHeaders`: Configures the **Access-Control-Expose-Headers** CORS header. Expects a comma-delimited string (ex: 'Content-Range,X-Content-Range') or an array (ex: `['Content-Range', 'X-Content-Range']`). If not specified, no custom headers are exposed.
+- `credentials`: Configures the **Access-Control-Allow-Credentials** CORS header. Set to `true` to pass the header, otherwise it is omitted.
+- `maxAge`: Configures the **Access-Control-Max-Age** CORS header. Set to an integer to pass the header, otherwise it is omitted.
+- `preflightContinue`: Pass the CORS preflight response to the next handler.
+- `optionsSuccessStatus`: Provides a status code to use for successful `OPTIONS` requests, since some legacy browsers (IE11, various SmartTVs) choke on `204`.
+
+The default configuration is the equivalent of:
+
+```json
+{
+  "origin": "*",
+  "methods": "GET,HEAD,PUT,PATCH,POST,DELETE",
+  "preflightContinue": false,
+  "optionsSuccessStatus": 204
+}
+```
+
+## Common Misconceptions
+
+### "CORS blocks requests from disallowed origins"
+
+**No.** Your server receives and processes every request. CORS headers tell the browser whether JavaScript can read the response—not whether the request is allowed.
+
+### "CORS protects my API from unauthorized access"
+
+**No.** CORS is not access control. Any HTTP client (curl, Postman, another server) can call your API regardless of CORS settings. Use authentication and authorization to protect your API.
+
+### "Setting `origin: 'http://example.com'` means only that domain can access my server"
+
+**No.** It means browsers will only let JavaScript from that origin read responses. The server still responds to all requests.
+
+## License
+
+[MIT License](http://www.opensource.org/licenses/mit-license.php)
+
+## Original Author
+
+[Troy Goode](https://github.com/TroyGoode) ([troygoode@gmail.com](mailto:troygoode@gmail.com))
+
+[downloads-url]: https://npmjs.com/package/cors
+[github-actions-ci-url]: https://github.com/expressjs/cors?query=workflow%3Aci
+[npm-url]: https://npmjs.com/package/cors
diff --git a/src/content/pages/en/resources/middleware/errorhandler.mdx b/src/content/pages/en/resources/middleware/errorhandler.mdx
new file mode 100644
index 0000000000..16839dc50a
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/errorhandler.mdx
@@ -0,0 +1,131 @@
+---
+title: errorhandler middleware
+description: Development-only error handler middleware
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="1.5.2"
+  github="https://github.com/expressjs/errorhandler"
+  npm="https://www.npmjs.com/package/errorhandler"
+/>
+
+Development-only error handler middleware.
+
+This middleware is only intended to be used in a development environment, as
+the _full error stack traces and internal details of any object passed to this
+module_ will be sent back to the client when an error occurs.
+
+When an object is provided to Express as an error, this module will display
+as much about this object as possible, and will do so by using content negotiation
+for the response between HTML, JSON, and plain text.
+
+- When the object is a standard `Error` object, the string provided by the
+  `stack` property will be returned in HTML/text responses.
+- When the object is a non-`Error` object, the result of
+  [util.inspect](https://nodejs.org/api/util.html#util_util_inspect_object_options)
+  will be returned in HTML/text responses.
+- For JSON responses, the result will be an object with all enumerable properties
+  from the object in the response.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install errorhandler
+```
+
+## API
+
+{/* eslint-disable no-unused-vars */}
+
+```js
+var errorhandler = require('errorhandler');
+```
+
+### errorhandler(options)
+
+Create new middleware to handle errors and respond with content negotiation.
+
+#### Options
+
+Error handler accepts these properties in the options object.
+
+##### log
+
+Provide a function to be called with the error and a string representation of
+the error. Can be used to write the error to any desired location, or set to
+`false` to only send the error back in the response. Called as
+`log(err, str, req, res)` where `err` is the `Error` object, `str` is a string
+representation of the error, `req` is the request object and `res` is the
+response object (note, this function is invoked _after_ the response has been
+written).
+
+The default value for this option is `true` unless `process.env.NODE_ENV === 'test'`.
+
+Possible values:
+
+- `true`: Log errors using `console.error(str)`.
+- `false`: Only send the error back in the response.
+- A function: pass the error to a function for handling.
+
+## Examples
+
+### Simple example
+
+Basic example of adding this middleware as the error handler only in development
+with `connect` (`express` also can be used in this example).
+
+```js
+var connect = require('connect');
+var errorhandler = require('errorhandler');
+
+var app = connect();
+
+// assumes NODE_ENV is set by the user
+if (process.env.NODE_ENV === 'development') {
+  // only use in development
+  app.use(errorhandler());
+}
+```
+
+### Custom output location
+
+Sometimes you may want to output the errors to a different location than STDERR
+during development, like a system notification, for example.
+
+{/* eslint-disable handle-callback-err */}
+
+```js
+var connect = require('connect');
+var errorhandler = require('errorhandler');
+var notifier = require('node-notifier');
+
+var app = connect();
+
+// assumes NODE_ENV is set by the user
+if (process.env.NODE_ENV === 'development') {
+  // only use in development
+  app.use(errorhandler({ log: errorNotification }));
+}
+
+function errorNotification(err, str, req) {
+  var title = 'Error in ' + req.method + ' ' + req.url;
+
+  notifier.notify({
+    title: title,
+    message: str,
+  });
+}
+```
+
+## License
+
+[MIT](https://github.com/expressjs/errorhandler/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/errorhandler
diff --git a/src/content/pages/en/resources/middleware/index.md b/src/content/pages/en/resources/middleware/index.md
new file mode 100755
index 0000000000..5f359bf571
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/index.md
@@ -0,0 +1,41 @@
+---
+title: Express middleware
+description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
+---
+
+The Express middleware modules listed here are maintained by the
+[Expressjs team](https://github.com/orgs/expressjs/people).
+
+| Middleware module                                           | Description                                                                                         |
+| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
+| [body-parser](/en/resources/middleware/body-parser)         | Parse HTTP request body.                                                                            |
+| [compression](/en/resources/middleware/compression)         | Compress HTTP responses.                                                                            |
+| [cookie-parser](/en/resources/middleware/cookie-parser)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
+| [cookie-session](/en/resources/middleware/cookie-session)   | Establish cookie-based sessions.                                                                    |
+| [cors](/en/resources/middleware/cors)                       | Enable cross-origin resource sharing (CORS) with various options.                                   |
+| [errorhandler](/en/resources/middleware/errorhandler)       | Development error-handling/debugging.                                                               |
+| [method-override](/en/resources/middleware/method-override) | Override HTTP methods using header.                                                                 |
+| [morgan](/en/resources/middleware/morgan)                   | HTTP request logger.                                                                                |
+| [multer](/en/resources/middleware/multer)                   | Handle multi-part form data.                                                                        |
+| [response-time](/en/resources/middleware/response-time)     | Record HTTP response time.                                                                          |
+| [serve-favicon](/en/resources/middleware/serve-favicon)     | Serve a favicon.                                                                                    |
+| [serve-index](/en/resources/middleware/serve-index)         | Serve directory listing for a given path.                                                           |
+| [serve-static](/en/resources/middleware/serve-static)       | Serve static files.                                                                                 |
+| [session](/en/resources/middleware/session)                 | Establish server-based sessions (development only).                                                 |
+| [timeout](/en/resources/middleware/timeout)                 | Set a timeout perioHTTP request processing.                                                         |
+| [vhost](/en/resources/middleware/vhost)                     | Create virtual domains.                                                                             |
+
+## Additional middleware modules
+
+These are some additional popular middleware modules.
+
+<Alert type="warning">
+  This information refers to third-party sites, products, or modules that are not maintained by the
+  Expressjs team. Listing here does not constitute an endorsement or recommendation from the
+  Expressjs project team.
+</Alert>
+
+| Middleware module                                   | Description                                                                                                                                  |
+| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| [helmet](https://github.com/helmetjs/helmet)        | Helps secure your apps by setting various HTTP headers.                                                                                      |
+| [passport](https://github.com/jaredhanson/passport) | Authentication using "strategies" such as OAuth, OpenID and many others. See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/src/content/pages/en/resources/middleware/method-override.mdx b/src/content/pages/en/resources/middleware/method-override.mdx
new file mode 100644
index 0000000000..6f2394a3e3
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/method-override.mdx
@@ -0,0 +1,184 @@
+---
+title: method-override middleware
+description: Override HTTP verbs
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="3.0.0"
+  github="https://github.com/expressjs/method-override"
+  npm="https://www.npmjs.com/package/method-override"
+/>
+
+Lets you use HTTP verbs such as PUT or DELETE in places where the client doesn't support it.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install method-override
+```
+
+## API
+
+**NOTE** It is very important that this module is used **before** any module that
+needs to know the method of the request (for example, it _must_ be used prior to
+the `csurf` module).
+
+### methodOverride(getter, options)
+
+Create a new middleware function to override the `req.method` property with a new
+value. This value will be pulled from the provided `getter`.
+
+- `getter` - The getter to use to look up the overridden request method for the request. (default: `X-HTTP-Method-Override`)
+- `options.methods` - The allowed methods the original request must be in to check for a method override value. (default: `['POST']`)
+
+If the found method is supported by node.js core, then `req.method` will be set to
+this value, as if it has originally been that value. The previous `req.method`
+value will be stored in `req.originalMethod`.
+
+#### getter
+
+This is the method of getting the override value from the request. If a function is provided,
+the `req` is passed as the first argument, the `res` as the second argument and the method is
+expected to be returned. If a string is provided, the string is used to look up the method
+with the following rules:
+
+- If the string starts with `X-`, then it is treated as the name of a header and that header
+  is used for the method override. If the request contains the same header multiple times, the
+  first occurrence is used.
+- All other strings are treated as a key in the URL query string.
+
+#### options.methods
+
+This allows the specification of what methods(s) the request _MUST_ be in in order to check for
+the method override value. This defaults to only `POST` methods, which is the only method the
+override should arrive in. More methods may be specified here, but it may introduce security
+issues and cause weird behavior when requests travel through caches. This value is an array
+of methods in upper-case. `null` can be specified to allow all methods.
+
+## Examples
+
+### override using a header
+
+To use a header to override the method, specify the header name
+as a string argument to the `methodOverride` function. To then make
+the call, send a `POST` request to a URL with the overridden method
+as the value of that header. This method of using a header would
+typically be used in conjunction with `XMLHttpRequest` on implementations
+that do not support the method you are trying to use.
+
+```js
+const express = require('express');
+const methodOverride = require('method-override');
+const app = express();
+
+// override with the X-HTTP-Method-Override header in the request
+app.use(methodOverride('X-HTTP-Method-Override'));
+```
+
+Example call with header override using `XMLHttpRequest`:
+
+{/* eslint-env browser */}
+
+```js
+const xhr = new XMLHttpRequest();
+xhr.onload = onload;
+xhr.open('post', '/resource', true);
+xhr.setRequestHeader('X-HTTP-Method-Override', 'DELETE');
+xhr.send();
+
+function onload() {
+  alert('got response: ' + this.responseText);
+}
+```
+
+### override using a query value
+
+To use a query string value to override the method, specify the query
+string key as a string argument to the `methodOverride` function. To
+then make the call, send a `POST` request to a URL with the overridden
+method as the value of that query string key. This method of using a
+query value would typically be used in conjunction with plain HTML
+`<form>` elements when trying to support legacy browsers but still use
+newer methods.
+
+```js
+const express = require('express');
+const methodOverride = require('method-override');
+const app = express();
+
+// override with POST having ?_method=DELETE
+app.use(methodOverride('_method'));
+```
+
+Example call with query override using HTML `<form>`:
+
+```html
+<form method="POST" action="/resource?_method=DELETE">
+  <button type="submit">Delete resource</button>
+</form>
+```
+
+### multiple format support
+
+```js
+const express = require('express');
+const methodOverride = require('method-override');
+const app = express();
+
+// override with different headers; last one takes precedence
+app.use(methodOverride('X-HTTP-Method')); //          Microsoft
+app.use(methodOverride('X-HTTP-Method-Override')); // Google/GData
+app.use(methodOverride('X-Method-Override')); //      IBM
+```
+
+### custom logic
+
+You can implement any kind of custom logic with a function for the `getter`. The following
+implements the logic for looking in `req.body` that was in `method-override@1`:
+
+```js
+const bodyParser = require('body-parser');
+const express = require('express');
+const methodOverride = require('method-override');
+const app = express();
+
+// NOTE: when using req.body, you must fully parse the request body
+//       before you call methodOverride() in your middleware stack,
+//       otherwise req.body will not be populated.
+app.use(bodyParser.urlencoded());
+app.use(
+  methodOverride(function (req, res) {
+    if (req.body && typeof req.body === 'object' && '_method' in req.body) {
+      // look in urlencoded POST bodies and delete it
+      const method = req.body._method;
+      delete req.body._method;
+      return method;
+    }
+  })
+);
+```
+
+Example call with query override using HTML `<form>`:
+
+```html
+{/* enctype must be set to the type you will parse before methodOverride() */}
+<form method="POST" action="/resource" enctype="application/x-www-form-urlencoded">
+  <input type="hidden" name="_method" value="DELETE" />
+  <button type="submit">Delete resource</button>
+</form>
+```
+
+## License
+
+[MIT](https://github.com/expressjs/method-override/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/method-override
+[travis-url]: https://travis-ci.org/expressjs/method-override
+[downloads-url]: https://npmjs.org/package/method-override
diff --git a/src/content/pages/en/resources/middleware/morgan.mdx b/src/content/pages/en/resources/middleware/morgan.mdx
new file mode 100644
index 0000000000..4568ece4b5
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/morgan.mdx
@@ -0,0 +1,452 @@
+---
+title: morgan middleware
+description: HTTP request logger middleware for Node.js
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="1.10.1"
+  github="https://github.com/expressjs/morgan"
+  npm="https://www.npmjs.com/package/morgan"
+/>
+
+HTTP request logger middleware for node.js
+
+> Named after [Dexter](http://en.wikipedia.org/wiki/Dexter_Morgan), a show you should not watch until completion.
+
+## Installation
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install morgan
+```
+
+## API
+
+{/* eslint-disable no-unused-vars */}
+
+```js
+var morgan = require('morgan');
+```
+
+### morgan(format, options)
+
+Create a new morgan logger middleware function using the given `format` and `options`.
+The `format` argument may be a string of a predefined name (see below for the names),
+a string of a format string, or a function that will produce a log entry.
+
+The `format` function will be called with three arguments `tokens`, `req`, and `res`,
+where `tokens` is an object with all defined tokens, `req` is the HTTP request and `res`
+is the HTTP response. The function is expected to return a string that will be the log
+line, or `undefined` / `null` to skip logging.
+
+#### Using a predefined format string
+
+{/* eslint-disable no-undef */}
+
+```js
+morgan('tiny');
+```
+
+#### Using format string of predefined tokens
+
+{/* eslint-disable no-undef */}
+
+```js
+morgan(':method :url :status :res[content-length] - :response-time ms');
+```
+
+#### Using a custom format function
+
+{/* eslint-disable no-undef */}
+
+```js
+morgan(function (tokens, req, res) {
+  return [
+    tokens.method(req, res),
+    tokens.url(req, res),
+    tokens.status(req, res),
+    tokens.res(req, res, 'content-length'), '-',
+    tokens['response-time'](https://github.com/expressjs/morgan/blob/HEAD/req, res), 'ms'
+  ].join(' ')
+})
+```
+
+#### Options
+
+Morgan accepts these properties in the options object.
+
+##### immediate
+
+Write log line on request instead of response. This means that a requests will
+be logged even if the server crashes, _but data from the response (like the
+response code, content length, etc.) cannot be logged_.
+
+##### skip
+
+Function to determine if logging is skipped, defaults to `false`. This function
+will be called as `skip(req, res)`.
+
+{/* eslint-disable no-undef */}
+
+```js
+// EXAMPLE: only log error responses
+morgan('combined', {
+  skip: function (req, res) {
+    return res.statusCode < 400;
+  },
+});
+```
+
+##### stream
+
+Output stream for writing log lines, defaults to `process.stdout`.
+
+#### Predefined Formats
+
+There are various pre-defined formats provided:
+
+##### combined
+
+Standard Apache combined log output.
+
+```
+:remote-addr - :remote-user [:date[clf]] ":method :url HTTP/:http-version" :status :res[content-length] ":referrer" ":user-agent"
+# will output
+::1 - - [27/Nov/2024:06:21:42 +0000] "GET /combined HTTP/1.1" 200 2 "-" "curl/8.7.1"
+```
+
+##### common
+
+Standard Apache common log output.
+
+```
+:remote-addr - :remote-user [:date[clf]] ":method :url HTTP/:http-version" :status :res[content-length]
+# will output
+::1 - - [27/Nov/2024:06:21:46 +0000] "GET /common HTTP/1.1" 200 2
+```
+
+##### dev
+
+Concise output colored by response status for development use. The `:status`
+token will be colored green for success codes, red for server error codes,
+yellow for client error codes, cyan for redirection codes, and uncolored
+for information codes.
+
+```
+:method :url :status :response-time ms - :res[content-length]
+# will output
+GET /dev 200 0.224 ms - 2
+```
+
+##### short
+
+Shorter than default, also including response time.
+
+```
+:remote-addr :remote-user :method :url HTTP/:http-version :status :res[content-length] - :response-time ms
+# will output
+::1 - GET /short HTTP/1.1 200 2 - 0.283 ms
+```
+
+##### tiny
+
+The minimal output.
+
+```
+:method :url :status :res[content-length] - :response-time ms
+# will output
+GET /tiny 200 2 - 0.188 ms
+```
+
+#### Tokens
+
+##### Creating new tokens
+
+To define a token, simply invoke `morgan.token()` with the name and a callback function.
+This callback function is expected to return a string value. The value returned is then
+available as ":type" in this case:
+
+{/* eslint-disable no-undef */}
+
+```js
+morgan.token('type', function (req, res) {
+  return req.headers['content-type'];
+});
+```
+
+Calling `morgan.token()` using the same name as an existing token will overwrite that
+token definition.
+
+The token function is expected to be called with the arguments `req` and `res`, representing
+the HTTP request and HTTP response. Additionally, the token can accept further arguments of
+it's choosing to customize behavior.
+
+##### :date[format]
+
+The current date and time in UTC. The available formats are:
+
+- `clf` for the common log format (`"10/Oct/2000:13:55:36 +0000"`)
+- `iso` for the common ISO 8601 date time format (`2000-10-10T13:55:36.000Z`)
+- `web` for the common RFC 1123 date time format (`Tue, 10 Oct 2000 13:55:36 GMT`)
+
+If no format is given, then the default is `web`.
+
+##### :http-version
+
+The HTTP version of the request.
+
+##### :method
+
+The HTTP method of the request.
+
+##### :pid
+
+The process ID of the Node.js process handling the request.
+
+##### :referrer
+
+The Referrer header of the request. This will use the standard mis-spelled Referer header if exists, otherwise Referrer.
+
+##### :remote-addr
+
+The remote address of the request. This will use `req.ip`, otherwise the standard `req.connection.remoteAddress` value (socket address).
+
+##### :remote-user
+
+The user authenticated as part of Basic auth for the request.
+
+##### :req[header]
+
+The given `header` of the request. If the header is not present, the
+value will be displayed as `"-"` in the log.
+
+##### :res[header]
+
+The given `header` of the response. If the header is not present, the
+value will be displayed as `"-"` in the log.
+
+##### :response-time[digits]
+
+The time between the request coming into `morgan` and when the response
+headers are written, in milliseconds.
+
+The `digits` argument is a number that specifies the number of digits to
+include on the number, defaulting to `3`, which provides microsecond precision.
+
+##### :status
+
+The status code of the response.
+
+If the request/response cycle completes before a response was sent to the
+client (for example, the TCP socket closed prematurely by a client aborting
+the request), then the status will be empty (displayed as `"-"` in the log).
+
+##### :total-time[digits]
+
+The time between the request coming into `morgan` and when the response
+has finished being written out to the connection, in milliseconds.
+
+The `digits` argument is a number that specifies the number of digits to
+include on the number, defaulting to `3`, which provides microsecond precision.
+
+##### :url
+
+The URL of the request. This will use `req.originalUrl` if exists, otherwise `req.url`.
+
+##### :user-agent
+
+The contents of the User-Agent header of the request.
+
+### morgan.compile(format)
+
+Compile a format string into a `format` function for use by `morgan`. A format string
+is a string that represents a single log line and can utilize token syntax.
+Tokens are references by `:token-name`. If tokens accept arguments, they can
+be passed using `[]`, for example: `:token-name[pretty]` would pass the string
+`'pretty'` as an argument to the token `token-name`.
+
+The function returned from `morgan.compile` takes three arguments `tokens`, `req`, and
+`res`, where `tokens` is object with all defined tokens, `req` is the HTTP request and
+`res` is the HTTP response. The function will return a string that will be the log line,
+or `undefined` / `null` to skip logging.
+
+Normally formats are defined using `morgan.format(name, format)`, but for certain
+advanced uses, this compile function is directly available.
+
+## Examples
+
+### express/connect
+
+Sample app that will log all request in the Apache combined format to STDOUT
+
+```js
+var express = require('express');
+var morgan = require('morgan');
+
+var app = express();
+
+app.use(morgan('combined'));
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+### vanilla http server
+
+Sample app that will log all request in the Apache combined format to STDOUT
+
+```js
+var finalhandler = require('finalhandler');
+var http = require('http');
+var morgan = require('morgan');
+
+// create "middleware"
+var logger = morgan('combined');
+
+http.createServer(function (req, res) {
+  var done = finalhandler(req, res);
+  logger(req, res, function (err) {
+    if (err) return done(err);
+
+    // respond to request
+    res.setHeader('content-type', 'text/plain');
+    res.end('hello, world!');
+  });
+});
+```
+
+### write logs to a file
+
+#### single file
+
+Sample app that will log all requests in the Apache combined format to the file
+`access.log`.
+
+```js
+var express = require('express');
+var fs = require('fs');
+var morgan = require('morgan');
+var path = require('path');
+
+var app = express();
+
+// create a write stream (in append mode)
+var accessLogStream = fs.createWriteStream(path.join(__dirname, 'access.log'), { flags: 'a' });
+
+// setup the logger
+app.use(morgan('combined', { stream: accessLogStream }));
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+#### log file rotation
+
+Sample app that will log all requests in the Apache combined format to one log
+file per day in the `log/` directory using the
+[rotating-file-stream module](https://www.npmjs.com/package/rotating-file-stream).
+
+```js
+var express = require('express');
+var morgan = require('morgan');
+var path = require('path');
+var rfs = require('rotating-file-stream'); // version 2.x
+
+var app = express();
+
+// create a rotating write stream
+var accessLogStream = rfs.createStream('access.log', {
+  interval: '1d', // rotate daily
+  path: path.join(__dirname, 'log'),
+});
+
+// setup the logger
+app.use(morgan('combined', { stream: accessLogStream }));
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+### split / dual logging
+
+The `morgan` middleware can be used as many times as needed, enabling
+combinations like:
+
+- Log entry on request and one on response
+- Log all requests to file, but errors to console
+- ... and more!
+
+Sample app that will log all requests to a file using Apache format, but
+error responses are logged to the console:
+
+```js
+var express = require('express');
+var fs = require('fs');
+var morgan = require('morgan');
+var path = require('path');
+
+var app = express();
+
+// log only 4xx and 5xx responses to console
+app.use(
+  morgan('dev', {
+    skip: function (req, res) {
+      return res.statusCode < 400;
+    },
+  })
+);
+
+// log all requests to access.log
+app.use(
+  morgan('common', {
+    stream: fs.createWriteStream(path.join(__dirname, 'access.log'), { flags: 'a' }),
+  })
+);
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+### use custom token formats
+
+Sample app that will use custom token formats. This adds an ID to all requests and displays it using the `:id` token.
+
+```js
+var express = require('express');
+var morgan = require('morgan');
+var uuid = require('node-uuid');
+
+morgan.token('id', function getId(req) {
+  return req.id;
+});
+
+var app = express();
+
+app.use(assignId);
+app.use(morgan(':id :method :url :response-time'));
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+
+function assignId(req, res, next) {
+  req.id = uuid.v4();
+  next();
+}
+```
+
+## License
+
+[MIT](https://github.com/expressjs/morgan/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/morgan
diff --git a/src/content/pages/en/resources/middleware/multer.mdx b/src/content/pages/en/resources/middleware/multer.mdx
new file mode 100644
index 0000000000..c1dcd5b9c2
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/multer.mdx
@@ -0,0 +1,355 @@
+---
+title: multer middleware
+description: Middleware for handling multipart/form-data
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.1.1"
+  github="https://github.com/expressjs/multer"
+  npm="https://www.npmjs.com/package/multer"
+/>
+
+Multer is a node.js middleware for handling `multipart/form-data`, which is primarily used for uploading files. It is written
+on top of [busboy](https://github.com/mscdex/busboy) for maximum efficiency.
+
+**NOTE**: Multer will not process any form which is not multipart (`multipart/form-data`).
+
+## Translations
+
+This README is also available in other languages:
+
+|                                                                                |                 |
+| ------------------------------------------------------------------------------ | --------------- |
+| [العربية](https://github.com/expressjs/multer/blob/main/doc/README-ar.md)      | Arabic          |
+| [简体中文](https://github.com/expressjs/multer/blob/main/doc/README-zh-cn.md)  | Chinese         |
+| [Français](https://github.com/expressjs/multer/blob/main/doc/README-fr.md)     | French          |
+| [한국어](https://github.com/expressjs/multer/blob/main/doc/README-ko.md)       | Korean          |
+| [Português](https://github.com/expressjs/multer/blob/main/doc/README-pt-br.md) | Portuguese (BR) |
+| [Русский язык](https://github.com/expressjs/multer/blob/main/doc/README-ru.md) | Russian         |
+| [Español](https://github.com/expressjs/multer/blob/main/doc/README-es.md)      | Spanish         |
+| [O'zbek tili](https://github.com/expressjs/multer/blob/main/doc/README-uz.md)  | Uzbek           |
+| [Việt Nam](https://github.com/expressjs/multer/blob/main/doc/README-vi.md)     | Vietnamese      |
+| [Türkçe](https://github.com/expressjs/multer/blob/main/doc/README-tr.md)       | Turkish         |
+
+## Installation
+
+```sh
+$ npm install multer
+```
+
+## Usage
+
+Multer adds a `body` object and a `file` or `files` object to the `request` object. The `body` object contains the values of the text fields of the form, the `file` or `files` object contains the files uploaded via the form.
+
+Basic usage example:
+
+Don't forget the `enctype="multipart/form-data"` in your form.
+
+```html
+<form action="/profile" method="post" enctype="multipart/form-data">
+  <input type="file" name="avatar" />
+</form>
+```
+
+```javascript
+const express = require('express');
+const multer = require('multer');
+const upload = multer({ dest: 'uploads/' });
+
+const app = express();
+
+app.post('/profile', upload.single('avatar'), function (req, res, next) {
+  // req.file is the `avatar` file
+  // req.body will hold the text fields, if there were any
+});
+
+app.post('/photos/upload', upload.array('photos', 12), function (req, res, next) {
+  // req.files is array of `photos` files
+  // req.body will contain the text fields, if there were any
+});
+
+const uploadMiddleware = upload.fields([
+  { name: 'avatar', maxCount: 1 },
+  { name: 'gallery', maxCount: 8 },
+]);
+app.post('/cool-profile', uploadMiddleware, function (req, res, next) {
+  // req.files is an object (String -> Array) where fieldname is the key, and the value is array of files
+  //
+  // e.g.
+  //  req.files['avatar'][0] -> File
+  //  req.files['gallery'] -> Array
+  //
+  // req.body will contain the text fields, if there were any
+});
+```
+
+In case you need to handle a text-only multipart form, you should use the `.none()` method:
+
+```javascript
+const express = require('express');
+const app = express();
+const multer = require('multer');
+const upload = multer();
+
+app.post('/profile', upload.none(), function (req, res, next) {
+  // req.body contains the text fields
+});
+```
+
+Here's an example on how multer is used in a HTML form. Take special note of the `enctype="multipart/form-data"` and `name="uploaded_file"` fields:
+
+```html
+<form action="/stats" enctype="multipart/form-data" method="post">
+  <div class="form-group">
+    <input type="file" class="form-control-file" name="uploaded_file" />
+    <input type="text" class="form-control" placeholder="Number of speakers" name="nspeakers" />
+    <input type="submit" value="Get me the stats!" class="btn btn-default" />
+  </div>
+</form>
+```
+
+Then in your javascript file you would add these lines to access both the file and the body. It is important that you use the `name` field value from the form in your upload function. This tells multer which field on the request it should look for the files in. If these fields aren't the same in the HTML form and on your server, your upload will fail:
+
+```javascript
+const multer = require('multer');
+const upload = multer({ dest: './public/data/uploads/' });
+app.post('/stats', upload.single('uploaded_file'), function (req, res) {
+  // req.file is the name of your file in the form above, here 'uploaded_file'
+  // req.body will hold the text fields, if there were any
+  console.log(req.file, req.body);
+});
+```
+
+## API
+
+### File information
+
+Each file contains the following information:
+
+| Key            | Description                                   | Note            |
+| -------------- | --------------------------------------------- | --------------- |
+| `fieldname`    | Field name specified in the form              |
+| `originalname` | Name of the file on the user's computer       |
+| `encoding`     | Encoding type of the file                     |
+| `mimetype`     | Mime type of the file                         |
+| `size`         | Size of the file in bytes                     |
+| `destination`  | The folder to which the file has been saved   | `DiskStorage`   |
+| `filename`     | The name of the file within the `destination` | `DiskStorage`   |
+| `path`         | The full path to the uploaded file            | `DiskStorage`   |
+| `buffer`       | A `Buffer` of the entire file                 | `MemoryStorage` |
+
+### `multer(opts)`
+
+Multer accepts an options object, the most basic of which is the `dest`
+property, which tells Multer where to upload the files. In case you omit the
+options object, the files will be kept in memory and never written to disk.
+
+By default, Multer will rename the files so as to avoid naming conflicts. The
+renaming function can be customized according to your needs.
+
+The following are the options that can be passed to Multer.
+
+| Key                 | Description                                                                                                                                                                |
+| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dest` or `storage` | Where to store the files                                                                                                                                                   |
+| `fileFilter`        | Function to control which files are accepted                                                                                                                               |
+| `limits`            | Limits of the uploaded data                                                                                                                                                |
+| `preservePath`      | Keep the full path of files instead of just the base name                                                                                                                  |
+| `defParamCharset`   | Default character set to use for values of part header parameters (e.g. filename) that are not extended parameters (that contain an explicit charset). Default: `'latin1'` |
+
+In an average web app, only `dest` might be required, and configured as shown in
+the following example.
+
+```javascript
+const upload = multer({ dest: 'uploads/' });
+```
+
+If you want more control over your uploads, you'll want to use the `storage`
+option instead of `dest`. Multer ships with storage engines `DiskStorage`
+and `MemoryStorage`; More engines are available from third parties.
+
+#### `.single(fieldname)`
+
+Accept a single file with the name `fieldname`. The single file will be stored
+in `req.file`.
+
+#### `.array(fieldname[, maxCount])`
+
+Accept an array of files, all with the name `fieldname`. Optionally error out if
+more than `maxCount` files are uploaded. The array of files will be stored in
+`req.files`.
+
+#### `.fields(fields)`
+
+Accept a mix of files, specified by `fields`. An object with arrays of files
+will be stored in `req.files`.
+
+`fields` should be an array of objects with `name` and optionally a `maxCount`.
+Example:
+
+```javascript
+[
+  { name: 'avatar', maxCount: 1 },
+  { name: 'gallery', maxCount: 8 },
+];
+```
+
+#### `.none()`
+
+Accept only text fields. If any file upload is made, error with code
+"LIMIT_UNEXPECTED_FILE" will be issued.
+
+#### `.any()`
+
+Accepts all files that comes over the wire. An array of files will be stored in
+`req.files`.
+
+**WARNING:** Make sure that you always handle the files that a user uploads.
+Never add multer as a global middleware since a malicious user could upload
+files to a route that you didn't anticipate. Only use this function on routes
+where you are handling the uploaded files.
+
+### `storage`
+
+#### `DiskStorage`
+
+The disk storage engine gives you full control on storing files to disk.
+
+```javascript
+const storage = multer.diskStorage({
+  destination: function (req, file, cb) {
+    cb(null, '/tmp/my-uploads');
+  },
+  filename: function (req, file, cb) {
+    const uniqueSuffix = Date.now() + '-' + Math.round(Math.random() * 1e9);
+    cb(null, file.fieldname + '-' + uniqueSuffix);
+  },
+});
+
+const upload = multer({ storage: storage });
+```
+
+There are two options available, `destination` and `filename`. They are both
+functions that determine where the file should be stored.
+
+`destination` is used to determine within which folder the uploaded files should
+be stored. This can also be given as a `string` (e.g. `'/tmp/uploads'`). If no
+`destination` is given, the operating system's default directory for temporary
+files is used.
+
+**Note:** You are responsible for creating the directory when providing
+`destination` as a function. When passing a string, multer will make sure that
+the directory is created for you.
+
+`filename` is used to determine what the file should be named inside the folder.
+If no `filename` is given, each file will be given a random name that doesn't
+include any file extension.
+
+**Note:** Multer will not append any file extension for you, your function
+should return a filename complete with a file extension.
+
+Each function gets passed both the request (`req`) and some information about
+the file (`file`) to aid with the decision.
+
+Note that `req.body` might not have been fully populated yet. It depends on the
+order that the client transmits fields and files to the server.
+
+For understanding the calling convention used in the callback (needing to pass
+null as the first param), refer to
+[Node.js error handling](https://web.archive.org/web/20220417042018/https://www.joyent.com/node-js/production/design/errors)
+
+#### `MemoryStorage`
+
+The memory storage engine stores the files in memory as `Buffer` objects. It
+doesn't have any options.
+
+```javascript
+const storage = multer.memoryStorage();
+const upload = multer({ storage: storage });
+```
+
+When using memory storage, the file info will contain a field called
+`buffer` that contains the entire file.
+
+**WARNING**: Uploading very large files, or relatively small files in large
+numbers very quickly, can cause your application to run out of memory when
+memory storage is used.
+
+### `limits`
+
+An object specifying the size limits of the following optional properties. Multer passes this object into busboy directly, and the details of the properties can be found on [busboy's page](https://github.com/mscdex/busboy#busboy-methods).
+
+The following integer values are available:
+
+| Key             | Description                                                             | Default   |
+| --------------- | ----------------------------------------------------------------------- | --------- |
+| `fieldNameSize` | Max field name size                                                     | 100 bytes |
+| `fieldSize`     | Max field value size (in bytes)                                         | 1MB       |
+| `fields`        | Max number of non-file fields                                           | Infinity  |
+| `fileSize`      | For multipart forms, the max file size (in bytes)                       | Infinity  |
+| `files`         | For multipart forms, the max number of file fields                      | Infinity  |
+| `parts`         | For multipart forms, the max number of parts (fields + files)           | Infinity  |
+| `headerPairs`   | For multipart forms, the max number of header key=>value pairs to parse | 2000      |
+
+Specifying the limits can help protect your site against denial of service (DoS) attacks.
+
+### `fileFilter`
+
+Set this to a function to control which files should be uploaded and which
+should be skipped. The function should look like this:
+
+```javascript
+function fileFilter(req, file, cb) {
+  // The function should call `cb` with a boolean
+  // to indicate if the file should be accepted
+
+  // To reject this file pass `false`, like so:
+  cb(null, false);
+
+  // To accept the file pass `true`, like so:
+  cb(null, true);
+
+  // You can always pass an error if something goes wrong:
+  cb(new Error("I don't have a clue!"));
+}
+```
+
+## Error handling
+
+When encountering an error, Multer will delegate the error to Express. You can
+display a nice error page using [the standard express way](http://expressjs.com/guide/error-handling.html).
+
+If you want to catch errors specifically from Multer, you can call the
+middleware function by yourself. Also, if you want to catch only [the Multer errors](https://github.com/expressjs/multer/blob/main/lib/multer-error.js), you can use the `MulterError` class that is attached to the `multer` object itself (e.g. `err instanceof multer.MulterError`).
+
+```javascript
+const multer = require('multer');
+const upload = multer().single('avatar');
+
+app.post('/profile', function (req, res) {
+  upload(req, res, function (err) {
+    if (err instanceof multer.MulterError) {
+      // A Multer error occurred when uploading.
+    } else if (err) {
+      // An unknown error occurred when uploading.
+    }
+
+    // Everything went fine.
+  });
+});
+```
+
+## Custom storage engine
+
+For information on how to build your own storage engine, see [Multer Storage Engine](https://github.com/expressjs/multer/blob/main/StorageEngine.md).
+
+## License
+
+[MIT](https://github.com/expressjs/multer/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/multer
+[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/multer/badge
+[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/multer
diff --git a/src/content/pages/en/resources/middleware/response-time.mdx b/src/content/pages/en/resources/middleware/response-time.mdx
new file mode 100644
index 0000000000..588ec099d7
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/response-time.mdx
@@ -0,0 +1,141 @@
+---
+title: response-time middleware
+description: Response time for Node.js servers
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.3.4"
+  github="https://github.com/expressjs/response-time"
+  npm="https://www.npmjs.com/package/response-time"
+/>
+
+Response time for Node.js servers.
+
+This module creates a middleware that records the response time for
+requests in HTTP servers. The "response time" is defined here as the
+elapsed time from when a request enters this middleware to when the
+headers are written out to the client.
+
+## Installation
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install response-time
+```
+
+## API
+
+{/* eslint-disable no-unused-vars */}
+
+```js
+var responseTime = require('response-time');
+```
+
+### responseTime([options])
+
+Create a middleware that adds a `X-Response-Time` header to responses. If
+you don't want to use this module to automatically set a header, please
+see the section about [`responseTime(fn)`](#responsetimefn).
+
+#### Options
+
+The `responseTime` function accepts an optional `options` object that may
+contain any of the following keys:
+
+##### digits
+
+The fixed number of digits to include in the output, which is always in
+milliseconds, defaults to `3` (ex: `2.300ms`).
+
+##### header
+
+The name of the header to set, defaults to `X-Response-Time`.
+
+##### suffix
+
+Boolean to indicate if units of measurement suffix should be added to
+the output, defaults to `true` (ex: `2.300ms` vs `2.300`).
+
+### responseTime(fn)
+
+Create a new middleware that records the response time of a request and
+makes this available to your own function `fn`. The `fn` argument will be
+invoked as `fn(req, res, time)`, where `time` is a number in milliseconds.
+
+## Examples
+
+### express/connect
+
+```js
+var express = require('express');
+var responseTime = require('response-time');
+
+var app = express();
+
+app.use(responseTime());
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+### vanilla http server
+
+```js
+var finalhandler = require('finalhandler');
+var http = require('http');
+var responseTime = require('response-time');
+
+// create "middleware"
+var _responseTime = responseTime();
+
+http.createServer(function (req, res) {
+  var done = finalhandler(req, res);
+  _responseTime(req, res, function (err) {
+    if (err) return done(err);
+
+    // respond to request
+    res.setHeader('content-type', 'text/plain');
+    res.end('hello, world!');
+  });
+});
+```
+
+### response time metrics
+
+```js
+var express = require('express');
+var responseTime = require('response-time');
+var StatsD = require('node-statsd');
+
+var app = express();
+var stats = new StatsD();
+
+stats.socket.on('error', function (error) {
+  console.error(error.stack);
+});
+
+app.use(
+  responseTime(function (req, res, time) {
+    var stat = (req.method + req.url).toLowerCase().replace(/[:.]/g, '').replace(/\//g, '_');
+    stats.timing(stat, time);
+  })
+);
+
+app.get('/', function (req, res) {
+  res.send('hello, world!');
+});
+```
+
+## License
+
+[MIT](https://github.com/expressjs/response-time/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/response-time
+[node-url]: https://nodejs.org/en/download
diff --git a/src/content/pages/en/resources/middleware/serve-favicon.mdx b/src/content/pages/en/resources/middleware/serve-favicon.mdx
new file mode 100644
index 0000000000..73a788eb06
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/serve-favicon.mdx
@@ -0,0 +1,136 @@
+---
+title: serve-favicon middleware
+description: Favicon serving middleware with caching
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.5.1"
+  github="https://github.com/expressjs/serve-favicon"
+  npm="https://www.npmjs.com/package/serve-favicon"
+/>
+
+Node.js middleware for serving a favicon.
+
+A favicon is a visual cue that client software, like browsers, use to identify
+a site. For an example and more information, please visit
+[the Wikipedia article on favicons](https://en.wikipedia.org/wiki/Favicon).
+
+Why use this module?
+
+- User agents request `favicon.ico` frequently and indiscriminately, so you
+  may wish to exclude these requests from your logs by using this middleware
+  before your logger middleware.
+- This module caches the icon in memory to improve performance by skipping
+  disk access.
+- This module provides an `ETag` based on the contents of the icon, rather
+  than file system properties.
+- This module will serve with the most compatible `Content-Type`.
+
+**Note** This module is exclusively for serving the "default, implicit favicon",
+which is `GET /favicon.ico`. For additional vendor-specific icons that require
+HTML markup, additional middleware is required to serve the relevant files, for
+example [serve-static](https://npmjs.org/package/serve-static).
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install serve-favicon
+```
+
+## API
+
+### favicon(path, options)
+
+Create new middleware to serve a favicon from the given `path` to a favicon file.
+`path` may also be a `Buffer` of the icon to serve.
+
+#### Options
+
+Serve favicon accepts these properties in the options object.
+
+##### maxAge
+
+The `cache-control` `max-age` directive in `ms`, defaulting to 1 year. This can
+also be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
+module.
+
+## Examples
+
+Typically this middleware will come very early in your stack (maybe even first)
+to avoid processing any other middleware if we already know the request is for
+`/favicon.ico`.
+
+### express
+
+```javascript
+var express = require('express');
+var favicon = require('serve-favicon');
+var path = require('path');
+
+var app = express();
+app.use(favicon(path.join(__dirname, 'public', 'favicon.ico')));
+
+// Add your routes here, etc.
+
+app.listen(3000);
+```
+
+### connect
+
+```javascript
+var connect = require('connect');
+var favicon = require('serve-favicon');
+var path = require('path');
+
+var app = connect();
+app.use(favicon(path.join(__dirname, 'public', 'favicon.ico')));
+
+// Add your middleware here, etc.
+
+app.listen(3000);
+```
+
+### vanilla http server
+
+This middleware can be used anywhere, even outside express/connect. It takes
+`req`, `res`, and `callback`.
+
+```javascript
+var http = require('http');
+var favicon = require('serve-favicon');
+var finalhandler = require('finalhandler');
+var path = require('path');
+
+var _favicon = favicon(path.join(__dirname, 'public', 'favicon.ico'));
+
+var server = http.createServer(function onRequest(req, res) {
+  var done = finalhandler(req, res);
+
+  _favicon(req, res, function onNext(err) {
+    if (err) return done(err);
+
+    // continue to process the request here, etc.
+
+    res.statusCode = 404;
+    res.end('oops');
+  });
+});
+
+server.listen(3000);
+```
+
+## License
+
+[MIT](https://github.com/expressjs/serve-favicon/blob/HEAD/LICENSE)
+
+[downloads-url]: https://npmjs.org/package/serve-favicon
+[npm-url]: https://npmjs.org/package/serve-favicon
+[ossf-scorecard-badge]: https://api.scorecard.dev/projects/github.com/expressjs/serve-favicon/badge
+[ossf-scorecard-visualizer]: https://ossf.github.io/scorecard-visualizer/#/projects/github.com/expressjs/serve-favicon
diff --git a/src/content/pages/en/resources/middleware/serve-index.mdx b/src/content/pages/en/resources/middleware/serve-index.mdx
new file mode 100644
index 0000000000..e6312b927a
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/serve-index.mdx
@@ -0,0 +1,150 @@
+---
+title: serve-index middleware
+description: Serve directory listings
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="1.9.2"
+  github="https://github.com/expressjs/serve-index"
+  npm="https://www.npmjs.com/package/serve-index"
+/>
+
+Serves pages that contain directory listings for a given path.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install serve-index
+```
+
+## API
+
+```js
+var serveIndex = require('serve-index');
+```
+
+### serveIndex(path, options)
+
+Returns middlware that serves an index of the directory in the given `path`.
+
+The `path` is based off the `req.url` value, so a `req.url` of `'/some/dir`
+with a `path` of `'public'` will look at `'public/some/dir'`. If you are using
+something like `express`, you can change the URL "base" with `app.use` (see
+the express example).
+
+#### Options
+
+Serve index accepts these properties in the options object.
+
+##### filter
+
+Apply this filter function to files. Defaults to `false`. The `filter` function
+is called for each file, with the signature `filter(filename, index, files, dir)`
+where `filename` is the name of the file, `index` is the array index, `files` is
+the array of files and `dir` is the absolute path the file is located (and thus,
+the directory the listing is for).
+
+##### hidden
+
+Display hidden (dot) files. Defaults to `false`.
+
+##### icons
+
+Display icons. Defaults to `false`.
+
+##### stylesheet
+
+Optional path to a CSS stylesheet. Defaults to a built-in stylesheet.
+
+##### template
+
+Optional path to an HTML template or a function that will render a HTML
+string. Defaults to a built-in template.
+
+When given a string, the string is used as a file path to load and then the
+following tokens are replaced in templates:
+
+- `{directory}` with the name of the directory.
+- `{files}` with the HTML of an unordered list of file links.
+- `{linked-path}` with the HTML of a link to the directory.
+- `{style}` with the specified stylesheet and embedded images.
+
+When given as a function, the function is called as `template(locals, callback)`
+and it needs to invoke `callback(error, htmlString)`. The following are the
+provided locals:
+
+- `directory` is the directory being displayed (where `/` is the root).
+- `displayIcons` is a Boolean for if icons should be rendered or not.
+- `fileList` is a sorted array of files in the directory. The array contains
+  objects with the following properties:
+  - `name` is the relative name for the file.
+  - `stat` is a `fs.Stats` object for the file.
+- `path` is the full filesystem path to `directory`.
+- `style` is the default stylesheet or the contents of the `stylesheet` option.
+- `viewName` is the view name provided by the `view` option.
+
+##### view
+
+Display mode. `tiles` and `details` are available. Defaults to `tiles`.
+
+## Examples
+
+### Serve directory indexes with vanilla node.js http server
+
+```js
+var finalhandler = require('finalhandler');
+var http = require('http');
+var serveIndex = require('serve-index');
+var serveStatic = require('serve-static');
+
+// Serve directory indexes for public/ftp folder (with icons)
+var index = serveIndex('public/ftp', { icons: true });
+
+// Serve up public/ftp folder files
+var serve = serveStatic('public/ftp');
+
+// Create server
+var server = http.createServer(function onRequest(req, res) {
+  var done = finalhandler(req, res);
+  serve(req, res, function onNext(err) {
+    if (err) return done(err);
+    index(req, res, done);
+  });
+});
+
+// Listen
+server.listen(3000);
+```
+
+### Serve directory indexes with express
+
+```js
+var express = require('express');
+var serveIndex = require('serve-index');
+
+var app = express();
+
+// Serve URLs like /ftp/thing as public/ftp/thing
+// The express.static serves the file contents
+// The serveIndex is this module serving the directory
+app.use('/ftp', express.static('public/ftp'), serveIndex('public/ftp', { icons: true }));
+
+// Listen
+app.listen(3000);
+```
+
+## License
+
+[MIT](https://github.com/expressjs/serve-index/blob/HEAD/LICENSE). The [Silk](http://www.famfamfam.com/lab/icons/silk/) icons
+are created by/copyright of [FAMFAMFAM](http://www.famfamfam.com/).
+
+[appveyor-url]: https://ci.appveyor.com/project/dougwilson/serve-index
+[downloads-url]: https://npmjs.org/package/serve-index
+[npm-url]: https://npmjs.org/package/serve-index
diff --git a/src/content/pages/en/resources/middleware/serve-static.mdx b/src/content/pages/en/resources/middleware/serve-static.mdx
new file mode 100644
index 0000000000..38af6fc42f
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/serve-static.mdx
@@ -0,0 +1,255 @@
+---
+title: serve-static middleware
+description: Serve static files
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="2.2.1"
+  github="https://github.com/expressjs/serve-static"
+  npm="https://www.npmjs.com/package/serve-static"
+/>
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install serve-static
+```
+
+## API
+
+```js
+const serveStatic = require('serve-static');
+```
+
+### serveStatic(root, options)
+
+Create a new middleware function to serve files from within a given root
+directory. The file to serve will be determined by combining `req.url`
+with the provided root directory. When a file is not found, instead of
+sending a 404 response, this module will instead call `next()` to move on
+to the next middleware, allowing for stacking and fall-backs.
+
+#### Options
+
+##### acceptRanges
+
+Enable or disable accepting ranged requests, defaults to true.
+Disabling this will not send `Accept-Ranges` and ignore the contents
+of the `Range` request header.
+
+##### cacheControl
+
+Enable or disable setting `Cache-Control` response header, defaults to
+true. Disabling this will ignore the `immutable` and `maxAge` options.
+
+##### dotfiles
+
+Set how "dotfiles" are treated when encountered. A dotfile is a file
+or directory that begins with a dot ("."). Note this check is done on
+the path itself without checking if the path actually exists on the
+disk. If `root` is specified, only the dotfiles above the root are
+checked (i.e. the root itself can be within a dotfile when set
+to "deny").
+
+- `'allow'` No special treatment for dotfiles.
+- `'deny'` Deny a request for a dotfile and 403/`next()`.
+- `'ignore'` Pretend like the dotfile does not exist and 404/`next()`.
+
+The default value is `'ignore'`.
+
+##### etag
+
+Enable or disable etag generation, defaults to true.
+
+##### extensions
+
+Set file extension fallbacks. When set, if a file is not found, the given
+extensions will be added to the file name and search for. The first that
+exists will be served. Example: `['html', 'htm']`.
+
+The default value is `false`.
+
+##### fallthrough
+
+Set the middleware to have client errors fall-through as just unhandled
+requests, otherwise forward a client error. The difference is that client
+errors like a bad request or a request to a non-existent file will cause
+this middleware to simply `next()` to your next middleware when this value
+is `true`. When this value is `false`, these errors (even 404s), will invoke
+`next(err)`.
+
+Typically `true` is desired such that multiple physical directories can be
+mapped to the same web address or for routes to fill in non-existent files.
+
+The value `false` can be used if this middleware is mounted at a path that
+is designed to be strictly a single file system directory, which allows for
+short-circuiting 404s for less overhead. This middleware will also reply to
+all methods.
+
+The default value is `true`.
+
+##### immutable
+
+Enable or disable the `immutable` directive in the `Cache-Control` response
+header, defaults to `false`. If set to `true`, the `maxAge` option should
+also be specified to enable caching. The `immutable` directive will prevent
+supported clients from making conditional requests during the life of the
+`maxAge` option to check if the file has changed.
+
+##### index
+
+By default this module will send "index.html" files in response to a request
+on a directory. To disable this set `false` or to supply a new index pass a
+string or an array in preferred order.
+
+##### lastModified
+
+Enable or disable `Last-Modified` header, defaults to true. Uses the file
+system's last modified value.
+
+##### maxAge
+
+Provide a max-age in milliseconds for http caching, defaults to 0. This
+can also be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
+module.
+
+##### redirect
+
+Redirect to trailing "/" when the pathname is a dir. Defaults to `true`.
+
+##### setHeaders
+
+Function to set custom headers on response. Alterations to the headers need to
+occur synchronously. The function is called as `fn(res, path, stat)`, where
+the arguments are:
+
+- `res` the response object
+- `path` the file path that is being sent
+- `stat` the stat object of the file that is being sent
+
+## Examples
+
+### Serve files with vanilla node.js http server
+
+```js
+const finalhandler = require('finalhandler');
+const http = require('http');
+const serveStatic = require('serve-static');
+
+// Serve up public/ftp folder
+const serve = serveStatic('public/ftp', { index: ['index.html', 'index.htm'] });
+
+// Create server
+const server = http.createServer((req, res) => {
+  serve(req, res, finalhandler(req, res));
+});
+
+// Listen
+server.listen(3000);
+```
+
+### Serve all files as downloads
+
+```js
+const contentDisposition = require('content-disposition');
+const finalhandler = require('finalhandler');
+const http = require('http');
+const serveStatic = require('serve-static');
+
+// Serve up public/ftp folder
+const serve = serveStatic('public/ftp', {
+  index: false,
+  setHeaders: setHeaders,
+});
+
+// Set header to force download
+function setHeaders(res, path) {
+  res.setHeader('Content-Disposition', contentDisposition(path));
+}
+
+// Create server
+const server = http.createServer((req, res) => {
+  serve(req, res, finalhandler(req, res));
+});
+
+// Listen
+server.listen(3000);
+```
+
+### Serving using express
+
+#### Simple
+
+This is a simple example of using Express.
+
+```js
+const express = require('express');
+const serveStatic = require('serve-static');
+
+const app = express();
+
+app.use(serveStatic('public/ftp', { index: ['default.html', 'default.htm'] }));
+app.listen(3000);
+```
+
+#### Multiple roots
+
+This example shows a simple way to search through multiple directories.
+Files are searched for in `public-optimized/` first, then `public/` second
+as a fallback.
+
+```js
+const express = require('express');
+const path = require('path');
+const serveStatic = require('serve-static');
+
+const app = express();
+
+app.use(serveStatic(path.join(__dirname, 'public-optimized')));
+app.use(serveStatic(path.join(__dirname, 'public')));
+app.listen(3000);
+```
+
+#### Different settings for paths
+
+This example shows how to set a different max age depending on the served
+file. In this example, HTML files are not cached, while everything else
+is for 1 day.
+
+```js
+const express = require('express');
+const path = require('path');
+const serveStatic = require('serve-static');
+
+const app = express();
+
+app.use(
+  serveStatic(path.join(__dirname, 'public'), {
+    maxAge: '1d',
+    setHeaders: setCustomCacheControl,
+  })
+);
+
+app.listen(3000);
+
+function setCustomCacheControl(res, file) {
+  if (path.extname(file) === '.html') {
+    // Custom Cache-Control for HTML files
+    res.setHeader('Cache-Control', 'public, max-age=0');
+  }
+}
+```
+
+## License
+
+[MIT](https://github.com/expressjs/serve-static/blob/HEAD/LICENSE)
+
+[node-url]: https://nodejs.org/en/download/
+[npm-url]: https://npmjs.org/package/serve-static
diff --git a/src/content/pages/en/resources/middleware/session.mdx b/src/content/pages/en/resources/middleware/session.mdx
new file mode 100644
index 0000000000..e014d433c6
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/session.mdx
@@ -0,0 +1,1010 @@
+---
+title: session middleware
+description: Simple session middleware for Express
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="0.1.0"
+  github="https://github.com/expressjs/session"
+  npm="https://www.npmjs.com/package/session"
+/>
+
+## Installation
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install express-session
+```
+
+## API
+
+```js
+var session = require('express-session');
+```
+
+### session(options)
+
+Create a session middleware with the given `options`.
+
+**Note** Session data is _not_ saved in the cookie itself, just the session ID.
+Session data is stored server-side.
+
+**Note** Since version 1.5.0, the [`cookie-parser` middleware](https://www.npmjs.com/package/cookie-parser)
+no longer needs to be used for this module to work. This module now directly reads
+and writes cookies on `req`/`res`. Using `cookie-parser` may result in issues
+if the `secret` is not the same between this module and `cookie-parser`.
+
+**Warning** The default server-side session storage, `MemoryStore`, is _purposely_
+not designed for a production environment. It will leak memory under most
+conditions, does not scale past a single process, and is meant for debugging and
+developing.
+
+For a list of stores, see [compatible session stores](#compatible-session-stores).
+
+#### Options
+
+`express-session` accepts these properties in the options object.
+
+##### cookie
+
+Settings object for the session ID cookie. The default value is
+`{ path: '/', httpOnly: true, secure: false, maxAge: null }`.
+
+In addition to providing a static object, you can also pass a callback function to dynamically generate the cookie options for each request. The callback receives the `req` object as its argument and should return an object containing the cookie settings.
+
+```js
+var app = express();
+app.use(
+  session({
+    secret: 'keyboard cat',
+    resave: false,
+    saveUninitialized: true,
+    cookie: function (req) {
+      var match = req.url.match(/^\/([^/]+)/);
+      return {
+        path: match ? '/' + match[1] : '/',
+        httpOnly: true,
+        secure: req.secure || false,
+        maxAge: 60000,
+      };
+    },
+  })
+);
+```
+
+The following are options that can be set in this object.
+
+##### cookie.domain
+
+Specifies the value for the `Domain` `Set-Cookie` attribute. By default, no domain
+is set, and most clients will consider the cookie to apply to only the current
+domain.
+
+##### cookie.expires
+
+Specifies the `Date` object to be the value for the `Expires` `Set-Cookie` attribute.
+By default, no expiration is set, and most clients will consider this a
+"non-persistent cookie" and will delete it on a condition like exiting a web browser
+application.
+
+**Note** If both `expires` and `maxAge` are set in the options, then the last one
+defined in the object is what is used.
+
+**Note** The `expires` option should not be set directly; instead only use the `maxAge`
+option.
+
+##### cookie.httpOnly
+
+Specifies the `boolean` value for the `HttpOnly` `Set-Cookie` attribute. When truthy,
+the `HttpOnly` attribute is set, otherwise it is not. By default, the `HttpOnly`
+attribute is set.
+
+**Note** be careful when setting this to `true`, as compliant clients will not allow
+client-side JavaScript to see the cookie in `document.cookie`.
+
+##### cookie.maxAge
+
+Specifies the `number` (in milliseconds) to use when calculating the `Expires`
+`Set-Cookie` attribute. This is done by taking the current server time and adding
+`maxAge` milliseconds to the value to calculate an `Expires` datetime. By default,
+no maximum age is set.
+
+**Note** If both `expires` and `maxAge` are set in the options, then the last one
+defined in the object is what is used.
+
+##### cookie.partitioned
+
+Specifies the `boolean` value for the [`Partitioned` `Set-Cookie`](https://github.com/expressjs/session/blob/HEAD/rfc-cutler-httpbis-partitioned-cookies)
+attribute. When truthy, the `Partitioned` attribute is set, otherwise it is not.
+By default, the `Partitioned` attribute is not set.
+
+**Note** This is an attribute that has not yet been fully standardized, and may
+change in the future. This also means many clients may ignore this attribute until
+they understand it.
+
+More information about can be found in [the proposal](https://github.com/privacycg/CHIPS).
+
+##### cookie.path
+
+Specifies the value for the `Path` `Set-Cookie`. By default, this is set to `'/'`, which
+is the root path of the domain.
+
+##### cookie.priority
+
+Specifies the `string` to be the value for the [`Priority` `Set-Cookie` attribute][rfc-west-cookie-priority-00-4.1].
+
+- `'low'` will set the `Priority` attribute to `Low`.
+- `'medium'` will set the `Priority` attribute to `Medium`, the default priority when not set.
+- `'high'` will set the `Priority` attribute to `High`.
+
+More information about the different priority levels can be found in
+[the specification][rfc-west-cookie-priority-00-4.1].
+
+**Note** This is an attribute that has not yet been fully standardized, and may change in the future.
+This also means many clients may ignore this attribute until they understand it.
+
+##### cookie.sameSite
+
+Specifies the `boolean` or `string` to be the value for the `SameSite` `Set-Cookie` attribute.
+By default, this is `false`.
+
+- `true` will set the `SameSite` attribute to `Strict` for strict same site enforcement.
+- `false` will not set the `SameSite` attribute.
+- `'lax'` will set the `SameSite` attribute to `Lax` for lax same site enforcement.
+- `'none'` will set the `SameSite` attribute to `None` for an explicit cross-site cookie.
+- `'strict'` will set the `SameSite` attribute to `Strict` for strict same site enforcement.
+- `'auto'` will set the `SameSite` attribute to `None` for secure connections and `Lax` for non-secure connections.
+
+More information about the different enforcement levels can be found in
+[the specification][rfc-6265bis-03-4.1.2.7].
+
+**Note** This is an attribute that has not yet been fully standardized, and may change in
+the future. This also means many clients may ignore this attribute until they understand it.
+
+**Note** There is a [draft spec](https://tools.ietf.org/html/draft-west-cookie-incrementalism-01)
+that requires that the `Secure` attribute be set to `true` when the `SameSite` attribute has been
+set to `'none'`. Some web browsers or other clients may be adopting this specification.
+
+The `cookie.sameSite` option can also be set to the special value `'auto'` to have
+this setting automatically match the determined security of the connection. When the connection
+is secure (HTTPS), the `SameSite` attribute will be set to `None` to enable cross-site usage.
+When the connection is not secure (HTTP), the `SameSite` attribute will be set to `Lax` for
+better security while maintaining functionality. This is useful when the Express `"trust proxy"`
+setting is properly setup to simplify development vs production configuration, particularly
+for SAML authentication scenarios.
+
+##### cookie.secure
+
+Specifies the `boolean` value for the `Secure` `Set-Cookie` attribute. When truthy,
+the `Secure` attribute is set, otherwise it is not. By default, the `Secure`
+attribute is not set.
+
+**Note** be careful when setting this to `true`, as compliant clients will not send
+the cookie back to the server in the future if the browser does not have an HTTPS
+connection.
+
+Please note that `secure: true` is a **recommended** option. However, it requires
+an https-enabled website, i.e., HTTPS is necessary for secure cookies. If `secure`
+is set, and you access your site over HTTP, the cookie will not be set. If you
+have your node.js behind a proxy and are using `secure: true`, you need to set
+"trust proxy" in express:
+
+```js
+var app = express();
+app.set('trust proxy', 1); // trust first proxy
+app.use(
+  session({
+    secret: 'keyboard cat',
+    resave: false,
+    saveUninitialized: true,
+    cookie: { secure: true },
+  })
+);
+```
+
+For using secure cookies in production, but allowing for testing in development,
+the following is an example of enabling this setup based on `NODE_ENV` in express:
+
+```js
+var app = express();
+var sess = {
+  secret: 'keyboard cat',
+  cookie: {},
+};
+
+if (app.get('env') === 'production') {
+  app.set('trust proxy', 1); // trust first proxy
+  sess.cookie.secure = true; // serve secure cookies
+}
+
+app.use(session(sess));
+```
+
+The `cookie.secure` option can also be set to the special value `'auto'` to have
+this setting automatically match the determined security of the connection. Be
+careful when using this setting if the site is available both as HTTP and HTTPS,
+as once the cookie is set on HTTPS, it will no longer be visible over HTTP. This
+is useful when the Express `"trust proxy"` setting is properly setup to simplify
+development vs production configuration.
+
+##### genid
+
+Function to call to generate a new session ID. Provide a function that returns
+a string that will be used as a session ID. The function is given `req` as the
+first argument if you want to use some value attached to `req` when generating
+the ID.
+
+The default value is a function which uses the `uid-safe` library to generate IDs.
+
+**NOTE** be careful to generate unique IDs so your sessions do not conflict.
+
+```js
+app.use(
+  session({
+    genid: function (req) {
+      return genuuid(); // use UUIDs for session IDs
+    },
+    secret: 'keyboard cat',
+  })
+);
+```
+
+##### name
+
+The name of the session ID cookie to set in the response (and read from in the
+request).
+
+The default value is `'connect.sid'`.
+
+**Note** if you have multiple apps running on the same hostname (this is just
+the name, i.e. `localhost` or `127.0.0.1`; different schemes and ports do not
+name a different hostname), then you need to separate the session cookies from
+each other. The simplest method is to simply set different `name`s per app.
+
+##### proxy
+
+Trust the reverse proxy when setting secure cookies (via the "X-Forwarded-Proto"
+header).
+
+The default value is `undefined`.
+
+- `true` The "X-Forwarded-Proto" header will be used.
+- `false` All headers are ignored and the connection is considered secure only
+  if there is a direct TLS/SSL connection.
+- `undefined` Uses the "trust proxy" setting from express
+
+##### resave
+
+Forces the session to be saved back to the session store, even if the session
+was never modified during the request. Depending on your store this may be
+necessary, but it can also create race conditions where a client makes two
+parallel requests to your server and changes made to the session in one
+request may get overwritten when the other request ends, even if it made no
+changes (this behavior also depends on what store you're using).
+
+The default value is `true`, but using the default has been deprecated,
+as the default will change in the future. Please research into this setting
+and choose what is appropriate to your use-case. Typically, you'll want
+`false`.
+
+How do I know if this is necessary for my store? The best way to know is to
+check with your store if it implements the `touch` method. If it does, then
+you can safely set `resave: false`. If it does not implement the `touch`
+method and your store sets an expiration date on stored sessions, then you
+likely need `resave: true`.
+
+##### rolling
+
+Force the session identifier cookie to be set on every response. The expiration
+is reset to the original [`maxAge`](#cookiemaxage), resetting the expiration
+countdown.
+
+The default value is `false`.
+
+With this enabled, the session identifier cookie will expire in
+[`maxAge`](#cookiemaxage) since the last response was sent instead of in
+[`maxAge`](#cookiemaxage) since the session was last modified by the server.
+
+This is typically used in conjunction with short, non-session-length
+[`maxAge`](#cookiemaxage) values to provide a quick timeout of the session data
+with reduced potential of it occurring during on going server interactions.
+
+**Note** When this option is set to `true` but the `saveUninitialized` option is
+set to `false`, the cookie will not be set on a response with an uninitialized
+session. This option only modifies the behavior when an existing session was
+loaded for the request.
+
+##### saveUninitialized
+
+Forces a session that is "uninitialized" to be saved to the store. A session is
+uninitialized when it is new but not modified. Choosing `false` is useful for
+implementing login sessions, reducing server storage usage, or complying with
+laws that require permission before setting a cookie. Choosing `false` will also
+help with race conditions where a client makes multiple parallel requests
+without a session.
+
+The default value is `true`, but using the default has been deprecated, as the
+default will change in the future. Please research into this setting and
+choose what is appropriate to your use-case.
+
+**Note** if you are using Session in conjunction with PassportJS, Passport
+will add an empty Passport object to the session for use after a user is
+authenticated, which will be treated as a modification to the session, causing
+it to be saved. _This has been fixed in PassportJS 0.3.0_
+
+##### secret
+
+**Required option**
+
+This is the secret used to sign the session ID cookie. The secret can be any type
+of value that is supported by Node.js `crypto.createHmac` (like a string or a
+`Buffer`). This can be either a single secret, or an array of multiple secrets. If
+an array of secrets is provided, only the first element will be used to sign the
+session ID cookie, while all the elements will be considered when verifying the
+signature in requests. The secret itself should be not easily parsed by a human and
+would best be a random set of characters. A best practice may include:
+
+- The use of environment variables to store the secret, ensuring the secret itself
+  does not exist in your repository.
+- Periodic updates of the secret, while ensuring the previous secret is in the
+  array.
+
+Using a secret that cannot be guessed will reduce the ability to hijack a session to
+only guessing the session ID (as determined by the `genid` option).
+
+Changing the secret value will invalidate all existing sessions. In order to rotate
+the secret without invalidating sessions, provide an array of secrets, with the new
+secret as first element of the array, and including previous secrets as the later
+elements.
+
+**Note** HMAC-256 is used to sign the session ID. For this reason, the secret should
+contain at least 32 bytes of entropy.
+
+##### store
+
+The session store instance, defaults to a new `MemoryStore` instance.
+
+##### unset
+
+Control the result of unsetting `req.session` (through `delete`, setting to `null`,
+etc.).
+
+The default value is `'keep'`.
+
+- `'destroy'` The session will be destroyed (deleted) when the response ends.
+- `'keep'` The session in the store will be kept, but modifications made during
+  the request are ignored and not saved.
+
+### req.session
+
+To store or access session data, simply use the request property `req.session`,
+which is (generally) serialized as JSON by the store, so nested objects
+are typically fine. For example below is a user-specific view counter:
+
+```js
+// Use the session middleware
+app.use(session({ secret: 'keyboard cat', cookie: { maxAge: 60000 } }));
+
+// Access the session as req.session
+app.get('/', function (req, res, next) {
+  if (req.session.views) {
+    req.session.views++;
+    res.setHeader('Content-Type', 'text/html');
+    res.write('<p>views: ' + req.session.views + '</p>');
+    res.write('<p>expires in: ' + req.session.cookie.maxAge / 1000 + 's</p>');
+    res.end();
+  } else {
+    req.session.views = 1;
+    res.end('welcome to the session demo. refresh!');
+  }
+});
+```
+
+#### Session.regenerate(callback)
+
+To regenerate the session simply invoke the method. Once complete,
+a new SID and `Session` instance will be initialized at `req.session`
+and the `callback` will be invoked.
+
+```js
+req.session.regenerate(function (err) {
+  // will have a new session here
+});
+```
+
+#### Session.destroy(callback)
+
+Destroys the session and will unset the `req.session` property.
+Once complete, the `callback` will be invoked.
+
+```js
+req.session.destroy(function (err) {
+  // cannot access session here
+});
+```
+
+#### Session.reload(callback)
+
+Reloads the session data from the store and re-populates the
+`req.session` object. Once complete, the `callback` will be invoked.
+
+```js
+req.session.reload(function (err) {
+  // session updated
+});
+```
+
+#### Session.save(callback)
+
+Save the session back to the store, replacing the contents on the store with the
+contents in memory (though a store may do something else--consult the store's
+documentation for exact behavior).
+
+This method is automatically called at the end of the HTTP response if the
+session data has been altered (though this behavior can be altered with various
+options in the middleware constructor). Because of this, typically this method
+does not need to be called.
+
+There are some cases where it is useful to call this method, for example,
+redirects, long-lived requests or in WebSockets.
+
+```js
+req.session.save(function (err) {
+  // session saved
+});
+```
+
+#### Session.touch()
+
+Updates the `.maxAge` property. Typically this is
+not necessary to call, as the session middleware does this for you.
+
+### req.session.id
+
+Each session has a unique ID associated with it. This property is an
+alias of [`req.sessionID`](#reqsessionid-1) and cannot be modified.
+It has been added to make the session ID accessible from the `session`
+object.
+
+### req.session.cookie
+
+Each session has a unique cookie object accompany it. This allows
+you to alter the session cookie per visitor. For example we can
+set `req.session.cookie.expires` to `false` to enable the cookie
+to remain for only the duration of the user-agent.
+
+#### Cookie.maxAge
+
+Alternatively `req.session.cookie.maxAge` will return the time
+remaining in milliseconds, which we may also re-assign a new value
+to adjust the `.expires` property appropriately. The following
+are essentially equivalent
+
+```js
+var hour = 3600000;
+req.session.cookie.expires = new Date(Date.now() + hour);
+req.session.cookie.maxAge = hour;
+```
+
+For example when `maxAge` is set to `60000` (one minute), and 30 seconds
+has elapsed it will return `30000` until the current request has completed,
+at which time `req.session.touch()` is called to reset
+`req.session.cookie.maxAge` to its original value.
+
+```js
+req.session.cookie.maxAge; // => 30000
+```
+
+#### Cookie.originalMaxAge
+
+The `req.session.cookie.originalMaxAge` property returns the original
+`maxAge` (time-to-live), in milliseconds, of the session cookie.
+
+### req.sessionID
+
+To get the ID of the loaded session, access the request property
+`req.sessionID`. This is simply a read-only value set when a session
+is loaded/created.
+
+## Session Store Implementation
+
+Every session store _must_ be an `EventEmitter` and implement specific
+methods. The following methods are the list of **required**, **recommended**,
+and **optional**.
+
+- Required methods are ones that this module will always call on the store.
+- Recommended methods are ones that this module will call on the store if
+  available.
+- Optional methods are ones this module does not call at all, but helps
+  present uniform stores to users.
+
+For an example implementation view the [connect-redis](http://github.com/visionmedia/connect-redis) repo.
+
+### store.all(callback)
+
+**Optional**
+
+This optional method is used to get all sessions in the store as an array. The
+`callback` should be called as `callback(error, sessions)`.
+
+### store.destroy(sid, callback)
+
+**Required**
+
+This required method is used to destroy/delete a session from the store given
+a session ID (`sid`). The `callback` should be called as `callback(error)` once
+the session is destroyed.
+
+### store.clear(callback)
+
+**Optional**
+
+This optional method is used to delete all sessions from the store. The
+`callback` should be called as `callback(error)` once the store is cleared.
+
+### store.length(callback)
+
+**Optional**
+
+This optional method is used to get the count of all sessions in the store.
+The `callback` should be called as `callback(error, len)`.
+
+### store.get(sid, callback)
+
+**Required**
+
+This required method is used to get a session from the store given a session
+ID (`sid`). The `callback` should be called as `callback(error, session)`.
+
+The `session` argument should be a session if found, otherwise `null` or
+`undefined` if the session was not found (and there was no error). A special
+case is made when `error.code === 'ENOENT'` to act like `callback(null, null)`.
+
+### store.set(sid, session, callback)
+
+**Required**
+
+This required method is used to upsert a session into the store given a
+session ID (`sid`) and session (`session`) object. The callback should be
+called as `callback(error)` once the session has been set in the store.
+
+### store.touch(sid, session, callback)
+
+**Recommended**
+
+This recommended method is used to "touch" a given session given a
+session ID (`sid`) and session (`session`) object. The `callback` should be
+called as `callback(error)` once the session has been touched.
+
+This is primarily used when the store will automatically delete idle sessions
+and this method is used to signal to the store the given session is active,
+potentially resetting the idle timer.
+
+## Compatible Session Stores
+
+The following modules implement a session store that is compatible with this
+module. Please make a PR to add additional modules :)
+
+[![★][aerospike-session-store-image] aerospike-session-store][aerospike-session-store-url] A session store using [Aerospike](http://www.aerospike.com/).
+
+[aerospike-session-store-url]: https://www.npmjs.com/package/aerospike-session-store
+
+[![★][better-sqlite3-session-store-image] better-sqlite3-session-store][better-sqlite3-session-store-url] A session store based on [better-sqlite3](https://github.com/JoshuaWise/better-sqlite3).
+
+[better-sqlite3-session-store-url]: https://www.npmjs.com/package/better-sqlite3-session-store
+
+[![★][cassandra-store-image] cassandra-store][cassandra-store-url] An Apache Cassandra-based session store.
+
+[cassandra-store-url]: https://www.npmjs.com/package/cassandra-store
+
+[![★][cluster-store-image] cluster-store][cluster-store-url] A wrapper for using in-process / embedded
+stores - such as SQLite (via knex), leveldb, files, or memory - with node cluster (desirable for Raspberry Pi 2
+and other multi-core embedded devices).
+
+[cluster-store-url]: https://www.npmjs.com/package/cluster-store
+
+[![★][connect-arango-image] connect-arango][connect-arango-url] An ArangoDB-based session store.
+
+[connect-arango-url]: https://www.npmjs.com/package/connect-arango
+
+[![★][connect-azuretables-image] connect-azuretables][connect-azuretables-url] An [Azure Table Storage](https://azure.microsoft.com/en-gb/services/storage/tables/)-based session store.
+
+[connect-azuretables-url]: https://www.npmjs.com/package/connect-azuretables
+
+[![★][connect-cloudant-store-image] connect-cloudant-store][connect-cloudant-store-url] An [IBM Cloudant](https://cloudant.com/)-based session store.
+
+[connect-cloudant-store-url]: https://www.npmjs.com/package/connect-cloudant-store
+
+[![★][connect-cosmosdb-image] connect-cosmosdb][connect-cosmosdb-url] An Azure [Cosmos DB](https://azure.microsoft.com/en-us/products/cosmos-db/)-based session store.
+
+[connect-cosmosdb-url]: https://www.npmjs.com/package/connect-cosmosdb
+
+[![★][connect-couchbase-image] connect-couchbase][connect-couchbase-url] A [couchbase](http://www.couchbase.com/)-based session store.
+
+[connect-couchbase-url]: https://www.npmjs.com/package/connect-couchbase
+
+[![★][connect-datacache-image] connect-datacache][connect-datacache-url] An [IBM Bluemix Data Cache](http://www.ibm.com/cloud-computing/bluemix/)-based session store.
+
+[connect-datacache-url]: https://www.npmjs.com/package/connect-datacache
+
+[![★][@google-cloud/connect-datastore-image] @google-cloud/connect-datastore][@google-cloud/connect-datastore-url] A [Google Cloud Datastore](https://cloud.google.com/datastore/docs/concepts/overview)-based session store.
+
+[@google-cloud/connect-datastore-url]: https://www.npmjs.com/package/@google-cloud/connect-datastore
+
+[![★][connect-db2-image] connect-db2][connect-db2-url] An IBM DB2-based session store built using [ibm_db](https://www.npmjs.com/package/ibm_db) module.
+
+[connect-db2-url]: https://www.npmjs.com/package/connect-db2
+
+[![★][connect-dynamodb-image] connect-dynamodb][connect-dynamodb-url] A DynamoDB-based session store.
+
+[connect-dynamodb-url]: https://www.npmjs.com/package/connect-dynamodb
+
+[![★][@google-cloud/connect-firestore-image] @google-cloud/connect-firestore][@google-cloud/connect-firestore-url] A [Google Cloud Firestore](https://cloud.google.com/firestore/docs/overview)-based session store.
+
+[@google-cloud/connect-firestore-url]: https://www.npmjs.com/package/@google-cloud/connect-firestore
+
+[![★][connect-hazelcast-image] connect-hazelcast][connect-hazelcast-url] Hazelcast session store for Connect and Express.
+
+[connect-hazelcast-url]: https://www.npmjs.com/package/connect-hazelcast
+
+[![★][connect-loki-image] connect-loki][connect-loki-url] A Loki.js-based session store.
+
+[connect-loki-url]: https://www.npmjs.com/package/connect-loki
+
+[![★][connect-lowdb-image] connect-lowdb][connect-lowdb-url] A lowdb-based session store.
+
+[connect-lowdb-url]: https://www.npmjs.com/package/connect-lowdb
+
+[![★][connect-memcached-image] connect-memcached][connect-memcached-url] A memcached-based session store.
+
+[connect-memcached-url]: https://www.npmjs.com/package/connect-memcached
+
+[![★][connect-memjs-image] connect-memjs][connect-memjs-url] A memcached-based session store using
+[memjs](https://www.npmjs.com/package/memjs) as the memcached client.
+
+[connect-memjs-url]: https://www.npmjs.com/package/connect-memjs
+
+[![★][connect-ml-image] connect-ml][connect-ml-url] A MarkLogic Server-based session store.
+
+[connect-ml-url]: https://www.npmjs.com/package/connect-ml
+
+[![★][connect-monetdb-image] connect-monetdb][connect-monetdb-url] A MonetDB-based session store.
+
+[connect-monetdb-url]: https://www.npmjs.com/package/connect-monetdb
+
+[![★][connect-mongo-image] connect-mongo][connect-mongo-url] A MongoDB-based session store.
+
+[connect-mongo-url]: https://www.npmjs.com/package/connect-mongo
+
+[![★][connect-mongodb-session-image] connect-mongodb-session][connect-mongodb-session-url] Lightweight MongoDB-based session store built and maintained by MongoDB.
+
+[connect-mongodb-session-url]: https://www.npmjs.com/package/connect-mongodb-session
+
+[![★][connect-mssql-v2-image] connect-mssql-v2][connect-mssql-v2-url] A Microsoft SQL Server-based session store based on [connect-mssql](https://www.npmjs.com/package/connect-mssql).
+
+[connect-mssql-v2-url]: https://www.npmjs.com/package/connect-mssql-v2
+
+[![★][connect-neo4j-image] connect-neo4j][connect-neo4j-url] A [Neo4j](https://neo4j.com)-based session store.
+
+[connect-neo4j-url]: https://www.npmjs.com/package/connect-neo4j
+
+[![★][connect-ottoman-image] connect-ottoman][connect-ottoman-url] A [couchbase ottoman](http://www.couchbase.com/)-based session store.
+
+[connect-ottoman-url]: https://www.npmjs.com/package/connect-ottoman
+
+[![★][connect-pg-simple-image] connect-pg-simple][connect-pg-simple-url] A PostgreSQL-based session store.
+
+[connect-pg-simple-url]: https://www.npmjs.com/package/connect-pg-simple
+
+[![★][connect-redis-image] connect-redis][connect-redis-url] A Redis-based session store.
+
+[connect-redis-url]: https://www.npmjs.com/package/connect-redis
+
+[![★][connect-session-firebase-image] connect-session-firebase][connect-session-firebase-url] A session store based on the [Firebase Realtime Database](https://firebase.google.com/docs/database/)
+
+[connect-session-firebase-url]: https://www.npmjs.com/package/connect-session-firebase
+
+[![★][connect-session-knex-image] connect-session-knex][connect-session-knex-url] A session store using
+[Knex.js](http://knexjs.org/), which is a SQL query builder for PostgreSQL, MySQL, MariaDB, SQLite3, and Oracle.
+
+[connect-session-knex-url]: https://www.npmjs.com/package/connect-session-knex
+
+[![★][connect-session-sequelize-image] connect-session-sequelize][connect-session-sequelize-url] A session store using
+[Sequelize.js](http://sequelizejs.com/), which is a Node.js / io.js ORM for PostgreSQL, MySQL, SQLite and MSSQL.
+
+[connect-session-sequelize-url]: https://www.npmjs.com/package/connect-session-sequelize
+
+[![★][connect-sqlite3-image] connect-sqlite3][connect-sqlite3-url] A [SQLite3](https://github.com/mapbox/node-sqlite3) session store modeled after the TJ's `connect-redis` store.
+
+[connect-sqlite3-url]: https://www.npmjs.com/package/connect-sqlite3
+
+[![★][connect-typeorm-image] connect-typeorm][connect-typeorm-url] A [TypeORM](https://github.com/typeorm/typeorm)-based session store.
+
+[connect-typeorm-url]: https://www.npmjs.com/package/connect-typeorm
+
+[![★][couchdb-expression-image] couchdb-expression][couchdb-expression-url] A [CouchDB](https://couchdb.apache.org/)-based session store.
+
+[couchdb-expression-url]: https://www.npmjs.com/package/couchdb-expression
+
+[![★][dynamodb-store-image] dynamodb-store][dynamodb-store-url] A DynamoDB-based session store.
+
+[dynamodb-store-url]: https://www.npmjs.com/package/dynamodb-store
+
+[![★][dynamodb-store-v3-image] dynamodb-store-v3][dynamodb-store-v3-url] Implementation of a session store using DynamoDB backed by the [AWS SDK for JavaScript v3](https://github.com/aws/aws-sdk-js-v3).
+
+[dynamodb-store-v3-url]: https://www.npmjs.com/package/dynamodb-store-v3
+
+[![★][express-etcd-image] express-etcd][express-etcd-url] An [etcd](https://github.com/stianeikeland/node-etcd) based session store.
+
+[express-etcd-url]: https://www.npmjs.com/package/express-etcd
+
+[![★][express-mysql-session-image] express-mysql-session][express-mysql-session-url] A session store using native
+[MySQL](https://www.mysql.com/) via the [node-mysql](https://github.com/felixge/node-mysql) module.
+
+[express-mysql-session-url]: https://www.npmjs.com/package/express-mysql-session
+
+[![★][express-nedb-session-image] express-nedb-session][express-nedb-session-url] A NeDB-based session store.
+
+[express-nedb-session-url]: https://www.npmjs.com/package/express-nedb-session
+
+[![★][express-oracle-session-image] express-oracle-session][express-oracle-session-url] A session store using native
+[oracle](https://www.oracle.com/) via the [node-oracledb](https://www.npmjs.com/package/oracledb) module.
+
+[express-oracle-session-url]: https://www.npmjs.com/package/express-oracle-session
+
+[![★][express-session-cache-manager-image] express-session-cache-manager][express-session-cache-manager-url]
+A store that implements [cache-manager](https://www.npmjs.com/package/cache-manager), which supports
+a [variety of storage types](https://www.npmjs.com/package/cache-manager#store-engines).
+
+[express-session-cache-manager-url]: https://www.npmjs.com/package/express-session-cache-manager
+
+[![★][express-session-etcd3-image] express-session-etcd3][express-session-etcd3-url] An [etcd3](https://github.com/mixer/etcd3) based session store.
+
+[express-session-etcd3-url]: https://www.npmjs.com/package/express-session-etcd3
+
+[![★][express-session-level-image] express-session-level][express-session-level-url] A [LevelDB](https://github.com/Level/levelup) based session store.
+
+[express-session-level-url]: https://www.npmjs.com/package/express-session-level
+
+[![★][express-session-rsdb-image] express-session-rsdb][express-session-rsdb-url] Session store based on Rocket-Store: A very simple, super fast and yet powerful, flat file database.
+
+[express-session-rsdb-url]: https://www.npmjs.com/package/express-session-rsdb
+
+[![★][express-sessions-image] express-sessions][express-sessions-url] A session store supporting both MongoDB and Redis.
+
+[express-sessions-url]: https://www.npmjs.com/package/express-sessions
+
+[![★][firestore-store-image] firestore-store][firestore-store-url] A [Firestore](https://github.com/hendrysadrak/firestore-store)-based session store.
+
+[firestore-store-url]: https://www.npmjs.com/package/firestore-store
+
+[![★][fortune-session-image] fortune-session][fortune-session-url] A [Fortune.js](https://github.com/fortunejs/fortune)
+based session store. Supports all backends supported by Fortune (MongoDB, Redis, Postgres, NeDB).
+
+[fortune-session-url]: https://www.npmjs.com/package/fortune-session
+
+[![★][hazelcast-store-image] hazelcast-store][hazelcast-store-url] A Hazelcast-based session store built on the [Hazelcast Node Client](https://www.npmjs.com/package/hazelcast-client).
+
+[hazelcast-store-url]: https://www.npmjs.com/package/hazelcast-store
+
+[![★][level-session-store-image] level-session-store][level-session-store-url] A LevelDB-based session store.
+
+[level-session-store-url]: https://www.npmjs.com/package/level-session-store
+
+[![★][lowdb-session-store-image] lowdb-session-store][lowdb-session-store-url] A [lowdb](https://www.npmjs.com/package/lowdb)-based session store.
+
+[lowdb-session-store-url]: https://www.npmjs.com/package/lowdb-session-store
+
+[![★][medea-session-store-image] medea-session-store][medea-session-store-url] A Medea-based session store.
+
+[medea-session-store-url]: https://www.npmjs.com/package/medea-session-store
+
+[![★][memorystore-image] memorystore][memorystore-url] A memory session store made for production.
+
+[memorystore-url]: https://www.npmjs.com/package/memorystore
+
+[![★][mssql-session-store-image] mssql-session-store][mssql-session-store-url] A SQL Server-based session store.
+
+[mssql-session-store-url]: https://www.npmjs.com/package/mssql-session-store
+
+[![★][nedb-session-store-image] nedb-session-store][nedb-session-store-url] An alternate NeDB-based (either in-memory or file-persisted) session store.
+
+[nedb-session-store-url]: https://www.npmjs.com/package/nedb-session-store
+
+[![★][@quixo3/prisma-session-store-image] @quixo3/prisma-session-store][@quixo3/prisma-session-store-url] A session store for the [Prisma Framework](https://www.prisma.io).
+
+[@quixo3/prisma-session-store-url]: https://www.npmjs.com/package/@quixo3/prisma-session-store
+
+[![★][restsession-image] restsession][restsession-url] Store sessions utilizing a RESTful API
+
+[restsession-url]: https://www.npmjs.com/package/restsession
+
+[![★][sequelstore-connect-image] sequelstore-connect][sequelstore-connect-url] A session store using [Sequelize.js](http://sequelizejs.com/).
+
+[sequelstore-connect-url]: https://www.npmjs.com/package/sequelstore-connect
+
+[![★][session-file-store-image] session-file-store][session-file-store-url] A file system-based session store.
+
+[session-file-store-url]: https://www.npmjs.com/package/session-file-store
+
+[![★][session-pouchdb-store-image] session-pouchdb-store][session-pouchdb-store-url] Session store for PouchDB / CouchDB. Accepts embedded, custom, or remote PouchDB instance and realtime synchronization.
+
+[session-pouchdb-store-url]: https://www.npmjs.com/package/session-pouchdb-store
+
+[![★][@cyclic.sh/session-store-image] @cyclic.sh/session-store][@cyclic.sh/session-store-url] A DynamoDB-based session store for [Cyclic.sh](https://www.cyclic.sh/) apps.
+
+[@cyclic.sh/session-store-url]: https://www.npmjs.com/package/@cyclic.sh/session-store
+
+[![★][@databunker/session-store-image] @databunker/session-store][@databunker/session-store-url] A [Databunker](https://databunker.org/)-based encrypted session store.
+
+[@databunker/session-store-url]: https://www.npmjs.com/package/@databunker/session-store
+
+[![★][sessionstore-image] sessionstore][sessionstore-url] A session store that works with various databases.
+
+[sessionstore-url]: https://www.npmjs.com/package/sessionstore
+
+[![★][tch-nedb-session-image] tch-nedb-session][tch-nedb-session-url] A file system session store based on NeDB.
+
+[tch-nedb-session-url]: https://www.npmjs.com/package/tch-nedb-session
+
+## Examples
+
+### View counter
+
+A simple example using `express-session` to store page views for a user.
+
+```js
+var express = require('express');
+var parseurl = require('parseurl');
+var session = require('express-session');
+
+var app = express();
+
+app.use(
+  session({
+    secret: 'keyboard cat',
+    resave: false,
+    saveUninitialized: true,
+  })
+);
+
+app.use(function (req, res, next) {
+  if (!req.session.views) {
+    req.session.views = {};
+  }
+
+  // get the url pathname
+  var pathname = parseurl(req).pathname;
+
+  // count the views
+  req.session.views[pathname] = (req.session.views[pathname] || 0) + 1;
+
+  next();
+});
+
+app.get('/foo', function (req, res, next) {
+  res.send('you viewed this page ' + req.session.views['/foo'] + ' times');
+});
+
+app.get('/bar', function (req, res, next) {
+  res.send('you viewed this page ' + req.session.views['/bar'] + ' times');
+});
+
+app.listen(3000);
+```
+
+### User login
+
+A simple example using `express-session` to keep a user log in session.
+
+```js
+var escapeHtml = require('escape-html');
+var express = require('express');
+var session = require('express-session');
+
+var app = express();
+
+app.use(
+  session({
+    secret: 'keyboard cat',
+    resave: false,
+    saveUninitialized: true,
+  })
+);
+
+// middleware to test if authenticated
+function isAuthenticated(req, res, next) {
+  if (req.session.user) next();
+  else next('route');
+}
+
+app.get('/', isAuthenticated, function (req, res) {
+  // this is only called when there is an authentication user due to isAuthenticated
+  res.send('hello, ' + escapeHtml(req.session.user) + '!' + ' <a href="/logout">Logout</a>');
+});
+
+app.get('/', function (req, res) {
+  res.send(
+    '<form action="/login" method="post">' +
+      'Username: <input name="user"><br />' +
+      'Password: <input name="pass" type="password"><br />' +
+      '<input type="submit" text="Login"></form>'
+  );
+});
+
+app.post('/login', express.urlencoded({ extended: false }), function (req, res) {
+  // login logic to validate req.body.user and req.body.pass
+  // would be implemented here. for this example any combo works
+
+  // regenerate the session, which is good practice to help
+  // guard against forms of session fixation
+  req.session.regenerate(function (err) {
+    if (err) next(err);
+
+    // store user information in session, typically a user id
+    req.session.user = req.body.user;
+
+    // save the session before redirection to ensure page
+    // load does not happen before session is saved
+    req.session.save(function (err) {
+      if (err) return next(err);
+      res.redirect('/');
+    });
+  });
+});
+
+app.get('/logout', function (req, res, next) {
+  // logout logic
+
+  // clear the user from the session object and save.
+  // this will ensure that re-using the old session id
+  // does not have a logged in user
+  req.session.user = null;
+  req.session.save(function (err) {
+    if (err) next(err);
+
+    // regenerate the session, which is good practice to help
+    // guard against forms of session fixation
+    req.session.regenerate(function (err) {
+      if (err) next(err);
+      res.redirect('/');
+    });
+  });
+});
+
+app.listen(3000);
+```
+
+## Debugging
+
+This module uses the [debug](https://www.npmjs.com/package/debug) module
+internally to log information about session operations.
+
+To see all the internal logs, set the `DEBUG` environment variable to
+`express-session` when launching your app (`npm start`, in this example):
+
+```sh
+$ DEBUG=express-session npm start
+```
+
+On Windows, use the corresponding command;
+
+```sh
+> set DEBUG=express-session & npm start
+```
+
+## License
+
+[MIT](https://github.com/expressjs/session/blob/HEAD/LICENSE)
+
+[rfc-6265bis-03-4.1.2.7]: https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-03#section-4.1.2.7
+[rfc-cutler-httpbis-partitioned-cookies]: https://tools.ietf.org/html/draft-cutler-httpbis-partitioned-cookies/
+[rfc-west-cookie-priority-00-4.1]: https://tools.ietf.org/html/draft-west-cookie-priority-00#section-4.1
+[node-url]: https://nodejs.org/en/download
+[npm-url]: https://npmjs.org/package/express-session
diff --git a/src/content/pages/en/resources/middleware/timeout.mdx b/src/content/pages/en/resources/middleware/timeout.mdx
new file mode 100644
index 0000000000..4942e10a44
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/timeout.mdx
@@ -0,0 +1,173 @@
+---
+title: timeout middleware
+description: Request timeout middleware for Connect/Express
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="0.2.1"
+  github="https://github.com/expressjs/timeout"
+  npm="https://www.npmjs.com/package/timeout"
+/>
+
+Times out a request in the Connect/Express application framework.
+
+## Install
+
+This is a [Node.js](https://nodejs.org/en/) module available through the
+[npm registry](https://www.npmjs.com/). Installation is done using the
+[`npm install` command](https://docs.npmjs.com/getting-started/installing-npm-packages-locally):
+
+```sh
+$ npm install connect-timeout
+```
+
+## API
+
+**NOTE** This module is not recommend as a "top-level" middleware (i.e.
+`app.use(timeout('5s'))`) unless you take precautions to halt your own
+middleware processing. See [as top-level middleware](#as-top-level-middleware)
+for how to use as a top-level middleware.
+
+While the library will emit a 'timeout' event when requests exceed the given
+timeout, node will continue processing the slow request until it terminates.
+Slow requests will continue to use CPU and memory, even if you are returning
+a HTTP response in the timeout callback. For better control over CPU/memory,
+you may need to find the events that are taking a long time (3rd party HTTP
+requests, disk I/O, database calls) and find a way to cancel them, and/or
+close the attached sockets.
+
+### timeout(time, [options])
+
+Returns middleware that times out in `time` milliseconds. `time` can also
+be a string accepted by the [ms](https://www.npmjs.org/package/ms#readme)
+module. On timeout, `req` will emit `"timeout"`.
+
+#### Options
+
+The `timeout` function takes an optional `options` object that may contain
+any of the following keys:
+
+##### respond
+
+Controls if this module will "respond" in the form of forwarding an error.
+If `true`, the timeout error is passed to `next()` so that you may customize
+the response behavior. This error has a `.timeout` property as well as
+`.status == 503`. This defaults to `true`.
+
+### req.clearTimeout()
+
+Clears the timeout on the request. The timeout is completely removed and
+will not fire for this request in the future.
+
+### req.timedout
+
+`true` if timeout fired; `false` otherwise.
+
+## Examples
+
+### as top-level middleware
+
+Because of the way middleware processing works, once this module
+passes the request to the next middleware (which it has to do in order
+for you to do work), it can no longer stop the flow, so you must take
+care to check if the request has timedout before you continue to act
+on the request.
+
+```javascript
+var bodyParser = require('body-parser');
+var cookieParser = require('cookie-parser');
+var express = require('express');
+var timeout = require('connect-timeout');
+
+// example of using this top-level; note the use of haltOnTimedout
+// after every middleware; it will stop the request flow on a timeout
+var app = express();
+app.use(timeout('5s'));
+app.use(bodyParser());
+app.use(haltOnTimedout);
+app.use(cookieParser());
+app.use(haltOnTimedout);
+
+// Add your routes here, etc.
+
+function haltOnTimedout(req, res, next) {
+  if (!req.timedout) next();
+}
+
+app.listen(3000);
+```
+
+### express 3.x
+
+```javascript
+var express = require('express');
+var bodyParser = require('body-parser');
+var timeout = require('connect-timeout');
+
+var app = express();
+app.post('/save', timeout('5s'), bodyParser.json(), haltOnTimedout, function (req, res, next) {
+  savePost(req.body, function (err, id) {
+    if (err) return next(err);
+    if (req.timedout) return;
+    res.send('saved as id ' + id);
+  });
+});
+
+function haltOnTimedout(req, res, next) {
+  if (!req.timedout) next();
+}
+
+function savePost(post, cb) {
+  setTimeout(
+    function () {
+      cb(null, (Math.random() * 40000) >>> 0);
+    },
+    (Math.random() * 7000) >>> 0
+  );
+}
+
+app.listen(3000);
+```
+
+### connect
+
+```javascript
+var bodyParser = require('body-parser');
+var connect = require('connect');
+var timeout = require('connect-timeout');
+
+var app = connect();
+app.use('/save', timeout('5s'), bodyParser.json(), haltOnTimedout, function (req, res, next) {
+  savePost(req.body, function (err, id) {
+    if (err) return next(err);
+    if (req.timedout) return;
+    res.send('saved as id ' + id);
+  });
+});
+
+function haltOnTimedout(req, res, next) {
+  if (!req.timedout) next();
+}
+
+function savePost(post, cb) {
+  setTimeout(
+    function () {
+      cb(null, (Math.random() * 40000) >>> 0);
+    },
+    (Math.random() * 7000) >>> 0
+  );
+}
+
+app.listen(3000);
+```
+
+## License
+
+[MIT](https://github.com/expressjs/timeout/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/connect-timeout
+[travis-url]: https://travis-ci.org/expressjs/timeout
+[downloads-url]: https://npmjs.org/package/connect-timeout
diff --git a/src/content/pages/en/resources/middleware/vhost.mdx b/src/content/pages/en/resources/middleware/vhost.mdx
new file mode 100644
index 0000000000..7d641e0a70
--- /dev/null
+++ b/src/content/pages/en/resources/middleware/vhost.mdx
@@ -0,0 +1,170 @@
+---
+title: vhost middleware
+description: Virtual domain hosting
+---
+
+import MiddlewareInfo from '@components/patterns/MiddlewareInfo/MiddlewareInfo.astro';
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<MiddlewareInfo
+  version="3.0.2"
+  github="https://github.com/expressjs/vhost"
+  npm="https://www.npmjs.com/package/vhost"
+/>
+
+## Install
+
+```sh
+$ npm install vhost
+```
+
+## API
+
+```js
+var vhost = require('vhost');
+```
+
+### vhost(hostname, handle)
+
+Create a new middleware function to hand off request to `handle` when the incoming
+host for the request matches `hostname`. The function is called as
+`handle(req, res, next)`, like a standard middleware.
+
+`hostname` can be a string or a RegExp object. When `hostname` is a string it can
+contain `*` to match 1 or more characters in that section of the hostname. When
+`hostname` is a RegExp, it will be forced to case-insensitive (since hostnames are)
+and will be forced to match based on the start and end of the hostname.
+
+When host is matched and the request is sent down to a vhost handler, the `req.vhost`
+property will be populated with an object. This object will have numeric properties
+corresponding to each wildcard (or capture group if RegExp object provided) and the
+`hostname` that was matched.
+
+```js
+var connect = require('connect');
+var vhost = require('vhost');
+var app = connect();
+
+app.use(
+  vhost('*.*.example.com', function handle(req, res, next) {
+    // for match of "foo.bar.example.com:8080" against "*.*.example.com":
+    console.dir(req.vhost.host); // => 'foo.bar.example.com:8080'
+    console.dir(req.vhost.hostname); // => 'foo.bar.example.com'
+    console.dir(req.vhost.length); // => 2
+    console.dir(req.vhost[0]); // => 'foo'
+    console.dir(req.vhost[1]); // => 'bar'
+  })
+);
+```
+
+## Examples
+
+### using with connect for static serving
+
+```js
+var connect = require('connect');
+var serveStatic = require('serve-static');
+var vhost = require('vhost');
+
+var mailapp = connect();
+
+// add middlewares to mailapp for mail.example.com
+
+// create app to serve static files on subdomain
+var staticapp = connect();
+staticapp.use(serveStatic('public'));
+
+// create main app
+var app = connect();
+
+// add vhost routing to main app for mail
+app.use(vhost('mail.example.com', mailapp));
+
+// route static assets for "assets-*" subdomain to get
+// around max host connections limit on browsers
+app.use(vhost('assets-*.example.com', staticapp));
+
+// add middlewares and main usage to app
+
+app.listen(3000);
+```
+
+### using with connect for user subdomains
+
+```js
+var connect = require('connect');
+var serveStatic = require('serve-static');
+var vhost = require('vhost');
+
+var mainapp = connect();
+
+// add middlewares to mainapp for the main web site
+
+// create app that will server user content from public/{username}/
+var userapp = connect();
+
+userapp.use(function (req, res, next) {
+  var username = req.vhost[0]; // username is the "*"
+
+  // pretend request was for /{username}/* for file serving
+  req.originalUrl = req.url;
+  req.url = '/' + username + req.url;
+
+  next();
+});
+userapp.use(serveStatic('public'));
+
+// create main app
+var app = connect();
+
+// add vhost routing for main app
+app.use(vhost('userpages.local', mainapp));
+app.use(vhost('www.userpages.local', mainapp));
+
+// listen on all subdomains for user pages
+app.use(vhost('*.userpages.local', userapp));
+
+app.listen(3000);
+```
+
+### using with any generic request handler
+
+```js
+var connect = require('connect');
+var http = require('http');
+var vhost = require('vhost');
+
+// create main app
+var app = connect();
+
+app.use(
+  vhost('mail.example.com', function (req, res) {
+    // handle req + res belonging to mail.example.com
+    res.setHeader('Content-Type', 'text/plain');
+    res.end('hello from mail!');
+  })
+);
+
+// an external api server in any framework
+var httpServer = http.createServer(function (req, res) {
+  res.setHeader('Content-Type', 'text/plain');
+  res.end('hello from the api!');
+});
+
+app.use(
+  vhost('api.example.com', function (req, res) {
+    // handle req + res belonging to api.example.com
+    // pass the request to a standard Node.js HTTP server
+    httpServer.emit('request', req, res);
+  })
+);
+
+app.listen(3000);
+```
+
+## License
+
+[MIT](https://github.com/expressjs/vhost/blob/HEAD/LICENSE)
+
+[npm-url]: https://npmjs.org/package/vhost
+[downloads-url]: https://npmjs.org/package/vhost
diff --git a/src/content/pages/en/resources/utils.md b/src/content/pages/en/resources/utils.md
new file mode 100644
index 0000000000..546b2f09b4
--- /dev/null
+++ b/src/content/pages/en/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Express utilities
+description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
+---
+
+## Express utility functions
+
+The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
+for utility functions that may be generally useful.
+
+| Utility modules                                                | Description                                                                                                                                             |
+| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification. Use this module to create custom CSRF middleware.                                       |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                        |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                               |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as ``/user/:name` into a regular expression.                                                                     |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                           |
+| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                         |
+| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.          |
+
+For additional low-level HTTP-related modules, see [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/en/support.md b/src/content/pages/en/support.md
new file mode 100644
index 0000000000..9e59b0976b
--- /dev/null
+++ b/src/content/pages/en/support.md
@@ -0,0 +1,23 @@
+---
+title: Version Support
+description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
+---
+
+Only the latest version of any given major release line is supported.
+
+Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
+
+| Major Version          | Minimum Node.js Version | Support Start Date | Support End Date |
+| ---------------------- | ----------------------- | ------------------ | ---------------- |
+| [**v5.x**](/en/5x/api) | 18                      | September 2024     | **ongoing**      |
+| [**v4.x**](/en/4x/api) | 0.10.0                  | April 2014         | **ongoing**      |
+| [**v3.x**](/en/3x/api) | 0.8.0                   | October 2012       | July 2015        |
+| [**v2.x**](/2x/)       | 0.4.1                   | March 2011         | July 2012        |
+| **v1.x**               | 0.2.0                   | December 2010      | March 2011       |
+| **v0.14.x**            | 0.1.98                  | December 2010      | December 2010    |
+
+## Commercial Support Options
+
+If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/es/advanced/best-practice-performance.md b/src/content/pages/es/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..575a6a97d8
--- /dev/null
+++ b/src/content/pages/es/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Mejores prácticas de producción: rendimiento y fiabilidad'
+description: Descubra las mejores prácticas de rendimiento y fiabilidad para aplicaciones Express en producción, cubriendo optimizaciones de código y configuraciones de entorno para un rendimiento óptimo.
+---
+
+Este artículo analiza el rendimiento y la fiabilidad de las mejores prácticas para aplicaciones Express implementadas en producción.
+
+Este tema entra claramente en el mundo de los "devops", que abarca tanto el desarrollo tradicional como las operaciones. En consecuencia, la información se divide en dos partes:
+
+- Cosas que hacer en tu código (la parte del desarrollador):
+  - [Usar compresión gzip](#use-gzip-compression)
+  - [No usar funciones sincrónicas](#dont-use-synchronous-functions)
+  - [Registrar correctamente] (#do-logging-correctly)
+  - [Manejar excepciones correctamente](#handle-exceptions-properly)
+- Cosas que hacer en tu entorno / configuración (parte de la opción):
+  - [Establecer NODE_ENV a "producción"](#set-node_env-to-production)
+  - [Asegúrate de que tu aplicación se reinicie automáticamente](#ensure-your-app-automatically-restarts)
+  - [Ejecutar tu aplicación en un clúster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Usa un balanceador de carga](#use-a-load-balancer)
+  - [Usa un proxy inverso](#use-a-reverse-proxy)
+
+## Cosas que hacer en tu código
+
+Aquí hay algunas cosas que puedes hacer en tu código para mejorar el rendimiento de tu aplicación:
+
+- [Usar compresión gzip](#use-gzip-compression)
+- [No usar funciones sincrónicas](#dont-use-synchronous-functions)
+- [Registrar correctamente] (#do-logging-correctly)
+- [Manejar excepciones correctamente](#handle-exceptions-properly)
+
+### Usar compresión gzip
+
+La compresión Gzip puede disminuir en gran medida el tamaño del cuerpo de respuesta y por lo tanto aumentar la velocidad de una aplicación web. Utilice el Middleware [compression](https://www.npmjs.com/package/compression) para compresión gzip en su aplicación Express. Por ejemplo:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+Para un sitio web de alto tráfico en producción, la mejor manera de poner compresión en su lugar es implementarla en un nivel proxy inverso (ver [Usar un proxy inverso](#use-a-reverse-proxy)). En ese caso, no necesita usar middleware de compresión. Para más detalles sobre habilitar compresión gzip en Nginx, vea [Módulo ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) en la documentación de Nginx.
+
+### No utilizar funciones sincrónicas
+
+Las funciones y métodos sincrónicos emiten el proceso de ejecución hasta que regresen. Una sola llamada a una función sincrónica puede regresar en unos pocos microsegundos o milisegundos, Sin embargo, en sitios web de alto tráfico, estas llamadas añaden y reducen el rendimiento de la aplicación. Evite su uso en la producción.
+
+Aunque Node y muchos módulos proporcionan versiones sincrónicas y asíncronas de sus funciones, siempre utiliza la versión asíncrona en producción. La única vez que una función sincrónica puede ser justificada es al inicio inicial.
+
+Puedes usar la bandera de línea de comandos `--trace-sync-io` para imprimir una advertencia y un stack trace cada vez que tu aplicación usa una API sincrónica. Por supuesto, no querrías usar esto en la producción, sino más bien asegurar que tu código esté listo para la producción. Vea la [documentación de opciones de línea de comandos de nodo](https://nodejs.org/api/cli#cli_trace_sync_io) para más información.
+
+### Hacer el registro correctamente
+
+En general, hay dos razones para registrarse desde tu aplicación: para depurar y para registrar la actividad de la aplicación (esencialmente, todo lo demás). Usar `console.log()` o `console.error()` para imprimir mensajes de registro en la terminal es práctica común en desarrollo. Pero [estas funciones son sincrónicas](https://nodejs.org/api/console#console) cuando el destino es un terminal o un archivo, por lo que no son aptos para la producción, a menos que usted pipe la salida a otro programa.
+
+#### Para depuración
+
+Si está registrando para fines de depuración, entonces en lugar de usar `console.log()`, utilice un módulo especial de depuración como [debug](https://www.npmjs.com/package/debug). Este módulo le permite usar la variable de entorno DEBUG para controlar qué mensajes de depuración se envían a `console.error()`, si los hay. Para mantener tu aplicación puramente asincrónica, todavía quieres pipe `console.error()` a otro programa. Pero entonces, no vas a depurar en la producción, ¿verdad?
+
+#### Para actividad de la aplicación
+
+Si estás registrando actividad de la aplicación (por ejemplo, rastreando tráfico o llamadas de API), en lugar de usar `console. og()`, utiliza una biblioteca de registro como [Pino](https://www.npmjs.com/package/pino), que es la opción más rápida y eficiente disponible.
+
+### Manejar excepciones correctamente
+
+Las aplicaciones del nodo fallan cuando se encuentran con una excepción no capturada. No manejar excepciones y tomar las acciones apropiadas hará que su aplicación Express se bloquee y se desconecte. Si sigues los consejos de [Asegúrate de que tu aplicación se reinicie automáticamente](#ensure-your-app-automatically-restarts) a continuación, tu aplicación se recuperará de un cuelgue. Afortunadamente, las aplicaciones Express típicamente tienen un corto tiempo de inicio. Sin embargo, usted quiere evitar el bloqueo en primer lugar, y para hacerlo, necesita manejar las excepciones adecuadamente.
+
+Para asegurar que maneja todas las excepciones, utilice las siguientes técnicas:
+
+- [Usar try-catch](#use-try-catch)
+- [Usar promesas](#use-promises)
+
+Antes de sumergirte en estos temas, deberías tener una comprensión básica del manejo de errores de Node/Express: usando callbacks de primer error, y propagando errores en middleware. Node utiliza una convención de "error de primer callback" para devolver errores de funciones asíncronas, donde el primer parámetro de la función callback es el objeto de error, seguido de los datos de resultado en los parámetros posteriores. Para indicar ningún error, pase nulo como el primer parámetro. La función callback debe seguir la convención de devolución de llamada de primer error para manejar el error de forma significativa. Y en Express, la mejor práctica es usar la función next() para propagar errores a través de la cadena middleware.
+
+Para más información sobre los fundamentos del manejo de errores, vea:
+
+- [Manejo de Error en Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Usar try-catch
+
+Try-catch es una construcción de lenguaje JavaScript que se puede utilizar para capturar excepciones en código sincrónico. Use try-catch, por ejemplo, para manejar errores de análisis JSON como se muestra a continuación.
+
+He aquí un ejemplo del uso de try-catch para manejar una posible excepción de bloqueo de procesos.
+Esta función middleware acepta un parámetro de campo de consulta llamado "params" que es un objeto JSON.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+Sin embargo, try-catch funciona sólo para código sincrónico. Debido a que la plataforma de Node es principalmente asíncrona (especialmente en un entorno de producción), la captura de pruebas no capturará muchas excepciones.
+
+#### Utilizar promesas
+
+Cuando se arroja un error en una función `async` o se espera una promesa rechazada dentro de una función `async`, esos errores se pasarán al gestor de errores como si llamara a `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+También, puede utilizar funciones asíncronas para su middleware, y el router manejará errores si la promesa falla, por ejemplo:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+La mejor práctica es manejar los errores lo más cerca posible del sitio. Así que mientras esto se maneja ahora en el router, es mejor capturar el error en el middleware y manejarlo sin depender de middleware separado para manejar errores.
+
+#### Qué no hacer
+
+Una cosa que debes _no_ hacer es escuchar el evento `uncaughtException`, emitido cuando una excepción emite todo el camino de regreso al bucle del evento. Añadir un detector de eventos para `uncaughtException` cambiará el comportamiento predeterminado del proceso que se encuentra con una excepción; el proceso continuará funcionando a pesar de la excepción. Esto puede sonar como una buena manera de evitar que tu aplicación falle, pero seguir ejecutando la aplicación después de una excepción no capturada es una práctica peligrosa y no se recomienda, porque el estado del proceso se vuelve poco fiable e impredecible.
+
+Además, usar `uncaughtException` es oficialmente reconocido como [crude](https://nodejs.org/api/process#process_event_uncaughtexception). Así que escuchar `uncaughtException` es sólo una mala idea. Por eso recomendamos cosas como múltiples procesos y supervisores: fallar y reiniciar es a menudo la manera más confiable de recuperarse de un error.
+
+Tampoco recomendamos usar [domains](https://nodejs.org/api/domain). Generalmente no resuelve el problema y es un módulo obsoleto.
+
+## Cosas que hacer en tu entorno / configuración
+
+Aquí hay algunas cosas que puedes hacer en el entorno de tu sistema para mejorar el rendimiento de tu aplicación:
+
+- [Establecer NODE_ENV a "producción"](#set-node_env-to-production)
+- [Asegúrate de que tu aplicación se reinicie automáticamente](#ensure-your-app-automatically-restarts)
+- [Ejecutar tu aplicación en un clúster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Usa un balanceador de carga](#use-a-load-balancer)
+- [Usa un proxy inverso](#use-a-reverse-proxy)
+
+### Establecer NODE_ENV a "producción"
+
+La variable de entorno NODE_ENV especifica el entorno en el que se está ejecutando una aplicación (normalmente, desarrollo o producción). Una de las cosas más sencillas que puedes hacer para mejorar el rendimiento es establecer NODE_ENV en `production`.
+
+Establecer NODE_ENV a "producción" hace Expresión:
+
+- Plantillas de vista de caché.
+- Caché de archivos CSS generados a partir de extensiones CSS.
+- Generar mensajes de error menos detallados.
+
+¡[Las pruebas indican](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) que hacer esto puede mejorar el rendimiento de la aplicación en un factor de tres!
+
+Si necesita escribir código específico del entorno, puede comprobar el valor de NODE_ENV con `process.env.NODE_ENV`. Tenga en cuenta que comprobar el valor de cualquier variable de entorno incurre en una penalidad de rendimiento, y por lo tanto debe hacerse de forma esparcida.
+
+En desarrollo, normalmente estableces variables de entorno en tu shell interactivo, por ejemplo usando `export` o tu archivo `.bash_profile`. Pero en general, no debería hacer esto en un servidor de producción; en cambio, utilice el sistema de inicio de su sistema operativo (systemd). La siguiente sección proporciona más detalles sobre el uso de tu sistema de inicio en general pero configurar `NODE_ENV` es tan importante para el rendimiento (y fácil de hacer), que está resaltado aquí.
+
+Con el sistema, utilice la directiva 'Entorno de Entorno' en su archivo de unidad. Por ejemplo:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+Para obtener más información, consulte [Usar variables de entorno en unidades del sistema](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Asegúrate de que tu aplicación se reinicie automáticamente
+
+En la producción, usted no quiere que su aplicación esté fuera de línea, nunca. Esto significa que necesita asegurarse de que se reinicie si la aplicación se bloquea y si el servidor mismo falla. Aunque usted espera que ninguno de estos eventos ocurra, realísticamente usted debe dar cuenta de ambos eventos por:
+
+- Usar un gestor de procesos para reiniciar la aplicación (y Node) cuando se bloquea.
+- Usando el sistema de inicio proporcionado por su sistema operativo para reiniciar el gestor de procesos cuando el sistema operativo se bloquea. También es posible usar el sistema init sin un gestor de procesos.
+
+Las aplicaciones de nodos se estrellan si se encuentran con una excepción no capturada. Lo más importante que tienes que hacer es asegurar que tu aplicación está bien probada y gestiona todas las excepciones (ver [excepciones de manejo correctamente](#handle-exceptions-properly) para más detalles). Pero como seguro de fallos, ponga en marcha un mecanismo para asegurar que si tu aplicación se bloquea y cuando se bloquee, se reiniciará automáticamente.
+
+#### Usar un gestor de procesos
+
+En desarrollo, ha iniciado su aplicación simplemente desde la línea de comandos con `node server.js` o algo similar. Pero hacer esto en la producción es una receta para el desastre. Si la aplicación falla, estará desconectada hasta que la reinicie. Para asegurar que su aplicación se reinicie si se bloquea, utilice un gestor de procesos. Un gestor de procesos es un "contenedor" para aplicaciones que facilita el despliegue, proporciona alta disponibilidad y le permite gestionar la aplicación en tiempo de ejecución.
+
+Además de reiniciar su aplicación cuando falla, un gestor de procesos puede habilitarlo:
+
+- Obtener información sobre el rendimiento y el consumo de recursos en tiempo de ejecución.
+- Modificar ajustes dinámicamente para mejorar el rendimiento.
+- Clasificación de controles (pm2).
+
+Históricamente, era popular usar un gestor de procesos Node.js como [PM2](https://github.com/Unitech/pm2). Vea su documentación si desea hacer esto. Sin embargo, recomendamos usar su sistema de inicio para la gestión de procesos.
+
+#### Usar un sistema de inicio
+
+La siguiente capa de fiabilidad es asegurar que la aplicación se reinicie cuando el servidor se reinicie. Los sistemas pueden seguir bajando por diversas razones. Para asegurarse de que su aplicación se reinicie si el servidor se bloquea, utilice el sistema init incorporado en su sistema operativo. El sistema principal de inicio en uso hoy es [systemd](https://wiki.debian.org/systemd).
+
+Hay dos formas de usar sistemas de inicio con su aplicación Express:
+
+- Ejecute su aplicación en un gestor de procesos, e instale el gestor de procesos como un servicio con el sistema init. El gestor de procesos reiniciará la aplicación cuando la aplicación se bloquee, y el sistema de inicio reiniciará el gestor de procesos cuando el sistema operativo se reinicie. Este es el enfoque recomendado.
+- Ejecute su aplicación (y Node) directamente con el sistema init. Esto es algo más simple, pero no obtiene las ventajas adicionales de usar un gestor de procesos.
+
+##### Systemd
+
+Systemd es un gestor de servicios y sistemas Linux. La mayoría de las distribuciones de Linux más importantes han adoptado el sistema de inicio como su sistema predeterminado.
+
+Un archivo de configuración de servicio systemd se llama _unit file_, con un nombre de archivo que termina en `.service`. Aquí hay un archivo de unidad de ejemplo para administrar directamente una aplicación de Node. Reemplaza los valores encerrados en `<angle brackets>` para tu sistema y aplicación:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Para más información sobre el sistema, vea la [referencia del sistema (página de manu)] (http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Ejecutar tu aplicación en un clúster
+
+En un sistema multinúcleo, puede aumentar el rendimiento de una aplicación Node muchas veces lanzando un clúster de procesos. Un clúster ejecuta múltiples instancias de la aplicación, idealmente una instancia en cada núcleo de CPU, distribuyendo así la carga y las tareas entre las instancias.
+
+![Balanceo entre las instancias de la aplicación usando la API del clúster](/images/clustering.png)
+
+IMPORTANTE: Dado que las instancias de la aplicación se ejecutan como procesos separados, no comparten el mismo espacio de memoria. Es decir, los objetos son locales a cada instancia de la aplicación. Por lo tanto, no puede mantener el estado en el código de la aplicación. Sin embargo, puede utilizar un datastore en memoria como [Redis](http://redis.io/) para almacenar datos y estado relacionados con la sesión. Esta advertencia se aplica esencialmente a todas las formas de escalado horizontal, ya sea en racimo con múltiples procesos o múltiples servidores físicos.
+
+En las aplicaciones agrupadas, los procesos del worker pueden fallar individualmente sin afectar al resto de los procesos. Aparte de las ventajas de rendimiento, el aislamiento de fallos es otra razón para ejecutar un cluster de procesos de aplicaciones. Cada vez que un proceso worker se bloquea, siempre asegúrese de registrar el evento y generar un nuevo proceso usando cluster.fork().
+
+#### Usando el módulo de cluster del nodo
+
+Clustering es posible con el [módulo de cluster]de Node (https://nodejs.org/api/cluster). Esto permite que un proceso maestro genere procesos de trabajador y distribuya conexiones entrantes entre los trabajadores.
+
+#### Usando PM2
+
+Si implementa su aplicación con PM2, puede aprovechar el clustering _without_ modificando su código de aplicación. Deberías asegurarte de que tu [aplicación está sin estado](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) primero, lo que significa que no hay datos locales almacenados en el proceso (como sesiones, conexiones websocket y similares).
+
+Cuando ejecutas una aplicación con PM2, puedes habilitar el **modo clúster** para ejecutarla en un clúster con varias instancias de tu elección, como el número de CPUs disponibles en la máquina. Puede cambiar manualmente el número de procesos en el clúster usando la herramienta de línea de comandos `pm2` sin detener la aplicación.
+
+Para activar el modo cluster, inicia tu aplicación así:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+Esto también se puede configurar dentro de un archivo de proceso PM2 (`ecosystem.config. s` o similar) estableciendo `exec_mode` a `cluster` y `instancias` al número de workers a comenzar.
+
+Una vez ejecutada, la aplicación puede escalarse así:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+Para más información sobre el clustering con PM2, vea [Modo Cluster](https://pm2.keymetrics.io/docs/usage/cluster-mode/) en la documentación de PM2.
+
+### Resultados de la solicitud de caché
+
+Otra estrategia para mejorar el rendimiento en la producción es almacenar en caché el resultado de las solicitudes, para que tu aplicación no repita la operación para servir la misma petición repetidamente.
+
+Usa un servidor de caché como [Varnish](https://www.varnish-cache.org/) o [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (ver también [Caching Nginx](https://serversforhackers.com/nginx-caching/)) para mejorar enormemente la velocidad y el rendimiento de tu aplicación.
+
+### Usar un balanceador de carga
+
+No importa cuán optimizada sea una aplicación, una sola instancia puede manejar sólo una cantidad limitada de carga y tráfico. Una forma de escalar una aplicación es ejecutar múltiples instancias de ella y distribuir el tráfico a través de un equilibrador de carga. Configurar un balanceador de carga puede mejorar el rendimiento y la velocidad de tu aplicación, y permitirla escalar más de lo posible con una sola instancia.
+
+Un balanceador de carga es generalmente un proxy inverso que orchestriza tráfico hacia y desde múltiples instancias y servidores de la aplicación. Puedes configurar fácilmente un equilibrador de carga para tu aplicación usando [Nginx](https://nginx.org/en/docs/http/load_balancing) o [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+Con el saldo de carga, puede que tenga que asegurarse de que las peticiones que están asociadas con un ID de sesión particular se conectan al proceso que las originó. Esto se conoce como _session affinity_, o _sticky sessions_, y puede ser abordado por la sugerencia anterior de utilizar un almacén de datos como Redis para datos de sesión (dependiendo de su aplicación). Para una discusión, vea [Usando múltiples nodos](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Usar un proxy inverso
+
+Un proxy inverso se sienta frente a una aplicación web y realiza operaciones de soporte en las peticiones, además de dirigir peticiones a la aplicación. Puede manejar páginas de errores, compresión, caché, servir archivos y equilibrar la carga entre otras cosas.
+
+La entrega de tareas que no requieren conocimiento del estado de la aplicación a un proxy inverso libera Express para realizar tareas especializadas de la aplicación. Por esta razón, se recomienda ejecutar Express detrás de un proxy inverso como [Nginx](https://www.nginx.org/) o [HAProxy](https://www.haproxy.org/) en producción.
diff --git a/src/content/pages/es/advanced/best-practice-security.mdx b/src/content/pages/es/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..32c1f8f307
--- /dev/null
+++ b/src/content/pages/es/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Mejores prácticas de producción: seguridad'
+description: Descubra las mejores prácticas de seguridad cruciales para aplicaciones Express en producción, incluyendo el uso de TLS, validación de entradas, cookies seguras y la prevención de vulnerabilidades.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+El término _"producción"_ se refiere a la etapa del ciclo de vida del software cuando una aplicación o API está generalmente disponible para sus usuarios finales o consumidores. En contraste, en la etapa _"desarrollo"_ todavía estás escribiendo activamente y probando código, y la aplicación no está abierta al acceso externo. Los entornos del sistema correspondientes se conocen como entornos _production_ y _development_, respectivamente.
+
+Los entornos de desarrollo y producción suelen establecerse de forma diferente y tienen requisitos muy diferentes. Lo que está bien en desarrollo puede no ser aceptable en la producción. Por ejemplo, en un entorno de desarrollo puede querer un registro detallado de errores para la depuración, mientras que el mismo comportamiento puede convertirse en una preocupación de seguridad en un entorno de producción. Y en desarrollo, usted no necesita preocuparse por la escalabilidad, fiabilidad y rendimiento, mientras que esas preocupaciones se vuelven críticas en la producción.
+
+<Alert type="info">
+
+Si cree que ha descubierto una vulnerabilidad de seguridad en Express, consulte Seguridad
+Políticas y procedimientos.
+
+</Alert>
+
+Las mejores prácticas de seguridad para aplicaciones Express en producción incluyen:
+
+- [Prácticas Mejores de Producción: Seguridad](#production-best-practices-security)
+  - [Overview](#overview)
+  - [No usar versiones obsoletas o vulnerables de Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Usar TLS](#use-tls)
+  - [No confiar en la entrada del usuario](#do-not-trust-user-input)
+    - [Prevenir redirecciones abiertas](#prevent-open-redirects)
+  - [Casco de Uso](#use-helmet)
+  - [Reducir la huella dactilar](#reduce-fingerprinting)
+  - [Usar cookies de forma segura](#use-cookies-securely)
+    - [No usar el nombre de cookie de sesión predeterminado](#dont-use-the-default-session-cookie-name)
+    - [Establecer opciones de seguridad de cookies](#set-cookie-security-options)
+  - [Prevenir ataques de fuerza bruta contra autorización](#prevent-brute-force-attacks-against-authorization)
+  - [Asegúrate de que tus dependencias son seguras](#ensure-your-dependencies-are-secure)
+    - [Evitar otras vulnerabilidades conocidas](#avoid-other-known-vulnerabilities)
+  - [Examen adicional](#additional-considerations)
+
+## No utilizar versiones obsoletas o vulnerables de Express
+
+Las exprés 2.x y 3.x ya no están mantenidas. No se solucionarán problemas de seguridad y rendimiento en estas versiones. ¡No los utilices! Si no has movido a la versión 4, sigue la [guía de migración](/en/guide/migrating-4) o considera [Opciones de Soporte Comercial](/en/support#commercial-support-options).
+
+También asegúrese de que no está usando ninguna de las versiones Express vulnerables listadas en la [página de actualizaciones de seguridad](/en/advanced/security-updates). Si lo está, actualice a una de las versiones estables, preferiblemente la más reciente.
+
+## Usar TLS
+
+Si tu aplicación trata o transmite datos confidenciales, usa [Seguridad de la capa de transporte](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) para asegurar la conexión y los datos. Esta tecnología encripta los datos antes de que sean enviados desde el cliente al servidor, evitando así algunos hacks comunes (y fáciles). Aunque las solicitudes Ajax y POST pueden no ser visiblemente obvias y parecen "ocultas" en los navegadores, su tráfico de red es vulnerable a [sniffing de paquetes](https://en.wikipedia.org/wiki/Packet_analyzer) y [ataques man-in-the-midds](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+Puede estar familiarizado con el cifrado de la capa de conector seguro (SSL). [TLS es simplemente la siguiente progresión de SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). En otras palabras, si estaba usando SSL antes, considere actualizar a TLS. En general, recomendamos Nginx para manejar TLS. Para una buena referencia para configurar TLS en Nginx (y otros servidores), vea [Configuraciones Recomendadas del servidor (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Además, una útil herramienta para obtener un certificado TLS gratis es [Vamos a cifrar](https://letsencrypt.org/about/), un gratuito, automatizado, y autoridad certificadora abierta (CA) proporcionada por el [Grupo de Investigación sobre Seguridad de Internet (ISRG)](https://www.abetterinternet.org/).
+
+## No confiar en la entrada del usuario
+
+Para aplicaciones web, uno de los requisitos de seguridad más importantes es la validación y manejo de entrada de usuario apropiados. Esto viene en muchas formas y no vamos a abarcar todas ellas.
+En última instancia, la responsabilidad de validar y manejar correctamente los tipos de entrada de usuario que su aplicación acepta es suya.
+
+### Evitar redirecciones abiertas
+
+Un ejemplo de entrada de usuario potencialmente peligrosa es una _open redirect_, donde una aplicación acepta una URL como entrada de usuario (a menudo en la consulta de URL, por ejemplo `? rl=https://ejemplo. om`) y usa `res.redirect` para establecer la cabecera `location` y
+devuelve un estado de 3xx.
+
+Una aplicación debe validar que soporta redirección a la URL entrante para evitar enviar usuarios a enlaces maliciosos como sitios web de phishing, entre otros riesgos.
+
+Aquí hay un ejemplo de comprobación de URLs antes de usar `res.redirect` o `res.location`:
+
+```js
+app.use((req, res) => {
+  prueba {
+    if (new Url(req. uery.url).host !== 'ejemplo.com') {
+      return res.status(400). nd(`Unsupported redirect to host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res. tatus(400).end(`URL inválida: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Usar Casco
+
+[Helmet][helmet] puede ayudar a proteger tu aplicación de algunas vulnerabilidades web conocidas configurando los encabezados HTTP adecuadamente.
+
+Helmet es una función middleware que establece cabeceras de respuesta HTTP relacionadas con la seguridad. El casco establece las siguientes cabeceras por defecto:
+
+- `Content-Security-Policy`: Una poderosa lista de permisos de lo que puede pasar en tu página que mitiga muchos ataques
+- `Cross-Origin-Opener-Policy`: Ayuda a procesar su página aislada
+- `Cross-Origin-Resource-Policy`: bloquea que otros carguen sus recursos de origen cruzado
+- `Origin-Agent-Cluster`: Cambia el aislamiento del proceso para ser basado en el origen
+- `Política de referido`: Controla el encabezado [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer)
+- `Strict-Transport-Security`: Indica a los navegadores que prefieran HTTPS
+- `X-Content Type-Options`: Evita [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controla la prebúsqueda DNS
+- `X-Download-Options`: Fuerza a guardar las descargas (sólo Internet Explorer)
+- `X-Frame-Options`: encabezado antiguo que mitiga ataques [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking)
+- `X-Permitted-Cross-Domain-Policies`: Controla el comportamiento entre dominios para los productos de Adobe, como Acrobat
+- `X-Powered-Por`: Información sobre el servidor web. Eliminado porque puede ser usado en ataques simples
+- `X-XSS-Protection`: Encabezado antiguo que intenta mitigar [Ataques XSS](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), pero empeora las cosas, así que Helmet lo deshabilita
+
+Cada cabecera puede ser configurada o deshabilitada. Para leer más al respecto, por favor vaya a [su sitio web de documentación][helmet].
+
+Instalar casco como cualquier otro módulo:
+
+```bash
+$ npm install helmet
+```
+
+Luego para usarlo en tu código:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Reduce la toma de huellas digitales
+
+Puede ayudar a proporcionar una capa extra de seguridad para reducir la capacidad de los atacantes para determinar
+el software que utiliza un servidor. conocido como "huella dactilar". Aunque no es un problema de seguridad en sí mismo,
+reducir la capacidad de huellas dactilares de una aplicación mejora su posición general de seguridad.
+El software del servidor puede ser tomado con huellas dactilares en cómo responde a peticiones específicas, por ejemplo en
+las cabeceras de respuesta HTTP.
+
+Por defecto, Express envía la cabecera de respuesta `X-Powered-By` que puede
+desactivar usando el método `app.disable()`:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="info">
+
+Deshabilitar la \`cabecera X-Powered-By no impide que un atacante sofisticado determine
+que una aplicación está ejecutando Express. It may discourage a casual exploit, but there are other ways to
+determine an app is running Express.
+
+</Alert>
+
+Express también envía sus propios mensajes de respuesta con formato "404 No encontrados" y de error de formato
+. Estos pueden ser cambiados por
+[agregando tu propio gestor de error](/en/starter/faq#how-do-i-handle-404-responses)
+y
+[escribiendo tu propio gestor de error](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// último app.use llama justo antes de app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404).end('¡Lo sentimos no puede encontrar eso!');
+});
+
+// manejador de errores personalizado
+app.se((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo roto!');
+});
+```
+
+## Usar cookies de forma segura
+
+Para asegurar que las cookies no abran su aplicación para explotar, no utilice el nombre de la cookie de sesión por defecto y establezca las opciones de seguridad de las cookies apropiadamente.
+
+Hay dos módulos principales de sesión de cookies de middleware:
+
+- [express-session](https://www.npmjs.com/package/express-session) que reemplaza `express.session` middleware integrado a Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) que reemplaza el middleware `express.cookieSession` integrado a Express 3.x.
+
+La principal diferencia entre estos dos módulos es cómo guardan los datos de sesión de cookies. El middleware [express-session](https://www.npmjs.com/package/express-session) almacena datos de sesión en el servidor; sólo guarda el ID de sesión en la cookie misma, no los datos de sesión. Por defecto, utiliza almacenamiento en memoria y no está diseñado para un entorno de producción. En producción, necesitarás configurar una tienda de sesiones escalable; consulta la lista de [tiendas de sesiones compatibles](https://github.com/expressjs/session#compatible-session-stores).
+
+En contraste, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implementa el almacenamiento respaldado por cookies: serializa toda la sesión a la cookie, en lugar de solo una clave de sesión. Sólo usarlo cuando los datos de sesión son relativamente pequeños y fácilmente codificados como valores primitivos (en lugar de objetos). Aunque los navegadores deben soportar al menos 4096 bytes por cookie, para asegurarse de que no exceda el límite, no exceda un tamaño de 4093 bytes por dominio. Además, tenga en cuenta que los datos de las cookies serán visibles para el cliente, así que si hay alguna razón para mantenerlo seguro u oscuro, entonces `express-session` puede ser una mejor elección.
+
+### No utilizar el nombre predeterminado de la cookie de sesión
+
+Usar el nombre de la cookie de sesión por defecto puede abrir su aplicación para atacar. El problema de seguridad planteado es similar al de `X-Powered-Por`: un atacante potencial puede usarlo para tomar las huellas dactilares del servidor y atacar en consecuencia.
+
+To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // confíe en primer proxy
+aplicación.se(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Configurar opciones de seguridad de cookies
+
+Establecer las siguientes opciones de cookie para mejorar la seguridad:
+
+- `secure` - Asegura que el navegador sólo envía la cookie a través de HTTPS.
+- `httpOnly` - Asegura que la cookie se envía sólo sobre HTTP(S), no sobre JavaScript del cliente, ayudando a proteger contra ataques de cross-site scripting.
+- `domain` - indica el dominio de la cookie; úselo para comparar con el dominio del servidor en el que se solicita la URL. Si coinciden, entonces marque el atributo de ruta siguiente.
+- `path` - indica la ruta de la cookie; úsala para comparar la ruta de la solicitud. Si esto y el dominio coinciden, entonces envíe la cookie en la solicitud.
+- `expires` - usa para fijar la fecha de caducidad de las cookies persistentes.
+
+Aquí hay un ejemplo usando un middleware [cookie-session](https://www.npmjs.com/package/cookie-session):
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.ow() + 60 * 60 * 1000); // 1 hora
+aplicación.se(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      dominio: 'ejemplo. om',
+      ruta: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## Evitar ataques de fuerza bruta contra autorización
+
+Asegúrese de que los puntos finales de inicio de sesión están protegidos para hacer que los datos privados sean más seguros.
+
+Una técnica simple y poderosa es bloquear los intentos de autorización utilizando dos métricas:
+
+1. El número de intentos fallidos consecutivos por el mismo nombre de usuario y dirección IP.
+2. El número de intentos fallidos de una dirección IP durante un largo período de tiempo. Por ejemplo, bloquee una dirección IP si hace 100 intentos fallidos en un día.
+
+Un paquete [rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) proporciona herramientas para hacer esta técnica fácil y rápida. Puedes encontrar [un ejemplo de protección de fuerza bruta en la documentación](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Asegúrate de que tus dependencias son seguras
+
+Usar npm para administrar las dependencias de tu aplicación es potente y conveniente. Pero los paquetes que usa pueden contener vulnerabilidades de seguridad críticas que también podrían afectar a su aplicación. La seguridad de tu aplicación es tan fuerte como el "enlace más débil" en tus dependencias.
+
+Desde npm@6, npm revisa automáticamente cada solicitud de instalación. También, puede usar `npm audit` para analizar su árbol de dependencias.
+
+```bash
+$ npm auditoría
+```
+
+Si quieres estar más seguro, considera [Snyk](https://snyk.io/).
+
+Snyk ofrece una [herramienta de línea de comandos](https://www.npmjs.com/package/snyk) y una [integración de Github](https://snyk.io/docs/github) que comprueba tu aplicación contra [la base de datos de vulnerabilidad de código abierto de Snyk](https://snyk.io/vuln/) para cualquier vulnerabilidad conocida en tus dependencias. Instalar el CLI de la siguiente manera:
+
+```bash
+$ npm install -g snyk
+$ cd tu-app
+```
+
+Utilice este comando para probar las vulnerabilidades de su aplicación:
+
+```bash
+$ prueba de snyk
+```
+
+### Evitar otras vulnerabilidades conocidas
+
+Esté atento a los avisos de [Node Security Project](https://npmjs.com/advisories) o [Snyk](https://snyk.io/vuln/) que pueden afectar a Express u otros módulos que tu aplicación utiliza. En general, estas bases de datos son excelentes recursos para conocimientos y herramientas sobre la seguridad de Node.
+
+Finalmente, las aplicaciones Express&mdash;como cualquier otra aplicación web&mdash;pueden ser vulnerables a una variedad de ataques basados en la web. Familiarizarse con [vulnerabilidades web](https://www.owasp.org/www-project-top-ten/) y tomar precauciones para evitarlas.
+
+## Consideraciones adicionales
+
+Estas son algunas recomendaciones adicionales de la excelente [Lista de verificación de seguridad de Node.js](https://blog.risingstack.com/node-js-security-checklist/). Consulte esa entrada para ver todos los detalles de estas recomendaciones:
+
+- Siempre filtrar y limpiar la entrada del usuario para proteger contra ataques de cross-site scripting (XSS) e inyección de comandos.
+- Defienda contra ataques de inyección de SQL usando consultas parametrizadas o sentencias preparadas.
+- Utilice la herramienta de código abierto [sqlmap](http://sqlmap.org/) para detectar vulnerabilidades de inyección SQL en su aplicación.
+- Utilice las herramientas [nmap](https://nmap.org/) y [sslyze](https://github.com/nabla-c0d3/sslyze) para probar la configuración de sus cifrados SSL, llaves, renegociación, así como la validez de su certificado.
+- Usa [safe-regex](https://www.npmjs.com/package/safe-regex) para asegurar que tus expresiones regulares no sean susceptibles a los ataques de [denegación de expresión regular de servicio](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/es/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/es/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..bb0926aaa2
--- /dev/null
+++ b/src/content/pages/es/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Comprobaciones de salud y apagado positivo
+description: Aprende cómo implementar comprobaciones de salud y apagado con gracia en aplicaciones Express para mejorar la confiabilidad, administrar implementaciones e integrarse con equilibradores de carga como Kubernetes.
+---
+
+## Apagado controlado
+
+Cuando despliegues una nueva versión de tu aplicación, debes reemplazar la versión anterior. El gestor de procesos que está utilizando enviará primero una señal de SIGTERM a la aplicación para notificarle que será asesinado. Una vez que la aplicación reciba esta señal, debería dejar de aceptar nuevas solicitudes, terminar todas las solicitudes en curso, limpiar los recursos que utilizó, incluyendo conexiones de base de datos y bloqueos de archivos y luego salir.
+
+### Ejemplo
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Revisiones de salud
+
+Un balanceador de carga utiliza cheques de salud para determinar si una instancia de aplicación es saludable y puede aceptar solicitudes. Por ejemplo, [Kubernetes tiene dos cheques de salud](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, que determina cuándo reiniciar un contenedor.
+- `readiness`, que determina cuando un contenedor está listo para empezar a aceptar tráfico. Cuando un pod no está listo, se elimina de los balanceadores de carga de servicio.
diff --git a/src/content/pages/es/advanced/security-updates.mdx b/src/content/pages/es/advanced/security-updates.mdx
new file mode 100644
index 0000000000..a2b561bbff
--- /dev/null
+++ b/src/content/pages/es/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Actualización de seguridad
+description: Revise las últimas actualizaciones de seguridad y los parches de Express.js, incluyendo listas detalladas de vulnerabilidades para diferentes versiones para ayudar a mantener una aplicación segura.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="alerta">
+
+Las vulnerabilidades de Node.js afectan directamente a Express. Por lo tanto, vigila Node.js
+vulnerabilidades y asegúrate de que estás usando la última versión
+estable de Node.js.
+
+</Alert>
+
+La siguiente lista enumera las vulnerabilidades Express que se corrigieron en la actualización de versión especificada.
+
+<Alert type="info">
+
+Si cree que ha descubierto una vulnerabilidad de seguridad en Express, consulte Seguridad
+Políticas y procedimientos.
+
+</Alert>
+
+## 4 x
+
+- 4.21.2
+  - La dependencia `path-to-regexp` ha sido actualizada para direccionar un [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - La dependencia `cookie` ha sido actualizada para dirigirse a una [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), Esto puede afectar a tu aplicación si utilizas `res.cookie`.
+- 4.20.0
+  - Se corrigió la vulnerabilidad XSS en `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - La dependencia `serve-static` ha sido actualizada para direccionar un [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - La dependencia `send` ha sido actualizada para direccionar un [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - La dependencia `path-to-regexp` ha sido actualizada para direccionar un [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - La dependencia `body-parser` ha sido actualizada para montar un [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), Esto puede afectar a tu aplicación si tenías activada la conexión url.
+- 4.19.0, 4.19.1
+  - Corregida vulnerabilidad de redirección abierta en `res.location` y `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - La dependencia `qs` ha sido actualizada para direccionar un [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). Esto puede afectar a su aplicación si se utilizan las siguientes API: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - La dependencia `forwarded` ha sido actualizada para direccionar un [vulnerability](https://npmjs.com/advisories/527). Esto puede afectar a su aplicación si se utilizan las siguientes API: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - La dependencia `mime` ha sido actualizada para abordar un [vulnerability](https://npmjs.com/advisories/535), pero este problema no afecta a Express.
+  - La dependencia `send` ha sido actualizada para proporcionar una protección contra una [vulnerabilidad de Node.js 8.5.0](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Esto sólo afecta a la ejecución de Express en la versión 8.5.0 específica de Node.js.
+- 4.15.5
+  - La dependencia `debug` ha sido actualizada para abordar un [vulnerability](https://snyk.io/vuln/npm:debug:20170905), pero este problema no afecta a Express.
+  - La dependencia `fresh` ha sido actualizada para direccionar un [vulnerability](https://npmjs.com/advisories/526). Esto afectará a tu aplicación si se utilizan las siguientes API: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - La dependencia `ms` ha sido actualizada para direccionar un [vulnerability](https://snyk.io/vuln/npm:ms:20170412). Esto puede afectar a tu aplicación si la entrada de cadena no confiable es pasada a la opción `maxAge` en las siguientes APIs: `express.static`, `res.sendfile`, y `res.sendFile`.
+- 4.15.2
+  - La dependencia `qs` ha sido actualizada para abordar un [vulnerability](https://snyk.io/vuln/npm:qs:20170213), pero este problema no afecta a Express. Actualizar a 4.15.2 es una buena práctica, pero no es necesario para abordar la vulnerabilidad.
+- 4.11.1
+  - Se corrigió la vulnerabilidad de revelación de ruta de root en `express.static`, `res.sendfile`, y `res.sendFile`
+- 4.10.7
+  - Se corrigió la vulnerabilidad de redirección abierta en `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Se corrigieron vulnerabilidades de recorrido de directorio en `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 puede filtrar `fd`s en ciertas situaciones que afectan `express.static` y `res.sendfile`. Las peticiones maliciosas podrían causar que `fd`s se filtrara y eventualmente llevar a `EMFILE` errores y la falta de respuesta del servidor.
+- 4.8.0
+  - Las matrices Sparse que tienen índices extremadamente altos en la cadena de consultas podrían causar que el proceso se quedara sin memoria y cayera el servidor.
+  - Los objetos de cadena de consulta anidados pueden causar que el proceso bloquee y haga que el servidor no responda temporalmente.
+
+## 3.x
+
+<Alert type="advertencia">
+**Express 3.x está END-OF-LIFE Y NINGUNA LONGERA MAINTADA**
+
+Los problemas de seguridad y rendimiento conocidos y desconocidos en 3.x no han sido abordados desde la última actualización (1 de agosto de 2015). Es altamente recomendable utilizar la última versión de Express.
+
+Si no puedes actualizar más allá de 3.x, por favor considera [Opciones de Soporte Comercial](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Se corrigió la vulnerabilidad de revelación de ruta de root en `express.static`, `res.sendfile`, y `res.sendFile`
+- 3.19.0
+  - Se corrigió la vulnerabilidad de redirección abierta en `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Se corrigieron vulnerabilidades de recorrido de directorio en `express.static`.
+- 3.16.6
+  - Node.js 0.10 puede filtrar `fd`s en ciertas situaciones que afectan `express.static` y `res.sendfile`. Las peticiones maliciosas podrían causar que `fd`s se filtrara y eventualmente llevar a `EMFILE` errores y la falta de respuesta del servidor.
+- 3.16.0
+  - Las matrices Sparse que tienen índices extremadamente altos en la cadena de consultas podían causar que el proceso se quedara sin memoria y cayera el servidor.
+  - Los objetos de cadena de consulta anidados pueden causar que el proceso bloquee y haga que el servidor no responda temporalmente.
+- 3.3.0
+  - La respuesta 404 de un intento de anulación de método no soportado era susceptible a ataques de cross-site scripting.
diff --git a/src/content/pages/es/guide/database-integration.mdx b/src/content/pages/es/guide/database-integration.mdx
new file mode 100644
index 0000000000..6bce2faa8f
--- /dev/null
+++ b/src/content/pages/es/guide/database-integration.mdx
@@ -0,0 +1,502 @@
+---
+title: Integración de la base de datos
+description: Descubra cómo integrar varias bases de datos con aplicaciones Express.js, incluyendo ejemplos de configuración para MongoDB, MySQL, PostgreSQL, y más.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Añadir la capacidad para conectar bases de datos a aplicaciones Express es sólo una cuestión de cargar un controlador Node.js apropiado para la base de datos en su aplicación. Este documento explica brevemente cómo agregar y utilizar algunos de los módulos Node.js más populares para sistemas de base de datos en su aplicación Express:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [Servidor SQL](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="alerta">
+
+Estos controladores de base de datos están entre muchos que están disponibles. Para otras opciones, busca en el sitio
+[npm](https://www.npmjs.com/).
+
+</Alert>
+
+## Cassandra
+
+**Módulo**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Instalación
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Ejemplo
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.xecute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Módulo**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Instalación
+
+```bash
+$ npm install couchbase
+```
+
+### Ejemplo
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// añade un documento al cubo
+bucket.nsert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    consola.og(err);
+  } else {
+    consola.og(result);
+  }
+});
+
+// obtener todos los documentos con el tamaño de zapato 13
+const n1ql = 'SELECT d. FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery.romString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    consola.og(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Módulo**: [nano](https://github.com/dscape/nano)
+
+### Instalación
+
+```bash
+$ npm install nano
+```
+
+### Ejemplo
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.se('books');
+
+// Inserta un documento de libro en la base de datos de libros
+libros.nsert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console.og(err);
+  } else {
+    consola.og(body);
+  }
+});
+
+// Obtén una lista de todos los libros
+libros.ist((err, body) => {
+  if (err) {
+    consola.og(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Módulo**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Instalación
+
+```bash
+$ npm instalar nivel de nivelación
+```
+
+### Ejemplo
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.ut('nombre', 'LevelUP', (err) => {
+  if (err) return console.log('¡Ooops!', err);
+
+  db.et('nombre', (err, value) => {
+    if (err) return consola.og('¡Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Módulo**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Instalación
+
+```bash
+$ npm install mysql
+```
+
+### Ejemplo
+
+```js
+const (0)[video] ql = require('mañql');
+const connection = .Uql. reateConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+conexión. onnect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, filas, campos) => {
+  if (err) throw err;
+
+  consola. og('La solución es: ', filas[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Módulo**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Instalación
+
+```bash
+$ npm install mongodb
+```
+
+### Ejemplo (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.ollection('mammals')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      consola.og(resultado);
+    });
+});
+```
+
+### Ejemplo (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.b('animales');
+
+  db.collection('mammals')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      consola.og(resultado);
+    });
+});
+```
+
+Si quieres un controlador de modelo de objeto para MongoDB, mira [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Módulo**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Instalación
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Ejemplo
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.asic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .un('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].et('count'));
+    })
+    .catch((error) => {
+      consola.og(error);
+    });
+});
+```
+
+## Oráculo
+
+**Módulo**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Instalación
+
+NOTA: [Ver los prerrequisitos de instalación](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Ejemplo
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb. etConnection(config);
+
+    const result = await conn. xecute('select * from employees where employee_id = :id', [empId]);
+
+    consola. og(result.rows[0]);
+  } catch (err) {
+    consola. og('¡Og! , err);
+  } finally {
+    if (conn) {
+      // asignación conn trabajada, necesitan cerrar
+      esperando conn. lose();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Módulo**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Instalación
+
+```bash
+$ npm install pg-promise
+```
+
+### Ejemplo
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .hen((data) => {
+    console.log('DATA:', data.value);
+  })
+  .atch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Módulo**: [redis](https://github.com/mranney/node_redis)
+
+### Instalación
+
+```bash
+$ npm install redis
+```
+
+### Ejemplo
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+cliente.et('clave de cadena', 'valor de cadena', redis.print);
+client.hset('clave hash', 'hashtest 1', 'some value', redis.print);
+cliente.set(['hash key', 'hashtest 2', 'algún otro valor'], redis.print);
+Cliente.keys('clave hash', (err, respuestas) => {
+  console.log(`${replies.length} respuestas:`);
+
+  respuestas.orEach((reply, i) => {
+    consola.og(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL Server
+
+**Módulo**: [tedious](https://github.com/tediousjs/tedious)
+
+### Instalación
+
+```bash
+$ npm install tedious
+```
+
+### Ejemplo
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious').equest;
+
+const config = {
+  server: 'localhost',
+  autenticación: {
+    type: 'default',
+    opciones: {
+      userName: 'su_usuario', // actualizarme
+      contraseña: 'su_contraseña', // actualizarme
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection.n('connect', (err) => {
+  if (err) {
+    consola.og(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hola mundo'", (err, rowCount) => {
+    if (err) {
+      consola.og(err);
+    } else {
+      consola.og(`${rowCount} filas`);
+    }
+    conexión.lose();
+  });
+
+  request.on('fila', (columnas) => {
+    columnas.orEach((column) => {
+      if (column.value === null) {
+        consola.og('NULL');
+      } else {
+        console.log(column.alue);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Módulo**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Instalación
+
+```bash
+$ npm install sqlite3
+```
+
+### Ejemplo
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.un('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.repare('INSERT INTO Lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.un(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.ach('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    consola.og(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Búsqueda elástica
+
+**Módulo**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Instalación
+
+```bash
+$ npm instalar elasticsearch
+```
+
+### Ejemplo
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .earch({
+    index: 'libros',
+    tipo: 'libro',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          campos: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .hen(
+    (response) => {
+      const hits = response.hits.its;
+    },
+    (error) => {
+      consola.race(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/es/guide/migrating-4.mdx b/src/content/pages/es/guide/migrating-4.mdx
new file mode 100644
index 0000000000..2aacb9445c
--- /dev/null
+++ b/src/content/pages/es/guide/migrating-4.mdx
@@ -0,0 +1,664 @@
+---
+title: Moviendo a Express 4
+description: Una guía para migrar sus aplicaciones Express.js de la versión 3 a 4, que cubre los cambios en middleware, routing, y cómo actualizar su código base efectivamente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 es un cambio de ruptura de Express 3. Esto significa que una aplicación Express 3 funcionará _no_ si actualiza la versión Express en sus dependencias.
+
+Este artículo cubre:
+
+<ul class="doclista">
+  <li>
+    <a href="#changes">Cambios en Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">Un ejemplo</a> de migrar una aplicación Express 3 a Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Upgrading to the Express 4 app generator</a>.
+  </li>
+</ul>
+
+## Cambios en Express 4
+
+Hay varios cambios significativos en Express 4:
+
+<ul class="doclista">
+  <li>
+    <a href="#core-changes">Cambios a Express core y middleware.</a> Las dependencias de Conectar y
+    middleware integrados fueron eliminadas, por lo que debe añadir middleware usted mismo.
+  </li>
+  <li>
+    <a href="#routing">Cambia al sistema de enrutamiento.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Otros cambios varios.</a>
+  </li>
+</ul>
+
+Ver también:
+
+- [Nuevas características en 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migración de 3.x a 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Cambios al sistema Express core y middleware
+
+Express 4 ya no depende de Connect, y elimina todo el Middleware integrado
+de su núcleo, excepto la función `express.static`. Esto significa que
+Express es ahora un entorno web independiente de enrutamiento y middleware. y
+Las versiones y versiones exprés no se ven afectadas por las actualizaciones de middleware.
+
+Sin middleware integrado, debe agregar explícitamente todo el Middleware
+que es necesario para ejecutar su aplicación. Simplemente sigue estos pasos:
+
+1. Instala el módulo: `npm install --save <module-name>`
+2. En tu aplicación, requiere el módulo: `require('module-name')`
+3. Utilice el módulo de acuerdo a su documentación: `app.use( ... )`
+
+La siguiente tabla muestra Express 3 middleware y sus contrapartes en Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compresione</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compresión</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">sesión de galletas</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">parser cookie-</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-sesión</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">tiempo de respuesta</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">sobrescribir método</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">tiempo de espera de conexión</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">serve-static</a>
+    </td>
+  </tr>
+</table>
+
+Aquí está la [lista completa](https://github.com/senchalabs/connect#middleware) de Middleware Express 4.
+
+En la mayoría de los casos, puede reemplazar el middleware de la versión 3 anterior por
+su contraparte Express 4. Para más detalles, consulte la documentación del módulo en
+GitHub.
+
+#### `app.use` acepta parámetros
+
+En la versión 4 se puede utilizar un parámetro variable para definir la ruta donde se cargan las funciones de middleware, entonces lea el valor del parámetro del gestor de rutas.
+Por ejemplo:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### El sistema de enrutamiento
+
+Aplicaciones ahora cargan implícitamente middleware de ruta, así que ya no tienes que preocuparte por
+del orden en el que el middleware está cargado con respecto a
+el middleware `router`.
+
+La forma en que defines las rutas no ha cambiado, pero el sistema de enrutamiento tiene dos características
+nuevas para ayudar a organizar tus rutas:
+
+- Un nuevo método, `app.route()`, para crear manejadores de rutas encadenables para una ruta de ruta.
+- Una nueva clase, `express.Router`, para crear manejadores modulares de rutas montables.
+
+#### método `app.route()`
+
+El nuevo método `app.route()` le permite crear controladores de rutas encadenables
+para una ruta de ruta. Debido a que el camino se especifica en una única ubicación, crear rutas modulares es útil, al igual que reducir redundancia y errores tipográficos. For more
+information about routes, see [`Router()` documentation](/en/4x/api#router).
+
+Aquí hay un ejemplo de manejadores encadenados de rutas que se definen usando la función `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Obtén un libro al azar');
+  })
+  .ost((req, res) => {
+    res.send('Agregar un libro');
+  })
+  .ut((req, res) => {
+    res.send('Actualizar el libro');
+  });
+```
+
+#### Clase `express.Router`
+
+La otra característica que ayuda a organizar rutas es una nueva clase,
+`express.Router`, que puedes usar para crear manejadores de rutas modulares montables
+. Una instancia `Router` es un completo middleware y un sistema de enrutamiento
+; por esta razón a menudo se le denomina "mini-app".
+
+El siguiente ejemplo crea un enrutador como módulo, carga middleware en
+, define algunas rutas y las monta en una ruta en la aplicación principal.
+
+Por ejemplo, crea un archivo de enrutador llamado `birds.js` en el directorio de la aplicación,
+con el siguiente contenido:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware específico para este router
+. se((req, res, next) => {
+  console.log('Hora: ', Date. ow());
+  siguiente();
+});
+// define el router
+de la página de inicio. et('/', (req, res) => {
+  res.send('Página inicial de aves');
+});
+// define la ruta
+router. et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Luego, cargue el módulo de enrutador en la aplicación:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', aves);
+```
+
+La aplicación ahora podrá manejar las solicitudes a las rutas `/birds` y
+`/birds/about`, y llamará al middleware `timeLog`
+que es específico de la ruta.
+
+### Otros cambios
+
+La siguiente tabla muestra otros cambios pequeños pero importantes en Express 4:
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Objeto</th>
+    <th>Descripción</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>
+      Express 4 requiere Node.js 0.10.x o posterior y ha eliminado el soporte para Node.js 0.8.x.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      El módulo `http` ya no es necesario, a menos que necesite trabajar directamente con él
+      (socket.io/SPDY/HTTPS). La aplicación puede iniciarse usando la función `app.listen()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      La función `app.configure()` ha sido eliminada. Usa la función `process.env.NODE_ENV` o
+      `app.get('env')` para detectar el entorno y configurar la aplicación en consecuencia.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`espacios json`</td>
+    <td markdown="1">
+      La propiedad de aplicación `json spaces` está deshabilitada por defecto en Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Usa `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, y
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">Ya no resuelve las URL relativas.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">Era un arreglo; ahora un objeto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Era una función; ahora un objeto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Cambiado a `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Ahora disponible como `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('encabezado')`</td>
+    <td markdown="1">Eliminado.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Eliminado.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      La funcionalidad ahora se limita a establecer el valor básico de la cookie. Usa `res.cookie()`
+      para añadir funcionalidad .
+    </td>
+  </tr>
+</table>
+
+## Ejemplo de migración de aplicación
+
+He aquí un ejemplo de migración de una aplicación Express 3 a Express 4.
+Los archivos de interés son `app.js` y `package.json`.
+
+### Versión 3 app
+
+#### `app.js`
+
+Considere una aplicación Express v.3 con el siguiente archivo `app.js`:
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('. routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// todos los entornos
+app.et('puerto', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.ession({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.tatic(path.join(__dirname, 'public')));
+
+// desarrolla sólo
+if (app.get('env') === 'development') {
+  app.se(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.reateServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+El archivo `package.json` de la versión 3 que acompaña podría verse
+algo así:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. "
+  },
+  "dependencies": {
+    "express": "3. 2.0",
+    "pug": "*"
+  }
+}
+```
+
+### Proceso
+
+Comience el proceso de migración instalando el middleware necesario para la aplicación
+Express 4 y actualizando Express y Pug a su respectiva versión
+con el siguiente comando:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Hacer los siguientes cambios a `app.js`:
+
+1. El middleware Express incorporado funciona `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` y
+   `express.errorHandler` ya no están disponibles en el objeto
+   `express`. Debes instalar sus alternativas
+   manualmente y cargarlas en la aplicación.
+
+2. Ya no necesitas cargar la función `app.router`.
+   No es un objeto de aplicación Express 4 válido, por lo que elimina el código
+   `app.use(app.router);`.
+
+3. Asegúrese de que las funciones de middleware se cargan en el orden correcto - cargar `errorHandler` después de cargar las rutas de la aplicación.
+
+### Versión 4 app
+
+#### `package.json`
+
+Ejecutar el comando anterior `npm` actualizará `package.json` de la siguiente manera:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. "
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1. ",
+    "express": "^4.8.0",
+    "express-session": "^1. .2",
+    "pug": "^2.0.0",
+    "method-override": "^2. .2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1. ",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Luego, elimina el código inválido, carga el middleware necesario y haz otros cambiosformat@@0
+según sea necesario. El archivo `app.js` se verá así:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('. routes/usuario');
+var path = require('ruta');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// todos los entornos
+app.et('puerto', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.se(methodOverride());
+app.se(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secretos: 'uwotm8',
+  })
+);
+aplicaciones.se(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', rutas.ndex);
+app.get('/users', user.list);
+
+// middleware de manejo de error debe ser cargado después de la carga de las rutas
+if (app.et('env') === 'development') {
+  app.se(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.et('puerto'), () => {
+  console.log('Servidor expreso escuchando en el puerto ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+A menos que necesite trabajar directamente con el módulo `http` (socket.io/SPDY/HTTPS), cargarlo no es necesario, y la aplicación puede iniciarse simplemente de esta manera:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Servidor Express escuchando en el puerto ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Ejecutar la aplicación
+
+El proceso de migración se ha completado, y la aplicación es ahora una aplicación
+Express 4. Para confirmar, inicia la aplicación usando el siguiente comando:
+
+```bash
+$ nodo .
+```
+
+Cargar [http://localhost:3000](http://localhost:3000)
+y ver la página de inicio mostrada por Express 4.
+
+## Actualización al generador de aplicaciones Express 4
+
+La herramienta de línea de comandos para generar una aplicación Express sigue siendo
+`express`, pero para actualizar a la nueva versión, debe desinstalar
+el generador de aplicaciones Express 3 y luego instalar el nuevo generador
+`express-generator`.
+
+### Instalando
+
+Si ya tiene instalado el generador de aplicaciones Express 3 en su sistema,
+debe desinstalarlo:
+
+```bash
+$ npm desinstalar -g express
+```
+
+Dependiendo de cómo estén configurados tus privilegios de archivo y directorio,
+puede que necesites ejecutar este comando con `sudo`.
+
+Ahora instale el nuevo generador:
+
+```bash
+$ npm install -g express-generator
+```
+
+Dependiendo de cómo estén configurados tus privilegios de archivo y directorio,
+puede que necesites ejecutar este comando con `sudo`.
+
+Ahora el comando `express` en su sistema se actualiza al generador
+Express 4.
+
+### Cambios al generador de aplicaciones
+
+Las opciones de comando y uso siguen siendo en gran medida las mismas, con las siguientes excepciones:
+
+- Se ha eliminado la opción `--sessions`.
+- Se ha eliminado la opción `--jshtml`.
+- Se añadió la opción `--hogan` para soportar [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Ejemplo
+
+Ejecutar el siguiente comando para crear una aplicación Express 4:
+
+```bash
+$ app4 expreso
+```
+
+Si observas el contenido del archivo `app4/app.js`, notarás
+que todas las funciones de middleware (excepto `express. tatic`) que son requeridos para
+la aplicación se cargan como módulos independientes, y el middleware `router`
+ya no se carga explícitamente en la aplicación.
+
+También notará que el archivo `app.js` es ahora un Nodo. , en contraste con la aplicación independiente generada por el generador anterior.
+
+Después de instalar las dependencias, inicie la aplicación usando el siguiente comando:
+
+```bash
+$ npm inicio
+```
+
+Si miras el script `npm start` en el `paquete. archivo son`,
+notarás que el comando real que inicia la aplicación es
+`node . bin/www`, que solía ser `node app.js`
+en Express 3.
+
+Porque el archivo `app.js` que fue generado por el generador Express 4
+es ahora un Nodo. s módulo, ya no puede iniciarse independientemente como una aplicación
+(a menos que modifiques el código). El módulo debe cargarse en un archivo Node.js
+y debe iniciarse a través del archivo Node.js. El archivo Node.js es `./bin/www`
+en este caso.
+
+Ni el directorio `bin` ni el archivo sin extensión `www`
+es obligatorio para crear una aplicación Express o iniciar la aplicación. Son
+solo sugerencias hechas por el generador, así que siéntete libre de modificarlas para adaptarse a tus
+necesidades.
+
+Para deshacerse del directorio `www` y mantener las cosas de la forma "Express 3",
+borrar la línea que dice `module. xports = app;` al final del archivo
+`app.js`, luego pega el siguiente código en su lugar:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Servidor Express escuchando en el puerto ' + server.address().port);
+});
+```
+
+Asegúrese de cargar el módulo `debug` en la parte superior del archivo `app.js` usando el siguiente código:
+
+```js
+var debug = require('debug')('app4');
+```
+
+A continuación, cambia `"start": "node ./bin/www"` en el archivo `package.json` a `"start": "node app.js"`.
+
+Ahora ha movido la funcionalidad de `./bin/www` de vuelta a
+`app.js`. Este cambio no es recomendable, pero el ejercicio te ayuda
+a entender cómo el `. bin/www` archivo funciona, y por qué el archivo `app.js`
+ya no comienza por sí mismo.
diff --git a/src/content/pages/es/guide/migrating-5.mdx b/src/content/pages/es/guide/migrating-5.mdx
new file mode 100644
index 0000000000..8a7f831a4a
--- /dev/null
+++ b/src/content/pages/es/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Moviendo a Express 5
+description: Una guía completa para migrar sus aplicaciones Express.js de la versión 4 a 5, detallando los cambios de ruptura, métodos obsoletos y nuevas mejoras.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 no es muy diferente de Express 4; aunque mantiene la misma API básica, todavía hay cambios que rompen la compatibilidad con la versión anterior. Por lo tanto, una aplicación construida con Express 4 podría no funcionar si la actualiza para usar Express 5.
+
+Para instalar esta versión, necesita tener una versión 18 o superior de Node.js. Luego, ejecuta el siguiente comando en el directorio de tu aplicación:
+
+```sh
+npm instalar "express@5"
+```
+
+Luego puede ejecutar sus pruebas automatizadas para ver qué falla, y arreglar problemas de acuerdo a las actualizaciones que se listan a continuación. Después de gestionar los fallos de prueba, ejecuta tu aplicación para ver qué errores ocurren. Descubrirá de inmediato si la aplicación utiliza cualquier método o propiedades que no sean compatibles.
+
+## Códigos Express 5
+
+Para ayudarle a migrar su servidor exprés, hemos creado un conjunto de códigos que te ayudarán a actualizar automáticamente tu código a la última versión de Express.
+
+Ejecutar el siguiente comando para ejecutar todos los codemods disponibles:
+
+```sh
+codemod@latest @expressjs/v5-migration-recipe
+```
+
+Si quieres ejecutar un código específico, puedes ejecutar el siguiente comando:
+
+```sh
+codemod@latest @expressjs/nombre-codemod npx
+```
+
+Puedes encontrar la lista de códigos disponibles [here](https://codemod.link/express).
+
+## Cambios en Express 5
+
+**Métodos y propiedades eliminadas**
+
+<ul class="doclista">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">El método multiplicado nombra</a>
+  </li>
+  <li>
+    <a href="#leading">Leading colon in name argument to app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(nombre)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') y res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:router debug logs</a>
+  </li>
+</ul>
+
+**Cambiado**
+
+<ul class="doclista">
+  <li>
+    <a href="#path-syntax">Ruta de ruta que coincide con la sintaxis</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">promesas rechazadas manejadas por middleware y manejadores</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Mejoras**
+
+<ul class="doclista">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Soporte de codificación de Brotli</a>
+  </li>
+</ul>
+
+## Métodos y propiedades eliminados
+
+Si utiliza cualquiera de estos métodos o propiedades en su aplicación, se bloqueará. Por lo tanto, necesitarás cambiar tu aplicación después de actualizar a la versión 5.
+
+### app.del()
+
+Express 5 ya no soporta la función `app.del()`. Si utiliza esta función, se arroja un error. Para registrar rutas HTTP DELETE, utilice la función `app.delete()` en su lugar.
+
+Inicialmente, `del` fue usado en lugar de `delete`, porque `delete` es una palabra clave reservada en JavaScript. Sin embargo, a partir de ECMAScript 6, `delete` y otras palabras clave reservadas pueden utilizarse legalmente como nombres de propiedad.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+codemod@latest @expressjs/route-del-de-borrar npx
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.elete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+La firma `app.param(fn)` fue usada para modificar el comportamiento de la función `app.param(name, fn)`. Ha sido obsoleto desde v4.11.0, y Express 5 ya no lo soporta en absoluto.
+
+### Nombres de métodos pluralizados
+
+Los siguientes nombres de métodos han sido pluralizados. En Express 4, el uso de los métodos antiguos resultó en una advertencia de desaprobación. Express 5 ya no los soporta:
+
+`req.acceptsCharset()` es reemplazado por `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` es reemplazado por `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` es reemplazado por `req.acceptsLanguages()`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-nombre-método-
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.cceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.ll('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('es');
+
+  // ...
+});
+```
+
+### Posible coma (:) en el nombre de app.param(nombre, fn)
+
+Un personaje con dos puntos (:) en el nombre de la aplicación `. aram(name, fn)` función es un remanente de Express 3, y por el bien de la compatibilidad hacia atrás, Express 4 lo soportó con un aviso de desaprobación. Express 5 lo ignorará silenciosamente y usará el parámetro de nombre sin prefijarlo con dos puntos.
+
+Esto no debería afectar tu código si sigues la documentación Express 4 de [app.param](/en/4x/api#app.param), ya que no hace mención alguna de los dos puntos principales.
+
+### req.param(nombre)
+
+Se ha eliminado este método potencialmente confuso y peligroso de recuperar datos de formularios. Ahora necesitará buscar específicamente el nombre del parámetro enviado en el objeto `req.params`, `req.body`, o `req.query`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+codemod@latest @expressjs/explícit-request-params npx
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.aram('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.d;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, estado)
+
+Express 5 ya no soporta la firma `res.json(obj, status)`. En su lugar, establece el estado y luego lo encadena al método `res.json()` de esta manera: `res.status(status).json(obj)`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-end
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 ya no soporta la firma `res.jsonp(obj, status)`. En su lugar, establece el estado y luego lo encadena al método `res.jsonp()` de esta manera: `res.status(status).jsonp(obj)`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-end
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Express 5 ya no soporta la firma `res.redirect(url, status)`. En su lugar, utilice la siguiente firma: `res.redirect(status, url)`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+codemod@latest @expressjs/redirect-arg-order npx
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') y res.location('back')
+
+Express 5 ya no soporta la cadena mágica `back` en los métodos `res.redirect()` y `res.location()`. En su lugar, utilice el valor `req.get('Referrer') || '/'` para redirigir de vuelta a la página anterior. En Express 4, los métodos `res.redirect('back')` y `res.location('back')` fueron obsoletos.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(cuerpo, estado)
+
+Express 5 ya no soporta la firma `res.send(obj, status)`. En su lugar, establece el estado y luego lo encadena al método `res.send()` de esta manera: `res.status(status).send(obj)`.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-end
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status)
+
+Express 5 ya no soporta la firma `res.send(status)`, donde `status` es un número. En su lugar, use el `res. función endStatus(statusCode)`, que establece el código de estado de la cabecera de respuesta HTTP y envía la versión de texto del código: "No encontrado", "Error interno del servidor", y así sucesivamente.
+Si necesita enviar un número usando el `res. función end()`, cita el número para convertirlo en una cadena, para que Express no lo interprete como un intento de usar la antigua firma no soportada.
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-end
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+La función `res.sendfile()` ha sido reemplazada por una versión `res.sendFile()` con casilla de camellos en Express 5.
+
+**Nota:** En Express 5, `res. endFile()` utiliza el paquete `mime-types` para la detección de tipos MIME, que devuelve diferentes valores de Tipo de Contenido que Express 4 para varios tipos de archivo comunes:
+
+- Archivos JavaScript (.js): ahora "text/javascript" en lugar de "application/javascript"
+- Archivos JSON (.json): ahora "application/json" en lugar de "text/json"
+- Archivos CSS (.css): ahora "text/css" en lugar de "text/plain"
+- Archivos XML (.xml): ahora "application/xml" en lugar de "text/xml"
+- Archivos de fuente (.woff): ahora "font/woff" en lugar de "application/font-woff"
+- Archivos SVG (.svg): ahora "image/svg+xml" en lugar de "application/svg+xml"
+
+<Alert type="info">
+Puedes reemplazar las firmas obsoletas con el siguiente comando:
+
+```plaintext
+codemod@latest @expressjs/camelcase-sendfile npx
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+La firma `router.param(fn)` fue usada para modificar el comportamiento de la función `router.param(name, fn)`. Ha sido obsoleto desde v4.11.0, y Express 5 ya no lo soporta en absoluto.
+
+### express.static.mime
+
+En Express 5, `mime` ya no es una propiedad exportada del campo `static`.
+Usa el [`mime-types` paquete](https://github.com/jshttp/mime-types) para trabajar con valores de tipo MIME.
+
+**Importante:** Este cambio afecta no sólo al uso directo de `express.static.mime` sino también a otros métodos Express que dependen de la detección de tipo MIME, como `res.sendFile()`. Los siguientes tipos MIME han cambiado de Express 4:
+
+- Archivos JavaScript (.js): ahora servido como "text/javascript" en lugar de "application/javascript"
+- Archivos JSON (.json): ahora servido como "application/json" en lugar de "text/json"
+- Archivos CSS (.css): ahora servido como "text/css" en lugar de "text/plain"
+- Archivos HTML (): ahora servido como "text/html; charset=utf-8" en lugar de sólo "text/html"
+- Archivos XML (.xml): ahora servido como "application/xml" en lugar de "text/xml"
+- Archivos de fuente (.woff): ahora servido como "font/woff" en lugar de "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:router debug logs
+
+En Express 5, la lógica de manejo del router es realizada por una dependencia. Por lo tanto, los registros de depuración
+para el enrutador ya no están disponibles bajo el espacio de nombres `express:`.
+En v4, los registros estaban disponibles bajo los espacios de nombres `express:router`, `express:router:layer`,
+y `express:router`. Todos estos fueron incluidos bajo el espacio de nombres `express:*`.
+En v5.1+, los registros están disponibles bajo los espacios de nombres `router`, `router:layer`, y `router:route`.
+Los registros de `router:layer` y `router:route` están incluidos en el namespace `router:*`.
+Para lograr el mismo detalle del registro de depuración al usar `express:*` en v4, usa una conjunción de
+`express:*`, `router`, y `router:*`.
+
+```sh
+
+DEBUG=expresar:* node index.js
+
+
+DEBUG=expresar:*,router,router:* node index.js
+```
+
+## Cambiado
+
+### Ruta de ruta que coincide con sintaxis
+
+Ruta de ruta que coincide con la sintaxis es cuando se proporciona una cadena como el primer parámetro a las APIs `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, y `router.use()`. Se han realizado los siguientes cambios en cómo la cadena de ruta se corresponde con una solicitud entrante:
+
+- El comodín `*` debe tener un nombre, coincidiendo con el comportamiento de los parámetros `:`, use `/*splat` en lugar de `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="info">
+`*splat` coincide con cualquier ruta sin la ruta raíz. Si necesita coincidir con la ruta de la raíz también `/`, puede usar `/{*splat}`, envolviendo el comodín entre llaves.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- El carácter opcional `?` ya no es compatible, utilice llaves en su lugar.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Los caracteres de expresión regular no son compatibles. Por ejemplo:
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+debe cambiarse a:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Algunos caracteres han sido reservados para evitar confusión durante la actualización (`()[]?+!`), use `\` para escapar de ellos.
+- Los nombres de parámetros ahora soportan identificadores JavaScript válidos, o citan como `:"this"`.
+
+### Las promesas rechazadas manejadas por middleware y manejadores
+
+Solicitar middleware y manejadores que devuelven promesas rechazadas ahora son manejados reenviando el valor rechazado como un `Error` al middleware que maneja errores. Esto significa que usar 'async' funciones como middleware y manejadores son más fáciles que nunca. Cuando se arroja un error en una función `async` o una promesa rechazada es `await`ed dentro de una función asíncrona, esos errores se pasarán al gestor de errores como si llamara a `next(err)`.
+
+Detalles de cómo Express maneja los errores se cubren en la [documentación de manejo de errores](/en/guide/error-handling).
+
+### express.urlencoded
+
+El método `express.urlencoded` hace que la opción `extended` sea `false` por defecto.
+
+### express.static dotfiles
+
+En Express 5, la opción `dotfiles` de `express.static` ahora es `ignore"`. Este es un cambio de Express 4, donde los ficheros de puntos fueron servidos por defecto. Como resultado, archivos dentro de un directorio que comienza con un punto (`.`), como `. ell-known`, ya no será accesible y devolverá un error **404 No encontrado**. Esto puede romper la funcionalidad que depende de servir directorios de puntos, como Android App Links y Apple Universal Links.
+
+Ejemplo de código de ruptura:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Después de migrar a Express 5, una solicitud a `/.well-known/assetlinks.json` resultará en un **404 No Encontrado**.
+
+Para arreglar esto, sirve directorios de puntos específicos explícitamente usando \`dotfiles: opción "allow"":
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+Este enfoque le permite servir de forma segura sólo los directorios de puntos deseados mientras mantiene el comportamiento seguro por defecto para otros archivos de puntos, que permanecen inaccesibles.
+
+### app.listen
+
+En Express 5, el método `app.listen` invocará la función callback proporcionada por el usuario (si se proporciona) cuando el servidor reciba un evento de error. En Express 4, esos errores se lanzarían. This change shifts error handling responsibility to the callback function in Express 5. Si hay un error, se pasará al callback como argumento.
+Por ejemplo:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Escuchando en ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+El objeto `app.router`, que fue eliminado en Express 4, ha regresado en Express 5. En la nueva versión, este objeto es sólo una referencia al router base Express, a diferencia de en Express 3, donde una aplicación tuvo que cargarla explícitamente.
+
+### req.body
+
+La propiedad `req.body` devuelve `undefined` cuando el cuerpo no ha sido analizado. En Express 4, devuelve `{}` por defecto.
+
+### req.host
+
+En Express 4, la función `req.host` borró incorrectamente del número de puerto si estaba presente. En Express 5, el número de puerto se mantiene.
+
+### req.params
+
+El objeto `req.params` ahora tiene un **prototipo nulo** al usar rutas de cadenas. Sin embargo, si la ruta se define con una expresión regular, `req.params` sigue siendo un objeto estándar con un prototipo normal. Además, hay dos cambios de comportamiento importantes:
+
+**Los parámetros comodín ahora son arrays:**
+
+Los comodines (por ejemplo, `/*splat`) capturan segmentos de ruta como una matriz en lugar de una sola cadena.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.arams);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Parámetros no coincidentes son omitidos:**
+
+En Express 4, los comodines no coinciden eran cadenas vacías (`''`) y los parámetros opcionales `:` (usando `?`) tenían una clave con valor `undefined`. En Express 5, los parámetros no coincidentes se omiten completamente de `req.params`.
+
+```js
+// v4: unmatched wildcard is empty string
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.arams);
+  // => { '0': '' }
+});
+
+// v4: unmatched optional param is undefined
+app.et('/:file.:ext?', (req, res) => {
+  // GET /image
+  console.ir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{. ext}', (req, res) => {
+  // GET /image
+  console.dir(req.arams);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.query
+
+La propiedad `req.query` ya no es una propiedad escribible y en su lugar es un getter. El analizador de consultas por defecto ha sido cambiado de "extendido" a "simple".
+
+### res.clearCookie
+
+El método `res.clearCookie` ignora las opciones `maxAge` y `expires` proporcionadas por el usuario.
+
+### res.estado
+
+El método `res.status` sólo acepta enteros en el rango de `100` a `999`, siguiendo el comportamiento definido por Node. , y devuelve un error cuando el código de estado no es un entero.
+
+### res.variar
+
+El `res.vary` arroja un error cuando falta el argumento `field`. En Express 4, si el argumento fue omitido, dio una advertencia en la consola
+
+## Mejoras
+
+### res.render()
+
+Este método ahora fuerza el comportamiento asíncrono para todos los motores de vista, evitando errores causados por motores de vista que tenían una implementación sincrónica y que violaban la interfaz recomendada.
+
+### Soporte de codificación Brotli
+
+Express 5 soporta la codificación de Brotli para peticiones recibidas de clientes que lo soportan.
diff --git a/src/content/pages/es/resources/glossary.mdx b/src/content/pages/es/resources/glossary.mdx
new file mode 100644
index 0000000000..59f1021c1b
--- /dev/null
+++ b/src/content/pages/es/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Un glosario completo de términos relacionados con Express.js, Node.js, middleware, rutaje y otros conceptos clave para ayudarle a entender y usar Express efectivamente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### aplicación
+
+En general, uno o más programas diseñados para llevar a cabo operaciones con un propósito específico. En el contexto de Express, un programa que utiliza la API Express corriendo en la plataforma Node.js. También podría referirse a un [objeto de aplicación](/en/api#express).
+
+### API
+
+Interfaz de programación de aplicaciones. Escribe la abreviatura cuando se utiliza por primera vez.
+
+### Exprés
+
+Un marco web rápido, sin opinión y minimalista para aplicaciones Node.js. En general, se prefiere "Express" a "Express.js", aunque esta última es aceptable.
+
+### libuv
+
+Una biblioteca de soporte multiplataforma que se centra en E/S asíncrona, desarrollada principalmente para su uso por Node.js.
+
+### middleware
+
+Una función que es invocada por la capa de enrutamiento Express antes del gestor de solicitud final, y por lo tanto se encuentra en el medio entre una solicitud cruda y la ruta final deseada. Unos pocos puntos finos de terminología en torno a middleware:
+
+- `var foo = require('middleware')` es llamado _requiring_ o _using_ un módulo Node.js. Luego la instrucción `var mw = foo()` típicamente devuelve el middleware.
+- `app.use(mw)` se llama _agregando el middleware a la pila global de procesamiento de datos_.
+- `app.get('/foo', mw, function (req, res) { ... })` se llama _adding the middleware to the "GET /foo" processing stack_.
+
+### Node.js
+
+Una plataforma de software que se utiliza para construir aplicaciones de red escalables. Node.js utiliza JavaScript como su lenguaje de scripting y logra un alto rendimiento a través de E/S sin bloqueo y un bucle de eventos con un solo hilo. Ver [nodejs.org](https://nodejs.org/en/). **Nota de uso**: Inicialmente, "Node.js", a partir de entonces "Node".
+
+### código abierto, código abierto
+
+Cuando se utiliza como adjetivo, guión; por ejemplo: "Esto es software de código abierto". Ver [Software de código abierto en Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Aunque es común no guiar este término, estamos utilizando las reglas estándar de Inglés para
+gueando un adjetivo compuesto.
+
+</Alert>
+
+### solicitud
+
+Una petición HTTP. Un cliente envía un mensaje de petición HTTP a un servidor, el cual devuelve una respuesta. La solicitud debe utilizar uno de varios [métodos de petición](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) como GET, POST, y así sucesivamente.
+
+### respuesta
+
+Una respuesta HTTP. Un servidor devuelve un mensaje de respuesta HTTP al cliente. La respuesta contiene información sobre el estado de finalización de la solicitud y también podría contener el contenido solicitado en su cuerpo del mensaje.
+
+### ruta
+
+Parte de una URL que identifica un recurso. Por ejemplo, en `http://foo.com/products/id`, "/products/id" es la ruta.
+
+### enrutador
+
+Ver [router](/en/api#router) en la referencia API.
diff --git a/src/content/pages/es/resources/utils.md b/src/content/pages/es/resources/utils.md
new file mode 100644
index 0000000000..c3fb043917
--- /dev/null
+++ b/src/content/pages/es/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: utilidades exprés
+description: Descubra los módulos de utilidad relacionados con Express.js y Node.js, incluyendo herramientas para cookies, protección CSRF, análisis de URL, enrutamiento, y más para mejorar sus aplicaciones.
+---
+
+## Funciones de utilidad Express
+
+La organización [pillarjs](https://github.com/pillarjs) de GitHub contiene varios módulos
+para funciones de utilidad que pueden ser generalmente útiles.
+
+| Módulos de utilidad                                            | Descripción                                                                                                                                                                    |
+| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [cookies](https://www.npmjs.com/package/cookies)               | Obtener y configurar cookies HTTP(S) que se pueden firmar para evitar manipulaciones, usando Keygrip. Se puede usar con la librería HTTP de Node.js o como middleware Express. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contiene la lógica detrás de la creación y verificación de token CSRF. Utilice este módulo para crear un middleware CSRF personalizado.                                        |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Función para invocar como paso final para responder a la petición HTTP.                                                                                                        |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Analizar una URL con caché.                                                                                                                                                    |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Convierte una cadena de ruta tipo Express-style como \`\`/user/:name\` en una expresión regular.                                                                               |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resuelve una ruta relativa contra una ruta raíz con validación.                                                                                                                |
+| [router](https://www.npmjs.com/package/router)                 | Enrutador simple de tipo middleware.                                                                                                                                           |
+| [send](https://www.npmjs.com/package/send)                     | Biblioteca para streaming de archivos como respuesta HTTP, con soporte para respuestas parciales (rangos), negociación condicional-GET y eventos granulares.                   |
+
+Para módulos adicionales relacionados con HTTP, consulte [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/es/support.md b/src/content/pages/es/support.md
new file mode 100644
index 0000000000..22d7eef706
--- /dev/null
+++ b/src/content/pages/es/support.md
@@ -0,0 +1,23 @@
+---
+title: Soporte para versiones
+description: Encuentre información sobre el programa de soporte para diferentes versiones de Express.js, incluyendo las versiones que se mantienen actualmente y las políticas de fin de su vida.
+---
+
+Sólo se admite la última versión de cualquier línea de lanzamiento mayor.
+
+Las versiones que son EOL (end-of-life) _pueden_ recibir actualizaciones para vulnerabilidades de seguridad críticas, pero el equipo de Express no ofrece ninguna garantía y no planea abordar o corregir versiones para ningún problema encontrado.
+
+| Versión principal      | Versión mínima de Node.js | Inicio de Soporte  | Fecha de fin de soporte |
+| ---------------------- | ------------------------- | ------------------ | ----------------------- |
+| [**v5.x**](/en/5x/api) | 18                        | Septiembre de 2024 | **en curso**            |
+| [**v4.x**](/en/4x/api) | 0.10.0                    | Abril de 2014      | **en curso**            |
+| [**v3.x**](/en/3x/api) | 0.8.0                     | Octubre de 2012    | Julio de 2015           |
+| [**v2.x**](/2x/)       | 0.4.1                     | Marzo de 2011      | Julio de 2012           |
+| **v1.x**               | 0.2.0                     | Diciembre 2010     | Marzo de 2011           |
+| **v0.14.x**            | 0.1.98                    | Diciembre 2010     | Diciembre 2010          |
+
+## Opciones de soporte comercial
+
+Si no puede actualizar a una versión soportada de Express, póngase en contacto con uno de nuestros socios para recibir actualizaciones de seguridad:
+
+- [Soporte de HeroDevs finalizado](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/fr/advanced/best-practice-performance.md b/src/content/pages/fr/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..70525e8e1f
--- /dev/null
+++ b/src/content/pages/fr/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Meilleures pratiques de production : performance et fiabilité'
+description: Découvrez les meilleures pratiques de performance et de fiabilité pour les applications Express en production, couvrant les optimisations de code et les configurations d'environnement pour des performances optimales.
+---
+
+Cet article traite des meilleures pratiques de performance et de fiabilité pour les applications Express déployées en production.
+
+Ce sujet tombe clairement dans le monde des « dévalises », englobant tant le développement traditionnel que les opérations. En conséquence, l'information est divisée en deux parties :
+
+- Les choses à faire dans votre code (la partie développeur) :
+  - [Utiliser la compression gzip](#use-gzip-compression)
+  - [Ne pas utiliser de fonctions synchrones](#dont-use-synchronous-functions)
+  - [Faire la journalisation correctement](#do-logging-correctly)
+  - [Gérer les exceptions correctement] (#handle-exceptions-properly)
+- Choses à faire dans votre environnement / configuration (partie Ops) :
+  - [Définir NODE_ENV comme "production"](#set-node_env-to-production)
+  - (#ensure-your-app-automatically-restarts)
+  - [Exécuter votre application dans un cluster](#run-your-app-in-a-cluster)
+  - (#cache-request-results)
+  - [Utiliser un répartiteur de charge](#use-a-load-balancer)
+  - [Utiliser un proxy inverse](#use-a-reverse-proxy)
+
+## Les choses à faire dans votre code
+
+Voici quelques choses que vous pouvez faire dans votre code pour améliorer les performances de votre application :
+
+- [Utiliser la compression gzip](#use-gzip-compression)
+- [Ne pas utiliser de fonctions synchrones](#dont-use-synchronous-functions)
+- [Faire la journalisation correctement](#do-logging-correctly)
+- [Gérer les exceptions correctement] (#handle-exceptions-properly)
+
+### Utiliser la compression gzip
+
+La compression Gzip peut réduire considérablement la taille du corps de réponse et ainsi augmenter la vitesse d'une application web. Utilisez le middleware [compression](https://www.npmjs.com/package/compression) pour la compression gzip dans votre application Express. Par exemple :
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+Pour un site internet à fort trafic en production, la meilleure façon de mettre en place une compression est de l'implémenter à un niveau de proxy inverse (voir [Utiliser un proxy inverse](#use-a-reverse-proxy)). Dans ce cas, vous n'avez pas besoin d'utiliser le middleware de compression. Pour plus de détails sur l'activation de la compression gzip dans Nginx, voir [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) dans la documentation Nginx.
+
+### Ne pas utiliser les fonctions synchrones
+
+Les fonctions et méthodes synchrones lient le processus d'exécution jusqu'à ce qu'elles soient retournées. Un seul appel à une fonction synchrone peut retourner en quelques microsecondes ou millisecondes, Cependant, dans les sites Web à fort trafic, ces appels s'ajoutent et réduisent les performances de l'application. Évitez leur utilisation en production.
+
+Bien que Node et de nombreux modules fournissent des versions synchrones et asynchrones de leurs fonctions, utilisez toujours la version asynchrone en production. Le seul moment où une fonction synchrone peut être justifiée est au démarrage initial.
+
+Vous pouvez utiliser le flag en ligne de commande `--trace-sync-io` pour afficher une alerte et une trace de pile chaque fois que votre application utilise une API synchrone. Bien sûr, vous ne voudriez pas utiliser cela en production, mais plutôt vous assurer que votre code est prêt pour la production. Voir la [documentation des options de la ligne de commande node](https://nodejs.org/api/cli#cli_trace_sync_io) pour plus d'informations.
+
+### Faire la journalisation correctement
+
+En général, il y a deux raisons de se connecter depuis votre application : pour le débogage et pour l'activité des applications de journalisation (essentiellement tout le reste). Utiliser `console.log()` ou `console.error()` pour imprimer les messages de log vers le terminal est pratique courante dans le développement. Mais [ces fonctions sont synchronisées] (https://nodejs.org/api/console#console) lorsque la destination est un terminal ou un fichier, elles ne sont donc pas adaptées à la production, à moins que vous ne conduisiez la sortie vers un autre programme.
+
+#### Pour le débogage
+
+Si vous êtes connecté à des fins de débogage, alors au lieu d'utiliser `console.log()`, utilisez un module de débogage spécial comme [debug](https://www.npmjs.com/package/debug). Ce module vous permet d'utiliser la variable d'environnement DEBUG pour contrôler quels messages de débogage sont envoyés à `console.error()`, le cas échéant. Pour garder votre application purement asynchrone, vous vouliez toujours canaliser `console.error()` vers un autre programme. Mais alors, vous n'allez pas vraiment déboguer en production, n'est-ce pas?
+
+#### Pour l'activité de l'application
+
+Si vous connectez l'activité de l'application (par exemple, suivre le trafic ou les appels API), au lieu d'utiliser la « console ». og()\`, utilise une bibliothèque de log comme [Pino](https://www.npmjs.com/package/pino), qui est l'option la plus rapide et la plus efficace disponible.
+
+### Gérer correctement les exceptions
+
+Les applications de nœud plantent lorsqu'elles rencontrent une exception non prise. Ne pas gérer les exceptions et prendre les actions appropriées fera planter votre application Express et se déconnectera. Si vous suivez les conseils de [Assurez-vous que votre application redémarre automatiquement] (#ensure-your-app-automatically-restarts) ci-dessous, votre application se remettra d'un crash. Heureusement, les applications Express ont généralement un temps de démarrage court. Néanmoins, vous voulez éviter de planter en premier lieu, et pour ce faire, vous devez gérer les exceptions correctement.
+
+Pour vous assurer de gérer toutes les exceptions, utilisez les techniques suivantes :
+
+- [Utiliser try-catch](#use-try-catch)
+- [Utiliser des promesses](#use-promises)
+
+Avant de plonger dans ces sujets, vous devriez avoir une compréhension de base de la gestion des erreurs Node/Express : utiliser les premiers callbacks d'erreurs et propager les erreurs dans les middleware. Le noeud utilise une convention "error-first callback" pour retourner des erreurs à partir de fonctions asynchrones, où le premier paramètre de la fonction callback est l'objet erreur, suivi par les données de résultat dans les paramètres successifs. Pour indiquer aucune erreur, passez null comme premier paramètre. La fonction callback doit suivre la première convention de callback pour gérer l'erreur de manière significative. Et dans Express, la meilleure pratique est d'utiliser la fonction next() pour propager les erreurs à travers la chaîne du middleware.
+
+Pour en savoir plus sur les fondamentaux de la gestion des erreurs, voir :
+
+- [Gestion des erreurs dans Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Utiliser try-catch
+
+Try-catch est un langage JavaScript que vous pouvez utiliser pour attraper des exceptions dans le code synchrone. Utilisez try-catch, par exemple, pour gérer les erreurs d'analyse JSON comme indiqué ci-dessous.
+
+Voici un exemple d'utilisation de try-catch pour gérer une éventuelle exception plantant le processus.
+Cette fonction du middleware accepte un paramètre de champ de requête nommé "params" qui est un objet JSON.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+Cependant, essayer-catch ne fonctionne que pour du code synchrone. Parce que la plate-forme Node est principalement asynchrone (particulièrement dans un environnement de production), les captures d'essai ne prendront pas beaucoup d'exceptions.
+
+#### Utiliser les promesses
+
+Lorsqu'une erreur est levée dans une fonction `async` ou qu'une promesse rejetée est attendue à l'intérieur d'une fonction `async`, ces erreurs seront passées au gestionnaire d'erreurs comme si elle appelait `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+De plus, vous pouvez utiliser des fonctions asynchrones pour votre middleware, et le routeur gérera des erreurs si la promesse échoue, par exemple :
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+La meilleure pratique est de gérer les erreurs le plus près possible du site. Donc, tant que ceci est maintenant géré dans le routeur, Il est préférable d’attraper l’erreur dans le middleware et de la manipuler sans s’appuyer sur un middleware séparé.
+
+#### Ce qu'il ne faut pas faire
+
+Une chose que vous ne devriez pas _faire_ est d'écouter l'évènement `uncatghtException` émise lorsqu'une exception bulle tout le retour à la boucle d'événement. Ajouter un event listener pour `uncatghtException` changera le comportement par défaut du processus qui rencontre une exception ; le processus continuera à fonctionner malgré l'exception. Cela peut sembler un bon moyen d'empêcher votre application de planter, mais continuer à exécuter l'application après une exception non capturée est une pratique dangereuse et n'est pas recommandé, parce que l'état du processus devient peu fiable et imprévisible.
+
+De plus, l'utilisation de `uncaughtException` est officiellement reconnue comme [crude](https://nodejs.org/api/process#process_event_uncaughtexception). Donc l'écoute de `uncatghtException` est juste une mauvaise idée. C'est pourquoi nous recommandons des choses comme des processus multiples et des superviseurs : plantage et redémarrage est souvent le moyen le plus fiable de se remettre d'une erreur.
+
+Nous ne recommandons pas non plus d'utiliser [domains](https://nodejs.org/api/domain). Il ne résout généralement pas le problème et est un module obsolète.
+
+## Choses à faire dans votre environnement / configuration
+
+Voici quelques choses que vous pouvez faire dans votre environnement système pour améliorer les performances de votre application :
+
+- [Définir NODE_ENV comme "production"](#set-node_env-to-production)
+- (#ensure-your-app-automatically-restarts)
+- [Exécuter votre application dans un cluster](#run-your-app-in-a-cluster)
+- (#cache-request-results)
+- [Utiliser un répartiteur de charge](#use-a-load-balancer)
+- [Utiliser un proxy inverse](#use-a-reverse-proxy)
+
+### Définir NODE_ENV à "production"
+
+La variable d'environnement NODE_ENV spécifie l'environnement dans lequel une application est en cours d'exécution (généralement, développement ou production). L'une des choses les plus simples que vous pouvez faire pour améliorer les performances est de définir NODE_ENV à `production`.
+
+Définir NODE_ENV sur "production" rend Express:
+
+- Modèles d'affichage du cache.
+- Cache les fichiers CSS générés à partir des extensions CSS.
+- Générer des messages d'erreur moins verbeux.
+
+[Les tests indiquent](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) que cela peut améliorer les performances de l'application par un facteur de trois !
+
+Si vous avez besoin d'écrire du code spécifique à l'environnement, vous pouvez vérifier la valeur de NODE_ENV avec `process.env.NODE_ENV`. Sachez que la vérification de la valeur d'une variable d'environnement entraîne une pénalité de performance, et qu'elle devrait donc être faite avec modération.
+
+En développement, vous définissez généralement des variables d'environnement dans votre shell interactif, par exemple en utilisant `export` ou votre fichier `.bash_profile`. Mais en général, vous ne devriez pas le faire sur un serveur de production ; au lieu de cela, utilisez le système d'initialisation de votre système d'exploitation (système). La section suivante fournit plus de détails sur l'utilisation de votre système d'initialisation en général, mais le paramètre `NODE_ENV` est si important pour les performances (et facile à faire), qu'il est mis en évidence ici.
+
+Avec le système, utilisez la directive `Environnement` dans votre fichier unitaire. Par exemple :
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+Pour plus d'informations, voir [Utilisation des variables d'environnement dans les unités systémiques](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Assurez-vous que votre application redémarre automatiquement
+
+En production, vous ne voulez pas que votre application soit déconnectée, jamais. Cela signifie que vous devez vous assurer qu'il redémarre à la fois si l'application plante et si le serveur lui-même plante. Bien que vous espériez qu'aucun de ces événements ne se produise, réalistement, vous devez rendre compte des deux éventualités par:
+
+- Utiliser un gestionnaire de processus pour redémarrer l'application (et Node) quand il plante.
+- Utiliser le système d'initialisation fourni par votre système d'exploitation pour redémarrer le gestionnaire de processus lorsque le système d'exploitation plante. Il est également possible d'utiliser le système d'initialisation sans gestionnaire de processus.
+
+Les applications de nœud plantent si elles rencontrent une exception non prise. La première chose à faire est de s'assurer que votre application est bien testée et gère toutes les exceptions (voir [gérer les exceptions correctement](#handle-exceptions-properly) pour plus de détails). Mais en tant que sécurité pour les échecs, mettez en place un mécanisme pour vous assurer que si et quand votre application se bloque, elle redémarrera automatiquement.
+
+#### Utiliser un gestionnaire de processus
+
+En cours de développement, vous avez démarré votre application simplement à partir de la ligne de commande avec `node server.js` ou quelque chose de similaire. Mais faire cela dans la production est une recette de désastre. Si l'application plante, elle sera hors ligne jusqu'à ce que vous la redémarrez. Pour s'assurer que votre application redémarre si elle plante, utilisez un gestionnaire de processus. Un gestionnaire de processus est un "conteneur" pour les applications qui facilitent le déploiement, fournissent une disponibilité élevée et vous permettent de gérer l'application à l'exécution.
+
+En plus de redémarrer votre application en cas de plantage, un gestionnaire de processus peut vous permettre de :
+
+- Obtenez un aperçu de la performance de l’exécution et de la consommation des ressources.
+- Modifiez les paramètres de façon dynamique pour améliorer les performances.
+- Contrôle de la grappe (pm2).
+
+Historiquement, il était populaire d'utiliser un gestionnaire de processus Node.js comme [PM2](https://github.com/Unitech/pm2). Consultez leur documentation si vous le souhaitez. Cependant, nous vous recommandons d'utiliser votre système d'initialisation pour la gestion des processus.
+
+#### Utiliser un système d'initialisation
+
+La prochaine étape de la fiabilité est de s'assurer que votre application redémarre lorsque le serveur redémarre. Les systèmes peuvent encore diminuer pour diverses raisons. Pour vous assurer que votre application redémarre si le serveur plante, utilisez le système d'initialisation intégré à votre système d'exploitation. Le système d'initialisation principal utilisé aujourd'hui est [systemd](https://wiki.debian.org/systemd).
+
+Il y a deux façons d'utiliser les systèmes d'initialisation avec votre application Express :
+
+- Exécutez votre application dans un gestionnaire de processus et installez le gestionnaire de processus en tant que service avec le système d'initialisation. Le gestionnaire de processus redémarrera votre application lorsque l'application se bloque, et le système d'initialisation redémarrera le gestionnaire de processus lorsque le système d'exploitation redémarrera. C'est l'approche recommandée.
+- Exécutez votre application (et Node) directement avec le système d'initialisation. C'est un peu plus simple, mais vous n'aurez pas les avantages supplémentaires d'utiliser un gestionnaire de processus.
+
+##### Systemd
+
+Systemd est un gestionnaire de systèmes et de services Linux. La plupart des grandes distributions Linux ont adopté le système comme système d'initialisation par défaut.
+
+Un fichier de configuration du service système est appelé un fichier \_unit avec un nom de fichier se terminant par `.service`. Voici un exemple de fichier d'unité pour gérer une application Node directement. Remplacez les valeurs placées en `<angle brackets>` pour votre système et votre application:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Pour plus d'informations sur le système, voir [systemd reference (man page)] (http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Exécutez votre application dans un cluster
+
+Dans un système multi-cœurs, vous pouvez augmenter les performances d'une application Node de plusieurs fois en lançant un cluster de processus. Un cluster exécute plusieurs instances de l'application, idéalement une instance sur chaque noyau de processeur, distribuant ainsi la charge et les tâches entre les instances.
+
+![Balancing between application instances using the cluster API](/images/clustering.png)
+
+IMPORTANT: Puisque les instances de l'application s'exécutent sous forme de processus séparés, elles ne partagent pas le même espace mémoire. C'est-à-dire que les objets sont locaux à chaque instance de l'application. Par conséquent, vous ne pouvez pas maintenir l'état dans le code de l'application. Cependant, vous pouvez utiliser un datastore en mémoire comme [Redis](http://redis.io/) pour stocker des données et des états liés à la session. Cette mise en garde s'applique essentiellement à toutes les formes de mise à l'échelle horizontale, qu'il s'agisse de regroupement avec de multiples processus ou de multiples serveurs physiques.
+
+Dans les applications groupées, les processus de travail peuvent planter individuellement sans affecter le reste des processus. Mis à part les avantages des performances, l'isolement des défaillances est une autre raison de lancer un cluster de processus applicatifs. À chaque fois qu'un processus worker plante, assurez-vous toujours de consigner l'événement et de faire apparaître un nouveau processus en utilisant la fonction cluster.fork().
+
+#### Utilisation du module de cluster de Node
+
+Le groupement est rendu possible avec le [module de clustage] (https://nodejs.org/api/cluster). Cela permet à un processus maître de faire apparaître des processus de travail et de distribuer des connexions entrantes entre les travailleurs.
+
+#### Utilisation du PM2
+
+Si vous déployez votre application avec PM2, alors vous pouvez profiter de la grappe de serveurs _sans_ pour modifier le code de votre application. Vous devez d'abord vous assurer que votre [application est sans états] (https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) signifiant qu'aucune donnée locale n'est stockée dans le processus (comme les sessions, les connexions websocket et les autres).
+
+Lorsque vous exécutez une application avec PM2, vous pouvez activer le **mode de cluster** pour l'exécuter dans une grappe avec un certain nombre d'instances de votre choix, comme le nombre de processeurs disponibles sur la machine. Vous pouvez modifier manuellement le nombre de processus dans le cluster en utilisant l'outil en ligne de commande `pm2` sans arrêter l'application.
+
+Pour activer le mode cluster, lancez votre application comme suit:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+Ceci peut également être configuré dans un fichier de processus PM2 (`ecosystem.config. s` ou similaire) en définissant `exec_mode` à `cluster` et `instances` au nombre de travaux à commencer.
+
+Une fois exécutée, l'application peut être mise à l'échelle comme ceci:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+Pour plus d'informations sur la grappe de serveurs avec PM2, voir [Mode clusters](https://pm2.keymetrics.io/docs/usage/cluster-mode/) dans la documentation PM2.
+
+### Résultats de la requête de cache
+
+Une autre stratégie pour améliorer les performances en production est de mettre en cache le résultat des requêtes, afin que votre application ne répète pas l'opération pour répondre à la même requête de manière répétée.
+
+Utilisez un serveur de cache comme [Varnish](https://www.varnish-cache.org/) ou [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (voir aussi [Nginx Caching](https://serversforhackers.com/nginx-caching/)) pour améliorer considérablement la vitesse et les performances de votre application.
+
+### Utiliser un répartiteur de charge
+
+Quelle que soit l'optimisation d'une application, une seule instance ne peut gérer qu'une quantité limitée de charge et de trafic. Une façon de mettre à l'échelle une application est d'exécuter plusieurs instances et de distribuer le trafic via un répartiteur de charge. La mise en place d'un répartiteur de charge peut améliorer les performances et la vitesse de votre application et l'activer pour augmenter la taille de votre système par une seule instance.
+
+Un répartiteur de charge est généralement un mandataire inversé qui orchestre le trafic entre et à partir de plusieurs instances et serveurs d'applications. Vous pouvez facilement configurer un répartiteur de charge pour votre application en utilisant [Nginx](https://nginx.org/en/docs/http/load_balancing) ou [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+Avec l'équilibrage de charge, vous devrez peut-être vous assurer que les requêtes qui sont associées à un ID de session particulier se connectent au processus qui les a originés. C'est connu sous le nom _affinity_, ou _sticky sessions_, et peut être adressé par la suggestion ci-dessus d'utiliser un stockage de données tel que Redis pour les données de session (selon votre application). Pour une discussion, voir [Utilisation de plusieurs nœuds](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Utiliser un proxy inversé
+
+Un mandataire inversé se trouve devant une application Web et effectue des opérations de support sur les requêtes, en plus de diriger les requêtes vers l'application. Il peut gérer les pages d'erreurs, la compression, la mise en cache, le service de fichiers et l'équilibrage de charge, entre autres.
+
+Le transfert de tâches qui ne nécessitent pas de connaissance de l'état de l'application à un mandataire inversé libère Express pour effectuer des tâches d'application spécialisées. Pour cette raison, il est recommandé d'exécuter Express derrière un proxy inverse comme [Nginx](https://www.nginx.org/) ou [HAProxy](https://www.haproxy.org/) en production.
diff --git a/src/content/pages/fr/advanced/best-practice-security.mdx b/src/content/pages/fr/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..2638d8e2d4
--- /dev/null
+++ b/src/content/pages/fr/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Meilleures pratiques de production : Sécurité'
+description: Découvrez les meilleures pratiques de sécurité cruciales pour les applications Express en production, y compris l'utilisation de TLS, la validation des entrées, les cookies sécurisés et la prévention des vulnérabilités.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Le terme _"production"_ désigne l'étape du cycle de vie du logiciel quand une application ou une API est généralement disponible pour ses utilisateurs finaux ou ses consommateurs. Par contre, dans l'étape _"développement"_, vous êtes toujours en train d'écrire et de tester du code, et l'application n'est pas ouverte à un accès externe. Les environnements système correspondants sont respectivement les environnements _production_ et _development_.
+
+Les environnements de développement et de production sont généralement mis en place différemment et ont des exigences très différentes. Ce qui est bon dans le développement peut ne pas être acceptable dans la production. Par exemple, dans un environnement de développement, vous pouvez vouloir une journalisation détaillée des erreurs pour le débogage, alors que le même comportement peut devenir une préoccupation de sécurité dans un environnement de production. Et en matière de développement, vous n'avez pas à vous soucier de l'évolutivité, de la fiabilité et de la performance, alors que ces préoccupations deviennent cruciales dans la production.
+
+<Alert type="Infos">
+
+Si vous pensez avoir découvert une faille de sécurité dans Express, veuillez consulter [Politiques et procédures de sécurité
+de sécurité [/en/resources/contributing#security-policies-and-procedures).
+
+</Alert>
+
+Les meilleures pratiques de sécurité pour les applications Express en production comprennent:
+
+- [Meilleures pratiques de production : Sécurité](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Ne pas utiliser de versions obsolètes ou vulnérables d'Express] (#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Utiliser TLS](#use-tls)
+  - [Ne pas faire confiance à la saisie de l'utilisateur](#do-not-trust-user-input)
+    - [Empêcher les redirections ouvertes](#prevent-open-redirects)
+  - [Utiliser le casque](#use-helmet)
+  - [Réduire l'empreinte digitale](#reduce-fingerprinting)
+  - (#use-cookies-securely)
+    - [Ne pas utiliser le nom du cookie de session par défaut](#dont-use-the-default-session-cookie-name)
+    - (#set-cookie-security-options)
+  - [Empêcher les attaques par force brute contre l'autorisation] (#prevent-brute-force-attacks-against-authorization)
+  - [Assurez-vous que vos dépendances sont sécurisées](#ensure-your-dependencies-are-secure)
+    - [Éviter les autres vulnérabilités connues] (#avoid-other-known-vulnerabilities)
+  - [Considérations supplémentaires](#additional-considerations)
+
+## Ne pas utiliser les versions obsolètes ou vulnérables de Express
+
+Express 2.x et 3.x ne sont plus maintenus. Les problèmes de sécurité et de performance dans ces versions ne seront pas résolus. Ne les utilisez pas ! Si vous n'avez pas déménagé vers la version 4, suivez le [guide de migration] (/en/guide/migrating-4) ou envisagez [Options de support commercial] (/en/support#commercial-support-options).
+
+Assurez-vous également que vous n'utilisez aucune des versions vulnérables Express listées sur la page [Mise à jour de sécurité] (/en/advanced/security-updates). Si vous l'êtes, mettez à jour vers l'une des versions stables, de préférence la plus récente.
+
+## Utiliser TLS
+
+Si votre application traite ou transmet des données sensibles, utilisez [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) pour sécuriser la connexion et les données. Cette technologie crypte les données avant qu'elles ne soient envoyées du client au serveur, empêchant ainsi certains hacks courants (et faciles). Bien que les requêtes Ajax et POST puissent ne pas être visiblement évidentes et semblent "cachées" dans les navigateurs, leur trafic réseau est vulnérable à [sniffing de paquets] (https://en.wikipedia.org/wiki/Packet_analyzer) et aux [attaques de l'homme au milieu] (https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+Il se peut que vous soyez familier avec le cryptage Secure Socket Layer (SSL) . [TLS est simplement la prochaine progression de SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). En d'autres termes, si vous utilisiez SSL auparavant, envisagez la mise à niveau vers TLS. En général, nous recommandons à Nginx de gérer les TLS. Pour une bonne référence pour configurer TLS sur Nginx (et d'autres serveurs), voir [Configurations de serveur recommandées (Mozilla Wiki)] (https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+De plus, un outil pratique pour obtenir un certificat TLS gratuit est [Let's Encrypt](https://letsencrypt.org/about/), un outil gratuit, automatisé, et l'autorité de certification ouverte (CA) fournie par le [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## Ne pas faire confiance à la saisie de l'utilisateur
+
+Pour les applications Web, l'une des exigences de sécurité les plus importantes est la validation et la gestion des entrées des utilisateurs. Cela se présente sous de nombreuses formes et nous ne les couvrirons pas tous.
+En fin de compte, la responsabilité de valider et de gérer correctement les types de saisie que votre application accepte est la vôtre.
+
+### Empêcher les redirections ouvertes
+
+Un exemple de saisie potentiellement dangereuse de l'utilisateur est une redirection \_ouverte, où une application accepte une URL comme entrée utilisateur (souvent dans la requête URL, par exemple `? rl=https://exemple. ) et utilise `res.redirect`pour définir l'en-tête`location\` et
+retourne un statut 3xx.
+
+Une application doit valider qu'elle prend en charge la redirection vers l'URL entrante pour éviter d'envoyer des utilisateurs à des liens malveillants tels que des sites Web d'hameçonnage, entre autres risques.
+
+Voici un exemple de vérification des URLs avant d'utiliser `res.redirect` ou `res.location`:
+
+```js
+app.use((req, res) => {
+  essayer {
+    if (new Url(req. uery.url).host !== 'exemple.com') {
+      return res.status(400). nd(`Redirection non prise en charge vers l'hôte : ${req.query.url}`);
+    }
+  } attraper (e) {
+    retourne. tatus(400).end(`URL invalide : ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Utiliser le Casque
+
+[Helmet][helmet] peut aider à protéger votre application contre certaines vulnérabilités Web bien connues en définissant correctement les en-têtes HTTP.
+
+Helmet est une fonction middleware qui définit les en-têtes de réponse HTTP liés à la sécurité. Le casque définit par défaut les en-têtes suivants :
+
+- `Content-Security-Policy` : Une puissante liste de ce qui peut se passer sur votre page qui atténue de nombreuses attaques
+- `Cross-Origin-Opener-Policy`: Aide à isoler votre page
+- `Cross-Origin-Resource-Policy`: empêche les autres de charger vos ressources cross-origin
+- `Origin-Agent-Cluster`: Modifie l'isolement du processus pour qu'il soit basé sur l'origine
+- `Referrer-Policy`: contrôle l'en-tête [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer)
+- `Strict-Transport-Security` : dit aux navigateurs de préférer HTTPS
+- `X-Content-Type-Options`: évite [sniffing MIME](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: contrôle le préchargement DNS
+- `X-Download-Options`: force les téléchargements à être sauvegardés (Internet Explorer uniquement)
+- `X-Frame-Options`: En-tête hérité qui atténue les attaques [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking)
+- `X-Permitted-Cross-Domain-Policies`: Contrôle le comportement inter-domaine pour les produits Adobe, comme Acrobat
+- `X-Powered-By`: Informations sur le serveur web. Supprimé parce qu'il peut être utilisé dans des attaques simples
+- `X-XSS-Protection`: L'en-tête hérité qui tente d'atténuer [les attaques XSS](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), mais rend les choses pires, alors le casque le désactive
+
+Chaque en-tête peut être configuré ou désactivé. Pour en savoir plus à ce sujet, veuillez vous rendre sur [son site de documentation][helmet].
+
+Installer le casque comme n'importe quel autre module :
+
+```bash
+$ npm install helmet
+```
+
+Ensuite, pour l'utiliser dans votre code:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Réduire la prise d'empreintes digitales
+
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Bien que ce ne soit pas un problème de sécurité en soi,
+réduisant la capacité d'empreinte digitale d'une application améliore sa position globale de sécurité.
+Le logiciel serveur peut être imprimé par des empreintes digitales dans la manière dont il répond à des requêtes spécifiques, par exemple dans
+les en-têtes de réponse HTTP.
+
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="Infos">
+
+Désactiver l'en-tête \`X-Powered-By n'empêche pas un attaquant sophistiqué de déterminer
+qu'une application exécute Express. Cela peut décourager une exploitation occasionnelle, mais il existe d'autres moyens pour
+de déterminer si une application exécute Express.
+
+</Alert>
+
+Express envoie également ses propres messages formatés "404 Not Found" et les messages d'erreur de formatteur
+de réponse. Celles-ci peuvent être modifiées par
+[ajouter votre propre gestionnaire non trouvé](/en/starter/faq#how-do-i-handle-404-responses)
+et
+[écrire votre propre gestionnaire d'erreur](/en/guide/error-handling#writing-error-handlers) :
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404). end("Désolé ne peut pas trouver cela!");
+});
+
+// application de gestion d'erreurs personnalisée
+. se(err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Quelque chose s'est cassé !');
+});
+```
+
+## Utiliser les cookies en toute sécurité
+
+Pour vous assurer que les cookies n'ouvrent pas votre application aux exploitations, n'utilisez pas le nom des cookies de session par défaut et définissez les options de sécurité des cookies de manière appropriée.
+
+Il y a deux principaux modules de session de cookies du middleware :
+
+- [express-session](https://www.npmjs.com/package/express-session) qui remplace le middleware `express.session` intégré à Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) qui remplace le middleware `express.cookieSession` intégré à Express 3.x.
+
+La principale différence entre ces deux modules est la façon dont ils enregistrent les données de session des cookies. Le middleware [express-session](https://www.npmjs.com/package/express-session) stocke les données de session sur le serveur ; il n'enregistre que l'ID de session dans le cookie lui-même, pas les données de session. Par défaut, il utilise du stockage en mémoire et n'est pas conçu pour un environnement de production. En production, vous devrez configurer un magasin de session évolutif ; voir la liste des [magasins de sessions compatibles] (https://github.com/expressjs/session#compatible-session-stores).
+
+En revanche, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implémente un stockage soutenu par des cookies : il sérialise la session entière au cookie, plutôt qu'une simple clé de session. Ne l'utilisez que lorsque les données de session sont relativement petites et facilement encodées en tant que valeurs primitives (plutôt que d'objets). Bien que les navigateurs soient supposés supporter au moins 4096 octets par cookie, pour vous assurer de ne pas dépasser la limite, ne pas dépasser une taille de 4093 octets par domaine. Sachez également que les données des cookies seront visibles par le client, donc s'il y a une raison de le garder sécurisé ou obscur, alors `express-session` pourrait être un meilleur choix.
+
+### Ne pas utiliser le nom du cookie de session par défaut
+
+Utiliser le nom par défaut des cookies de session peut ouvrir votre application à des attaques. Le problème de sécurité posé est similaire à `X-Powered-By`: un attaquant potentiel peut l'utiliser pour empreinte digitale le serveur et les attaques ciblées en conséquence.
+
+Pour éviter ce problème, utilisez des noms génériques de cookies; par exemple en utilisant [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.se(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Définir les options de sécurité des cookies
+
+Définissez les options suivantes des cookies pour améliorer la sécurité :
+
+- `secure` - Permet au navigateur d'envoyer le cookie uniquement via HTTPS.
+- `httpOnly` - Assure que le cookie est envoyé uniquement sur HTTP(S), et non sur le JavaScript du client, aidant à se protéger contre les attaques de scripts intersites.
+- `domain` - indique le domaine du cookie; utilisez-le pour comparer avec le domaine du serveur dans lequel l'URL est demandée. S'ils correspondent alors vérifiez l'attribut path suivant.
+- `path` - indique le chemin du cookie; utilisez-le pour comparer le chemin de la requête. Si cela et le domaine correspondent, alors envoyez le cookie dans la requête.
+- `expires` - utiliser pour définir la date d'expiration des cookies persistants.
+
+Voici un exemple utilisant [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000); // 1 hour
+app.use(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      domain: 'example.com',
+      path: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## Empêcher les attaques par force brute contre l'autorisation
+
+Assurez-vous que les terminaux de connexion sont protégés pour rendre les données privées plus sécurisées.
+
+Une technique simple et puissante est de bloquer les tentatives d'autorisation à l'aide de deux mesures :
+
+1. Le nombre de tentatives échouées consécutives par le même nom d'utilisateur et adresse IP.
+2. Le nombre de tentatives échouées depuis une adresse IP sur une longue période. Par exemple, bloquer une adresse IP si elle fait 100 tentatives échouées en un jour.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. Vous pouvez trouver [un exemple de protection brute dans la documentation] (https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Assurez-vous que vos dépendances sont sécurisées
+
+Utiliser npm pour gérer les dépendances de votre application est puissant et pratique. Mais les paquets que vous utilisez peuvent contenir des vulnérabilités de sécurité critiques qui pourraient également affecter votre application. La sécurité de votre application est aussi forte que le « lien le plus faible » dans vos dépendances.
+
+Depuis npm@6, npm vérifie automatiquement chaque demande d'installation. Vous pouvez également utiliser `npm audit` pour analyser votre arborescence des dépendances.
+
+```bash
+Audit npm $
+```
+
+Si vous voulez être plus sécurisé, considérez [Snyk](https://snyk.io/).
+
+Snyk offre à la fois un [outil de ligne de commande] (https://www.npmjs.com/package/snyk) et une [intégration Github](https://snyk.io/docs/github) qui vérifie votre application contre [la base de données de vulnérabilité open source] (https://snyk.io/vuln/) pour toutes les vulnérabilités connues dans vos dépendances. Installez le CLI comme suit:
+
+```bash
+$ npm install -g snyk
+$ cd votre-application
+```
+
+Utilisez cette commande pour tester les vulnérabilités de votre application :
+
+```bash
+$ test snyk
+```
+
+### Éviter les autres vulnérabilités connues
+
+Gardez un œil sur [Node Security Project](https://npmjs.com/advisories) ou [Snyk](https://snyk.io/vuln/) qui peuvent affecter Express ou d'autres modules que votre application utilise. En général, ces bases de données sont d'excellentes ressources pour la connaissance et les outils sur la sécurité des nœuds.
+
+Enfin, les applications Express&mdash;comme toutes les autres applications web&mdash;peuvent être vulnérables à diverses attaques sur le Web. Familiarisez-vous avec les [vulnérabilités web connues] (https://www.owasp.org/www-project-top-ten/) et prenez des précautions pour les éviter.
+
+## Considérations supplémentaires
+
+Voici quelques autres recommandations de l'excellent [Liste de contrôle de sécurité Node.js](https://blog.risingstack.com/node-js-security-checklist/). Reportez-vous à cet article de blog pour tous les détails sur ces recommandations :
+
+- Filtrer et nettoyer toujours les entrées de l'utilisateur pour se protéger contre les attaques de script intersite (XSS) et d'injection de commandes.
+- Protégez contre les attaques d'injection SQL en utilisant des requêtes paramétrées ou des requêtes préparées.
+- Utilisez l'outil [sqlmap](http://sqlmap.org/) pour détecter les vulnérabilités d'injection SQL dans votre application.
+- Utilisez les outils [nmap](https://nmap.org/) et [sslyze](https://github.com/nabla-c0d3/sslyze) pour tester la configuration de vos codes SSL, , et renégociation ainsi que la validité de votre certificat.
+- Utilisez [safe-regex](https://www.npmjs.com/package/safe-regex) pour vous assurer que vos expressions régulières ne sont pas susceptibles d'attaques [déni de service d'expression régulière](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/fr/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/fr/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..25736a4538
--- /dev/null
+++ b/src/content/pages/fr/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Tests de santé et arrêt gracieux
+description: Apprenez comment mettre en œuvre des contrôles de santé et une fermeture gracieuse dans les applications Express pour améliorer la fiabilité, gérer les déploiements et s'intégrer avec les équilibreurs de charge comme Kubernetes.
+---
+
+## Arrêt gracieux
+
+Lorsque vous déployez une nouvelle version de votre application, vous devez remplacer la version précédente. Le gestionnaire de processus que vous utilisez enverra d'abord un signal SIGTERM à l'application pour l'informer qu'il sera tué. Une fois que l'application reçoit ce signal, elle devrait cesser d'accepter de nouvelles requêtes, terminer toutes les demandes en cours, nettoyer les ressources utilisées, y compris les connexions à la base de données et les verrous de fichiers puis quitter.
+
+### Exemple
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Examens de santé
+
+Un répartiteur de charge utilise des contrôles de santé pour déterminer si une instance de l'application est saine et peut accepter les demandes. Par exemple, [Kubernetes a deux examens de santé](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, qui détermine quand redémarrer un conteneur.
+- `readiness`, qui détermine quand un conteneur est prêt à accepter le trafic. Lorsqu'un pod n'est pas prêt, il est retiré des répartiteurs de charge du service.
diff --git a/src/content/pages/fr/advanced/security-updates.mdx b/src/content/pages/fr/advanced/security-updates.mdx
new file mode 100644
index 0000000000..5bca00be1e
--- /dev/null
+++ b/src/content/pages/fr/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Mises à jour de sécurité
+description: Examinez les dernières mises à jour de sécurité et correctifs pour Express.js, y compris les listes de vulnérabilité détaillées pour différentes versions pour aider à maintenir une application sécurisée.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="Alerte">
+
+Les vulnérabilités de Node.js affectent directement Express. Therefore, keep a watch on Node.js
+vulnerabilities and make sure you are using the latest
+stable version of Node.js.
+
+</Alert>
+
+La liste ci-dessous énumère les vulnérabilités Express qui ont été corrigées dans la mise à jour de version spécifiée.
+
+<Alert type="Infos">
+
+Si vous pensez avoir découvert une faille de sécurité dans Express, veuillez consulter [Politiques et procédures de sécurité
+de sécurité [/en/resources/contributing#security-policies-and-procedures).
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - La dépendance `path-to-regexp` a été mise à jour pour répondre à un [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - Le `cookie` de dépendance a été mis à jour pour répondre à un [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), cela peut affecter votre application si vous utilisez `res.cookie`.
+- 4.20.0
+  - Correction de la vulnérabilité XSS dans `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - La dépendance `serve-static` a été mise à jour pour adresser un [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - La dépendance `send` a été mise à jour pour répondre à un [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - La dépendance `path-to-regexp` a été mise à jour pour répondre à un [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - La dépendance `body-parser` a été mise à jour pour administrer un [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), cela peut affecter votre application si vous aviez l'url en cours d'activation.
+- 4.19.0, 4.19.1
+  - Correction de la vulnérabilité de redirection ouverte dans `res.location` et `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - La dépendance `qs` a été mise à jour pour répondre à un [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). Cela peut affecter votre application si les API suivantes sont utilisées: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - La dépendance `transférée` a été mise à jour pour répondre à un [vulnerability](https://npmjs.com/advisories/527). Cela peut affecter votre application si les API suivantes sont utilisées: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - La dépendance `mime` a été mise à jour pour répondre à un [vulnerability](https://npmjs.com/advisories/535), mais ce problème n'a pas d'impact sur Express.
+  - La dépendance `send` a été mise à jour pour fournir une protection contre une vulnérabilité [Node.js 8.5.0](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Ceci n'affecte que l'exécution Express sur la version spécifique de Node.js 8.5.0.
+- 4.15.5
+  - La dépendance `debug` a été mise à jour pour répondre à un [vulnerability](https://snyk.io/vuln/npm:debug:20170905), mais ce problème n'a pas d'impact sur Express.
+  - La dépendance `fresh` a été mise à jour pour répondre à un [vulnerability](https://npmjs.com/advisories/526). Cela affectera votre application si les API suivantes sont utilisées: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - La dépendance `ms` a été mise à jour pour adresser un [vulnerability](https://snyk.io/vuln/npm:ms:20170412). Cela peut affecter votre application si des chaînes de caractères non fiables sont passées à l'option `maxAge` dans les APIs suivantes: `express.static`, `res.sendfile` et `res.sendFile`.
+- 4.15.2
+  - La dépendance `qs` a été mise à jour pour répondre à un [vulnerability](https://snyk.io/vuln/npm:qs:20170213), mais ce problème n'a pas d'impact sur Express. Mettre à jour la version 4.15.2 est une bonne pratique, mais pas nécessaire pour résoudre la vulnérabilité.
+- 4.11.1
+  - Correction de la vulnérabilité de divulgation de chemin racine dans `express.static`, `res.sendfile` et `res.sendFile`
+- 4.10.7
+  - Correction de la vulnérabilité de redirection ouverte dans `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Correction de vulnérabilités de traversée de répertoire dans `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 peut fuir `fd`s dans certaines situations qui affectent `express.static` et `res.sendfile`. Des requêtes malveillantes pourraient provoquer une fuite de `fd`s et éventuellement entraîner des erreurs `EMFILE` et une incapacité du serveur.
+- 4.8.0
+  - Les tableaux d'analyse qui ont des index extrêmement élevés dans la chaîne de requête peuvent faire que le processus est à court de mémoire et planter le serveur.
+  - Les objets de chaîne de requête extrêmement imbriqués peuvent bloquer le processus et rendre le serveur temporairement inadapté.
+
+## 3.x
+
+<Alert type="avertissement">
+\*\*Express 3.x EST END-OF-LIFE ET AUCUNE LONGER MAINTENUE \*\*
+
+Les problèmes connus et inconnus de sécurité et de performance dans 3.x n'ont pas été résolus depuis la dernière mise à jour (1 août 2015). Il est fortement recommandé d'utiliser la dernière version de Express.
+
+Si vous ne pouvez pas mettre à jour après la version 3.x, veuillez considérer [les options de support commercial](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Correction de la vulnérabilité de divulgation de chemin racine dans `express.static`, `res.sendfile` et `res.sendFile`
+- 3.19.0
+  - Correction de la vulnérabilité de redirection ouverte dans `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Correction de vulnérabilités de traversée de répertoire dans `express.static`.
+- 3.16.6
+  - Node.js 0.10 peut fuir `fd`s dans certaines situations qui affectent `express.static` et `res.sendfile`. Des requêtes malveillantes pourraient provoquer une fuite de `fd`s et éventuellement entraîner des erreurs `EMFILE` et une incapacité du serveur.
+- 3.16.0
+  - Des tableaux d'analyse qui ont des index extrêmement élevés dans la chaîne de requête peuvent faire que le processus est à court de mémoire et planter le serveur.
+  - Les objets de chaîne de requête extrêmement imbriqués peuvent bloquer le processus et rendre le serveur temporairement inadapté.
+- 3.3.0
+  - La réponse 404 d'une tentative de substitution de méthode non supportée était susceptible d'attaques de type cross-site scripting.
diff --git a/src/content/pages/fr/guide/database-integration.mdx b/src/content/pages/fr/guide/database-integration.mdx
new file mode 100644
index 0000000000..43778395ff
--- /dev/null
+++ b/src/content/pages/fr/guide/database-integration.mdx
@@ -0,0 +1,502 @@
+---
+title: Intégration de la base de données
+description: Découvrez comment intégrer différentes bases de données avec les applications Express.js, y compris des exemples de configuration pour MongoDB, MySQL, PostgreSQL, et plus encore.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Ajouter la possibilité de connecter des bases de données à des applications Express est juste une question de charger un pilote Node.js approprié pour la base de données dans votre application. Ce document explique brièvement comment ajouter et utiliser certains des modules Node.js les plus populaires pour les systèmes de base de données dans votre application Express :
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [Serveur SQL](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="Alerte">
+
+Ces pilotes de bases de données sont parmi les nombreux qui sont disponibles. Pour d'autres options, recherchez sur le site
+[npm](https://www.npmjs.com/).
+
+</Alert>
+
+## Cassandra
+
+**Module** : [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installation
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Exemple
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.xecute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Module** : [couchnode](https://github.com/couchbase/couchnode)
+
+### Installation
+
+```bash
+$ npm install couchbase
+```
+
+### Exemple
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// ajoute un document à un bucket
+bucket. nsert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console. og(err);
+  } autre {
+    console. og(result);
+  }
+});
+
+// obtient tous les documents de taille de chaussures 13
+const n1ql = 'SELECT d. FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery. romString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Module** : [nano](https://github.com/dscape/nano)
+
+### Installation
+
+```bash
+$ npm install nano
+```
+
+### Exemple
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db. se('livress');
+
+// Insérer un document dans la base de données de livres
+. nsert({ name: 'L'Art de la guerre' }, null, (err, body) => {
+  if (err) {
+    console. og(err);
+  } autre {
+    console. og(body);
+  }
+});
+
+// Obtenez une liste de tous les livres
+livres. ist((err, body) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Module** : [levelup](https://github.com/rvagg/node-levelup)
+
+### Installation
+
+```bash
+$ npm install levelup levelup level down
+```
+
+### Exemple
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.ut('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.et('name', (err, value) => {
+    if (err) return console.og('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Module** : [mysql](https://github.com/felixge/node-mysql/)
+
+### Installation
+
+```bash
+$ npm install mysql
+```
+
+### Exemple
+
+```js
+const mysql = require('mysql');
+const connection = mysql.reateConnection({
+  hôte: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connexion.onnect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.og('La solution est : ', lignes[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Module** : [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installation
+
+```bash
+$ npm install mongodb
+```
+
+### Exemple (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db. ollection('mammifères)
+    .find()
+    . oArray((err, result) => {
+      if (err) throw err;
+
+      console. og(résultat);
+    });
+});
+```
+
+### Exemple (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client. b('animaux');
+
+  db.collection('mammifères)
+    .find()
+    . oArray((err, result) => {
+      if (err) throw err;
+
+      console. og(résultat);
+    });
+});
+```
+
+Si vous voulez un pilote de modèle objet pour MongoDB, regardez [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Module** : [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installation
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Exemple
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.asic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .un('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].et('count'));
+    })
+    .catch((error) => {
+      console.og(erreur);
+    });
+});
+```
+
+## Oracle
+
+**Module** : [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installation
+
+REMARQUE : [Voir les conditions préalables à l'installation] (https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Exemple
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  utilisateur: '<your db user>',
+  mot de passe : '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+fonction async getEmployee(empId) {
+  let conn;
+
+  essayer {
+    conn = wait oracledb. etConnection(config);
+
+    résultat const = attendre conn. xecute('select * des employés où employee_id = :id', [empId]);
+
+    console. og(result.rows[0]);
+  } attraper (err) {
+    console. og('Aïe ! , erreur);
+  } enfin {
+    if (conn) {
+      // conn assignment fonctionné, ont besoin de fermer
+      attendent conn. perte();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Module** : [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installation
+
+```bash
+$ npm install pg-promise
+```
+
+### Exemple
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS valeur', 123)
+  .hen((data) => {
+    console.log('DATA:', data.value);
+  })
+  .atch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Module** : [redis](https://github.com/mranney/node_redis)
+
+### Installation
+
+```bash
+$ npm install redis
+```
+
+### Exemple
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.et('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.set(['hash key', 'hashtest 2', 'une autre valeur'], redis.print);
+client.keys('clé de hachage', (err, replies) => {
+  console.log(`${replies.length} réponses:`);
+
+  réponses.orEach((reply, i) => {
+    console.og(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## Serveur SQL
+
+**Module** : [tedious](https://github.com/tediousjs/tedious)
+
+### Installation
+
+```bash
+$ npm install tedious
+```
+
+### Exemple
+
+```js
+const Connection = require('tedious').Connexion;
+const Request = require('tedious'). équête;
+
+const config = {
+  serveur: 'localhost',
+  authentification: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // me mettre à jour
+      mot de passe: 'votre_mot de passed', // me mettre à jour
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection. n('connect', (err) => {
+  if (err) {
+    console. og(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'bonjour world'", (err, rowCount) => {
+    if (err) {
+      console. og(err);
+    } autre {
+      console. og(`${rowCount} lignes`);
+    }
+    connexion. lose();
+  });
+
+  request.on('row', (columns) => {
+    colonnes. orEach((column) => {
+      if (column.value === null) {
+        console. og('NULL');
+      } else {
+        console.log(colonne.
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Module** : [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installation
+
+```bash
+$ npm install sqlite3
+```
+
+### Exemple
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.un('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.repare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.un(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.ach('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.og(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Module** : [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installation
+
+```bash
+$ npm install elasticsearch
+```
+
+### Exemple
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  hôte: 'localhost:9200',
+});
+
+client
+  . earch({
+    index: 'books',
+    type: 'book',
+    corps : {
+      requête : {
+        multi_match: {
+          requête: 'express js',
+          champs: ['title', 'description'],
+        },
+      },
+    },
+  })
+  . hen(
+    (response) => {
+      hits const = response.hits. its;
+    },
+    (erreur) => {
+      console. course(erreur.message);
+    }
+);
+```
diff --git a/src/content/pages/fr/guide/migrating-4.mdx b/src/content/pages/fr/guide/migrating-4.mdx
new file mode 100644
index 0000000000..54320b08b6
--- /dev/null
+++ b/src/content/pages/fr/guide/migrating-4.mdx
@@ -0,0 +1,666 @@
+---
+title: Déplacement vers Express 4
+description: Un guide pour migrer vos applications Express.js de la version 3 à la version 4, couvrant les changements dans le middleware, le routage et la façon de mettre à jour votre code base efficacement.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 est un changement ininterrompu de Express 3. Cela signifie qu'une application Express 3 existante ne fonctionnera _pas_ si vous mettez à jour la version Express dans ses dépendances.
+
+Cet article couvre :
+
+<ul class="docliste">
+  <li>
+    <a href="#changes">Changes in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Mise à niveau vers le générateur d'applications Express 4</a>.
+  </li>
+</ul>
+
+## Changements dans Express 4
+
+Il y a plusieurs changements significatifs dans Express 4 :
+
+<ul class="docliste">
+  <li>
+    <a href="#core-changes">Changement de coeur et de système middleware Express.</a> Les
+    dépendances de Connect et les middleware intégrés ont été supprimées, vous devez donc ajouter du
+    middleware vous-même.
+  </li>
+  <li>
+    <a href="#routing">Modifications au système de routage.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Diverses autres modifications.</a>
+  </li>
+</ul>
+
+Voir aussi:
+
+- [Nouvelles fonctionnalités en 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migration de 3.x vers 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Changements vers le coeur Express et le système middleware
+
+Express 4 ne dépend plus de Connect, et supprime tous les middleware
+intégrés de son cœur, à l'exception de la fonction `express.static`. Cela signifie que
+Express est maintenant une framework web de routage et de middleware indépendante, et
+Le versionnage et les versions Express ne sont pas affectés par les mises à jour du middleware.
+
+Sans middleware intégré, vous devez explicitement ajouter tout le middleware
+nécessaire pour exécuter votre application. Suivez simplement ces étapes :
+
+1. Installez le module: `npm install --save <module-name>`
+2. Dans votre application, nécessite le module : `require('module-name')`
+3. Utilisez le module selon sa documentation: `app.use( ... )`
+
+Le tableau suivant liste les middleware Express 3 et leurs homologues dans Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compression</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">session de cookies</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">analyseur de cookies</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">session expresse</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">favicon service</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">temps de réponse</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">méthode-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">délai de connexion</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">indice de service</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">serve-static</a>
+    </td>
+  </tr>
+</table>
+
+Voici la [liste complète] (https://github.com/senchalabs/connect#middleware) du middleware Express 4.
+
+Dans la plupart des cas, vous pouvez simplement remplacer l'ancienne version 3 du middleware par
+son homologue Express 4. Pour plus de détails, consultez la documentation du module dans
+GitHub.
+
+#### `app.use` accepte les paramètres
+
+Dans la version 4, vous pouvez utiliser un paramètre variable pour définir le chemin où les fonctions du middleware sont chargées, puis lit la valeur du paramètre à partir du gestionnaire de routes.
+Par exemple :
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### Le système de routage
+
+Les applications chargent implicitement le middleware de routage, donc vous n'avez plus à
+vous inquiéter de l'ordre dans lequel le middleware est chargé par rapport à
+le middleware `router`.
+
+The way you define routes is unchanged, but the routing system has two
+new features to help organize your routes:
+
+- Une nouvelle méthode, `app.route()`, pour créer des gestionnaires de routes chaînables pour un chemin de route.
+- Une nouvelle classe, `express.Router`, pour créer des gestionnaires de routes modulaires montables.
+
+#### méthode `app.route()`
+
+La nouvelle méthode `app.route()` vous permet de créer des gestionnaires de routes chaînables
+pour un chemin de route. Parce que le chemin est spécifié dans un seul endroit, la création de routes modulaires est utile, tout comme la réduction de la redondance et des fautes de frappe. Pour plus d'informations
+sur les routes, voir [`Router()` documentation](/en/4x/api#router).
+
+Voici un exemple de gestionnaires de routes enchaînés qui sont définis en utilisant la fonction `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    end('Obtenir un livre aléatoire');
+  })
+  .ost((req, res) => {
+    res.send('Ajouter un livre');
+  })
+  .ut((req, res) => {
+    res.send('Mettre à jour le livre');
+  });
+```
+
+#### Classe `express.Router`
+
+L'autre fonctionnalité qui aide à organiser les routes est une nouvelle classe,
+`express.Router`, que vous pouvez utiliser pour créer des gestionnaires de routes montables modulaires
+. Une instance `Router` est un middleware complet et un système de routage
+; pour cette raison, elle est souvent appelée "mini-app".
+
+L'exemple suivant crée un routeur en tant que module, charge le middleware dans
+it, définit certains itinéraires, et le monte sur un chemin sur l'application principale.
+
+Par exemple, créez un fichier de routeur nommé `birds.js` dans le répertoire de l'application,
+avec le contenu suivant:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specific to this router
+router.use((req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+});
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Ensuite, chargez le module routeur dans l'application :
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', oiseaux);
+```
+
+L'application sera maintenant en mesure de traiter les requêtes vers les chemins `/birds` et
+`/birds/about`, et appellera le middleware `timeLog`
+spécifique à la route.
+
+### Autres modifications
+
+Le tableau suivant liste d'autres changements mineurs mais importants dans Express 4 :
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Objet</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>
+      Express 4 nécessite Node.js 0.10.x ou ultérieur et a abandonné la prise en charge de Node.js
+      0.8.x.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      Le module `http` n'est plus nécessaire, à moins que vous ayez besoin de travailler directement
+      avec lui (socket.io/SPDY/HTTPS). L'application peut être démarrée en utilisant la fonction
+      `app.listen()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      La fonction `app.configure()` a été supprimée. Utilisez la fonction `process.env.NODE_ENV` ou
+      `app.get('env')` pour détecter l'environnement et configurer l'application en conséquence.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      La propriété `json spaces` de l'application est désactivée par défaut dans Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Utilisez `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, et
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">Ne résout plus les URL relatives.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">A été un tableau ; maintenant un objet.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Était une fonction ; maintenant un objet.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Changé en `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Maintenant disponible en tant que `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">Supprimé.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Supprimé.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      La fonctionnalité est maintenant limitée à définir la valeur de base des cookies. Utilisez
+      `res.cookie()` pour ajouter une fonctionnalité .
+    </td>
+  </tr>
+</table>
+
+## Exemple de migration d'applications
+
+Voici un exemple de migration d'une application Express 3 vers Express 4.
+Les fichiers d'intérêt sont `app.js` et `package.json`.
+
+### Application version 3
+
+#### `app.js`
+
+Considérez une application Express v.3 avec le fichier `app.js` suivant :
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('. routes/utilisateur');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// toutes les applications
+environnement.et('port', process.env.PORT || 3000);
+app.set('vues', path.join(__dirname, 'views'));
+app.set('voir engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.ession({ secret: 'votre secret ici' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.tatic(path.join(__dirname, 'public')));
+
+// développement seulement
+if (app.get('env') === 'development') {
+  app.se(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.reateServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+Le fichier `package.json` de la version 3 pourrait ressembler à
+quelque chose comme ceci:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dépendances": {
+    "express": "3. 2.0",
+    "pug": "*"
+  }
+}
+```
+
+### Processus
+
+Commencez le processus de migration en installant le middleware requis pour l'application
+Express 4 et en mettant à jour Express et Pug vers leur dernière version
+respective avec la commande suivante :
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Effectuez les modifications suivantes à `app.js`:
+
+1. Les fonctions internes du middleware Express `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` et
+   `express.errorHandler` ne sont plus disponibles sur l'objet
+   `express`. Vous devez installer leurs alternatives
+   manuellement et les charger dans l'application.
+
+2. Vous n'avez plus besoin de charger la fonction `app.router`.
+   Ce n'est pas un objet d'application Express 4 valide, alors supprimez le code
+   `app.use(app.router);`.
+
+3. Assurez-vous que les fonctions du middleware sont chargées dans le bon ordre - chargez `errorHandler` après avoir chargé les routes de l'application.
+
+### Application version 4
+
+#### `package.json`
+
+Lancer la commande `npm` ci-dessus mettra à jour `package.json` comme suit:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1. ",
+    "express": "^4.8.0",
+    "express-session": "^1. .2",
+    "pug": "^2.0.0",
+    "method-override": "^2. .2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1. ",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Then, remove invalid code, load the required middleware, and make other
+changes as necessary. Le fichier `app.js` ressemblera à ceci :
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('. routes/utilisateur');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// tous environnements
+application. et('port', process.env.PORT || 3000);
+app.set('vues', path.join(__dirname, 'views'));
+app.set('moteur de vue', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico'));
+app.use(logger('dev'));
+application. se(methodOverride());
+app. se(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app. se(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes. ndex);
+app.get('/users', user.list);
+
+// gestion des erreurs du middleware doit être chargée après le chargement des routes
+si (app. et('env') === 'développement') {
+  application. se(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app. et('port'), () => {
+  console.log('Ecoute de serveur Express sur le port ' + app.get('port'));
+});
+```
+
+<Alert type="Infos">
+Sauf si vous avez besoin de travailler directement avec le module `http` (socket.io/SPDY/HTTPS), le chargement n'est pas nécessaire et l'application peut être simplement démarrée de cette façon :
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Ecouter le serveur Express sur le port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Exécuter l'application
+
+Le processus de migration est terminé, et l'application est maintenant une application
+Express 4. Pour confirmer, lancez l'application en utilisant la commande suivante :
+
+```bash
+$ node .
+```
+
+Charger [http://localhost:3000](http://localhost:3000)
+et voir la page d'accueil rendue par Express 4.
+
+## Mise à niveau vers le générateur d'application Express 4
+
+L'outil en ligne de commande pour générer une application Express est toujours
+`express`, mais pour mettre à jour vers la nouvelle version, vous devez désinstaller
+le générateur d'applications Express 3 puis installer le nouveau
+`express-generator`.
+
+### Installation en cours
+
+Si vous avez déjà le générateur d'application Express 3 installé sur votre système,
+vous devez le désinstaller :
+
+```bash
+$ npm désinstaller -g express
+```
+
+Selon la façon dont vos droits de fichier et de répertoire sont configurés,
+vous pourriez avoir besoin d'exécuter cette commande avec `sudo`.
+
+Installez maintenant le nouveau générateur :
+
+```bash
+$ npm install -g express-generator
+```
+
+Selon la façon dont vos droits de fichier et de répertoire sont configurés,
+vous pourriez avoir besoin d'exécuter cette commande avec `sudo`.
+
+Maintenant la commande `express` sur votre système est mise à jour vers le générateur
+Express 4.
+
+### Modifications du générateur d'application
+
+Les options de commande et l'utilisation restent en grande partie les mêmes, avec les exceptions suivantes :
+
+- Suppression de l'option `--sessions`.
+- Suppression de l'option `--jshtml`.
+- Ajout de l'option `--hogan` pour supporter [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Exemple
+
+Exécutez la commande suivante pour créer une application Express 4 :
+
+```bash
+$ app4 express
+```
+
+Si vous regardez le contenu du fichier `app4/app.js`, vous remarquerez
+que toutes les fonctions du middleware (sauf `express. tatic`) requis pour
+l'application est chargée en tant que modules indépendants, et le middleware `router`
+n'est plus explicitement chargé dans l'application.
+
+Vous remarquerez également que le fichier `app.js` est maintenant un Node. , contrairement à l'application autonome générée par l'ancien générateur.
+
+Après avoir installé les dépendances, lancez l'application en utilisant la commande suivante :
+
+```bash
+$ npm start
+```
+
+Si vous regardez le script `npm start` dans le paquet. son`fichier,
+vous remarquerez que la commande qui démarre l'application est`node . bin/www`, qui était `node app.js\`
+dans Express 3.
+
+Parce que le fichier `app.js` qui a été généré par le générateur Express 4
+est maintenant un nœud. , il ne peut plus être démarré indépendamment en tant qu'application
+(sauf si vous modifiez le code). Le module doit être chargé dans un fichier Node.js
+et démarré via le fichier Node.js. Le fichier Node.js est `./bin/www`
+dans ce cas.
+
+Ni le répertoire `bin` ni le fichier `www`
+sans extension n'est obligatoire pour créer une application Express ou démarrer l'application. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+Pour se débarrasser du répertoire `www` et garder les choses comme "Express 3 way",
+supprime la ligne qui dit `module. xports = app;` à la fin du fichier
+`app.js`, puis collez le code suivant à sa place:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+Assurez-vous de charger le module `debug` en haut du fichier `app.js` en utilisant le code suivant :
+
+```js
+var debug = require('debug')('app4');
+```
+
+Ensuite, changez `"start": "node ./bin/www"` dans le fichier `package.json` en `"start": "node app.js"`.
+
+Vous avez maintenant déplacé la fonctionnalité de `./bin/www` vers
+`app.js`. Ce changement n'est pas recommandé, mais l'exercice vous aide
+à comprendre comment le `. Le fichier bin/www` fonctionne, et pourquoi le fichier `app.js`
+ne démarre plus seul.
diff --git a/src/content/pages/fr/guide/migrating-5.mdx b/src/content/pages/fr/guide/migrating-5.mdx
new file mode 100644
index 0000000000..457daf944c
--- /dev/null
+++ b/src/content/pages/fr/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Déplacement vers Express 5
+description: Un guide complet pour migrer vos applications Express.js de la version 4 à 5, détaillant les changements cassés, les méthodes obsolètes et les nouvelles améliorations.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+L'Express 5 n'est pas très différent de l'Express 4 ; bien qu'il maintienne la même API de base, il y a toujours des changements qui cèdent la compatibilité avec la version précédente. Par conséquent, une application construite avec Express 4 pourrait ne pas fonctionner si vous la mettez à jour pour utiliser Express 5.
+
+Pour installer cette version, vous devez avoir une version 18 ou supérieure de Node.js. Ensuite, exécutez la commande suivante dans le répertoire de votre application :
+
+```sh
+npm install "express@5"
+```
+
+Vous pouvez ensuite exécuter vos tests automatisés pour voir ce qui échoue, et corriger les problèmes en fonction des mises à jour listées ci-dessous. Après avoir résolu des échecs de test, exécutez votre application pour voir quelles erreurs se produisent. Vous découvrirez immédiatement si l'application utilise des méthodes ou des propriétés qui ne sont pas prises en charge.
+
+## 5 Codemos Express
+
+Pour vous aider à migrer votre serveur express nous avons créé un ensemble de codemods qui vous aideront à mettre à jour automatiquement votre code vers la dernière version d'Express.
+
+Exécutez la commande suivante pour exécuter tous les codemods disponibles :
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+Si vous voulez exécuter un code spécifique, vous pouvez exécuter la commande suivante :
+
+```sh
+codemod@latest @expressjs/name-of-the-codemod
+```
+
+Vous pouvez trouver la liste des codes disponibles [here](https://codemod.link/express).
+
+## Changements dans Express 5
+
+**Méthodes et propriétés supprimées**
+
+<ul class="docliste">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Noms de méthodes plurialisées</a>
+  </li>
+  <li>
+    <a href="#leading">Deux points principaux dans l'argument de nom à app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(nom)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, statut)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') et res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, statut)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, statut)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:le journal de débogage</a>
+  </li>
+</ul>
+
+**Modifié**
+
+<ul class="docliste">
+  <li>
+    <a href="#path-syntax">Path route matching syntax</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">Rejected promises handled from middleware and handlers</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Améliorations**
+
+<ul class="docliste">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Support de l'encodage Brotli</a>
+  </li>
+</ul>
+
+## Méthodes et propriétés supprimées
+
+Si vous utilisez l'une de ces méthodes ou propriétés dans votre application, cela plantera. Donc, vous devrez changer votre application après la mise à jour vers la version 5.
+
+### app.del()
+
+Express 5 ne prend plus en charge la fonction `app.del()`. Si vous utilisez cette fonction, une erreur est levée. Pour enregistrer les routes HTTP DELETE, utilisez la fonction `app.delete()` à la place.
+
+Initialement, `del` a été utilisé à la place de `delete`, parce que `delete` est un mot-clé réservé en JavaScript. Cependant, depuis ECMAScript 6, `delete` et d'autres mots-clés réservés peuvent légalement être utilisés comme noms de propriétés.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+codemod@latest @expressjs/route-de-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+application.elete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+La signature `app.param(fn)` a été utilisée pour modifier le comportement de la fonction `app.param(name, fn)`. Il est obsolète depuis la version 4.11.0, et Express 5 ne le supporte plus du tout.
+
+### Noms de méthodes pluralisées
+
+Les noms de méthodes suivantes ont été pluralisés. Dans Express 4, l'utilisation des anciennes méthodes a donné lieu à un avertissement de dépréciation. Express 5 ne les supporte plus du tout:
+
+`req.acceptsCharset()` est remplacé par `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` est remplacé par `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` est remplacé par `req.acceptsLanguages()`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.cceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+application.ll('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### Point-virgule (:) dans le nom de app.param(name, fn)
+
+Un caractère de deux points (:) dans le nom de l'application`. aram(name, fn)` est un reste d'Express 3, et pour des raisons de compatibilité ascendante, Express 4 l'a supporté avec une notification de dépréciation. Express 5 l'ignorera silencieusement et utilisera le paramètre de nom sans le préfixer avec un deux-points.
+
+Cela ne devrait pas affecter votre code si vous suivez la documentation Express 4 de [app.param](/en/4x/api#app.param), car il ne fait aucune mention du côlon principal.
+
+### param(nom)
+
+Cette méthode potentiellement confuse et dangereuse de récupération des données de formulaire a été supprimée. Vous devrez maintenant spécifiquement chercher le nom du paramètre soumis dans l'objet `req.params`, `req.body`, ou `req.query`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.aram('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.d;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, statut)
+
+Express 5 ne prend plus en charge la signature `res.json(obj, status)`. Au lieu de cela, définissez le statut, puis enchaînez-le à la méthode `res.json()` comme ceci: `res.status(status).json(obj)`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// application v5
+. ost('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 ne prend plus en charge la signature `res.jsonp(obj, status)`. Au lieu de cela, définissez le statut, puis enchaînez-le à la méthode `res.jsonp()` comme ceci: `res.status(status).jsonp(obj)`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, statut)
+
+Express 5 ne prend plus en charge la signature `res.redirect(url, status)`. À la place, utilisez la signature suivante : `res.redirect(status, url)`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') et res.location('back')
+
+Express 5 ne supporte plus la chaîne magique `back` dans les méthodes `res.redirect()` et `res.location()`. À la place, utilisez la valeur `req.get('Referrer') || '/'` pour rediriger vers la page précédente. Dans Express 4, les méthodes `res.redirect('back')` et `res.location('back')` sont dépréciées.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+application.et('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(body, statut)
+
+Express 5 ne prend plus en charge la signature `res.send(obj, status)`. Au lieu de cela, définissez le statut, puis enchaînez-le à la méthode `res.send()` comme ceci: `res.status(status).send(obj)`.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(statut)
+
+Express 5 ne prend plus en charge la signature `res.send(status)`, où `status` est un nombre. À la place, utilisez les `res. la fonction endStatus(statusCode)`, qui définit le code d'état de l'en-tête de réponse HTTP et envoie la version texte du code: "Non trouvée", "Erreur interne du serveur", et ainsi de suite.
+Si vous avez besoin d'envoyer un numéro en utilisant les `res. la fonction end()`, guillemets le nombre pour le convertir en une chaîne, afin qu'Express ne l'interprète pas comme une tentative d'utiliser l'ancienne signature non supportée.
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+La fonction `res.sendfile()` a été remplacée par une version à chameau `res.sendFile()` dans Express 5.
+
+**Note:** En Express 5, `res. endFile()` utilise le paquet `mime-types` pour la détection de type MIME, qui retourne des valeurs de type de contenu différentes que Express 4 pour plusieurs types de fichiers communs:
+
+- Fichiers JavaScript (.js): maintenant "text/javascript" au lieu de "application/javascript"
+- Fichiers JSON (.json): maintenant "application/json" au lieu de "text/json"
+- Fichiers CSS (.css): maintenant "text/css" au lieu de "text/plain"
+- Fichiers XML (.xml): maintenant "application/xml" au lieu de "text/xml"
+- Fichiers de police (.woff): maintenant "font/woff" au lieu de "application/font-woff"
+- Fichiers SVG (.svg): maintenant "image/svg+xml" au lieu de "application/svg+xml"
+
+<Alert type="Infos">
+Vous pouvez remplacer les signatures obsolètes par la commande suivante :
+
+```plaintext
+codemod@latest @expressjs/camelcase-sendfile npx
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+La signature `router.param(fn)` a été utilisée pour modifier le comportement de la fonction `router.param(name, fn)`. Il est obsolète depuis la version 4.11.0, et Express 5 ne le supporte plus du tout.
+
+### express.static.mime
+
+Dans Express 5, `mime` n'est plus une propriété exportée du champ `static`.
+Utilisez le paquet [`mime-types`](https://github.com/jshttp/mime-types) pour travailler avec les valeurs de type MIME.
+
+**Important:** Ce changement affecte non seulement l'utilisation directe de `express.static.mime` mais aussi d'autres méthodes Express qui dépendent de la détection de type MIME, telles que `res.sendFile()`. Les types MIME suivants sont passés de Express 4 :
+
+- Fichiers JavaScript (.js): maintenant servi comme "text/javascript" au lieu de "application/javascript"
+- Fichiers JSON (.json): maintenant servi comme "application/json" au lieu de "text/json"
+- Fichiers CSS (.css): maintenant servi comme "text/css" au lieu de "text/plain"
+- Fichiers HTML (): maintenant servi comme "text/html; charset=utf-8" au lieu de "text/html"
+- Fichiers XML (.xml): maintenant servi comme "application/xml" au lieu de "text/xml"
+- Fichiers de police (.woff): maintenant utilisé comme "font/woff" au lieu de "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:journaux de débogage du routeur
+
+Dans Express 5, la logique de gestion du routeur est effectuée par une dépendance. Par conséquent, les journaux de débogage
+pour le routeur ne sont plus disponibles dans l'espace de noms `express:`.
+Dans la v4, les logs étaient disponibles sous les espaces de noms `express:router`, `express:router:layer`,
+et `express:router:route`. Tous ces éléments ont été inclus dans l'espace de noms `express:*`.
+En v5.1+, les logs sont disponibles dans les espaces de noms `router`, `router:layer`, et `router:route`.
+Les logs de `router:layer` et `router:route` sont inclus dans l'espace de noms `router:*`.
+Pour obtenir le même détail de débogage lors de l'utilisation de `express:*` dans la v4, utilisez une conjonction de
+`express:*`, `router`, et `router:*`.
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,routeur:* node index.js
+```
+
+## Modifié
+
+### Syntaxe correspondante au chemin
+
+La syntaxe correspondante au chemin d'accès est lorsqu'une chaîne de caractères est fournie comme premier paramètre pour les API `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, et `router.use()`. Les modifications suivantes ont été apportées à la façon dont la chaîne de chemin est associée à une requête entrante :
+
+- Le caractère générique `*` doit avoir un nom correspondant au comportement des paramètres `:`, utilisez `/*splat` au lieu de `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+application.et('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="Infos">
+`*splat` correspond à n'importe quel chemin sans le chemin racine. Si vous avez besoin de faire correspondre le chemin racine aussi bien que `/`, vous pouvez utiliser `/{*splat}`, envelopper le joker entre parenthèses.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- Le caractère optionnel `?` n'est plus pris en charge, utilisez plutôt des accolades.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// application v5
+. et('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Les caractères Regexp ne sont pas pris en charge. Par exemple :
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+devrait être changé en :
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Certains caractères ont été réservés pour éviter toute confusion lors de la mise à jour (`()[]?+!`), utilisez `\` pour les échapper.
+- Les noms de paramètres supportent maintenant des identifiants JavaScript valides, ou des guillemets comme `:"this"`.
+
+### Les promesses rejetées des middleware et des gestionnaires
+
+Les requêtes de middleware et les gestionnaires qui retournent les promesses rejetées sont maintenant gérées en renvoyant la valeur rejetée comme une `Erreur` vers le middleware. Cela signifie que l'utilisation des fonctions `async` comme middleware et des gestionnaires est plus facile que jamais. Lorsqu'une erreur est levée dans une fonction `async` ou qu'une promesse rejetée est `attendu` dans une fonction asynchrone, ces erreurs seront passées au gestionnaire d'erreurs comme si elle appelait `next(err)`.
+
+Détail de la façon dont Express gère les erreurs est couvert dans la [documentation de gestion des erreurs](/en/guide/error-handling).
+
+### express.urlencodé
+
+La méthode `express.urlencoded` rend l'option `extended` `false` par défaut.
+
+### express.static dotfiles
+
+Dans Express 5, l'option `express.static` du middleware `dotfiles` par défaut est maintenant `"ignore"`. Ceci est un changement par rapport à Express 4, où les dotfiles ont été servis par défaut. En conséquence, les fichiers à l'intérieur d'un répertoire qui commence par un point (`.`), comme `. ell-known`, ne sera plus accessible et retournera une erreur **404 Not Found**. Cela peut casser la fonctionnalité qui dépend du service de répertoires de points, tels que les liens d'applications Android, et Apple Universal Links.
+
+Exemple de code cassé :
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Après avoir migré vers Express 5, une requête vers `/.well-known/assetlinks.json` résultera en un **404 Not Found**.
+
+Pour corriger ceci, servir explicitement des répertoires de points spécifiques en utilisant l'option `dotfiles: "allow"` :
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+Cette approche vous permet de ne servir en toute sécurité que les répertoires de points prévus tout en conservant le comportement sécurisé par défaut pour les autres dotfiles, qui restent inaccessibles.
+
+### Écouter
+
+Dans Express 5, la méthode `app.listen` invoquera la fonction de rappel fournie par l'utilisateur (si fournie) lorsque le serveur reçoit un événement d'erreur. Dans Express 4, de telles erreurs seraient lancées. Ce changement déplace la responsabilité de gestion des erreurs vers la fonction callback dans Express 5. S'il y a une erreur, elle sera passée au callback en tant qu'argument.
+Par exemple :
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Écoute sur ${JSON.stringify(server.address())}`);
+});
+```
+
+### routeur
+
+L'objet `app.router`, qui a été supprimé dans Express 4, a fait un retour dans Express 5. Dans la nouvelle version, cet objet est juste une référence au routeur de base Express, contrairement à Express 3, où une application devait explicitement la charger.
+
+### Req.body
+
+La propriété `req.body` retourne `undefined` quand le corps n'a pas été analysé. Dans Express 4, il retourne `{}` par défaut.
+
+### Hôte
+
+Dans Express 4, la fonction `req.host` a incorrectement retiré le numéro de port si elle était présente. Dans Express 5, le numéro de port est maintenu.
+
+### Réglages
+
+L'objet `req.params` a maintenant un **prototype null** lors de l'utilisation des chemins de chaîne de caractères. Cependant, si le chemin est défini avec une expression régulière, `req.params` reste un objet standard avec un prototype normal. En outre, il y a deux changements importants de comportement:
+
+**Les paramètres de la carte joker sont maintenant des tableaux :**
+
+Les jokers (par exemple, `/*splat`) capturent les segments de chemin en tant que tableau au lieu d'une seule chaîne.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.arams);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Les paramètres sans correspondance sont omis :**
+
+Dans Express 4, les caractères génériques sans correspondance étaient des chaînes vides (`''`) et les paramètres optionnels `:` (à l'aide de `?`) avaient une clé avec la valeur `undefined`. Dans Express 5, les paramètres incomparables sont complètement omis de `req.params`.
+
+```js
+// v4: un joker sans correspondance est une chaîne
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req. arams);
+  // => { '0': '' }
+});
+
+// v4: un paramètre facultatif sans correspondance est une application
+non définie. et('/:file.:ext?', (req, res) => {
+  // GET /image
+  console. ir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{. ext}', (req, res) => {
+  // GET /image
+  console.dir(req. arams);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### Requête
+
+La propriété `req.query` n'est plus une propriété accessible en écriture et est plutôt un getter. L'analyseur de requête par défaut a été changé de "étendu" à "simple".
+
+### Effacer les cookies
+
+La méthode `res.clearCookie` ignore les options `maxAge` et `expires` fournies par l'utilisateur.
+
+### Statut
+
+La méthode `res.status` n'accepte que les entiers de la plage de `100` à `999`, suivant le comportement défini par Node. , et retourne une erreur lorsque le code de statut n'est pas un entier.
+
+### res.vary
+
+Le fichier `res.vary` lance une erreur quand l'argument `field` est manquant. Dans Express 4, si l'argument a été omis, il a donné un avertissement dans la console
+
+## Améliorations
+
+### res.render()
+
+Cette méthode impose maintenant un comportement asynchrone pour tous les moteurs de vue, en évitant les bogues causés par les moteurs de vue qui avaient une implémentation synchronisée et qui violaient l'interface recommandée.
+
+### Prise en charge de l'encodage Brotli
+
+Express 5 prend en charge l'encodage Brotli pour les requêtes reçues des clients qui le supportent.
diff --git a/src/content/pages/fr/resources/glossary.mdx b/src/content/pages/fr/resources/glossary.mdx
new file mode 100644
index 0000000000..b1d378a968
--- /dev/null
+++ b/src/content/pages/fr/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Un glossaire complet de termes liés à Express.js, Node.js, middleware, routing et autres concepts clés pour vous aider à comprendre et utiliser Express efficacement.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### application
+
+En général, un ou plusieurs programmes sont conçus pour réaliser des opérations à des fins précises. Dans le contexte d'Express, un programme qui utilise l'API Express exécutée sur la plate-forme Node.js. Peut aussi se référer à un [objet application] (/en/api#express).
+
+### API
+
+Interface de programmation applicative. Sortez l'abréviation quand elle est utilisée pour la première fois.
+
+### Exprimé
+
+Un framework web rapide, sans avis et minimaliste pour les applications Node.js. En général, "Express" est préféré à "Express.js", bien que ce dernier soit acceptable.
+
+### libuv
+
+Une bibliothèque de support multi-plateforme qui se concentre sur les E/S asynchrones, principalement développée pour Node.js.
+
+### middleware
+
+Une fonction qui est appelée par la couche de routage Express avant le gestionnaire de requête finale, et se trouve donc au milieu entre une requête brute et la route finale. Quelques bons points de terminologie autour du middleware :
+
+- `var foo = require('middleware')` est appelé _requiring_ ou _using_ un module Node.js. Puis l'instruction `var mw = foo()` retourne typiquement le middleware.
+- `app.use(mw)` est appelé _adding the middleware to the global processing stack_.
+- `app.get('/foo', mw, function (req, res) { ... })` est appelé \_ajoutant le middleware à la pile de traitement "GET /foo".
+
+### Node.js
+
+Une plate-forme logicielle utilisée pour construire des applications réseau évolutives. Node.js utilise JavaScript comme langage de script, et obtient un débit élevé via des E/S non-bloquantes et une boucle d'événements à un seul thread. Voir [nodejs.org](https://nodejs.org/en/). **Note d'utilisation**: Initialement, "Node.js," ensuite "Node".
+
+### open-source, open source
+
+Lorsqu'il est utilisé comme adjectif, trait d'union, par exemple : "Il s'agit d'un logiciel open-source". Voir [Logiciel open source sur Wikipédia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="Infos">
+
+Bien qu'il soit courant de ne pas faire de trait d'union avec ce terme, nous utilisons les règles anglaises standards pour
+tiret de trait d'union d'un adjectif composé.
+
+</Alert>
+
+### demande
+
+Une requête HTTP. Un client envoie un message de requête HTTP à un serveur, qui retourne une réponse. La requête doit utiliser une de plusieurs [méthodes de requête] (https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) telles que GET, POST, etc.
+
+### réponse
+
+Une réponse HTTP. Un serveur retourne un message de réponse HTTP au client. La réponse contient des informations sur l'état de la requête et peut également contenir le contenu demandé dans le corps du message.
+
+### route
+
+Partie d'une URL qui identifie une ressource. Par exemple, dans `http://foo.com/products/id`, "/products/id" est la route.
+
+### routeur
+
+Voir [router](/en/api#router) dans la référence de l'API.
diff --git a/src/content/pages/fr/resources/utils.md b/src/content/pages/fr/resources/utils.md
new file mode 100644
index 0000000000..0b064382e4
--- /dev/null
+++ b/src/content/pages/fr/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Utilitaires Express
+description: Découvrez des modules utilitaires liés à Express.js et Node.js, y compris des outils pour les cookies, la protection CSRF, l'analyse d'URL, le routage, et plus encore pour améliorer vos applications.
+---
+
+## Fonctions utilitaires Express
+
+L'organisation GitHub [pillarjs](https://github.com/pillarjs) contient un certain nombre de modules
+pour des fonctions utilitaires qui peuvent être généralement utiles.
+
+| Modules utilitaires                                            | Libellé                                                                                                                                                                                               |
+| -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Obtenez et définissez les cookies HTTP(S) qui peuvent être signés pour éviter toute altération en utilisant Keygrip. Peut être utilisé avec la bibliothèque HTTP Node.js ou comme middleware Express. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contient la logique derrière la création et la vérification de jetons CSRF. Utilisez ce module pour créer un middleware CSRF personnalisé.                                                            |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Fonction à invoquer comme dernière étape pour répondre à la requête HTTP.                                                                                                                             |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Analyser une URL avec le cache.                                                                                                                                                                       |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Transformez une chaîne de chemin de type Express, telle que \`\`/user/:name\` en une expression régulière.                                                                                            |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Résout un chemin relatif par rapport à un chemin racine avec validation.                                                                                                                              |
+| [router](https://www.npmjs.com/package/router)                 | Routeur de type middleware simple.                                                                                                                                                                    |
+| [send](https://www.npmjs.com/package/send)                     | Bibliothèque pour le streaming des fichiers en tant que réponse HTTP, avec le support des réponses partielles (gammes), la négociation conditional-GET et les événements granulaires.                 |
+
+Pour des modules supplémentaires liés au protocole HTTP, voir [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/fr/support.md b/src/content/pages/fr/support.md
new file mode 100644
index 0000000000..2cb3050f0e
--- /dev/null
+++ b/src/content/pages/fr/support.md
@@ -0,0 +1,23 @@
+---
+title: Support de la version
+description: Trouvez des informations sur le calendrier de support des différentes versions de Express.js, y compris les versions actuellement maintenues et les politiques de fin de vie.
+---
+
+Seule la dernière version d'une ligne de publication majeure est prise en charge.
+
+Les versions qui sont EdlV (fin de vie) _peuvent_ recevoir des mises à jour pour les vulnérabilités critiques de sécurité, mais l'équipe Express n'offre aucune garantie et ne prévoit pas de résoudre ou de corriger les problèmes rencontrés.
+
+| Version majeure        | Version minimale de Node.js | Date de début du support | Date de fin du support |
+| ---------------------- | --------------------------- | ------------------------ | ---------------------- |
+| [**v5.x**](/en/5x/api) | 18                          | Septembre 2024           | **en cours**           |
+| [**v4.x**](/en/4x/api) | 0.10.0                      | Avril 2014               | **en cours**           |
+| [**v3.x**](/en/3x/api) | 0.8.0                       | Octobre 2012             | Juillet 2015           |
+| [**v2.x**](/2x/)       | 0.4.1                       | Mars 2011                | Juillet 2012           |
+| **v1.x**               | 0.2.0                       | Décembre 2010            | Mars 2011              |
+| **v0.14.x**            | 0.1.98                      | Décembre 2010            | Décembre 2010          |
+
+## Options de support commercial
+
+Si vous ne pouvez pas mettre à jour une version prise en charge de Express, veuillez contacter l'un de nos partenaires pour recevoir les mises à jour de sécurité :
+
+- [Support des Héros sans fin](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/it/advanced/best-practice-performance.md b/src/content/pages/it/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..c0a8ac9a9c
--- /dev/null
+++ b/src/content/pages/it/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Migliori pratiche di produzione: prestazioni e affidabilità'
+description: Scopri le migliori pratiche di performance e affidabilità per le app Express in produzione, coprendo ottimizzazioni di codice e impostazioni ambientali per prestazioni ottimali.
+---
+
+Questo articolo discute le migliori pratiche di performance e affidabilità per le applicazioni Express distribuite alla produzione.
+
+Questo argomento rientra chiaramente nel mondo dei "devops", che abbraccia sia lo sviluppo tradizionale che le operazioni. Di conseguenza, le informazioni sono suddivise in due parti:
+
+- Cose da fare nel tuo codice (la parte dev):
+  - [Usa compressione gzip](#use-gzip-compression)
+  - [Non utilizzare le funzioni sincrone](#dont-use-synchronous-functions)
+  - [Effettua la registrazione corretta](#do-logging-correctly)
+  - [Maneggiare correttamente le eccezioni](#handle-exceptions-properly)
+- Cose da fare nel tuo ambiente / configurazione (la parte ops):
+  - [Imposta NODE_ENV a "production"](#set-node_env-to-production)
+  - [Assicurati che l'app si riavvii automaticamente](#ensure-your-app-automatically-restarts)
+  - [Esegui la tua app in un cluster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Usa un balancer](#use-a-load-balancer)
+  - [Usa un proxy inverso](#use-a-reverse-proxy)
+
+## Cose da fare nel tuo codice
+
+Ecco alcune cose che puoi fare nel tuo codice per migliorare le prestazioni della tua applicazione:
+
+- [Usa compressione gzip](#use-gzip-compression)
+- [Non utilizzare le funzioni sincrone](#dont-use-synchronous-functions)
+- [Effettua la registrazione corretta](#do-logging-correctly)
+- [Maneggiare correttamente le eccezioni](#handle-exceptions-properly)
+
+### Usa compressione gzip
+
+La compressione di Gzip può ridurre notevolmente la dimensione del corpo della risposta e quindi aumentare la velocità di una web app. Usa il middleware [compression](https://www.npmjs.com/package/compression) per la compressione gzip nella tua app Express. Per esempio:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+Per un sito web ad alto traffico in produzione, il modo migliore per mettere in atto la compressione è implementarla a un livello di proxy inverso (vedere [Usa un proxy inverso](#use-a-reverse-proxy)). In tal caso, non è necessario utilizzare middleware di compressione. Per maggiori dettagli sull'attivazione della compressione gzip in Nginx, vedere [Modulo ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) nella documentazione Nginx.
+
+### Non utilizzare funzioni sincrone
+
+Le funzioni e i metodi sincroni legano il processo di esecuzione fino al loro ritorno. Una singola chiamata ad una funzione sincrona potrebbe tornare in pochi microsecondi o millisecondi, tuttavia nei siti web ad alto traffico, queste chiamate si sommano e riducono le prestazioni dell'app. Evitare il loro uso in produzione.
+
+Sebbene Node e molti moduli forniscano versioni sincrone e asincrone delle loro funzioni, utilizzare sempre la versione asincrona in produzione. L'unico momento in cui una funzione sincrona può essere giustificata è all'avvio iniziale.
+
+Puoi usare il flag da riga di comando `--trace-sync-io` per stampare un avviso e uno stack trace ogni volta che la tua applicazione utilizza un'API sincrona. Naturalmente, non si desidera utilizzare questo in produzione, ma piuttosto per garantire che il codice è pronto per la produzione. Vedi la [documentazione delle opzioni a riga di comando del nodo](https://nodejs.org/api/cli#cli_trace_sync_io) per maggiori informazioni.
+
+### Effettuare la registrazione correttamente
+
+In generale, ci sono due motivi per la registrazione dalla tua app: Per il debug e per la registrazione delle attività delle app (essenzialmente, tutto il resto). Usare `console.log()` o `console.error()` per stampare i messaggi di log sul terminale è una pratica comune nello sviluppo. Ma [queste funzioni sono sincrone](https://nodejs.org/api/console#console) quando la destinazione è un terminale o un file, in modo che non siano adatti per la produzione, a meno che non convogliate l'uscita ad un altro programma.
+
+#### Per il debug
+
+Se stai registrando a fini di debug, invece di usare `console.log()`, usa uno speciale modulo di debug come [debug](https://www.npmjs.com/package/debug). Questo modulo consente di utilizzare la variabile di ambiente DEBUG per controllare quali messaggi di debug vengono inviati a `console.error()`, se presenti. Per mantenere la tua app puramente asincrona, dovresti ancora reindirizzare `console.error()` ad un altro programma. Ma allora, non stai davvero andando a debug nella produzione, vero?
+
+#### Per attività app
+
+Se stai registrando le attività delle app (ad esempio, tracciando traffico o chiamate API), invece di usare `console. og()`, usa una libreria di registrazione come [Pino](https://www.npmjs.com/package/pino), che è l'opzione più veloce ed efficiente disponibile.
+
+### Gestisci correttamente le eccezioni
+
+Le app del nodo si bloccano quando incontrano un'eccezione non catturata. Non gestire le eccezioni e intraprendere azioni appropriate renderà il tuo crash di app Express e andare offline. Se segui i consigli in [Assicurati che la tua app riavvii automaticamente](#ensure-your-app-automatically-restarts) qui sotto, allora la tua app recupererà da un crash. Fortunatamente, le applicazioni Express in genere hanno un breve tempo di avvio. Tuttavia, si desidera evitare di schiantarsi in primo luogo, e per farlo, è necessario gestire le eccezioni correttamente.
+
+Per garantire la gestione di tutte le eccezioni, utilizzare le seguenti tecniche:
+
+- [Usa try-catch](#use-try-catch)
+- [Usa promesse](#use-promises)
+
+Prima di immergersi in questi argomenti, si dovrebbe avere una comprensione di base della gestione degli errori Node/Express: utilizzando error-first callback e gli errori di propagazione in middleware. Il nodo utilizza una convenzione "error-first callback" per restituire gli errori dalle funzioni asincrone, dove il primo parametro della funzione callback è l'oggetto errore, seguito da dati di risultato in parametri successivi. Per indicare nessun errore, passare null come primo parametro. La funzione di callback deve seguire in modo corrispondente la convenzione di callback errore-first callback per gestire in modo significativo l'errore. E in Express, la migliore pratica è quella di utilizzare la funzione next() per propagare gli errori attraverso la catena middleware.
+
+Per maggiori informazioni sui fondamenti della gestione degli errori, consultare:
+
+- [Gestione degli errori in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Usa try-catch
+
+Try-catch è una struttura in linguaggio JavaScript che puoi usare per catturare le eccezioni in codice sincrono. Usa try-catch, per esempio, per gestire gli errori di analisi JSON come mostrato di seguito.
+
+Ecco un esempio di utilizzo di try-catch per gestire una potenziale eccezione di processo-crashing.
+Questa funzione middleware accetta un parametro del campo di query denominato "params" che è un oggetto JSON.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+Tuttavia, try-catch funziona solo per il codice sincrono. Poiché la piattaforma Nodo è principalmente asincrona (in particolare in un ambiente di produzione), il try-catch non prenderà molte eccezioni.
+
+#### Usa promesse
+
+Quando un errore viene lanciato in una funzione `async` o una promessa rifiutata è attesa all'interno di una funzione `async`, questi errori verranno passati al gestore degli errori come se chiamasse `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Inoltre, è possibile utilizzare funzioni asincrone per il vostro middleware, e il router gestirà gli errori se la promessa fallisce, per esempio:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+La migliore pratica è quella di gestire gli errori il più vicino possibile al sito. Quindi, mentre questo è ora gestito nel router, è meglio catturare l'errore nel middleware e gestirlo senza fare affidamento su middleware di gestione degli errori separati.
+
+#### Cosa non fare
+
+Una cosa che dovresti _non_ fare è ascoltare per l'evento `uncaughtException`, emessa quando una bolla di eccezione ritorna fino al ciclo evento. L'aggiunta di un ascoltatore di eventi per `uncaughtException` cambierà il comportamento predefinito del processo che sta incontrando un'eccezione; il processo continuerà a funzionare nonostante l'eccezione. Questo potrebbe sembrare un buon modo per impedire che la tua app si blocchi, ma continuare ad eseguire l'app dopo un'eccezione non catturata è una pratica pericolosa e non è raccomandato, perché lo stato del processo diventa inaffidabile e imprevedibile.
+
+Inoltre, l'utilizzo di `uncaughtException` è ufficialmente riconosciuto come [crude](https://nodejs.org/api/process#process_event_uncaughtexception). Quindi ascoltare `uncaughtException` è solo una cattiva idea. Questo è il motivo per cui consigliamo cose come più processi e supervisori: crash e riavvio è spesso il modo più affidabile per recuperare da un errore.
+
+Inoltre non consigliamo di utilizzare [domains](https://nodejs.org/api/domain). Generalmente non risolve il problema ed è un modulo deprecato.
+
+## Cose da fare nel tuo ambiente / configurazione
+
+Ecco alcune cose che puoi fare nel tuo ambiente di sistema per migliorare le prestazioni della tua app:
+
+- [Imposta NODE_ENV a "production"](#set-node_env-to-production)
+- [Assicurati che l'app si riavvii automaticamente](#ensure-your-app-automatically-restarts)
+- [Esegui la tua app in un cluster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Usa un balancer](#use-a-load-balancer)
+- [Usa un proxy inverso](#use-a-reverse-proxy)
+
+### Imposta NODE_ENV a "produzione"
+
+La variabile d' ambiente NODE_ENV specifica l' ambiente in cui un' applicazione è in esecuzione (solitamente, sviluppo o produzione). Una delle cose più semplici che puoi fare per migliorare le prestazioni è impostare NODE_ENV a `produzione`.
+
+Impostando NODE_ENV a "production" makes Express:
+
+- Modelli visualizzazione della cache.
+- File CSS della cache generati dalle estensioni CSS.
+- Genera messaggi di errore meno dettagliati.
+
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) che solo facendo questo può migliorare le prestazioni dell'app di un fattore di tre!
+
+Se è necessario scrivere un codice specifico per l'ambiente, è possibile controllare il valore di NODE_ENV con `process.env.NODE_ENV`. Essere consapevoli che il controllo del valore di qualsiasi variabile ambientale comporta una penalità di prestazione, e quindi dovrebbe essere fatto con parsimonia.
+
+In fase di sviluppo, in genere imposterai le variabili di ambiente nella tua shell interattiva, ad esempio usando `export` o il tuo file `.bash_profile`. Ma in generale, non dovresti farlo su un server di produzione; invece, usa il sistema di ingresso del tuo sistema operativo (systemd). La sezione successiva fornisce maggiori dettagli sull'utilizzo del sistema di init in generale, ma l'impostazione `NODE_ENV` è così importante per le prestazioni (e facile da fare), che è evidenziata qui.
+
+Con il sistema, usa la direttiva `Environment` nel tuo file unitario. Per esempio:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+Per ulteriori informazioni, vedere [Uso delle variabili ambientali nelle unità systemd](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Assicurati che l'app si riavvii automaticamente
+
+In produzione, non vuoi che la tua applicazione sia offline, mai. Ciò significa che è necessario assicurarsi che si riavvia sia se l'applicazione si blocca e se il server stesso si blocca. Anche se si spera che nessuno di questi eventi accada, realisticamente si deve rendere conto di entrambe le eventualità mediante:
+
+- Utilizzando un gestore di processo per riavviare l'applicazione (e Node) quando si blocca.
+- Utilizzando il sistema di init fornito dal sistema operativo per riavviare il gestore di processo quando il sistema operativo si blocca. È anche possibile utilizzare il sistema init senza un gestore di processo.
+
+Le applicazioni del nodo si bloccano se incontrano un'eccezione non catturata. La cosa più importante che devi fare è assicurarsi che la tua app sia ben testata e gestisca tutte le eccezioni (vedi [gestire le eccezioni correttamente](#handle-exceptions-properly) per i dettagli). Ma come un fail-safe, mettere un meccanismo in atto per garantire che se e quando l'app si blocca, si riavvierà automaticamente.
+
+#### Usa un gestore di processo
+
+In fase di sviluppo, hai avviato la tua app semplicemente dalla riga di comando con `node server.js` o qualcosa di simile. Ma fare questo in produzione è una ricetta per il disastro. Se l'app si blocca, sarà offline fino al riavvio. Per garantire il riavvio dell'app in caso di crash usa un gestore di processo. Un process-manager è un "container" per le applicazioni che facilita l'implementazione, fornisce un'elevata disponibilità e consente di gestire l'applicazione durante il runtime.
+
+Oltre a riavviare la tua app quando si blocca, un gestore di processo può permetterti di:
+
+- Ottieni informazioni sulle prestazioni di runtime e sul consumo di risorse.
+- Modifica le impostazioni dinamicamente per migliorare le prestazioni.
+- Clustering di controllo (pm2).
+
+Storicamente, era popolare usare un manager di processo Node.js come [PM2](https://github.com/Unitech/pm2). Vedere la loro documentazione se si desidera farlo. Tuttavia, si consiglia di utilizzare il sistema init per la gestione dei processi.
+
+#### Usa un sistema init
+
+Il livello successivo di affidabilità è quello di garantire che l'app si riavvia quando il server si riavvia. I sistemi possono ancora andare giù per una varietà di motivi. Per garantire che la tua app si riavvii in caso di crash del server, usa il sistema init integrato nel tuo sistema operativo. Il sistema di init principale oggi in uso è [systemd](https://wiki.debian.org/systemd).
+
+Ci sono due modi per utilizzare i sistemi init con la tua app Express:
+
+- Eseguire l'app in un gestore di processo e installare il gestore di processo come un servizio con il sistema init. Il gestore di processo riavvierà l'app quando l'app si blocca e il sistema init riavvierà il gestore di processo quando il sistema operativo riavvia. Questo è l'approccio raccomandato.
+- Esegui la tua app (e Node) direttamente con il sistema init. Questo è un po 'più semplice, ma non si ottengono i vantaggi aggiuntivi di utilizzare un manager di processo.
+
+##### Systemd
+
+Systemd è un sistema Linux e service manager. La maggior parte delle principali distribuzioni Linux hanno adottato systemd come sistema di init predefinito.
+
+Un file di configurazione del servizio di sistema è chiamato _unit file_, con un nome di file che termina in `.service`. Ecco un file unità di esempio per gestire direttamente un'app Node. Sostituisci i valori racchiusi in `<angle brackets>` per il tuo sistema e l'app:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Per ulteriori informazioni sul sistema, vedere [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Esegui la tua app in un cluster
+
+In un sistema multi-core, è possibile aumentare le prestazioni di un'applicazione Nodo di molte volte lanciando un cluster di processi. Un cluster esegue più istanze dell'app, idealmente una istanza su ogni nucleo della CPU, distribuendo così il carico e le attività tra le istanze.
+
+![Bilanciamento tra istanze dell'applicazione utilizzando l'API cluster](/images/clustering.png)
+
+IMPORTANTE: Poiché le istanze dell'app vengono eseguite come processi separati, non condividono lo stesso spazio di memoria. Cioè, gli oggetti sono locali per ogni istanza dell'app. Pertanto, non è possibile mantenere lo stato nel codice dell'applicazione. Tuttavia, è possibile utilizzare un datastore in memoria come [Redis](http://redis.io/) per memorizzare i dati e lo stato relativi alla sessione. Questa avvertenza si applica essenzialmente a tutte le forme di ridimensionamento orizzontale, sia che si tratti di raggruppamento con più processi o più server fisici.
+
+Nelle applicazioni raggruppate, i processi di lavoro possono bloccarsi individualmente senza influenzare il resto dei processi. Oltre ai vantaggi delle prestazioni, l'isolamento del guasto è un altro motivo per eseguire un cluster di processi app. Ogni volta che un processo di lavoro si blocca, assicurarsi sempre di registrare l'evento e generare un nuovo processo utilizzando cluster.fork().
+
+#### Uso del modulo cluster Node
+
+Il cluster è reso possibile con il [modulo cluster di Node](https://nodejs.org/api/cluster). Ciò consente a un processo master di generare processi di lavoro e distribuire le connessioni in entrata tra i lavoratori.
+
+#### Uso PM2
+
+Se distribuisci la tua applicazione con PM2, puoi approfittare del clustering _without_ modificando il codice dell'applicazione. Dovresti prima assicurarti che la tua [applicazione sia senza condizione](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) il che significa che nessun dato locale viene memorizzato nel processo (ad esempio sessioni, connessioni websocket e simili).
+
+Quando si esegue un'applicazione con PM2, è possibile abilitare la modalità **cluster** per eseguirla in un cluster con un certo numero di istanze a propria scelta, come il corrispondente numero di CPU disponibili sulla macchina. È possibile modificare manualmente il numero di processi nel cluster utilizzando lo strumento da riga di comando `pm2` senza interrompere l'app.
+
+Per abilitare la modalità cluster, avvia la tua applicazione così:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+Questo può anche essere configurato all'interno di un file di processo PM2 (`ecosystem.config. s` o simile) impostando `exec_mode` su `cluster` e `instances` sul numero di lavoratori da avviare.
+
+Una volta in esecuzione, l'applicazione può essere ridimensionata così:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+Per ulteriori informazioni sul clustering con PM2, vedere [Modalità cluster](https://pm2.keymetrics.io/docs/usage/cluster-mode/) nella documentazione PM2.
+
+### Risultati richiesta cache
+
+Un'altra strategia per migliorare le prestazioni nella produzione è quella di nascondere il risultato delle richieste, in modo che l'app non ripeta l'operazione per servire la stessa richiesta ripetutamente.
+
+Usa un server di cache come [Varnish](https://www.varnish-cache.org/) o [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (vedi anche [Nginx Caching](https://serversforhackers.com/nginx-caching/)) per migliorare notevolmente la velocità e le prestazioni della tua app.
+
+### Usa un bilanciatore di carico
+
+Non importa quanto sia ottimizzata un'app, una singola istanza può gestire solo una quantità limitata di carico e traffico. Un modo per scalare un'app è quello di eseguire più istanze di esso e distribuire il traffico tramite un balancer. La configurazione di un bilanciatore di carico può migliorare le prestazioni e la velocità della tua app e permetterle di scalare più di quanto sia possibile con una singola istanza.
+
+Un bilanciatore di carico è di solito un proxy inverso che orchestra il traffico da e verso più istanze di applicazione e server. Puoi configurare facilmente un bilanciatore di carico per la tua app utilizzando [Nginx](https://nginx.org/en/docs/http/load_balancing) o [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+Con il bilanciamento del carico, potrebbe essere necessario assicurarsi che le richieste associate a un particolare ID di sessione si connettano al processo che le ha originate. Questo è conosciuto come _session affinity_, o _sticky sessions_, e può essere affrontato dal suggerimento di cui sopra per utilizzare un archivio dati come Redis per i dati di sessione (a seconda della tua applicazione). Per una discussione, vedere [Utilizzo di nodi multipli](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Usa un proxy inverso
+
+Un proxy inverso si siede davanti ad una web app ed esegue operazioni di supporto sulle richieste, oltre a dirigere le richieste verso l'app. Può gestire pagine di errore, compressione, caching, servire i file, e bilanciamento del carico tra le altre cose.
+
+Spostare le attività che non richiedono la conoscenza dello stato dell'applicazione per un proxy inverso libera Express per eseguire attività di applicazione specializzate. Per questo motivo, si raccomanda di eseguire Express dietro un proxy inverso come [Nginx](https://www.nginx.org/) o [HAProxy](https://www.haproxy.org/) in produzione.
diff --git a/src/content/pages/it/advanced/best-practice-security.mdx b/src/content/pages/it/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..dd46812c43
--- /dev/null
+++ b/src/content/pages/it/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: Migliori Pratiche Di Produzione
+description: Scopri le migliori pratiche di sicurezza fondamentali per le app Express in produzione, tra cui l'utilizzo di TLS, la convalida degli input, i cookie sicuri e la prevenzione delle vulnerabilità.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Il termine _"produzione"_ si riferisce allo stadio del ciclo di vita del software quando un'applicazione o API è generalmente disponibile per i suoi utenti finali o consumatori. Al contrario, nella fase di _"sviluppo"_ stai ancora scrivendo attivamente e testando il codice, e l'applicazione non è aperta ad accesso esterno. Gli ambienti di sistema corrispondenti sono conosciuti rispettivamente come ambienti _production_ e _development_.
+
+Gli ambienti di sviluppo e di produzione sono di solito impostati in modo diverso e hanno esigenze molto diverse. Che cosa bene in sviluppo potrebbe non essere accettabile nella produzione. Ad esempio, in un ambiente di sviluppo potresti voler registrare dettagliatamente gli errori per il debug, mentre lo stesso comportamento può diventare una preoccupazione di sicurezza in un ambiente di produzione. E nello sviluppo, non c'è bisogno di preoccuparsi di scalabilità, affidabilità e prestazioni, mentre queste preoccupazioni diventano fondamentali nella produzione.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+Le migliori pratiche di sicurezza per le applicazioni Express in produzione includono:
+
+- [Migliori Pratiche Di Produzione: Sicurezza](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Non utilizzare versioni deprecate o vulnerabili di Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Usa TLS](#use-tls)
+  - [Non fidarti dell'input dell'utente](#do-not-trust-user-input)
+    - [Previene reindirizzamenti aperti](#prevent-open-redirects)
+  - [Usa Elmet](#use-helmet)
+  - [Riduci l'impronta digitale](#reduce-fingerprinting)
+  - [Usa i cookie in modo sicuro](#use-cookies-securely)
+    - [Non utilizzare il nome predefinito del cookie di sessione](#dont-use-the-default-session-cookie-name)
+    - [Imposta opzioni di sicurezza dei cookie](#set-cookie-security-options)
+  - [Prevenire attacchi di forza brutale contro l'autorizzazione](#prevent-brute-force-attacks-against-authorization)
+  - [Assicurati che le tue dipendenze siano sicure](#ensure-your-dependencies-are-secure)
+    - [Evitare altre vulnerabilità conosciute](#avoid-other-known-vulnerabilities)
+  - [Ulteriori considerazioni](#additional-considerations)
+
+## Non utilizzare versioni deprecate o vulnerabili di Express
+
+Express 2.x e 3.x non sono più mantenuti. Problemi di sicurezza e prestazioni in queste versioni non saranno risolti. Non usarli! Se non hai spostato nella versione 4, segui la [guida alla migrazione](/en/guide/migrating-4) o prendi in considerazione [Opzioni di supporto commerciale](/en/support#commercial-support-options).
+
+Assicurati inoltre di non utilizzare nessuna delle versioni Express vulnerabili elencate nella [pagina Aggiornamenti di sicurezza](/en/advanced/security-updates). Se lo si è, aggiornare a una delle versioni stabili, preferibilmente l'ultimo.
+
+## Usa TLS
+
+Se la tua app si occupa o trasmette dati sensibili, usa [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) per proteggere la connessione e i dati. Questa tecnologia crittografa i dati prima che vengano inviati dal client al server, impedendo così alcuni hack comuni (e facili). Anche se le richieste Ajax e POST potrebbero non essere visibilmente evidenti e sembrano "nascoste" nei browser, il loro traffico di rete è vulnerabile a [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) e [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+Potresti avere familiarità con la crittografia Secure Socket Layer (SSL). [TLS è semplicemente la prossima progressione di SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). In altre parole, se si utilizza SSL prima, considerare l'aggiornamento a TLS. In generale, si consiglia Nginx per gestire TLS. Per un buon riferimento per configurare TLS su Nginx (e altri server), vedere [Configurazioni server consigliate (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Inoltre, uno strumento utile per ottenere un certificato TLS gratuito è [Let's Encrypt](https://letsencrypt.org/about/), un gratuito, automatizzato, e autorità di certificazione aperta (CA) fornite dal [Gruppo di ricerca sulla sicurezza Internet (ISRG)](https://www.abetterinternet.org/).
+
+## Non fidarti dell'input utente
+
+Per le applicazioni web, uno dei requisiti di sicurezza più critici è la convalida e la gestione dell'input dell'utente. Questo avviene in molte forme e non li copriremo tutti qui.
+In definitiva, la responsabilità di convalidare e gestire correttamente i tipi di input utente che la tua applicazione accetta è tua.
+
+### Impedisci reindirizzamenti aperti
+
+Un esempio di input utente potenzialmente pericoloso è un _open redirect_, dove un'applicazione accetta un URL come input utente (spesso nella domanda URL, ad esempio `? rl=https://esempio. om`) e utilizza `res.redirect` per impostare l'intestazione `location` e
+restituisce uno stato 3xx.
+
+Un'applicazione deve convalidare che supporta il reindirizzamento all'URL in arrivo per evitare di inviare gli utenti a link dannosi come siti web di phishing, tra gli altri rischi.
+
+Ecco un esempio di controllo degli URL prima di usare `res.redirect` o `res.location`:
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.uery.url).host !== 'example.com') {
+      return res.status(400).nd(`Redirect non supportato all'host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.tatus(400).end(`URL non valido: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Usa Elmo
+
+[Helmet][helmet] può aiutare a proteggere la tua app da alcune note vulnerabilità web impostando le intestazioni HTTP in modo appropriato.
+
+Helmet è una funzione middleware che imposta le intestazioni di risposta HTTP legate alla sicurezza. Casco imposta le seguenti intestazioni per impostazione predefinita:
+
+- `Content-Security-Policy`: Una potente lista di permessi di ciò che può accadere sulla tua pagina che attenua molti attacchi
+- `Cross-Origin-Opener-Policy`: aiuta a isolare la tua pagina
+- `Cross-Origin-Resource-Policy`: blocca gli altri dal caricamento delle risorse cross-origin
+- `Origin-Agent-Cluster`: Modifica l'isolamento del processo per essere basato sull'origine
+- `Referrer-Policy`: controlla l'intestazione [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer)
+- `Strict-Transport-Security`: Racconta i browser per preferire HTTPS
+- `X-Content-Type-Options`: Evita [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: controlla il prefetching DNS
+- `X-D<unk> ad-Options`: Forza il salvataggio dei download (solo Internet Explorer)
+- `X-Frame-Options`: intestazione legacy che attenua gli attacchi [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking)
+- `X-Permitted-Cross-Domain-Policies`: Controlla il comportamento cross-domain per i prodotti Adobe, come Acrobat
+- `X-Powered-By`: Informazioni sul server web. Rimosso perché potrebbe essere usato in semplici attacchi
+- `X-XSS-Protection`: intestazione legacy che cerca di mitigare [attacchi XSS](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), ma peggiora le cose, quindi l'Elmo lo disabilita
+
+Ogni intestazione può essere configurata o disabilitata. Per saperne di più su di esso si prega di andare su [il suo sito di documentazione][helmet].
+
+Installare Elmo come qualsiasi altro modulo:
+
+```bash
+$ npm install helmet
+```
+
+Quindi per usarlo nel tuo codice:
+
+```js
+// ...
+
+const casco = require('casco');
+app.use(casco());
+
+// ...
+```
+
+## Riduci l'impronta digitale
+
+Può aiutare a fornire un ulteriore livello di sicurezza per ridurre la capacità degli aggressori di determinare
+il software che un server utilizza, conosciuto come "impronta digitale". Anche se non un problema di sicurezza in sé,
+ridurre la capacità di impronte digitali un'applicazione migliora la sua posizione generale di sicurezza.
+Il software del server può essere improntato alle impronte digitali per quanto riguarda il modo in cui risponde a richieste specifiche, ad esempio in
+le intestazioni di risposta HTTP.
+
+Per impostazione predefinita, Express invia l'intestazione della risposta `X-Powered-By` che puoi disabilitare
+usando il metodo `app.disable()`:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="info">
+
+Disabilitare l'intestazione `X-Powered-By ` non impedisce a un sofisticato aggressore di determinare
+che un'app sta eseguendo Express. Può scoraggiare un exploit casuale, ma ci sono altri modi per
+determinare che un'app è in esecuzione Express.
+
+</Alert>
+
+Express invia anche i propri messaggi di risposta "404 Not Found" formattati e i messaggi di risposta di errore di formattazione
+. Questi possono essere modificati da
+[aggiungendo il tuo gestore non trovato](/en/starter/faq#how-do-i-handle-404-responses)
+e
+[scrivendo il tuo gestore di errore](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404). end("Siamo spiacenti non riesci a trovarlo!");
+});
+
+// app gestore di errori personalizzato
+. se((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+## Utilizzare i cookie in modo sicuro
+
+Per garantire che i cookie non aprano la tua app agli exploit, non utilizzare il nome predefinito del cookie di sessione e impostare le opzioni di sicurezza dei cookie in modo appropriato.
+
+Ci sono due principali moduli di sessione di cookie middleware:
+
+- [express-session](https://www.npmjs.com/package/express-session) che sostituisce il middleware `express.session` integrato in Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) che sostituisce il middleware `express.cookieSession` integrato in Express 3.x.
+
+La differenza principale tra questi due moduli è come salvano i dati di sessione dei cookie. La [express-session](https://www.npmjs.com/package/express-session) middleware memorizza i dati di sessione sul server; salva solo l'ID di sessione nel cookie stesso, non i dati di sessione. Per impostazione predefinita, utilizza l'archivio in-memory e non è progettato per un ambiente di produzione. Nella produzione, dovrai impostare un archivio di sessione scalabile; vedi l'elenco di [negozi di sessione compatibili](https://github.com/expressjs/session#compatible-session-stores).
+
+Al contrario, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implementa la memorizzazione supportata dai cookie: serializza l'intera sessione al cookie, piuttosto che una semplice chiave di sessione. Usalo solo quando i dati di sessione sono relativamente piccoli e facilmente codificati come valori primitivi (piuttosto che oggetti). Anche se i browser dovrebbero supportare almeno 4096 byte per cookie, per assicurarsi di non superare il limite, non superare una dimensione di 4093 byte per dominio. Inoltre, essere consapevoli che i dati dei cookie saranno visibili al cliente, quindi se c'è qualche motivo per mantenerlo sicuro o oscuro, allora `express-session` potrebbe essere una scelta migliore.
+
+### Non utilizzare il nome predefinito del cookie di sessione
+
+Utilizzando il nome predefinito del cookie di sessione puoi aprire la tua app agli attacchi. Il problema di sicurezza posto è simile a `X-Powered-By`: un potenziale attaccante può usarlo per impronte digitali il server e attacchi di destinazione di conseguenza.
+
+Per evitare questo problema, usa i nomi generici dei cookie, ad esempio usando il middleware [express-session](https://www.npmjs.com/package/express-session):
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.se(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Imposta opzioni di sicurezza cookie
+
+Impostare le seguenti opzioni di cookie per migliorare la sicurezza:
+
+- `secure` - Assicura il browser solo invia il cookie su HTTPS.
+- `httpOnly` - Assicura che il cookie venga inviato solo su HTTP(S), non su JavaScript, contribuendo a proteggere dagli attacchi di scripting cross-site.
+- `domain` - indica il dominio del cookie; usalo per confrontare con il dominio del server in cui viene richiesto l'URL. Se corrispondono, controlla l'attributo percorso successivo.
+- `path` - indica il percorso del cookie; usalo per confrontare con il percorso della richiesta. Se questo e dominio corrispondono, quindi inviare il cookie nella richiesta.
+- `expires` - usa per impostare la data di scadenza per i cookie persistenti.
+
+Ecco un esempio che usa [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.ow() + 60 * 60 * 1000); // 1 ora
+app.se(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      dominio: 'esempio. om',
+      percorso: 'foo/bar',
+      scadenza: ScadenzaData,
+    },
+  })
+);
+```
+
+## Prevenire attacchi di forza brutale contro l'autorizzazione
+
+Assicurati che gli endpoint di accesso siano protetti per rendere i dati privati più sicuri.
+
+Una tecnica semplice e potente è quella di bloccare i tentativi di autorizzazione utilizzando due metriche:
+
+1. Il numero di tentativi consecutivi falliti dallo stesso nome utente e indirizzo IP.
+2. Il numero di tentativi falliti da un indirizzo IP per un lungo periodo di tempo. Ad esempio, blocca un indirizzo IP se fa 100 tentativi falliti in un giorno.
+
+Il pacchetto [rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) fornisce strumenti per rendere questa tecnica facile e veloce. Puoi trovare [un esempio di protezione della forza brutale nella documentazione](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Assicurati che le tue dipendenze siano sicure
+
+Usare npm per gestire le dipendenze della tua applicazione è potente e conveniente. Ma i pacchetti che si utilizzano possono contenere vulnerabilità di sicurezza critiche che potrebbero influenzare anche la vostra applicazione. La sicurezza della tua app è forte solo come il "link più debole" nelle tue dipendenze.
+
+Dal momento che npm@6, npm esamina automaticamente ogni richiesta di installazione. Inoltre, puoi usare `npm audit` per analizzare il tuo albero delle dipendenze.
+
+```bash
+$ npm audit
+```
+
+Se vuoi rimanere più sicuro, considera [Snyk](https://snyk.io/).
+
+Snyk offre sia un [strumento da riga di comando](https://www.npmjs.com/package/snyk) che una [integrazione Github](https://snyk.io/docs/github) che controlla la tua applicazione contro [database di vulnerabilità open source di Snyk](https://snyk.io/vuln/) per qualsiasi vulnerabilità nota nelle tue dipendenze. Installare il CLI come segue:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Usa questo comando per testare la tua applicazione per le vulnerabilità:
+
+```bash
+$ snyk test
+```
+
+### Evitare altre vulnerabilità note
+
+Tieni d'occhio [Progetto di Sicurezza Nodi](https://npmjs.com/advisories) o [Snyk](https://snyk.io/vuln/) gli avvisi che possono influenzare Express o altri moduli che la tua app utilizza. In generale, queste banche dati sono risorse eccellenti per la conoscenza e gli strumenti sulla sicurezza del nodo.
+
+Infine, Express apps&mdash;come qualsiasi altra web app&mdash;può essere vulnerabile a una varietà di attacchi basati sul web. Conoscere se stessi con conosciute [vulnerabilità web](https://www.owasp.org/www-project-top-ten/) e prendere precauzioni per evitarli.
+
+## Considerazioni aggiuntive
+
+Ecco alcuni ulteriori consigli dall'eccellente [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Fare riferimento a quel post del blog per tutti i dettagli su queste raccomandazioni:
+
+- Filtrare e sanificare sempre l'input dell'utente per proteggere contro gli script cross-site (XSS) e gli attacchi di iniezione dei comandi.
+- Difendi gli attacchi di SQL injection utilizzando query parametrizzate o dichiarazioni preparate.
+- Usa lo strumento open-source [sqlmap](http://sqlmap.org/) per rilevare le vulnerabilità di SQL injection nella tua app.
+- Usa gli strumenti [nmap](https://nmap.org/) e [sslyze](https://github.com/nabla-c0d3/sslyze) per testare la configurazione dei tuoi cifrari SSL, chiavi, rinegoziazione e validità del certificato.
+- Usa [safe-regex](https://www.npmjs.com/package/safe-regex) per garantire che le tue espressioni regolari non siano suscettibili di [espressione regolare negazione del servizio](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacchi.
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/it/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/it/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..580db6bbdf
--- /dev/null
+++ b/src/content/pages/it/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Controlli sanitari e spegnimento grazioso
+description: Scopri come implementare controlli di salute e arresto aggraziato nelle app Express per migliorare l'affidabilità, gestire le distribuzioni e integrare con bilanciatori di carico come Kubernetes.
+---
+
+## Spegnimento grazioso
+
+Quando si distribuisce una nuova versione della propria applicazione, è necessario sostituire la versione precedente. Il gestore di processo che stai utilizzando invierà prima un segnale SIGTERM all'applicazione per notificarlo che verrà ucciso. Una volta che l'applicazione ottiene questo segnale, dovrebbe smettere di accettare nuove richieste, completare tutte le richieste in corso, pulire le risorse utilizzate, incluse le connessioni del database e i blocchi di file quindi uscire.
+
+### Esempio
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Controlli sanitari
+
+Un bilanciatore del carico utilizza controlli sanitari per determinare se un'istanza di applicazione è sana e può accettare le richieste. Ad esempio, [Kubernetes ha due controlli di salute](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, che determina quando riavviare un contenitore.
+- `pronte`, che determina quando un contenitore è pronto per iniziare ad accettare il traffico. Quando un baccello non è pronto, viene rimosso dai balanceri di carico di servizio.
diff --git a/src/content/pages/it/advanced/security-updates.mdx b/src/content/pages/it/advanced/security-updates.mdx
new file mode 100644
index 0000000000..4be10c2190
--- /dev/null
+++ b/src/content/pages/it/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Aggiornamenti di sicurezza
+description: Rivedere gli ultimi aggiornamenti e patch di sicurezza per Express.js, tra cui elenchi di vulnerabilità dettagliati per diverse versioni per aiutare a mantenere un'applicazione sicura.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="allerta">
+
+Le vulnerabilità di Node.js influenzano direttamente Express. Pertanto, tieni un orologio su Node.js
+vulnerabilità e assicurati di utilizzare l'ultima versione stabile
+di Node.js.
+
+</Alert>
+
+L'elenco di seguito elenca le vulnerabilità Express che sono state risolte nell'aggiornamento della versione specificata.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - La dipendenza `path-to-regexp` è stata aggiornata per affrontare una [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - Il `cookie` di dipendenza è stato aggiornato per indirizzare un [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), Questo può influenzare la tua applicazione se usi `res.cookie`.
+- 4.20.0
+  - Corretta vulnerabilità XSS in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - La dipendenza `serve-static` è stata aggiornata per affrontare una [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - La dipendenza `send` è stata aggiornata per indirizzare una [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - La dipendenza `path-to-regexp` è stata aggiornata per affrontare una [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - La dipendenza `body-parser` è stata aggiornata per aggiungere una [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), Questo può influenzare la tua applicazione se l'url è stato attivato .
+- 4.19.0, 4.19.1
+  - Risolto la vulnerabilità di reindirizzamento aperto in `res.location` e `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - La dipendenza `qs` è stata aggiornata per indirizzare una [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). Questo può influenzare la tua applicazione se vengono utilizzate le seguenti API: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - La dipendenza `inoltrata` è stata aggiornata per indirizzare una [vulnerability](https://npmjs.com/advisories/527). Questo può influenzare la tua applicazione se vengono utilizzate le seguenti API: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - La dipendenza `mime` è stata aggiornata per affrontare una [vulnerability](https://npmjs.com/advisories/535), ma questo problema non influisce su Express.
+  - La dipendenza `send` è stata aggiornata per fornire una protezione contro una [vulnerabilità Node.js 8.5.0](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Questo influenza solo l'esecuzione di Express sulla specifica versione di Node.js 8.5.0.
+- 4.15.5
+  - Il `debug` della dipendenza è stato aggiornato per affrontare una [vulnerability](https://snyk.io/vuln/npm:debug:20170905), ma questo problema non influisce su Express.
+  - La dipendenza `fresh` è stata aggiornata per affrontare una [vulnerability](https://npmjs.com/advisories/526). Questo influenzerà la tua applicazione se vengono utilizzate le seguenti API: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - Il `ms` di dipendenza è stato aggiornato per indirizzare un [vulnerability](https://snyk.io/vuln/npm:ms:20170412). Questo può influenzare la tua applicazione se l'input di stringa non attendibile viene passato all'opzione `maxAge` nelle seguenti API: `express.static`, `res.sendfile`, e `res.sendFile`.
+- 4.15.2
+  - La dipendenza `qs` è stata aggiornata per affrontare una [vulnerability](https://snyk.io/vuln/npm:qs:20170213), ma questo problema non influisce su Express. Aggiornare al 4.15.2 è una buona pratica, ma non è necessario per affrontare la vulnerabilità.
+- 4.11.1
+  - Risolto la vulnerabilità alla divulgazione del percorso di root in `express.static`, `res.sendfile`, e `res.sendFile`
+- 4.10.7
+  - Risolto la vulnerabilità di reindirizzamento aperto in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Vulnerabilità delle directory corrette in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 può perdere `fd`s in alcune situazioni che influenzano `express.static` e `res.sendfile`. Le richieste dannose potrebbero causare perdite di `fd`s e alla fine portare a errori `EMFILE` e il server non reattività.
+- 4.8.0
+  - Gli array sparsi che hanno indici estremamente alti nella stringa di interrogazione potrebbero causare il processo di esaurimento della memoria e crash del server.
+  - Oggetti di stringa di query estremamente annidati potrebbero causare il blocco del processo e rendere il server non reattivo temporaneamente.
+
+## 3.x
+
+<Alert type="avviso">
+**Express 3.x È END-OF-LIFE E NON È MANTENENTE LONGERI**
+
+I problemi noti e sconosciuti di sicurezza e prestazioni in 3.x non sono stati affrontati dall'ultimo aggiornamento (1 agosto 2015). Si consiglia vivamente di utilizzare l'ultima versione di Express.
+
+Se non sei in grado di aggiornare il precedente 3.x, ti preghiamo di considerare [Opzioni di Supporto Commerciale](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Risolto la vulnerabilità alla divulgazione del percorso di root in `express.static`, `res.sendfile`, e `res.sendFile`
+- 3.19.0
+  - Risolto la vulnerabilità di reindirizzamento aperto in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Vulnerabilità delle directory corrette in `express.static`.
+- 3.16.6
+  - Node.js 0.10 può perdere `fd`s in alcune situazioni che influenzano `express.static` e `res.sendfile`. Le richieste dannose potrebbero causare perdite di `fd`s e alla fine portare a errori `EMFILE` e il server non reattività.
+- 3.16.0
+  - Gli array sparsi che hanno indici estremamente alti nella stringa di query potrebbero causare il processo di esaurimento della memoria e crash del server.
+  - Oggetti di stringa di query estremamente annidati potrebbero causare il blocco del processo e rendere il server non reattivo temporaneamente.
+- 3.3.0
+  - La risposta 404 di un tentativo di override metodo non supportato era suscettibile di attacchi di scripting cross-site.
diff --git a/src/content/pages/it/guide/database-integration.mdx b/src/content/pages/it/guide/database-integration.mdx
new file mode 100644
index 0000000000..ebef257425
--- /dev/null
+++ b/src/content/pages/it/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Integrazione database
+description: Scopri come integrare vari database con le applicazioni Express.js, inclusi esempi di configurazione per MongoDB, MySQL, PostgreSQL e altro ancora.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Aggiungere la possibilità di collegare i database alle applicazioni Express è solo una questione di caricare un driver Node.js appropriato per il database nella tua app. Questo documento spiega brevemente come aggiungere e utilizzare alcuni dei moduli Node.js più popolari per i sistemi di database nell'app Express:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="allerta">
+
+Questi driver di database sono tra molti che sono disponibili. Per altre opzioni, cerca sul sito
+[npm](https://www.npmjs.com/).
+
+</Alert>
+
+## Cassandra
+
+**Modulo**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installazione
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Esempio
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.xecute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Modulo**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Installazione
+
+```bash
+$ npm install couchbase
+```
+
+### Esempio
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// aggiungi un documento a un bucket
+. nsert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console. og(result);
+  }
+});
+
+// ottieni tutti i documenti con scarpa taglia 13
+const n1ql = 'SELECT d. FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery. romString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Modulo**: [nano](https://github.com/dscape/nano)
+
+### Installazione
+
+```bash
+$ npm install nano
+```
+
+### Esempio
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db. se('books');
+
+// Inserisci un documento di libro nel database di libri
+. nsert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console. og(body);
+  }
+});
+
+// Ottieni un elenco di tutti i libri
+libri. ist((err, body) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Modulo**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Installazione
+
+```bash
+$ npm install level levelup down
+```
+
+### Esempio
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.ut('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.et('name', (err, value) => {
+    if (err) return console.og('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Modulo**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Installazione
+
+```bash
+$ npm install mysql
+```
+
+### Esempio
+
+```js
+const mysql = require('mysql');
+const connection = mysql.reateConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connessione.onnect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.og('La soluzione è: ', righe[0].solution);
+});
+
+connessione.end();
+```
+
+## MongoDB
+
+**Modulo**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installazione
+
+```bash
+$ npm install mongodb
+```
+
+### Esempio (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.ollection('mammals')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(risultato);
+    });
+});
+```
+
+### Esempio (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.b('animals');
+
+  db.collection('mammals')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(risultato);
+    });
+});
+```
+
+Se vuoi un driver modello oggetto per MongoDB, guarda [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Modulo**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installazione
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Esempio
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.asic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .un('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].et('count'));
+    })
+    .catch((error) => {
+      console.og(errore);
+    });
+});
+```
+
+## Oracle
+
+**Modulo**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installazione
+
+NOTA: [Vedi i prerequisiti di installazione](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Esempio
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  utente: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb. etConnection(config);
+
+    const result = await conn. xecute('select * from employees where employee_id = :id', [empId]);
+
+    console. og(result.rows[0]);
+  } catch (err) {
+    console. og('Ouch! , err);
+  } finalmente {
+    if (conn) {
+      // conn assignment worked, bisogno di chiudere
+      attesa conn. lose();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Modulo**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installazione
+
+```bash
+$ npm install pg-promise
+```
+
+### Esempio
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .hen((data) => {
+    console.log('DATA:', data.value);
+  })
+  .atch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Modulo**: [redis](https://github.com/mranney/node_redis)
+
+### Installazione
+
+```bash
+$ npm install redis
+```
+
+### Esempio
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.et('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.set(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.keys('hash key', (err, replies) => {
+  console.log(`${replies.length} risponde:`);
+
+  risposte.orEach((reply, i) => {
+    console.og(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## Server SQL
+
+**Modulo**: [tedious](https://github.com/tediousjs/tedious)
+
+### Installazione
+
+```bash
+$ npm install tedious
+```
+
+### Esempio
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious'). ricerca;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // aggiorna la password
+      : 'tuo_password', // aggiornami
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connessione. n('connect', (err) => {
+  if (err) {
+    console. og(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hello world'", (err, rowCount) => {
+    if (err) {
+      console. og(err);
+    } else {
+      console. og(`${rowCount} righe`);
+    }
+    connessione. lose();
+  });
+
+  request.on('row', (columns) => {
+    colonne. orEach((column) => {
+      if (column.value === null) {
+        console. og('NULL');
+      } else {
+        console.log(column. alue);
+      }
+    });
+  });
+
+  connessione.execSql(request);
+}
+```
+
+## SQLite
+
+**Modulo**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installazione
+
+```bash
+$ npm install sqlite3
+```
+
+### Esempio
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.un('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.repare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.un(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.ach('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.og(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Modulo**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installazione
+
+```bash
+$ npm install elasticsearch
+```
+
+### Esempio
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .earch({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          campi: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .hen(
+    (response) => {
+      const hits = response.hits.its;
+    },
+    (error) => {
+      console.gara(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/it/guide/migrating-4.mdx b/src/content/pages/it/guide/migrating-4.mdx
new file mode 100644
index 0000000000..c1d451904a
--- /dev/null
+++ b/src/content/pages/it/guide/migrating-4.mdx
@@ -0,0 +1,667 @@
+---
+title: Passaggio a Express 4
+description: Una guida per la migrazione delle applicazioni Express.js dalla versione 3 alla 4, che copre i cambiamenti nel middleware, nel routing, e come aggiornare il codice in modo efficace.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 è un cambiamento di rottura rispetto a Express 3. Ciò significa che un'app Express 3 esistente non funzionerà\_ se aggiorni la versione Express nelle sue dipendenze.
+
+Questo articolo comprende:
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Changes in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">Un esempio</a> di migrazione di un'app Express 3 per Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Aggiornamento al generatore di app Express 4</a>.
+  </li>
+</ul>
+
+## Modifiche in Express 4
+
+Nel documento Express 4 sono stati apportati diversi cambiamenti significativi:
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Change to Express core and middleware system.</a> Le dipendenze da
+    Connect e built-in middleware sono state rimosse, quindi è necessario aggiungere middleware da
+    soli.
+  </li>
+  <li>
+    <a href="#routing">Modifiche al sistema di routing.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Vari altri cambiamenti.</a>
+  </li>
+</ul>
+
+Cfr. anche:
+
+- [Nuove funzionalità in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrazione da 3.x a 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Modifiche al sistema Express core e middleware
+
+Express 4 non dipende più da Connect, e rimuove tutti i middleware
+incorporati dal suo core, ad eccezione della funzione `express.static`. Ciò significa che
+Express è ora un routing indipendente e un framework web middleware, e il versionamento e le versioni di
+Express non sono influenzati dagli aggiornamenti di middleware.
+
+Senza middleware integrato, è necessario aggiungere esplicitamente tutto il middleware
+che è necessario per eseguire l'app. Basta seguire questi passaggi:
+
+1. Installa il modulo: `npm install --save <module-name>`
+2. Nella tua app, richiede il modulo: `require('module-name')`
+3. Usa il modulo in base alla sua documentazione: `app.use( ... )`
+
+La seguente tabella elenca il middleware Express 3 e le loro controparti in Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      Compressione <a href="https://github.com/expressjs/compression" />
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">cookie-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">cookie-parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">tempo di risposta</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">method-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">connect-timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">servo-statico</a>
+    </td>
+  </tr>
+</table>
+
+Ecco la [lista completa](https://github.com/senchalabs/connect#middleware) di Express 4 middleware.
+
+Nella maggior parte dei casi, puoi semplicemente sostituire la vecchia versione 3 middleware con
+la sua controparte Express 4. Per i dettagli, vedere la documentazione del modulo in
+GitHub.
+
+#### `app.use` accetta parametri
+
+Nella versione 4 è possibile utilizzare un parametro variabile per definire il percorso in cui vengono caricate le funzioni middleware, quindi leggere il valore del parametro dal gestore del percorso.
+Per esempio:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### Il sistema di routing
+
+Le app ora caricano implicitamente il middleware di routing, quindi non devi più preoccuparti di
+dell'ordine in cui il middleware viene caricato rispetto a
+il middleware `router`.
+
+Il modo in cui definisci i percorsi non è cambiato, ma il sistema di routing ha due
+nuove funzionalità per aiutare a organizzare i tuoi percorsi:
+
+- Un nuovo metodo, `app.route()`, per creare i gestori di rotte per un percorso tracciato.
+- Una nuova classe, `express.Router`, per creare percorsi modulari montabili.
+
+#### `app.route()` metodo
+
+Il nuovo metodo `app.route()` ti permette di creare i gestori di rotte
+per un percorso percorso. Poiché il percorso è specificato in una singola posizione, è utile creare percorsi modulari, così come ridurre la ridondanza e pneumatici. Per ulteriori informazioni
+sulle rotte, vedere [`Router()` documentazione](/en/4x/api#router).
+
+Ecco un esempio di router incatenati che sono definiti utilizzando la funzione `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Ottieni un libro casuale');
+  })
+  .ost((req, res) => {
+    res.send('Add a book');
+  })
+  .ut((req, res) => {
+    res.send('Aggiorna il libro');
+  });
+```
+
+#### Classe `express.Router`
+
+L'altra funzione che aiuta a organizzare i percorsi è una nuova classe,
+`express.Router`, che puoi usare per creare percorsi modulari montabili
+. Un'istanza `Router` è un sistema completo di routing middleware e
+; per questo motivo è spesso chiamata "mini-app".
+
+L'esempio seguente crea un router come modulo, carica middleware in
+, definisce alcuni percorsi e lo monta su un percorso sull'app principale.
+
+Ad esempio, crea un file router chiamato `birds.js` nella directory app,
+con i seguenti contenuti:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specifico per questo router
+router. se((req, res, next) => {
+  console.log('Time: ', Date. ow());
+  next();
+});
+// definire il router della home page
+. et('/', (req, res) => {
+  res.send('Birds home page');
+});
+// definire il router circa il percorso
+. et('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Quindi, caricare il modulo router nell'app:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+L'app sarà ora in grado di gestire le richieste ai percorsi `/birds` e
+`/birds/about`, e chiamerà il middleware `timeLog`
+che è specifico per il percorso.
+
+### Altre modifiche
+
+La seguente tabella elenca altre modifiche di piccole dimensioni ma importanti in Express 4:
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Oggetto</th>
+    <th>Descrizione</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>
+      Express 4 richiede Node.js 0.10.x o versioni successive e ha abbandonato il supporto per
+      Node.js 0.8.x.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      Il modulo `http` non è più necessario, a meno che non sia necessario lavorare direttamente con
+      esso (socket.io/SPDY/HTTPS). L'app può essere avviata utilizzando la funzione `app.listen()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      La funzione `app.configure()` è stata rimossa. Usa la funzione `process.env.NODE_ENV` o
+      `app.get('env')` per rilevare l'ambiente e configurare l'app di conseguenza.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      La proprietà dell'applicazione `json spaces` è disabilitata per impostazione predefinita in
+      Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Usa `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, and
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">Non risolve più gli URL relativi.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">È stato un array; ora un oggetto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Era una funzione; ora un oggetto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Cambiato in `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Ora disponibile come `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">rimosso.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">rimosso.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      La funzionalità è ora limitata all'impostazione del valore di base dei cookie. Usa
+      `res.cookie()` per le funzionalità aggiunte.
+    </td>
+  </tr>
+</table>
+
+## Migrazione ad esempio app
+
+Ecco un esempio di migrazione di un'applicazione Express 3 per Express 4.
+I file di interesse sono `app.js` e `package.json`.
+
+### Versione 3 app
+
+#### `app.js`
+
+Considera un'applicazione Express v.3 con il seguente file `app.js`:
+
+```js
+var express = require('express');
+var route = require('./routes');
+var user = require('. routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// tutti gli ambienti
+app. et('port', process.env.PORT <unk> <unk> 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express. ession({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express. tatic(path.join(__dirname, 'public')));
+
+// sviluppo solo
+if (app.get('env') === 'development') {
+  app. se(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http. reateServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+Il file `package.json` che accompagna la versione 3 potrebbe sembrare
+qualcosa del genere:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dependencies": {
+    "express": "3. 2.0",
+    "pug": "*"
+  }
+}
+```
+
+### Processo
+
+Inizia il processo di migrazione installando il middleware richiesto per l'app
+Express 4 e aggiornando Express e Pug alla rispettiva versione
+con il seguente comando:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Effettuare le seguenti modifiche a `app.js`:
+
+1. Le funzioni integrate di Express middleware `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` e
+   `express.errorHandler` non sono più disponibili nell'oggetto `express`
+   . Devi installare manualmente le loro alternative
+   e caricarle nell'app.
+
+2. Non è più necessario caricare la funzione `app.router`.
+   Non è un valido oggetto app Express 4, quindi rimuovi il codice
+   `app.use(app.router);`.
+
+3. Assicurati che le funzioni middleware siano caricate nell'ordine corretto: carica `errorHandler` dopo aver caricato le rotte dell'app.
+
+### Versione 4 app
+
+#### `package.json`
+
+L'esecuzione del comando `npm` sopra aggiornerà `package.json` come segue:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. s"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1. ",
+    "express": "^4.8.0",
+    "express-session": "^1. .2",
+    "pug": "^2.0.0",
+    "method-override": "^2. .2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1. ",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Quindi, rimuovere il codice non valido, caricare il middleware richiesto e fare altre modifiche
+se necessario. Il file `app.js` sarà simile a questo:
+
+```js
+var http = require('http');
+var express = require('express');
+var route = require('./routes');
+var user = require('. routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// tutti gli ambienti
+app. et('port', process.env.PORT <unk> <unk> 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico'));
+app.use(logger('dev'));
+app. se(methodOverride());
+app. se(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    segreto: 'uwotm8',
+  })
+);
+app. se(bodyParser.json());
+app.use(bodyParser.urlencoded({ extened: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes. ndex);
+app.get('/users', user.list);
+
+// la gestione degli errori middleware dovrebbe essere caricata dopo il caricamento delle rotte
+se (app. et('env') === 'development') {
+  app. se(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app. et('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+A meno che non sia necessario lavorare direttamente con il modulo `http` (socket.io/SPDY/HTTPS), il caricamento non è richiesto e l'applicazione può essere semplicemente avviata in questo modo:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Esegui l'app
+
+Il processo di migrazione è completo, e l'app è ora un'app
+Express 4. Per confermare, avviare l'applicazione utilizzando il seguente comando:
+
+```bash
+$ node .
+```
+
+Carica [http://localhost:3000](http://localhost:3000)
+e vedi che la home page è resa da Express 4.
+
+## Aggiornamento al generatore di app Express 4
+
+The command-line tool to generate an Express app is still
+`express`, but to upgrade to the new version, you must uninstall
+the Express 3 app generator and then install the new
+`express-generator`.
+
+### Installazione
+
+Se hai già installato il generatore di app Express 3 sul tuo sistema,
+devi disinstallarlo:
+
+```bash
+$ npm uninstall -g express
+```
+
+A seconda di come i privilegi di file e directory sono configurati,
+potrebbe essere necessario eseguire questo comando con `sudo`.
+
+Ora installa il nuovo generatore:
+
+```bash
+$ npm install -g express-generator
+```
+
+A seconda di come i privilegi di file e directory sono configurati,
+potrebbe essere necessario eseguire questo comando con `sudo`.
+
+Ora il comando `express` sul tuo sistema viene aggiornato al generatore
+Express 4.
+
+### Modifiche al generatore di app
+
+Le opzioni di comando e l'uso restano in gran parte uguali, con le seguenti eccezioni:
+
+- Rimosso l'opzione `--sessions`.
+- Rimosso l'opzione `--jshtml`.
+- Aggiunta l'opzione `--hogan` per supportare [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Esempio
+
+Esegue il seguente comando per creare un'app Express 4:
+
+```bash
+$ express app4
+```
+
+Se si guarda il contenuto del file `app4/app.js`, si noterà
+che tutte le funzioni middleware (tranne `express. tatic`) che sono richiesti per
+l'applicazione sono caricati come moduli indipendenti, e il 'router' middleware
+non è più esplicitamente caricato nell'app.
+
+Noterai anche che il file `app.js` è ora un Node. s modulo, in contrasto con l'app standalone che è stata generata dal vecchio generatore.
+
+Dopo aver installato le dipendenze, avviare l'applicazione utilizzando il seguente comando:
+
+```bash
+$ npm start
+```
+
+Se guardi lo script `npm start` nel `package. file son`,
+noterai che il comando attuale che avvia l'app è
+`node . bin/www`, che era `node app.js`
+in Express 3.
+
+Poiché il file `app.js` generato dal generatore di Express 4
+è ora un Node. s modulo, non può più essere avviato indipendentemente come app
+(a meno che tu non modifichi il codice). Il modulo deve essere caricato in un file Node.js
+e avviato tramite il file Node.js. Il file Node.js è `./bin/www`
+in questo caso.
+
+Né la directory `bin` né il file `www`
+extensionless sono obbligatori per creare un'app Express o per avviare l'app. Sono
+solo suggerimenti fatti dal generatore, quindi sentitevi liberi di modificarli per soddisfare le vostre esigenze
+.
+
+To get rid of the `www` directory and keep things the "Express 3 way",
+delete the line that says `module.exports = app;` at the end of the
+`app.js` file, then paste the following code in its place:
+
+```js
+app.set('port', process.env.PORT <unk> <unk> 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+Assicurati di caricare il modulo `debug` nella parte superiore del file `app.js` utilizzando il seguente codice:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Successivamente, cambia `"start": "node ./bin/www"` nel file `package.json` in `"start": "node app.js"`.
+
+Ora hai spostato la funzionalità di `./bin/www` di nuovo in
+`app.js`. Questo cambiamento non è raccomandato, ma l'esercizio ti aiuta
+a capire come `. bin/www` funziona e perché il file `app.js`
+non inizia più da solo.
diff --git a/src/content/pages/it/guide/migrating-5.mdx b/src/content/pages/it/guide/migrating-5.mdx
new file mode 100644
index 0000000000..3dda509552
--- /dev/null
+++ b/src/content/pages/it/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Passaggio a Express 5
+description: Una guida completa per la migrazione delle applicazioni Express.js dalla versione 4 alla 5, che descrive in dettaglio i cambiamenti di rottura, i metodi deprecati e i nuovi miglioramenti.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 non è molto diverso da Express 4; anche se mantiene la stessa API di base, ci sono ancora cambiamenti che rompono la compatibilità con la versione precedente. Pertanto, un'applicazione costruita con Express 4 potrebbe non funzionare se lo si aggiorna per utilizzare Express 5.
+
+Per installare questa versione, è necessario avere una versione 18 o superiore. Quindi, esegui il seguente comando nella directory dell'applicazione:
+
+```sh
+npm install "express@5"
+```
+
+È quindi possibile eseguire i test automatici per vedere cosa non funziona, e risolvere i problemi in base agli aggiornamenti elencati di seguito. Dopo aver affrontato i fallimenti di test, eseguire l'app per vedere quali errori si verificano. Scoprirai subito se l'app utilizza metodi o proprietà che non sono supportati.
+
+## Express 5 Codemods
+
+Per aiutarti a migrare il tuo server espresso, abbiamo creato un set di codemods che ti aiuterà ad aggiornare automaticamente il tuo codice all'ultima versione di Express.
+
+Eseguire il seguente comando per eseguire tutte le codemods disponibili:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-ricetta
+```
+
+Se si desidera eseguire un codice specifico, è possibile eseguire il seguente comando:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+Puoi trovare la lista dei codici disponibili [here](https://codemod.link/express).
+
+## Modifiche in Express 5
+
+**Metodi e proprietà rimosse**
+
+<ul class="doclist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Nomi metodo pluralizzato</a>
+  </li>
+  <li>
+    <a href="#leading">Leading colon in name argument to app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(nome)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') and res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:log di debug router</a>
+  </li>
+</ul>
+
+**Modificato**
+
+<ul class="doclist">
+  <li>
+    <a href="#path-syntax">Percorso percorso corrispondente alla sintassi</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">Promesse respinte gestite da middleware e gestori</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Miglioramenti**
+
+<ul class="doclist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    Supporto di codifica <a href="#brotli-support">Brotli</a>
+  </li>
+</ul>
+
+## Metodi e proprietà rimossi
+
+Se si utilizza uno qualsiasi di questi metodi o proprietà nella tua app, si bloccherà. Quindi, avrai bisogno di cambiare la tua app dopo l'aggiornamento alla versione 5.
+
+### app.del()
+
+Express 5 non supporta più la funzione `app.del()`. Se si utilizza questa funzione, viene generato un errore. Per registrare i percorsi HTTP DELETE, utilizza invece la funzione `app.delete()`.
+
+Inizialmente, `del` è stato usato invece di `delete`, perché `delete` è una parola chiave riservata in JavaScript. Tuttavia, come ECMAScript 6, `delete` e altre parole chiave riservate possono essere legalmente utilizzati come nomi di proprietà.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.elete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+La firma `app.param(fn)` è stata usata per modificare il comportamento della funzione `app.param(name, fn)`. È stato deprecato dal v4.11.0, e Express 5 non lo supporta più.
+
+### Nomi dei metodi pluralizzati
+
+I seguenti nomi di metodo sono stati pluralizzati. In Express 4, utilizzando i vecchi metodi ha prodotto un avvertimento di deprecazione. Express 5 non li supporta più:
+
+`req.acceptsCharset()` è sostituito da `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` è sostituito da `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` è sostituito da `req.acceptsLanguages()`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.cceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.ll('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### Colon iniziale (:) nel nome di app.param(name, fn)
+
+Un carattere principale (:) nel nome della `app. aram(name, fn)` function is a remnant of Express 3, and for the sake of backwards compatity, Express 4 supported it with a deprecation notice. Express 5 lo ignorerà silenziosamente e userà il parametro del nome senza prefissarlo con un colon.
+
+Questo non dovrebbe influenzare il tuo codice se segui la documentazione Express 4 di [app.param](/en/4x/api#app.param), in quanto non fa alcuna menzione del colon principale.
+
+### req.param(nome)
+
+Questo metodo potenzialmente confuso e pericoloso di recupero dei dati del modulo è stato rimosso. Ora dovrai cercare in modo specifico il nome del parametro inviato nell'oggetto `req.params`, `req.body`, o `req.query`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.aram('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.d;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, status)
+
+Express 5 non supporta più la firma `res.json(obj, status)`. Invece, impostare lo stato e poi catena il metodo `res.json()` così: `res.status(status).json(obj)`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 non supporta più la firma `res.jsonp(obj, status)`. Invece, impostare lo stato e poi catena il metodo `res.jsonp()` così: `res.status(status).jsonp(obj)`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.ost('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Express 5 non supporta più la firma `res.redirect(url, status)`. Invece, utilizzare la seguente firma: `res.redirect(status, url)`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') e res.location('back')
+
+Express 5 non supporta più la stringa magica `back` nei metodi `res.redirect()` e `res.location()`. Usa invece il valore `req.get('Referrer') <unk> <unk> '/'` per reindirizzare alla pagina precedente. In Express 4, i metodi `res.redirect('back')` e `res.location('back')` sono stati deprecati.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecato
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app. et('/user', (req, res) => {
+  res.redirect(req.get('Referrer') <unk> <unk> '/');
+});
+```
+
+### res.send(body, status)
+
+Express 5 non supporta più la firma `res.send(obj, status)`. Invece, imposta lo stato e poi la catena al metodo `res.send()` così: `res.status(status).send(obj)`.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status)
+
+Express 5 non supporta più la firma `res.send(status)`, dove `status` è un numero. Invece, utilizzare `res. endStatus(statusCode)` funzione, che imposta il codice di stato dell'intestazione della risposta HTTP e invia la versione del testo del codice: "Not Found", "Errore interno del server", e così via.
+Se è necessario inviare un numero utilizzando `res. la funzione end()`, cita il numero per convertirlo in una stringa, in modo che Express non lo interpreti come un tentativo di utilizzare la vecchia firma non supportata.
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+La funzione `res.sendfile()` è stata sostituita da una versione a cassa in camme `res.sendFile()` in Express 5.
+
+**Nota:** In Express 5, `res. endFile()` utilizza il pacchetto `mime-types` per il rilevamento del tipo MIME, che restituisce diversi valori di Content-Type rispetto a Express 4 per diversi tipi di file comuni:
+
+- File JavaScript (.js): ora "text/javascript" invece di "application/javascript"
+- File JSON (.json): ora "application/json" invece di "text/json"
+- File CSS (.css): ora "text/css" invece di "text/plain"
+- File XML (.xml): ora "application/xml" invece di "text/xml"
+- File dei caratteri (.woff): ora "font/woff" invece di "application/font-woff"
+- File SVG (.svg): ora "image/svg+xml" invece di "application/svg+xml"
+
+<Alert type="info">
+È possibile sostituire le firme deprecate con il seguente comando:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+La firma `router.param(fn)` è stata utilizzata per modificare il comportamento della funzione `router.param(name, fn)`. È stato deprecato dal v4.11.0, e Express 5 non lo supporta più.
+
+### express.static.mime
+
+In Express 5, `mime` non è più una proprietà esportata del campo `static`.
+Usa il pacchetto [`mime-types`](https://github.com/jshttp/mime-types) per lavorare con i valori del tipo MIME.
+
+**Importante:** Questa modifica influisce non solo sull'uso diretto di `express.static.mime` ma anche su altri metodi Express che si basano sul rilevamento del tipo MIME, come `res.sendFile()`. I seguenti tipi di MIME sono cambiati da Express 4:
+
+- File JavaScript (.js): ora servito come "text/javascript" invece di "application/javascript"
+- File JSON (.json): ora servito come "application/json" invece di "text/json"
+- File CSS (.css): ora servito come "text/css" invece di "text/plain"
+- File HTML (): ora servito come "text/html; charset=utf-8" invece di "text/html"
+- File XML (.xml): ora servito come "application/xml" invece di "text/xml"
+- File di carattere (.woff): ora servito come "font/woff" invece di "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:router debug log
+
+In Express 5, la logica di gestione del router viene eseguita da una dipendenza. Pertanto, i log di debug
+per il router non sono più disponibili sotto lo spazio dei nomi `express:`.
+In v4, i log erano disponibili sotto i namespace `express:router`, `express:router:layer`,
+e `express:router:route`. Tutti questi sono stati inclusi nel namespace `express:*`.
+In v5.1+, i log sono disponibili sotto i namespace `router`, `router:layer`, e `router:route`.
+I log di `router:layer` e `router:route` sono inclusi nel namespace `router:*`.
+Per ottenere lo stesso dettaglio di debug quando si utilizza `express:*` in v4, utilizzare una combinazione di
+`express:*`, `router`, e `router:*`.
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,router:* node index.js
+```
+
+## Modificato
+
+### Sintassi percorso corrispondente
+
+Il percorso percorso corrispondente alla sintassi è quando una stringa viene fornita come primo parametro alle API `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, e `router.use()`. Sono state apportate le seguenti modifiche a come la stringa del percorso è abbinata a una richiesta in ingresso:
+
+- Il carattere jolly `*` deve avere un nome, corrispondente al comportamento dei parametri `:`, usa `/*splat` invece di `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="info">
+`*splat` corrisponde a qualsiasi percorso senza il percorso root. Se hai bisogno di abbinare anche il percorso radice `/`, puoi usare `/{*splat}`, avvolgendo il carattere jolly nelle graffe.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- Il carattere opzionale `?` non è più supportato, utilizza invece le graffe.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- I caratteri Regexp non sono supportati. Per esempio:
+
+```js
+app.get('/[discussion<unk> page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+dovrebbe essere modificato in:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Alcuni caratteri sono stati riservati per evitare confusione durante l'aggiornamento (`()[]?+!`), usa `\` per sfuggire a loro.
+- I nomi dei parametri ora supportano identificativi JavaScript validi, o citati come `:"this"`.
+
+### Promesse respinte gestite da middleware e gestori
+
+Richiedi middleware e gestori che restituiscono le promesse rifiutate sono ora gestiti inoltrando il valore rifiutato come `Error` alla gestione degli errori middleware. Ciò significa che usare le funzioni `async` come middleware e manipolatori sono più facili che mai. Quando un errore viene lanciato in una funzione `async` o una promessa rifiutata è `await`ed all'interno di una funzione asincrona, questi errori verranno passati al gestore degli errori come se chiamasse `next(err)`.
+
+Dettagli su come Express gestisce gli errori sono coperti nella [documentazione relativa alla gestione degli errori](/en/guide/error-handling).
+
+### express.urlencoded
+
+Il metodo `express.urlencoded` rende l'opzione `extended` `false` per impostazione predefinita.
+
+### express.static dotfiles
+
+In Express 5, l'opzione `express.static` middleware `dotfiles` ora è predefinita per `"ignore"`. Questo è un cambiamento da Express 4, dove i dotfiles sono stati serviti per impostazione predefinita. Di conseguenza, i file all'interno di una directory che inizia con un punto (`.`), come `. ell-known`, non sarà più accessibile e restituirà un errore **404 non trovato**. Questo può rompere la funzionalità che dipende dal servizio di directory a punti, come Android App Links, e Apple Universal Links.
+
+Esempio di codice di rottura:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Dopo la migrazione a Express 5, una richiesta a `/.well-known/assetlinks.json` comporterà un **404 Non Trovato**.
+
+Per risolvere questo problema, serve specifiche directory punti esplicitamente usando il file `dotes: "allow"` opzione:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+Questo approccio consente di servire in modo sicuro solo le directory punti desiderate mantenendo il comportamento sicuro predefinito per altri file dot, che rimangono inaccessibili.
+
+### app.listen
+
+In Express 5, il metodo `app.listen` richiamerà la funzione di callback fornita dall'utente (se fornita) quando il server riceve un evento di errore. In Express 4, tali errori verrebbero lanciati. Questa modifica sposta la responsabilità di gestione degli errori alla funzione di callback in Express 5. Se c'è un errore, verrà passato al callback come argomento.
+Per esempio:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Ascolto su ${JSON.stringify(server.address()}`);
+});
+```
+
+### app.router
+
+L'oggetto `app.router`, che è stato rimosso in Express 4, ha fatto una rimonta in Express 5. Nella nuova versione, questo oggetto è solo un riferimento al router base Express, a differenza di Express 3, dove un'app ha dovuto caricarla esplicitamente.
+
+### req.body
+
+La proprietà `req.body` restituisce `undefined` quando il corpo non è stato analizzato. In Express 4, restituisce `{}` per impostazione predefinita.
+
+### req.host
+
+In Express 4, la funzione `req.host` è stata eliminata in modo errato dal numero di porta se era presente. In Express 5, il numero di porta è mantenuto.
+
+### req.params
+
+L'oggetto `req.params` ora ha un **null prototipe** quando si usano i percorsi delle stringhe. Tuttavia, se il percorso è definito con un'espressione regolare, `req.params` rimane un oggetto standard con un prototipo normale. Inoltre, ci sono due importanti cambiamenti comportamentali:
+
+**I parametri Wildcard sono ora array:**
+
+I caratteri jolly (ad esempio, `/*splat`) catturano i segmenti di percorso come un array invece di una singola stringa.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.arams);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Parametri non corrispondenti sono omessi:**
+
+In Express 4, i caratteri jolly non corrispondenti erano stringhe vuote (`''`) e parametri opzionali `:` (usando `?`) avevano una chiave con valore `undefined`. In Express 5, i parametri non corrispondenti vengono completamente omessi da `req.params`.
+
+```js
+// v4: wildcard unmatched is empty string
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req. aram);
+  // => { '0': '' }
+});
+
+// v4: il param opzionale non corrisponde è l'app
+non definita. et('/:file.:ext?', (req, res) => {
+  // GET /image
+  console. ir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{. ext}', (req, res) => {
+  // GET /image
+  console.dir(req. arams);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.query
+
+La proprietà `req.query` non è più una proprietà scrivibile ed è invece un getter. Il parser di query predefinito è stato cambiato da "esteso" a "semplice".
+
+### res.clearCookie
+
+Il metodo `res.clearCookie` ignora le opzioni `maxAge` e `expires` fornite dall'utente.
+
+### res.status
+
+Il metodo `res.status` accetta solo interi nell'intervallo da `100` a `999`, seguendo il comportamento definito da Node. s, e restituisce un errore quando il codice di stato non è un numero intero.
+
+### res.vary
+
+Il file `res.vary` lancia un errore quando manca l'argomento `field`. In Express 4, se l'argomento è stato omesso, ha dato un avviso nella console
+
+## Miglioramenti
+
+### res.render()
+
+Questo metodo ora forza il comportamento asincrono per tutti i motori di visualizzazione, evitando bug causati da motori di visualizzazione che avevano un'implementazione sincrona e che violavano l'interfaccia raccomandata.
+
+### Supporto codifica Brotli
+
+Express 5 supporta la codifica Brotli per le richieste ricevute dai clienti che la supportano.
diff --git a/src/content/pages/it/resources/glossary.mdx b/src/content/pages/it/resources/glossary.mdx
new file mode 100644
index 0000000000..794a8f4393
--- /dev/null
+++ b/src/content/pages/it/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Un glossario completo di termini relativi a Express.js, Node.js, middleware, routing e altri concetti chiave per aiutarti a capire e utilizzare Express in modo efficace.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### applicazione
+
+In generale, uno o più programmi che sono progettati per effettuare operazioni per uno scopo specifico. Nel contesto di Express, un programma che utilizza l'API Express in esecuzione sulla piattaforma Node.js. Potrebbe anche fare riferimento a un [app object](/en/api#express).
+
+### API
+
+Interfaccia di programmazione applicativa. Spiega l'abbreviazione quando viene usata per la prima volta.
+
+### Espresso
+
+Un framework web veloce, non opinabile, minimalista per applicazioni Node.js. In generale, "Express" è preferito a "Express.js", anche se quest'ultimo è accettabile.
+
+### libuv
+
+Una libreria di supporto multi-piattaforma che si concentra su I/O asincrono sviluppato principalmente per l'uso da Node.js.
+
+### middleware
+
+Una funzione che viene invocata dallo strato di routing Express prima del gestore finale della richiesta, e si siede così al centro tra una richiesta grezza e il percorso finale previsto. Alcuni punti di fine terminologia intorno al middleware:
+
+- `var foo = require('middleware')` si chiama _requiring_ o _using_ un modulo Node.js. Quindi la dichiarazione `var mw = foo()` restituisce tipicamente il middleware.
+- `app.use(mw)` si chiama _aggiungendo il middleware allo stack globale di elaborazione_.
+- `app.get('/foo', mw, function (req, res) { ... })` si chiama \_aggiungendo il middleware allo stack di elaborazione "GET /foo" .
+
+### Node.js
+
+Una piattaforma software che viene utilizzata per costruire applicazioni di rete scalabili. Node.js utilizza JavaScript come linguaggio di scripting e raggiunge un elevato rendimento tramite I/O non bloccante e un ciclo di eventi a filettatura singola. Vedi [nodejs.org](https://nodejs.org/en/). **Nota di utilizzo**: Inizialmente, "Node.js," in seguito "Node".
+
+### open-source, open source
+
+Quando usato come aggettivo, ifenato; per esempio: "Questo è software open-source." Vedi [Software Open-source su Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Anche se è comune non trattenere questo termine, stiamo usando le regole standard inglesi per
+che trattiene un aggettivo composto.
+
+</Alert>
+
+### richiesta
+
+Una richiesta HTTP. Un client invia un messaggio di richiesta HTTP a un server, che restituisce una risposta. La richiesta deve utilizzare uno dei diversi [metodi di richiesta](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) come GET, POST, e così via.
+
+### risposta
+
+Una risposta HTTP. Un server restituisce un messaggio di risposta HTTP al client. La risposta contiene informazioni sullo stato di completamento della richiesta e potrebbe anche contenere contenuto richiesto nel suo corpo del messaggio.
+
+### percorso
+
+Parte di un URL che identifica una risorsa. Ad esempio, in `http://foo.com/products/id`, "/products/id" è il percorso.
+
+### router
+
+Vedi [router](/en/api#router) nel riferimento API.
diff --git a/src/content/pages/it/resources/utils.md b/src/content/pages/it/resources/utils.md
new file mode 100644
index 0000000000..b017cc6caf
--- /dev/null
+++ b/src/content/pages/it/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Utilità Express
+description: Scopri i moduli di utilità relativi a Express.js e Node.js, inclusi strumenti per cookie, protezione CSRF, analisi URL, routing e molto altro per migliorare le tue applicazioni.
+---
+
+## Funzioni di utilità Express
+
+L'organizzazione [pillarjs](https://github.com/pillarjs) GitHub contiene una serie di moduli
+per funzioni di utilità che possono essere generalmente utili.
+
+| Moduli di utilità                                              | Descrizione                                                                                                                                                                                |
+| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [cookies](https://www.npmjs.com/package/cookies)               | Ottieni e imposta i cookie HTTP(S) che possono essere firmati per evitare manomissioni, utilizzando Keygrip. Può essere utilizzato con la libreria HTTP Node.js o come middleware Express. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contiene la logica dietro la creazione e la verifica del token CSRF. Usa questo modulo per creare middleware CSRF personalizzato.                                                          |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Funzione di invocare come passo finale per rispondere alla richiesta HTTP.                                                                                                                 |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Analizza un URL con la cache.                                                                                                                                                              |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Trasforma una stringa di percorso in stile Express, come \`\`/user/:name\` in un'espressione regolare.                                                                                     |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Risolve un percorso relativo contro un percorso radice con convalida.                                                                                                                      |
+| [router](https://www.npmjs.com/package/router)                 | Semplice router in stile middleware.                                                                                                                                                       |
+| [send](https://www.npmjs.com/package/send)                     | Libreria per lo streaming di file come risposta HTTP, con supporto per risposte parziali (intervalli), negoziazione condizionale-GET ed eventi granulari.                                  |
+
+Per ulteriori moduli correlati all'HTTP di basso livello, vedere [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/it/support.md b/src/content/pages/it/support.md
new file mode 100644
index 0000000000..2a10bed63e
--- /dev/null
+++ b/src/content/pages/it/support.md
@@ -0,0 +1,23 @@
+---
+title: Supporto Versione
+description: Trova informazioni sul programma di supporto per le diverse versioni di Express.js, comprese le versioni attualmente mantenute e le politiche di fine vita.
+---
+
+È supportata solo l'ultima versione di una data linea di rilascio principale.
+
+Versioni che sono EOL (end-of-life) _may_ ricevere aggiornamenti per le vulnerabilità di sicurezza critiche, ma il team Express non offre alcuna garanzia e non prevede di affrontare o risolvere i problemi riscontrati.
+
+| Versione Maggiore      | Versione Minima Node.js | Data Inizio Supporto | Data Di Fine Supporto |
+| ---------------------- | ----------------------- | -------------------- | --------------------- |
+| [**v5.x**](/en/5x/api) | 18                      | Settembre 2024       | **in corso**          |
+| [**v4.x**](/en/4x/api) | 0.10.0                  | Aprile 2014          | **in corso**          |
+| [**v3.x**](/en/3x/api) | 0.8.0                   | Ottobre 2012         | Luglio 2015           |
+| [**v2.x**](/2x/)       | 0.4.1                   | Marzo 2011           | Luglio 2012           |
+| **v1.x**               | 0.2.0                   | Dicembre 2010        | Marzo 2011            |
+| **v0.14.x**            | 0.1.98                  | Dicembre 2010        | Dicembre 2010         |
+
+## Opzioni Di Supporto Commerciale
+
+Se non riesci ad aggiornare ad una versione supportata di Express, contatta uno dei nostri partner per ricevere aggiornamenti di sicurezza:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/ja/advanced/best-practice-performance.md b/src/content/pages/ja/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..ee1b15f619
--- /dev/null
+++ b/src/content/pages/ja/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: '生産のベストプラクティス：性能と信頼性'
+description: 実稼働中の Express アプリケーションのパフォーマンスと信頼性のベストプラクティスをご覧ください。最適なパフォーマンスを得るためのコードの最適化と環境設定を網羅しています。
+---
+
+この記事では、本番環境にデプロイされた Express アプリケーションのパフォーマンスと信頼性のベストプラクティスについて説明します。
+
+このトピックは、伝統的な開発と運営の両方にまたがる"devops"の世界にはっきりと当てはまります。 したがって、情報は以下の2つに分かれています。
+
+- コード内で行うべきこと（開発部分）：
+  - [Use gzip compression](#use-gzip-compression)
+  - [Don't use synchronous functions](#dont-use-synchronous-functions)
+  - [Do logging correctly](#do-logging-correctly)
+  - [Handle exceptions properly](#handle-exceptions-properly)
+- あなたの環境/セットアップで行うべきこと（オプスパート）：
+  - [NODE_ENV を "production"に設定] (#set-node_env-to-production)
+  - [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+  - [Run your app in a cluster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Use a load balancer](#use-a-load-balancer)
+  - [Use a reverse proxy](#use-a-reverse-proxy)
+
+## コード内でやるべきこと
+
+コードでアプリケーションのパフォーマンスを向上させるためにできることをいくつか紹介します。
+
+- [Use gzip compression](#use-gzip-compression)
+- [Don't use synchronous functions](#dont-use-synchronous-functions)
+- [Do logging correctly](#do-logging-correctly)
+- [Handle exceptions properly](#handle-exceptions-properly)
+
+### gzip 圧縮を使用する
+
+Gzip 圧縮は応答本体のサイズを大幅に減らすことができるので、ウェブアプリの速度を向上させます。 エクスプレスアプリでgzip圧縮用の [compression](https://www.npmjs.com/package/compression) ミドルウェアを使用してください。 例:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). その場合、圧縮ミドルウェアを使用する必要はありません。 Nginx で gzip 圧縮を有効にする方法については、Nginx ドキュメントの [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) を参照してください。
+
+### 同期関数を使用しない
+
+同期関数とメソッドは、実行中のプロセスを返すまで結びつけます。 同期関数への単一の呼び出しは、数マイクロ秒またはミリ秒で戻る可能性があります。 しかし、交通量の多いウェブサイトでは、これらの呼び出しはアプリのパフォーマンスを向上させ、削減します。 生産での使用を避けます。
+
+Node と多くのモジュールは同期バージョンと非同期バージョンの関数を提供しますが、本番環境では常に非同期バージョンを使用します。 同期関数を正当化できる唯一の時間は、最初の起動時です。
+
+`--trace-sync-io` コマンドラインフラグを使用すると、アプリケーションが同期 API を使用するたびに警告とスタックトレースを表示できます。 もちろん、本番環境では使用したくないのではなく、コードが本番環境で使用できるようにしてください。 詳細は [node command-line options documentation](https://nodejs.org/api/cli#cli_trace_sync_io) を参照してください。
+
+### 正しくログを行う
+
+一般的に、アプリからログを記録するには、次の2つの理由があります。デバッグとアプリアクティビティのロギング(基本的には他のすべて)です。 `console.log()` または `console.error()` を使って、ターミナルにログメッセージを出力するのが一般的です。 デスティネーションが端末やファイルの場合、[これらの関数は同期されます](https://nodejs.org/api/console#console) 別のプログラムに出力を送らない限り生産には向いていません
+
+#### デバッグ用
+
+デバッグの目的でログを記録する場合は、 `console.log()` の代わりに、 [debug](https://www.npmjs.com/package/debug) のような特別なデバッグモジュールを使用してください。 このモジュールにより、DEBUG 環境変数を使用して `console.error()` に送信されるデバッグメッセージを制御することができます。 アプリケーションを純粋に非同期に保つために、`console.error()`を別のプログラムにパイプします。 しかし、実際に本番環境でデバッグするつもりはありませんね。
+
+#### アプリのアクティビティ用
+
+アプリのアクティビティを記録している場合 (トラフィックや API コールのトラッキングなど)、コンソールを使用する代わりに。 og()\`は、 [Pino](https://www.npmjs.com/package/pino)のようなロギングライブラリを使用します。これは利用可能な最速かつ最も効率的なオプションです。
+
+### 例外を適切に処理する
+
+ノードアプリは、キャッチされていない例外に遭遇するとクラッシュします。 例外を処理せず、適切なアクションを実行すると、Express アプリがクラッシュしてオフラインになります。 If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. 幸いなことに、Expressアプリは通常、短い起動時間を持っています。 それにもかかわらず、あなたは最初の場所でクラッシュを避けたいし、それを行うには、適切な例外を処理する必要があります。
+
+すべての例外を確実に処理するには、以下の手法を使用します。
+
+- [Use try-catch](#use-try-catch)
+- [Use promises](#use-promises)
+
+これらのトピックに取り組む前に、Node/Express エラー処理の基本的な理解を持っている必要があります。すなわち、error-first コールバックの使用、およびミドルウェアのエラーの伝播です。 ノードは、非同期関数からエラーを返すために "error-first callback" 規則を使用します。 コールバック関数の最初のパラメータがエラーオブジェクトであり、続くパラメータの結果データが続きます。 エラーがないことを示すには、最初のパラメータとして null を指定します。 コールバック関数は、エラーを有意義に処理するために、error-first コールバック規約に従わなければなりません。 Express では、next() 関数を使用してミドルウェアチェーンを通じてエラーを伝播させるのがベストプラクティスです。
+
+エラー処理の基礎については、以下を参照してください。
+
+- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Try-catchを使用
+
+Try-catch は同期コードで例外をキャッチするために使用できる JavaScript 言語構造です。 例えば、以下のように JSON 解析エラーを処理するには、try-catch を使用します。
+
+ここでは、プロセスクラッシュの可能性がある例外を処理するために try-catch を使用した例を示します。
+このミドルウェア関数は、JSONオブジェクトである"params"という名前のクエリフィールドパラメータを受け取ります。
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+しかし、try-catch は同期コードでのみ動作します。 Node プラットフォームは主に (特に本番環境では) 非同期であるため、try-catch は多くの例外をキャッチしません。
+
+#### Promiseの使用
+
+`async` 関数内でエラーがスローされた場合、または `async` 関数内で rejected Promise が待機されます。 これらのエラーは、`next(err)`を呼び出すかのようにエラーハンドラに渡されます。
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+また、ミドルウェアに非同期関数を使用することもできますし、promiseが失敗した場合にルーターがエラーを処理します。例えば:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+ベストプラクティスは、できるだけサイトに近いエラーを処理することです。 これはルータで処理されていますが ミドルウェアでエラーをキャッチし、別々のエラー処理ミドルウェアに頼らずに処理するのが最善です。
+
+#### 何をしないか
+
+`unchaughtException`をリッスンするのは\_しないでください。 イベントループに戻るまで例外が発生した場合に発生します。 `uncaughtException` に対してイベントリスナーを追加すると、例外に遭遇するプロセスのデフォルトの動作が変更されます。 例外にもかかわらずこのプロセスは続けられます これはアプリがクラッシュするのを防ぐ良い方法に思えるかもしれません。 しかし、未取得の例外が危険な方法であり、推奨されていない場合、アプリを実行し続けます。 プロセスの状態は信頼できず予測不能になるからです
+
+さらに、 `uncaughtException` を使用すると、公式に [crude](https://nodejs.org/api/process#process_event_uncaughtexception) として認識されます。 ですから、 `unchaughtException` を聴くのは悪い考えです。 このため、複数のプロセスやスーパーバイザのようなものをお勧めします。クラッシュと再起動は、多くの場合、エラーから回復する最も信頼性の高い方法です。
+
+また、 [domains](https://nodejs.org/api/domain) の使用はお勧めしません。 これは一般的に問題を解決せず、非推奨のモジュールです。
+
+## 環境/設定
+
+以下は、アプリのパフォーマンスを向上させるためにシステム環境でできるいくつかのことです。
+
+- [NODE_ENV を "production"に設定] (#set-node_env-to-production)
+- [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+- [Run your app in a cluster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Use a load balancer](#use-a-load-balancer)
+- [Use a reverse proxy](#use-a-reverse-proxy)
+
+### NODE_ENV を "production" に設定
+
+NODE_ENV 環境変数は、アプリケーションが実行されている環境 (通常は開発または実装) を指定します。 パフォーマンスを向上させるためにできる最も簡単なことの一つは、NODE_ENV を `production` に設定することです。
+
+NODE_ENV を "production" に設定すると Express:
+
+- ビューテンプレートのキャッシュ。
+- CSS 拡張機能から生成された CSS ファイルをキャッシュします。
+- あまり冗長なエラーメッセージを生成します。
+
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) これを行うだけでアプリのパフォーマンスが3倍向上することができます!
+
+環境固有のコードを書く必要がある場合は、 `process.env.NODE_ENV` でNODE_ENVの値を確認できます。 環境変数の値をチェックするとパフォーマンスペナルティが発生するため、慎重に行う必要があります。
+
+開発では、通常、 `export` または `.bash_profile` ファイルを使用して、対話型シェルで環境変数を設定します。 しかし、一般的には、本番サーバーでそれを行うべきではありません。代わりに、OS の init システム (systemd) を使用します。 次のセクションでは、init システム一般の使用法についての詳細を説明します。 しかし、`NODE_ENV`を設定することはパフォーマンスにとってとても重要です(そして実行しやすいので、ここでハイライトされています)。
+
+systemdでは、ユニットファイルの中で`Environment`ディレクティブを使用します。 例:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+詳細については、[systemd 単位で環境変数を使用する](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/)を参照してください。
+
+### アプリが自動的に再起動することを確認します
+
+本番環境では、アプリケーションをオフラインにしたくありません。 つまり、アプリがクラッシュした場合とサーバー自体がクラッシュした場合の両方が再起動することを確認する必要があります。 これらのイベントのどちらも発生しないことを願っていますが、現実的には両方のイベントを次のように説明する必要があります。
+
+- プロセス・マネージャーを使用して、クラッシュしたときにアプリ(およびノード)を再起動します。
+- OS がクラッシュしたときに、OS が提供する init システムを使用して、プロセス マネージャを再起動します。 プロセス管理者なしで init システムを使用することもできます。
+
+ノードアプリケーションは、キャッチされていない例外が発生した場合にクラッシュします。 The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). しかし、フェイルセーフとして、アプリがクラッシュしたときに自動的に再起動するようにメカニズムを導入します。
+
+#### プロセス管理者を使用する
+
+開発では、コマンドラインから `node server.js` などでアプリを起動しました。 しかし、生産でこれを行うことは災害のレシピです。 アプリがクラッシュすると、再起動するまでオフラインになります。 クラッシュした場合にアプリを再起動させるには、プロセスマネージャーを使用します。 プロセス マネージャは、デプロイを容易にし、高可用性を提供し、実行時にアプリケーションを管理することができるアプリケーションの「コンテナ」です。
+
+クラッシュ時にアプリを再起動することに加え、プロセスマネージャーは以下を可能にします:
+
+- ランタイムのパフォーマンスとリソース消費に関する洞察を得ます。
+- パフォーマンスを向上させるために動的に設定を変更します。
+- 制御クラスタリング (pm2)
+
+歴史的には、 [PM2](https://github.com/Unitech/pm2) のような Node.js プロセス管理者を使用することが一般的でした。 これを行いたい場合は、ドキュメントを参照してください。 ただし、プロセス管理に init システムを使用することをお勧めします。
+
+#### init システムを使用します
+
+信頼性の次の層は、サーバーの再起動時にアプリが再起動することを確認することです。 システムはまださまざまな理由でダウンすることができます。 サーバーがクラッシュした場合にアプリが再起動するようにするには、OS に組み込まれた init システムを使用します。 今日使用されている主な init システムは [systemd](https://wiki.debian.org/systemd) です。
+
+Express アプリで init システムを使用するには、次の 2 つの方法があります。
+
+- プロセス・マネージャーでアプリを実行し、init システムを使用したサービスとしてプロセス・マネージャをインストールします。 アプリがクラッシュしたときにプロセスマネージャーがアプリを再起動し、OS の再起動時に init システムがプロセスマネージャーを再起動します。 これは推奨されるアプローチです。
+- init システムを使用して、アプリケーションを直接実行します。 これはいくらか簡単ですが、プロセスマネージャーを使用することの追加の利点を得ることはありません。
+
+##### Systemd
+
+SystemdはLinuxシステムとサービスマネージャーです。 ほとんどの主要な Linux ディストリビューションでは、systemd をデフォルトの init システムとして採用しています。
+
+systemd サービスの設定ファイルは *unit file*と呼ばれ、ファイル名は `.service` で終わります。 Nodeアプリケーションを直接管理するためのユニットファイルの例を示します。 `<angle brackets>`で囲まれたシステムとアプリの値を置き換えます。
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+systemd の詳細については、[systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit)を参照してください。
+
+### クラスターでアプリを実行
+
+マルチコアシステムでは、プロセスのクラスタを起動することで、Node アプリケーションのパフォーマンスを何度も向上させることができます。 クラスタはアプリケーションの複数のインスタンスを実行し、理想的には各 CPU コアで 1 つのインスタンスを実行し、負荷とタスクをインスタンス間で分配します。
+
+![Balancing between application instances using the cluster API](/images/clustering.png)
+
+重要: アプリケーション・インスタンスは別々のプロセスとして実行されるため、同じメモリ・スペースは共有されません。 つまり、オブジェクトはアプリの各インスタンスに対してローカルです。 したがって、アプリケーションコードで状態を維持することはできません。 ただし、 [Redis](http://redis.io/) のようなインメモリデータストアを使用してセッション関連のデータや状態を保存することができます。 この注意は、基本的には全ての形態の水平スケーリングに適用され、複数のプロセスまたは複数の物理サーバーでのクラスタリングに適用されます。
+
+クラスター化されたアプリケーションでは、ワーカープロセスは他のプロセスに影響を与えることなく個別にクラッシュする可能性があります。 パフォーマンス上の利点とは別に、アプリケーションプロセスのクラスタを実行するもう一つの理由は、障害の分離です。 ワーカープロセスがクラッシュするたびに、常にイベントをログに記録し、cluster.fork() を使用して新しいプロセスを生成するようにしてください。
+
+#### ノードのクラスタモジュールの使用
+
+ノードの [cluster module](https://nodejs.org/api/cluster) でクラスタリングが可能になりました。 これにより、マスタープロセスはワーカープロセスを生成し、ワーカー間の受信接続を分配することができます。
+
+#### PM2の使用
+
+PM2を使用してアプリケーションをデプロイする場合は、*without*アプリケーションコードを変更するクラスタリングを利用できます。 [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) を最初に確認してください。 つまり、プロセスにローカルデータは保存されません(セッション、WebSocket接続など)。
+
+PM2を使用してアプリケーションを実行する場合、**クラスタモード**を有効にして、選択した複数のインスタンスを使用してクラスタで実行できます。 例えば、マシン上の利用可能なCPU数と一致するなど。 `pm2`コマンドラインツールを使って、クラスタ内のプロセス数を手動で変更できます。
+
+クラスタモードを有効にするには、以下のようにアプリケーションを起動します。
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+これは PM2 プロセス ファイル (`ecosystem.config ) 内で設定することもできます。 `exec_mode`を`cluster`に、`instances\`を開始するワーカーの数に設定します。
+
+一度実行すると、アプリケーションは次のようにスケーリングできます。
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
+
+### キャッシュリクエストの結果
+
+本番環境のパフォーマンスを向上させるもう一つの戦略は、リクエストの結果をキャッシュすることです。 アプリが同じリクエストを繰り返し処理しないようにします。
+
+[Varnish](https://www.varnish-cache.org/) や [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) のようなキャッシュサーバーを使用して、アプリの速度とパフォーマンスを大幅に向上させます。([Nginx Caching](https://serversforhackers.com/nginx-caching/)) を参照してください。
+
+### ロードバランサーを使用
+
+どんなに最適化されたアプリであっても、1つのインスタンスは限られた負荷とトラフィックしか処理できません。 アプリを拡張する方法の1つは、アプリの複数のインスタンスを実行し、ロードバランサを介してトラフィックを分散することです。 ロードバランサを設定すると、アプリのパフォーマンスと速度が向上し、1つのインスタンスでより多くのスケールが可能になります。
+
+ロードバランサは通常、複数のアプリケーションインスタンスとサーバーとの間でトラフィックをオーケストレーションするリバースプロキシです。 アプリのロードバランサーは、 [Nginx](https://nginx.org/en/docs/http/load_balancing) または [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts) を使用して簡単に設定できます。
+
+ロードバランシングでは、特定のセッション ID に関連付けられているリクエストがそれらを起動したプロセスに接続されていることを確認する必要があります。 これは*session affinity*または*sticky sessions*として知られています。 そして、セッションデータにRedisなどのデータストアを使用するために上記の提案によって対処される場合があります(アプリケーションによって異なります)。 For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### リバースプロキシを使用
+
+リバースプロキシは Web アプリの前にあり、リクエストをアプリに指示するのとは別に、リクエストに対するサポート操作を行います。 これは、エラーページ、圧縮、キャッシュ、ファイルの提供、および他の間の負荷分散を処理することができます。
+
+アプリケーション状態の知識を必要としないタスクをリバースプロキシに引き渡すと、Express を解放して専用のアプリケーションタスクを実行できます。 このため、Express はプロダクション環境で [Nginx](https://www.nginx.org/) や [HAProxy](https://www.haproxy.org/) のようなリバースプロキシの後ろで Express を実行することをお勧めします。
diff --git a/src/content/pages/ja/advanced/best-practice-security.mdx b/src/content/pages/ja/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..eb85967ae7
--- /dev/null
+++ b/src/content/pages/ja/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: プロダクションのベストプラクティス：セキュリティ
+description: 運用中のExpressアプリのセキュリティベストプラクティス(TLSの使用、入力検証、セキュリティ保護されたCookieの使用、脆弱性の防止など)をご覧ください。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+_"production"_ という用語は、アプリケーションや API がエンドユーザーや消費者に一般的に提供されるソフトウェアのライフサイクルにおける段階を指します。 対照的に、*"development"*段階では、コードを積極的に書いたりテストしたりしており、アプリケーションは外部からのアクセスに開かれていません。 対応するシステム環境はそれぞれ _production_ と _development_ と呼ばれています。
+
+開発環境と生産環境は通常、異なる設定であり、非常に異なる要件を持っています。 開発で問題のあるものは、生産では受け入れられないかもしれません。 たとえば、開発環境では、デバッグ用のエラーの詳細なロギングを行うことができます。 同じ行動が本番環境ではセキュリティ上の懸念になることがあります 開発では拡張性、信頼性、パフォーマンスを心配する必要はありませんが、それらの懸念は生産において重要になります。
+
+<Alert type="情報">
+
+Express でセキュリティ上の脆弱性を発見したと思われる場合は、Security
+ポリシーと手順をご覧ください。
+
+</Alert>
+
+実稼働中の Express アプリケーションのセキュリティのベスト プラクティスは以下のとおりです。
+
+- [プロダクションのベストプラクティス: セキュリティ] (#production-best-practices-security)
+  - [Overview](#overview)
+  - [Expressの非推奨バージョンや脆弱バージョンを使用しないでください](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Use TLS](#use-tls)
+  - [Do not trust user input](#do-not-trust-user-input)
+    - [Prevent open redirects](#prevent-open-redirects)
+  - [Use Helmet](#use-helmet)
+  - [Reduce fingerprinting](#reduce-fingerprinting)
+  - [Use cookies securely](#use-cookies-securely)
+    - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
+    - [Set cookie security options](#set-cookie-security-options)
+  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+  - [Additional considerations](#additional-considerations)
+
+## 非推奨または脆弱なバージョンの Express を使用しない
+
+Express 2.x と 3.x はメンテナンスされなくなりました。 これらのバージョンのセキュリティとパフォーマンスの問題は修正されません。 それらを使用しないでください! If you haven't moved to version 4, follow the [migration guide](/en/guide/migrating-4) or consider [Commercial Support Options](/en/support#commercial-support-options).
+
+Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/en/advanced/security-updates). もしそうであれば、安定版リリースのいずれかにアップデートしてください。
+
+## TLS を使用
+
+機密データを扱ったり転送したりする場合は、[Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) を使用して接続とデータを保護します。 この技術は、クライアントからサーバーに送信される前にデータを暗号化し、一般的な(そして簡単な)ハッキングを防ぎます。 Ajax と POST リクエストは目に見えて明らかではなく、ブラウザーでは「非表示」に見えるかもしれません。 彼らのネットワークトラフィックは、[パケットスニッフィング](https://en.wikipedia.org/wiki/Packet_analyzer)と[man-in-the-middle攻撃](https://en.wikipedia.org/wiki/Man-in-the-middle_attack)に対して脆弱です。
+
+You may be familiar with Secure Socket Layer (SSL) encryption. [TLS は、単に SSLの次の進行である](<%3Chttps://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx%3E>)。 言い換えれば、以前SSLを使用していた場合は、TLSへのアップグレードを検討してください。 一般的に、Nginx は TLS を扱うことをお勧めします。 Nginx (および他のサーバ) で TLS を設定するための参考情報については、[推奨サーバー構成 (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations)を参照してください。
+
+Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## ユーザー入力を信頼しない
+
+Webアプリケーションの場合、最も重要なセキュリティ要件の1つは、適切なユーザー入力検証と処理です。 これは多くの形態で来て、我々はここでそれらのすべてをカバーしません。
+最終的に、アプリケーションが受け入れるユーザー入力の種類を検証し、正しく処理する責任はあなたのものです。
+
+### 開いているリダイレクトを防止
+
+潜在的に危険なユーザー入力の例は _open redirect_ です。 ここで、アプリケーションはユーザー入力としてURLを受け入れます (多くの場合、URLクエリでは、例えば`? rl=https://example. om`) `res.redirect` を使用して、 `location` ヘッダーを設定し、
+は 3xx ステータスを返します。
+
+アプリケーションは、フィッシングサイトなどの悪意のあるリンクにユーザーを送信しないように、着信URLへのリダイレクトをサポートしていることを検証する必要があります。 他のリスクの中でもね
+
+`res.redirect`または`res.location`を使用する前にURLをチェックする例を示します。
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.query.url).host !== 'example.com') {
+      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.status(400).end(`Invalid url: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## ヘルメットを使用
+
+[Helmet][helmet] は、HTTPヘッダーを適切に設定することで、よく知られているWeb脆弱性からアプリを保護するのに役立ちます。
+
+Helmet は、セキュリティ関連の HTTP レスポンスヘッダーを設定するミドルウェア機能です。 ヘルメットは、デフォルトで次のヘッダーを設定します。
+
+- `Content-Security-Policy`: 多くの攻撃を軽減するためにあなたのページで何が起こるかを許可する強力なリスト
+- `Cross-Origin-Opener-Policy`: あなたのページを分離するのに役立ちます
+- `Cross-Origin-Resource-Policy`: クロスオリジンからリソースを読み込むことをブロックします
+- `Origin-Agent-Cluster`: プロセスの分離を元ベースに変更します
+- `Referrer-Policy`: [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) ヘッダーを制御します
+- `Strict-Transport-Security`: HTTPSを好むようブラウザーに教える
+- `X-Content-Type-Options`: 回避 [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: DNS プリフェッチを制御します
+- `X-Download-Options`: 強制的にダウンロードを保存します (Internet Explorerのみ)
+- `X-Frame-Options`: [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) 攻撃を軽減する従来のヘッダー
+- `X-Permitted-Cross-Domain-Policies`: Acrobat など、Adobe 製品のクロスドメイン動作を制御します
+- `X-Powered-By`: Webサーバーに関する情報。 簡単な攻撃で使用できるため削除されました
+- `X-XSS-Protection`: [XSS アタック]（https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting）を軽減しようとするレガシーヘッダーが悪化するため、ヘルメットは無効にします
+
+各ヘッダーは、設定または無効にできます。 詳細については、[its documentation website][helmet] をご覧ください。
+
+他のモジュールと同様にヘルメットをインストール：
+
+```bash
+$ npm install helmet
+```
+
+次に、コードでそれを使用します:
+
+```js
+// ...
+
+const helt = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## フィンガープリントを減らす
+
+サーバーが使用する
+ソフトウェアを判断する攻撃者の能力を低下させるために、セキュリティの追加層を提供するのに役立ちます。 「指紋」として知られています セキュリティ問題自体ではありませんが、
+アプリケーションの指紋化能力を低下させることで、セキュリティ全体の姿勢が改善されます。
+サーバーソフトウェアは、例えば、
+HTTPレスポンスヘッダのように、特定のリクエストにどのように応答するかの癖でフィンガープリントすることができます。
+
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="情報">
+
+`X-Powered-By header` を無効にすると、洗練された攻撃者が Express を実行していることを
+判断できません。 カジュアルなエクスプロイトを妨げるかもしれませんが、アプリがExpressを実行していることを
+判断する他の方法があります。
+
+</Alert>
+
+Expressはまた、独自のフォーマットされた「404 Not Found」メッセージとフォーマッタエラー
+応答メッセージを送信します。 これらは、
+[自分の見つからないハンドラを追加する](/en/starter/faq#how-do-i-handle-404-responses)
+と
+[自分のエラーハンドラを書く](/en/guide/error-handling#writing-error-handlers): によって変更できます。
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+
+// custom error handler
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+## Cookieを安全に使用
+
+クッキーが悪用されるようにアプリを開かないようにするため、デフォルトのセッションクッキー名を使用しないでください。また、クッキーのセキュリティオプションを適切に設定してください。
+
+2つの主なミドルウェアのセッションモジュールがあります。
+
+- `express.session`ミドルウェアをExpress 3.xに置き換える[express-session](https://www.npmjs.com/package/express-session)
+- `express.cookieSession` ミドルウェアをExpress 3.xに置き換える[cookie-session](https://www.npmjs.com/package/cookie-session)
+
+これらの2つのモジュールの主な違いは、クッキーセッションデータの保存方法です。 [express-session](https://www.npmjs.com/package/express-session) ミドルウェアは、セッションデータをサーバー上に保存します。セッションIDは、セッションデータではなく、クッキー自体にのみ保存します。 デフォルトでは、インメモリストレージを使用し、本番環境用に設計されていません。 本番環境では、スケーラブルな session-store を設定する必要があります。[compatible session store](https://github.com/expressjs/session#compatible-session-stores) のリストを参照してください。
+
+対照的に、 [cookie-session](https://www.npmjs.com/package/cookie-session) middleware は、セッションキーだけではなく、セッション全体を Cookie にシリアライズします。 セッションデータが比較的小さく、(オブジェクトではなく)プリミティブ値としてエンコードしやすい場合にのみ使用してください。 ブラウザはクッキーごとに少なくとも4096バイトをサポートすることになっていますが。 制限を超えないようにするには、ドメインあたり4093バイトのサイズを超えないようにします。 また、クッキーデータがクライアントに表示されることに注意してください ですから、もしそれを安全または不明瞭に保つ理由がある場合は、 `express-session` はより良い選択かもしれません。
+
+### デフォルトのセッションクッキー名を使用しない
+
+デフォルトのセッションクッキー名を使用すると、あなたのアプリを攻撃することができます。 提起されたセキュリティ上の問題は `X-Powered-By` と似ています。潜在的な攻撃者がそれを使用してサーバーにフィンガープリントを行い、それに応じて攻撃を標的にすることができます。
+
+この問題を回避するには、ジェネリックな Cookie 名を使用してください。例えば、 [express-session](https://www.npmjs.com/package/express-session) ミドルウェアを使用してください。
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.use(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Cookie のセキュリティオプションを設定
+
+セキュリティを強化するために、次のクッキーオプションを設定します。
+
+- `secure` - HTTPS経由でのみCookieを送信できるようにします。
+- `httpOnly` - CookieがクライアントJavaScriptではなくHTTP(S)上でのみ送信されることを保証し、クロスサイトスクリプティング攻撃から保護します。
+- `domain` - Cookie のドメインを示します。URL がリクエストされているサーバーのドメインと比較するために使用します。 一致する場合は、次にパス属性を確認します。
+- `path` - クッキーのパスを示します。リクエストパスと比較するために使用します。 これとドメインが一致した場合は、リクエストにクッキーを送信します。
+- `expires` - 永続的クッキーの有効期限を設定するために使用します。
+
+[cookie-session](https://www.npmjs.com/package/cookie-session) ミドルウェアを使用した例を以下に示します。
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000); // 1 hour
+app.use(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      domain: 'example.com',
+      path: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## 承認に対するブルートフォース攻撃を防止
+
+プライベートデータをより安全にするために、ログインエンドポイントが保護されていることを確認してください。
+
+シンプルで強力な手法は、2つの指標を使用して認証試行をブロックすることです。
+
+1. 同じユーザー名とIPアドレスによる連続失敗回数。
+2. 長期間IPアドレスからの失敗回数。 たとえば、1 日で 100 回失敗した場合、IP アドレスをブロックします。
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) パッケージは、このテクニックを簡単かつ高速にするためのツールを提供します。 You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## 依存関係が安全であることを確認する
+
+npm を使用してアプリケーションの依存関係を管理するのは強力で便利です。 ただし、使用するパッケージには、アプリケーションにも影響を与える可能性のある重大なセキュリティ脆弱性が含まれている場合があります。 アプリのセキュリティは、依存関係の「最も弱いリンク」と同じくらい強力です。
+
+npm@6 以降、npm は自動的にすべてのインストール リクエストをレビューします。 また、`npm audit` を使用して依存関係のツリーを分析することもできます。
+
+```bash
+$ npm audit
+```
+
+もっと安全な場合は、 [Snyk](https://snyk.io/) を検討してください。
+
+Snyk は [コマンド ライン ツール](https://www.npmjs.com/package/snyk) と [Github 統合] (https://snyk.io/docs/github) の両方を提供しており、依存関係の既知の脆弱性についてアプリケーションを [Snyk のオープン ソース 脆弱性 データベース](https://snyk.io/vuln/) でチェックします。 CLI を以下のようにインストールします。
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+このコマンドを使用して、アプリケーションの脆弱性をテストします。
+
+```bash
+$ snyk test
+```
+
+### その他の既知の脆弱性を回避する
+
+Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. 一般的に、これらのデータベースは、Node セキュリティに関する知識とツールのための優れたリソースです。
+
+Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
+
+## その他の考慮事項
+
+優れた [Node.js セキュリティ チェックリスト](https://blog.risingstack.com/node-js-security-checklist/) からのさらなる推奨事項をいくつか紹介します。 これらの推奨事項の詳細については、そのブログ記事を参照してください。
+
+- クロスサイト・スクリプティング(XSS)やコマンドインジェクション攻撃から保護するため、常にユーザー入力をフィルタリングしてサニタイズします。
+- パラメータ化されたクエリまたは準備された文を使用してSQLインジェクション攻撃を防御します。
+- アプリケーションのSQLインジェクションの脆弱性を検出するには、オープンソースの [sqlmap](http://sqlmap.org/)ツールを使用してください。
+- SSL暗号の設定をテストするには、 [nmap](https://nmap.org/) と [sslyze](https://github.com/nabla-c0d3/sslyze) ツールを使用します。 キー、再ネゴシエーション、および証明書の有効性。
+- [safe-regex](https://www.npmjs.com/package/safe-regex) を使用して、正規表現が [正規表現 サービス妨害](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) 攻撃の影響を受けないようにしましょう。
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/ja/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/ja/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..6611117c3a
--- /dev/null
+++ b/src/content/pages/ja/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: 健康チェックと優雅な閉鎖
+description: Expressアプリケーションでヘルスチェックと優雅なシャットダウンを実装して、信頼性を高め、デプロイメントを管理し、Kubernetesのようなロードバランサと統合する方法を学びます。
+---
+
+## 優雅な停止
+
+アプリケーションの新しいバージョンをデプロイする場合は、以前のバージョンを置き換える必要があります。 使用しているプロセスマネージャーは、最初にアプリケーションにSIGTERM信号を送信し、それが終了することを通知します。 アプリケーションがこのシグナルを取得したら、新しいリクエストの受け付けを停止し、継続中のリクエストをすべて終了する必要があります。 データベース接続とファイルロックを含む、使用するリソースをクリーンアップし、終了します。
+
+### 例
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## 健康チェック
+
+ロードバランサは、ヘルスチェックを使用して、アプリケーションインスタンスが健全かどうかを判断し、リクエストを受け入れることができます。 例えば、[Kubernetes には2つのヘルスチェックがあります](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness` コンテナを再起動するタイミングを決定します。
+- コンテナがいつトラフィックを受け入れる準備ができているかを決める準備が整います。 ポッドの準備ができていない場合は、サービスロードバランサーから取り外されます。
diff --git a/src/content/pages/ja/advanced/security-updates.mdx b/src/content/pages/ja/advanced/security-updates.mdx
new file mode 100644
index 0000000000..7af30ba04f
--- /dev/null
+++ b/src/content/pages/ja/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: セキュリティの更新
+description: 様々なバージョンの脆弱性リストを含む、Express.jsの最新のセキュリティアップデートとパッチを確認し、セキュアなアプリケーションを維持します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="アラート">
+
+Node.js の脆弱性は Express に直接影響します。 そのため、Node.js
+脆弱性を監視する と最新の
+安定版の Node.js を使用していることを確認してください。
+
+</Alert>
+
+以下のリストは、指定されたバージョンアップで修正された Express の脆弱性を列挙しています。
+
+<Alert type="情報">
+
+Express でセキュリティ上の脆弱性を発見したと思われる場合は、Security
+ポリシーと手順をご覧ください。
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - 依存関係の `path-to-regexp` が [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w) に対応するように更新されました。
+- 4.21.1
+  - 依存関係の `cookie` が [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x) アドレスに更新されました。`res.cookie` を使用すると、アプリケーションに影響する可能性があります。
+- 4.20.0
+  - `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796))におけるXSSの脆弱性の修正。
+  - 依存関係の `serve-static` が [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p) に更新されました。
+  - 依存関係の `send` が [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg) に更新されました。
+  - 依存関係の `path-to-regexp` が [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j) に対応するように更新されました。
+  - 依存関係の `body-parser` が [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7) を追加するように更新されました。これはURLエンコンデーションが有効になっている場合、アプリケーションに影響する可能性があります。
+- 4.19.0, 4.19.1
+  - `res.location` と `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)のオープンリダイレクトの脆弱性を修正しました。
+- 4.17.3
+  - 依存関係の `qs` が [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp) に更新されました。 `req.query`、`req.body`、`req.param`という以下のAPIを使用すると、アプリケーションに影響を与える可能性があります。
+- 4.16.0
+  - 依存関係の `forwarded` が [vulnerability](https://npmjs.com/advisories/527) に更新されました。 以下の API が使用されている場合、アプリケーションに影響を与える可能性があります: `req.host` 、 `req.hostname` 、 `req.ips` 、 `req.protocol` 。
+  - 依存関係の `mime` が [vulnerability](https://npmjs.com/advisories/535) 宛先に更新されましたが、この問題は Express には影響しません。
+  - 依存関係の `send` が更新され、[Node.js 8.5.0 脆弱性](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/)に対する保護が提供されました。 これは、Express が特定の Node.js バージョン 8.5.0 で実行されることにのみ影響します。
+- 4.15.5
+  - 依存関係の `debug` が [vulnerability](https://snyk.io/vuln/npm:debug:20170905) アドレスに更新されましたが、この問題は Express には影響しません。
+  - 依存関係の `fresh` が [vulnerability](https://npmjs.com/advisories/526) に更新されました。 `express.static` 、 `req.fresh` 、 `res.json` 、 `res.json` 、 `res.send` 、 `res.send` 、 `res.sendFile` 、 `res.sendFile` 、 `res.sendStatus` などのAPIが使用されると、アプリケーションに影響します。
+- 4.15.3
+  - 依存関係の `ms` が [vulnerability](https://snyk.io/vuln/npm:ms:20170412) に更新されました。 信頼されていない文字列が次の API で `maxAge` オプションに渡されると、アプリケーションに影響を与える可能性があります。`express.static` 、 `res.sendfile` 、 `res.sendFile` です。
+- 4.15.2
+  - 依存関係`qs`が [vulnerability]（https://snyk.io/vuln/npm:qs:20170213）アドレスに更新されましたが、この問題はExpressには影響しません。 4.15.2 へのアップデートは良い方法ですが、脆弱性に対処する必要はありません。
+- 4.11.1
+  - `express.static`、`res.sendfile`、`res.sendFile`におけるルートパス開示の脆弱性を修正しました。
+- 4.10.7
+  - `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)のオープンリダイレクトの脆弱性を修正しました。
+- 4.8.8
+  - `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)のディレクトリトラバーサルの脆弱性を修正しました。
+- 4.8.4
+  - Node.js 0.10 は、`express.static` と `res.sendfile` に影響を与える特定の状況で `fd` をリークできます。 悪意のある要求は`fd`がリークし、最終的には`EMFILE`エラーとサーバーの応答性が低下する可能性があります。
+- 4.8.0
+  - クエリ文字列に非常に高いインデックスを持つ疎行列は、プロセスがメモリ不足になり、サーバーがクラッシュする可能性があります。
+  - 非常にネストされたクエリ文字列オブジェクトは、プロセスをブロックし、サーバーが一時的に応答しないようにする可能性があります。
+
+## 3.x
+
+<Alert type="警告">
+**エクスプレス 3.x is END-OF-LIFE and no longer maintained**
+
+3.x における既知のセキュリティとパフォーマンスの問題は、前回のアップデート(2015年8月1日)から解決されていません。 最新版のExpressをご利用いただくことを強くお勧めします。
+
+3.x以降のアップグレードができない場合は、[Commercial Support Options](/en/support#commercial-support-options)をご検討ください。
+
+</Alert>
+
+- 3.19.1
+  - `express.static`、`res.sendfile`、`res.sendFile`におけるルートパス開示の脆弱性を修正しました。
+- 3.19.0
+  - `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)のオープンリダイレクトの脆弱性を修正しました。
+- 3.16.10
+  - `express.static`におけるディレクトリトラバーサルの脆弱性を修正しました。
+- 3.16.6
+  - Node.js 0.10 は、`express.static` と `res.sendfile` に影響を与える特定の状況で `fd` をリークできます。 悪意のある要求は`fd`がリークし、最終的には`EMFILE`エラーとサーバーの応答性が低下する可能性があります。
+- 3.16.0
+  - クエリ文字列のインデックスが非常に高いスパース配列は、プロセスがメモリ不足になり、サーバーがクラッシュする可能性があります。
+  - 非常にネストされたクエリ文字列オブジェクトは、プロセスをブロックし、サーバーが一時的に応答しないようにする可能性があります。
+- 3.3.0
+  - サポートされていないメソッドのオーバーライドを試みた 404 応答は、クロスサイトスクリプティング攻撃の影響を受けやすくなりました。
diff --git a/src/content/pages/ja/guide/database-integration.mdx b/src/content/pages/ja/guide/database-integration.mdx
new file mode 100644
index 0000000000..288e0fc5c0
--- /dev/null
+++ b/src/content/pages/ja/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: データベースの統合
+description: MongoDB、MySQL、PostgreSQLなどのセットアップ例を含む、様々なデータベースを Express.js アプリケーションに統合する方法をご覧ください。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Expressアプリケーションにデータベースを接続する機能を追加することは、アプリケーション内のデータベースに適切なNode.jsドライバをロードするだけです。 このドキュメントでは、Express アプリケーションで最も人気のある Node.js モジュールのいくつかを追加して使用する方法を簡単に説明します。
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="アラート">
+
+これらのデータベースドライバは、利用可能な多くの中にあります。 その他のオプションについては、
+[npm](https://www.npmjs.com/) サイトを検索してください。
+
+</Alert>
+
+## Cassandra
+
+**モジュール**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### インストール
+
+```bash
+$ npm install cassandra-driver
+```
+
+### 例
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.execute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**モジュール**: [couchnode](https://github.com/couchbase/couchnode)
+
+### インストール
+
+```bash
+$ npm install couchbase
+```
+
+### 例
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// add a document to a bucket
+bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+
+// get all documents with shoe size 13
+const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery.fromString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**モジュール**: [nano](https://github.com/dscape/nano)
+
+### インストール
+
+```bash
+$ npm install nano
+```
+
+### 例
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.use('books');
+
+// Insert a book document in the books database
+books.insert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body);
+  }
+});
+
+// Get a list of all books
+books.list((err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**モジュール**: [levelup](https://github.com/rvagg/node-levelup)
+
+### インストール
+
+```bash
+$ npm install level levelup leveldown
+```
+
+### 例
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.put('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.get('name', (err, value) => {
+    if (err) return console.log('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**モジュール**: [mysql](https://github.com/felixge/node-mysql/)
+
+### インストール
+
+```bash
+$ npm install mysql
+```
+
+### 例
+
+```js
+const mysql = require('mysql');
+const connection = mysql.createConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connection.connect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.log('The solution is: ', rows[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**モジュール**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### インストール
+
+```bash
+$ npm install mongodb
+```
+
+### 例 (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+### 例 (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.db('animals');
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+MongoDB用のオブジェクトモデルドライバが必要な場合は、 [Mongoose](https://github.com/LearnBoost/mongoose) を参照してください。
+
+## Neo4j
+
+**モジュール**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### インストール
+
+```bash
+$ npm install neo4j-driver
+```
+
+### 例
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .run('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].get('count'));
+    })
+    .catch((error) => {
+      console.log(error);
+    });
+});
+```
+
+## Oracle
+
+**モジュール**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### インストール
+
+注意: [インストール前提条件を参照](https://github.com/oracle/node-oracledb#-installation)。
+
+```bash
+$ npm install oracledb
+```
+
+### 例
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb.getConnection(config);
+
+    const result = await conn.execute('select * from employees where employee_id = :id', [empId]);
+
+    console.log(result.rows[0]);
+  } catch (err) {
+    console.log('Ouch!', err);
+  } finally {
+    if (conn) {
+      // conn assignment worked, need to close
+      await conn.close();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**モジュール**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### インストール
+
+```bash
+$ npm install pg-promise
+```
+
+### 例
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .then((data) => {
+    console.log('DATA:', data.value);
+  })
+  .catch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**モジュール**: [redis](https://github.com/mranney/node_redis)
+
+### インストール
+
+```bash
+$ npm install redis
+```
+
+### 例
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.set('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.hkeys('hash key', (err, replies) => {
+  console.log(`${replies.length} replies:`);
+
+  replies.forEach((reply, i) => {
+    console.log(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL Server
+
+**モジュール**: [tedious](https://github.com/tediousjs/tedious)
+
+### インストール
+
+```bash
+$ npm install tedious
+```
+
+### 例
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious').Request;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // update me
+      password: 'your_password', // update me
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection.on('connect', (err) => {
+  if (err) {
+    console.log(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hello world'", (err, rowCount) => {
+    if (err) {
+      console.log(err);
+    } else {
+      console.log(`${rowCount} rows`);
+    }
+    connection.close();
+  });
+
+  request.on('row', (columns) => {
+    columns.forEach((column) => {
+      if (column.value === null) {
+        console.log('NULL');
+      } else {
+        console.log(column.value);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**モジュール**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### インストール
+
+```bash
+$ npm install sqlite3
+```
+
+### 例
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.run('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.prepare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.run(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.log(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**モジュール**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### インストール
+
+```bash
+$ npm install elasticsearch
+```
+
+### 例
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .search({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          fields: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .then(
+    (response) => {
+      const hits = response.hits.hits;
+    },
+    (error) => {
+      console.trace(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/ja/guide/migrating-4.mdx b/src/content/pages/ja/guide/migrating-4.mdx
new file mode 100644
index 0000000000..c9afc49bea
--- /dev/null
+++ b/src/content/pages/ja/guide/migrating-4.mdx
@@ -0,0 +1,663 @@
+---
+title: Express 4に移動中
+description: Express.jsアプリケーションをバージョン3からバージョン4に移行するためのガイドでは、ミドルウェアの変更、ルーティング、コードベースの効果的な更新方法について説明します。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+エクスプレス4はエクスプレス3からの変更です。 つまり、Expressバージョンを依存関係で更新すると、既存のExpress 3アプリは動作しなくなります。
+
+この記事のカバー：
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Express 4</a> の変更点。
+  </li>
+  <li>
+    <a href="#example-migration">Express 3 アプリを Express 4 に移行する例</a>
+  </li>
+  <li>
+    <a href="#app-gen">Upgrading to the Express 4 app generator</a>.
+  </li>
+</ul>
+
+## Express 4の変更
+
+Express 4にはいくつかの大きな変更点があります。
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Express core システムとミドルウェアシステムに変更しました。</a>
+    Connectとビルトインミドルウェアの依存関係が削除されましたので、自分でミドルウェアを追加する必要があります。
+  </li>
+  <li>
+    <a href="#routing">ルーティングシステムへの変更。</a>
+  </li>
+  <li>
+    <a href="#other-changes">その他の様々な変更。</a>
+  </li>
+</ul>
+
+こちらもご参照ください:
+
+- [新機能 in 4.x] (https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrating from 3.x to 4.x](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Express coreとミドルウェアシステムへの変更
+
+Express 4はもうConnectに依存せず、組み込みの
+ミドルウェアをコアから削除します。ただし、`express.static`関数は除外します。 This means that
+Express is now an independent routing and middleware web framework, and
+Express versioning and releases are not affected by middleware updates.
+
+組み込みのミドルウェアがなければ、アプリケーションの実行に必要なすべての
+ミドルウェアを明示的に追加する必要があります。 以下の手順に従ってください：
+
+1. モジュールをインストール: `npm install --save \<module-name>`
+2. アプリでは、次のモジュールを必要とします: `require('module-name')`
+3. ドキュメントに従ってモジュールを使用します: `app.use( ... )`
+
+以下の表は、Express 4でのExpress 3ミドルウェアとそのミドルウェアを示しています。
+
+<table class="doctable" border="1">
+  <tr>
+    <th>エクスプレス 3</th>
+    <th>エクスプレス 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">圧縮</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">クッキーセッション</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">クッキーパーサ</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">モーガン</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">サービスファビコン</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">応答時間</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">メソッド-オーバーライド</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">接続タイムアウト</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">サーブインデックス</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">スタティック</a>
+    </td>
+  </tr>
+</table>
+
+Here is the [complete list](https://github.com/senchalabs/connect#middleware) of Express 4 middleware.
+
+ほとんどの場合、古いバージョン3のミドルウェアを
+のExpress 4に置き換えることができます。 詳細については、
+GitHub のモジュールドキュメントを参照してください。
+
+#### `app.use`はパラメータを受け付けます
+
+バージョン 4 では、変数 parameter を使用して、ミドルウェア関数がロードされるパスを定義できます。 次に、ルートハンドラからパラメータの値を読み込みます。
+例:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### ルーティング システム
+
+Apps now implicitly load routing middleware, so you no longer have to
+worry about the order in which middleware is loaded with respect to
+the `router` middleware.
+
+ルートの定義方法は変更されていませんが、ルーティングシステムにはルートの整理に役立つ2つの
+新機能があります。
+
+- 新しいメソッド `app.route()` は、ルートパスに対してチェーン可能なルートハンドラを作成します。
+- モジュール式のマウント可能なルートハンドラを作成するための新しいクラス `express.Router` 。
+
+#### `app.route()`メソッド
+
+新しい`app.route()`メソッドを使用すると、ルートパスのチェーン可能なルートハンドラ
+を作成できます。 パスは単一の場所で指定されているため、モジュラールートを作成することは、冗長性とタイプミスを削減するのに役立ちます。 For more
+information about routes, see [`Router()` documentation](/en/4x/api#router).
+
+以下は、`app.route()`関数を使用して定義されたルートハンドラの例です。
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+#### `express.Router` クラス
+
+ルートを整理するのに役立つもう一つの機能は、新しいクラス
+`express.Router` で、モジュラーマウント可能な
+ルートハンドラを作成するために使用できます。 `Router`インスタンスは完全なミドルウェアと
+ルーティングシステムです。このため、しばしば"mini-app"と呼ばれます。
+
+The following example creates a router as a module, loads middleware in
+it, defines some routes, and mounts it on a path on the main app.
+
+For example, create a router file named `birds.js` in the app directory,
+with the following content:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specific to this router
+router.use((req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+});
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+次に、アプリにルーターモジュールをロードします。
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to the `/birds` and
+`/birds/about` paths, and will call the `timeLog`
+middleware that is specific to the route.
+
+### その他の変更
+
+以下の表は、Express 4の他の重要な変更点を示しています。
+
+<table class="doctable" border="1">
+  <tr>
+    <th>オブジェクト</th>
+    <th>説明</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>Express 4 は Node.js 0.10.x 以降が必要で、Node.js 0.8.x のサポートを廃止しました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      `http`モジュールは、
+      （socket.io/SPDY/HTTPS）で直接動作する必要がない限り、もはや必要ありません。
+      アプリは、`app.listen()`関数を使用して起動できます。
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      `app.configure()`関数が削除されました。 `process.env.NODE_ENV` または `app.get('env')`
+      関数を使用して環境を検出し、それに応じてアプリを構成します。
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      Express 4では、`json spaces` アプリケーションプロパティはデフォルトで無効になっています。
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      `req.accepts()`、`req.acceptsEncodings()`、`req.acceptsCharsets()`、および
+      `req.acceptsLanguages()`を使用してください。
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">相対URLを解決しなくなりました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">配列で、現在はオブジェクトです。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">関数でした; 今はオブジェクトです。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">`res.headersSent` に変更しました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">`app.mountpath` として利用可能になりました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">削除しました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">削除しました。</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      機能は基本的なクッキー値の設定に限定されるようになりました。 追加された 機能には、
+      `res.cookie()` を使用します。
+    </td>
+  </tr>
+</table>
+
+## アプリの移行例
+
+Express 3アプリケーションをExpress 4に移行する例を以下に示します。
+関心のあるファイルは `app.js` と `package.json` です。
+
+### バージョン3アプリ
+
+#### `app.js`
+
+次の `app.js` ファイルを含む Express v.3 アプリケーションを考えてみましょう。
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.session({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.static(path.join(__dirname, 'public')));
+
+// development only
+if (app.get('env') === 'development') {
+  app.use(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.createServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+The accompanying version 3 `package.json` file might look
+something like this:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "express": "3.12.0",
+    "pug": "*"
+  }
+}
+```
+
+### プロセス
+
+以下のコマンドを使用して、
+Express 4アプリに必要なミドルウェアをインストールし、ExpressとPugを最新の
+バージョンにアップデートして移行を開始します。
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest --save
+```
+
+`app.js`に以下の変更を加えます。
+
+1. 組み込みの Express ミドルウェア関数 `express.favicon` ,
+   `express.logger` , `express.methodOverride` ,
+   `express.session` , `express.bodyParser` と
+   `express.errorHandler` は、
+   `express` オブジェクトでは使用できなくなりました。 代わりの
+   を手動でインストールし、アプリにロードする必要があります。
+
+2. `app.router`関数をロードする必要がなくなりました。
+   有効なExpress 4アプリオブジェクトではないため、
+   `app.use(app.router);` コードを削除します。
+
+3. ミドルウェア関数が正しい順序でロードされていることを確認してください - アプリのルートをロードした後に `errorHandler` をロードします。
+
+### バージョン4アプリ
+
+#### `package.json`
+
+上記の `npm` コマンドを実行すると、 `package.json` が以下のように更新されます。
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1.1",
+    "express": "^4.8.0",
+    "express-session": "^1.7.2",
+    "pug": "^2.0.0",
+    "method-override": "^2.1.2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1.3",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+次に、無効なコードを削除し、必要なミドルウェアをロードし、必要に応じて他の
+変更を行います。 `app.js`ファイルは次のようになります。
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.use(methodOverride());
+app.use(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app.use(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+// error handling middleware should be loaded after the loading the routes
+if (app.get('env') === 'development') {
+  app.use(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="情報">
+`http` モジュール (socket.io/SPDY/HTTPS) で直接作業する必要がない限り、読み込みは必要ありません。この方法でアプリを起動できます。
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### アプリの実行
+
+移行処理が完了し、アプリは
+エクスプレス4アプリになりました。 確認するには、次のコマンドを使用してアプリを起動します。
+
+```bash
+$ node .
+```
+
+[http://localhost:3000](http://localhost:3000)
+を読み込み、Express 4によってレンダリングされるホームページを参照してください。
+
+## Express 4アプリジェネレーターへのアップグレード
+
+The command-line tool to generate an Express app is still
+`express`, but to upgrade to the new version, you must uninstall
+the Express 3 app generator and then install the new
+`express-generator`.
+
+### インストール中
+
+すでにExpress 3アプリジェネレータがシステムにインストールされている場合、
+アンインストールする必要があります。
+
+```bash
+$ npm uninstall -g express
+```
+
+ファイルとディレクトリ権限の設定に応じて、
+`sudo` でこのコマンドを実行する必要があります。
+
+新しいジェネレータをインストールします。
+
+```bash
+$ npm install -g express-generator
+```
+
+ファイルとディレクトリ権限の設定に応じて、
+`sudo` でこのコマンドを実行する必要があります。
+
+システムの `express` コマンドが
+Express 4ジェネレータに更新されます。
+
+### アプリジェネレーターの変更
+
+コマンドオプションと使用方法は、以下の例外を除き、ほとんど同じままです。
+
+- `--sessions` オプションを削除しました。
+- `--jshtml` オプションを削除しました。
+- [Hogan.js](http://twitter.github.io/hogan.js/) をサポートするための `--hogan` オプションを追加しました。
+
+### 例
+
+Express 4 アプリを作成するには、次のコマンドを実行します。
+
+```bash
+$ express app4
+```
+
+If you look at the contents of the `app4/app.js` file, you will notice
+that all the middleware functions (except `express.static`) that are required for
+the app are loaded as independent modules, and the `router` middleware
+is no longer explicitly loaded in the app.
+
+`app.js`ファイルがノードになっていることにも気づくでしょう。 sモジュールは、古いジェネレータによって生成されたスタンドアロンアプリとは対照的に。
+
+依存関係をインストールした後、次のコマンドを使用してアプリを起動します。
+
+```bash
+$ npm start
+```
+
+If you look at the `npm start` script in the `package.json` file,
+you will notice that the actual command that starts the app is
+`node ./bin/www`, which used to be `node app.js`
+in Express 3.
+
+Because the `app.js` file that was generated by the Express 4 generator
+is now a Node.js module, it can no longer be started independently as an app
+(unless you modify the code). モジュールは Node.js ファイル
+にロードされ、Node.js ファイルを介して開始する必要があります。 Node.js ファイルは `./bin/www`
+です。
+
+Expressアプリの作成やアプリの起動には、`bin`ディレクトリも拡張機能のない`www`
+ファイルも必須ではありません。 それらは
+発電機による提案ですので、
+のニーズに合わせて変更してください。
+
+To get rid of the `www` directory and keep things the "Express 3 way",
+delete the line that says `module.exports = app;` at the end of the
+`app.js` file, then paste the following code in its place:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+`app.js`ファイルの先頭にある`debug`モジュールがロードされていることを確認します。
+
+```js
+var debug = require('debug')('app4');
+```
+
+次に、 `start": `package.json` ファイル中の "node ./bin/www"` を `"start": "node app.js"` に変更します。
+
+これで `./bin/www` の機能を
+`app.js` に戻しました。 This change is not recommended, but the exercise helps you
+to understand how the `./bin/www` file works, and why the `app.js` file
+no longer starts on its own.
diff --git a/src/content/pages/ja/guide/migrating-5.mdx b/src/content/pages/ja/guide/migrating-5.mdx
new file mode 100644
index 0000000000..c221b9db56
--- /dev/null
+++ b/src/content/pages/ja/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Express 5に移動中
+description: Express.jsアプリケーションをバージョン4からバージョン5に移行するための包括的なガイドで、破壊的な変更、非推奨のメソッド、および新たな改善が詳しく説明されています。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+エクスプレス5はエクスプレス4と大きく異なりません。 同じ基本APIを維持していますが、以前のバージョンとの互換性を破る変更はまだあります。 したがって、Express 5を使用するように更新すると、Express 4で構築されたアプリケーションが動作しない可能性があります。
+
+このバージョンをインストールするには、Node.js バージョン 18 以上が必要です。 次に、アプリケーションディレクトリで次のコマンドを実行します。
+
+```sh
+npm install "express@5"
+```
+
+その後、自動テストを実行して何が失敗するかを確認し、以下に示すアップデートに従って問題を解決することができます。 テストに失敗した後、どのエラーが発生したかを確認するためにアプリケーションを実行します。 サポートされていないメソッドやプロパティを使用している場合は、すぐに確認できます。
+
+## Express 5 Codemods
+
+エクスプレスサーバーを移行するのに役立ちます。 コードを自動的に最新バージョンの Express に更新するコードを作成しました。
+
+使用可能なすべてのコードを実行するには、次のコマンドを実行します。
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipes
+```
+
+特定のコードを実行したい場合は、次のコマンドを実行できます。
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+利用可能なコードリスト [here](https://codemod.link/express) があります。
+
+## Express 5の変更
+
+**メソッドとプロパティを削除**
+
+<ul class="doclist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">複数化メソッド名</a>
+  </li>
+  <li>
+    <a href="#leading">名前引数でコロンを先頭に付けるapp.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(name)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') and res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:routerデバッグログ</a>
+  </li>
+</ul>
+
+**変更**
+
+<ul class="doclist">
+  <li>
+    <a href="#path-syntax">パスルート一致シンタックス</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">ミドルウェアとハンドラーから取り扱われる拒否された約束</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.variety</a>
+  </li>
+</ul>
+
+**改善**
+
+<ul class="doclist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Brotliエンコーディングサポート</a>
+  </li>
+</ul>
+
+## 削除されたメソッドとプロパティ
+
+これらのメソッドやプロパティをアプリケーションで使用すると、クラッシュします。 したがって、バージョン5にアップデートした後、アプリを変更する必要があります。
+
+### app.del()
+
+Express 5では、`app.del()`関数がサポートされなくなりました。 この関数を使うと、エラーがスローされます。 HTTP DELETEルートを登録するには、代わりに`app.delete()`関数を使用します。
+
+`delete`はJavaScriptで予約されているキーワードであるため、最初は`delete`の代わりに`del`が使用されていました。 しかし、ECMAScript 6 では、 `delete` などの予約キーワードをプロパティ名として使用することができます。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.delete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+`app.param(fn)`署名は、`app.param(name, fn)`関数の動作を変更するために使用されました。 v4.11.0以降非推奨となり、Express 5では全くサポートされなくなりました。
+
+### 複数化されたメソッド名
+
+以下のメソッド名が複数化されています。 Express 4 では、古いメソッドを使用すると非推奨になりました。 Express 5ではサポートされていません：
+
+`req.acceptsCharset()`は`req.acceptsCharsets()`に置き換えられます。
+
+`req.acceptsEncoding()`は`req.acceptsEncodings()`に置き換えられます。
+
+`req.acceptsLanguage()`は`req.acceptsLanguages()`に置き換えられました。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.acceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.all('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### app.param(name, fn) の名前の先頭コロン (:)
+
+\`appの名前の先頭にあるコロン文字 (:) です。 aram(name, fn)関数はExpress 3の名残であり、後方互換性のため、Express 4は廃止予定の通知でサポートしています。 Express 5は黙って無視し、コロンをつけずに名前パラメータを使用します。
+
+Express 4 の [app.param](/en/4x/api#app.param) のドキュメントに従っている場合、これはあなたのコードには影響しません。 主要な結腸については言及していません
+
+### req.param(name)
+
+これは、潜在的に混乱し、フォームデータを取得する危険な方法が削除されました。 ここで、`req.params`、`req.body`、または`req.query`オブジェクトの中で、送信されたパラメータ名を具体的に探す必要があります。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.param('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.id;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, status)
+
+Express 5 では署名 `res.json(obj, status)` がサポートされなくなりました。 代わりに、ステータスを設定し、 `res.json()` メソッドに次のようにチェーンさせます。`res.status(status).json(obj)` 。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 では署名 `res.jsonp(obj, status)` がサポートされなくなりました。 代わりに、ステータスを設定し、 `res.jsonp()` メソッドを次のようにチェーンします。`res.status(status).jsonp(obj)` 。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Express 5 では署名 `res.redirect(url, status)` がサポートされなくなりました。 代わりに、`res.redirect(status, url)` という署名を使用します。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') と res.location('back')
+
+Express 5では、`res.redirect()`と`res.location()`メソッドの魔法文字列`back`がサポートされなくなりました。 代わりに、 `req.get('Referrer') |'/'`の値を使用して前のページにリダイレクトします。 Express 4 では、`res.redirect('back')` と `res.location('back')` メソッドは廃止されました。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(body, status)
+
+Express 5 では署名 `res.send(obj, status)` がサポートされなくなりました。 代わりに、ステータスを設定し、 `res.status(status).send(obj)` のように、 `res.send()` メソッドを連鎖させます。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status
+
+Express 5では、`status` が数値である署名 `res.send(status)` がサポートされなくなりました。 代わりに、 `res を使ってください。 endStatus(statusCode)` 関数は、HTTP レスポンスヘッダーのステータスコードを設定し、コードのテキストバージョンを送信します。 "Not Found", "Internal Server Error"など。
+\`res を使って数字を送る必要がある場合。 end()関数は、数字を文字列に変換するために引用符で囲みます Expressはサポートされていない古い署名を使用しようとしないようにします。
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+`res.sendfile()`関数は、Express 5でキャメルケースのバージョン`res.sendFile()`に置き換えられました。
+
+**注意:** Express 5, `res. endFile()`は、MIME タイプの検出に`mime-types`パッケージを使用します。これは、一般的なファイルタイプの場合、Express 4とは異なるContent-Type値を返します。
+
+- JavaScriptファイル (.js): 「application/javascript」の代わりに「text/javascript」を追加しました
+- JSON ファイル (.json): 「text/json」の代わりに「application/json」になりました
+- CSS ファイル (.css): "text/plain" ではなく "text/css" になりました
+- XML ファイル (.xml): "text/xml" の代わりに "application/xml" になりました
+- フォントファイル (.woff): "application/font-woff" ではなく "font/woff" になりました
+- SVG ファイル (.svg): "application/svg+xml" の代わりに "image/svg+xml" になりました
+
+<Alert type="情報">
+非推奨の署名は次のコマンドで置き換えることができます:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+`router.param(fn)`署名は、`router.param(name, fn)`関数の動作を変更するために使用されました。 v4.11.0以降非推奨となり、Express 5では全くサポートされなくなりました。
+
+### express.static.mime
+
+Express 5 では、`mime` は `static` フィールドのエクスポートされたプロパティではなくなりました。
+MIME タイプの値を扱うには、[`mime-types` package](https://github.com/jshttp/mime-types) を使用します。
+
+**重要:** この変更は `express.static.mime` の直接使用だけでなく、 `res.sendFile()` のような MIME タイプの検出に依存する Express メソッドにも影響します。 Express 4から次のMIMEタイプが変更されました。
+
+- JavaScriptファイル (.js): 「application/javascript」の代わりに「text/javascript」として提供されるようになりました
+- JSON ファイル (.json): 「text/json」の代わりに「application/json」として提供されるようになりました
+- CSS ファイル (.css): 「text/plain」の代わりに「text/css」として提供されるようになりました
+- HTML ファイル (): 単に "text/html" の代わりに "text/html; charset=utf-8" として提供されました
+- XML ファイル (.xml): "text/xml" の代わりに "application/xml" として提供されるようになりました
+- フォント ファイル (.woff): "application/font-woff" ではなく "font/woff" として提供されるようになりました
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:routerデバッグログ
+
+Express 5では、ルータの処理ロジックは依存関係によって実行されます。 したがって、ルーターの
+デバッグログは、`express::` 名前空間で使用できなくなります。
+v4 では、`express:router` 、 `express:router:layer` 、
+および `express:router:route` の下でログを利用できました。 これらはすべて `express:*` という名前空間の下に含まれています。
+v5.1以降では、ログは名前空間`router`、`router:layer`、および`router:route`の下で利用できます。
+`router:layer` と `router:route` のログは、名前空間の `router:*` に含まれています。
+v4 で `express:*` を使用してデバッグログの詳細を達成するには、
+`express:*` 、 `router`、 `router:*` を使用します。
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,router:* node index.js
+```
+
+## 変更済み
+
+### パス経路一致の構文
+
+パスルートマッチング構文は、文字列が`app.all()`、`app.use()`、`app.METHOD()`、`router.all()`、`router.METHOD()`、`router.METHOD()`、`router.METHOD()`、`router.use()` APIに最初のパラメータとして与えられた場合です。 パス文字列が受信リクエストと一致する方法を次のように変更しました:
+
+- ワイルドカード`*`には名前が必要です。パラメータ`:`の動作に一致します。`/*`の代わりに`/*splat`を使用します。
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="情報">
+`*spat` はルートパスのないパスにマッチします。 `/`と同様にルートパスをマッチさせる必要がある場合は、 `/{*spat}`を使用し、ワイルドカードを括弧で囲みます。
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- オプションの文字 `?` はサポートされなくなりました。代わりに括弧を使用してください。
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- 正規表現文字はサポートされていません。 例:
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+次に変更する必要があります：
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- いくつかの文字はアップグレード中に混乱を避けるために予約されています (`()[]?+!`), それらをエスケープするために`\`を使用します。
+- パラメータ名が有効な JavaScript 識別子をサポートするようになりました。また、`:"this"` のように引用符で囲まれました。
+
+### ミドルウェアとハンドラーから取り扱われる拒否された約束。
+
+rejected promiseを返すリクエストミドルウェアとハンドラは、「Error」として拒否された値をエラー処理ミドルウェアに転送することで処理されるようになりました。 つまり、 `async` 関数をミドルウェアとして、ハンドラを使うのはこれまで以上に簡単です。 `async` 関数でエラーがスローされるか、拒否された Promise が async 関数内で `await`ed になります。 これらのエラーは、`next(err)`を呼び出すかのようにエラーハンドラに渡されます。
+
+Express でのエラー処理の詳細については、[Error handling documentation](/en/guide/error-handling)を参照してください。
+
+### express.urlencoded
+
+`express.urlencoded` メソッドはデフォルトで `extended` オプション `false` を設定します。
+
+### express.static dotfiles
+
+Express 5では、`express.static` ミドルウェアの `dotfiles` オプションがデフォルトで `"ignore"` になりました。 これは、デフォルトでdotfilesが提供されたExpress 4からの変更です。 結果として、`のようにドット(`.`)で始まるディレクトリ内のファイル。 ell-known`はアクセスできなくなり、**404 Not Found**エラーが返されます。 これにより、Android App LinksやApple Universal Linksなどのドットディレクトリの提供に依存する機能が壊れる可能性があります。
+
+破壊コードの例:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Express 5に移行した後、`/.well-known/assetlinks.json`へのリクエストは**404 Not Found**になります。
+
+これを修正するには、`dotfiles: "allow"` オプションを使用して特定のドットディレクトリを指定します。
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+このアプローチにより、意図したドットディレクトリのみを安全に提供し、他のdotfilesのデフォルトの安全な動作を維持することができます。
+
+### app.listen
+
+Express 5 では、サーバーがエラーイベントを受信したときに `app.listen` メソッドがユーザーが提供するコールバック関数を呼び出します。 Express 4では、そのようなエラーがスローされます。 この変更により、エラー処理の責任が Express 5 のコールバック関数に移行されます。 エラーがある場合は、コールバックに引数として渡されます。
+例:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Listening on ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+Express 4 で削除された `app.router` オブジェクトは、Express 5 で復活しました。 新しいバージョンでは、このオブジェクトはベース Express ルータへの単なる参照です。 アプリが明示的にロードしなければならなかったExpress 3とは異なります。
+
+### req.body
+
+`req.body` プロパティは、本文が解析されていない場合に `undefined` を返します。 Express 4 ではデフォルトで `{}` を返します。
+
+### req.host
+
+Express 4では、`req.host`関数がポート番号を間違って剥奪しました。 Express 5ではポート番号が維持されています。
+
+### req.params
+
+`req.params` オブジェクトに文字列パスを使用する際に **null プロトタイプ** が追加されました。 しかし、パスが正規表現で定義されている場合、`req.params` は通常のプロトタイプを持つ標準オブジェクトのままです。 さらに、2つの重要な行動変更があります。
+
+**ワイルドカードパラメータは配列になりました:**
+
+ワイルドカード(例: `/*splat`)は単一の文字列の代わりにパスセグメントを配列として取り込みます。
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.params);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**マッチしないパラメータは省略されました:**
+
+Express 4では、マッチしないワイルドカードは空文字列(`'`)であり、オプションのパラメータ(`?`を使用)には値が`undefined`のキーがありました。 Express 5 では、マッチしないパラメータは `req.params` から完全に省略されます。
+
+```js
+// v4: unmatched wildcard is empty string
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.params);
+  // => { '0': '' }
+});
+
+// v4: unmatched optional param is undefined
+app.get('/:file.:ext?', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{.:ext}', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.query
+
+`req.query` プロパティはもはや書き込み可能なプロパティではなく、代わりにゲッターです。 デフォルトのクエリパーサが"extended"から"simple"に変更されました。
+
+### res.clearCookie
+
+`res.clearCookie`メソッドは、ユーザーが提供する`maxAge`と`expires`オプションを無視します。
+
+### res.status
+
+`res.status` メソッドは、Node によって定義された動作に従い、`100` から `999` の範囲の整数のみを受け付けます。 s, そしてステータスコードが整数でない場合にエラーを返します。
+
+### res.variable
+
+`field`引数がない場合、`res.vary`はエラーをスローします。 Express 4では、引数が省略された場合、コンソールに警告が表示されました。
+
+## 改善
+
+### res.render()
+
+このメソッドは、すべてのビューエンジンの非同期動作を強制するようになりました。 同期実装されたビューエンジンによるバグを回避し、推奨されるインターフェイスに違反していました。
+
+### Brotliエンコーディングのサポート
+
+Express 5では、サポートしているクライアントから受信したリクエストに対応するBrotliエンコーディングに対応しています。
diff --git a/src/content/pages/ja/resources/glossary.mdx b/src/content/pages/ja/resources/glossary.mdx
new file mode 100644
index 0000000000..cf3b262b4f
--- /dev/null
+++ b/src/content/pages/ja/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Express.js、Node.js、ミドルウェア、ルーティング、その他の重要な概念に関連する包括的な用語集で、Expressを効果的に理解し使用するのに役立ちます。
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### アプリケーション
+
+一般に、特定の目的のために操作を実行するように設計された1つまたは複数のプログラム。 Express のコンテキストでは、Node.js プラットフォームで実行される Express API を使用するプログラムがあります。 [app object](/en/api#express) も参照しているかもしれません。
+
+### API
+
+アプリケーションプログラミングインターフェイス。 略語が最初に使用されたときにスペルアウトします。
+
+### エクスプレス
+
+Node.jsアプリケーション用の高速で、意見が異なる、ミニマリストなWebフレームワーク。 一般的には「Express」は「Express.js」よりも好まれますが、後者は許容されます。
+
+### libuv
+
+非同期I/Oに焦点を当てたマルチプラットフォームサポートライブラリ。主にNode.jsで使用するために開発されました。
+
+### middleware
+
+最後のリクエストハンドラの前に Express ルーティング層によって呼び出される関数 生の要求と最終目的のルートの間に座っています ミドルウェアに関する用語のいくつかの細かい点:
+
+- `var foo = require('middleware')` は Node.js モジュールの _requiring_ または _using_ と呼ばれます。 `var mw = foo()`という文は通常、ミドルウェアを返します。
+- `app.use(mw)`は、ミドルウェアをグローバルな処理スタックに追加することを呼びます。
+- `app.get('/foo', mw, function (req, res) { ... })` は、ミドルウェアを "GET /foo" 処理の stack\_ に追加すると呼ばれます。
+
+### Node.js
+
+スケーラブルなネットワークアプリケーションの構築に使用されるソフトウェアプラットフォーム。 Node.jsはJavaScriptをスクリプト言語として使用し、ノンブロッキングI/Oとシングルスレッドイベントループにより高いスループットを実現します。 [nodejs.org](https://nodejs.org/en/) を参照してください。 **使用上の注意**: 最初は、"Node.js"以降は"Node"です。
+
+### オープンソースのオープンソース
+
+形容詞として使われる場合、ハイフネートなど。例: "これはオープンソースソフトウェアです。 [Wikipediaのオープンソースソフトウェア](http://en.wikipedia.org/wiki/Open-source_software)を参照してください。
+
+<Alert type="情報">
+
+この用語をハイフネーションしないことは一般的ですが、
+の標準的な英語規則を用いて複合形容詞をハイフネーションします。
+
+</Alert>
+
+### リクエスト
+
+HTTP リクエスト。 クライアントは、レスポンスを返すサーバーに HTTP リクエストメッセージを送信します。 リクエストは、GET、POST など、いくつかの [request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) のうちの 1 つを使用する必要があります。
+
+### 応答
+
+HTTPレスポンス。 サーバーはクライアントに HTTP 応答メッセージを返します。 レスポンスには、リクエストに関する完了ステータス情報が含まれており、メッセージ本文に要求されたコンテンツが含まれている場合もあります。
+
+### route
+
+リソースを識別する URL の一部です。 例えば、`http://foo.com/products/id`では、"/products/id"がルートです。
+
+### ルーター:
+
+API リファレンスの [router](/en/api#router) を参照してください。
diff --git a/src/content/pages/ja/resources/utils.md b/src/content/pages/ja/resources/utils.md
new file mode 100644
index 0000000000..cb44ec26ca
--- /dev/null
+++ b/src/content/pages/ja/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: エクスプレスユーティリティ
+description: Express.jsとNode.jsに関連するユーティリティモジュール、Cookie、CSRF保護、URLの解析、ルーティングなど、アプリケーションを強化するためのツールを含む。
+---
+
+## Express ユーティリティ関数
+
+[pillarjs](https://github.com/pillarjs) GitHub Organization には、一般的に便利なユーティリティ関数用の多くのモジュール
+が含まれています。
+
+| ユーティリティモジュール                                       | 説明                                                                                                                                                              |
+| -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | HTTP(S) Cookie を取得して設定し、改ざんを防ぐために署名できます。Keygrip を使用します。 Node.js HTTP ライブラリまたは Express ミドルウェアとして使用できます。    |
+| [csrf](https://www.npmjs.com/package/csrf)                     | CSRFトークンの作成と検証の背後にあるロジックが含まれています。 このモジュールを使用して、カスタム CSRF ミドルウェアを作成します。                                 |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | HTTP リクエストに応答するための最後のステップとして呼び出す関数。                                                                                                 |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | URLをキャッシュで解析します。                                                                                                                                     |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | \`\`/user/:name\`のようなExpressスタイルのパス文字列を正規表現に変換します。                                                                                      |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | 検証されたルートパスに対して相対パスを解決します。                                                                                                                |
+| [router](https://www.npmjs.com/package/router)                 | シンプルなミドルウェアスタイルのルータ。                                                                                                                          |
+| [send](https://www.npmjs.com/package/send)                     | HTTP レスポンスとしてファイルをストリーミングするためのライブラリで、部分的な応答 (範囲)、条件付きの GET ネゴシエーション、および細かいイベントをサポートします。 |
+
+低レベルの HTTP 関連モジュールについては、 [jshttp](https://github.com/jshttp) を参照してください。
diff --git a/src/content/pages/ja/support.md b/src/content/pages/ja/support.md
new file mode 100644
index 0000000000..b413964397
--- /dev/null
+++ b/src/content/pages/ja/support.md
@@ -0,0 +1,23 @@
+---
+title: バージョンサポート
+description: 現在メンテナンスされているバージョンや終了ポリシーを含む、さまざまなExpress.jsバージョンのサポートスケジュールに関する情報をご覧ください。
+---
+
+任意のメジャーリリースラインの最新バージョンのみがサポートされています。
+
+EOL (終了) _may_ のバージョンは、重大なセキュリティ脆弱性の更新を受け取ります。 しかし、Expressチームは保証を提供しておらず、見つかった問題の修正やリリースを計画していません。
+
+| メジャーバージョン     | 最小Node.js バージョン | サポート開始日 | サポート終了日 |
+| ---------------------- | ---------------------- | -------------- | -------------- |
+| [**v5.x**](/en/5x/api) | 18                     | 2024年9月      | **進行中**     |
+| [**v4.x**](/en/4x/api) | 0.10.0                 | 2014 年 4 月   | **進行中**     |
+| [**v3.x**](/en/3x/api) | 0.8.0                  | 2012年10月     | 2015 年 7 月   |
+| [**v2.x**](/2x/)       | 0.4.1                  | 2011 年 3 月   | 2012 年 7 月   |
+| **v1.x**               | 0.2.0                  | 2010年12月     | 2011 年 3 月   |
+| **v0.14.x**            | 0.1.98                 | 2010年12月     | 2010年12月     |
+
+## 商用サポートオプション
+
+サポートされているバージョンの Express にアップデートできない場合は、以下のいずれかのパートナーにお問い合わせください:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/ko/advanced/best-practice-performance.md b/src/content/pages/ko/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..a98c7fcf6a
--- /dev/null
+++ b/src/content/pages/ko/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Production best practices: performance and reliability'
+description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
+---
+
+This article discusses performance and reliability best practices for Express applications deployed to production.
+
+This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
+
+- Things to do in your code (the dev part):
+  - [Use gzip compression](#use-gzip-compression)
+  - [Don't use synchronous functions](#dont-use-synchronous-functions)
+  - [Do logging correctly](#do-logging-correctly)
+  - [Handle exceptions properly](#handle-exceptions-properly)
+- Things to do in your environment / setup (the ops part):
+  - [Set NODE_ENV to "production"](#set-node_env-to-production)
+  - [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+  - [Run your app in a cluster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Use a load balancer](#use-a-load-balancer)
+  - [Use a reverse proxy](#use-a-reverse-proxy)
+
+## Things to do in your code
+
+Here are some things you can do in your code to improve your application's performance:
+
+- [Use gzip compression](#use-gzip-compression)
+- [Don't use synchronous functions](#dont-use-synchronous-functions)
+- [Do logging correctly](#do-logging-correctly)
+- [Handle exceptions properly](#handle-exceptions-properly)
+
+### Use gzip compression
+
+Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. For details on enabling gzip compression in Nginx, see [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) in the Nginx documentation.
+
+### Don't use synchronous functions
+
+Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
+
+Although Node and many modules provide synchronous and asynchronous versions of their functions, always use the asynchronous version in production. The only time when a synchronous function can be justified is upon initial startup.
+
+You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli#cli_trace_sync_io) for more information.
+
+### Do logging correctly
+
+In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
+
+#### For debugging
+
+If you're logging for purposes of debugging, then instead of using `console.log()`, use a special debugging module like [debug](https://www.npmjs.com/package/debug). This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
+
+#### For app activity
+
+If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
+
+### Handle exceptions properly
+
+Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
+
+To ensure you handle all exceptions, use the following techniques:
+
+- [Use try-catch](#use-try-catch)
+- [Use promises](#use-promises)
+
+Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
+
+For more on the fundamentals of error handling, see:
+
+- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Use try-catch
+
+Try-catch is a JavaScript language construct that you can use to catch exceptions in synchronous code. Use try-catch, for example, to handle JSON parsing errors as shown below.
+
+Here is an example of using try-catch to handle a potential process-crashing exception.
+This middleware function accepts a query field parameter named "params" that is a JSON object.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+However, try-catch works only for synchronous code. Because the Node platform is primarily asynchronous (particularly in a production environment), try-catch won't catch a lot of exceptions.
+
+#### Use promises
+
+When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+#### What not to do
+
+One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
+
+Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
+
+We also don't recommend using [domains](https://nodejs.org/api/domain). It generally doesn't solve the problem and is a deprecated module.
+
+## Things to do in your environment / setup
+
+Here are some things you can do in your system environment to improve your app's performance:
+
+- [Set NODE_ENV to "production"](#set-node_env-to-production)
+- [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+- [Run your app in a cluster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Use a load balancer](#use-a-load-balancer)
+- [Use a reverse proxy](#use-a-reverse-proxy)
+
+### Set NODE_ENV to "production"
+
+The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
+
+Setting NODE_ENV to "production" makes Express:
+
+- Cache view templates.
+- Cache CSS files generated from CSS extensions.
+- Generate less verbose error messages.
+
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
+
+If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
+
+In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
+
+With systemd, use the `Environment` directive in your unit file. For example:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Ensure your app automatically restarts
+
+In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
+
+- Using a process manager to restart the app (and Node) when it crashes.
+- Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
+
+Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
+
+#### Use a process manager
+
+In development, you started your app simply from the command line with `node server.js` or something similar. But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
+
+In addition to restarting your app when it crashes, a process manager can enable you to:
+
+- Gain insights into runtime performance and resource consumption.
+- Modify settings dynamically to improve performance.
+- Control clustering (pm2).
+
+Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
+
+#### Use an init system
+
+The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
+
+There are two ways to use init systems with your Express app:
+
+- Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
+- Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
+
+##### Systemd
+
+Systemd is a Linux system and service manager. Most major Linux distributions have adopted systemd as their default init system.
+
+A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Run your app in a cluster
+
+In a multi-core system, you can increase the performance of a Node app by many times by launching a cluster of processes. A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
+
+![Balancing between application instances using the cluster API](/images/clustering.png)
+
+IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
+
+In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
+
+#### Using Node's cluster module
+
+Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
+
+#### Using PM2
+
+If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
+
+When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
+
+To enable cluster mode, start your application like so:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
+
+Once running, the application can be scaled like so:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
+
+### Cache request results
+
+Another strategy to improve the performance in production is to cache the result of requests, so that your app does not repeat the operation to serve the same request repeatedly.
+
+Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
+
+### Use a load balancer
+
+No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
+
+A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Use a reverse proxy
+
+A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
+
+Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/src/content/pages/ko/advanced/best-practice-security.mdx b/src/content/pages/ko/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..4ca68c5122
--- /dev/null
+++ b/src/content/pages/ko/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Production Best Practices: Security'
+description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
+
+Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+Security best practices for Express applications in production include:
+
+- [Production Best Practices: Security](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Use TLS](#use-tls)
+  - [Do not trust user input](#do-not-trust-user-input)
+    - [Prevent open redirects](#prevent-open-redirects)
+  - [Use Helmet](#use-helmet)
+  - [Reduce fingerprinting](#reduce-fingerprinting)
+  - [Use cookies securely](#use-cookies-securely)
+    - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
+    - [Set cookie security options](#set-cookie-security-options)
+  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+  - [Additional considerations](#additional-considerations)
+
+## Don't use deprecated or vulnerable versions of Express
+
+Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/en/guide/migrating-4) or consider [Commercial Support Options](/en/support#commercial-support-options).
+
+Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/en/advanced/security-updates). If you are, update to one of the stable releases, preferably the latest.
+
+## Use TLS
+
+If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## Do not trust user input
+
+For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
+Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
+
+### Prevent open redirects
+
+An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
+return a 3xx status.
+
+An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
+
+Here is an example of checking URLs before using `res.redirect` or `res.location`:
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.query.url).host !== 'example.com') {
+      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.status(400).end(`Invalid url: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Use Helmet
+
+[Helmet][helmet] can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
+
+Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
+
+- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
+- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
+- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
+- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
+- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
+- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
+- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
+- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
+- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
+- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
+- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
+
+Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
+
+Install Helmet like any other module:
+
+```bash
+$ npm install helmet
+```
+
+Then to use it in your code:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Reduce fingerprinting
+
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Though not a security issue itself,
+reducing the ability to fingerprint an application improves its overall security posture.
+Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
+the HTTP response headers.
+
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="info">
+
+Disabling the `X-Powered-By header` does not prevent a sophisticated attacker from determining
+that an app is running Express. It may discourage a casual exploit, but there are other ways to
+determine an app is running Express.
+
+</Alert>
+
+Express also sends its own formatted "404 Not Found" messages and formatter error
+response messages. These can be changed by
+[adding your own not found handler](/en/starter/faq#how-do-i-handle-404-responses)
+and
+[writing your own error handler](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+
+// custom error handler
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+## Use cookies securely
+
+To ensure cookies don't open your app to exploits, don't use the default session cookie name and set cookie security options appropriately.
+
+There are two main middleware cookie session modules:
+
+- [express-session](https://www.npmjs.com/package/express-session) that replaces `express.session` middleware built-in to Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
+
+The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
+
+In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
+
+### Don't use the default session cookie name
+
+Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
+
+To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.use(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Set cookie security options
+
+Set the following cookie options to enhance security:
+
+- `secure` - Ensures the browser only sends the cookie over HTTPS.
+- `httpOnly` - Ensures the cookie is sent only over HTTP(S), not client JavaScript, helping to protect against cross-site scripting attacks.
+- `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
+- `path` - indicates the path of the cookie; use it to compare against the request path. If this and domain match, then send the cookie in the request.
+- `expires` - use to set expiration date for persistent cookies.
+
+Here is an example using [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000); // 1 hour
+app.use(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      domain: 'example.com',
+      path: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## Prevent brute-force attacks against authorization
+
+Make sure login endpoints are protected to make private data more secure.
+
+A simple and powerful technique is to block authorization attempts using two metrics:
+
+1. The number of consecutive failed attempts by the same user name and IP address.
+2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Ensure your dependencies are secure
+
+Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
+
+Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
+
+```bash
+$ npm audit
+```
+
+If you want to stay more secure, consider [Snyk](https://snyk.io/).
+
+Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Use this command to test your application for vulnerabilities:
+
+```bash
+$ snyk test
+```
+
+### Avoid other known vulnerabilities
+
+Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
+
+Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
+
+## Additional considerations
+
+Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
+
+- Always filter and sanitize user input to protect against cross-site scripting (XSS) and command injection attacks.
+- Defend against SQL injection attacks by using parameterized queries or prepared statements.
+- Use the open-source [sqlmap](http://sqlmap.org/) tool to detect SQL injection vulnerabilities in your app.
+- Use the [nmap](https://nmap.org/) and [sslyze](https://github.com/nabla-c0d3/sslyze) tools to test the configuration of your SSL ciphers, keys, and renegotiation as well as the validity of your certificate.
+- Use [safe-regex](https://www.npmjs.com/package/safe-regex) to ensure your regular expressions are not susceptible to [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacks.
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/ko/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/ko/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..c060e58605
--- /dev/null
+++ b/src/content/pages/ko/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Health Checks and Graceful Shutdown
+description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
+---
+
+## Graceful shutdown
+
+When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+
+### Example
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Health checks
+
+A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, that determines when to restart a container.
+- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
diff --git a/src/content/pages/ko/advanced/security-updates.mdx b/src/content/pages/ko/advanced/security-updates.mdx
new file mode 100644
index 0000000000..c5ea3f336a
--- /dev/null
+++ b/src/content/pages/ko/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Security updates
+description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="alert">
+
+Node.js vulnerabilities directly affect Express. Therefore, keep a watch on Node.js
+vulnerabilities and make sure you are using the latest
+stable version of Node.js.
+
+</Alert>
+
+The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+- 4.20.0
+  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+- 4.19.0, 4.19.1
+  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
+  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
+- 4.15.5
+  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
+  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
+- 4.15.2
+  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
+- 4.11.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 4.10.7
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Fixed directory traversal vulnerabilities in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 4.8.0
+  - Sparse arrays that have extremely high indexes in the query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+
+## 3.x
+
+<Alert type="warning">
+**Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
+
+Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 3.19.0
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Fixed directory traversal vulnerabilities in `express.static`.
+- 3.16.6
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 3.16.0
+  - Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+- 3.3.0
+  - The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
diff --git a/src/content/pages/ko/guide/database-integration.mdx b/src/content/pages/ko/guide/database-integration.mdx
new file mode 100644
index 0000000000..b0855e4a2a
--- /dev/null
+++ b/src/content/pages/ko/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Database integration
+description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="alert">
+
+These database drivers are among many that are available. For other options, search on the
+[npm](https://www.npmjs.com/) site.
+
+</Alert>
+
+## Cassandra
+
+**Module**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installation
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Example
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.execute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Module**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Installation
+
+```bash
+$ npm install couchbase
+```
+
+### Example
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// add a document to a bucket
+bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+
+// get all documents with shoe size 13
+const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery.fromString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Module**: [nano](https://github.com/dscape/nano)
+
+### Installation
+
+```bash
+$ npm install nano
+```
+
+### Example
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.use('books');
+
+// Insert a book document in the books database
+books.insert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body);
+  }
+});
+
+// Get a list of all books
+books.list((err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Module**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Installation
+
+```bash
+$ npm install level levelup leveldown
+```
+
+### Example
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.put('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.get('name', (err, value) => {
+    if (err) return console.log('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Module**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Installation
+
+```bash
+$ npm install mysql
+```
+
+### Example
+
+```js
+const mysql = require('mysql');
+const connection = mysql.createConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connection.connect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.log('The solution is: ', rows[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Module**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installation
+
+```bash
+$ npm install mongodb
+```
+
+### Example (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+### Example (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.db('animals');
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+If you want an object model driver for MongoDB, look at [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installation
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Example
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .run('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].get('count'));
+    })
+    .catch((error) => {
+      console.log(error);
+    });
+});
+```
+
+## Oracle
+
+**Module**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installation
+
+NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Example
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb.getConnection(config);
+
+    const result = await conn.execute('select * from employees where employee_id = :id', [empId]);
+
+    console.log(result.rows[0]);
+  } catch (err) {
+    console.log('Ouch!', err);
+  } finally {
+    if (conn) {
+      // conn assignment worked, need to close
+      await conn.close();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installation
+
+```bash
+$ npm install pg-promise
+```
+
+### Example
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .then((data) => {
+    console.log('DATA:', data.value);
+  })
+  .catch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Module**: [redis](https://github.com/mranney/node_redis)
+
+### Installation
+
+```bash
+$ npm install redis
+```
+
+### Example
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.set('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.hkeys('hash key', (err, replies) => {
+  console.log(`${replies.length} replies:`);
+
+  replies.forEach((reply, i) => {
+    console.log(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL Server
+
+**Module**: [tedious](https://github.com/tediousjs/tedious)
+
+### Installation
+
+```bash
+$ npm install tedious
+```
+
+### Example
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious').Request;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // update me
+      password: 'your_password', // update me
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection.on('connect', (err) => {
+  if (err) {
+    console.log(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hello world'", (err, rowCount) => {
+    if (err) {
+      console.log(err);
+    } else {
+      console.log(`${rowCount} rows`);
+    }
+    connection.close();
+  });
+
+  request.on('row', (columns) => {
+    columns.forEach((column) => {
+      if (column.value === null) {
+        console.log('NULL');
+      } else {
+        console.log(column.value);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Module**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installation
+
+```bash
+$ npm install sqlite3
+```
+
+### Example
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.run('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.prepare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.run(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.log(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Module**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installation
+
+```bash
+$ npm install elasticsearch
+```
+
+### Example
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .search({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          fields: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .then(
+    (response) => {
+      const hits = response.hits.hits;
+    },
+    (error) => {
+      console.trace(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/ko/guide/migrating-4.mdx b/src/content/pages/ko/guide/migrating-4.mdx
new file mode 100644
index 0000000000..42a1b63163
--- /dev/null
+++ b/src/content/pages/ko/guide/migrating-4.mdx
@@ -0,0 +1,662 @@
+---
+title: Moving to Express 4
+description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 is a breaking change from Express 3. That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
+
+This article covers:
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Changes in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Upgrading to the Express 4 app generator</a>.
+  </li>
+</ul>
+
+## Changes in Express 4
+
+There are several significant changes in Express 4:
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on
+    Connect and built-in middleware were removed, so you must add middleware yourself.
+  </li>
+  <li>
+    <a href="#routing">Changes to the routing system.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Various other changes.</a>
+  </li>
+</ul>
+
+See also:
+
+- [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Changes to Express core and middleware system
+
+Express 4 no longer depends on Connect, and removes all built-in
+middleware from its core, except for the `express.static` function. This means that
+Express is now an independent routing and middleware web framework, and
+Express versioning and releases are not affected by middleware updates.
+
+Without built-in middleware, you must explicitly add all the
+middleware that is required to run your app. Simply follow these steps:
+
+1. Install the module: `npm install --save <module-name>`
+2. In your app, require the module: `require('module-name')`
+3. Use the module according to its documentation: `app.use( ... )`
+
+The following table lists Express 3 middleware and their counterparts in Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compression</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">cookie-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">cookie-parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">response-time</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">method-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">connect-timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">serve-static</a>
+    </td>
+  </tr>
+</table>
+
+Here is the [complete list](https://github.com/senchalabs/connect#middleware) of Express 4 middleware.
+
+In most cases, you can simply replace the old version 3 middleware with
+its Express 4 counterpart. For details, see the module documentation in
+GitHub.
+
+#### `app.use` accepts parameters
+
+In version 4 you can use a variable parameter to define the path where middleware functions are loaded, then read the value of the parameter from the route handler.
+For example:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### The routing system
+
+Apps now implicitly load routing middleware, so you no longer have to
+worry about the order in which middleware is loaded with respect to
+the `router` middleware.
+
+The way you define routes is unchanged, but the routing system has two
+new features to help organize your routes:
+
+- A new method, `app.route()`, to create chainable route handlers for a route path.
+- A new class, `express.Router`, to create modular mountable route handlers.
+
+#### `app.route()` method
+
+The new `app.route()` method enables you to create chainable route handlers
+for a route path. Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
+information about routes, see [`Router()` documentation](/en/4x/api#router).
+
+Here is an example of chained route handlers that are defined by using the `app.route()` function.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+#### `express.Router` class
+
+The other feature that helps to organize routes is a new class,
+`express.Router`, that you can use to create modular mountable
+route handlers. A `Router` instance is a complete middleware and
+routing system; for this reason it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads middleware in
+it, defines some routes, and mounts it on a path on the main app.
+
+For example, create a router file named `birds.js` in the app directory,
+with the following content:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specific to this router
+router.use((req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+});
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to the `/birds` and
+`/birds/about` paths, and will call the `timeLog`
+middleware that is specific to the route.
+
+### Other changes
+
+The following table lists other small but important changes in Express 4:
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Object</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>Express 4 requires Node.js 0.10.x or later and has dropped support for Node.js 0.8.x.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      The `http` module is no longer needed, unless you need to directly work with it
+      (socket.io/SPDY/HTTPS). The app can be started by using the `app.listen()` function.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      The `app.configure()` function has been removed. Use the `process.env.NODE_ENV` or
+      `app.get('env')` function to detect the environment and configure the app accordingly.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      The `json spaces` application property is disabled by default in Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Use `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, and
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">No longer resolves relative URLs.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">Was an array; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Was a function; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Changed to `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Now available as `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      Functionality is now limited to setting the basic cookie value. Use `res.cookie()` for added
+      functionality.
+    </td>
+  </tr>
+</table>
+
+## Example app migration
+
+Here is an example of migrating an Express 3 application to Express 4.
+The files of interest are `app.js` and `package.json`.
+
+### Version 3 app
+
+#### `app.js`
+
+Consider an Express v.3 application with the following `app.js` file:
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.session({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.static(path.join(__dirname, 'public')));
+
+// development only
+if (app.get('env') === 'development') {
+  app.use(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.createServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+The accompanying version 3 `package.json` file might look
+something like this:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "express": "3.12.0",
+    "pug": "*"
+  }
+}
+```
+
+### Process
+
+Begin the migration process by installing the required middleware for the
+Express 4 app and updating Express and Pug to their respective latest
+version with the following command:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Make the following changes to `app.js`:
+
+1. The built-in Express middleware functions `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` and
+   `express.errorHandler` are no longer available on the
+   `express` object. You must install their alternatives
+   manually and load them in the app.
+
+2. You no longer need to load the `app.router` function.
+   It is not a valid Express 4 app object, so remove the
+   `app.use(app.router);` code.
+
+3. Make sure that the middleware functions are loaded in the correct order - load `errorHandler` after loading the app routes.
+
+### Version 4 app
+
+#### `package.json`
+
+Running the above `npm` command will update `package.json` as follows:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1.1",
+    "express": "^4.8.0",
+    "express-session": "^1.7.2",
+    "pug": "^2.0.0",
+    "method-override": "^2.1.2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1.3",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Then, remove invalid code, load the required middleware, and make other
+changes as necessary. The `app.js` file will look like this:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.use(methodOverride());
+app.use(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app.use(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+// error handling middleware should be loaded after the loading the routes
+if (app.get('env') === 'development') {
+  app.use(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+Unless you need to work directly with the `http` module (socket.io/SPDY/HTTPS), loading it is not required, and the app can be simply started this way:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Run the app
+
+The migration process is complete, and the app is now an
+Express 4 app. To confirm, start the app by using the following command:
+
+```bash
+$ node .
+```
+
+Load [http://localhost:3000](http://localhost:3000)
+and see the home page being rendered by Express 4.
+
+## Upgrading to the Express 4 app generator
+
+The command-line tool to generate an Express app is still
+`express`, but to upgrade to the new version, you must uninstall
+the Express 3 app generator and then install the new
+`express-generator`.
+
+### Installing
+
+If you already have the Express 3 app generator installed on your system,
+you must uninstall it:
+
+```bash
+$ npm uninstall -g express
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now install the new generator:
+
+```bash
+$ npm install -g express-generator
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now the `express` command on your system is updated to the
+Express 4 generator.
+
+### Changes to the app generator
+
+Command options and use largely remain the same, with the following exceptions:
+
+- Removed the `--sessions` option.
+- Removed the `--jshtml` option.
+- Added the `--hogan` option to support [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Example
+
+Execute the following command to create an Express 4 app:
+
+```bash
+$ express app4
+```
+
+If you look at the contents of the `app4/app.js` file, you will notice
+that all the middleware functions (except `express.static`) that are required for
+the app are loaded as independent modules, and the `router` middleware
+is no longer explicitly loaded in the app.
+
+You will also notice that the `app.js` file is now a Node.js module, in contrast to the standalone app that was generated by the old generator.
+
+After installing the dependencies, start the app by using the following command:
+
+```bash
+$ npm start
+```
+
+If you look at the `npm start` script in the `package.json` file,
+you will notice that the actual command that starts the app is
+`node ./bin/www`, which used to be `node app.js`
+in Express 3.
+
+Because the `app.js` file that was generated by the Express 4 generator
+is now a Node.js module, it can no longer be started independently as an app
+(unless you modify the code). The module must be loaded in a Node.js file
+and started via the Node.js file. The Node.js file is `./bin/www`
+in this case.
+
+Neither the `bin` directory nor the extensionless `www`
+file is mandatory for creating an Express app or starting the app. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+To get rid of the `www` directory and keep things the "Express 3 way",
+delete the line that says `module.exports = app;` at the end of the
+`app.js` file, then paste the following code in its place:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+Ensure that you load the `debug` module at the top of the `app.js` file by using the following code:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Next, change `"start": "node ./bin/www"` in the `package.json` file to `"start": "node app.js"`.
+
+You have now moved the functionality of `./bin/www` back to
+`app.js`. This change is not recommended, but the exercise helps you
+to understand how the `./bin/www` file works, and why the `app.js` file
+no longer starts on its own.
diff --git a/src/content/pages/ko/guide/migrating-5.mdx b/src/content/pages/ko/guide/migrating-5.mdx
new file mode 100644
index 0000000000..dac703c953
--- /dev/null
+++ b/src/content/pages/ko/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Moving to Express 5
+description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 is not very different from Express 4; although it maintains the same basic API, there are still changes that break compatibility with the previous version. Therefore, an application built with Express 4 might not work if you update it to use Express 5.
+
+To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
+
+```sh
+npm install "express@5"
+```
+
+You can then run your automated tests to see what fails, and fix problems according to the updates listed below. After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
+
+## Express 5 Codemods
+
+To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
+
+Run the following command for run all the codemods available:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+If you want to run a specific codemod, you can run the following command:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+You can find the list of available codemods [here](https://codemod.link/express).
+
+## Changes in Express 5
+
+**Removed methods and properties**
+
+<ul class="doclist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Pluralized method names</a>
+  </li>
+  <li>
+    <a href="#leading">Leading colon in name argument to app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(name)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') and res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:router debug logs</a>
+  </li>
+</ul>
+
+**Changed**
+
+<ul class="doclist">
+  <li>
+    <a href="#path-syntax">Path route matching syntax</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">Rejected promises handled from middleware and handlers</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Improvements**
+
+<ul class="doclist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Brotli encoding support</a>
+  </li>
+</ul>
+
+## Removed methods and properties
+
+If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
+
+### app.del()
+
+Express 5 no longer supports the `app.del()` function. If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
+
+Initially, `del` was used instead of `delete`, because `delete` is a reserved keyword in JavaScript. However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.delete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+The `app.param(fn)` signature was used for modifying the behavior of the `app.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### Pluralized method names
+
+The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
+
+`req.acceptsCharset()` is replaced by `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` is replaced by `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` is replaced by `req.acceptsLanguages()`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.acceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.all('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### Leading colon (:) in the name for app.param(name, fn)
+
+A leading colon character (:) in the name for the `app.param(name, fn)` function is a remnant of Express 3, and for the sake of backwards compatibility, Express 4 supported it with a deprecation notice. Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
+
+This should not affect your code if you follow the Express 4 documentation of [app.param](/en/4x/api#app.param), as it makes no mention of the leading colon.
+
+### req.param(name)
+
+This potentially confusing and dangerous method of retrieving form data has been removed. You will now need to specifically look for the submitted parameter name in the `req.params`, `req.body`, or `req.query` object.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.param('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.id;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, status)
+
+Express 5 no longer supports the signature `res.json(obj, status)`. Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 no longer supports the signature `res.jsonp(obj, status)`. Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') and res.location('back')
+
+Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(body, status)
+
+Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status)
+
+Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
+If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+The `res.sendfile()` function has been replaced by a camel-cased version `res.sendFile()` in Express 5.
+
+**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
+
+- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
+- JSON files (.json): now "application/json" instead of "text/json"
+- CSS files (.css): now "text/css" instead of "text/plain"
+- XML files (.xml): now "application/xml" instead of "text/xml"
+- Font files (.woff): now "font/woff" instead of "application/font-woff"
+- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### express.static.mime
+
+In Express 5, `mime` is no longer an exported property of the `static` field.
+Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
+
+**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
+
+- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
+- JSON files (.json): now served as "application/json" instead of "text/json"
+- CSS files (.css): now served as "text/css" instead of "text/plain"
+- HTML files (): now served as "text/html; charset=utf-8" instead of just "text/html"
+- XML files (.xml): now served as "application/xml" instead of "text/xml"
+- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:router debug logs
+
+In Express 5, router handling logic is performed by a dependency. Therefore, the
+debug logs for the router are no longer available under the `express:` namespace.
+In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
+and `express:router:route`. All of these were included under the namespace `express:*`.
+In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
+The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
+To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
+`express:*`, `router`, and `router:*`.
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,router:* node index.js
+```
+
+## Changed
+
+### Path route matching syntax
+
+Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
+
+- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="info">
+`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- The optional character `?` is no longer supported, use braces instead.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Regexp characters are not supported. For example:
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+should be changed to:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
+- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
+
+### Rejected promises handled from middleware and handlers
+
+Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
+
+Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling).
+
+### express.urlencoded
+
+The `express.urlencoded` method makes the `extended` option `false` by default.
+
+### express.static dotfiles
+
+In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
+
+Example of breaking code:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
+
+To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
+
+### app.listen
+
+In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
+For example:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Listening on ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+The `app.router` object, which was removed in Express 4, has made a comeback in Express 5. In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
+
+### req.body
+
+The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
+
+### req.host
+
+In Express 4, the `req.host` function incorrectly stripped off the port number if it was present. In Express 5, the port number is maintained.
+
+### req.params
+
+The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
+
+**Wildcard parameters are now arrays:**
+
+Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.params);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Unmatched parameters are omitted:**
+
+In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
+
+```js
+// v4: unmatched wildcard is empty string
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.params);
+  // => { '0': '' }
+});
+
+// v4: unmatched optional param is undefined
+app.get('/:file.:ext?', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{.:ext}', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.query
+
+The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
+
+### res.clearCookie
+
+The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
+
+### res.status
+
+The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
+
+### res.vary
+
+The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
+
+## Improvements
+
+### res.render()
+
+This method now enforces asynchronous behavior for all view engines, avoiding bugs caused by view engines that had a synchronous implementation and that violated the recommended interface.
+
+### Brotli encoding support
+
+Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/src/content/pages/ko/resources/glossary.mdx b/src/content/pages/ko/resources/glossary.mdx
new file mode 100644
index 0000000000..c40a0a2e15
--- /dev/null
+++ b/src/content/pages/ko/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### application
+
+In general, one or more programs that are designed to carry out operations for a specific purpose. In the context of Express, a program that uses the Express API running on the Node.js platform. Might also refer to an [app object](/en/api#express).
+
+### API
+
+Application programming interface. Spell out the abbreviation when it is first used.
+
+### Express
+
+A fast, un-opinionated, minimalist web framework for Node.js applications. In general, "Express" is preferred to "Express.js," though the latter is acceptable.
+
+### libuv
+
+A multi-platform support library which focuses on asynchronous I/O, primarily developed for use by Node.js.
+
+### middleware
+
+A function that is invoked by the Express routing layer before the final request handler, and thus sits in the middle between a raw request and the final intended route. A few fine points of terminology around middleware:
+
+- `var foo = require('middleware')` is called _requiring_ or _using_ a Node.js module. Then the statement `var mw = foo()` typically returns the middleware.
+- `app.use(mw)` is called _adding the middleware to the global processing stack_.
+- `app.get('/foo', mw, function (req, res) { ... })` is called _adding the middleware to the "GET /foo" processing stack_.
+
+### Node.js
+
+A software platform that is used to build scalable network applications. Node.js uses JavaScript as its scripting language, and achieves high throughput via non-blocking I/O and a single-threaded event loop. See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
+
+### open-source, open source
+
+When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Although it is common not to hyphenate this term, we are using the standard English rules for
+hyphenating a compound adjective.
+
+</Alert>
+
+### request
+
+An HTTP request. A client submits an HTTP request message to a server, which returns a response. The request must use one of several [request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) such as GET, POST, and so on.
+
+### response
+
+An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
+
+### route
+
+Part of a URL that identifies a resource. For example, in `http://foo.com/products/id`, "/products/id" is the route.
+
+### router
+
+See [router](/en/api#router) in the API reference.
diff --git a/src/content/pages/ko/resources/utils.md b/src/content/pages/ko/resources/utils.md
new file mode 100644
index 0000000000..739b352f3e
--- /dev/null
+++ b/src/content/pages/ko/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Express utilities
+description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
+---
+
+## Express utility functions
+
+The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
+for utility functions that may be generally useful.
+
+| Utility modules                                                | Description                                                                                                                                             |
+| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification. Use this module to create custom CSRF middleware.                                       |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                        |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                               |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                  |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                           |
+| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                         |
+| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.          |
+
+For additional low-level HTTP-related modules, see [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/ko/support.md b/src/content/pages/ko/support.md
new file mode 100644
index 0000000000..9e59b0976b
--- /dev/null
+++ b/src/content/pages/ko/support.md
@@ -0,0 +1,23 @@
+---
+title: Version Support
+description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
+---
+
+Only the latest version of any given major release line is supported.
+
+Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
+
+| Major Version          | Minimum Node.js Version | Support Start Date | Support End Date |
+| ---------------------- | ----------------------- | ------------------ | ---------------- |
+| [**v5.x**](/en/5x/api) | 18                      | September 2024     | **ongoing**      |
+| [**v4.x**](/en/4x/api) | 0.10.0                  | April 2014         | **ongoing**      |
+| [**v3.x**](/en/3x/api) | 0.8.0                   | October 2012       | July 2015        |
+| [**v2.x**](/2x/)       | 0.4.1                   | March 2011         | July 2012        |
+| **v1.x**               | 0.2.0                   | December 2010      | March 2011       |
+| **v0.14.x**            | 0.1.98                  | December 2010      | December 2010    |
+
+## Commercial Support Options
+
+If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/pt-br/advanced/best-practice-performance.md b/src/content/pages/pt-br/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..cc86d01356
--- /dev/null
+++ b/src/content/pages/pt-br/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Práticas de produção: desempenho e confiabilidade'
+description: Descubra desempenho e confiabilidade melhores práticas para aplicativos Express na produção, cobrindo otimizações de código e configurações de ambiente para um desempenho ideal.
+---
+
+Este artigo discute as melhores práticas de desempenho e confiabilidade para aplicativos Expresso aplicados à produção.
+
+Este tema cai claramente no mundo "devops", abrangendo tanto o desenvolvimento tradicional como as operações. Assim, a informação é dividida em duas partes:
+
+- Coisas a fazer no seu código (a parte de desenvolvedor):
+  - [Usar compressão gzip](#use-gzip-compression)
+  - [Não usar funções síncronas](#dont-use-synchronous-functions)
+  - [Faça o registro corretamente](#do-logging-correctly)
+  - [Tratar exceções corretamente](#handle-exceptions-properly)
+- Coisas a fazer em seu ambiente / configuração (a parte ops):
+  - [Definir NODE_ENV para "produção"](#set-node_env-to-production)
+  - [Verifique se seu aplicativo reinicia automaticamente](#ensure-your-app-automatically-restarts)
+  - [Execute seu aplicativo em um cluster](#run-your-app-in-a-cluster)
+  - [Resultados da requisição de cache](#cache-request-results)
+  - [Usar um balanceador de carga](#use-a-load-balancer)
+  - [Usar um proxy reverso](#use-a-reverse-proxy)
+
+## Coisas a fazer em seu código
+
+Aqui estão algumas coisas que você pode fazer em seu código para melhorar o desempenho do seu aplicativo:
+
+- [Usar compressão gzip](#use-gzip-compression)
+- [Não usar funções síncronas](#dont-use-synchronous-functions)
+- [Faça o registro corretamente](#do-logging-correctly)
+- [Tratar exceções corretamente](#handle-exceptions-properly)
+
+### Usar compressão gzip
+
+O compactação Gzip pode diminuir significativamente o tamanho do corpo da resposta e, assim, aumentar a velocidade de um aplicativo da web. Use o [compression](https://www.npmjs.com/package/compression) middleware para compressão gzip no seu aplicativo Express. Por exemplo:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+Para um sítio web de alto tráfego, em produção, a melhor maneira de colocar a compressão no lugar é implementá-la a um nível de proxy reverso (veja [usar um proxy reverso](#use-a-reverse-proxy)). Nesse caso, não é necessário utilizar um middleware de compressão. Para detalhes sobre como ativar a compressão gzip no Nginx, consulte [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) na documentação do Nginx.
+
+### Não usar funções síncronas
+
+Os métodos e funções síncríveis ligam o processo de execução até que retornam. Uma única chamada para uma função síncrona pode retornar em alguns microsegundos ou milissegundos, No entanto, em sites com alto tráfego, essas chamadas somam e reduzem o desempenho do aplicativo. Evite a sua utilização em produção.
+
+Embora o Node e muitos módulos fornecem versões sincronizadas e assíncronas de suas funções, sempre use a versão assíncrona em produção. O único momento em que uma função síncrona pode ser justificada é na inicialização inicial.
+
+Você pode usar o sinalizador de linha de comando `--trace-sync-io` para imprimir um aviso e um rastreamento de pilha sempre que seu aplicativo usar uma API síncrona. Claro, você não gostaria de usar isto em produção, mas sim de garantir que seu código esteja pronto para produção. Veja a [documentação de opções de linha de comando do nó](https://nodejs.org/api/cli#cli_trace_sync_io) para mais informações.
+
+### Faça o login corretamente
+
+Em geral, existem duas razões para registrar seu aplicativo: para depuração e para registrar a atividade do aplicativo (essencialmente, tudo o mais). Usar `console.log()` ou `console.error()` para imprimir mensagens de log no terminal é uma prática comum de desenvolvimento. Mas [essas funções são sincronizadas](https://nodejs.org/api/console#console) quando o destino é um terminal ou um arquivo, então eles não são adequados para produção, a menos que você canalize a saída para outro programa.
+
+#### Para depuração
+
+Se você está logando para fins de depuração, em vez de usar `console.log()`, use um módulo de depuração especial, como [debug](https://www.npmjs.com/package/debug). Esse módulo permite que você use a variável de ambiente DEBUG para controlar quais mensagens de depuração são enviadas para `console.error()`, se houver. Para manter seu aplicativo puramente assíncrono, você ainda pode usar o comando `console.error()` para outro programa. Mas então, você realmente não vai depurar na produção, não é?
+
+#### Para atividades do aplicativo
+
+Se você está registrando a atividade do aplicativo (por exemplo, monitorando tráfego ou chamadas de API), em vez de usar o `console. og()`, use uma biblioteca de logs como [Pino](https://www.npmjs.com/package/pino), que é a opção mais rápida e eficiente disponível.
+
+### Manipular exceções corretamente
+
+Aplicativos do nó falham quando encontram uma exceção desmarcada. Não lidar com exceções e tomar as ações adequadas fará com que seu app Express pare de funcionar e fique offline. Se você seguir o conselho em [Verifique se seu aplicativo reinicia automaticamente](#ensure-your-app-automatically-restarts) abaixo, então seu aplicativo se recuperará de uma falha. Felizmente, os aplicativos Express normalmente têm um curto tempo de inicialização. No entanto, o senhor deputado quer evitar a queda, e, para isso, tem de tratar devidamente as excepções.
+
+Para garantir que você lida com todas as exceções, use as seguintes técnicas:
+
+- [Usar captura final](#use-try-catch)
+- [Usar promessas](#use-promises)
+
+Antes de mergulhar nestes tópicos, você deve ter um entendimento básico da manipulação de erro Node/Express: usar callback error first e propagar erros no middleware. O nó utiliza uma convenção "error-first callback" para retornar erros de funções assíncronas, onde o primeiro parâmetro para a função de callback é o objeto de erro, seguido pelos dados de resultado em parâmetros de sucesso. Para indicar nenhum erro, passe nulo como primeiro parâmetro. A função de callback deve seguir correspondentemente a convenção de callback error-first para lidar de forma significativa com o erro. E em Express, a melhor prática é usar a função next() para propagar erros através da cadeia de middleware.
+
+Para saber mais sobre os fundamentos da manipulação de erros, veja:
+
+- [Erro manipulando o Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Usar try-catch
+
+Try-catch é uma construção de idioma JavaScript que você pode usar para capturar exceções em código síncrono. Use a tentativa de captura, por exemplo, para lidar com erros de análise JSON, como mostrado abaixo.
+
+Aqui está um exemplo de utilização de capturas de tentativa para lidar com uma potencial exceção do crash do processo.
+Esta função middleware aceita um parâmetro de campo de consulta chamado "params" que é um objeto JSON.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+No entanto, a tentativa y-catch só funciona para código síncrono. Porque a plataforma Node é principalmente assíncrona (particularmente em ambiente de produção), a tentativa de captura não vai pegar muitas exceções.
+
+#### Usar promessas
+
+Quando um erro é lançado em uma função `async` ou uma promessa rejeitada é aguardada dentro de uma função `async`, esses erros serão passados para o manipulador de erros como se chamando `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Além disso, você pode usar funções assíncronas para o seu middleware, e o roteador irá lidar com erros se a promessa falhar, por exemplo:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+A melhor prática é lidar com os erros o mais próximo possível do site. Então enquanto isso é manipulado no roteador, É melhor encontrar o erro no middleware e lidar com ele sem depender de um middleware separado para manipular erros.
+
+#### O que não fazer
+
+Uma coisa que você não deveria fazer é ouvir o evento `uncaughtException`, emitido quando uma exceção bolha até o laço de repetição do evento. Adicionando um listener de eventos para `uncaughtException` mudará o comportamento padrão do processo que está encontrando uma exceção; o processo continuará a decorrer apesar da excepção. Isso pode soar como uma boa maneira de impedir que seu aplicativo caia, mas continuar a executar o aplicativo após uma exceção não detectada é uma prática perigosa e não é recomendado, porque o estado do processo se torna pouco fiável e imprevisível.
+
+Além disso, usar `uncaughtException` é oficialmente reconhecido como [crude](https://nodejs.org/api/process#process_event_uncaughtexception). Então ouvir por `uncaughtException` é apenas uma má ideia. É por isso que recomendamos coisas como processos múltiplos e supervisores: falhar e reiniciar é muitas vezes a maneira mais confiável de recuperar de um erro.
+
+Também não recomendamos o uso de [domains](https://nodejs.org/api/domain). Geralmente isso não resolve o problema e é um módulo obsoleto.
+
+## Coisas a fazer no seu ambiente / configuração
+
+Aqui estão algumas coisas que você pode fazer em seu ambiente de sistema para melhorar o desempenho do seu aplicativo:
+
+- [Definir NODE_ENV para "produção"](#set-node_env-to-production)
+- [Verifique se seu aplicativo reinicia automaticamente](#ensure-your-app-automatically-restarts)
+- [Execute seu aplicativo em um cluster](#run-your-app-in-a-cluster)
+- [Resultados da requisição de cache](#cache-request-results)
+- [Usar um balanceador de carga](#use-a-load-balancer)
+- [Usar um proxy reverso](#use-a-reverse-proxy)
+
+### Definir NODE_ENV para "produção"
+
+A variável de ambiente NODE_ENV especifica o ambiente em que uma aplicação está sendo executada (usualmente, desenvolvimento ou produção). Uma das coisas mais simples que você pode fazer para melhorar o desempenho é configurar NODE_ENV para `produção`.
+
+Definir NODE_ENV para "produção" faz Expressão:
+
+- Modelos de exibição em cache.
+- Arquivos CSS do cache gerados a partir de extensões CSS.
+- Gerar mensagens de erro menos detalhadas.
+
+[Testes indicados](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) que apenas fazer isso pode melhorar o desempenho do aplicativo por um fator de três!
+
+Se você precisar escrever código de ambiente específico, você pode verificar o valor de NODE_ENV com `process.env.NODE_ENV`. Esteja ciente de que verificar o valor de qualquer variável de ambiente implica uma penalização de desempenho, assim como deve ser feito com moderação.
+
+No desenvolvimento, você normalmente define variáveis de ambiente em seu shell interativo, por exemplo, usando `export` ou seu arquivo `.bash_profile`. Mas, em geral, você não deve fazer isso em um servidor de produção; em vez disso, use o sistema init do seu SO (sistema). A próxima seção fornece mais detalhes sobre o uso do seu sistema de init em geral mas a configuração de `NODE_ENV` é tão importante para desempenho (e fácil de fazer), que é destacada aqui.
+
+Com o sistema, use a diretiva `Ambiente` no seu arquivo unitário. Por exemplo:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+Para obter mais informações, consulte [Usando Variáveis de Ambiente em Unidades sistêmicas](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Certifique-se de que seu aplicativo reinicie automaticamente
+
+Em produção, você não quer que sua aplicação fique offline, nunca. Isto significa que você precisa ter certeza que ele reiniciará tanto se o aplicativo falhar e o próprio servidor falhar. Embora você espere que nenhum desses acontecimentos ocorra, realisticamente você deve ter em conta ambas as eventualidades por:
+
+- Usando um gerenciador de processo para reiniciar o aplicativo (e Node) quando ele travar.
+- Usando o sistema de init fornecido pelo seu sistema operacional para reiniciar o gerenciador de processos quando o sistema operacional travar. Também é possível usar o sistema sem um gerente de processo.
+
+Aplicativos do nó falham se encontrarem uma exceção não capturada. A principal coisa que você precisa fazer é garantir que seu aplicativo seja bem testado e tenha todas as exceções (veja [handle exceptions correctly](#handle-exceptions-properly) para detalhes). Mas como falha, coloque um mecanismo em prática para garantir que se e quando o aplicativo parar de funcionar, ele será reiniciado automaticamente.
+
+#### Usar um gerenciador de processo
+
+Em desenvolvimento, você iniciou seu aplicativo simplesmente pela linha de comando com `node server.js` ou algo parecido. Mas fazer isto em produção é uma receita para o desastre. Se o aplicativo falhar, ele ficará offline até você reiniciá-lo. Para garantir que seu aplicativo seja reiniciado se ele falhar, use um gerenciador de processo. Um gerenciador de processo é um "container" para aplicativos que facilitam a implantação, fornece alta disponibilidade, e permite que você gerencie o aplicativo em tempo de execução.
+
+Além de reiniciar seu aplicativo quando ele falhar, um gerente de processo pode habilitá-lo:
+
+- Receba informações sobre o desempenho da execução e o consumo de recursos.
+- Modifique as configurações dinamicamente para melhorar o desempenho.
+- Controle agrupamento (pm2).
+
+Historicamente, foi popular usar um gerente de processo Node.js como [PM2](https://github.com/Unitech/pm2). Veja a documentação deles, se você quiser fazer isso. No entanto, recomendamos a utilização de seu sistema de init para gerenciamento de processos.
+
+#### Usar um sistema de entrada
+
+A próxima camada de confiabilidade é garantir que seu aplicativo seja reiniciado quando o servidor reiniciar. Os sistemas ainda podem descer por diversas razões. Para garantir que seu aplicativo seja reiniciado se o servidor falhar, use o sistema incorporado no seu sistema operacional. O sistema principal de init em uso hoje é [systemd](https://wiki.debian.org/systemd).
+
+Existem duas maneiras de usar sistemas de entrada com seu aplicativo Express:
+
+- Execute seu aplicativo em um gerenciador de processo e instale o gerente de processo como um serviço com o sistema de init. O gerenciador de processos irá reiniciar seu aplicativo quando o aplicativo falhar, e o sistema inicial irá reiniciar o gerenciador de processos quando o sistema operacional for reiniciado. Esta é a abordagem recomendada.
+- Execute seu aplicativo (e Node) diretamente com o sistema init. Isto é um pouco mais simples, mas você não obtém as vantagens adicionais de usar um gerenciador de processo.
+
+##### Systemd
+
+O Systemd é um gerenciador de serviços e sistema Linux. A maioria das principais distribuições de Linux adotaram o sistema como sistema de init padrão.
+
+Um arquivo de configuração de serviço systemd é chamado de _unit file_, com um nome de arquivo terminando em `.service`. Aqui está um exemplo de arquivo unitário para gerenciar um aplicativo Node diretamente. Substitua os valores colocados em \`<angle brackets>para o seu sistema e aplicativo:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Para obter mais informações sobre o sistema, consulte a [referência do sistema (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Executar seu aplicativo em um cluster
+
+Em um sistema multi-núcleo, você pode aumentar o desempenho de um aplicativo Node muitas vezes, iniciando um cluster de processos. Um cluster executa várias instâncias do aplicativo, idealmente uma instância em cada núcleo da CPU, distribuindo assim a carga e tarefas entre as instâncias.
+
+![Balanceamento entre instâncias de aplicação usando a API de agrupamento](/images/clustering.png)
+
+IMPORTANTE: Como as instâncias do aplicativo são executadas como processos separados, eles não compartilham o mesmo espaço de memória. Ou seja, objetos são locais para cada instância do aplicativo. Por conseguinte, não pode manter o estado no código de candidatura. No entanto, você pode usar um datastore na memória como [Redis](http://redis.io/) para armazenar dados e estado relacionados à sessão. Esta ressalva se aplica essencialmente a todas as formas de escala horizontal, seja agrupamento com vários processos ou vários servidores físicos.
+
+Em apps agrupados, os processos dos trabalhadores podem falhar individualmente sem afetar o resto dos processos. Além das vantagens de desempenho, isolamento de falhas é outra razão para executar um agrupamento de processos de aplicativos. Sempre que um processo do worker parar de funcionar, tenha certeza de registrar o evento e gerar um novo processo usando cluster.fork().
+
+#### Usando módulo de cluster do Node
+
+É possível agrupar com o [módulo cluster do Node](https://nodejs.org/api/cluster). Isto permite a um processo mestre gerar processos de trabalhadores e distribuir conexões de entrada entre os trabalhadores.
+
+#### Usando PM2
+
+Se você publicar sua aplicação com PM2, então você pode aproveitar o clustering _without_ para modificar o código da sua aplicação. Você deve garantir sua [inscrição sem estado](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) primeiro, significando que nenhum dado local é armazenado no processo (como sessões, conexões de websocket e coisas parecidas).
+
+Ao executar um aplicativo com PM2, você pode habilitar o **modo de agrupamento** para executá-lo em um cluster com várias instâncias de sua escolha, como o número de CPUs disponíveis na máquina. Você pode alterar manualmente o número de processos no cluster usando a ferramenta de linha de comando `pm2` sem parar o aplicativo.
+
+Para ativar o modo de agrupamento, inicie seu aplicativo assim:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+Isto também pode ser configurado em um arquivo de processo PM2 (`ecosystem.config. s` ou similar) definindo `exec_mode` para `cluster` e `instâncias` para o número de trabalhadores para começar.
+
+Ao executar, o aplicativo pode ser dimensionado assim:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+Para obter mais informações sobre agrupamento com PM2, consulte [Modo Cluster](https://pm2.keymetrics.io/docs/usage/cluster-mode/) na documentação PM2.
+
+### Resultados da requisição em cache
+
+Outra estratégia para melhorar o desempenho em produção é armazenar em cache o resultado das solicitações, para que seu aplicativo não repita a operação para atender o mesmo pedido repetidamente.
+
+Use um servidor de cache como [Varnish](https://www.varnish-cache.org/) ou [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (veja também [Nginx Caching](https://serversforhackers.com/nginx-caching/)) para melhorar muito a velocidade e o desempenho de sua aplicação.
+
+### Use um balanceador de carga
+
+Não importa o quão otimizado um app seja, uma única instância pode manipular apenas uma quantidade limitada de carga e tráfego. Uma maneira de expandir um aplicativo é rodando várias instâncias dele e distribuindo o tráfego através de um balanceador de carga. Configurar um balanceador de carga pode melhorar o desempenho e a velocidade do seu aplicativo, e habilitá-lo a escalar mais do que é possível com uma única instância.
+
+Um balanceador de carga geralmente é um proxy reverso que orqualiza o tráfego de e para a partir de várias instâncias de aplicativos e servidores. Você pode facilmente configurar um balanceador de carga para o seu aplicativo usando [Nginx](https://nginx.org/en/docs/http/load_balancing) ou [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+Com o balanceamento de carga, você pode ter que garantir que os pedidos que estão associados a um determinado ID de sessão estejam conectados ao processo que os originou. Isto é conhecido como afinidade de sessão, ou _sessões fixas_, e pode ser abordado pela sugestão acima para usar um armazenamento de dados, como Redis para dados de sessão (dependendo do seu aplicativo). Para uma discussão, consulte [Usando múltiplos nós](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Usar um proxy reverso
+
+Um proxy reverso está na frente de um aplicativo web e executa operações de suporte sobre as solicitações, além de direcionar solicitações para o aplicativo. Ele pode lidar com páginas de erro, compressão, cache, arquivos de servidor, e o equilíbrio de carga entre outras coisas.
+
+Atingir tarefas que não exigem conhecimento do estado do aplicativo para um proxy reverso libera o Express para executar tarefas de aplicativo especializado. Por este motivo, é recomendado executar Expresso atrás de um proxy reverso como [Nginx](https://www.nginx.org/) ou [HAProxy](https://www.haproxy.org/) em produção.
diff --git a/src/content/pages/pt-br/advanced/best-practice-security.mdx b/src/content/pages/pt-br/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..16d04ed456
--- /dev/null
+++ b/src/content/pages/pt-br/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Melhores Práticas de Produção: Segurança'
+description: Descubra as melhores práticas de segurança cruciais para aplicativos Express em produção, incluindo o uso de TLS, validação de entrada, cookies seguros e prevenção de vulnerabilidades.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+O termo _"produção"_ se refere ao estágio no ciclo de vida do software quando uma aplicação ou API está geralmente disponível para seus usuários finais ou consumidores. Em contraste, na etapa "development"\_\_ , você ainda está escrevendo e testando o código, e o aplicativo não está aberto para acesso externo. Os ambientes de sistema correspondentes são conhecidos como ambientes de _produção_ e _desenvolvimento_, respectivamente.
+
+Os ambientes de desenvolvimento e de produção são concebidos de forma diferente e têm requisitos muito diferentes. O que há de bom no desenvolvimento pode não ser aceitável na produção. Por exemplo, em um ambiente de desenvolvimento, você pode querer um registro detalhado de erros para depuração, enquanto o mesmo comportamento pode se tornar uma preocupação de segurança em ambiente de produção. E no desenvolvimento, você não precisa se preocupar com escalabilidade, confiabilidade e desempenho, enquanto esses problemas se tornam críticos em produção.
+
+<Alert type="informações">
+
+Se acredita que descobriu uma vulnerabilidade de segurança em Express, consulte Segurança
+Políticas e Procedimentos.
+
+</Alert>
+
+As melhores práticas de segurança para aplicações Expressas na produção incluem:
+
+- [Práticas de Melhor Produção: Segurança](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Não usar versões descontinuadas ou vulneráveis do Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Usar TLS](#use-tls)
+  - [Não confie na entrada do usuário](#do-not-trust-user-input)
+    - [Impedir redirecionamentos abertos](#prevent-open-redirects)
+  - [Usar capacete](#use-helmet)
+  - [Reduzir impressão digital](#reduce-fingerprinting)
+  - [Usar cookies de forma segura](#use-cookies-securely)
+    - [Não usar o nome padrão de cookie da sessão](#dont-use-the-default-session-cookie-name)
+    - [Definir opções de segurança de cookies](#set-cookie-security-options)
+  - [Impedir ataques brute-force contra a autorização](#prevent-brute-force-attacks-against-authorization)
+  - [Garanta que suas dependências sejam seguras](#ensure-your-dependencies-are-secure)
+    - [Evitar outras vulnerabilidades conhecidas](#avoid-other-known-vulnerabilities)
+  - [Considerações adicionais](#additional-considerations)
+
+## Não usar versões obsoletas ou vulneráveis do Express
+
+Expresso 2,x e 3.x já não são mantidos. Problemas de segurança e desempenho nestas versões não serão corrigidos. Não os utilize! Se você não se moveu para a versão 4, siga o [guia de migração](/en/guide/migrating-4) ou considere [Opções de Suporte Comercial](/en/support#commercial-support-options).
+
+Certifique-se também de que você não está usando nenhuma das versões vulneráveis Express listadas na [Página de atualizações de segurança](/en/advanced/security-updates). Se você estiver, atualize para uma das versões estáveis, de preferência a mais recente.
+
+## Usar TLS
+
+Se seu aplicativo lida com ou transmite dados confidenciais, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) para proteger a conexão e os dados. Esta tecnologia criptografa dados antes de ser enviada do cliente para o servidor, impedindo assim alguns hackers comuns (e fáceis). Embora solicitações do Ajax e POST não sejam óbvias e pareçam "ocultas" nos navegadores, seu tráfego de rede está vulnerável ao [sniffing de pacotes](https://en.wikipedia.org/wiki/Packet_analyzer) e [ataques do meio](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+Você deve estar familiarizado com a criptografia Secure Socket Layer (SSL). [TLS é simplesmente a próxima progressão do SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). Em outras palavras, se você estava usando SSL antes, considere atualizar para o TLS. Em geral, recomendamos o Nginx para lidar com TLS. Para uma boa referência para configurar TLS no Nginx (e outros servidores), consulte [Configurações de servidores recomendadas (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Além disso, uma ferramenta prática para obter um certificado TLS gratuito é [Let's Encrypt](https://letsencrypt.org/about/), uma ferramenta gratuita, automatizada, e abrir autoridade certificadora (CA) fornecida pelo [Grupo de Investigação de Segurança da Internet (ISRG)](https://www.abetterinternet.org/).
+
+## Não confiar em entrada do usuário
+
+Para aplicativos web, um dos requisitos de segurança mais críticos é a validação e tratamento adequado dos dados de entrada do usuário. Isto tem muitas formas e não as cobriremos todas aqui.
+Em última análise, a responsabilidade de validar e manipular corretamente os tipos de entrada de usuário que seu aplicativo aceita é sua.
+
+### Impedir redirecionamentos abertos
+
+Um exemplo de entrada de usuário potencialmente perigosa é um _open redirect_, onde um aplicativo aceita uma URL como entrada de usuário (muitas vezes na consulta de URL, por exemplo `? rl=https://exemplo. om`) e usa `res.redirect` para definir o cabeçalho `location` e
+return um status de 3xx.
+
+Uma aplicação deve validar que suporta redirecionamento para a URL de entrada, para evitar enviar usuários para links maliciosos, como sites de phishing, entre outros riscos.
+
+Aqui está um exemplo de verificar URLs antes de usar `res.redirect` ou `res.location`:
+
+```js
+app.use((req, res) => {
+  tente {
+    if (nova Url(req. uery.url).host !== 'example.com') {
+      return res.status(400). nd(`Redirecionamento não suportado para host: ${req.query.url}`);
+    }
+  } capturar (e) {
+    retorna! tatus(400).end(`url inválida: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Usar o Capacete
+
+[Helmet][helmet] pode ajudar a proteger seu app de algumas vulnerabilidades conhecidas da web, definindo os cabeçalhos HTTP adequadamente.
+
+Capacete é uma função middleware que define cabeçalhos de resposta HTTP relacionados à segurança. Capacete define os seguintes cabeçalhos por padrão:
+
+- `Content-Security-Policy`: Uma poderosa lista de permissões do que pode acontecer na sua página, que mitiga muitos ataques
+- `Cross-Origin-Opener-Policy`: Ajuda a isolar sua página
+- `Cross-Origin-Resource-Policy`: Bloqueia outros de carregar seus recursos de cruzamento de origem
+- `Origin-Agent-Cluster`: Altera o isolamento de processo para ser baseado na origem
+- `Referrer-Policy`: Controla o cabeçalho [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer)
+- `Strict-Transport-Security`: Diz aos navegadores para preferirem HTTPS
+- `X-Content-Type-Options`: Evitar [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Força os downloads a serem salvos (apenas no Internet Explorer
+- `X-Frame-Options`: Cabeçalho de legado que mitiga [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) ataques
+- `X-Perting-Cross-Domain-Policies`: Controla o comportamento entre domínios para produtos Adobe, como a Acrobat
+- `X-Powered-By`: Informações sobre o servidor web. Removido porque poderia ser utilizado em ataques simples
+- `X-XSS-Protection`: Cabeçalho de legado que tenta mitigar [ataques XSS](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), mas piora as coisas, então o Capacete desabilita
+
+Cada cabeçalho pode ser configurado ou desativado. Para ler mais sobre isso, por favor, vá para [a documentação do site][helmet].
+
+Instalar o Capacete como qualquer outro módulo:
+
+```bash
+$ npm install helmet
+```
+
+Então para usá-lo em seu código:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Reduzir impressão digital
+
+Ele pode ajudar a fornecer uma camada extra de segurança para reduzir a capacidade dos invasores de determinar
+o software que um servidor utiliza, conhecido como "impressão digital". Embora não seja um problema de segurança em si,
+reduzir a capacidade de impressão digital de um aplicativo melhora sua posição geral de segurança.
+O software do servidor pode ser impresso por peculiares em como ele responde a solicitações específicas, por exemplo em
+os cabeçalhos de resposta HTTP.
+
+Por padrão, o Expresso envia o cabeçalho de resposta `X-Powered-By` que você pode
+desabilitar usando o método `app.disable()`:
+
+```js
+app.disable('x-powered-por');
+```
+
+<Alert type="informações">
+
+Desativar o cabeçalho 'X-Powered-By ' não impede que um invasor sofisticado determine
+que um aplicativo está executando o Express. Isso pode desencorajar um exploit casual, mas existem outras maneiras de
+determinar que um aplicativo está executando o Expresso.
+
+</Alert>
+
+Express também envia suas próprias mensagens formatadas "404 Não Encontradas" e erro de formatação
+mensagens de resposta. Elas podem ser alteradas por
+[adicionando seu próprio manipulador não encontrado](/en/starter/faq#how-do-i-handle-404-responses)
+e
+[escrevendo seu próprio manipulador de erro](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// personalizado 404
+app.use((req, res, next) => {
+  res.status(404). end("Desculpe não consegue encontrar isso!");
+});
+
+// aplicativo personalizado para manipulador de erros
+. se((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Algo quebra!');
+});
+```
+
+## Usar cookies de forma segura
+
+Para garantir que cookies não abram seu aplicativo para exploits, não use o nome padrão de cookie de sessão e defina as opções de segurança de cookie adequadamente.
+
+Existem dois principais módulos de sessão do cookie middleware:
+
+- [express-session](https://www.npmjs.com/package/express-session) que substitui `express.session` middleware integrado ao Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
+
+A principal diferença entre estes dois módulos é como eles salvam os dados da sessão de cookie. O [express-session](https://www.npmjs.com/package/express-session) middleware armazena os dados de sessão no servidor; apenas salva o ID da sessão no próprio cookie, não nos dados da sessão. Por padrão, ele usa armazenamento de memória e não é projetado para um ambiente de produção. Na produção, você precisará configurar uma loja de sessão escalável; ver a lista de [lojas de sessões compatíveis](https://github.com/expressjs/session#compatible-session-stores).
+
+Em contraste, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implementa o armazenamento apoiado por cookie: serializa toda a sessão para o cookie, em vez de apenas uma chave de sessão. Use isso apenas quando os dados da sessão são relativamente pequenos e facilmente codificados como valores primitivos (em vez de objetos). Embora os navegadores devem suportar pelo menos 4096 bytes por cookie, para garantir que você não exceda o limite, não exceda um tamanho de 4093 bytes por domínio. Além disso, esteja ciente de que os dados de cookie serão visíveis para o cliente, portanto, se houver qualquer razão para mantê-lo seguro ou obscurecer, então `express-session` pode ser uma melhor escolha.
+
+### Não usar o nome padrão de cookie de sessão
+
+Usar o nome padrão de cookie de sessão pode abrir seu aplicativo para ataques. A questão de segurança colocada é semelhante ao `X-Powered-By`: um potencial atacante pode usá-lo para impressão digital do servidor e ataques alvo de acordo.
+
+Para evitar este problema, use nomes genéricos de cookie, por exemplo, usando [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // confia no primeiro proxy
+app. se(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+
+```
+
+### Definir opções de segurança do cookie
+
+Defina as seguintes opções de cookies para aumentar a segurança:
+
+- `secure` - Garante que o navegador envie apenas o cookie via HTTPS.
+- `httpOnly` - Garante que o cookie é enviado somente via HTTP(S), não do cliente JavaScript, ajudando a proteger contra ataques de script via site.
+- `domínio` - indica o domínio do cookie; use-o para comparar com o domínio do servidor no qual a URL está sendo solicitada. Se eles coincidirem, verifique o atributo de caminho em seguida.
+- `path` - indica o caminho do cookie; use-o para comparar com o caminho do pedido. Se este e o domínio corresponderem então envie o cookie na solicitação.
+- `expires` - use para definir a data de validade para cookies persistentes.
+
+Aqui está um exemplo usando [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date. ow() + 60 * 60 * 1000); aplicativo // 1 hora
+se(
+  sessão({
+    nome: 'sessão',
+    chaves: ['chave1', 'chave2'],
+    cookie: {
+      seguro: verdadeiro,
+      httpOnly: true,
+      domínio: 'exemplo. om',
+      caminho: 'foo/bar',
+      expira: data de expiração,
+    },
+  })
+);
+```
+
+## Evite ataques brutos contra autorização
+
+Certifique-se de que os endpoints de login estejam protegidos para tornar os dados privados mais seguros.
+
+Uma técnica simples e poderosa é bloquear tentativas de autorização usando duas métricas:
+
+1. O número de tentativas consecutivas com o mesmo nome de usuário e endereço IP.
+2. O número de tentativas falhadas de um endereço IP por um longo período de tempo. Por exemplo, bloqueie um endereço IP se fizer 100 tentativas falhadas em um dia.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) pacote fornece ferramentas para tornar essa técnica fácil e rápida. Você pode encontrar [um exemplo de proteção brute-force na documentação](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Certifique-se de que suas dependências estejam seguras
+
+Usar o npm para gerenciar as dependências do seu aplicativo é poderoso e conveniente. Mas os pacotes que você usa podem conter vulnerabilidades de segurança críticas que também podem afetar sua aplicação. A segurança do seu aplicativo só é forte como o link "mais fraco" em suas dependências.
+
+Desde npm@6, npm revisa automaticamente toda requisição de instalação. Além disso, você pode usar o `npm audit` para analisar sua árvore de dependências.
+
+```bash
+$ auditoria do npm
+```
+
+Se você deseja ficar mais seguro, considere [Snyk](https://snyk.io/).
+
+Snyk oferece tanto uma [ferramenta de linha de comando](https://www.npmjs.com/package/snyk) quanto uma [integração com um Github](https://snyk.io/docs/github) que verifica a sua aplicação no [banco de dados de vulnerabilidades de fonte aberta do Snyk](https://snyk.io/vuln/) para quaisquer vulnerabilidades conhecidas em suas dependências. Instalar CLI da seguinte forma:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Use este comando para testar suas vulnerabilidades:
+
+```bash
+$ teste snyk
+```
+
+### Evitar outras vulnerabilidades conhecidas
+
+Fique de olho nos conselhos [Node Security Project](https://npmjs.com/advisories) ou [Snyk](https://snyk.io/vuln/) que possam afetar os módulos Express ou outros que seu aplicativo usa. Em geral, estas bases de dados são excelentes recursos para o conhecimento e ferramentas sobre a segurança dos Nós.
+
+Finalmente, Aplicativos Expressos&mdash;como qualquer outro aplicativo da web&mdash;podem ser vulneráveis a uma variedade de ataques baseados na web. Familiarize-se com as conhecidas [vulnerabilidades da web](https://www.owasp.org/www-project-top-ten/) e tome precauções para evitá-las.
+
+## Considerações adicionais
+
+Aqui estão mais algumas recomendações do excelente [Checklist de Segurança do Node.js](https://blog.risingstack.com/node-js-security-checklist/). Consulte este post para todos os detalhes destas recomendações:
+
+- Sempre filtre e sanize a entrada do usuário para proteger contra scripts entre sites (XSS) e ataques de injeção de comando.
+- Defenda-se contra ataques de injeção de SQL usando consultas parametrizadas ou declarações preparadas.
+- Use a ferramenta de código aberto [sqlmap](http://sqlmap.org/) para detectar as vulnerabilidades de injeção de SQL em seu aplicativo.
+- Usar as ferramentas [nmap](https://nmap.org/) e [sslyze](https://github.com/nabla-c0d3/sslyze) para testar a configuração de suas cifras SSL, chaves e renegociação, bem como a validade de seu certificado.
+- Use [safe-regex](https://www.npmjs.com/package/safe-regex) para garantir que suas expressões regulares não são suscetíveis a ataques [negação regular de serviço](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS).
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/pt-br/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/pt-br/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..392c97191a
--- /dev/null
+++ b/src/content/pages/pt-br/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Exame de Saúde e Desligamento Gracioso
+description: Aprenda como implementar verificações de saúde e encerramentos graciosos em aplicativos Express, para melhorar a confiabilidade, gerenciar implantações e integrar com balanceadores de carga como Kubernetes.
+---
+
+## Encerramento Gracioso
+
+Quando você publica uma nova versão do seu aplicativo, você deve substituir a versão anterior. O gerente de processo que você está utilizando primeiro enviará um sinal SIGTERM ao aplicativo para notificá-lo de que ele será encerrado. Assim que o aplicativo receber este sinal, ele deve parar de aceitar novas solicitações, finalizar todas as solicitações em andamento, limpe os recursos que usou, incluindo conexões de banco de dados e bloqueios de arquivos e depois saia.
+
+### Exemplo
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Exercícios de saúde
+
+Um balanceador de carga usa verificações de saúde para determinar se uma instância do aplicativo é saudável e pode aceitar pedidos. Por exemplo, [Kubernetes tem dois exames de saúde](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, isso determina quando reiniciar um contêiner.
+- `pronto`, que determina quando um recipiente está pronto para começar a aceitar tráfego. Quando um pod não está pronto, é removido dos balanceadores de carga de serviço.
diff --git a/src/content/pages/pt-br/advanced/security-updates.mdx b/src/content/pages/pt-br/advanced/security-updates.mdx
new file mode 100644
index 0000000000..38498582a3
--- /dev/null
+++ b/src/content/pages/pt-br/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Atualizações de segurança
+description: Revise as últimas atualizações de segurança e patches do Express.js, incluindo listas detalhadas de vulnerabilidades para diferentes versões para ajudar a manter um aplicativo seguro.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="alerta">
+
+vulnerabilidades do Node.js afetam diretamente o Express. Portanto, mantenha um relógio no Node.js
+vulnerabilidades e certifique-se que está usando a última versão estável
+do Node.js.
+
+</Alert>
+
+A lista abaixo enumera as vulnerabilidades Express que foram corrigidas na atualização da versão especificada.
+
+<Alert type="informações">
+
+Se acredita que descobriu uma vulnerabilidade de segurança em Express, consulte Segurança
+Políticas e Procedimentos.
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - A dependência `path-to-regexp` foi atualizada para o endereço de um [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - A dependência `cookie` foi atualizada para o endereço [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), isso pode afetar sua aplicação se você usar `res.cookie`.
+- 4.20.0
+  - Vulnerabilidade XSS corrigida em `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - A dependência `serve-static` foi atualizada para o endereço [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - A dependência `enviar` foi atualizada para o endereço [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - A dependência `path-to-regexp` foi atualizada para o endereço de um [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - A dependência `body-parser` foi atualizada para adicionar um [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), isso pode afetar sua aplicação se você tiver uma url ativa de codificação.
+- 4.19.0, 4.19.1
+  - Corrigido a vulnerabilidade de redirecionamento aberto em `res.location` e `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - A dependência `qs` foi atualizada para o endereço [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). Isso pode afetar sua aplicação se as seguintes APIs forem usadas: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - A dependência `encaminhado` foi atualizada para o endereço [vulnerability](https://npmjs.com/advisories/527). Isso pode afetar sua aplicação se as seguintes APIs forem usadas: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - A dependência `mime` foi atualizada para endereçar um [vulnerability](https://npmjs.com/advisories/535), mas esta issue não afeta o Express.
+  - A dependência `send` foi atualizada para fornecer uma proteção contra uma [Node.js 8.5.0 vulnerabilidade](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). Isso só afeta a execução do Express na versão 8.5.0 específica do Node.js.
+- 4.15.5
+  - A dependência `debug` foi atualizada para endereçar um [vulnerability](https://snyk.io/vuln/npm:debug:20170905), mas esta issue não afeta o Express.
+  - A dependência `fresh` foi atualizada para endereço [vulnerability](https://npmjs.com/advisories/526). Isso afetará sua aplicação se as seguintes APIs forem usadas: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - A dependência `ms` foi atualizada para endereço [vulnerability](https://snyk.io/vuln/npm:ms:20170412). Isso pode afetar sua aplicação se entrada de string não confiável for passada para a opção `maxAge` nas seguintes APIs: `express.static`, `res.sendfile` e `res.sendFile`.
+- 4.15.2
+  - A dependência `qs` foi atualizada para endereçar um [vulnerability](https://snyk.io/vuln/npm:qs:20170213), mas esta issue não afeta o Express. Atualizar para 4.15.2 é uma boa prática, mas não é necessário para resolver a vulnerabilidade.
+- 4.11.1
+  - vulnerabilidade de divulgação de caminhos raiz corrigidos em `express.static`, `res.sendfile`, e `res.sendFile`
+- 4.10.7
+  - Corrigido a vulnerabilidade de redirecionamento aberto em `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Vulnerabilidades de travessia de diretório fixas em `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 pode vazar `fd`s em certas situações que afetam `express.static` e `res.sendfile`. Solicitações maliciosas podem causar vazamento de `fd`s e eventualmente levar a erros `EMFILE` e servidor sem resposta.
+- 4.8.0
+  - Matrizes Sparse que possuem índices extremamente altos na cadeia de consulta pode fazer com que o processo fique sem memória e falhe o servidor.
+  - Objetos de string de consulta extremamente aninhados poderiam fazer com que o processo bloqueasse e tornar o servidor temporariamente não responsivo.
+
+## 3.x
+
+<Alert type="advertência">
+**Expresso 3.x É END-OF-LIFE E NÃO É LONGER MAINTADO**
+
+Problemas conhecidos e desconhecidos de segurança e desempenho em 3.x não foram abordados desde a última atualização (1 de agosto de 2015). É altamente recomendado usar a versão mais recente do Express.
+
+Se você não puder atualizar as anteriores 3.x, considere as [Opções de Suporte Comercial](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - vulnerabilidade de divulgação de caminhos raiz corrigidos em `express.static`, `res.sendfile`, e `res.sendFile`
+- 3.19.0
+  - Corrigido a vulnerabilidade de redirecionamento aberto em `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Vulnerabilidades de transposição de diretório fixas em `express.static`.
+- 3.16.6
+  - Node.js 0.10 pode vazar `fd`s em certas situações que afetam `express.static` e `res.sendfile`. Solicitações maliciosas podem causar vazamento de `fd`s e eventualmente levar a erros `EMFILE` e servidor sem resposta.
+- 3.16.0
+  - Matrizes Sparse que possuem índices extremamente altos em cadeia de consulta pode fazer com que o processo fique sem memória e falhe o servidor.
+  - Objetos de string de consulta extremamente aninhados poderiam fazer com que o processo bloqueasse e tornar o servidor temporariamente não responsivo.
+- 3.3.0
+  - A resposta 404 de uma tentativa de substituição de método não suportado era suscetível a ataques de script entre sites.
diff --git a/src/content/pages/pt-br/guide/database-integration.mdx b/src/content/pages/pt-br/guide/database-integration.mdx
new file mode 100644
index 0000000000..5d2de4370e
--- /dev/null
+++ b/src/content/pages/pt-br/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Integração com base de dados
+description: Descubra como integrar vários bancos de dados com aplicações do Express.js, incluindo exemplos de configuração para MongoDB, MySQL, PostgreSQL e muito mais.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Adicionar a capacidade de conectar bancos de dados aos aplicativos Express é apenas uma questão de carregar um driver Node.js apropriado para o banco de dados em seu aplicativo. Este documento explica brevemente como adicionar e usar alguns dos mais populares módulos Node.js para os sistemas de banco de dados no seu aplicativo Express:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="alerta">
+
+Estes motoristas da base de dados estão entre muitos que estão disponíveis. Para outras opções, pesquise no site
+[npm](https://www.npmjs.com/).
+
+</Alert>
+
+## Cassandra
+
+**Módulo**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Instalação
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Exemplo
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+cliente.xecute('selecione chave de system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Módulo**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Instalação
+
+```bash
+$ npm install couchbase
+```
+
+### Exemplo
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// adiciona um documento a um balde
+. nsert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console. og(resultado);
+  }
+});
+
+// recebe todos os documentos com o tamanho de sapatos 13
+const n1ql = 'SELECT d. DE `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery. romString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console. og(err);
+  } else {
+    console.log(resultado);
+  }
+});
+```
+
+## CouchDB
+
+**Módulo**: [nano](https://github.com/dscape/nano)
+
+### Instalação
+
+```bash
+$ npm install nano
+```
+
+### Exemplo
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.se('livros');
+
+// Insira um documento de livro no banco de dados de livros
+livros.nsert({ name: 'A Arte da guerra' }, null, (err, body) => {
+  if (err) {
+    console.og(err);
+  } else {
+    console.og(corpo);
+  }
+});
+
+// Pegue uma lista de todos os livros
+livros.ist((err, corpo) => {
+  if (err) {
+    console.og(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Módulo**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Instalação
+
+```bash
+$ npm install level levelup leveldown
+```
+
+### Exemplo
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db. ut('nome', 'NívelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db. et('nome', (err, value) => {
+    se (err) retornar um console. og('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Módulo**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Instalação
+
+```bash
+$ npm install mysql
+```
+
+### Exemplo
+
+```js
+const mysql = require('mysql');
+const connection = mysql.createConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connection.connect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.log('The solution is: ', rows[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Módulo**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Instalação
+
+```bash
+$ npm install mongodb
+```
+
+### Exemplo (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.ollection('mammal')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(resultado);
+    });
+});
+```
+
+### Exemplo (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.b('animais');
+
+  db.collection('mammals')
+    .find()
+    .oArray((err, result) => {
+      if (err) throw err;
+
+      console.og(resultado);
+    });
+});
+```
+
+Se você quer um driver de objeto para MongoDB, olhe para [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Módulo**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Instalação
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Exemplo
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.asic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .un('MATCH (n) contagem RETURN COMO count')
+    .then((res) => {
+      console.log(res.records[0].et('count'));
+    })
+    .catch((error) => {
+      console.og(erro);
+    });
+});
+```
+
+## Orátopo
+
+**Módulo**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Instalação
+
+NOTA: [Ver pré-requisitos de instalação](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Exemplo
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  usuário: '<your db user>',
+  password: '<your db password>',
+  conectando: 'localhost:1521/orcl',
+};
+
+função async getEmployee(empId) {
+  let conn;
+
+  tente {
+    conn = await oracledb. etConnection(config);
+
+    const result = await conn. xecute('selecione * de funcionários onde empregado_id = :id', [empId]);
+
+    console. og(result.rows[0]);
+  } captura (err) {
+    console. og('Ai! , err);
+  } finalmente {
+    if (conn) {
+      // atribuição de conn funcionou, precisa fechar
+      aguarda conn. Perdido ();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Módulo**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Instalação
+
+```bash
+$ npm install pg-promise
+```
+
+### Exemplo
+
+```js
+const pgp = require('pg-promise')(/* opções */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS valor', 123)
+  .hen((data) => {
+    console.log('DATA:', data.value);
+  })
+  .atch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Módulo**: [redis](https://github.com/mranney/node_redis)
+
+### Instalação
+
+```bash
+$ npm install redis
+```
+
+### Exemplo
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+cliente.et('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+cliente.set(['chave hash', 'hashtest 2', 'alguns outros valor'], redis.print);
+
+cliente.keys('hash key', (err, respostas) => {
+  console.log(`${replies.length} respostas:`);
+
+  respostas.orEach((reply, i) => {
+    console.og(`    ${i}: ${reply}`);
+  });
+
+  cliente.quit();
+});
+```
+
+## Servidor SQL
+
+**Módulo**: [tedious](https://github.com/tediousjs/tedious)
+
+### Instalação
+
+```bash
+$ npm install tedious
+```
+
+### Exemplo
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious'). equipar;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    opções: {
+      userName: 'nome_seu_usuário', // atualiza-me
+      senha: 'your_password', // atualiza-me
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+de conexão. n('connect', (err) => {
+  if (err) {
+    console. og(err);
+  } else {
+    executeStatement();
+  }
+});
+
+função executeStatement() {
+  request = new Request("selecione 123, 'olá mundo'", (err, rowCount) => {
+    if (err) {
+      console. og(err);
+    } else {
+      console. og(`${rowCount} linhas`);
+    }
+    conexão. lose();
+  });
+
+  request.on('row', (columns) => {
+    colunas. orEach((column) => {
+      if (column.value === null) {
+        console. og('NULL');
+      } else {
+        console.log(coluna. alue);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Módulo**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Instalação
+
+```bash
+$ npm install sqlite3
+```
+
+### Exemplo
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db. un('CRIAR TABLE lorem (info TEXT)');
+  const stmt = db. repare('INSERIR VALORES (?)');
+
+  para (let i = 0; i < 10; i++) {
+    stmt. un(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db. ach('SELECT rowid AS id, info FROM lorem', (err, linha) => {
+    console. og(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Módulo**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Instalação
+
+```bash
+$ npm install elasticsearch
+```
+
+### Exemplo
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .earch({
+    index: 'books',
+    type: 'book',
+    corpo: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          campos: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .hen(
+    (resposta) => {
+      const hits = response.hits.itens;
+    },
+    (error) => {
+      console.race(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/pt-br/guide/migrating-4.mdx b/src/content/pages/pt-br/guide/migrating-4.mdx
new file mode 100644
index 0000000000..196e881f52
--- /dev/null
+++ b/src/content/pages/pt-br/guide/migrating-4.mdx
@@ -0,0 +1,664 @@
+---
+title: Mover para Expresso 4
+description: Um guia para migrar seus aplicativos Express.js da versão 3 para 4, cobrindo mudanças no middleware, roteamento e como atualizar sua base de código eficazmente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Expresso 4 é uma mudança quebrada do Express 3. Isso significa que um aplicativo Expresso 3 não funcionará se você atualizar a versão Expresso em suas dependências.
+
+Cobertos deste artigo:
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Alterações no Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Atualizando para o gerador de aplicativos Express 4</a>.
+  </li>
+</ul>
+
+## Mudanças no Express 4
+
+Há várias mudanças significativas na Expresso 4:
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Altera para Express core e sistema de middleware.</a> As dependências de
+    conectar e middleware embutido foram removidas, então você deve adicionar middleware você mesmo.
+  </li>
+  <li>
+    <a href="#routing">Altera o sistema de roteamento.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Various other changes.</a>
+  </li>
+</ul>
+
+Ver também:
+
+- [Novas funcionalidades em 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrando da 3.x para a versão 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Alterações no núcleo do Express e sistema de middleware
+
+Express 4 no longer depends on Connect, and removes all built-in
+middleware from its core, except for the `express.static` function. Isto significa que
+Express agora é uma estrutura web de roteamento e middleware independente e
+Versões e versões Express não são afetados por atualizações de middleware.
+
+Sem o intermediário integrado, você deve adicionar explicitamente todo o intermediário
+que é necessário para executar seu aplicativo. Basta seguir estes passos:
+
+1. Instale o módulo: `npm install --save <module-name>`
+2. Na sua aplicação, requer o módulo: `require('module-name')`
+3. Use o módulo de acordo com sua documentação: `app.use( ... )`
+
+A seguinte tabela lista Express 3 middleware e seus homólogos no Express 4.
+
+<table class="Docável" border="1">
+  <tr>
+    <th>Expressar 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compressão</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      U<a href="https://github.com/expressjs/cookie-session">cookie-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">cookie-parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">Morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      U<code>expressão.sessão</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">response-time</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">method-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">connect-timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      U<code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">Ave-estática</a>
+    </td>
+  </tr>
+</table>
+
+Aqui está a [lista completa](https://github.com/senchalabs/connect#middleware) de Express 4 middleware.
+
+Na maioria dos casos, você pode simplesmente substituir a versão antiga 3 middleware com
+seu Expresso 4. Para obter detalhes, consulte a documentação do módulo no
+GitHub.
+
+#### `app.use` aceita parâmetros
+
+Na versão 4 você pode usar um parâmetro variável para definir o caminho onde as funções de middleware são carregadas, em seguida, leia o valor do parâmetro a partir do manipulador de reta.
+Por exemplo:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### O sistema de roteamento
+
+Apps agora carregam implicitamente roteando middleware, então você não tem mais que
+se preocupar com a ordem em que o middleware é carregado em relação a
+o middleware do `router`.
+
+A forma como você define rotas é inalterada, mas o sistema de roteamento tem dois
+novos recursos para ajudar a organizar suas rotas:
+
+- Um novo método, `app.route()`, para criar gerenciadores de rotas em cadeia para um caminho de rota.
+- Uma nova classe, `express.Router`, para criar modular montável handlers.
+
+#### Método `app.route()`
+
+O novo método `app.route()` permite que você crie gerenciadores de rotas
+encadeáveis para um caminho de rota. Como o caminho é especificado em um único local, é útil criar rotas modulares, assim como reduzir a redundância e os tipos. Para obter mais informações
+sobre rotas, consulte [`Router()` documentação](/en/4x/api#router).
+
+Aqui está um exemplo de manipuladores de rota encadeados que são definidos usando a função `app.route()`.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.end('Recebe um livro aleatório');
+  })
+  .ost((req, res) => {
+    res.send('Adicionar um livro');
+  })
+  .ut((req, res) => {
+    res.send('Atualizar o livro');
+  });
+```
+
+#### Classe `express.Router`
+
+O outro recurso que ajuda a organizar rotas é uma nova classe,
+`express.Router`, que você pode usar para criar modular montável um controlador de rotas
+. Uma instância `Router` é um sistema de roteamento de intermediários e
+completo; por esta razão, é muitas vezes referido como um "mini-app".
+
+O exemplo a seguir cria um roteador como um módulo, carrega middleware em
+ele, define algumas rotas e o conecta em um caminho no aplicativo principal.
+
+Por exemplo, crie um arquivo de roteador chamado `birds.js` no diretório de aplicativos,
+com o seguinte conteúdo:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware específico para este roteador
+. se((req, res, ext) => {
+  console.log('Tempo:', Data. ow());
+  next();
+});
+// define a rota da página inicial do roteador
+. et('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define a rota
+roteador. et('/about', (req, res) => {
+  res.send('Sobre birds');
+});
+
+module.exports = router;
+```
+
+Em seguida, carregue o módulo do roteador no aplicativo:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+Agora o aplicativo será capaz de lidar com pedidos para os caminhos `/birds` e
+`/birds/about`, e irá chamar o middleware `timeLog`
+que é específico da rota.
+
+### Outras mudanças
+
+A tabela a seguir lista outras pequenas mas importantes mudanças no Express 4:
+
+<table class="Docável" border="1">
+  <tr>
+    <th>Object</th>
+    <th>Descrição</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>
+      Express 4 requer Node.js 0.10.x ou posterior e tem abandonado o suporte para Node.js 0.8.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      O módulo `http` não é mais necessário, a menos que você precise trabalhar diretamente com ele
+      (socket.io/SPDY/HTTPS). O aplicativo pode ser iniciado usando a função `app.listen()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      A função `app.configure()` foi removida. Use a função `process.env.NODE_ENV` ou
+      `app.get('env')` para detectar o ambiente e configurar o aplicativo de acordo.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`espaços json`</td>
+    <td markdown="1">
+      A propriedade de aplicação `json spaces` está desativada por padrão no Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Use `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, e
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">Não resolve mais URLs relativas.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">Era um array; agora um objeto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Era uma função; agora um objeto.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Alterado para `res.headers`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Agora disponível como `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">removido.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">removida.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      A funcionalidade agora está limitada a definir o valor básico de cookie. Use `res.cookie()`
+      para adicionar funcionalidade.
+    </td>
+  </tr>
+</table>
+
+## Exemplo de migração de aplicativos
+
+Aqui está um exemplo de migração de um aplicativo Express 3 para o Express 4.
+Os arquivos de interesse são `app.js` e `package.json`.
+
+### Versão 3 do aplicativo
+
+#### `app.js`
+
+Considere um aplicativo Express v.3 com o seguinte arquivo `app.js`:
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var usuário = require('. routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// todos os ambientes
+app. et('porta', process.env.PORT ├3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express. ession({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express. tatic(path.join(__dirname, 'public')));
+
+// desenvolvimento apenas
+if (app.get('env') === 'development') {
+  app. se(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http. reateServer(app).listen(app.get('port'), () => {
+  console.log('Servidor expresso escutando na porta ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+O arquivo de acompanhamento da versão 3 `package.json` pode parecer
+algo como isto:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. "
+  },
+  "dependencies": {
+    "express": "3. 2.0",
+    "pug": "*"
+  }
+}
+```
+
+### processo
+
+Inicie o processo de migração instalando o middleware necessário para o aplicativo
+Express 4 e atualize o Express e o Pug para sua respectiva versão
+mais recente com o seguinte comando:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Faça as seguintes alterações no `app.js`:
+
+1. As funções embutidas do Express middleware `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` e
+   `express.errorHandler` não estão mais disponíveis no objeto
+   `express`. Você deve instalar suas alternativas
+   manualmente e carregá-las no aplicativo.
+
+2. Você não precisa mais carregar a função `app.router`.
+   Não é um objeto de aplicativo Expresso 4, então remova o código
+   `app.use(app.router);`.
+
+3. Certifique-se de que as funções de middleware estão carregadas na ordem correta - carregue o `errorHandler` após carregar as rotas do aplicativo.
+
+### Versão 4 do aplicativo
+
+#### `package.json`
+
+Executar o comando `npm` acima atualizará o `package.json` da seguinte forma:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0. ",
+  "private": true,
+  "scripts": {
+    "start": "node app. "
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1. ",
+    "express": "^4.8.0",
+    "express-session": "^1. .2",
+    "put": "^2.0.0",
+    "override-método": "^2. .2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1. ",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Then, remove invalid code, load the required middleware, and make other
+changes as necessary. O arquivo `app.js` será parecido com este:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.use(methodOverride());
+app.use(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app.use(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+// error handling middleware should be loaded after the loading the routes
+if (app.get('env') === 'development') {
+  app.use(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="informações">
+A menos que você precise trabalhar diretamente com o módulo 'http' (socket.io/SPDY/HTTPS), carregá-lo não é necessário, e o aplicativo pode ser simplesmente iniciado dessa forma:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Servidor Express escutando na porta ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Executar o aplicativo
+
+O processo de migração está completo, e o aplicativo agora é um aplicativo
+Express 4. Para confirmar, inicie o aplicativo usando o seguinte comando:
+
+```bash
+$ nó .
+```
+
+Carregue [http://localhost:3000](http://localhost:3000)
+e veja a página inicial sendo renderizada pelo Express 4.
+
+## Atualizando para o gerador de aplicativos Express 4
+
+A ferramenta de linha de comando para gerar um app Express ainda é
+`express`, mas para atualizar para a nova versão, você deve desinstalar
+o gerador de aplicativo Express 3 e então instalar o novo gerador
+`express-generator`.
+
+### Instalando
+
+Se você já tiver o gerador de aplicativo Express 3 instalado em seu sistema,
+você deve desinstalá-lo:
+
+```bash
+$ npm desinstale -g expresso
+```
+
+Dependendo de como seus privilégios de arquivo e diretório são configurados,
+talvez você precise executar este comando com `sudo`.
+
+Agora instale o novo gerador:
+
+```bash
+$ npm install -g express-generator
+```
+
+Dependendo de como seus privilégios de arquivo e diretório são configurados,
+talvez você precise executar este comando com `sudo`.
+
+Agora o comando `express` no seu sistema é atualizado para o gerador
+Express 4.
+
+### Alterações no gerador de aplicativos
+
+Opções de comando e uso em grande parte permanecem iguais, com as seguintes exceções:
+
+- A opção `--sessions` foi removida.
+- A opção `--jshtml` foi removida.
+- Adicionado a opção `--hogan` para apoiar [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Exemplo
+
+Execute o seguinte comando para criar um aplicativo Express 4:
+
+```bash
+$ app4 expresso
+```
+
+Se você olhar o conteúdo do arquivo `app4/app.js`, você notará
+que todas as funções de middleware (exceto `expressos. tatic`) que são necessários para
+o aplicativo são carregados como módulos independentes, e o 'router' middleware
+não está mais carregado explicitamente no aplicativo.
+
+Você também vai notar que o arquivo `app.js` agora é um Node. módulo s, em contraste com o app autônomo gerado pelo gerador antigo.
+
+Depois de instalar as dependências, inicie o aplicativo usando o seguinte comando:
+
+```bash
+$ início do npm
+```
+
+Se você olhar o script `npm start` no `package. arquivo son`,
+você notará que o comando real que inicia o aplicativo é
+`node . bin/www`, que costumava ser `node app.js`
+no Express 3.
+
+Porque o arquivo `app.js` que foi gerado pelo gerador Express 4
+agora é um Node. Módulo s não pode mais ser iniciado de forma independente como um aplicativo
+(a menos que você modifique o código). O módulo deve ser carregado em um arquivo Node.js
+e iniciado via arquivo Node.js. O arquivo Node.js é `./bin/www`
+neste caso.
+
+Nem o diretório `bin` nem o arquivo `www`
+sem extensão são obrigatórios para a criação de um aplicativo Express ou para iniciar o aplicativo. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+Para se livrar do diretório `www` e manter as coisas no caminho "Express 3",
+apague a linha que diz `módulo. xports = app;` no final do arquivo
+`app.js`, e então cole o seguinte código em seu lugar:
+
+```js
+app.set('port', process.env.PORT →3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Expresse servidor escutando na porta ' + server.address().port);
+});
+```
+
+Certifique-se de carregar o módulo `debug` no topo do arquivo `app.js` usando o seguinte código:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Em seguida, mude `"start": "node ./bin/www"` no arquivo `package.json` para `"start": "node app.js"`.
+
+Você moveu a funcionalidade `./bin/www` de volta para
+`app.js`. Esta mudança não é recomendada, mas o exercício ajuda você
+a entender como o `. arquivo bin/www` funciona, e porque o arquivo `app.js`
+não inicia mais por conta própria.
diff --git a/src/content/pages/pt-br/guide/migrating-5.mdx b/src/content/pages/pt-br/guide/migrating-5.mdx
new file mode 100644
index 0000000000..6236f46038
--- /dev/null
+++ b/src/content/pages/pt-br/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Movendo para Expresso 5
+description: Um guia completo para migrar seus aplicativos Express.js da versão 4 a 5, detalhando alterações quebraduras, métodos obsoletos e novas melhorias.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Expresso 5 não é muito diferente do Express 4; embora ele mantenha a mesma API básica, ainda há mudanças que quebram a compatibilidade com a versão anterior. Portanto, um aplicativo construído com Express 4 pode não funcionar se você atualizá-lo para usar o Express 5.
+
+Para instalar esta versão, você precisa ter uma versão 18 ou superior de Node.js. Em seguida, execute o seguinte comando em seu diretório de aplicativos:
+
+```sh
+npm install "express@5"
+```
+
+Você pode então executar seus testes automatizados para ver o que falhou e corrigir problemas de acordo com as atualizações listadas abaixo. Após falhas no teste, execute seu aplicativo para ver quais erros ocorrem. Você vai descobrir imediatamente se o aplicativo usa quaisquer métodos ou propriedades que não são suportadas.
+
+## Expresse 5 Codemods
+
+Para ajudá-lo a migrar seu servidor expresso, nós criamos um conjunto de codemods que irão ajudá-lo a atualizar automaticamente seu código para a última versão do Express.
+
+Execute o seguinte comando para executar todos os codemods disponíveis:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+Se você quiser executar um código específico, você pode executar o seguinte comando:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+Você pode encontrar a lista de codemods disponíveis [here](https://codemod.link/express).
+
+## Mudanças no Express 5
+
+**Métodos e propriedades removidos**
+
+<ul class="doclist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Nomes de métodos plurais</a>
+  </li>
+  <li>
+    <a href="#leading">Evoluindo dois pontos no argumento de nome para app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(nome)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('voltar') e res.location('voltar')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">expresso: roteador depurar logs</a>
+  </li>
+</ul>
+
+**Mudou**
+
+<ul class="doclist">
+  <li>
+    <a href="#path-syntax">Caminho de rota correspondente à sintaxe</a>
+  </li>
+  <li>
+    U<a href="#rejected-promises">promessas rejeitadas tratadas de middleware e manipuladores</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Melhorias**
+
+<ul class="doclist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Suporte a codificação Brotli</a>
+  </li>
+</ul>
+
+## Métodos e propriedades removidos
+
+Se você usar qualquer um desses métodos ou propriedades em seu aplicativo, ele irá falhar. Então, você precisará alterar seu aplicativo depois que você atualizar para a versão 5.
+
+### app.del()
+
+Expresso 5 não suporta mais a função `app.del()`. Se você usa essa função, um erro é lançado. Para registrar as rotas HTTP DELETE, use a função `app.delete()`.
+
+Inicialmente, `del` foi usado em vez de `delete`, porque `delete` é uma palavra-chave reservada em JavaScript. Entretanto, a partir do ECMAScript 6, `apagar` e outras palavras-chave reservadas podem ser usadas legalmente como nomes de propriedades.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.elete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+A assinatura `app.param(fn)` foi usada para modificar o comportamento da função `app.param(name, fn)`. Está obsoleto desde a versão 4.11.0, e Express 5 não apoia mais nada.
+
+### Nomes de métodos plurais
+
+Os nomes dos seguintes métodos foram pluralizados. No Express 4, a utilização dos métodos antigos resultou em um aviso de depreciação. Expresso 5 não os suporta de forma alguma:
+
+`req.acceptsCharset()` foi substituído por `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` é substituído por `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` foi substituído por `req.acceptsLanguages()`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.cceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.ll('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### Posicionando dois pontos (:) no nome do app.param(name, fn)
+
+Um personagem com dois pontos principais (:) no nome do `app. aram(name, fn)` é um remanescente do Express 3, e por uma questão de compatibilidade retrógrada, Express 4 apoiou-o com um aviso de depreciação. Expresso 5 irá ignorá-lo silenciosamente e usar o parâmetro de nome sem prefixá-lo com dois-pontos.
+
+Isso não deve afetar o seu código se você seguir a documentação Express 4 do [app.param](/en/4x/api#app.param), uma vez que não faz qualquer menção ao casal principal.
+
+### req.param(nome)
+
+Este método potencialmente confuso e perigoso de recuperação de dados de formulários foi removido. Agora você precisará procurar especificamente o nome do parâmetro enviado em `req.params`, `req.body`, ou `req.query`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.aram('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.d;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, status)
+
+Expresso 5 não suporta mais a assinatura `res.json(obj, status)`. Ao invés disso, defina o status e então encadee-o ao método `res.json()` como este: `res.status(status).json(obj)`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+aplicativo.ost('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Expresso 5 não suporta mais a assinatura `res.jsonp(obj, status)`. Ao invés disso, defina o status e então encadee-o ao método `res.jsonp()` como este: `res.status(status).jsonp(obj)`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Expresso 5 não suporta mais a assinatura `res.redirect(url, status)`. Ao invés disso, use a seguinte assinatura: `res.redirect(status, url)`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('voltar') e res.location('voltar')
+
+Expresse 5 não suporta mais a string mágica `back` nos métodos `res.redirect()` e `res.location()`. Ao invés disso, use o valor `req.get('Referrer') ahead '/'` para redirecionar de volta para a página anterior. No Express 4, os métodos `res.redirect('back')` e `res.location('back')` foram descontinuados.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app. et('/user', (req, res) => {
+  res.redirect(req.get('Referrer') ├'/');
+});
+```
+
+### res.send(corpo estado)
+
+Expresso 5 não suporta mais a assinatura `res.send(obj, status)`. Em vez disso, defina o status e então encadeie com o método `res.send()` como este: `res.status(status).send(obj)`.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.et('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status)
+
+Expresso 5 não suporta mais a assinatura `res.send(status)`, onde `status` é um número. Ao invés disso, use os `res. função endStatus(statusCode)`, que define o código de status do cabeçalho de resposta HTTP e envia o texto da versão do código: "Não encontrado", "Erro interno do servidor", e assim por diante.
+Se você precisar enviar um número usando os `res. função end()`, cita o número para convertê-lo em uma string, para que o Express não interprete como uma tentativa de usar a antiga assinatura não suportada.
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+A função `res.sendfile()` foi substituída por uma versão caída por camelo `res.sendFile()` no Express 5.
+
+**Nota:** No Expresso 5, `res. endFile()` usa o pacote `mime-types` para detecção do tipo MIME que retorna valores diferentes de Content-Type que Expresso 4 para vários tipos de arquivo comuns:
+
+- Arquivos JavaScript (.js): agora "text/javascript" ao invés de "application/javascript"
+- Arquivos JSON (.json): agora "application/json" em vez de "text/json"
+- Arquivos CSS (.css): agora "text/css" em vez de "text/plain"
+- Arquivos XML (.xml): agora "application/xml" em vez de "text/xml"
+- Arquivos de fonte (.woff): agora "font/woff" em vez de "application/font-woff"
+- Arquivos SVG (.svg): agora "image/svg+xml" em vez de "application/svg+xml"
+
+<Alert type="informações">
+Você pode substituir as assinaturas obsoletas pelo seguinte comando:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+A assinatura `router.param(fn)` foi usada para modificar o comportamento da função `router.param(name, fn)`. Está obsoleto desde a versão 4.11.0, e Express 5 não apoia mais nada.
+
+### express.static.mime
+
+No Express 5, `mime` não é mais uma propriedade exportada do campo `static`.
+Use o [pacote `mime-types`](https://github.com/jshttp/mime-types) para trabalhar com valores do tipo MIME.
+
+**Importante:** Esta alteração afeta não apenas o uso direto de `express.static.mime`, mas também outros métodos Express que dependem da detecção de tipo MIME como `res.sendFile()`. Os seguintes tipos MIME mudaram de Express 4:
+
+- Arquivos JavaScript (.js): agora servido como "text/javascript" em vez de "application/javascript"
+- Arquivos JSON (.json): agora servido como "application/json" em vez de "text/json"
+- Arquivos CSS (.css): agora servido como "text/css" em vez de "text/plain"
+- Arquivos HTML (): agora servido como "text/html; charset=utf-8" ao invés de apenas "text/html"
+- Arquivos XML (.xml): agora servido como "application/xml" ao invés de "text/xml"
+- Arquivos de fonte (.woff): agora servido como "font/woff" em vez de "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### expressão:roteador logs de depuração
+
+No Express 5, a lógica de manipulação do roteador é realizada por uma dependência. Portanto, os logs de depuração
+para o roteador não estão mais disponíveis sob o namespace 'expresso'.
+No v4, os logs estavam disponíveis sob os namespaces `express:router`, `express:router:layer`,
+e `express:router:route`. Todos esses foram incluídos sob o namespace `express:*`.
+Na v5.1+, os logs estão disponíveis sob o namespaces `router`, `router:layer` e `router:route`.
+Os logs de `roteador:layer` e `router:route` estão incluídos no namespace `router:*`.
+Para alcançar os mesmos detalhes do log de depuração ao usar `express:*` no v4, use uma combinação de
+`express:*`, `router` e `router:*`.
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,router:* node index.js
+```
+
+## Alterado
+
+### Caminho de rota correspondente
+
+A sintaxe de rota de correspondência de um caminho é quando uma string é fornecida como o primeiro parâmetro para o `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. As seguintes alterações foram feitas em como a seqüência de caracteres de caminho é combinada para uma solicitação de entrada:
+
+- O caractere curinga `*` deve ter um nome, correspondendo ao comportamento dos parâmetros `:`, use `/*splat` em vez de `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.et('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="informações">
+`*splat` corresponde a qualquer caminho sem o caminho raiz. Caso você precise coincidir com o caminho raiz também `/`, você pode usar `/{*splat}`, envolvendo o caractere curinga nos quadros.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- O caractere opcional `?` não é mais suportado, use chaves em vez disso.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Caracteres Regexp não são suportados. Por exemplo:
+
+```js
+app.get('/[discussionőpage]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+deve ser alterado para:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Alguns personagens foram reservados para evitar confusão durante a atualização (`()[]?+!`), use `\` para escapá-los.
+- Os nomes de parâmetros agora suportam identificadores JavaScript válidos, ou citados como `:"isto"`.
+
+### promessas rejeitadas tratadas de intermediários e manipuladores
+
+Solicite aos manipuladores e manipuladores que retornam promessas rejeitadas agora são tratados encaminhando o valor rejeitado como um `Erro` para o erro de manipulação do middleware. Isto significa que usar funções `async` como middleware e manipuladores são mais fáceis do que nunca. Quando um erro é lançado em uma função `async` ou uma promessa rejeitada é `aguardada` dentro de uma função async esses erros serão passados para o manipulador de erro como se chamando `next(err)`.
+
+Detalhes de como Expresso lida com os erros está coberto na [documentação de manipulação de erro](/en/guide/error-handling).
+
+### expres.urlencoded
+
+O método `express.urlencoded` torna a opção `estendida` `false` por padrão.
+
+### dotfiles express.static
+
+No Expresso 5, a opção `express.static` do middleware `dotfiles` agora padrão é `"ignore"`. Isto é uma alteração do Express 4, onde os dotfiles foram servidos por padrão. Como resultado, arquivos dentro de um diretório que começa com um ponto (`.`), como `. ell-known`, não será mais acessível e retornará um erro **404 Não Encontrado**. Isso pode quebrar funcionalidade que depende de servir diretórios de pontos, como Android App Links, e Apple Universal Links.
+
+Exemplo de código de quebra:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+Depois de migrar para o Express 5, um pedido para `/.well-known/assetlinks.json` resultará em uma **404 Não Encontrado**.
+
+Para corrigir isso, sirva diretórios de pontos específicos usando explicitamente os `dotfiles: "allow"` option:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+Esta abordagem permite que você sirva com segurança apenas os diretórios de pontos pretendidos, mantendo o comportamento seguro padrão para outros dotfiles, que permanecem inacessíveis.
+
+### Ouvir
+
+No Express 5, o método `app.listen` invocará a função de callback fornecido pelo usuário (se fornecido) quando o servidor receber um evento de erro. Na Expressa 4, esses erros seriam lançados. Essa mudança desloca a responsabilidade da manipulação de erros para a função de retorno de chamada no Express 5. Se houver um erro, ele será passado para o callback como argumento.
+Por exemplo:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw erro; // ex. EADDRINUSE
+  }
+  console.log(`Ouvindo em ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+O objeto `app.router`, que foi removido no Express 4, retornou no Express 5. Na nova versão, este objeto é apenas uma referência ao roteador básico Express, Ao contrário do Express 3, onde um aplicativo teve que carregá-lo explicitamente.
+
+### req.corpo
+
+A propriedade `req.body` retorna `undefined` quando o corpo não foi analisado. No Express 4, por padrão ele retorna `{}`.
+
+### req.anfitrião
+
+No Express 4, a função `req.host` incorretamente retirou o número da porta se estivesse presente. No Express 5, o número da porta é mantido.
+
+### req.params
+
+O objeto `req.params` agora tem um **protótipo nulo** ao usar caminhos de string. No entanto, se o caminho é definido com uma expressão regular, `req.params` permanece um objeto padrão com um protótipo normal. Além disso, existem duas mudanças comportamentais importantes:
+
+**Os parâmetros coringa agora são arrays:**
+
+Caracteres curinga (por exemplo, `/*splat`) capturam segmentos de caminho como um array em vez de uma única string.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.arams);
+  // => [Objeto: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Parâmetros não correspondentes são omitidos:**
+
+No Expresso 4, os caracteres curinga eram strings vazias (`''`) e parâmetros opcionais `:` (usando `?`) tinham uma chave com valor `undefined`. No Expresso 5, parâmetros não correspondentes são completamente omitidos de `req.params`.
+
+```js
+// v4: curinga sem comparação é uma string vazia
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.arams);
+  // => { '0': '' }
+});
+
+// v4: parâmetro opcional não correspondente é indefinido
+aplicativo.et('/:file.:ext?', (req, res) => {
+  // GET /image
+  console.ir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: param opcional não comparado é omitido
+app.get('/:file{. ext}', (req, res) => {
+  // GET /image
+  console.dir(req.arams);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.consulta
+
+A propriedade `req.query` não é mais uma propriedade gravável e em vez disso é um getter. O analisador de consulta padrão foi alterado de "estendido" para "simples".
+
+### res.clearCookie
+
+O método `res.clearCookie` ignora as opções `maxAge` e `expires` fornecidas pelo usuário.
+
+### status.res.status
+
+O método `res.status` só aceita inteiros no intervalo de `100` para `999`, seguindo o comportamento definido pelo Node. , e retorna um erro quando o código de status não é um inteiro.
+
+### variável.variação
+
+O 'res.vary' lança um erro quando o argumento 'field' está faltando. No Express 4, se o argumento foi omitido, ele deu um aviso no console
+
+## Melhorias
+
+### res.render()
+
+Este método agora exige comportamento assíncrono para todos os motores de visualização, evitando erros causados por mecanismos de visualização que tiveram uma implementação síncrona e que violaram a interface recomendada.
+
+### Suporte à codificação Brotli
+
+Expresso 5 suporta a codificação Brotli para solicitações recebidas de clientes que suportam isso.
diff --git a/src/content/pages/pt-br/resources/glossary.mdx b/src/content/pages/pt-br/resources/glossary.mdx
new file mode 100644
index 0000000000..f0572e24fe
--- /dev/null
+++ b/src/content/pages/pt-br/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: Um glossário abrangente de termos relacionados ao Express.js, Node.js, middleware, routing e outros conceitos-chave para ajudá-lo a entender e usar o Express eficazmente.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### aplicativo
+
+Em geral, um ou mais programas que são projetados para realizar operações para uma finalidade específica. No contexto da Express, um programa que usa o API Express executando na plataforma Node.js. Também pode se referir a um [objeto do aplicativo](/en/api#express).
+
+### API
+
+Interface de programação de aplicativos. Feitiço a abreviação quando ela for usada pela primeira vez.
+
+### Expresso
+
+Uma rápida, não-opinionada e minimalista estrutura web para aplicativos Node.js. Em geral, "Expresso" é preferida a "Express.js", embora este último seja aceitável.
+
+### libuv
+
+Uma biblioteca de suporte multiplataforma focada em E/O assíncrono, desenvolvida principalmente para uso pelo Node.js.
+
+### middleware
+
+Uma função que é invocada pela camada de roteamento Express antes do manipulador de requisições final, e assim situa-se no meio entre um pedido em bruto e a rota final pretendida. Alguns belos pontos de terminologia em torno do middleware:
+
+- `var foo = require('middleware')` é chamado de _requiring_ ou _usando_ um módulo Node.js. Então, a instrução `var mw = foo()` normalmente retorna o middleware.
+- `app.use(mw)` é chamado de _adicionando o middleware à pilha de processamento global_.
+- `app.get('/foo', mw, função (req, res) { ... })` é chamado de _adicionando o middleware para a pilha de processamento "GET /foo"_.
+
+### Node.js
+
+Uma plataforma de software usada para construir aplicações de rede escaláveis. Node.js usa JavaScript como sua linguagem de script e alcança alta taxa de transferência através de I/O não bloqueando e de um loop de eventos uni-la-thread. Ver [nodejs.org](https://nodejs.org/en/). **Nota de uso**: Inicialmente, "Node.js", em seguida, "Node".
+
+### código aberto, código aberto
+
+Quando usado como adjetivo, hífene; por exemplo: "Este é um software de código aberto". Veja [Software de código aberto na Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="informações">
+
+Embora seja comum não fazer hifenização deste termo, estamos usando as regras padrão em inglês para
+hifenização de um adjetivo composto.
+
+</Alert>
+
+### solicitação
+
+Um pedido HTTP. Um cliente envia uma mensagem de solicitação HTTP para um servidor, que retorna uma resposta. A solicitação deve usar um dos vários [métodos de requisição](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) como GET, POST, e assim por diante.
+
+### Resposta
+
+Uma resposta HTTP. Um servidor retorna uma mensagem de resposta HTTP para o cliente. A resposta contém informações de estado de conclusão sobre o pedido e também pode conter conteúdo solicitado em seu corpo da mensagem.
+
+### rota
+
+Parte de uma URL que identifica um recurso. Por exemplo, em `http://foo.com/products/id`, "/products/id" é a rota.
+
+### roteador
+
+Ver [router](/en/api#router) na referência da API.
diff --git a/src/content/pages/pt-br/resources/utils.md b/src/content/pages/pt-br/resources/utils.md
new file mode 100644
index 0000000000..7bcafd69dd
--- /dev/null
+++ b/src/content/pages/pt-br/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Utilidades Expressas
+description: Descubra módulos de utilitários relacionados ao Express.js e Node.js, incluindo ferramentas para cookies, proteção CSRF, análise de URLs, roteamento e muito mais para melhorar seus aplicativos.
+---
+
+## Funções do utilitário expresso
+
+A organização [pillarjs](https://github.com/pillarjs) do GitHub contém um número de módulos
+para funções utilitárias que podem ser úteis em geral.
+
+| Módulos utilitários                                            | Descrição:                                                                                                                                                                   |
+| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Obter e definir cookies HTTP(S) que podem ser assinados para evitar manipulação, usando Keygrip. Pode ser usado com a biblioteca HTTP do Node.js ou como Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contém a lógica por trás da criação e verificação de tokens CSRF. Use este módulo para criar um middleware de CSRF personalizado.                                            |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Função a invocar como o passo final para responder a requisição HTTP.                                                                                                        |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Analisar uma URL com cache.                                                                                                                                                  |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Transforme uma string de caminho estilo Express, como \`\`/user/:name\` em uma expressão regular.                                                                            |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolve um caminho relativo contra um caminho raiz com validação.                                                                                                            |
+| [router](https://www.npmjs.com/package/router)                 | Roteador simples ao estilo de middleware.                                                                                                                                    |
+| [send](https://www.npmjs.com/package/send)                     | Biblioteca para streaming de arquivos como uma resposta HTTP, com suporte para respostas parciais (intervalos), negociação condicional-GET e eventos granulares.             |
+
+Para módulos adicionais de baixo nível relacionados à HTTP, consulte [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/pt-br/support.md b/src/content/pages/pt-br/support.md
new file mode 100644
index 0000000000..3687ec8365
--- /dev/null
+++ b/src/content/pages/pt-br/support.md
@@ -0,0 +1,23 @@
+---
+title: Suporte à Versão
+description: Encontre informações sobre o cronograma de suporte para diferentes versões do Express.js, incluindo quais versões são atualmente mantidas e políticas em fim de vida.
+---
+
+Somente a versão mais recente de qualquer linha de lançamento principal é suportada.
+
+Versões que são EOL (fim de vida) _pode_ receber atualizações de vulnerabilidades de segurança críticas, mas a equipe Express não oferece garantia e não planeja endereçar ou liberar correções para quaisquer problemas encontrados.
+
+| Versão maior           | Versão mínima do Node.js | Início Suporte   | Término Suporte  |
+| ---------------------- | ------------------------ | ---------------- | ---------------- |
+| [**v5.x**](/en/5x/api) | 18                       | Setembro de 2024 | **em andamento** |
+| [**v4.x**](/en/4x/api) | 0.10.0                   | Abril de 2014    | **em andamento** |
+| [**v3.x**](/en/3x/api) | 0.8.0                    | Outubro de 2012  | Julho de 2015    |
+| [**v2.x**](/2x/)       | 0.4.1                    | Março de 2011    | Julho de 2012    |
+| **v1.x**               | 0.2.0                    | Dezembro de 2010 | Março de 2011    |
+| **v0.14.x**            | 0.1.98                   | Dezembro de 2010 | Dezembro de 2010 |
+
+## Opções de Suporte Comercial
+
+Se você não puder atualizar para uma versão suportada do Express, entre em contato com um de nossos parceiros para receber atualizações de segurança:
+
+- [Suporte para HeroDevs Final Interminável](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/content/pages/zh-tw/advanced/best-practice-performance.md b/src/content/pages/zh-tw/advanced/best-practice-performance.md
new file mode 100644
index 0000000000..a98c7fcf6a
--- /dev/null
+++ b/src/content/pages/zh-tw/advanced/best-practice-performance.md
@@ -0,0 +1,305 @@
+---
+title: 'Production best practices: performance and reliability'
+description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
+---
+
+This article discusses performance and reliability best practices for Express applications deployed to production.
+
+This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
+
+- Things to do in your code (the dev part):
+  - [Use gzip compression](#use-gzip-compression)
+  - [Don't use synchronous functions](#dont-use-synchronous-functions)
+  - [Do logging correctly](#do-logging-correctly)
+  - [Handle exceptions properly](#handle-exceptions-properly)
+- Things to do in your environment / setup (the ops part):
+  - [Set NODE_ENV to "production"](#set-node_env-to-production)
+  - [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+  - [Run your app in a cluster](#run-your-app-in-a-cluster)
+  - [Cache request results](#cache-request-results)
+  - [Use a load balancer](#use-a-load-balancer)
+  - [Use a reverse proxy](#use-a-reverse-proxy)
+
+## Things to do in your code
+
+Here are some things you can do in your code to improve your application's performance:
+
+- [Use gzip compression](#use-gzip-compression)
+- [Don't use synchronous functions](#dont-use-synchronous-functions)
+- [Do logging correctly](#do-logging-correctly)
+- [Handle exceptions properly](#handle-exceptions-properly)
+
+### Use gzip compression
+
+Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
+
+```js
+const compression = require('compression');
+const express = require('express');
+const app = express();
+
+app.use(compression());
+```
+
+For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. For details on enabling gzip compression in Nginx, see [Module ngx_http_gzip_module](http://nginx.org/en/docs/http/ngx_http_gzip_module) in the Nginx documentation.
+
+### Don't use synchronous functions
+
+Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
+
+Although Node and many modules provide synchronous and asynchronous versions of their functions, always use the asynchronous version in production. The only time when a synchronous function can be justified is upon initial startup.
+
+You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli#cli_trace_sync_io) for more information.
+
+### Do logging correctly
+
+In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
+
+#### For debugging
+
+If you're logging for purposes of debugging, then instead of using `console.log()`, use a special debugging module like [debug](https://www.npmjs.com/package/debug). This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
+
+#### For app activity
+
+If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
+
+### Handle exceptions properly
+
+Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
+
+To ensure you handle all exceptions, use the following techniques:
+
+- [Use try-catch](#use-try-catch)
+- [Use promises](#use-promises)
+
+Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
+
+For more on the fundamentals of error handling, see:
+
+- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
+
+#### Use try-catch
+
+Try-catch is a JavaScript language construct that you can use to catch exceptions in synchronous code. Use try-catch, for example, to handle JSON parsing errors as shown below.
+
+Here is an example of using try-catch to handle a potential process-crashing exception.
+This middleware function accepts a query field parameter named "params" that is a JSON object.
+
+```js
+app.get('/search', (req, res) => {
+  // Simulating async operation
+  setImmediate(() => {
+    const jsonStr = req.query.params;
+    try {
+      const jsonObj = JSON.parse(jsonStr);
+      res.send('Success');
+    } catch (e) {
+      res.status(400).send('Invalid JSON string');
+    }
+  });
+});
+```
+
+However, try-catch works only for synchronous code. Because the Node platform is primarily asynchronous (particularly in a production environment), try-catch won't catch a lot of exceptions.
+
+#### Use promises
+
+When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
+
+```js
+app.get('/', async (req, res, next) => {
+  const data = await userData(); // If this promise fails, it will automatically call `next(err)` to handle the error.
+
+  res.send(data);
+});
+
+app.use((err, req, res, next) => {
+  res.status(err.status ?? 500).send({ error: err.message });
+});
+```
+
+Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
+
+```js
+app.use(async (req, res, next) => {
+  req.locals.user = await getUser(req);
+
+  next(); // This will be called if the promise does not throw an error.
+});
+```
+
+Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
+
+#### What not to do
+
+One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
+
+Additionally, using `uncaughtException` is officially recognized as [crude](https://nodejs.org/api/process#process_event_uncaughtexception). So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
+
+We also don't recommend using [domains](https://nodejs.org/api/domain). It generally doesn't solve the problem and is a deprecated module.
+
+## Things to do in your environment / setup
+
+Here are some things you can do in your system environment to improve your app's performance:
+
+- [Set NODE_ENV to "production"](#set-node_env-to-production)
+- [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts)
+- [Run your app in a cluster](#run-your-app-in-a-cluster)
+- [Cache request results](#cache-request-results)
+- [Use a load balancer](#use-a-load-balancer)
+- [Use a reverse proxy](#use-a-reverse-proxy)
+
+### Set NODE_ENV to "production"
+
+The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
+
+Setting NODE_ENV to "production" makes Express:
+
+- Cache view templates.
+- Cache CSS files generated from CSS extensions.
+- Generate less verbose error messages.
+
+[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
+
+If you need to write environment-specific code, you can check the value of NODE_ENV with `process.env.NODE_ENV`. Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
+
+In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
+
+With systemd, use the `Environment` directive in your unit file. For example:
+
+```sh
+
+Environment=NODE_ENV=production
+```
+
+For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
+
+### Ensure your app automatically restarts
+
+In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
+
+- Using a process manager to restart the app (and Node) when it crashes.
+- Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
+
+Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
+
+#### Use a process manager
+
+In development, you started your app simply from the command line with `node server.js` or something similar. But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
+
+In addition to restarting your app when it crashes, a process manager can enable you to:
+
+- Gain insights into runtime performance and resource consumption.
+- Modify settings dynamically to improve performance.
+- Control clustering (pm2).
+
+Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
+
+#### Use an init system
+
+The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
+
+There are two ways to use init systems with your Express app:
+
+- Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
+- Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
+
+##### Systemd
+
+Systemd is a Linux system and service manager. Most major Linux distributions have adopted systemd as their default init system.
+
+A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
+
+```sh
+[Unit]
+Description=<Awesome Express App>
+
+[Service]
+Type=simple
+ExecStart=/usr/local/bin/node </projects/myapp/index.js>
+WorkingDirectory=</projects/myapp>
+
+User=nobody
+Group=nogroup
+
+
+Environment=NODE_ENV=production
+
+
+LimitNOFILE=infinity
+
+
+LimitCORE=infinity
+
+StandardInput=null
+StandardOutput=syslog
+StandardError=syslog
+Restart=always
+
+[Install]
+WantedBy=multi-user.target
+```
+
+For more information on systemd, see the [systemd reference (man page)](http://www.freedesktop.org/software/systemd/man/systemd.unit).
+
+### Run your app in a cluster
+
+In a multi-core system, you can increase the performance of a Node app by many times by launching a cluster of processes. A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
+
+![Balancing between application instances using the cluster API](/images/clustering.png)
+
+IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
+
+In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
+
+#### Using Node's cluster module
+
+Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
+
+#### Using PM2
+
+If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
+
+When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
+
+To enable cluster mode, start your application like so:
+
+```bash
+
+$ pm2 start npm --name my-app -i 4 -- start
+
+$ pm2 start npm --name my-app -i max -- start
+```
+
+This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
+
+Once running, the application can be scaled like so:
+
+```bash
+
+$ pm2 scale my-app +3
+
+$ pm2 scale my-app 2
+```
+
+For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
+
+### Cache request results
+
+Another strategy to improve the performance in production is to cache the result of requests, so that your app does not repeat the operation to serve the same request repeatedly.
+
+Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
+
+### Use a load balancer
+
+No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
+
+A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
+
+With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
+
+### Use a reverse proxy
+
+A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
+
+Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/src/content/pages/zh-tw/advanced/best-practice-security.mdx b/src/content/pages/zh-tw/advanced/best-practice-security.mdx
new file mode 100644
index 0000000000..4ca68c5122
--- /dev/null
+++ b/src/content/pages/zh-tw/advanced/best-practice-security.mdx
@@ -0,0 +1,276 @@
+---
+title: 'Production Best Practices: Security'
+description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
+
+Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+Security best practices for Express applications in production include:
+
+- [Production Best Practices: Security](#production-best-practices-security)
+  - [Overview](#overview)
+  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
+  - [Use TLS](#use-tls)
+  - [Do not trust user input](#do-not-trust-user-input)
+    - [Prevent open redirects](#prevent-open-redirects)
+  - [Use Helmet](#use-helmet)
+  - [Reduce fingerprinting](#reduce-fingerprinting)
+  - [Use cookies securely](#use-cookies-securely)
+    - [Don't use the default session cookie name](#dont-use-the-default-session-cookie-name)
+    - [Set cookie security options](#set-cookie-security-options)
+  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
+  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
+    - [Avoid other known vulnerabilities](#avoid-other-known-vulnerabilities)
+  - [Additional considerations](#additional-considerations)
+
+## Don't use deprecated or vulnerable versions of Express
+
+Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/en/guide/migrating-4) or consider [Commercial Support Options](/en/support#commercial-support-options).
+
+Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/en/advanced/security-updates). If you are, update to one of the stable releases, preferably the latest.
+
+## Use TLS
+
+If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
+
+You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](<https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515(v=vs.85).aspx>). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
+
+Also, a handy tool to get a free TLS certificate is [Let's Encrypt](https://letsencrypt.org/about/), a free, automated, and open certificate authority (CA) provided by the [Internet Security Research Group (ISRG)](https://www.abetterinternet.org/).
+
+## Do not trust user input
+
+For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
+Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
+
+### Prevent open redirects
+
+An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
+return a 3xx status.
+
+An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
+
+Here is an example of checking URLs before using `res.redirect` or `res.location`:
+
+```js
+app.use((req, res) => {
+  try {
+    if (new Url(req.query.url).host !== 'example.com') {
+      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`);
+    }
+  } catch (e) {
+    return res.status(400).end(`Invalid url: ${req.query.url}`);
+  }
+  res.redirect(req.query.url);
+});
+```
+
+## Use Helmet
+
+[Helmet][helmet] can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately.
+
+Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
+
+- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
+- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
+- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
+- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
+- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
+- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
+- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
+- `X-DNS-Prefetch-Control`: Controls DNS prefetching
+- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
+- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
+- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
+- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
+- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
+
+Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
+
+Install Helmet like any other module:
+
+```bash
+$ npm install helmet
+```
+
+Then to use it in your code:
+
+```js
+// ...
+
+const helmet = require('helmet');
+app.use(helmet());
+
+// ...
+```
+
+## Reduce fingerprinting
+
+It can help to provide an extra layer of security to reduce the ability of attackers to determine
+the software that a server uses, known as "fingerprinting." Though not a security issue itself,
+reducing the ability to fingerprint an application improves its overall security posture.
+Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
+the HTTP response headers.
+
+By default, Express sends the `X-Powered-By` response header that you can
+disable using the `app.disable()` method:
+
+```js
+app.disable('x-powered-by');
+```
+
+<Alert type="info">
+
+Disabling the `X-Powered-By header` does not prevent a sophisticated attacker from determining
+that an app is running Express. It may discourage a casual exploit, but there are other ways to
+determine an app is running Express.
+
+</Alert>
+
+Express also sends its own formatted "404 Not Found" messages and formatter error
+response messages. These can be changed by
+[adding your own not found handler](/en/starter/faq#how-do-i-handle-404-responses)
+and
+[writing your own error handler](/en/guide/error-handling#writing-error-handlers):
+
+```js
+// last app.use calls right before app.listen():
+
+// custom 404
+app.use((req, res, next) => {
+  res.status(404).send("Sorry can't find that!");
+});
+
+// custom error handler
+app.use((err, req, res, next) => {
+  console.error(err.stack);
+  res.status(500).send('Something broke!');
+});
+```
+
+## Use cookies securely
+
+To ensure cookies don't open your app to exploits, don't use the default session cookie name and set cookie security options appropriately.
+
+There are two main middleware cookie session modules:
+
+- [express-session](https://www.npmjs.com/package/express-session) that replaces `express.session` middleware built-in to Express 3.x.
+- [cookie-session](https://www.npmjs.com/package/cookie-session) that replaces `express.cookieSession` middleware built-in to Express 3.x.
+
+The main difference between these two modules is how they save cookie session data. The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
+
+In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
+
+### Don't use the default session cookie name
+
+Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
+
+To avoid this problem, use generic cookie names; for example using [express-session](https://www.npmjs.com/package/express-session) middleware:
+
+```js
+const session = require('express-session');
+app.set('trust proxy', 1); // trust first proxy
+app.use(
+  session({
+    secret: 's3Cur3',
+    name: 'sessionId',
+  })
+);
+```
+
+### Set cookie security options
+
+Set the following cookie options to enhance security:
+
+- `secure` - Ensures the browser only sends the cookie over HTTPS.
+- `httpOnly` - Ensures the cookie is sent only over HTTP(S), not client JavaScript, helping to protect against cross-site scripting attacks.
+- `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
+- `path` - indicates the path of the cookie; use it to compare against the request path. If this and domain match, then send the cookie in the request.
+- `expires` - use to set expiration date for persistent cookies.
+
+Here is an example using [cookie-session](https://www.npmjs.com/package/cookie-session) middleware:
+
+```js
+const session = require('cookie-session');
+const express = require('express');
+const app = express();
+
+const expiryDate = new Date(Date.now() + 60 * 60 * 1000); // 1 hour
+app.use(
+  session({
+    name: 'session',
+    keys: ['key1', 'key2'],
+    cookie: {
+      secure: true,
+      httpOnly: true,
+      domain: 'example.com',
+      path: 'foo/bar',
+      expires: expiryDate,
+    },
+  })
+);
+```
+
+## Prevent brute-force attacks against authorization
+
+Make sure login endpoints are protected to make private data more secure.
+
+A simple and powerful technique is to block authorization attempts using two metrics:
+
+1. The number of consecutive failed attempts by the same user name and IP address.
+2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
+
+[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
+
+## Ensure your dependencies are secure
+
+Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
+
+Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
+
+```bash
+$ npm audit
+```
+
+If you want to stay more secure, consider [Snyk](https://snyk.io/).
+
+Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
+
+```bash
+$ npm install -g snyk
+$ cd your-app
+```
+
+Use this command to test your application for vulnerabilities:
+
+```bash
+$ snyk test
+```
+
+### Avoid other known vulnerabilities
+
+Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
+
+Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
+
+## Additional considerations
+
+Here are some further recommendations from the excellent [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/). Refer to that blog post for all the details on these recommendations:
+
+- Always filter and sanitize user input to protect against cross-site scripting (XSS) and command injection attacks.
+- Defend against SQL injection attacks by using parameterized queries or prepared statements.
+- Use the open-source [sqlmap](http://sqlmap.org/) tool to detect SQL injection vulnerabilities in your app.
+- Use the [nmap](https://nmap.org/) and [sslyze](https://github.com/nabla-c0d3/sslyze) tools to test the configuration of your SSL ciphers, keys, and renegotiation as well as the validity of your certificate.
+- Use [safe-regex](https://www.npmjs.com/package/safe-regex) to ensure your regular expressions are not susceptible to [regular expression denial of service](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS) attacks.
+
+[helmet]: https://helmetjs.github.io/
diff --git a/src/content/pages/zh-tw/advanced/healthcheck-graceful-shutdown.md b/src/content/pages/zh-tw/advanced/healthcheck-graceful-shutdown.md
new file mode 100644
index 0000000000..c060e58605
--- /dev/null
+++ b/src/content/pages/zh-tw/advanced/healthcheck-graceful-shutdown.md
@@ -0,0 +1,28 @@
+---
+title: Health Checks and Graceful Shutdown
+description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
+---
+
+## Graceful shutdown
+
+When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used, including database connections and file locks then exit.
+
+### Example
+
+```js
+const server = app.listen(port);
+
+process.on('SIGTERM', () => {
+  debug('SIGTERM signal received: closing HTTP server');
+  server.close(() => {
+    debug('HTTP server closed');
+  });
+});
+```
+
+## Health checks
+
+A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
+
+- `liveness`, that determines when to restart a container.
+- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
diff --git a/src/content/pages/zh-tw/advanced/security-updates.mdx b/src/content/pages/zh-tw/advanced/security-updates.mdx
new file mode 100644
index 0000000000..c5ea3f336a
--- /dev/null
+++ b/src/content/pages/zh-tw/advanced/security-updates.mdx
@@ -0,0 +1,87 @@
+---
+title: Security updates
+description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+<Alert type="alert">
+
+Node.js vulnerabilities directly affect Express. Therefore, keep a watch on Node.js
+vulnerabilities and make sure you are using the latest
+stable version of Node.js.
+
+</Alert>
+
+The list below enumerates the Express vulnerabilities that were fixed in the specified version update.
+
+<Alert type="info">
+
+If you believe you have discovered a security vulnerability in Express, please see Security
+Policies and Procedures.
+
+</Alert>
+
+## 4.x
+
+- 4.21.2
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
+- 4.21.1
+  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
+- 4.20.0
+  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
+  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
+  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
+  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
+  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
+- 4.19.0, 4.19.1
+  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
+- 4.17.3
+  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
+- 4.16.0
+  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
+  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
+  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
+- 4.15.5
+  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
+  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
+- 4.15.3
+  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
+- 4.15.2
+  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
+- 4.11.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 4.10.7
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 4.8.8
+  - Fixed directory traversal vulnerabilities in `express.static` ([advisory](http://npmjs.com/advisories/32) , [CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)).
+- 4.8.4
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 4.8.0
+  - Sparse arrays that have extremely high indexes in the query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+
+## 3.x
+
+<Alert type="warning">
+**Express 3.x IS END-OF-LIFE AND NO LONGER MAINTAINED**
+
+Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
+
+If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/en/support#commercial-support-options).
+
+</Alert>
+
+- 3.19.1
+  - Fixed root path disclosure vulnerability in `express.static`, `res.sendfile`, and `res.sendFile`
+- 3.19.0
+  - Fixed open redirect vulnerability in `express.static` ([advisory](https://npmjs.com/advisories/35), [CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)).
+- 3.16.10
+  - Fixed directory traversal vulnerabilities in `express.static`.
+- 3.16.6
+  - Node.js 0.10 can leak `fd`s in certain situations that affect `express.static` and `res.sendfile`. Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
+- 3.16.0
+  - Sparse arrays that have extremely high indexes in query string could cause the process to run out of memory and crash the server.
+  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
+- 3.3.0
+  - The 404 response of an unsupported method override attempt was susceptible to cross-site scripting attacks.
diff --git a/src/content/pages/zh-tw/guide/database-integration.mdx b/src/content/pages/zh-tw/guide/database-integration.mdx
new file mode 100644
index 0000000000..b0855e4a2a
--- /dev/null
+++ b/src/content/pages/zh-tw/guide/database-integration.mdx
@@ -0,0 +1,503 @@
+---
+title: Database integration
+description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
+
+- [Cassandra](#cassandra)
+- [Couchbase](#couchbase)
+- [CouchDB](#couchdb)
+- [LevelDB](#leveldb)
+- [MySQL](#mysql)
+- [MongoDB](#mongodb)
+- [Neo4j](#neo4j)
+- [Oracle](#oracle)
+- [PostgreSQL](#postgresql)
+- [Redis](#redis)
+- [SQL Server](#sql-server)
+- [SQLite](#sqlite)
+- [Elasticsearch](#elasticsearch)
+
+<Alert type="alert">
+
+These database drivers are among many that are available. For other options, search on the
+[npm](https://www.npmjs.com/) site.
+
+</Alert>
+
+## Cassandra
+
+**Module**: [cassandra-driver](https://github.com/datastax/nodejs-driver)
+
+### Installation
+
+```bash
+$ npm install cassandra-driver
+```
+
+### Example
+
+```js
+const cassandra = require('cassandra-driver');
+const client = new cassandra.Client({ contactPoints: ['localhost'] });
+
+client.execute('select key from system.local', (err, result) => {
+  if (err) throw err;
+  console.log(result.rows[0]);
+});
+```
+
+## Couchbase
+
+**Module**: [couchnode](https://github.com/couchbase/couchnode)
+
+### Installation
+
+```bash
+$ npm install couchbase
+```
+
+### Example
+
+```js
+const couchbase = require('couchbase');
+const bucket = new couchbase.Cluster('http://localhost:8091').openBucket('bucketName');
+
+// add a document to a bucket
+bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+
+// get all documents with shoe size 13
+const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1';
+const query = N1qlQuery.fromString(n1ql);
+bucket.query(query, [13], (err, result) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(result);
+  }
+});
+```
+
+## CouchDB
+
+**Module**: [nano](https://github.com/dscape/nano)
+
+### Installation
+
+```bash
+$ npm install nano
+```
+
+### Example
+
+```js
+const nano = require('nano')('http://localhost:5984');
+nano.db.create('books');
+const books = nano.db.use('books');
+
+// Insert a book document in the books database
+books.insert({ name: 'The Art of war' }, null, (err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body);
+  }
+});
+
+// Get a list of all books
+books.list((err, body) => {
+  if (err) {
+    console.log(err);
+  } else {
+    console.log(body.rows);
+  }
+});
+```
+
+## LevelDB
+
+**Module**: [levelup](https://github.com/rvagg/node-levelup)
+
+### Installation
+
+```bash
+$ npm install level levelup leveldown
+```
+
+### Example
+
+```js
+const levelup = require('levelup');
+const db = levelup('./mydb');
+
+db.put('name', 'LevelUP', (err) => {
+  if (err) return console.log('Ooops!', err);
+
+  db.get('name', (err, value) => {
+    if (err) return console.log('Ooops!', err);
+
+    console.log(`name=${value}`);
+  });
+});
+```
+
+## MySQL
+
+**Module**: [mysql](https://github.com/felixge/node-mysql/)
+
+### Installation
+
+```bash
+$ npm install mysql
+```
+
+### Example
+
+```js
+const mysql = require('mysql');
+const connection = mysql.createConnection({
+  host: 'localhost',
+  user: 'dbuser',
+  password: 's3kreee7',
+  database: 'my_db',
+});
+
+connection.connect();
+
+connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
+  if (err) throw err;
+
+  console.log('The solution is: ', rows[0].solution);
+});
+
+connection.end();
+```
+
+## MongoDB
+
+**Module**: [mongodb](https://github.com/mongodb/node-mongodb-native)
+
+### Installation
+
+```bash
+$ npm install mongodb
+```
+
+### Example (v2.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
+  if (err) throw err;
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+### Example (v3.\*)
+
+```js
+const MongoClient = require('mongodb').MongoClient;
+
+MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
+  if (err) throw err;
+
+  const db = client.db('animals');
+
+  db.collection('mammals')
+    .find()
+    .toArray((err, result) => {
+      if (err) throw err;
+
+      console.log(result);
+    });
+});
+```
+
+If you want an object model driver for MongoDB, look at [Mongoose](https://github.com/LearnBoost/mongoose).
+
+## Neo4j
+
+**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
+
+### Installation
+
+```bash
+$ npm install neo4j-driver
+```
+
+### Example
+
+```js
+const neo4j = require('neo4j-driver');
+const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'));
+
+const session = driver.session();
+
+session.readTransaction((tx) => {
+  return tx
+    .run('MATCH (n) RETURN count(n) AS count')
+    .then((res) => {
+      console.log(res.records[0].get('count'));
+    })
+    .catch((error) => {
+      console.log(error);
+    });
+});
+```
+
+## Oracle
+
+**Module**: [oracledb](https://github.com/oracle/node-oracledb)
+
+### Installation
+
+NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
+
+```bash
+$ npm install oracledb
+```
+
+### Example
+
+```js
+const oracledb = require('oracledb');
+const config = {
+  user: '<your db user>',
+  password: '<your db password>',
+  connectString: 'localhost:1521/orcl',
+};
+
+async function getEmployee(empId) {
+  let conn;
+
+  try {
+    conn = await oracledb.getConnection(config);
+
+    const result = await conn.execute('select * from employees where employee_id = :id', [empId]);
+
+    console.log(result.rows[0]);
+  } catch (err) {
+    console.log('Ouch!', err);
+  } finally {
+    if (conn) {
+      // conn assignment worked, need to close
+      await conn.close();
+    }
+  }
+}
+
+getEmployee(101);
+```
+
+## PostgreSQL
+
+**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
+
+### Installation
+
+```bash
+$ npm install pg-promise
+```
+
+### Example
+
+```js
+const pgp = require('pg-promise')(/* options */);
+const db = pgp('postgres://username:password@host:port/database');
+
+db.one('SELECT $1 AS value', 123)
+  .then((data) => {
+    console.log('DATA:', data.value);
+  })
+  .catch((error) => {
+    console.log('ERROR:', error);
+  });
+```
+
+## Redis
+
+**Module**: [redis](https://github.com/mranney/node_redis)
+
+### Installation
+
+```bash
+$ npm install redis
+```
+
+### Example
+
+```js
+const redis = require('redis');
+const client = redis.createClient();
+
+client.on('error', (err) => {
+  console.log(`Error ${err}`);
+});
+
+client.set('string key', 'string val', redis.print);
+client.hset('hash key', 'hashtest 1', 'some value', redis.print);
+client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print);
+
+client.hkeys('hash key', (err, replies) => {
+  console.log(`${replies.length} replies:`);
+
+  replies.forEach((reply, i) => {
+    console.log(`    ${i}: ${reply}`);
+  });
+
+  client.quit();
+});
+```
+
+## SQL Server
+
+**Module**: [tedious](https://github.com/tediousjs/tedious)
+
+### Installation
+
+```bash
+$ npm install tedious
+```
+
+### Example
+
+```js
+const Connection = require('tedious').Connection;
+const Request = require('tedious').Request;
+
+const config = {
+  server: 'localhost',
+  authentication: {
+    type: 'default',
+    options: {
+      userName: 'your_username', // update me
+      password: 'your_password', // update me
+    },
+  },
+};
+
+const connection = new Connection(config);
+
+connection.on('connect', (err) => {
+  if (err) {
+    console.log(err);
+  } else {
+    executeStatement();
+  }
+});
+
+function executeStatement() {
+  request = new Request("select 123, 'hello world'", (err, rowCount) => {
+    if (err) {
+      console.log(err);
+    } else {
+      console.log(`${rowCount} rows`);
+    }
+    connection.close();
+  });
+
+  request.on('row', (columns) => {
+    columns.forEach((column) => {
+      if (column.value === null) {
+        console.log('NULL');
+      } else {
+        console.log(column.value);
+      }
+    });
+  });
+
+  connection.execSql(request);
+}
+```
+
+## SQLite
+
+**Module**: [sqlite3](https://github.com/mapbox/node-sqlite3)
+
+### Installation
+
+```bash
+$ npm install sqlite3
+```
+
+### Example
+
+```js
+const sqlite3 = require('sqlite3').verbose();
+const db = new sqlite3.Database(':memory:');
+
+db.serialize(() => {
+  db.run('CREATE TABLE lorem (info TEXT)');
+  const stmt = db.prepare('INSERT INTO lorem VALUES (?)');
+
+  for (let i = 0; i < 10; i++) {
+    stmt.run(`Ipsum ${i}`);
+  }
+
+  stmt.finalize();
+
+  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
+    console.log(`${row.id}: ${row.info}`);
+  });
+});
+
+db.close();
+```
+
+## Elasticsearch
+
+**Module**: [elasticsearch](https://github.com/elastic/elasticsearch-js)
+
+### Installation
+
+```bash
+$ npm install elasticsearch
+```
+
+### Example
+
+```js
+const elasticsearch = require('elasticsearch');
+const client = elasticsearch.Client({
+  host: 'localhost:9200',
+});
+
+client
+  .search({
+    index: 'books',
+    type: 'book',
+    body: {
+      query: {
+        multi_match: {
+          query: 'express js',
+          fields: ['title', 'description'],
+        },
+      },
+    },
+  })
+  .then(
+    (response) => {
+      const hits = response.hits.hits;
+    },
+    (error) => {
+      console.trace(error.message);
+    }
+  );
+```
diff --git a/src/content/pages/zh-tw/guide/migrating-4.mdx b/src/content/pages/zh-tw/guide/migrating-4.mdx
new file mode 100644
index 0000000000..42a1b63163
--- /dev/null
+++ b/src/content/pages/zh-tw/guide/migrating-4.mdx
@@ -0,0 +1,662 @@
+---
+title: Moving to Express 4
+description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 4 is a breaking change from Express 3. That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
+
+This article covers:
+
+<ul class="doclist">
+  <li>
+    <a href="#changes">Changes in Express 4</a>.
+  </li>
+  <li>
+    <a href="#example-migration">An example</a> of migrating an Express 3 app to Express 4.
+  </li>
+  <li>
+    <a href="#app-gen">Upgrading to the Express 4 app generator</a>.
+  </li>
+</ul>
+
+## Changes in Express 4
+
+There are several significant changes in Express 4:
+
+<ul class="doclist">
+  <li>
+    <a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on
+    Connect and built-in middleware were removed, so you must add middleware yourself.
+  </li>
+  <li>
+    <a href="#routing">Changes to the routing system.</a>
+  </li>
+  <li>
+    <a href="#other-changes">Various other changes.</a>
+  </li>
+</ul>
+
+See also:
+
+- [New features in 4.x.](https://github.com/expressjs/express/wiki/New-features-in-4.x)
+- [Migrating from 3.x to 4.x.](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
+
+### Changes to Express core and middleware system
+
+Express 4 no longer depends on Connect, and removes all built-in
+middleware from its core, except for the `express.static` function. This means that
+Express is now an independent routing and middleware web framework, and
+Express versioning and releases are not affected by middleware updates.
+
+Without built-in middleware, you must explicitly add all the
+middleware that is required to run your app. Simply follow these steps:
+
+1. Install the module: `npm install --save <module-name>`
+2. In your app, require the module: `require('module-name')`
+3. Use the module according to its documentation: `app.use( ... )`
+
+The following table lists Express 3 middleware and their counterparts in Express 4.
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Express 3</th>
+    <th>Express 4</th>
+  </tr>
+  <tr>
+    <td>
+      <code>express.bodyParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/body-parser">body-parser</a> +
+      <a href="https://github.com/expressjs/multer">multer</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.compress</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/compression">compression</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieSession</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-session">cookie-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.cookieParser</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/cookie-parser">cookie-parser</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.logger</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/morgan">morgan</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.session</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/session">express-session</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.favicon</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-favicon">serve-favicon</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.responseTime</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/response-time">response-time</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.errorHandler</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/errorhandler">errorhandler</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.methodOverride</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/method-override">method-override</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.timeout</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/timeout">connect-timeout</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.vhost</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/vhost">vhost</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.csrf</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/csurf">csurf</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.directory</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-index">serve-index</a>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <code>express.static</code>
+    </td>
+    <td>
+      <a href="https://github.com/expressjs/serve-static">serve-static</a>
+    </td>
+  </tr>
+</table>
+
+Here is the [complete list](https://github.com/senchalabs/connect#middleware) of Express 4 middleware.
+
+In most cases, you can simply replace the old version 3 middleware with
+its Express 4 counterpart. For details, see the module documentation in
+GitHub.
+
+#### `app.use` accepts parameters
+
+In version 4 you can use a variable parameter to define the path where middleware functions are loaded, then read the value of the parameter from the route handler.
+For example:
+
+```js
+app.use('/book/:id', (req, res, next) => {
+  console.log('ID:', req.params.id);
+  next();
+});
+```
+
+### The routing system
+
+Apps now implicitly load routing middleware, so you no longer have to
+worry about the order in which middleware is loaded with respect to
+the `router` middleware.
+
+The way you define routes is unchanged, but the routing system has two
+new features to help organize your routes:
+
+- A new method, `app.route()`, to create chainable route handlers for a route path.
+- A new class, `express.Router`, to create modular mountable route handlers.
+
+#### `app.route()` method
+
+The new `app.route()` method enables you to create chainable route handlers
+for a route path. Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
+information about routes, see [`Router()` documentation](/en/4x/api#router).
+
+Here is an example of chained route handlers that are defined by using the `app.route()` function.
+
+```js
+app
+  .route('/book')
+  .get((req, res) => {
+    res.send('Get a random book');
+  })
+  .post((req, res) => {
+    res.send('Add a book');
+  })
+  .put((req, res) => {
+    res.send('Update the book');
+  });
+```
+
+#### `express.Router` class
+
+The other feature that helps to organize routes is a new class,
+`express.Router`, that you can use to create modular mountable
+route handlers. A `Router` instance is a complete middleware and
+routing system; for this reason it is often referred to as a "mini-app".
+
+The following example creates a router as a module, loads middleware in
+it, defines some routes, and mounts it on a path on the main app.
+
+For example, create a router file named `birds.js` in the app directory,
+with the following content:
+
+```js
+var express = require('express');
+var router = express.Router();
+
+// middleware specific to this router
+router.use((req, res, next) => {
+  console.log('Time: ', Date.now());
+  next();
+});
+// define the home page route
+router.get('/', (req, res) => {
+  res.send('Birds home page');
+});
+// define the about route
+router.get('/about', (req, res) => {
+  res.send('About birds');
+});
+
+module.exports = router;
+```
+
+Then, load the router module in the app:
+
+```js
+var birds = require('./birds');
+
+// ...
+
+app.use('/birds', birds);
+```
+
+The app will now be able to handle requests to the `/birds` and
+`/birds/about` paths, and will call the `timeLog`
+middleware that is specific to the route.
+
+### Other changes
+
+The following table lists other small but important changes in Express 4:
+
+<table class="doctable" border="1">
+  <tr>
+    <th>Object</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>Node.js</td>
+    <td>Express 4 requires Node.js 0.10.x or later and has dropped support for Node.js 0.8.x.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`http.createServer()`</td>
+    <td markdown="1">
+      The `http` module is no longer needed, unless you need to directly work with it
+      (socket.io/SPDY/HTTPS). The app can be started by using the `app.listen()` function.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.configure()`</td>
+    <td markdown="1">
+      The `app.configure()` function has been removed. Use the `process.env.NODE_ENV` or
+      `app.get('env')` function to detect the environment and configure the app accordingly.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`json spaces`</td>
+    <td markdown="1">
+      The `json spaces` application property is disabled by default in Express 4.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.accepted()`</td>
+    <td markdown="1">
+      Use `req.accepts()`, `req.acceptsEncodings()`, `req.acceptsCharsets()`, and
+      `req.acceptsLanguages()`.
+    </td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.location()`</td>
+    <td markdown="1">No longer resolves relative URLs.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`req.params`</td>
+    <td markdown="1">Was an array; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.locals`</td>
+    <td markdown="1">Was a function; now an object.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.headerSent`</td>
+    <td markdown="1">Changed to `res.headersSent`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`app.route`</td>
+    <td markdown="1">Now available as `app.mountpath`.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.on('header')`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.charset`</td>
+    <td markdown="1">Removed.</td>
+  </tr>
+  <tr>
+    <td markdown="1">`res.setHeader('Set-Cookie', val)`</td>
+    <td markdown="1">
+      Functionality is now limited to setting the basic cookie value. Use `res.cookie()` for added
+      functionality.
+    </td>
+  </tr>
+</table>
+
+## Example app migration
+
+Here is an example of migrating an Express 3 application to Express 4.
+The files of interest are `app.js` and `package.json`.
+
+### Version 3 app
+
+#### `app.js`
+
+Consider an Express v.3 application with the following `app.js` file:
+
+```js
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var http = require('http');
+var path = require('path');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(express.favicon());
+app.use(express.logger('dev'));
+app.use(express.methodOverride());
+app.use(express.session({ secret: 'your secret here' }));
+app.use(express.bodyParser());
+app.use(app.router);
+app.use(express.static(path.join(__dirname, 'public')));
+
+// development only
+if (app.get('env') === 'development') {
+  app.use(express.errorHandler());
+}
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+http.createServer(app).listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+#### `package.json`
+
+The accompanying version 3 `package.json` file might look
+something like this:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "express": "3.12.0",
+    "pug": "*"
+  }
+}
+```
+
+### Process
+
+Begin the migration process by installing the required middleware for the
+Express 4 app and updating Express and Pug to their respective latest
+version with the following command:
+
+```bash
+$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
+```
+
+Make the following changes to `app.js`:
+
+1. The built-in Express middleware functions `express.favicon`,
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` and
+   `express.errorHandler` are no longer available on the
+   `express` object. You must install their alternatives
+   manually and load them in the app.
+
+2. You no longer need to load the `app.router` function.
+   It is not a valid Express 4 app object, so remove the
+   `app.use(app.router);` code.
+
+3. Make sure that the middleware functions are loaded in the correct order - load `errorHandler` after loading the app routes.
+
+### Version 4 app
+
+#### `package.json`
+
+Running the above `npm` command will update `package.json` as follows:
+
+```json
+{
+  "name": "application-name",
+  "version": "0.0.1",
+  "private": true,
+  "scripts": {
+    "start": "node app.js"
+  },
+  "dependencies": {
+    "body-parser": "^1.5.2",
+    "errorhandler": "^1.1.1",
+    "express": "^4.8.0",
+    "express-session": "^1.7.2",
+    "pug": "^2.0.0",
+    "method-override": "^2.1.2",
+    "morgan": "^1.2.2",
+    "multer": "^0.1.3",
+    "serve-favicon": "^2.0.1"
+  }
+}
+```
+
+#### `app.js`
+
+Then, remove invalid code, load the required middleware, and make other
+changes as necessary. The `app.js` file will look like this:
+
+```js
+var http = require('http');
+var express = require('express');
+var routes = require('./routes');
+var user = require('./routes/user');
+var path = require('path');
+
+var favicon = require('serve-favicon');
+var logger = require('morgan');
+var methodOverride = require('method-override');
+var session = require('express-session');
+var bodyParser = require('body-parser');
+var multer = require('multer');
+var errorHandler = require('errorhandler');
+
+var app = express();
+
+// all environments
+app.set('port', process.env.PORT || 3000);
+app.set('views', path.join(__dirname, 'views'));
+app.set('view engine', 'pug');
+app.use(favicon(path.join(__dirname, '/public/favicon.ico')));
+app.use(logger('dev'));
+app.use(methodOverride());
+app.use(
+  session({
+    resave: true,
+    saveUninitialized: true,
+    secret: 'uwotm8',
+  })
+);
+app.use(bodyParser.json());
+app.use(bodyParser.urlencoded({ extended: true }));
+app.use(multer());
+app.use(express.static(path.join(__dirname, 'public')));
+
+app.get('/', routes.index);
+app.get('/users', user.list);
+
+// error handling middleware should be loaded after the loading the routes
+if (app.get('env') === 'development') {
+  app.use(errorHandler());
+}
+
+var server = http.createServer(app);
+server.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+<Alert type="info">
+Unless you need to work directly with the `http` module (socket.io/SPDY/HTTPS), loading it is not required, and the app can be simply started this way:
+
+```js
+app.listen(app.get('port'), () => {
+  console.log('Express server listening on port ' + app.get('port'));
+});
+```
+
+</Alert>
+
+### Run the app
+
+The migration process is complete, and the app is now an
+Express 4 app. To confirm, start the app by using the following command:
+
+```bash
+$ node .
+```
+
+Load [http://localhost:3000](http://localhost:3000)
+and see the home page being rendered by Express 4.
+
+## Upgrading to the Express 4 app generator
+
+The command-line tool to generate an Express app is still
+`express`, but to upgrade to the new version, you must uninstall
+the Express 3 app generator and then install the new
+`express-generator`.
+
+### Installing
+
+If you already have the Express 3 app generator installed on your system,
+you must uninstall it:
+
+```bash
+$ npm uninstall -g express
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now install the new generator:
+
+```bash
+$ npm install -g express-generator
+```
+
+Depending on how your file and directory privileges are configured,
+you might need to run this command with `sudo`.
+
+Now the `express` command on your system is updated to the
+Express 4 generator.
+
+### Changes to the app generator
+
+Command options and use largely remain the same, with the following exceptions:
+
+- Removed the `--sessions` option.
+- Removed the `--jshtml` option.
+- Added the `--hogan` option to support [Hogan.js](http://twitter.github.io/hogan.js/).
+
+### Example
+
+Execute the following command to create an Express 4 app:
+
+```bash
+$ express app4
+```
+
+If you look at the contents of the `app4/app.js` file, you will notice
+that all the middleware functions (except `express.static`) that are required for
+the app are loaded as independent modules, and the `router` middleware
+is no longer explicitly loaded in the app.
+
+You will also notice that the `app.js` file is now a Node.js module, in contrast to the standalone app that was generated by the old generator.
+
+After installing the dependencies, start the app by using the following command:
+
+```bash
+$ npm start
+```
+
+If you look at the `npm start` script in the `package.json` file,
+you will notice that the actual command that starts the app is
+`node ./bin/www`, which used to be `node app.js`
+in Express 3.
+
+Because the `app.js` file that was generated by the Express 4 generator
+is now a Node.js module, it can no longer be started independently as an app
+(unless you modify the code). The module must be loaded in a Node.js file
+and started via the Node.js file. The Node.js file is `./bin/www`
+in this case.
+
+Neither the `bin` directory nor the extensionless `www`
+file is mandatory for creating an Express app or starting the app. They are
+just suggestions made by the generator, so feel free to modify them to suit your
+needs.
+
+To get rid of the `www` directory and keep things the "Express 3 way",
+delete the line that says `module.exports = app;` at the end of the
+`app.js` file, then paste the following code in its place:
+
+```js
+app.set('port', process.env.PORT || 3000);
+
+var server = app.listen(app.get('port'), () => {
+  debug('Express server listening on port ' + server.address().port);
+});
+```
+
+Ensure that you load the `debug` module at the top of the `app.js` file by using the following code:
+
+```js
+var debug = require('debug')('app4');
+```
+
+Next, change `"start": "node ./bin/www"` in the `package.json` file to `"start": "node app.js"`.
+
+You have now moved the functionality of `./bin/www` back to
+`app.js`. This change is not recommended, but the exercise helps you
+to understand how the `./bin/www` file works, and why the `app.js` file
+no longer starts on its own.
diff --git a/src/content/pages/zh-tw/guide/migrating-5.mdx b/src/content/pages/zh-tw/guide/migrating-5.mdx
new file mode 100644
index 0000000000..dac703c953
--- /dev/null
+++ b/src/content/pages/zh-tw/guide/migrating-5.mdx
@@ -0,0 +1,678 @@
+---
+title: Moving to Express 5
+description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+Express 5 is not very different from Express 4; although it maintains the same basic API, there are still changes that break compatibility with the previous version. Therefore, an application built with Express 4 might not work if you update it to use Express 5.
+
+To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
+
+```sh
+npm install "express@5"
+```
+
+You can then run your automated tests to see what fails, and fix problems according to the updates listed below. After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
+
+## Express 5 Codemods
+
+To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
+
+Run the following command for run all the codemods available:
+
+```sh
+npx codemod@latest @expressjs/v5-migration-recipe
+```
+
+If you want to run a specific codemod, you can run the following command:
+
+```sh
+npx codemod@latest @expressjs/name-of-the-codemod
+```
+
+You can find the list of available codemods [here](https://codemod.link/express).
+
+## Changes in Express 5
+
+**Removed methods and properties**
+
+<ul class="doclist">
+  <li>
+    <a href="#app.del">app.del()</a>
+  </li>
+  <li>
+    <a href="#app.param">app.param(fn)</a>
+  </li>
+  <li>
+    <a href="#plural">Pluralized method names</a>
+  </li>
+  <li>
+    <a href="#leading">Leading colon in name argument to app.param(name, fn)</a>
+  </li>
+  <li>
+    <a href="#req.param">req.param(name)</a>
+  </li>
+  <li>
+    <a href="#res.json">res.json(obj, status)</a>
+  </li>
+  <li>
+    <a href="#res.jsonp">res.jsonp(obj, status)</a>
+  </li>
+  <li>
+    <a href="#magic-redirect">res.redirect('back') and res.location('back')</a>
+  </li>
+  <li>
+    <a href="#res.redirect">res.redirect(url, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.body">res.send(body, status)</a>
+  </li>
+  <li>
+    <a href="#res.send.status">res.send(status)</a>
+  </li>
+  <li>
+    <a href="#res.sendfile">res.sendfile()</a>
+  </li>
+  <li>
+    <a href="#router.param">router.param(fn)</a>
+  </li>
+  <li>
+    <a href="#express.static.mime">express.static.mime</a>
+  </li>
+  <li>
+    <a href="#express:router-debug-logs">express:router debug logs</a>
+  </li>
+</ul>
+
+**Changed**
+
+<ul class="doclist">
+  <li>
+    <a href="#path-syntax">Path route matching syntax</a>
+  </li>
+  <li>
+    <a href="#rejected-promises">Rejected promises handled from middleware and handlers</a>
+  </li>
+  <li>
+    <a href="#express.urlencoded">express.urlencoded</a>
+  </li>
+  <li>
+    <a href="#express.static.dotfiles">express.static dotfiles</a>
+  </li>
+  <li>
+    <a href="#app.listen">app.listen</a>
+  </li>
+  <li>
+    <a href="#app.router">app.router</a>
+  </li>
+  <li>
+    <a href="#req.body">req.body</a>
+  </li>
+  <li>
+    <a href="#req.host">req.host</a>
+  </li>
+  <li>
+    <a href="#req.params">req.params</a>
+  </li>
+  <li>
+    <a href="#req.query">req.query</a>
+  </li>
+  <li>
+    <a href="#res.clearCookie">res.clearCookie</a>
+  </li>
+  <li>
+    <a href="#res.status">res.status</a>
+  </li>
+  <li>
+    <a href="#res.vary">res.vary</a>
+  </li>
+</ul>
+
+**Improvements**
+
+<ul class="doclist">
+  <li>
+    <a href="#res.render">res.render()</a>
+  </li>
+  <li>
+    <a href="#brotli-support">Brotli encoding support</a>
+  </li>
+</ul>
+
+## Removed methods and properties
+
+If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
+
+### app.del()
+
+Express 5 no longer supports the `app.del()` function. If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
+
+Initially, `del` was used instead of `delete`, because `delete` is a reserved keyword in JavaScript. However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/route-del-to-delete
+```
+
+</Alert>
+
+```js
+// v4
+app.del('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+
+// v5
+app.delete('/user/:id', (req, res) => {
+  res.send(`DELETE /user/${req.params.id}`);
+});
+```
+
+### app.param(fn)
+
+The `app.param(fn)` signature was used for modifying the behavior of the `app.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### Pluralized method names
+
+The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
+
+`req.acceptsCharset()` is replaced by `req.acceptsCharsets()`.
+
+`req.acceptsEncoding()` is replaced by `req.acceptsEncodings()`.
+
+`req.acceptsLanguage()` is replaced by `req.acceptsLanguages()`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/pluralize-method-names
+```
+
+</Alert>
+
+```js
+// v4
+app.all('/', (req, res) => {
+  req.acceptsCharset('utf-8');
+  req.acceptsEncoding('br');
+  req.acceptsLanguage('en');
+
+  // ...
+});
+
+// v5
+app.all('/', (req, res) => {
+  req.acceptsCharsets('utf-8');
+  req.acceptsEncodings('br');
+  req.acceptsLanguages('en');
+
+  // ...
+});
+```
+
+### Leading colon (:) in the name for app.param(name, fn)
+
+A leading colon character (:) in the name for the `app.param(name, fn)` function is a remnant of Express 3, and for the sake of backwards compatibility, Express 4 supported it with a deprecation notice. Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
+
+This should not affect your code if you follow the Express 4 documentation of [app.param](/en/4x/api#app.param), as it makes no mention of the leading colon.
+
+### req.param(name)
+
+This potentially confusing and dangerous method of retrieving form data has been removed. You will now need to specifically look for the submitted parameter name in the `req.params`, `req.body`, or `req.query` object.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/explicit-request-params
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  const id = req.param('id');
+  const body = req.param('body');
+  const query = req.param('query');
+
+  // ...
+});
+
+// v5
+app.post('/user', (req, res) => {
+  const id = req.params.id;
+  const body = req.body;
+  const query = req.query;
+
+  // ...
+});
+```
+
+### res.json(obj, status)
+
+Express 5 no longer supports the signature `res.json(obj, status)`. Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.json({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).json({ name: 'Ruben' });
+});
+```
+
+### res.jsonp(obj, status)
+
+Express 5 no longer supports the signature `res.jsonp(obj, status)`. Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.post('/user', (req, res) => {
+  res.jsonp({ name: 'Ruben' }, 201);
+});
+
+// v5
+app.post('/user', (req, res) => {
+  res.status(201).jsonp({ name: 'Ruben' });
+});
+```
+
+### res.redirect(url, status)
+
+Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/redirect-arg-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('/users', 301);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(301, '/users');
+});
+```
+
+### res.redirect('back') and res.location('back')
+
+Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/back-redirect-deprecated
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.redirect('back');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.redirect(req.get('Referrer') || '/');
+});
+```
+
+### res.send(body, status)
+
+Express 5 no longer supports the signature `res.send(obj, status)`. Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send({ name: 'Ruben' }, 200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.status(200).send({ name: 'Ruben' });
+});
+```
+
+### res.send(status)
+
+Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
+If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/status-send-order
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.send(200);
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendStatus(200);
+});
+```
+
+### res.sendfile()
+
+The `res.sendfile()` function has been replaced by a camel-cased version `res.sendFile()` in Express 5.
+
+**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
+
+- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
+- JSON files (.json): now "application/json" instead of "text/json"
+- CSS files (.css): now "text/css" instead of "text/plain"
+- XML files (.xml): now "application/xml" instead of "text/xml"
+- Font files (.woff): now "font/woff" instead of "application/font-woff"
+- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
+
+<Alert type="info">
+You can replace the deprecated signatures with the following command:
+
+```plaintext
+npx codemod@latest @expressjs/camelcase-sendfile
+```
+
+</Alert>
+
+```js
+// v4
+app.get('/user', (req, res) => {
+  res.sendfile('/path/to/file');
+});
+
+// v5
+app.get('/user', (req, res) => {
+  res.sendFile('/path/to/file');
+});
+```
+
+### router.param(fn)
+
+The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
+
+### express.static.mime
+
+In Express 5, `mime` is no longer an exported property of the `static` field.
+Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
+
+**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
+
+- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
+- JSON files (.json): now served as "application/json" instead of "text/json"
+- CSS files (.css): now served as "text/css" instead of "text/plain"
+- HTML files (): now served as "text/html; charset=utf-8" instead of just "text/html"
+- XML files (.xml): now served as "application/xml" instead of "text/xml"
+- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
+
+```js
+// v4
+express.static.mime.lookup('json');
+
+// v5
+const mime = require('mime-types');
+mime.lookup('json');
+```
+
+### express:router debug logs
+
+In Express 5, router handling logic is performed by a dependency. Therefore, the
+debug logs for the router are no longer available under the `express:` namespace.
+In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
+and `express:router:route`. All of these were included under the namespace `express:*`.
+In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
+The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
+To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
+`express:*`, `router`, and `router:*`.
+
+```sh
+
+DEBUG=express:* node index.js
+
+
+DEBUG=express:*,router,router:* node index.js
+```
+
+## Changed
+
+### Path route matching syntax
+
+Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
+
+- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
+
+```js
+// v4
+app.get('/*', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/*splat', async (req, res) => {
+  res.send('ok');
+});
+```
+
+<Alert type="info">
+`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
+
+```js
+// v5
+app.get('/{*splat}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+</Alert>
+
+- The optional character `?` is no longer supported, use braces instead.
+
+```js
+// v4
+app.get('/:file.:ext?', async (req, res) => {
+  res.send('ok');
+});
+
+// v5
+app.get('/:file{.:ext}', async (req, res) => {
+  res.send('ok');
+});
+```
+
+- Regexp characters are not supported. For example:
+
+```js
+app.get('/[discussion|page]/:slug', async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+should be changed to:
+
+```js
+app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
+  res.status(200).send('ok');
+});
+```
+
+- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
+- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
+
+### Rejected promises handled from middleware and handlers
+
+Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
+
+Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling).
+
+### express.urlencoded
+
+The `express.urlencoded` method makes the `extended` option `false` by default.
+
+### express.static dotfiles
+
+In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
+
+Example of breaking code:
+
+```js
+// v4
+app.use(express.static('public'));
+```
+
+After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
+
+To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
+
+```js
+// v5
+app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }));
+app.use(express.static('public'));
+```
+
+This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
+
+### app.listen
+
+In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
+For example:
+
+```js
+const server = app.listen(8080, '0.0.0.0', (error) => {
+  if (error) {
+    throw error; // e.g. EADDRINUSE
+  }
+  console.log(`Listening on ${JSON.stringify(server.address())}`);
+});
+```
+
+### app.router
+
+The `app.router` object, which was removed in Express 4, has made a comeback in Express 5. In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
+
+### req.body
+
+The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
+
+### req.host
+
+In Express 4, the `req.host` function incorrectly stripped off the port number if it was present. In Express 5, the port number is maintained.
+
+### req.params
+
+The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
+
+**Wildcard parameters are now arrays:**
+
+Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
+
+```js
+app.get('/*splat', (req, res) => {
+  // GET /foo/bar
+  console.dir(req.params);
+  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
+});
+```
+
+**Unmatched parameters are omitted:**
+
+In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
+
+```js
+// v4: unmatched wildcard is empty string
+app.get('/*', (req, res) => {
+  // GET /
+  console.dir(req.params);
+  // => { '0': '' }
+});
+
+// v4: unmatched optional param is undefined
+app.get('/:file.:ext?', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => { file: 'image', ext: undefined }
+});
+
+// v5: unmatched optional param is omitted
+app.get('/:file{.:ext}', (req, res) => {
+  // GET /image
+  console.dir(req.params);
+  // => [Object: null prototype] { file: 'image' }
+});
+```
+
+### req.query
+
+The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
+
+### res.clearCookie
+
+The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
+
+### res.status
+
+The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
+
+### res.vary
+
+The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
+
+## Improvements
+
+### res.render()
+
+This method now enforces asynchronous behavior for all view engines, avoiding bugs caused by view engines that had a synchronous implementation and that violated the recommended interface.
+
+### Brotli encoding support
+
+Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/src/content/pages/zh-tw/resources/glossary.mdx b/src/content/pages/zh-tw/resources/glossary.mdx
new file mode 100644
index 0000000000..c40a0a2e15
--- /dev/null
+++ b/src/content/pages/zh-tw/resources/glossary.mdx
@@ -0,0 +1,61 @@
+---
+title: Glossary
+description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
+---
+
+import Alert from '@components/primitives/Alert/Alert.astro';
+
+### application
+
+In general, one or more programs that are designed to carry out operations for a specific purpose. In the context of Express, a program that uses the Express API running on the Node.js platform. Might also refer to an [app object](/en/api#express).
+
+### API
+
+Application programming interface. Spell out the abbreviation when it is first used.
+
+### Express
+
+A fast, un-opinionated, minimalist web framework for Node.js applications. In general, "Express" is preferred to "Express.js," though the latter is acceptable.
+
+### libuv
+
+A multi-platform support library which focuses on asynchronous I/O, primarily developed for use by Node.js.
+
+### middleware
+
+A function that is invoked by the Express routing layer before the final request handler, and thus sits in the middle between a raw request and the final intended route. A few fine points of terminology around middleware:
+
+- `var foo = require('middleware')` is called _requiring_ or _using_ a Node.js module. Then the statement `var mw = foo()` typically returns the middleware.
+- `app.use(mw)` is called _adding the middleware to the global processing stack_.
+- `app.get('/foo', mw, function (req, res) { ... })` is called _adding the middleware to the "GET /foo" processing stack_.
+
+### Node.js
+
+A software platform that is used to build scalable network applications. Node.js uses JavaScript as its scripting language, and achieves high throughput via non-blocking I/O and a single-threaded event loop. See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
+
+### open-source, open source
+
+When used as an adjective, hyphenate; for example: "This is open-source software." See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
+
+<Alert type="info">
+
+Although it is common not to hyphenate this term, we are using the standard English rules for
+hyphenating a compound adjective.
+
+</Alert>
+
+### request
+
+An HTTP request. A client submits an HTTP request message to a server, which returns a response. The request must use one of several [request methods](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods) such as GET, POST, and so on.
+
+### response
+
+An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
+
+### route
+
+Part of a URL that identifies a resource. For example, in `http://foo.com/products/id`, "/products/id" is the route.
+
+### router
+
+See [router](/en/api#router) in the API reference.
diff --git a/src/content/pages/zh-tw/resources/utils.md b/src/content/pages/zh-tw/resources/utils.md
new file mode 100644
index 0000000000..739b352f3e
--- /dev/null
+++ b/src/content/pages/zh-tw/resources/utils.md
@@ -0,0 +1,22 @@
+---
+title: Express utilities
+description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
+---
+
+## Express utility functions
+
+The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
+for utility functions that may be generally useful.
+
+| Utility modules                                                | Description                                                                                                                                             |
+| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
+| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification. Use this module to create custom CSRF middleware.                                       |
+| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                        |
+| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                               |
+| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                  |
+| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                           |
+| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                         |
+| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.          |
+
+For additional low-level HTTP-related modules, see [jshttp](https://github.com/jshttp).
diff --git a/src/content/pages/zh-tw/support.md b/src/content/pages/zh-tw/support.md
new file mode 100644
index 0000000000..9e59b0976b
--- /dev/null
+++ b/src/content/pages/zh-tw/support.md
@@ -0,0 +1,23 @@
+---
+title: Version Support
+description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
+---
+
+Only the latest version of any given major release line is supported.
+
+Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
+
+| Major Version          | Minimum Node.js Version | Support Start Date | Support End Date |
+| ---------------------- | ----------------------- | ------------------ | ---------------- |
+| [**v5.x**](/en/5x/api) | 18                      | September 2024     | **ongoing**      |
+| [**v4.x**](/en/4x/api) | 0.10.0                  | April 2014         | **ongoing**      |
+| [**v3.x**](/en/3x/api) | 0.8.0                   | October 2012       | July 2015        |
+| [**v2.x**](/2x/)       | 0.4.1                   | March 2011         | July 2012        |
+| **v1.x**               | 0.2.0                   | December 2010      | March 2011       |
+| **v0.14.x**            | 0.1.98                  | December 2010      | December 2010    |
+
+## Commercial Support Options
+
+If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
+
+- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/src/i18n/locales.ts b/src/i18n/locales.ts
new file mode 100644
index 0000000000..79ed73d631
--- /dev/null
+++ b/src/i18n/locales.ts
@@ -0,0 +1,45 @@
+import en from './ui/en.json';
+import fr from './ui/fr.json';
+import de from './ui/de.json';
+import es from './ui/es.json';
+import it from './ui/it.json';
+import ja from './ui/ja.json';
+import ko from './ui/ko.json';
+import ptBr from './ui/pt-br.json';
+import zhCn from './ui/zh-cn.json';
+import zhTw from './ui/zh-tw.json';
+
+export const languages = {
+  en: { label: 'English', direction: 'ltr' },
+  de: { label: 'Deutsch', direction: 'ltr' },
+  es: { label: 'Español', direction: 'ltr' },
+  fr: { label: 'Français', direction: 'ltr' },
+  it: { label: 'Italiano', direction: 'ltr' },
+  ja: { label: '日本語', direction: 'ltr' },
+  ko: { label: '한국어', direction: 'ltr' },
+  'pt-br': { label: 'Português', direction: 'ltr' },
+  'zh-cn': { label: '简体中文', direction: 'ltr' },
+  'zh-tw': { label: '繁體中文', direction: 'ltr' },
+} as const;
+
+export type LanguageCode = keyof typeof languages;
+
+export const languagesArray = Object.entries(languages).map(([code, obj]) => ({
+  code,
+  label: obj.label,
+}));
+
+export const defaultLang = 'en';
+
+export const ui = {
+  en,
+  fr,
+  de,
+  es,
+  it,
+  ja,
+  ko,
+  'pt-br': ptBr,
+  'zh-cn': zhCn,
+  'zh-tw': zhTw,
+} as const;
diff --git a/src/i18n/ui/de.json b/src/i18n/ui/de.json
new file mode 100644
index 0000000000..763fa10a6d
--- /dev/null
+++ b/src/i18n/ui/de.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Begrüßung",
+    "workInProgress": "Dies ist eine Work-in-progress Homepage.",
+    "reviewDesignSystem": {
+      "prefix": "Überprüfen Sie die",
+      "link": "Design System Foundations",
+      "suffix": "Demo-Seite, um alle Token, Primitive und Muster zu erkunden."
+    }
+  },
+  "search": {
+    "placeholder": "Tippe ein...",
+    "ariaLabel": "Tippen zum Suchen starten"
+  },
+  "theme": {
+    "toggle": "Theme umschalten",
+    "switchToLight": "Zum Lichtmodus wechseln",
+    "switchToDark": "Zum dunklen Modus wechseln"
+  },
+  "version": {
+    "selectLabel": "API-Version auswählen"
+  },
+  "nav": {
+    "mainMenu": "Hauptmenü",
+    "toggleMenu": "Menü umschalten",
+    "home": "home",
+    "breadcrumb": "Breadcrumb",
+    "mainNavigation": "Hauptnavigation",
+    "selectVersion": "Dokumentationsversion auswählen"
+  },
+  "menu": {
+    "main": {
+      "docs": "Texte",
+      "api": "API",
+      "resources": "Ressourcen",
+      "blog": "Blog",
+      "support": "Unterstützung"
+    },
+    "sections": {
+      "gettingStarted": "Erste Schritte",
+      "guide": "Anleitung",
+      "migration": "Migrationsanleitungen",
+      "advanced": "Erweiterte Themen",
+      "express": "express()",
+      "application": "Anwendung",
+      "request": "Anfrage",
+      "response": "Antwort",
+      "router": "Router",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installiere",
+      "helloWorld": "Hallo Welt",
+      "expressGenerator": "Express-Generator",
+      "basicRouting": "Basisrouting",
+      "staticFiles": "Serviere statische Dateien",
+      "examples": "Beispiele",
+      "faq": "FAQ",
+      "routing": "Routing",
+      "writingMiddleware": "Middleware schreiben",
+      "usingMiddleware": "Middleware verwenden",
+      "usingTemplateEngines": "Template-Engines verwenden",
+      "errorHandling": "Fehlerbehandlung",
+      "debugging": "Debuggen",
+      "behindProxies": "Hinter Proxys",
+      "databaseIntegration": "Datenbankintegration",
+      "overridingExpressApi": "Überschreiben der Express-API",
+      "migratingTo4": "Umzug nach Express 4",
+      "migratingTo5": "Umzug nach Express 5",
+      "buildingTemplateEngines": "Bauvorlagen-Engines",
+      "bestPracticePerformance": "Best Practices",
+      "bestPracticeSecurity": "Sicherheits-Best Practices",
+      "healthcheckGracefulShutdown": "Gesundheitschecks & anmutiges Herunterfahren",
+      "securityUpdates": "Sicherheitsupdates",
+      "overview": "Übersicht",
+      "properties": "Eigenschaften",
+      "methods": "Methoden",
+      "events": "Ereignisse",
+      "types": "Integriert",
+      "community": "Community",
+      "glossary": "Glossary",
+      "contributing": "Mitwirken",
+      "utils": "Hilfsmittel",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Dokumentation",
+      "api": "API-Referenz",
+      "resources": "Ressourcen",
+      "blog": "Blog",
+      "support": "Unterstützung",
+      "installing": "Express installieren",
+      "helloWorld": "Hallo Weltbeispiel",
+      "expressGenerator": "Express-Generator",
+      "routing": "Routenanleitung",
+      "writingMiddleware": "Middleware-Anleitung schreiben",
+      "usingMiddleware": "Middleware-Anleitung verwenden",
+      "usingTemplateEngines": "Hilfe für Template-Engines",
+      "errorHandling": "Fehler beim Handling",
+      "debugging": "Debuggen Express",
+      "behindProxies": "Express hinter Proxies",
+      "databaseIntegration": "Datenbank-Integrationshandbuch",
+      "overridingExpressApi": "Überschreiben der Express-API-Anleitung",
+      "application": "Anwendungsübersicht",
+      "request": "Übersicht anfordern",
+      "response": "Antwortübersicht",
+      "router": "Routerübersicht",
+      "middleware": "Middleware-Ressourcen",
+      "community": "Community-Ressourcen",
+      "glossary": "Glossar der Begriffe",
+      "contributing": "Beitragende Anleitung",
+      "utils": "Hilfsmittel"
+    }
+  },
+  "doc": {
+    "previousPage": "Vorherige",
+    "nextPage": "Nächste",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Diese Seite übersetzen"
+  },
+  "post": {
+    "share": "Teilen",
+    "shareOnX": "Auf X teilen",
+    "shareOnBluesky": "Auf Bluesky teilen",
+    "shareOnLinkedIn": "Auf LinkedIn teilen",
+    "shareOnSlack": "Auf Slack teilen",
+    "shareOnTelegram": "Auf Telegram teilen",
+    "shareOnWhatsApp": "Auf WhatsApp teilen",
+    "rssFeed": "RSS-Feed",
+    "copyLink": "Link kopieren",
+    "linkCopied": "Link kopiert!",
+    "toc": "Auf dieser Seite",
+    "more": "Mehr von Express",
+    "writeBanner": "Möchten Sie einen Beitrag schreiben? \n Schauen Sie sich unsere Richtlinien an, um loszulegen.",
+    "writeGuidelines": "Lies die Richtlinien"
+  },
+  "toc": {
+    "overview": "Übersicht"
+  },
+  "features": {
+    "title": "Klarheit über die Komplexität. Für jeden Entwickler.",
+    "performance": {
+      "title": "Leistung",
+      "body": "Express bietet eine dünne Schicht von grundlegenden Web-Applikations-Funktionen, ohne verschleiernde Node.js Funktionen, die Sie kennen und lieben."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "Mit einer Vielzahl von HTTP-Utility-Methoden und Middleware steht Ihnen eine robuste API zu erstellen ist schnell und einfach."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express ist ein leichtes, flexibles Routing-Framework mit minimalen Kernfunktionen, die durch den Einsatz von Express-Middleware-Modulen ergänzt werden sollen."
+    },
+    "webapplication": {
+      "title": "Web-Anwendungen",
+      "body": "Express ist ein minimales und flexibles Node.js Web Application Framework, das eine robuste Reihe von Funktionen für Web- und mobile Anwendungen bietet."
+    }
+  },
+  "error404": {
+    "title": "404 - Seite nicht gefunden",
+    "description": "Die gesuchte Seite konnte nicht gefunden werden.",
+    "heading": "Seite nicht gefunden",
+    "message": "Die gesuchte Seite existiert nicht oder wurde verschoben.",
+    "goHome": "Gehe zu Zuhause"
+  },
+  "hero": {
+    "tagline": "Schnell, unüberlegtes, minimalistisches Web-Framework für Node.js",
+    "getStarted": "Los geht's",
+    "videoPause": "Hintergrundvideo pausieren",
+    "videoPlay": "Hintergrundvideo abspielen"
+  }
+}
diff --git a/src/i18n/ui/en.json b/src/i18n/ui/en.json
new file mode 100644
index 0000000000..0347fe4ad1
--- /dev/null
+++ b/src/i18n/ui/en.json
@@ -0,0 +1,198 @@
+{
+  "home": {
+    "welcome": "Welcome",
+    "workInProgress": "This is a work-in-progress homepage.",
+    "reviewDesignSystem": {
+      "prefix": "Review the",
+      "link": "Design System Foundations",
+      "suffix": "demo page to explore all tokens, primitives, and patterns."
+    }
+  },
+  "search": {
+    "placeholder": "Start typing...",
+    "ariaLabel": "Start typing to search"
+  },
+  "theme": {
+    "toggle": "Toggle theme",
+    "switchToLight": "Switch to light mode",
+    "switchToDark": "Switch to dark mode"
+  },
+  "version": {
+    "selectLabel": "Select API version"
+  },
+  "language": {
+    "selectLabel": "Select language"
+  },
+  "nav": {
+    "mainMenu": "Main menu",
+    "toggleMenu": "Toggle menu",
+    "home": "home",
+    "breadcrumb": "Breadcrumb",
+    "mainNavigation": "Main navigation",
+    "selectVersion": "Select documentation version"
+  },
+  "menu": {
+    "main": {
+      "docs": "Docs",
+      "api": "API",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support"
+    },
+    "sections": {
+      "gettingStarted": "Getting started",
+      "guide": "Guide",
+      "migration": "Migration guides",
+      "advanced": "Advanced topics",
+
+      "express": "express()",
+      "application": "Application",
+      "request": "Request",
+      "response": "Response",
+      "router": "Router",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installing",
+      "helloWorld": "Hello world",
+      "expressGenerator": "Express generator",
+      "basicRouting": "Basic routing",
+      "staticFiles": "Serving static files",
+      "examples": "Examples",
+      "faq": "FAQ",
+
+      "routing": "Routing",
+      "writingMiddleware": "Writing middleware",
+      "usingMiddleware": "Using middleware",
+      "usingTemplateEngines": "Using template engines",
+      "errorHandling": "Error handling",
+      "debugging": "Debugging",
+      "behindProxies": "Behind proxies",
+      "databaseIntegration": "Database integration",
+      "overridingExpressApi": "Overriding the Express API",
+
+      "migratingTo4": "Moving to Express 4",
+      "migratingTo5": "Moving to Express 5",
+
+      "buildingTemplateEngines": "Building template engines",
+      "bestPracticePerformance": "Performance best practices",
+      "bestPracticeSecurity": "Security best practices",
+      "healthcheckGracefulShutdown": "Health checks & graceful shutdown",
+      "securityUpdates": "Security updates",
+
+      "overview": "Overview",
+      "properties": "Properties",
+      "methods": "Methods",
+      "events": "Events",
+      "types": "Built-in",
+
+      "community": "Community",
+      "glossary": "Glossary",
+      "contributing": "Contributing",
+      "utils": "Utilities",
+      "changelog": "Changelog",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Documentation",
+      "api": "API Reference",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support",
+
+      "installing": "Installing Express",
+      "helloWorld": "Hello world example",
+      "expressGenerator": "Express generator",
+
+      "routing": "Routing guide",
+      "writingMiddleware": "Writing middleware guide",
+      "usingMiddleware": "Using middleware guide",
+      "usingTemplateEngines": "Using template engines guide",
+      "errorHandling": "Error handling guide",
+      "debugging": "Debugging Express",
+      "behindProxies": "Express behind proxies",
+      "databaseIntegration": "Database integration guide",
+      "overridingExpressApi": "Overriding the Express API guide",
+
+      "application": "Application overview",
+      "request": "Request overview",
+      "response": "Response overview",
+      "router": "Router overview",
+      "middleware": "Middleware resources",
+
+      "community": "Community resources",
+      "glossary": "Glossary of terms",
+      "contributing": "Contributing guide",
+      "utils": "Utilities",
+      "changelog": "Express changelog"
+    }
+  },
+  "doc": {
+    "previousPage": "Previous",
+    "nextPage": "Next",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Translate this page"
+  },
+  "announcement": {
+    "readMore": "Read more",
+    "checkLatestBlog": "Check out our latest blog"
+  },
+  "post": {
+    "share": "Share",
+    "shareOnX": "Share on X",
+    "shareOnBluesky": "Share on Bluesky",
+    "shareOnLinkedIn": "Share on LinkedIn",
+    "shareOnSlack": "Share on Slack",
+    "shareOnTelegram": "Share on Telegram",
+    "shareOnWhatsApp": "Share on WhatsApp",
+    "rssFeed": "RSS Feed",
+    "copyLink": "Copy link",
+    "linkCopied": "Link copied!",
+    "toc": "On this page",
+    "more": "More from Express",
+    "writeBanner": "Interested in writing a post? \n Check out our guidelines to get started.",
+    "writeGuidelines": "Read the guidelines"
+  },
+  "toc": {
+    "overview": "Overview"
+  },
+  "features": {
+    "title": "Clarity over complexity. For every developer.",
+    "performance": {
+      "title": "Performance",
+      "body": "Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express is a lightweight and flexible routing framework with minimal core features meant to be augmented through the use of Express middleware modules."
+    },
+    "webapplication": {
+      "title": "Web Applications",
+      "body": "Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications."
+    }
+  },
+  "error404": {
+    "title": "404 - Page Not Found",
+    "description": "The page you are looking for could not be found.",
+    "heading": "Page Not Found",
+    "message": "The page you are looking for does not exist or has been moved.",
+    "goHome": "Go to Home"
+  },
+  "common": {
+    "download": "Download"
+  },
+  "hero": {
+    "tagline": "Fast, unopinionated, minimalist web framework for Node.js",
+    "getStarted": "Get Started",
+    "kawaiiLogoAlt": "Express.js kawaii logo",
+    "videoPause": "Pause background video",
+    "videoPlay": "Play background video"
+  }
+}
diff --git a/src/i18n/ui/es.json b/src/i18n/ui/es.json
new file mode 100644
index 0000000000..7954faf7c4
--- /dev/null
+++ b/src/i18n/ui/es.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Bienvenida",
+    "workInProgress": "Esta es una página de trabajo en progreso.",
+    "reviewDesignSystem": {
+      "prefix": "Revisar el",
+      "link": "Fundaciones del sistema de diseño",
+      "suffix": "página de demostración para explorar todos los tokens, primitivos y patrones."
+    }
+  },
+  "search": {
+    "placeholder": "Comience a escribir...",
+    "ariaLabel": "Empezar a escribir para buscar"
+  },
+  "theme": {
+    "toggle": "Cambiar tema",
+    "switchToLight": "Cambiar al modo de luz",
+    "switchToDark": "Cambiar a modo oscuro"
+  },
+  "version": {
+    "selectLabel": "Seleccionar versión API"
+  },
+  "nav": {
+    "mainMenu": "Menú principal",
+    "toggleMenu": "Cambiar menú",
+    "home": "casa",
+    "breadcrumb": "migas de pan",
+    "mainNavigation": "Navegación principal",
+    "selectVersion": "Seleccione la versión de documentación"
+  },
+  "menu": {
+    "main": {
+      "docs": "Documentos",
+      "api": "API",
+      "resources": "Recursos",
+      "blog": "Blog",
+      "support": "Soporte"
+    },
+    "sections": {
+      "gettingStarted": "Comenzando",
+      "guide": "Guía",
+      "migration": "Guías de Migración",
+      "advanced": "Temas avanzados",
+      "express": "express()",
+      "application": "Aplicación",
+      "request": "Solicitud",
+      "response": "Respuesta",
+      "router": "Enrutador",
+      "middleware": "Medios"
+    },
+    "items": {
+      "installing": "Instalando",
+      "helloWorld": "Hola mundo",
+      "expressGenerator": "Generador exprés",
+      "basicRouting": "Ruta básica",
+      "staticFiles": "Subrayando archivos estáticos",
+      "examples": "Ejemplos",
+      "faq": "FAQ",
+      "routing": "Ruta",
+      "writingMiddleware": "Escribiendo middleware",
+      "usingMiddleware": "Usando middleware",
+      "usingTemplateEngines": "Utilizando motores de plantillas",
+      "errorHandling": "Manejo de errores",
+      "debugging": "Depuración",
+      "behindProxies": "Behind proxies",
+      "databaseIntegration": "Integración de la base de datos",
+      "overridingExpressApi": "Reemplazar la API Express",
+      "migratingTo4": "Moviendo a Express 4",
+      "migratingTo5": "Moviendo a Express 5",
+      "buildingTemplateEngines": "Construcción de motores de plantillas",
+      "bestPracticePerformance": "Mejores prácticas de rendimiento",
+      "bestPracticeSecurity": "Buenas prácticas de seguridad",
+      "healthcheckGracefulShutdown": "Revisiones de salud y apagado con gracia",
+      "securityUpdates": "Actualización de seguridad",
+      "overview": "Resumen",
+      "properties": "Propiedades",
+      "methods": "Métodos",
+      "events": "Eventos",
+      "types": "Integrado",
+      "community": "Comunidad",
+      "glossary": "Glossary",
+      "contributing": "Contribuyendo",
+      "utils": "Utilidades",
+      "middleware": "Medios"
+    },
+    "aria": {
+      "docs": "Documentación",
+      "api": "Referencia API",
+      "resources": "Recursos",
+      "blog": "Blog",
+      "support": "Soporte",
+      "installing": "Instalando Express",
+      "helloWorld": "Hola ejemplo de mundo",
+      "expressGenerator": "Generador exprés",
+      "routing": "Guía de ruta",
+      "writingMiddleware": "Guía de middleware de escritura",
+      "usingMiddleware": "Usando la guía de middleware",
+      "usingTemplateEngines": "Usando la guía de motores de plantillas",
+      "errorHandling": "Guía de manejo de errores",
+      "debugging": "Depuración Express",
+      "behindProxies": "Expresar detrás de proxies",
+      "databaseIntegration": "Guía de integración de base de datos",
+      "overridingExpressApi": "Reemplazar la guía Express API",
+      "application": "Resumen de la aplicación",
+      "request": "Resumen de solicitudes",
+      "response": "Respuesta general",
+      "router": "Resumen de ruta",
+      "middleware": "Recursos de Middleware",
+      "community": "Recursos de la comunidad",
+      "glossary": "Glosario de términos",
+      "contributing": "Guía de contribución",
+      "utils": "Utilidades"
+    }
+  },
+  "doc": {
+    "previousPage": "Anterior",
+    "nextPage": "Siguiente",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Traducir esta página"
+  },
+  "post": {
+    "share": "Compartir",
+    "shareOnX": "Compartir en X",
+    "shareOnBluesky": "Compartir en Bluesky",
+    "shareOnLinkedIn": "Compartir en LinkedIn",
+    "shareOnSlack": "Compartir en Slack",
+    "shareOnTelegram": "Compartir en Telegram",
+    "shareOnWhatsApp": "Compartir en WhatsApp",
+    "rssFeed": "Feed RSS",
+    "copyLink": "Copiar enlace",
+    "linkCopied": "¡Enlace copiado!",
+    "toc": "En esta página",
+    "more": "Más de Express",
+    "writeBanner": "¿Interesado en escribir una publicación? \n Revisa nuestras directrices para empezar.",
+    "writeGuidelines": "Leer las directrices"
+  },
+  "toc": {
+    "overview": "Resumen"
+  },
+  "features": {
+    "title": "Claridad sobre complejidad. Para cada desarrollador.",
+    "performance": {
+      "title": "Rendimiento",
+      "body": "Express proporciona una capa delgada de características fundamentales de la aplicación web, sin ocultar las características de Node.js que usted conoce y ama."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "Con una infinidad de métodos de utilidad HTTP y middleware a tu disposición, crear una API robusta es rápido y fácil."
+    },
+    "middleware": {
+      "title": "Medios",
+      "body": "Express es un marco de enrutamiento ligero y flexible, con características básicas mínimas destinadas a ser incrementado mediante el uso de módulos Express middleware."
+    },
+    "webapplication": {
+      "title": "Aplicaciones Web",
+      "body": "Express es un marco de aplicación web de Node.js mínimo y flexible que proporciona un robusto conjunto de características para aplicaciones web y móviles."
+    }
+  },
+  "error404": {
+    "title": "404 - Página no encontrada",
+    "description": "La página que estás buscando no se pudo encontrar.",
+    "heading": "Página no encontrada",
+    "message": "La página que buscas no existe o ha sido movida.",
+    "goHome": "Ir a Inicio"
+  },
+  "hero": {
+    "tagline": "Marco web para Node.js rápido, sin opinión y minimalista",
+    "getStarted": "Empezar",
+    "videoPause": "Pausar vídeo de fondo",
+    "videoPlay": "Reproducir vídeo de fondo"
+  }
+}
diff --git a/src/i18n/ui/fr.json b/src/i18n/ui/fr.json
new file mode 100644
index 0000000000..6864fac1f6
--- /dev/null
+++ b/src/i18n/ui/fr.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Bienvenue",
+    "workInProgress": "Ceci est une page d'accueil en cours de travail.",
+    "reviewDesignSystem": {
+      "prefix": "Examiner le",
+      "link": "Conception des fondations du système",
+      "suffix": "page de démonstration pour explorer tous les jetons, primitives et motifs."
+    }
+  },
+  "search": {
+    "placeholder": "Commencez à taper...",
+    "ariaLabel": "Commencez à taper pour rechercher"
+  },
+  "theme": {
+    "toggle": "Basculer le thème",
+    "switchToLight": "Basculer en mode lumière",
+    "switchToDark": "Basculer en mode sombre"
+  },
+  "version": {
+    "selectLabel": "Sélectionnez la version de l'API"
+  },
+  "nav": {
+    "mainMenu": "Menu principal",
+    "toggleMenu": "Afficher/Masquer le menu",
+    "home": "maison",
+    "breadcrumb": "Fil d'Ariane",
+    "mainNavigation": "Navigation principale",
+    "selectVersion": "Sélectionnez la version de la documentation"
+  },
+  "menu": {
+    "main": {
+      "docs": "Documents",
+      "api": "API",
+      "resources": "Ressource",
+      "blog": "Blogue",
+      "support": "Soutien"
+    },
+    "sections": {
+      "gettingStarted": "Commencer",
+      "guide": "Tutoriel",
+      "migration": "Guides de migration",
+      "advanced": "Sujets avancés",
+      "express": "express()",
+      "application": "Application",
+      "request": "Demander",
+      "response": "Réponse",
+      "router": "Routeur",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installation en cours",
+      "helloWorld": "Bonjour le monde",
+      "expressGenerator": "Générateur Express",
+      "basicRouting": "Routage de base",
+      "staticFiles": "Servir les fichiers statiques",
+      "examples": "Exemples",
+      "faq": "Foire Aux Questions",
+      "routing": "Routage",
+      "writingMiddleware": "Écriture du middleware",
+      "usingMiddleware": "Utilisation du middleware",
+      "usingTemplateEngines": "Utiliser les moteurs de gabarits",
+      "errorHandling": "Gestion des erreurs",
+      "debugging": "Débogage",
+      "behindProxies": "Derrière les proxies",
+      "databaseIntegration": "Intégration de la base de données",
+      "overridingExpressApi": "Outrepasser l'API Express",
+      "migratingTo4": "Déplacement vers Express 4",
+      "migratingTo5": "Déplacement vers Express 5",
+      "buildingTemplateEngines": "Construire des moteurs de gabarits",
+      "bestPracticePerformance": "Meilleures pratiques de performance",
+      "bestPracticeSecurity": "Meilleures pratiques de sécurité",
+      "healthcheckGracefulShutdown": "Extinction gracieuse des contrôles de santé",
+      "securityUpdates": "Mises à jour de sécurité",
+      "overview": "Aperçu",
+      "properties": "Propriétés",
+      "methods": "Méthodes",
+      "events": "Évènements",
+      "types": "Intégrée",
+      "community": "Communauté",
+      "glossary": "Glossary",
+      "contributing": "Contribuer",
+      "utils": "Utilitaires",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Documentation",
+      "api": "Référence API",
+      "resources": "Ressource",
+      "blog": "Blogue",
+      "support": "Soutien",
+      "installing": "Installation Express",
+      "helloWorld": "Bonjour l'exemple du monde",
+      "expressGenerator": "Générateur Express",
+      "routing": "Guide de routage",
+      "writingMiddleware": "Écriture du tutoriel middleware",
+      "usingMiddleware": "Utilisation du tutoriel du middleware",
+      "usingTemplateEngines": "Utilisation du guide des moteurs de gabarits",
+      "errorHandling": "Guide de gestion des erreurs",
+      "debugging": "Débogage Express",
+      "behindProxies": "Exprimez derrière les mandataires",
+      "databaseIntegration": "Guide d'intégration de la base de données",
+      "overridingExpressApi": "Outrepasser le guide de l'API Express",
+      "application": "Aperçu de l'application",
+      "request": "Aperçu de la requête",
+      "response": "Aperçu de la réponse",
+      "router": "Aperçu du routeur",
+      "middleware": "Ressources Middleware",
+      "community": "Ressources de la communauté",
+      "glossary": "Glossaire des termes",
+      "contributing": "Guide de contribution",
+      "utils": "Utilitaires"
+    }
+  },
+  "doc": {
+    "previousPage": "Précédent",
+    "nextPage": "Suivant",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Traduire cette page"
+  },
+  "post": {
+    "share": "Partager",
+    "shareOnX": "Partager sur X",
+    "shareOnBluesky": "Partager sur Bluesky",
+    "shareOnLinkedIn": "Partager sur LinkedIn",
+    "shareOnSlack": "Partager sur Slack",
+    "shareOnTelegram": "Partager sur Telegram",
+    "shareOnWhatsApp": "Partager sur WhatsApp",
+    "rssFeed": "Flux RSS",
+    "copyLink": "Copier le lien",
+    "linkCopied": "Lien copié !",
+    "toc": "Sur cette page",
+    "more": "En savoir plus sur Express",
+    "writeBanner": "Vous souhaitez écrire un message ? \n Consultez nos consignes pour commencer.",
+    "writeGuidelines": "Lisez les directives"
+  },
+  "toc": {
+    "overview": "Aperçu"
+  },
+  "features": {
+    "title": "La clarté sur la complexité. Pour chaque développeur.",
+    "performance": {
+      "title": "Performances",
+      "body": "Express fournit une couche mince de fonctionnalités Web fondamentales, sans obscurcir les fonctionnalités de Node.js que vous connaissez et aimez."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "Avec une myriade de méthodes HTTP utilitaires et de middleware à votre disposition, créer une API robuste est rapide et facile."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express est un framework de routage léger et souple avec des fonctionnalités de base minimales destinées à être augmentées grâce à l'utilisation de modules middleware Express."
+    },
+    "webapplication": {
+      "title": "Applications Web",
+      "body": "Express est un framework d'application web Node.js minimal et flexible qui fournit un ensemble robuste de fonctionnalités pour les applications web et mobile."
+    }
+  },
+  "error404": {
+    "title": "404 - Page introuvable",
+    "description": "La page que vous cherchez est introuvable.",
+    "heading": "Page introuvable",
+    "message": "La page que vous cherchez n'existe pas ou a été déplacée.",
+    "goHome": "Aller à la page d'accueil"
+  },
+  "hero": {
+    "tagline": "Cadre web rapide, sans opinion et minimaliste pour Node.js",
+    "getStarted": "Commencer",
+    "videoPause": "Mettre en pause la vidéo de fond",
+    "videoPlay": "Lire la vidéo de fond"
+  }
+}
diff --git a/src/i18n/ui/it.json b/src/i18n/ui/it.json
new file mode 100644
index 0000000000..fe7f9532d5
--- /dev/null
+++ b/src/i18n/ui/it.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Benvenuto",
+    "workInProgress": "Questa è una homepage di work-in-progress.",
+    "reviewDesignSystem": {
+      "prefix": "Rivedi la",
+      "link": "Design System Foundations",
+      "suffix": "pagina demo per esplorare tutti i gettoni, primitive e modelli."
+    }
+  },
+  "search": {
+    "placeholder": "Inizia a digitare...",
+    "ariaLabel": "Inizia a digitare per cercare"
+  },
+  "theme": {
+    "toggle": "Attiva/Disattiva tema",
+    "switchToLight": "Passa alla modalità luce",
+    "switchToDark": "Passa alla modalità scura"
+  },
+  "version": {
+    "selectLabel": "Seleziona la versione API"
+  },
+  "nav": {
+    "mainMenu": "Menu principale",
+    "toggleMenu": "Attiva/disattiva menu",
+    "home": "home",
+    "breadcrumb": "Breadcrumb",
+    "mainNavigation": "Navigazione principale",
+    "selectVersion": "Seleziona la versione della documentazione"
+  },
+  "menu": {
+    "main": {
+      "docs": "Documenti",
+      "api": "API",
+      "resources": "Risorse",
+      "blog": "Blog",
+      "support": "Supporto"
+    },
+    "sections": {
+      "gettingStarted": "Per iniziare",
+      "guide": "Guida",
+      "migration": "Guide di migrazione",
+      "advanced": "Argomenti avanzati",
+      "express": "express()",
+      "application": "Applicazione",
+      "request": "Richiesta",
+      "response": "Risposta",
+      "router": "Router",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installazione",
+      "helloWorld": "Ciao mondo",
+      "expressGenerator": "Generatore espresso",
+      "basicRouting": "Instradamento base",
+      "staticFiles": "Servire file statici",
+      "examples": "Esempi",
+      "faq": "FAQ",
+      "routing": "Routing",
+      "writingMiddleware": "Scrittura middleware",
+      "usingMiddleware": "Usare middleware",
+      "usingTemplateEngines": "Utilizzo di modelli di motori",
+      "errorHandling": "Gestione errori",
+      "debugging": "Debug",
+      "behindProxies": "Dietro proxy",
+      "databaseIntegration": "Integrazione database",
+      "overridingExpressApi": "Sovrascrivendo l'API Express",
+      "migratingTo4": "Passaggio a Express 4",
+      "migratingTo5": "Passaggio a Express 5",
+      "buildingTemplateEngines": "Motori modello di costruzione",
+      "bestPracticePerformance": "Migliori pratiche di prestazione",
+      "bestPracticeSecurity": "Migliori pratiche di sicurezza",
+      "healthcheckGracefulShutdown": "Controlli di salute & spegnimento aggraziato",
+      "securityUpdates": "Aggiornamenti di sicurezza",
+      "overview": "Panoramica",
+      "properties": "Proprietà",
+      "methods": "Metodi",
+      "events": "Eventi",
+      "types": "Integrato",
+      "community": "Community",
+      "glossary": "Glossary",
+      "contributing": "Contribuire",
+      "utils": "Utilità",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Documentazione",
+      "api": "Riferimento API",
+      "resources": "Risorse",
+      "blog": "Blog",
+      "support": "Supporto",
+      "installing": "Installazione Di Express",
+      "helloWorld": "Ciao esempio mondiale",
+      "expressGenerator": "Generatore espresso",
+      "routing": "Guida di routing",
+      "writingMiddleware": "Scrittura guida middleware",
+      "usingMiddleware": "Utilizzo della guida middleware",
+      "usingTemplateEngines": "Utilizzo guida motori modello",
+      "errorHandling": "Guida gestione errori",
+      "debugging": "Debug Express",
+      "behindProxies": "Espresso dietro i proxy",
+      "databaseIntegration": "Guida all'integrazione del database",
+      "overridingExpressApi": "Superare la guida API di Express",
+      "application": "Panoramica dell'applicazione",
+      "request": "Panoramica richiesta",
+      "response": "Panoramica delle risposte",
+      "router": "Panoramica del router",
+      "middleware": "Risorse Middleware",
+      "community": "Risorse comunitarie",
+      "glossary": "Glossario dei termini",
+      "contributing": "Guida al contributo",
+      "utils": "Utilità"
+    }
+  },
+  "doc": {
+    "previousPage": "Precedente",
+    "nextPage": "Successivo",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Traduci questa pagina"
+  },
+  "post": {
+    "share": "Condividi",
+    "shareOnX": "Condividi su X",
+    "shareOnBluesky": "Condividi su Bluesky",
+    "shareOnLinkedIn": "Condividi su LinkedIn",
+    "shareOnSlack": "Condividi su Slack",
+    "shareOnTelegram": "Condividi su Telegram",
+    "shareOnWhatsApp": "Condividi su WhatsApp",
+    "rssFeed": "Feed RSS",
+    "copyLink": "Copia link",
+    "linkCopied": "Link copiato!",
+    "toc": "Su questa pagina",
+    "more": "Altro da Express",
+    "writeBanner": "Sei interessato a scrivere un post? \n Scopri le nostre linee guida per iniziare.",
+    "writeGuidelines": "Leggi le linee guida"
+  },
+  "toc": {
+    "overview": "Panoramica"
+  },
+  "features": {
+    "title": "Chiarezza sulla complessità. Per ogni sviluppatore.",
+    "performance": {
+      "title": "Prestazioni",
+      "body": "Express fornisce un sottile strato di funzionalità di applicazione web fondamentali, senza oscurare le caratteristiche di Node.js che conoscete e amate."
+    },
+    "api": {
+      "title": "API",
+      "body": "Con una miriade di metodi di utilità HTTP e middleware a vostra disposizione, la creazione di un'API robusta è facile e veloce."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express è un framework di routing leggero e flessibile con caratteristiche essenziali minimali che devono essere aumentate attraverso l'uso di moduli middleware Express."
+    },
+    "webapplication": {
+      "title": "Applicazioni Web",
+      "body": "Express è un framework di applicazioni web di Node.js minimale e flessibile che fornisce un insieme robusto di funzionalità per applicazioni web e mobili."
+    }
+  },
+  "error404": {
+    "title": "404 - Pagina Non Trovata",
+    "description": "La pagina che stai cercando non è stata trovata.",
+    "heading": "Pagina Non Trovata",
+    "message": "La pagina che stai cercando non esiste o è stata spostata.",
+    "goHome": "Vai a Home"
+  },
+  "hero": {
+    "tagline": "Quadro web veloce, senza pareri, minimalista per Node.js",
+    "getStarted": "Per Iniziare",
+    "videoPause": "Pausa video in background",
+    "videoPlay": "Riproduci video in background"
+  }
+}
diff --git a/src/i18n/ui/ja.json b/src/i18n/ui/ja.json
new file mode 100644
index 0000000000..143632500b
--- /dev/null
+++ b/src/i18n/ui/ja.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "ようこそ",
+    "workInProgress": "これは進行中のホームページです。",
+    "reviewDesignSystem": {
+      "prefix": "レビュー：",
+      "link": "デザインシステム基礎",
+      "suffix": "すべてのトークン、プリミティブ、パターンを調べるデモページ。"
+    }
+  },
+  "search": {
+    "placeholder": "入力を開始...",
+    "ariaLabel": "検索を開始する"
+  },
+  "theme": {
+    "toggle": "テーマの切り替え",
+    "switchToLight": "ライトモードに切り替える",
+    "switchToDark": "ダークモードに切り替える"
+  },
+  "version": {
+    "selectLabel": "API バージョンを選択"
+  },
+  "nav": {
+    "mainMenu": "メインメニュー",
+    "toggleMenu": "切り替えメニュー",
+    "home": "ホーム",
+    "breadcrumb": "パンくずリスト",
+    "mainNavigation": "メインナビゲーション",
+    "selectVersion": "ドキュメントのバージョンを選択"
+  },
+  "menu": {
+    "main": {
+      "docs": "ドキュメント",
+      "api": "API",
+      "resources": "リソース",
+      "blog": "ブログ",
+      "support": "サポート"
+    },
+    "sections": {
+      "gettingStarted": "はじめに",
+      "guide": "ガイド",
+      "migration": "移行ガイド",
+      "advanced": "高度なトピック",
+      "express": "express()",
+      "application": "アプリケーション",
+      "request": "リクエスト",
+      "response": "回答",
+      "router": "Router",
+      "middleware": "ミドルウェア"
+    },
+    "items": {
+      "installing": "インストール中",
+      "helloWorld": "Hello world",
+      "expressGenerator": "Express generator",
+      "basicRouting": "基本ルーティング",
+      "staticFiles": "静的ファイルを提供中",
+      "examples": "例",
+      "faq": "FAQ",
+      "routing": "ルーティング",
+      "writingMiddleware": "ミドルウェアの書き込み",
+      "usingMiddleware": "ミドルウェアの使用",
+      "usingTemplateEngines": "テンプレートエンジンの使用",
+      "errorHandling": "エラー処理",
+      "debugging": "デバッグ",
+      "behindProxies": "プロキシの背後にある",
+      "databaseIntegration": "データベースの統合",
+      "overridingExpressApi": "Express API のオーバーライド",
+      "migratingTo4": "Express 4に移動中",
+      "migratingTo5": "Express 5に移動中",
+      "buildingTemplateEngines": "ビルディングテンプレートエンジン",
+      "bestPracticePerformance": "パフォーマンスのベストプラクティス",
+      "bestPracticeSecurity": "セキュリティのベストプラクティス",
+      "healthcheckGracefulShutdown": "ヘルスチェックと優雅な停止",
+      "securityUpdates": "セキュリティの更新",
+      "overview": "概要",
+      "properties": "プロパティー",
+      "methods": "メソッド",
+      "events": "イベント",
+      "types": "ビルトイン",
+      "community": "コミュニティ",
+      "glossary": "Glossary",
+      "contributing": "コントリビューション",
+      "utils": "ユーティリティ",
+      "middleware": "ミドルウェア"
+    },
+    "aria": {
+      "docs": "ドキュメント",
+      "api": "APIリファレンス",
+      "resources": "リソース",
+      "blog": "ブログ",
+      "support": "サポート",
+      "installing": "Express のインストール",
+      "helloWorld": "Hello world example",
+      "expressGenerator": "Express generator",
+      "routing": "ルーティングガイド",
+      "writingMiddleware": "ミドルウェアガイドを書く",
+      "usingMiddleware": "ミドルウェアガイドの使用",
+      "usingTemplateEngines": "テンプレートエンジンガイドの使用",
+      "errorHandling": "ガイドの処理中にエラー",
+      "debugging": "Expressのデバッグ",
+      "behindProxies": "プロキシの背後にあるエクスプレス",
+      "databaseIntegration": "データベース統合ガイド",
+      "overridingExpressApi": "Express API ガイドをオーバーライド",
+      "application": "アプリケーションの概要",
+      "request": "要求の概要",
+      "response": "応答の概要",
+      "router": "ルーターの概要",
+      "middleware": "ミドルウェアのリソース",
+      "community": "コミュニティリソース",
+      "glossary": "用語集",
+      "contributing": "貢献ガイド",
+      "utils": "ユーティリティ"
+    }
+  },
+  "doc": {
+    "previousPage": "前",
+    "nextPage": "次へ",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "このページを翻訳"
+  },
+  "post": {
+    "share": "共有",
+    "shareOnX": "X上で共有",
+    "shareOnBluesky": "Blueskyで共有",
+    "shareOnLinkedIn": "LinkedInで共有",
+    "shareOnSlack": "Slack で共有",
+    "shareOnTelegram": "Telegramで共有",
+    "shareOnWhatsApp": "WhatsAppで共有",
+    "rssFeed": "RSS フィード",
+    "copyLink": "リンクをコピー",
+    "linkCopied": "リンクをコピーしました！",
+    "toc": "このページ",
+    "more": "エクスプレスからもっと見る",
+    "writeBanner": "投稿を書くことに興味がありますか？ \n 私たちのガイドラインをチェックして始めましょう。",
+    "writeGuidelines": "ガイドラインを読む"
+  },
+  "toc": {
+    "overview": "概要"
+  },
+  "features": {
+    "title": "複雑性より明快です。すべての開発者にとって。",
+    "performance": {
+      "title": "パフォーマンス",
+      "body": "Express は基本的な Web アプリケーション機能の薄い層を提供しますが、Node.js の機能を不明瞭にすることはありません。"
+    },
+    "api": {
+      "title": "API",
+      "body": "無数のHTTPユーティリティメソッドとミドルウェアを自由に使えば、堅牢なAPIを簡単かつ迅速に作成できます。"
+    },
+    "middleware": {
+      "title": "ミドルウェア",
+      "body": "Expressは軽量で柔軟なルーティングフレームワークで、最小限のコア機能を備え、Expressミドルウェアモジュールを使用して拡張します。"
+    },
+    "webapplication": {
+      "title": "Webアプリケーション",
+      "body": "Express は最小限かつ柔軟な Node.js の Web アプリケーションフレームワークで、Web およびモバイル アプリケーションに堅牢な一連の機能を提供します。"
+    }
+  },
+  "error404": {
+    "title": "404 - ページが見つかりません",
+    "description": "お探しのページが見つかりませんでした。",
+    "heading": "ページが見つかりません",
+    "message": "お探しのページは存在しないか、移動されています。",
+    "goHome": "ホームへ移動"
+  },
+  "hero": {
+    "tagline": "Node.jsの高速、非公開、最小限のWebフレームワーク",
+    "getStarted": "はじめよう",
+    "videoPause": "背景ビデオを一時停止",
+    "videoPlay": "背景ビデオを再生"
+  }
+}
diff --git a/src/i18n/ui/ko.json b/src/i18n/ui/ko.json
new file mode 100644
index 0000000000..5a085e2a46
--- /dev/null
+++ b/src/i18n/ui/ko.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Welcome",
+    "workInProgress": "This is a work-in-progress homepage.",
+    "reviewDesignSystem": {
+      "prefix": "Review the",
+      "link": "Design System Foundations",
+      "suffix": "demo page to explore all tokens, primitives, and patterns."
+    }
+  },
+  "search": {
+    "placeholder": "Start typing...",
+    "ariaLabel": "Start typing to search"
+  },
+  "theme": {
+    "toggle": "Toggle theme",
+    "switchToLight": "Switch to light mode",
+    "switchToDark": "Switch to dark mode"
+  },
+  "version": {
+    "selectLabel": "Select API version"
+  },
+  "nav": {
+    "mainMenu": "Main menu",
+    "toggleMenu": "Toggle menu",
+    "home": "home",
+    "breadcrumb": "Breadcrumb",
+    "mainNavigation": "Main navigation",
+    "selectVersion": "Select documentation version"
+  },
+  "menu": {
+    "main": {
+      "docs": "Docs",
+      "api": "API",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support"
+    },
+    "sections": {
+      "gettingStarted": "Getting started",
+      "guide": "Guide",
+      "migration": "Migration guides",
+      "advanced": "Advanced topics",
+      "express": "express()",
+      "application": "Application",
+      "request": "Request",
+      "response": "Response",
+      "router": "Router",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installing",
+      "helloWorld": "Hello world",
+      "expressGenerator": "Express generator",
+      "basicRouting": "Basic routing",
+      "staticFiles": "Serving static files",
+      "examples": "Examples",
+      "faq": "FAQ",
+      "routing": "Routing",
+      "writingMiddleware": "Writing middleware",
+      "usingMiddleware": "Using middleware",
+      "usingTemplateEngines": "Using template engines",
+      "errorHandling": "Error handling",
+      "debugging": "Debugging",
+      "behindProxies": "Behind proxies",
+      "databaseIntegration": "Database integration",
+      "overridingExpressApi": "Overriding the Express API",
+      "migratingTo4": "Moving to Express 4",
+      "migratingTo5": "Moving to Express 5",
+      "buildingTemplateEngines": "Building template engines",
+      "bestPracticePerformance": "Performance best practices",
+      "bestPracticeSecurity": "Security best practices",
+      "healthcheckGracefulShutdown": "Health checks & graceful shutdown",
+      "securityUpdates": "Security updates",
+      "overview": "Overview",
+      "properties": "Properties",
+      "methods": "Methods",
+      "events": "Events",
+      "types": "Built-in",
+      "community": "Community",
+      "glossary": "Glossary",
+      "contributing": "Contributing",
+      "utils": "Utilities",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Documentation",
+      "api": "API Reference",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support",
+      "installing": "Installing Express",
+      "helloWorld": "Hello world example",
+      "expressGenerator": "Express generator",
+      "routing": "Routing guide",
+      "writingMiddleware": "Writing middleware guide",
+      "usingMiddleware": "Using middleware guide",
+      "usingTemplateEngines": "Using template engines guide",
+      "errorHandling": "Error handling guide",
+      "debugging": "Debugging Express",
+      "behindProxies": "Express behind proxies",
+      "databaseIntegration": "Database integration guide",
+      "overridingExpressApi": "Overriding the Express API guide",
+      "application": "Application overview",
+      "request": "Request overview",
+      "response": "Response overview",
+      "router": "Router overview",
+      "middleware": "Middleware resources",
+      "community": "Community resources",
+      "glossary": "Glossary of terms",
+      "contributing": "Contributing guide",
+      "utils": "Utilities"
+    }
+  },
+  "doc": {
+    "previousPage": "Previous",
+    "nextPage": "Next",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Translate this page"
+  },
+  "post": {
+    "share": "Share",
+    "shareOnX": "Share on X",
+    "shareOnBluesky": "Share on Bluesky",
+    "shareOnLinkedIn": "Share on LinkedIn",
+    "shareOnSlack": "Share on Slack",
+    "shareOnTelegram": "Share on Telegram",
+    "shareOnWhatsApp": "Share on WhatsApp",
+    "rssFeed": "RSS Feed",
+    "copyLink": "Copy link",
+    "linkCopied": "Link copied!",
+    "toc": "On this page",
+    "more": "More from Express",
+    "writeBanner": "Interested in writing a post? \n Check out our guidelines to get started.",
+    "writeGuidelines": "Read the guidelines"
+  },
+  "toc": {
+    "overview": "Overview"
+  },
+  "features": {
+    "title": "Clarity over complexity. For every developer.",
+    "performance": {
+      "title": "Performance",
+      "body": "Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express is a lightweight and flexible routing framework with minimal core features meant to be augmented through the use of Express middleware modules."
+    },
+    "webapplication": {
+      "title": "Web Applications",
+      "body": "Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications."
+    }
+  },
+  "error404": {
+    "title": "404 - Page Not Found",
+    "description": "The page you are looking for could not be found.",
+    "heading": "Page Not Found",
+    "message": "The page you are looking for does not exist or has been moved.",
+    "goHome": "Go to Home"
+  },
+  "hero": {
+    "tagline": "Fast, unopinionated, minimalist web framework for Node.js",
+    "getStarted": "Get Started",
+    "videoPause": "Pause background video",
+    "videoPlay": "Play background video"
+  }
+}
diff --git a/src/i18n/ui/pt-br.json b/src/i18n/ui/pt-br.json
new file mode 100644
index 0000000000..721361c1e8
--- /dev/null
+++ b/src/i18n/ui/pt-br.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Boas-vindas",
+    "workInProgress": "Esta é uma página inicial em progresso.",
+    "reviewDesignSystem": {
+      "prefix": "Revisar o",
+      "link": "Criar Fundamentos de Sistema",
+      "suffix": "página demo para explorar todos os tokens, primitivos e padrões."
+    }
+  },
+  "search": {
+    "placeholder": "Comece a digitar...",
+    "ariaLabel": "Comece a digitar para pesquisar"
+  },
+  "theme": {
+    "toggle": "Alternar tema",
+    "switchToLight": "Alternar para o modo claro",
+    "switchToDark": "Mudar para o modo escuro"
+  },
+  "version": {
+    "selectLabel": "Selecionar versão da API"
+  },
+  "nav": {
+    "mainMenu": "Menu principal",
+    "toggleMenu": "Abrir/fechar menu",
+    "home": "casa",
+    "breadcrumb": "Trilha",
+    "mainNavigation": "Navegação principal",
+    "selectVersion": "Selecionar versão da documentação"
+  },
+  "menu": {
+    "main": {
+      "docs": "Documentação",
+      "api": "API",
+      "resources": "Recursos",
+      "blog": "Blogue",
+      "support": "SUPORTE"
+    },
+    "sections": {
+      "gettingStarted": "Primeiros Passos",
+      "guide": "Guia",
+      "migration": "Guias de migração",
+      "advanced": "Tópicos avançados",
+      "express": "express()",
+      "application": "Solicitação",
+      "request": "Pedir",
+      "response": "Resposta",
+      "router": "Roteador",
+      "middleware": "Mediador"
+    },
+    "items": {
+      "installing": "Instalando",
+      "helloWorld": "Olá, mundo",
+      "expressGenerator": "Gerador expresso",
+      "basicRouting": "Roteamento básico",
+      "staticFiles": "Servindo arquivos estáticos",
+      "examples": "Exemplos",
+      "faq": "Perguntas Frequentes",
+      "routing": "Roteamento",
+      "writingMiddleware": "Escrevendo middleware",
+      "usingMiddleware": "Usando o middleware",
+      "usingTemplateEngines": "Usando motores de modelos",
+      "errorHandling": "Manipulação de erros",
+      "debugging": "Depuração",
+      "behindProxies": "Atrás dos proxies",
+      "databaseIntegration": "Integração com base de dados",
+      "overridingExpressApi": "Sobrescrevendo a API Expresso",
+      "migratingTo4": "Mover para Expresso 4",
+      "migratingTo5": "Movendo para Expresso 5",
+      "buildingTemplateEngines": "Mecanismos de construção",
+      "bestPracticePerformance": "Melhores práticas de desempenho",
+      "bestPracticeSecurity": "Melhores práticas de segurança",
+      "healthcheckGracefulShutdown": "Verificações de saúde e desligamento gracioso",
+      "securityUpdates": "Atualizações de segurança",
+      "overview": "Geral",
+      "properties": "propriedades",
+      "methods": "Métodos",
+      "events": "Eventos",
+      "types": "Internos",
+      "community": "Comunidade",
+      "glossary": "Glossary",
+      "contributing": "Contribuições",
+      "utils": "Serviços",
+      "middleware": "Mediador"
+    },
+    "aria": {
+      "docs": "Documentação",
+      "api": "Referência de API",
+      "resources": "Recursos",
+      "blog": "Blogue",
+      "support": "SUPORTE",
+      "installing": "Instalando o Express",
+      "helloWorld": "Olá, exemplo do mundo",
+      "expressGenerator": "Gerador expresso",
+      "routing": "Guia de roteamento",
+      "writingMiddleware": "Escrevendo o guia middleware",
+      "usingMiddleware": "Usando guia de middleware",
+      "usingTemplateEngines": "Usando guia de motores de modelos",
+      "errorHandling": "Guia para manipulação de erros",
+      "debugging": "Expresso de depuração",
+      "behindProxies": "Expresso atrás dos proxies",
+      "databaseIntegration": "Guia de integração do banco",
+      "overridingExpressApi": "Sobrescrevendo o guia API Expresso",
+      "application": "Resumo do aplicativo",
+      "request": "Solicitar resumo",
+      "response": "Resumo da resposta",
+      "router": "Visão geral do roteador",
+      "middleware": "Recursos do Mediador",
+      "community": "Recursos da Comunidade",
+      "glossary": "Glossário de termos",
+      "contributing": "Guia contribuidor",
+      "utils": "Serviços"
+    }
+  },
+  "doc": {
+    "previousPage": "Anterior",
+    "nextPage": "Próximo",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Traduzir esta página"
+  },
+  "post": {
+    "share": "Compartilhar",
+    "shareOnX": "Compartilhar no X",
+    "shareOnBluesky": "Compartilhar no Bluesky",
+    "shareOnLinkedIn": "Compartilhar no LinkedIn",
+    "shareOnSlack": "Compartilhar no Slack",
+    "shareOnTelegram": "Compartilhar no Telegram",
+    "shareOnWhatsApp": "Compartilhe no WhatsApp",
+    "rssFeed": "Feed RSS",
+    "copyLink": "Link de cópia",
+    "linkCopied": "Link copiado!",
+    "toc": "Nesta página",
+    "more": "Mais do Express",
+    "writeBanner": "Interessou-se em escrever uma publicação? U \n Confira nossas diretrizes para começar.",
+    "writeGuidelines": "Leia as diretrizes"
+  },
+  "toc": {
+    "overview": "Geral"
+  },
+  "features": {
+    "title": "Clareza sobre complexidade. Para cada desenvolvedor.",
+    "performance": {
+      "title": "Desempenho",
+      "body": "Expresso fornece uma fina camada de recursos fundamentais de aplicativos web, sem obscurecer recursos de Node.js que você conhece e ama."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "Com uma miríade de métodos de utilitário HTTP e middleware à sua disposição, criar uma API robusta é rápido e fácil."
+    },
+    "middleware": {
+      "title": "Mediador",
+      "body": "Expresso é um framework de roteamento leve e flexível com recursos básicos mínimos destinados a serem aumentados através do uso de módulos de middleware Express."
+    },
+    "webapplication": {
+      "title": "Aplicativos Web",
+      "body": "Expresso é um framework de aplicativos web Node.js mínimo e flexível que fornece um conjunto robusto de recursos para aplicativos web e móveis."
+    }
+  },
+  "error404": {
+    "title": "404 - Página não encontrada",
+    "description": "A página que você está procurando não pôde ser encontrada.",
+    "heading": "Página não encontrada",
+    "message": "A página que você procura não existe ou foi movida.",
+    "goHome": "Ir para o início"
+  },
+  "hero": {
+    "tagline": "Framework web para Node.js rápido, não opinionizado e minimalista",
+    "getStarted": "Comece Agora",
+    "videoPause": "Pausar vídeo em segundo plano",
+    "videoPlay": "Reproduzir vídeo de fundo"
+  }
+}
diff --git a/src/i18n/ui/zh-cn.json b/src/i18n/ui/zh-cn.json
new file mode 100644
index 0000000000..98b2590d7b
--- /dev/null
+++ b/src/i18n/ui/zh-cn.json
@@ -0,0 +1,178 @@
+{
+  "home": {
+    "welcome": "欢迎",
+    "workInProgress": "这是正在开发中的主页。",
+    "reviewDesignSystem": {
+      "prefix": "查看",
+      "link": "设计系统基础",
+      "suffix": "演示页面以探索所有令牌、原语和模式。"
+    }
+  },
+  "search": {
+    "placeholder": "开始输入...",
+    "ariaLabel": "开始输入以搜索"
+  },
+  "theme": {
+    "toggle": "切换主题",
+    "switchToLight": "切换到浅色模式",
+    "switchToDark": "切换到深色模式"
+  },
+  "version": {
+    "selectLabel": "选择 API 版本"
+  },
+  "language": {
+    "selectLabel": "选择语言"
+  },
+  "nav": {
+    "mainMenu": "主菜单",
+    "toggleMenu": "切换菜单",
+    "home": "首页",
+    "breadcrumb": "面包屑导航",
+    "mainNavigation": "主导航",
+    "selectVersion": "选择文档版本"
+  },
+  "menu": {
+    "main": {
+      "docs": "文档",
+      "api": "API",
+      "resources": "资源",
+      "blog": "博客",
+      "support": "支持"
+    },
+    "sections": {
+      "gettingStarted": "入门",
+      "guide": "指南",
+      "migration": "迁移指南",
+      "advanced": "高级主题",
+      "express": "express()",
+      "application": "应用程序",
+      "request": "请求",
+      "response": "响应",
+      "router": "路由器",
+      "middleware": "中间件"
+    },
+    "items": {
+      "installing": "安装",
+      "helloWorld": "Hello world",
+      "expressGenerator": "Express 生成器",
+      "basicRouting": "基础路由",
+      "staticFiles": "静态文件服务",
+      "examples": "示例",
+      "faq": "常见问题",
+      "routing": "路由",
+      "writingMiddleware": "编写中间件",
+      "usingMiddleware": "使用中间件",
+      "usingTemplateEngines": "使用模板引擎",
+      "errorHandling": "错误处理",
+      "debugging": "调试",
+      "behindProxies": "代理背后",
+      "databaseIntegration": "数据库集成",
+      "overridingExpressApi": "覆盖 Express API",
+      "migratingTo4": "迁移到 Express 4",
+      "migratingTo5": "迁移到 Express 5",
+      "buildingTemplateEngines": "构建模板引擎",
+      "bestPracticePerformance": "性能最佳实践",
+      "bestPracticeSecurity": "安全最佳实践",
+      "healthcheckGracefulShutdown": "健康检查 & 优雅关闭",
+      "securityUpdates": "安全更新",
+      "overview": "概览",
+      "properties": "属性",
+      "methods": "方法",
+      "events": "事件",
+      "types": "内置",
+      "community": "社区",
+      "glossary": "术语表",
+      "contributing": "贡献",
+      "utils": "工具",
+      "middleware": "中间件"
+    },
+    "aria": {
+      "docs": "文档",
+      "api": "API 参考",
+      "resources": "资源",
+      "blog": "博客",
+      "support": "支持",
+      "installing": "安装 Express",
+      "helloWorld": "Hello world 示例",
+      "expressGenerator": "Express 生成器",
+      "routing": "路由指南",
+      "writingMiddleware": "编写中间件指南",
+      "usingMiddleware": "使用中间件指南",
+      "usingTemplateEngines": "使用模板引擎指南",
+      "errorHandling": "错误处理指南",
+      "debugging": "调试 Express",
+      "behindProxies": "代理背后的 Express",
+      "databaseIntegration": "数据库集成指南",
+      "overridingExpressApi": "覆盖 Express API 指南",
+      "application": "应用程序概览",
+      "request": "请求概览",
+      "response": "响应概览",
+      "router": "路由器概览",
+      "middleware": "中间件资源",
+      "community": "社区资源",
+      "glossary": "术语表",
+      "contributing": "贡献指南",
+      "utils": "工具"
+    }
+  },
+  "doc": {
+    "previousPage": "上一页",
+    "nextPage": "下一页",
+    "pageNavigation": "页面导航"
+  },
+  "page": {
+    "editOnGitHub": "在 GitHub 上编辑",
+    "translateThis": "翻译此页面"
+  },
+  "post": {
+    "share": "分享",
+    "shareOnX": "在 X 上分享",
+    "shareOnBluesky": "在 Bluesky 上分享",
+    "shareOnLinkedIn": "在 LinkedIn 上分享",
+    "shareOnSlack": "在 Slack 上分享",
+    "shareOnTelegram": "在 Telegram 上分享",
+    "shareOnWhatsApp": "在 WhatsApp 上分享",
+    "rssFeed": "RSS 订阅",
+    "copyLink": "复制链接",
+    "linkCopied": "链接已复制！",
+    "toc": "本页内容",
+    "more": "更多 Express 内容",
+    "writeBanner": "有兴趣写文章吗？\n查看我们的指南开始。",
+    "writeGuidelines": "阅读指南"
+  },
+  "toc": {
+    "overview": "概览"
+  },
+  "features": {
+    "title": "清晰胜于复杂。为每位开发者而设。",
+    "performance": {
+      "title": "性能",
+      "body": "Express 提供了 Web 应用的基础功能层，同时不隐藏你熟悉的 Node.js 功能。"
+    },
+    "api": {
+      "title": "API",
+      "body": "借助丰富的 HTTP 工具方法和中间件，可快速轻松地创建强大的 API。"
+    },
+    "middleware": {
+      "title": "中间件",
+      "body": "Express 是轻量且灵活的路由框架，核心功能最小，可通过中间件模块扩展。"
+    },
+    "webapplication": {
+      "title": "Web 应用",
+      "body": "Express 是一个简洁灵活的 Node.js Web 应用框架，为 Web 和移动应用提供强大功能集。"
+    }
+  },
+  "error404": {
+    "title": "404 - 页面未找到",
+    "description": "您访问的页面不存在。",
+    "heading": "页面未找到",
+    "message": "您访问的页面不存在或已被移动。",
+    "goHome": "返回首页"
+  },
+  "hero": {
+    "tagline": "Node.js 的快速、简约 Web 框架",
+    "getStarted": "开始使用",
+    "videoPause": "暂停背景视频",
+    "videoPlay": "播放背景视频"
+  }
+}
diff --git a/src/i18n/ui/zh-tw.json b/src/i18n/ui/zh-tw.json
new file mode 100644
index 0000000000..5a085e2a46
--- /dev/null
+++ b/src/i18n/ui/zh-tw.json
@@ -0,0 +1,175 @@
+{
+  "home": {
+    "welcome": "Welcome",
+    "workInProgress": "This is a work-in-progress homepage.",
+    "reviewDesignSystem": {
+      "prefix": "Review the",
+      "link": "Design System Foundations",
+      "suffix": "demo page to explore all tokens, primitives, and patterns."
+    }
+  },
+  "search": {
+    "placeholder": "Start typing...",
+    "ariaLabel": "Start typing to search"
+  },
+  "theme": {
+    "toggle": "Toggle theme",
+    "switchToLight": "Switch to light mode",
+    "switchToDark": "Switch to dark mode"
+  },
+  "version": {
+    "selectLabel": "Select API version"
+  },
+  "nav": {
+    "mainMenu": "Main menu",
+    "toggleMenu": "Toggle menu",
+    "home": "home",
+    "breadcrumb": "Breadcrumb",
+    "mainNavigation": "Main navigation",
+    "selectVersion": "Select documentation version"
+  },
+  "menu": {
+    "main": {
+      "docs": "Docs",
+      "api": "API",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support"
+    },
+    "sections": {
+      "gettingStarted": "Getting started",
+      "guide": "Guide",
+      "migration": "Migration guides",
+      "advanced": "Advanced topics",
+      "express": "express()",
+      "application": "Application",
+      "request": "Request",
+      "response": "Response",
+      "router": "Router",
+      "middleware": "Middleware"
+    },
+    "items": {
+      "installing": "Installing",
+      "helloWorld": "Hello world",
+      "expressGenerator": "Express generator",
+      "basicRouting": "Basic routing",
+      "staticFiles": "Serving static files",
+      "examples": "Examples",
+      "faq": "FAQ",
+      "routing": "Routing",
+      "writingMiddleware": "Writing middleware",
+      "usingMiddleware": "Using middleware",
+      "usingTemplateEngines": "Using template engines",
+      "errorHandling": "Error handling",
+      "debugging": "Debugging",
+      "behindProxies": "Behind proxies",
+      "databaseIntegration": "Database integration",
+      "overridingExpressApi": "Overriding the Express API",
+      "migratingTo4": "Moving to Express 4",
+      "migratingTo5": "Moving to Express 5",
+      "buildingTemplateEngines": "Building template engines",
+      "bestPracticePerformance": "Performance best practices",
+      "bestPracticeSecurity": "Security best practices",
+      "healthcheckGracefulShutdown": "Health checks & graceful shutdown",
+      "securityUpdates": "Security updates",
+      "overview": "Overview",
+      "properties": "Properties",
+      "methods": "Methods",
+      "events": "Events",
+      "types": "Built-in",
+      "community": "Community",
+      "glossary": "Glossary",
+      "contributing": "Contributing",
+      "utils": "Utilities",
+      "middleware": "Middleware"
+    },
+    "aria": {
+      "docs": "Documentation",
+      "api": "API Reference",
+      "resources": "Resources",
+      "blog": "Blog",
+      "support": "Support",
+      "installing": "Installing Express",
+      "helloWorld": "Hello world example",
+      "expressGenerator": "Express generator",
+      "routing": "Routing guide",
+      "writingMiddleware": "Writing middleware guide",
+      "usingMiddleware": "Using middleware guide",
+      "usingTemplateEngines": "Using template engines guide",
+      "errorHandling": "Error handling guide",
+      "debugging": "Debugging Express",
+      "behindProxies": "Express behind proxies",
+      "databaseIntegration": "Database integration guide",
+      "overridingExpressApi": "Overriding the Express API guide",
+      "application": "Application overview",
+      "request": "Request overview",
+      "response": "Response overview",
+      "router": "Router overview",
+      "middleware": "Middleware resources",
+      "community": "Community resources",
+      "glossary": "Glossary of terms",
+      "contributing": "Contributing guide",
+      "utils": "Utilities"
+    }
+  },
+  "doc": {
+    "previousPage": "Previous",
+    "nextPage": "Next",
+    "pageNavigation": "Page navigation"
+  },
+  "page": {
+    "editOnGitHub": "Edit on GitHub",
+    "translateThis": "Translate this page"
+  },
+  "post": {
+    "share": "Share",
+    "shareOnX": "Share on X",
+    "shareOnBluesky": "Share on Bluesky",
+    "shareOnLinkedIn": "Share on LinkedIn",
+    "shareOnSlack": "Share on Slack",
+    "shareOnTelegram": "Share on Telegram",
+    "shareOnWhatsApp": "Share on WhatsApp",
+    "rssFeed": "RSS Feed",
+    "copyLink": "Copy link",
+    "linkCopied": "Link copied!",
+    "toc": "On this page",
+    "more": "More from Express",
+    "writeBanner": "Interested in writing a post? \n Check out our guidelines to get started.",
+    "writeGuidelines": "Read the guidelines"
+  },
+  "toc": {
+    "overview": "Overview"
+  },
+  "features": {
+    "title": "Clarity over complexity. For every developer.",
+    "performance": {
+      "title": "Performance",
+      "body": "Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love."
+    },
+    "api": {
+      "title": "APIs",
+      "body": "With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy."
+    },
+    "middleware": {
+      "title": "Middleware",
+      "body": "Express is a lightweight and flexible routing framework with minimal core features meant to be augmented through the use of Express middleware modules."
+    },
+    "webapplication": {
+      "title": "Web Applications",
+      "body": "Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications."
+    }
+  },
+  "error404": {
+    "title": "404 - Page Not Found",
+    "description": "The page you are looking for could not be found.",
+    "heading": "Page Not Found",
+    "message": "The page you are looking for does not exist or has been moved.",
+    "goHome": "Go to Home"
+  },
+  "hero": {
+    "tagline": "Fast, unopinionated, minimalist web framework for Node.js",
+    "getStarted": "Get Started",
+    "videoPause": "Pause background video",
+    "videoPlay": "Play background video"
+  }
+}
diff --git a/src/i18n/utils.ts b/src/i18n/utils.ts
new file mode 100644
index 0000000000..562188a1f8
--- /dev/null
+++ b/src/i18n/utils.ts
@@ -0,0 +1,51 @@
+import { ui, defaultLang, languages } from './locales';
+
+export function getLangFromUrl(url: URL) {
+  const [, lang] = url.pathname.split('/');
+  if (lang in ui) return lang as keyof typeof ui;
+  return defaultLang;
+}
+
+function getNestedValue(obj: (typeof ui)[keyof typeof ui], path: string): string | undefined {
+  const value = path.split('.').reduce((acc: unknown, part) => {
+    if (acc && typeof acc === 'object' && part in acc) {
+      return (acc as Record<string, unknown>)[part];
+    }
+    return undefined;
+  }, obj);
+
+  return typeof value === 'string' ? value : undefined;
+}
+
+export function useTranslations(lang: keyof typeof ui) {
+  return function t(key: string): string {
+    return getNestedValue(ui[lang], key) ?? getNestedValue(ui[defaultLang], key) ?? key;
+  };
+}
+/**
+ * Get all supported language codes
+ */
+export function getLanguageCodes(): string[] {
+  return Object.keys(languages);
+}
+
+/**
+ * Create a regex pattern to match language prefixes in URLs
+ */
+export function createLanguagePathRegex(): RegExp {
+  const codes = getLanguageCodes().join('|');
+  return new RegExp(`^/(${codes})/`);
+}
+
+/**
+ * Replace the language code in a path with a new one
+ */
+export function replaceLanguageInPath(path: string, newLang: string): string {
+  const langRegex = createLanguagePathRegex();
+
+  if (langRegex.test(path)) {
+    return path.replace(langRegex, `/${newLang}/`);
+  } else {
+    return `/${newLang}${path}`;
+  }
+}
diff --git a/src/icons/bsky.svg b/src/icons/bsky.svg
new file mode 100644
index 0000000000..470288aa8c
--- /dev/null
+++ b/src/icons/bsky.svg
@@ -0,0 +1,3 @@
+<svg width="12" height="11" viewBox="0 0 12 11" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M2.51447 0.697231C3.84439 1.70978 5.27487 3.76281 5.80007 4.86458C6.32531 3.76289 7.75571 1.70976 9.08567 0.697231C10.0453 -0.0333841 11.6001 -0.598692 11.6001 1.20015C11.6001 1.5594 11.397 4.21806 11.2778 4.64968C10.8638 6.1503 9.35497 6.53304 8.01285 6.30139C10.3588 6.70632 10.9556 8.04759 9.66679 9.38887C7.21899 11.9362 6.14859 8.74973 5.87419 7.93324C5.82391 7.78356 5.80038 7.71353 5.80003 7.77307C5.79969 7.71353 5.77616 7.78356 5.72588 7.93324C5.4516 8.74973 4.38122 11.9363 1.93328 9.38887C0.6444 8.04759 1.24118 6.70624 3.58722 6.30139C2.24506 6.53304 0.73622 6.1503 0.32222 4.64968C0.203096 4.21802 0 1.55936 0 1.20015C0 -0.598692 1.55484 -0.0333841 2.5144 0.697231H2.51447Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/github.svg b/src/icons/github.svg
new file mode 100644
index 0000000000..e5c5a6896e
--- /dev/null
+++ b/src/icons/github.svg
@@ -0,0 +1,3 @@
+<svg width="12" height="12" viewBox="0 0 12 12" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M6.00496 0C2.68437 0 0 2.70416 0 6.04958C0 8.72375 1.71997 10.9874 4.10603 11.7886C4.40435 11.8488 4.51362 11.6584 4.51362 11.4982C4.51362 11.358 4.50378 10.8773 4.50378 10.3764C2.83335 10.737 2.4855 9.65522 2.4855 9.65522C2.21705 8.9541 1.81929 8.7739 1.81929 8.7739C1.27255 8.40331 1.85911 8.40331 1.85911 8.40331C2.46558 8.44338 2.78381 9.02429 2.78381 9.02429C3.32059 9.94567 4.18555 9.68533 4.53353 9.52505C4.58319 9.13442 4.74237 8.864 4.91138 8.7138C3.57908 8.57355 2.17734 8.05275 2.17734 5.72902C2.17734 5.06797 2.4158 4.52714 2.79365 4.10652C2.73403 3.95631 2.5252 3.33522 2.85338 2.50393C2.85338 2.50393 3.36042 2.34365 4.50366 3.12491C4.99313 2.99248 5.4979 2.92512 6.00496 2.92455C6.512 2.92455 7.02886 2.99474 7.50614 3.12491C8.64951 2.34365 9.15655 2.50393 9.15655 2.50393C9.48473 3.33522 9.27577 3.95631 9.21616 4.10652C9.60396 4.52714 9.83259 5.06797 9.83259 5.72902C9.83259 8.05275 8.43085 8.56347 7.0886 8.7138C7.30739 8.90407 7.49619 9.26459 7.49619 9.83554C7.49619 10.6468 7.48635 11.2979 7.48635 11.4981C7.48635 11.6584 7.59575 11.8488 7.89395 11.7887C10.28 10.9873 12 8.72375 12 6.04958C12.0098 2.70416 9.3156 0 6.00496 0Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/linkedin.svg b/src/icons/linkedin.svg
new file mode 100644
index 0000000000..bdffa543c8
--- /dev/null
+++ b/src/icons/linkedin.svg
@@ -0,0 +1,3 @@
+<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M0 2a2 2 0 0 1 2-2h12a2 2 0 0 1 2 2v12a2 2 0 0 1-2 2H2a2 2 0 0 1-2-2V2zm4.88 1.79a1.1 1.1 0 1 1 0 2.2 1.1 1.1 0 0 1 0-2.2zM3.92 6.39H5.8V12H3.92V6.39zm5.04 0H7.08V12h1.88V9.17c0-.79.15-1.55 1.13-1.55 1 0 .97.93.97 1.6V12H13V8.86c0-1.62-.35-2.87-2.24-2.87-.91 0-1.52.5-1.77.97h-.03v-.57z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/logo-dark.svg b/src/icons/logo-dark.svg
new file mode 100644
index 0000000000..0dc200a93c
--- /dev/null
+++ b/src/icons/logo-dark.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="797" height="583" fill="none"><mask id="a" width="797" height="583" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:luminance"><path fill="#fff" d="M796.444 0H0v582.187h796.444V0Z"/></mask><g fill="#0A0A0A" mask="url(#a)"><path d="M406.935 445.941h37.984l231.478-309.444h-38.545L406.935 445.941Z"/><path d="M731.398 493.765v.106l-143.83-189.349-18.503 24.553 161.718 221.741H31.37V31.37h315.442l166.741 222.304 19.066-25.628L387.459 31.37h.102L363.725 0H0v582.188h796.444l-65.046-88.423Z"/><path d="M362.291 181.759c-11.022-16.197-25.27-29.267-42.903-39.262-17.581-9.996-38.804-14.968-63.562-14.968-24.755 0-45.465 4.714-63.252 14.095-17.786 9.381-32.291 21.785-43.465 37.162-11.174 15.377-19.478 32.908-24.911 52.489a225.233 225.233 0 0 0-8.099 59.972c0 21.988 2.716 42.903 8.099 62.686 5.382 19.786 13.685 37.163 24.911 52.181 11.174 15.019 25.679 26.809 43.465 35.368 17.787 8.613 38.855 12.917 63.252 12.917 39.163 0 69.456-9.583 90.883-28.806 21.373-19.172 36.085-46.39 44.08-81.55h-37.777c-5.996 23.987-16.813 43.158-32.395 57.56-15.582 14.404-37.163 21.581-64.791 21.581-17.991 0-33.368-3.795-46.182-11.381s-23.373-17.169-31.778-28.806c-8.408-11.585-14.508-24.706-18.301-39.264-3.383-12.917-5.228-25.424-5.638-37.573a294.756 294.756 0 0 0-.461-9.48c-.667-9.381-.564-18.557.461-27.526 1.589-13.841 4.87-27.372 9.842-40.596 4.971-13.38 11.687-25.167 20.093-35.368 8.405-10.2 18.605-18.403 30.6-24.604 11.995-6.204 25.782-9.279 41.364-9.279 15.585 0 28.809 3.075 40.804 9.279 11.992 6.201 22.192 14.404 30.6 24.604 8.406 10.201 14.865 21.886 19.479 35.061 4.611 13.173 7.071 27.011 7.484 41.364H186.681l.153 31.781H391.97c.819-21.581-1.181-42.903-5.999-63.869-4.819-20.964-12.712-39.569-23.68-55.768Z"/></g></svg>
\ No newline at end of file
diff --git a/src/icons/logo-express-black.svg b/src/icons/logo-express-black.svg
new file mode 100644
index 0000000000..268c1b5495
--- /dev/null
+++ b/src/icons/logo-express-black.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="599" height="159" fill="none" viewBox="0 0 599 159"><g fill="#000" clip-path="url(#a)"><path d="M110.82 121.236h12.709l62.932-84.1271h-12.876z"/><path d="M198.851 134.239v.028l-36.413-48.5091-6.703 8.7374 40.161 55.2537H8.53622V8.52841H91.5071L137.159 69.2306l6.661-8.6817-38.475-52.02049h.028L98.8928 0H.00781v158.277H216.535zm39.778-10.716c6.41 0 11.984-1.171 16.708-3.512 4.725-2.341 8.668-5.546 11.818-9.615 3.149-4.069 5.49-8.807 7.009-14.1865 1.519-5.379 2.286-11.0646 2.286-17.0429 0-5.9782-.767-11.6638-2.286-17.0429-1.519-5.379-3.86-10.1031-7.009-14.1861-3.15-4.0691-7.093-7.3021-11.818-9.699-4.724-2.3829-10.298-3.5814-16.708-3.5814-6.842 0-12.96 1.6026-18.339 4.8077s-9.267 7.748-11.664 13.6148h-.32V37.0959h-9.462v76.9091l10.27 13.963V105.24h.321c1.087 3.037 2.633 5.713 4.64 7.985 2.007 2.285 4.32 4.18 6.926 5.713 2.606 1.519 5.435 2.662 8.473 3.428 3.037.753 6.089 1.143 9.127 1.143zm-22.91-19.886c-2.341-3.372-4.027-7.2045-5.058-11.4966s-1.547-8.612-1.547-12.9599c0-4.7798.46-9.3505 1.38-13.6984.919-4.3478 2.522-8.1521 4.807-11.413 2.286-3.2608 5.324-5.8668 9.128-7.8316 3.804-1.951 8.528-2.9404 14.186-2.9404 4.891 0 9.072 1.0591 12.556 3.1773 3.484 2.1181 6.326 4.8634 8.556 8.2357 2.23 3.3724 3.86 7.2046 4.891 11.4967 1.032 4.292 1.547 8.612 1.547 12.9598s-.515 8.6678-1.547 12.9598c-1.031 4.2921-2.661 8.1246-4.891 11.4966s-5.086 6.118-8.556 8.236c-3.484 2.118-7.665 3.177-12.556 3.177-5.435 0-10.033-1.059-13.782-3.177s-6.8-4.864-9.128-8.236z"/><path d="m113.754 0 6.48 8.52841h470.219V149.749H225.125l6.271 8.528h367.585V0zM98.4977 49.414c-2.9961-4.4036-6.8701-7.9571-11.6638-10.6745-4.7799-2.7174-10.5491-4.0691-17.2798-4.0691-6.7308 0-12.3607 1.2821-17.1962 3.8322-4.8356 2.5502-8.7793 5.9225-11.8172 10.1031-3.0378 4.1806-5.2954 8.9465-6.7725 14.2698-1.4632 5.3233-2.2018 10.758-2.2018 16.3043 0 5.9782.7386 11.6639 2.2018 17.0429 1.4632 5.3793 3.7207 10.1033 6.7725 14.1863 3.0379 4.083 6.9816 7.288 11.8172 9.615 4.8355 2.341 10.563 3.512 17.1962 3.512 10.6465 0 18.8823-2.606 24.7073-7.832 5.8106-5.212 9.8106-12.611 11.9846-22.1708H95.9754c-1.6304 6.5218-4.5708 11.7338-8.8071 15.6498-4.2363 3.915-10.1031 5.866-17.6142 5.866-4.8913 0-9.0719-1.031-12.5557-3.093-3.4839-2.063-6.3545-4.669-8.6399-7.832-2.2854-3.149-3.9437-6.7168-4.9749-10.6744-.9198-3.5117-1.4214-6.912-1.5329-10.2146-.0279-.864-.0697-1.7141-.1254-2.5781-.1812-2.5501-.1533-5.0445.1254-7.4832.432-3.7626 1.3238-7.4415 2.6755-11.0368 1.3518-3.6371 3.1773-6.8422 5.4627-9.6154 2.2854-2.7731 5.0585-5.0027 8.3194-6.6889 3.2608-1.6862 7.0094-2.5223 11.2458-2.5223 4.2363 0 7.8316.8361 11.0925 2.5223 3.2608 1.6862 6.034 3.9158 8.3194 6.6889 2.2854 2.7732 4.0412 5.9504 5.2954 9.5318 1.2541 3.5814 1.923 7.3439 2.0345 11.2458H50.7553l.0418 8.6399h55.7689c.223-5.8668-.32-11.6639-1.63-17.3634-1.31-5.6996-3.456-10.7581-6.4383-15.1616"/><path d="M292.434 37.1093v84.1277h10.27V76.393c0-4.4593.752-8.5563 2.285-12.3049q2.2785-5.6229 6.438-9.699c2.774-2.7174 6.062-4.8077 9.867-6.2709 3.804-1.4632 8.04-2.0903 12.723-1.8813V35.9666c-7.609-.3205-14.159 1.3657-19.649 5.0585-5.491 3.6929-9.532 8.9604-12.152 15.8166h-.32V37.1093zm117.56 27.4663c-1.31-5.6996-3.456-10.7581-6.438-15.1616-2.996-4.4036-6.87-7.9571-11.664-10.6745-4.779-2.7174-10.549-4.0691-17.279-4.0691-6.731 0-12.361 1.2821-17.196 3.8322-4.836 2.5502-8.78 5.9225-11.818 10.1031s-5.295 8.9465-6.772 14.2698c-1.463 5.3233-2.202 10.758-2.202 16.3043 0 5.9782.739 11.6639 2.202 17.0429 1.463 5.3793 3.721 10.1033 6.772 14.1863 3.038 4.083 6.982 7.288 11.818 9.615 4.835 2.341 10.562 3.512 17.196 3.512 10.646 0 18.882-2.606 24.707-7.832 5.811-5.212 9.81-12.611 11.984-22.1708h-10.27c-1.63 6.5218-4.571 11.7338-8.807 15.6498-4.236 3.915-10.103 5.866-17.614 5.866-4.892 0-9.072-1.031-12.556-3.093-3.484-2.063-6.355-4.669-8.64-7.832-2.285-3.149-3.944-6.7168-4.975-10.6744-1.031-3.9716-1.547-7.8038-1.547-11.4967h64.73c.223-5.8667-.321-11.6638-1.631-17.3634zm-63.099 8.7235c.432-3.8043 1.324-7.5251 2.69-11.1622 1.352-3.6371 3.177-6.8422 5.462-9.6154 2.286-2.7731 5.059-5.0027 8.32-6.6889s7.009-2.5223 11.246-2.5223c4.236 0 7.831.8361 11.092 2.5223s6.034 3.9158 8.32 6.6889c2.285 2.7732 4.041 5.9504 5.295 9.5318s1.923 7.3439 2.035 11.2458zm124.076 38.1559c-2.286 1.31-4.752 2.23-7.414 2.773-2.662.544-5.24.808-7.748.808-6.842 0-12.584-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.119-9.6154-1.407-2.7173-3.233-5.0027-5.462-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.699-3.0936c-1.741-.432-3.637-1.0034-5.713-1.7141-2.062-.7107-3.972-1.6025-5.7-2.6895-1.741-1.0869-3.177-2.4108-4.319-3.9994-1.143-1.5747-1.715-3.5117-1.715-5.7832 0-2.7173.6-5.0027 1.798-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.341-.4877 4.641-.7386 6.926-.7386 2.94 0 5.714.3484 8.32 1.0591 2.605.7107 4.919 1.8256 6.925 3.3445 2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.853 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.616-5.0585-3.637-1.087-7.58-1.6304-11.817-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.187 4.083-3.037 1.8534-5.518 4.2921-7.413 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.152 4.2364c1.032 1.6861 1.547 3.7764 1.547 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975zm78.414 0c-2.286 1.31-4.752 2.23-7.414 2.773-2.661.544-5.24.808-7.748.808-6.842 0-12.583-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.118-9.6154-1.408-2.7173-3.233-5.0027-5.463-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.698-3.0936c-1.742-.432-3.638-1.0034-5.714-1.7141-2.062-.7107-3.971-1.6025-5.699-2.6895-1.742-1.0869-3.178-2.4108-4.32-3.9994-1.143-1.5747-1.714-3.5117-1.714-5.7832 0-2.7173.599-5.0027 1.797-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.342-.4877 4.641-.7386 6.926-.7386 2.941 0 5.714.3484 8.32 1.0591s4.919 1.8256 6.925 3.3445c2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.854 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.615-5.0585-3.638-1.087-7.581-1.6304-11.818-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.186 4.083-3.038 1.8534-5.519 4.2921-7.414 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.153 4.2364c1.031 1.6861 1.546 3.7764 1.546 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975z"/></g><defs><clipPath id="a"><path fill="#000" d="M0 0h598.982v158.277H0z"/></clipPath></defs></svg>
diff --git a/src/icons/logo-express-white.svg b/src/icons/logo-express-white.svg
new file mode 100644
index 0000000000..f35c4beccc
--- /dev/null
+++ b/src/icons/logo-express-white.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="599" height="159" fill="none" viewBox="0 0 599 159"><g fill="#fff" clip-path="url(#a)"><path d="M110.82 121.236h12.709l62.932-84.1271h-12.876z"/><path d="M198.851 134.239v.028l-36.413-48.5091-6.703 8.7374 40.161 55.2537H8.53622V8.52841H91.5071L137.159 69.2306l6.661-8.6817-38.475-52.02049h.028L98.8928 0H.00781v158.277H216.535zM238.629 123.523c6.41 0 11.984-1.171 16.708-3.512 4.725-2.341 8.668-5.546 11.818-9.615 3.149-4.069 5.49-8.807 7.009-14.1865 1.519-5.379 2.286-11.0646 2.286-17.0429 0-5.9782-.767-11.6638-2.286-17.0429-1.519-5.379-3.86-10.1031-7.009-14.1861-3.15-4.0691-7.093-7.3021-11.818-9.699-4.724-2.3829-10.298-3.5814-16.708-3.5814-6.842 0-12.96 1.6026-18.339 4.8077s-9.267 7.748-11.664 13.6148h-.32V37.0959h-9.462v76.9091l10.27 13.963V105.24h.321c1.087 3.037 2.633 5.713 4.64 7.985 2.007 2.285 4.32 4.18 6.926 5.713 2.606 1.519 5.435 2.662 8.473 3.428 3.037.753 6.089 1.143 9.127 1.143zm-22.91-19.886c-2.341-3.372-4.027-7.2045-5.058-11.4966s-1.547-8.612-1.547-12.9599c0-4.7798.46-9.3505 1.38-13.6984.919-4.3478 2.522-8.1521 4.807-11.413 2.286-3.2608 5.324-5.8668 9.128-7.8316 3.804-1.951 8.528-2.9404 14.186-2.9404 4.891 0 9.072 1.0591 12.556 3.1773 3.484 2.1181 6.326 4.8634 8.556 8.2357 2.23 3.3724 3.86 7.2046 4.891 11.4967 1.032 4.292 1.547 8.612 1.547 12.9598s-.515 8.6678-1.547 12.9598c-1.031 4.2921-2.661 8.1246-4.891 11.4966s-5.086 6.118-8.556 8.236c-3.484 2.118-7.665 3.177-12.556 3.177-5.435 0-10.033-1.059-13.782-3.177s-6.8-4.864-9.128-8.236z"/><path d="m113.754 0 6.48 8.52841h470.219V149.749H225.125l6.271 8.528h367.585V0zM98.4977 49.414c-2.9961-4.4036-6.8701-7.9571-11.6638-10.6745-4.7799-2.7174-10.5491-4.0691-17.2798-4.0691-6.7308 0-12.3607 1.2821-17.1962 3.8322-4.8356 2.5502-8.7793 5.9225-11.8172 10.1031-3.0378 4.1806-5.2954 8.9465-6.7725 14.2698-1.4632 5.3233-2.2018 10.758-2.2018 16.3043 0 5.9782.7386 11.6639 2.2018 17.0429 1.4632 5.3793 3.7207 10.1033 6.7725 14.1863 3.0379 4.083 6.9816 7.288 11.8172 9.615 4.8355 2.341 10.563 3.512 17.1962 3.512 10.6465 0 18.8823-2.606 24.7073-7.832 5.8106-5.212 9.8106-12.611 11.9846-22.1708H95.9754c-1.6304 6.5218-4.5708 11.7338-8.8071 15.6498-4.2363 3.915-10.1031 5.866-17.6142 5.866-4.8913 0-9.0719-1.031-12.5557-3.093-3.4839-2.063-6.3545-4.669-8.6399-7.832-2.2854-3.149-3.9437-6.7168-4.9749-10.6744-.9198-3.5117-1.4214-6.912-1.5329-10.2146-.0279-.864-.0697-1.7141-.1254-2.5781-.1812-2.5501-.1533-5.0445.1254-7.4832.432-3.7626 1.3238-7.4415 2.6755-11.0368 1.3518-3.6371 3.1773-6.8422 5.4627-9.6154 2.2854-2.7731 5.0585-5.0027 8.3194-6.6889 3.2608-1.6862 7.0094-2.5223 11.2458-2.5223 4.2363 0 7.8316.8361 11.0925 2.5223 3.2608 1.6862 6.034 3.9158 8.3194 6.6889 2.2854 2.7732 4.0412 5.9504 5.2954 9.5318 1.2541 3.5814 1.923 7.3439 2.0345 11.2458H50.7553l.0418 8.6399h55.7689c.223-5.8668-.32-11.6639-1.63-17.3634-1.31-5.6996-3.456-10.7581-6.4383-15.1616"/><path d="M292.434 37.1093v84.1277h10.27V76.393c0-4.4593.752-8.5563 2.285-12.3049q2.2785-5.6229 6.438-9.699c2.774-2.7174 6.062-4.8077 9.867-6.2709 3.804-1.4632 8.04-2.0903 12.723-1.8813V35.9666c-7.609-.3205-14.159 1.3657-19.649 5.0585-5.491 3.6929-9.532 8.9604-12.152 15.8166h-.32V37.1093zM409.994 64.5756c-1.31-5.6996-3.456-10.7581-6.438-15.1616-2.996-4.4036-6.87-7.9571-11.664-10.6745-4.779-2.7174-10.549-4.0691-17.279-4.0691-6.731 0-12.361 1.2821-17.196 3.8322-4.836 2.5502-8.78 5.9225-11.818 10.1031s-5.295 8.9465-6.772 14.2698c-1.463 5.3233-2.202 10.758-2.202 16.3043 0 5.9782.739 11.6639 2.202 17.0429 1.463 5.3793 3.721 10.1033 6.772 14.1863 3.038 4.083 6.982 7.288 11.818 9.615 4.835 2.341 10.562 3.512 17.196 3.512 10.646 0 18.882-2.606 24.707-7.832 5.811-5.212 9.81-12.611 11.984-22.1708h-10.27c-1.63 6.5218-4.571 11.7338-8.807 15.6498-4.236 3.915-10.103 5.866-17.614 5.866-4.892 0-9.072-1.031-12.556-3.093-3.484-2.063-6.355-4.669-8.64-7.832-2.285-3.149-3.944-6.7168-4.975-10.6744-1.031-3.9716-1.547-7.8038-1.547-11.4967h64.73c.223-5.8667-.321-11.6638-1.631-17.3634zm-63.099 8.7235c.432-3.8043 1.324-7.5251 2.69-11.1622 1.352-3.6371 3.177-6.8422 5.462-9.6154 2.286-2.7731 5.059-5.0027 8.32-6.6889s7.009-2.5223 11.246-2.5223c4.236 0 7.831.8361 11.092 2.5223s6.034 3.9158 8.32 6.6889c2.285 2.7732 4.041 5.9504 5.295 9.5318s1.923 7.3439 2.035 11.2458zM470.971 111.455c-2.286 1.31-4.752 2.23-7.414 2.773-2.662.544-5.24.808-7.748.808-6.842 0-12.584-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.119-9.6154-1.407-2.7173-3.233-5.0027-5.462-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.699-3.0936c-1.741-.432-3.637-1.0034-5.713-1.7141-2.062-.7107-3.972-1.6025-5.7-2.6895-1.741-1.0869-3.177-2.4108-4.319-3.9994-1.143-1.5747-1.715-3.5117-1.715-5.7832 0-2.7173.6-5.0027 1.798-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.341-.4877 4.641-.7386 6.926-.7386 2.94 0 5.714.3484 8.32 1.0591 2.605.7107 4.919 1.8256 6.925 3.3445 2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.853 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.616-5.0585-3.637-1.087-7.58-1.6304-11.817-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.187 4.083-3.037 1.8534-5.518 4.2921-7.413 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.152 4.2364c1.032 1.6861 1.547 3.7764 1.547 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975zM549.385 111.455c-2.286 1.31-4.752 2.23-7.414 2.773-2.661.544-5.24.808-7.748.808-6.842 0-12.583-1.769-17.196-5.295-4.627-3.526-7.149-8.779-7.581-15.733h-10.27c.864 10.326 4.375 17.823 10.521 22.506 6.145 4.668 14.158 7.009 24.052 7.009 3.916 0 7.874-.432 11.901-1.31 4.013-.864 7.637-2.313 10.842-4.32s5.839-4.612 7.901-7.832c2.062-3.205 3.094-7.093 3.094-11.6634 0-3.6928-.711-6.898-2.118-9.6154-1.408-2.7173-3.233-5.0027-5.463-6.8422-2.23-1.8534-4.78-3.3445-7.665-4.4872-2.884-1.1427-5.783-1.923-8.723-2.369l-13.698-3.0936c-1.742-.432-3.638-1.0034-5.714-1.7141-2.062-.7107-3.971-1.6025-5.699-2.6895-1.742-1.0869-3.178-2.4108-4.32-3.9994-1.143-1.5747-1.714-3.5117-1.714-5.7832 0-2.7173.599-5.0027 1.797-6.8422 1.199-1.8534 2.773-3.3445 4.724-4.4872s4.097-1.9509 6.438-2.4526c2.342-.4877 4.641-.7386 6.926-.7386 2.941 0 5.714.3484 8.32 1.0591s4.919 1.8256 6.925 3.3445c2.007 1.519 3.61 3.456 4.808 5.7832 1.199 2.3411 1.854 5.0863 1.951 8.2357h10.27c-.223-4.5708-1.142-8.5284-2.773-11.9007-1.63-3.3724-3.832-6.2012-6.605-8.4727-2.773-2.2854-5.978-3.9716-9.615-5.0585-3.638-1.087-7.581-1.6304-11.818-1.6304-3.692 0-7.413.4319-11.162 1.3099-3.748.8779-7.149 2.2296-10.186 4.083-3.038 1.8534-5.519 4.2921-7.414 7.3439-1.909 3.0379-2.857 6.689-2.857 10.9253 0 3.5814.599 6.6054 1.798 9.044 1.198 2.4387 2.857 4.5151 4.975 6.2012 2.118 1.6862 4.584 3.0937 7.413 4.2364s5.923 2.146 9.295 3.01l13.211 2.9404c2.285.5434 4.543 1.1984 6.772 1.9509 2.23.7664 4.209 1.714 5.951 2.8567s3.121 2.5502 4.153 4.2364c1.031 1.6861 1.546 3.7764 1.546 6.2709 0 2.9404-.738 5.4064-2.201 7.4134-1.464 2.007-3.345 3.665-5.63 4.975z"/></g><defs><clipPath id="a"><path fill="#fff" d="M0 0h598.982v158.277H0z"/></clipPath></defs></svg>
diff --git a/src/icons/logo-light.svg b/src/icons/logo-light.svg
new file mode 100644
index 0000000000..1ba7920fd9
--- /dev/null
+++ b/src/icons/logo-light.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="797" height="583" fill="none"><mask id="a" width="797" height="583" x="0" y="0" maskUnits="userSpaceOnUse" style="mask-type:luminance"><path fill="#fff" d="M796.444 0H0v582.187h796.444V0Z"/></mask><g fill="#fff" mask="url(#a)"><path d="M406.935 445.941h37.984l231.478-309.444h-38.545L406.935 445.941Z"/><path d="M731.398 493.765v.106l-143.83-189.349-18.503 24.553 161.718 221.741H31.37V31.37h315.442l166.741 222.304 19.066-25.628L387.459 31.37h.102L363.725 0H0v582.188h796.444l-65.046-88.423Z"/><path d="M362.291 181.759c-11.022-16.197-25.27-29.267-42.903-39.262-17.581-9.996-38.804-14.968-63.562-14.968-24.755 0-45.465 4.714-63.252 14.095-17.786 9.381-32.291 21.785-43.465 37.162-11.174 15.377-19.478 32.908-24.911 52.489a225.233 225.233 0 0 0-8.099 59.972c0 21.988 2.716 42.903 8.099 62.686 5.382 19.786 13.685 37.163 24.911 52.181 11.174 15.019 25.679 26.809 43.465 35.368 17.787 8.613 38.855 12.917 63.252 12.917 39.163 0 69.456-9.583 90.883-28.806 21.373-19.172 36.085-46.39 44.08-81.55h-37.777c-5.996 23.987-16.813 43.159-32.395 57.56-15.582 14.404-37.163 21.581-64.791 21.581-17.991 0-33.368-3.795-46.182-11.381s-23.373-17.169-31.778-28.806c-8.408-11.585-14.508-24.706-18.301-39.264-3.383-12.917-5.228-25.424-5.638-37.573a294.756 294.756 0 0 0-.461-9.48c-.667-9.381-.564-18.557.461-27.526 1.589-13.841 4.87-27.372 9.842-40.596 4.971-13.38 11.687-25.167 20.093-35.368 8.405-10.2 18.605-18.403 30.6-24.604 11.995-6.204 25.782-9.279 41.364-9.279 15.585 0 28.809 3.075 40.804 9.279 11.992 6.201 22.192 14.404 30.6 24.604 8.406 10.201 14.865 21.886 19.479 35.061 4.611 13.173 7.071 27.011 7.484 41.364H186.681l.153 31.781H391.97c.819-21.581-1.181-42.903-5.999-63.869-4.819-20.964-12.712-39.569-23.68-55.768Z"/></g></svg>
\ No newline at end of file
diff --git a/src/icons/open-collective.svg b/src/icons/open-collective.svg
new file mode 100644
index 0000000000..250d734a1f
--- /dev/null
+++ b/src/icons/open-collective.svg
@@ -0,0 +1,4 @@
+<svg width="12" height="12" viewBox="0 0 12 12" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M9.81465 5.98423C9.81465 6.73985 9.59527 7.46454 9.21877 8.06304L10.7555 9.60616C11.5081 8.59835 11.9786 7.33854 11.9786 5.98404C11.9786 4.62954 11.508 3.36991 10.7555 2.36191L9.21877 3.90504C9.59509 4.50354 9.81465 5.19673 9.81465 5.98423Z" fill="currentColor"/>
+<path fill-rule="evenodd" clip-rule="evenodd" d="M5.99006 9.82687C3.88875 9.82687 2.16394 8.09437 2.16394 5.98444C2.16394 3.8745 3.88894 2.142 5.99006 2.142C6.77419 2.142 7.46381 2.3625 8.06006 2.772L9.59681 1.22887C8.59312 0.4725 7.33875 0 5.99006 0C2.69681 0 0 2.67712 0 6.01575C0 9.35437 2.69681 12 5.99006 12C7.37006 12 8.62444 11.5275 9.62812 10.7719L8.09137 9.22875C7.4955 9.60675 6.77419 9.82687 5.99006 9.82687Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/orama-logo-dark.svg b/src/icons/orama-logo-dark.svg
new file mode 100644
index 0000000000..1cb8a4d8a8
--- /dev/null
+++ b/src/icons/orama-logo-dark.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="4868" height="1816" fill="none" viewBox="0 0 4868 1816"><path fill="#efedf0" d="M4188.21 1128.75c73.6 0 142.18-30.11 153.05-76.94 3.35 30.11 20.07 52.69 44.33 64.39 21.74 10.88 48.51 12.55 74.43 2.51v-75.27c-10.87 2.51-22.58 3.35-31.78-4.18s-15.89-24.25-15.89-55.196V836.032c0-91.161-68.58-148.032-188.17-148.032-103.71 0-182.33 42.653-192.36 107.051l80.29 23.418c6.69-32.617 45.99-55.199 107.05-55.199 58.54 0 104.54 19.236 104.54 51.017 0 30.108-41.82 44.326-145.52 51.853-98.69 7.527-158.91 55.198-158.91 132.141 0 76.109 59.38 130.469 168.94 130.469m0-74.43c-49.34 0-79.45-20.91-79.45-55.202 0-32.618 28.44-55.199 74.43-58.544 77.78-5.018 125.46-14.218 141.35-32.617 0 88.652-56.88 146.363-136.33 146.363M3766.14 690.79c-64.86 0-123.48 30.584-152.39 77.637-22.67-49.405-74.25-76.853-129.74-77.637-55.48 0-102.37 28.232-127.38 72.932v-61.169h-84.41v415.327h85.97V890.764c0-72.147 43.77-119.2 106.29-119.2 59.39 0 96.9 43.916 96.9 116.848v229.468h85.97V889.196c0-71.363 42.99-117.632 105.51-117.632 58.61 0 96.12 40.779 96.12 115.279v231.037h85.97V872.727c0-55.679-15.63-100.379-46.89-132.532-30.48-32.937-71.12-49.405-121.92-49.405M1828.97 1128.75c133.82 0 224.14-90.32 224.14-223.302 0-132.142-88.65-216.612-224.14-216.612-135.48 0-224.97 85.307-224.97 216.612 0 132.982 92 223.302 224.97 223.302m0-80.29c-80.28 0-135.48-59.378-135.48-143.012 0-82.798 53.52-136.323 135.48-136.323 82.8 0 134.66 53.525 134.66 136.323 0 84.47-54.37 143.012-134.66 143.012M2448.54 688c-69.41 0-128.79 28.435-165.59 76.107v-70.253h-127.12v72.762h125.45c-25.09 33.453-39.31 76.106-39.31 125.45v153.054h-83.63v72.76h282.68v-72.76h-108.73V889.557c0-66.907 51.02-117.087 116.25-117.087 52.69 0 86.98 34.29 97.02 76.943l81.96-29.272C2609.96 740.689 2543.05 688 2448.54 688M2892.85 1128.75c73.6 0 142.18-30.11 153.05-76.94 3.34 30.11 20.07 52.69 44.32 64.39 21.75 10.88 48.51 12.55 74.44 2.51v-75.27c-10.87 2.51-22.58 3.35-31.78-4.18s-15.89-24.25-15.89-55.196V836.032c0-91.161-68.58-148.032-188.18-148.032-103.7 0-182.32 42.653-192.36 107.051l80.29 23.418c6.69-32.617 46-55.199 107.05-55.199 58.55 0 104.55 19.236 104.55 51.017 0 30.108-41.82 44.326-145.53 51.853-98.69 7.527-158.9 55.198-158.9 132.141 0 76.109 59.38 130.469 168.94 130.469m0-74.43c-49.35 0-79.45-20.91-79.45-55.202 0-32.618 28.43-55.199 74.43-58.544 77.78-5.018 125.45-14.218 141.34-32.617 0 88.652-56.87 146.363-136.32 146.363"/><mask id="dark-a" width="992" height="1000" x="408" y="408" maskUnits="userSpaceOnUse" style="mask-type:luminance"><path fill="#fff" d="M1400 408H408v1000h992z"/></mask><g mask="url(#dark-a)"><path fill="url(#dark-b)" fill-rule="evenodd" d="M912.724 663.395c36.48-32.397 86.93-48.777 135.686-46.526 27.84 1.285 52.82 8.423 73.38 20.252 17.77 9.529 35.6 27.016 50.29 47.475 25.88 22.593 64.78 25.376 93.97 4.549 34.12-24.35 42.05-71.752 17.7-105.875-55.19-77.341-142.81-114.099-228.34-118.048-85.424-3.943-175.886 24.162-244.4 85.476-.229.205-.457.411-.683.619-135.66 121.929-147.218 330.869-25.428 466.963 27.956 31.23 75.942 33.9 107.18 5.94 31.238-27.956 33.899-75.942 5.943-107.18-66.006-73.756-59.664-187.139 14.134-253.132.191-.17.38-.341.568-.513" clip-rule="evenodd"/><mask id="dark-d" width="598" height="580" x="700" y="464" maskUnits="userSpaceOnUse" style="mask-type:alpha"><path fill="url(#dark-c)" fill-rule="evenodd" d="M912.737 663.384c36.478-32.39 86.923-48.767 135.673-46.516 27.84 1.285 52.82 8.423 73.38 20.252 17.77 9.529 35.6 27.016 50.29 47.475 25.88 22.593 64.78 25.376 93.97 4.549 34.12-24.35 42.05-71.752 17.7-105.875-55.19-77.34-142.81-114.099-228.34-118.047-85.423-3.944-175.886 24.161-244.399 85.475-.235.21-.468.421-.699.634-135.646 121.931-147.198 330.86-25.413 466.949 27.956 31.23 75.942 33.9 107.18 5.94 31.238-27.956 33.899-75.942 5.943-107.18-66.006-73.756-59.664-187.139 14.134-253.132.195-.174.388-.349.581-.524" clip-rule="evenodd"/></mask><g mask="url(#dark-d)"><path fill="url(#dark-e)" d="m815.442 488.439-257.863 252.15 471.211 73.248 189.64-148.885v-99.867z" style="mix-blend-mode:multiply"/></g><path fill="url(#dark-f)" fill-rule="evenodd" d="M681.479 543.438c27.943 31.249 25.263 79.234-5.986 107.177-142.846 127.734-155.084 347.036-27.343 489.895 27.943 31.25 25.263 79.23-5.986 107.17-31.249 27.95-79.234 25.27-107.177-5.98-183.62-205.35-166.038-520.62 39.315-704.248 31.249-27.943 79.234-25.263 107.177 5.986" clip-rule="evenodd"/><path fill="url(#dark-g)" fill-rule="evenodd" d="M540.973 1134.52c31.249-27.94 79.234-25.26 107.177 5.99 127.734 142.84 347.037 155.08 489.89 27.34 31.25-27.94 79.24-25.26 107.18 5.99s25.26 79.23-5.99 107.17c-205.34 183.62-520.615 166.04-704.243-39.31-27.943-31.25-25.263-79.24 5.986-107.18" clip-rule="evenodd"/><path fill="url(#dark-h)" fill-rule="evenodd" d="M1225.41 624.307c36.22-21.108 82.69-8.858 103.8 27.36 115.13 197.541 92.22 466.423-89.9 629.333-31.25 27.94-79.23 25.27-107.18-5.98-27.95-31.24-25.27-79.23 5.97-107.17 122.51-109.58 142.9-297.418 59.95-439.744-21.1-36.218-8.86-82.691 27.36-103.799" clip-rule="evenodd"/><mask id="dark-j" width="288" height="688" x="1112" y="613" maskUnits="userSpaceOnUse" style="mask-type:alpha"><path fill="url(#dark-i)" fill-rule="evenodd" d="M1225.41 624.307c36.22-21.108 82.69-8.859 103.8 27.36 115.13 197.54 92.22 466.423-89.9 629.333-31.25 27.94-79.23 25.27-107.18-5.98-27.95-31.24-25.27-79.23 5.97-107.18 122.51-109.57 142.9-297.409 59.95-439.734-21.1-36.219-8.86-82.691 27.36-103.799" clip-rule="evenodd"/></mask><g mask="url(#dark-j)"><path fill="url(#dark-k)" d="M1195.2 935.842 941.304 1200.63l372.166 105.91 159.57-383.87-210.26-457.256-18.77 381.987z" style="mix-blend-mode:multiply"/></g><path fill="#f97cbf" fill-rule="evenodd" d="m1240.67 536.021 22.2 24.558 22.25 24.558c-.55-.824-1.13-1.677-1.75-2.554l2.04 2.198c-.92-1.217-2.62-3.339-4.87-6.067-10.16-13.475-26.34-31.02-39.87-42.693" clip-rule="evenodd"/><path fill="url(#dark-l)" fill-rule="evenodd" d="M790.933 911.08c31.249-27.943 79.234-25.264 107.178 5.985 65.992 73.799 179.379 80.141 253.129 14.134 31.24-27.955 79.23-25.294 107.18 5.944 27.96 31.238 25.3 79.227-5.94 107.177-136.3 121.98-345.684 110.2-467.532-26.06-27.943-31.251-25.263-79.236 5.985-107.18" clip-rule="evenodd"/><path fill="url(#dark-m)" fill-rule="evenodd" d="M1278.53 576.74c-27.96-31.238-75.94-33.899-107.18-5.944-27.05 24.208-32.67 63.434-15.54 93.8 9.42 10.181 18.19 21.9 25.68 34.224 48.23 72.965 36.93 172.243-30.22 232.288-31.25 27.943-33.93 75.932-5.98 107.182 27.94 31.24 75.92 33.92 107.17 5.98 136.26-121.847 148.05-331.227 26.07-467.53" clip-rule="evenodd"/><path fill="url(#dark-n)" fill-rule="evenodd" d="M1149.47 658.088c-107.08-125.222-331.814-134.518-473.973-7.398-31.249 27.943-79.234 25.263-107.177-5.986-27.944-31.249-25.264-79.234 5.986-107.177 200.816-179.572 543.984-179.576 708.854 44.992 24.8 33.792 17.52 81.296-16.27 106.104-29.15 21.396-68.49 18.921-94.68-3.842-6.98-9.747-14.67-18.824-22.74-26.693" clip-rule="evenodd"/></g><defs><linearGradient id="dark-b" x1="820.116" x2="871.279" y1="910.363" y2="581.461" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f8b580"/></linearGradient><linearGradient id="dark-c" x1="820.116" x2="871.279" y1="910.363" y2="581.46" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f8b580"/></linearGradient><linearGradient id="dark-e" x1="1049.43" x2="754.751" y1="426.414" y2="766.59" gradientUnits="userSpaceOnUse"><stop stop-color="#895200"/><stop offset=".83333" stop-color="#e28800" stop-opacity="0"/></linearGradient><linearGradient id="dark-f" x1="554.401" x2="590.876" y1="594.033" y2="1127.83" gradientUnits="userSpaceOnUse"><stop stop-color="#ed51f2"/><stop offset="1" stop-color="#b771f2"/></linearGradient><linearGradient id="dark-g" x1="553.339" x2="1119.35" y1="1158.87" y2="1192.96" gradientUnits="userSpaceOnUse"><stop stop-color="#b971f3"/><stop offset="1" stop-color="#8f6fde"/></linearGradient><linearGradient id="dark-h" x1="1258.65" x2="1170.99" y1="734.396" y2="1253.17" gradientUnits="userSpaceOnUse"><stop stop-color="#6a4bb2"/><stop offset="1" stop-color="#9170e0"/></linearGradient><linearGradient id="dark-i" x1="1258.65" x2="1156.33" y1="687.436" y2="1246.57" gradientUnits="userSpaceOnUse"><stop stop-color="#6a4bb2"/><stop offset="1" stop-color="#9170e0"/></linearGradient><linearGradient id="dark-k" x1="1133.25" x2="1265.16" y1="901.97" y2="1180.22" gradientUnits="userSpaceOnUse"><stop stop-color="#542da7"/><stop offset=".83333" stop-color="#5f2eaf" stop-opacity="0"/></linearGradient><linearGradient id="dark-l" x1="860.316" x2="1119.78" y1="914.015" y2="987.104" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f9a38f"/></linearGradient><linearGradient id="dark-m" x1="1233.5" x2="1244.41" y1="711.379" y2="987.688" gradientUnits="userSpaceOnUse"><stop stop-color="#fa80b7"/><stop offset="1" stop-color="#f8a48d"/></linearGradient><linearGradient id="dark-n" x1="644.701" x2="1203.84" y1="574.152" y2="603.388" gradientUnits="userSpaceOnUse"><stop stop-color="#e755f3"/><stop offset="1" stop-color="#f97fb6"/></linearGradient></defs></svg>
diff --git a/src/icons/orama-logo-light.svg b/src/icons/orama-logo-light.svg
new file mode 100644
index 0000000000..29c2d24939
--- /dev/null
+++ b/src/icons/orama-logo-light.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="4096" height="1528" fill="none" viewBox="0 0 4096 1528"><g clip-path="url(#light-a)"><path fill="#302f33" d="M3542.82 950.183c62.1 0 119.97-25.406 129.14-64.926 2.83 25.406 16.94 44.46 37.41 54.34 18.34 9.175 40.93 10.586 62.81 2.117V878.2c-9.18 2.117-19.06 2.823-26.82-3.529-7.77-6.351-13.41-20.466-13.41-46.577V703.182c0-76.924-57.87-124.912-158.79-124.912-87.51 0-153.84 35.991-162.31 90.331l67.75 19.761c5.64-27.523 38.81-46.578 90.33-46.578 49.4 0 88.21 16.232 88.21 43.049 0 25.406-35.28 37.403-122.79 43.754-83.28 6.352-134.09 46.578-134.09 111.504 0 64.22 50.11 110.092 142.56 110.092m0-62.809c-41.64 0-67.05-17.643-67.05-46.577 0-27.523 24-46.578 62.81-49.401 65.63-4.234 105.86-11.997 119.27-27.523 0 74.807-47.99 123.501-115.03 123.501M3186.67 580.624c-54.74 0-104.2 25.807-128.6 65.511-19.12-41.689-62.65-64.85-109.47-65.511-46.82 0-86.39 23.822-107.49 61.541V590.55h-71.22v350.461h72.54V749.366c0-60.88 36.93-100.584 89.68-100.584 50.12 0 81.78 37.057 81.78 98.599v193.63h72.54V748.043c0-60.218 36.27-99.261 89.02-99.261 49.46 0 81.12 34.41 81.12 97.275v194.954h72.54V734.146c0-46.983-13.19-84.702-39.57-111.833-25.72-27.793-60.01-41.689-102.87-41.689M1552.05 950.183c112.91 0 189.13-76.218 189.13-188.427 0-111.503-74.81-182.781-189.13-182.781-114.33 0-189.84 71.983-189.84 182.781 0 112.209 77.63 188.427 189.84 188.427m0-67.749c-67.75 0-114.33-50.106-114.33-120.678 0-69.866 45.17-115.032 114.33-115.032 69.86 0 113.62 45.166 113.62 115.032 0 71.278-45.87 120.678-113.62 120.678M2074.85 578.27c-58.57 0-108.68 23.994-139.73 64.22v-59.28h-107.27v61.397h105.86c-21.17 28.229-33.17 64.22-33.17 105.858v129.146h-70.57v61.398h238.53v-61.398h-91.74V748.348c0-56.458 43.04-98.801 98.09-98.801 44.46 0 73.4 28.935 81.86 64.926l69.16-24.7c-14.82-67.043-71.27-111.503-151.02-111.503M2449.76 950.183c62.11 0 119.98-25.406 129.15-64.926 2.82 25.406 16.94 44.46 37.4 54.34 18.35 9.175 40.93 10.586 62.81 2.117V878.2c-9.17 2.117-19.05 2.823-26.82-3.529-7.76-6.351-13.4-20.466-13.4-46.577V703.182c0-76.924-57.87-124.912-158.79-124.912-87.51 0-153.85 35.991-162.32 90.331l67.75 19.761c5.65-27.523 38.82-46.578 90.34-46.578 49.4 0 88.21 16.232 88.21 43.049 0 25.406-35.29 37.403-122.8 43.754-83.27 6.352-134.08 46.578-134.08 111.504 0 64.22 50.1 110.092 142.55 110.092m0-62.809c-41.63 0-67.04-17.643-67.04-46.577 0-27.523 23.99-46.578 62.81-49.401 65.63-4.234 105.86-11.997 119.27-27.523 0 74.807-47.99 123.501-115.04 123.501"/><g clip-path="url(#light-b)"><path fill="#fb81b8" d="M1101.42 501.152c-6.32-8.526-12.97-16.795-19.92-24.791l.37 10.173 7.02 15.085z"/><path fill="url(#light-c)" fill-rule="evenodd" d="M778.888 557.501c30.78-27.333 73.346-41.153 114.483-39.254 23.497 1.085 44.573 7.11 61.926 17.095 14.988 8.041 30.034 22.794 42.423 40.054 21.84 19.065 54.66 21.414 79.29 3.84 28.79-20.547 35.48-60.546 14.93-89.34-46.56-65.261-120.496-96.279-192.662-99.611-72.081-3.327-148.412 20.388-206.223 72.126-.197.176-.392.353-.586.531C578.01 565.83 568.261 742.131 671.023 856.963c23.589 26.359 64.078 28.604 90.437 5.015 26.358-23.589 28.603-64.081 5.015-90.44-55.695-62.237-50.344-157.912 11.926-213.598.163-.146.325-.292.487-.439" clip-rule="evenodd"/><mask id="light-e" width="505" height="490" x="599" y="389" maskUnits="userSpaceOnUse" style="mask-type:alpha"><path fill="url(#light-d)" fill-rule="evenodd" d="M778.899 557.49c30.78-27.326 73.341-41.142 114.473-39.243 23.496 1.084 44.57 7.109 61.923 17.092 14.989 8.041 30.036 22.795 42.427 40.057 21.838 19.065 54.658 21.414 79.288 3.839 28.8-20.547 35.48-60.546 14.93-89.34-46.56-65.261-120.495-96.279-192.661-99.61-72.081-3.328-148.412 20.388-206.223 72.126-.201.18-.402.362-.601.544-114.445 102.89-124.189 279.181-21.432 394.008 23.589 26.359 64.079 28.605 90.437 5.015 26.359-23.589 28.604-64.081 5.015-90.44-55.695-62.237-50.344-157.912 11.927-213.598.167-.149.332-.299.497-.45" clip-rule="evenodd"/></mask><g mask="url(#light-e)"><path fill="url(#light-f)" d="M696.794 409.876 479.212 622.645l397.604 61.808 160.014-125.632v-84.27z" style="mix-blend-mode:multiply"/></g><path fill="url(#light-g)" fill-rule="evenodd" d="M583.758 456.285c23.578 26.369 21.317 66.859-5.051 90.438-120.531 107.784-130.858 292.836-23.071 413.379 23.578 26.369 21.316 66.858-5.051 90.438-26.368 23.58-66.857 21.32-90.435-5.05-154.936-173.274-140.101-439.307 33.173-594.256 26.368-23.579 66.857-21.318 90.435 5.051" clip-rule="evenodd"/><path fill="url(#light-h)" fill-rule="evenodd" d="M465.201 955.053c26.368-23.579 66.857-21.318 90.435 5.051C663.416 1080.64 848.461 1090.97 969 983.176c26.367-23.579 66.86-21.317 90.43 5.051 23.58 26.373 21.32 66.863-5.05 90.443-173.263 154.94-439.287 140.1-594.23-33.18-23.578-26.37-21.317-66.858 5.051-90.437" clip-rule="evenodd"/><path fill="url(#light-i)" fill-rule="evenodd" d="M1042.72 524.524c30.56-17.811 69.78-7.475 87.59 23.087 97.14 166.689 77.81 393.581-75.86 531.039-26.37 23.58-66.858 21.33-90.439-5.04-23.581-26.36-21.325-66.86 5.04-90.438 103.369-92.463 120.579-250.963 50.589-371.06-17.81-30.562-7.48-69.777 23.08-87.588" clip-rule="evenodd"/><mask id="light-k" width="243" height="580" x="947" y="515" maskUnits="userSpaceOnUse" style="mask-type:alpha"><path fill="url(#light-j)" fill-rule="evenodd" d="M1042.72 524.524c30.56-17.812 69.78-7.475 87.59 23.087 97.14 166.688 77.81 393.58-75.86 531.039-26.37 23.58-66.858 21.33-90.439-5.04s-21.325-66.86 5.04-90.439c103.369-92.463 120.579-250.963 50.589-371.06-17.81-30.562-7.48-69.776 23.08-87.587" clip-rule="evenodd"/></mask><g mask="url(#light-k)"><path fill="url(#light-l)" d="M1017.23 787.403 802.995 1010.84l314.035 89.36 134.64-323.912-177.41-385.841-15.84 322.328z" style="mix-blend-mode:multiply"/></g><path fill="#f97cbf" fill-rule="evenodd" d="m1055.6 450.026 18.73 20.723 18.77 20.723c-.46-.696-.95-1.415-1.48-2.155l1.73 1.855c-.78-1.027-2.21-2.819-4.11-5.12-8.57-11.371-22.23-26.175-33.64-36.026" clip-rule="evenodd"/><path fill="url(#light-m)" fill-rule="evenodd" d="M676.114 766.509c26.368-23.579 66.857-21.318 90.435 5.05 55.684 62.273 151.355 67.624 213.59 11.927 26.361-23.589 66.851-21.344 90.441 5.015 23.58 26.36 21.34 66.851-5.02 90.44-115.01 102.93-291.683 92.986-394.496-21.994-23.578-26.368-21.317-66.859 5.05-90.438" clip-rule="evenodd"/><path fill="url(#light-n)" fill-rule="evenodd" d="M1087.54 484.386c-23.59-26.36-64.08-28.605-90.437-5.016-22.825 20.428-27.568 53.529-13.112 79.153 7.95 8.586 15.339 18.468 21.659 28.86 40.71 61.57 31.18 145.354-25.488 196.025-26.367 23.58-28.628 64.07-5.05 90.439 23.578 26.368 64.068 28.629 90.438 5.05 114.97-102.817 124.92-279.496 21.99-394.511" clip-rule="evenodd"/><path fill="url(#light-o)" fill-rule="evenodd" d="M978.643 553.03c-90.349-105.666-279.98-113.51-399.933-6.243-26.367 23.579-66.856 21.317-90.434-5.052-23.578-26.368-21.317-66.859 5.051-90.438 169.446-151.526 459.009-151.529 598.113 37.965 20.94 28.515 14.79 68.6-13.72 89.533-24.59 18.054-57.79 15.966-79.886-3.242-5.891-8.224-12.385-15.883-19.191-22.523" clip-rule="evenodd"/></g></g><defs><linearGradient id="light-c" x1="700.739" x2="743.912" y1="765.903" y2="488.37" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f8b580"/></linearGradient><linearGradient id="light-d" x1="700.739" x2="743.913" y1="765.904" y2="488.37" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f8b580"/></linearGradient><linearGradient id="light-f" x1="894.226" x2="645.573" y1="357.538" y2="644.576" gradientUnits="userSpaceOnUse"><stop stop-color="#895200"/><stop offset=".83333" stop-color="#e28800" stop-opacity="0"/></linearGradient><linearGradient id="light-g" x1="476.531" x2="507.311" y1="498.978" y2="949.402" gradientUnits="userSpaceOnUse"><stop stop-color="#ed51f2"/><stop offset="1" stop-color="#b771f2"/></linearGradient><linearGradient id="light-h" x1="475.636" x2="953.23" y1="975.598" y2="1004.36" gradientUnits="userSpaceOnUse"><stop stop-color="#b971f3"/><stop offset="1" stop-color="#8f6fde"/></linearGradient><linearGradient id="light-i" x1="1070.77" x2="996.795" y1="617.419" y2="1055.17" gradientUnits="userSpaceOnUse"><stop stop-color="#6a4bb2"/><stop offset="1" stop-color="#9170e0"/></linearGradient><linearGradient id="light-j" x1="1070.77" x2="984.423" y1="577.794" y2="1049.6" gradientUnits="userSpaceOnUse"><stop stop-color="#6a4bb2"/><stop offset="1" stop-color="#9170e0"/></linearGradient><linearGradient id="light-l" x1="964.956" x2="1076.27" y1="758.822" y2="993.615" gradientUnits="userSpaceOnUse"><stop stop-color="#542da7"/><stop offset=".83333" stop-color="#5f2eaf" stop-opacity="0"/></linearGradient><linearGradient id="light-m" x1="734.658" x2="953.595" y1="768.985" y2="830.655" gradientUnits="userSpaceOnUse"><stop stop-color="#f6d25b"/><stop offset="1" stop-color="#f9a38f"/></linearGradient><linearGradient id="light-n" x1="1049.54" x2="1058.75" y1="597.997" y2="831.152" gradientUnits="userSpaceOnUse"><stop stop-color="#fa80b7"/><stop offset="1" stop-color="#f8a48d"/></linearGradient><linearGradient id="light-o" x1="552.725" x2="1024.52" y1="482.202" y2="506.87" gradientUnits="userSpaceOnUse"><stop stop-color="#e755f3"/><stop offset="1" stop-color="#f97fb6"/></linearGradient><clipPath id="light-a"><path fill="#fff" d="M353 342h3420v843.819H353z"/></clipPath><clipPath id="light-b"><path fill="#fff" d="M353 342h837.037v843.819H353z"/></clipPath></defs></svg>
diff --git a/src/icons/rss.svg b/src/icons/rss.svg
new file mode 100644
index 0000000000..c87ee98604
--- /dev/null
+++ b/src/icons/rss.svg
@@ -0,0 +1,3 @@
+<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M2 0C0.896 0 0 0.896 0 2V14C0 15.104 0.896 16 2 16H14C15.104 16 16 15.104 16 14V2C16 0.896 15.104 0 14 0H2ZM4.801 12.8C3.922 12.8 3.2 12.078 3.2 11.199C3.2 10.32 3.922 9.6 4.801 9.6C5.68 9.6 6.4 10.32 6.4 11.199C6.4 12.078 5.68 12.8 4.801 12.8ZM8.326 12.8C8.326 9.975 6.025 7.674 3.2 7.674V5.474C7.24 5.474 10.526 8.76 10.526 12.8H8.326ZM12.012 12.8C12.012 7.938 8.062 3.988 3.2 3.988V1.788C9.276 1.788 14.212 6.724 14.212 12.8H12.012Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/slack.svg b/src/icons/slack.svg
new file mode 100644
index 0000000000..c0b1f1156a
--- /dev/null
+++ b/src/icons/slack.svg
@@ -0,0 +1,6 @@
+<svg width="12" height="12" viewBox="0 0 12 12" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M2.53036 7.58601C2.53036 8.28346 1.96713 8.84715 1.27026 8.84715C0.573391 8.84715 0.010166 8.28346 0.010166 7.58601C0.010166 6.88857 0.573391 6.32487 1.27026 6.32487H2.53036V7.58601ZM3.16041 7.58601C3.16041 6.88857 3.72363 6.32487 4.4205 6.32487C5.11738 6.32487 5.6806 6.88857 5.6806 7.58601V10.7389C5.6806 11.4363 5.11738 12 4.4205 12C3.72363 12 3.16041 11.4363 3.16041 10.7389V7.58601Z" fill="currentColor"/>
+<path d="M4.41988 2.52228C3.72301 2.52228 3.15979 1.95859 3.15979 1.26114C3.15979 0.563691 3.72301 0 4.41988 0C5.11676 0 5.67998 0.563691 5.67998 1.26114V2.52228H4.41988ZM4.41988 3.1624C5.11676 3.1624 5.67998 3.72609 5.67998 4.42354C5.67998 5.12099 5.11676 5.68468 4.41988 5.68468H1.2601C0.563225 5.68468 0 5.12099 0 4.42354C0 3.72609 0.563225 3.1624 1.2601 3.1624H4.41988Z" fill="currentColor"/>
+<path d="M9.47026 4.42354C9.47026 3.72609 10.0335 3.1624 10.7304 3.1624C11.4272 3.1624 11.9905 3.72609 11.9905 4.42354C11.9905 5.12099 11.4272 5.68468 10.7304 5.68468H9.47026V4.42354ZM8.84021 4.42354C8.84021 5.12099 8.27699 5.68468 7.58012 5.68468C6.88324 5.68468 6.32002 5.12099 6.32002 4.42354V1.26114C6.32002 0.563691 6.88324 0 7.58012 0C8.27699 0 8.84021 0.563691 8.84021 1.26114V4.42354Z" fill="currentColor"/>
+<path d="M7.58012 9.47772C8.27699 9.47772 8.84021 10.0414 8.84021 10.7389C8.84021 11.4363 8.27699 12 7.58012 12C6.88324 12 6.32002 11.4363 6.32002 10.7389V9.47772H7.58012ZM7.58012 8.84715C6.88324 8.84715 6.32002 8.28346 6.32002 7.58601C6.32002 6.88857 6.88324 6.32487 7.58012 6.32487H10.7399C11.4368 6.32487 12 6.88857 12 7.58601C12 8.28346 11.4368 8.84715 10.7399 8.84715H7.58012Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/telegram.svg b/src/icons/telegram.svg
new file mode 100644
index 0000000000..a32111b4a0
--- /dev/null
+++ b/src/icons/telegram.svg
@@ -0,0 +1,3 @@
+<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M8 0C3.58 0 0 3.58 0 8s3.58 8 8 8 8-3.58 8-8-3.58-8-8-8zm3.93 5.44-1.35 6.37c-.1.45-.36.56-.73.35l-2-1.48-1.01.97c-.11.11-.21.21-.42.21l.15-2.14 3.88-3.5c.17-.15-.04-.23-.26-.09L4.54 9.27 2.58 8.65c-.44-.14-.45-.44.09-.65l7.7-2.97c.37-.13.7.09.56.41z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/whatsapp.svg b/src/icons/whatsapp.svg
new file mode 100644
index 0000000000..3bee6534a0
--- /dev/null
+++ b/src/icons/whatsapp.svg
@@ -0,0 +1,3 @@
+<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path fill-rule="evenodd" clip-rule="evenodd" d="M8 0C3.58 0 0 3.58 0 8c0 1.41.37 2.73 1.01 3.88L0 16l4.25-1.11A7.96 7.96 0 0 0 8 16c4.42 0 8-3.58 8-8s-3.58-8-8-8zm4.45 11.32c-.19.53-1.11.98-1.52 1.04-.41.06-.83.07-1.34-.08-.31-.1-.7-.23-1.2-.45-2.12-.91-3.5-3.06-3.61-3.2-.1-.14-.84-1.12-.84-2.13 0-1.01.53-1.5.71-1.7.19-.2.41-.25.55-.25.14 0 .27 0 .39.01.13.01.3-.05.46.34.17.4.56 1.36.61 1.46.05.1.08.22.02.35-.06.13-.09.22-.18.33-.09.11-.19.25-.27.34-.09.09-.18.19-.08.38.1.19.46.75.99 1.22.68.6 1.25.79 1.43.88.19.09.3.07.41-.05.12-.12.5-.58.64-.78.13-.2.26-.17.44-.1.18.07 1.16.55 1.36.65.2.1.34.15.39.23.05.08.05.46-.14.99z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/x.svg b/src/icons/x.svg
new file mode 100644
index 0000000000..780ab6a346
--- /dev/null
+++ b/src/icons/x.svg
@@ -0,0 +1,3 @@
+<svg width="11" height="10" viewBox="0 0 11 10" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M8.66314 0H10.3499L6.66486 4.21175L11 9.94298H7.60562L4.94702 6.46702L1.90497 9.94298H0.217216L4.15872 5.43805L0 0H3.48055L5.8837 3.17717L8.66314 0ZM8.07115 8.93339H9.00579L2.9727 0.956566H1.96973L8.07115 8.93339Z" fill="currentColor"/>
+</svg>
diff --git a/src/icons/youtube.svg b/src/icons/youtube.svg
new file mode 100644
index 0000000000..e8db9ce050
--- /dev/null
+++ b/src/icons/youtube.svg
@@ -0,0 +1,3 @@
+<svg width="12" height="9" viewBox="0 0 12 9" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M11.8805 1.82109C11.8805 1.82109 11.7633 0.99375 11.4023 0.630469C10.9453 0.152344 10.4344 0.15 10.2 0.121875C8.52188 -6.70552e-08 6.00234 0 6.00234 0H5.99766C5.99766 0 3.47813 -6.70552e-08 1.8 0.121875C1.56563 0.15 1.05469 0.152344 0.597656 0.630469C0.236719 0.99375 0.121875 1.82109 0.121875 1.82109C0.121875 1.82109 0 2.79375 0 3.76406V4.67344C0 5.64375 0.119531 6.61641 0.119531 6.61641C0.119531 6.61641 0.236719 7.44375 0.595312 7.80703C1.05234 8.28516 1.65234 8.26875 1.91953 8.32031C2.88047 8.41172 6 8.43985 6 8.43985C6 8.43985 8.52188 8.43516 10.2 8.31563C10.4344 8.2875 10.9453 8.28516 11.4023 7.80703C11.7633 7.44375 11.8805 6.61641 11.8805 6.61641C11.8805 6.61641 12 5.64609 12 4.67344V3.76406C12 2.79375 11.8805 1.82109 11.8805 1.82109ZM4.76016 5.77734V2.40469L8.00156 4.09688L4.76016 5.77734Z" fill="currentColor"/>
+</svg>
diff --git a/src/layouts/DocLayout.astro b/src/layouts/DocLayout.astro
new file mode 100644
index 0000000000..d0d21c2db3
--- /dev/null
+++ b/src/layouts/DocLayout.astro
@@ -0,0 +1,109 @@
+---
+import Layout from './Layout.astro';
+import type { AdjacentPage } from '@utils/content';
+import { buildBreadcrumbs } from '@utils/content';
+import { PageTopbar, TableOfContents, DocBottomNav } from '@components/patterns';
+import { Button, Container } from '@/components/primitives';
+import { Icon } from 'astro-icon/components';
+import { getLangFromUrl, useTranslations } from '@/i18n/utils';
+
+interface Heading {
+  depth: number;
+  slug: string;
+  text: string;
+}
+
+interface Props {
+  title: string;
+  description?: string;
+  headings?: Heading[];
+  editUrl?: string;
+  isTranslation?: boolean;
+  prev?: AdjacentPage | null;
+  next?: AdjacentPage | null;
+}
+
+const {
+  title,
+  description,
+  headings = [],
+  editUrl,
+  isTranslation = false,
+  prev,
+  next,
+} = Astro.props;
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+const breadcrumbs = buildBreadcrumbs(Astro.url.pathname, t);
+---
+
+<Layout title={title} description={description}>
+  <Container>
+    <PageTopbar breadcrumbs={breadcrumbs}>
+      {
+        editUrl && (
+          <Button as="a" variant="secondary" size="sm" href={editUrl}>
+            <Icon
+              name={isTranslation ? 'fluent:translate-20-regular' : 'github'}
+              aria-hidden="true"
+            />
+            {isTranslation ? t('page.translateThis') : t('page.editOnGitHub')}
+          </Button>
+        )
+      }
+    </PageTopbar>
+
+    <div class="doc-layout">
+      <article>
+        <h1 id="overview">
+          <a href="#overview">{title}</a>
+        </h1>
+        <slot />
+        <DocBottomNav {prev} {next} />
+      </article>
+
+      <TableOfContents headings={headings} class="doc-toc" />
+    </div>
+  </Container>
+</Layout>
+
+<style>
+  .doc-layout {
+    display: flex;
+    flex-direction: column;
+  }
+
+  @media (--md-up) {
+    .doc-layout {
+      flex-direction: row;
+      align-items: flex-start;
+      gap: var(--space-10);
+    }
+  }
+
+  .doc-layout > article {
+    min-width: 0;
+    flex: 1;
+    order: 1;
+  }
+
+  .doc-toc {
+    flex-shrink: 0;
+    order: 0;
+    background-color: var(--color-bg-primary);
+    position: sticky;
+    top: var(--space-14);
+    padding: var(--space-6) 0 0;
+  }
+
+  @media (--md-up) {
+    .doc-toc {
+      order: 1;
+      width: var(--size-56);
+      max-height: calc(100vh - var(--space-24));
+      overflow-y: auto;
+    }
+  }
+</style>
diff --git a/src/layouts/Layout.astro b/src/layouts/Layout.astro
new file mode 100644
index 0000000000..bfe6e71174
--- /dev/null
+++ b/src/layouts/Layout.astro
@@ -0,0 +1,161 @@
+---
+import '@styles/main.css';
+import { Flex, FlexItem } from '@components/primitives';
+import { Footer, Sidebar } from '@/components/patterns';
+import { Header } from '@/components/patterns';
+import { getLangFromUrl, replaceLanguageInPath } from '@/i18n/utils';
+import { languages } from '@/i18n/locales';
+
+interface Props {
+  title?: string;
+  description?: string;
+  authors?: { name: string; github?: string }[];
+  image?: string;
+}
+
+const {
+  title,
+  description = 'Fast, unopinionated, minimalist web framework for Node.js',
+  authors,
+  image,
+} = Astro.props;
+
+const pageTitle = title
+  ? `${title} · Express.js`
+  : 'Express.js · Node.js web application framework';
+
+const canonicalUrl = new URL(Astro.url.pathname, Astro.site || Astro.url.origin);
+
+const pathname = Astro.url.pathname.replace(/\/$/, '');
+const segments = pathname.split('/').filter(Boolean);
+const langSegment = segments[0] || 'en';
+const restSegments = segments.slice(1);
+const isApi =
+  restSegments[0] === 'api' || (restSegments[1] === 'api' && /^\dx$/.test(restSegments[0] ?? ''));
+const isBlogOrApi = restSegments[0] === 'blog' || isApi;
+// Build the OG image URL:
+// - Home pages (no rest segments) use a per-language image: /og/home-{lang}.png
+// - Blog and API pages strip the lang prefix since their content is not translated: /og/blog-{slug}.png
+// - Docs and other pages include the lang prefix for i18n support: /og/{lang}-{slug}.png
+const ogSlug =
+  restSegments.length === 0 ? '' : isBlogOrApi ? restSegments.join('-') : segments.join('-');
+const imageUrl = image
+  ? new URL(image, Astro.site || Astro.url.origin)
+  : new URL(`/og/${ogSlug || `home-${langSegment}`}.png`, Astro.site || Astro.url.origin);
+
+const isNetlify = import.meta.env.DEPLOY_PRIME_URL;
+
+const lang = getLangFromUrl(Astro.url);
+---
+
+<!doctype html>
+<html lang={lang} dir={languages[lang].direction}>
+  <head>
+    <script is:inline>
+      (function () {
+        // Theme
+        const storedTheme = localStorage.getItem('theme');
+        const theme =
+          storedTheme === 'dark' || storedTheme === 'light'
+            ? storedTheme
+            : window.matchMedia('(prefers-color-scheme: dark)').matches
+              ? 'dark'
+              : 'light';
+        document.documentElement.setAttribute('data-theme', theme);
+
+        // Dismissed banners
+        const styles = [];
+        for (let i = 0; i < localStorage.length; i++) {
+          const key = localStorage.key(i);
+          if (key && key.startsWith('banner-dismissed-') && localStorage.getItem(key) === 'true') {
+            styles.push('#banner-' + key.replace('banner-dismissed-', '') + '{display:none}');
+          }
+        }
+        if (styles.length) {
+          const el = document.createElement('style');
+          el.textContent = styles.join('');
+          document.head.appendChild(el);
+        }
+      })();
+    </script>
+
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width" />
+    <link rel="icon" href="/favicon.svg" type="image/svg+xml" />
+    <link rel="icon" href="/favicon.ico" sizes="any" />
+    <link rel="apple-touch-icon" href="/apple-touch-icon.png" />
+    <link rel="manifest" href="/site.webmanifest" />
+    <meta name="description" content={description} />
+
+    <link rel="canonical" href={canonicalUrl} />
+
+    {
+      Object.keys(languages).map((altLang) => (
+        <link
+          rel="alternate"
+          hreflang={altLang}
+          href={
+            new URL(
+              replaceLanguageInPath(Astro.url.pathname, altLang),
+              Astro.site || Astro.url.origin
+            )
+          }
+        />
+      ))
+    }
+
+    <title>{pageTitle}</title>
+
+    <style is:inline>
+      @layer orama, base, primitives, patterns;
+    </style>
+
+    <!-- Open Graph -->
+    <meta property="og:type" content={authors?.length ? 'article' : 'website'} />
+    <meta property="og:site_name" content="Express.js" />
+    <meta property="og:url" content={canonicalUrl} />
+    <meta property="og:title" content={pageTitle} />
+    <meta property="og:description" content={description} />
+    <meta property="og:image" content={imageUrl} />
+    {authors?.map((author) => <meta property="article:author" content={author.name} />)}
+
+    <!-- Twitter Card -->
+    <meta name="twitter:card" content="summary_large_image" />
+    <meta name="twitter:site" content="@UseExpressJS" />
+    <meta name="twitter:title" content={pageTitle} />
+    <meta name="twitter:description" content={description} />
+    <meta name="twitter:domail" content="expressjs.com" />
+    <meta name="twitter:image" content={imageUrl} />
+
+    <link rel="sitemap" href={new URL('/sitemap-index.xml', Astro.site || Astro.url.origin)} />
+    <!-- Robots meta tag for Google Search. Enables a large image preview in Google search results,
+      most pertinently in Chrome’s “Discover” view on mobile. See:
+      https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#max-image-preview
+    -->
+    <meta
+      name="robots"
+      content={isNetlify ? 'noindex, nofollow' : 'max-image-preview:large, index, follow'}
+    />
+    <link rel="alternate" type="application/rss+xml" href="/feed.xml" title="The Express.js blog" />
+    <link
+      rel="alternate"
+      type="application/rss+xml"
+      href="/vulnerabilities.xml"
+      title="Express.js Security Feed"
+    />
+  </head>
+  <body>
+    <Header />
+    <Flex class="layout-wrapper">
+      <Sidebar />
+      <FlexItem grow class="layout-content">
+        <Flex direction="column" class="h-full">
+          <main id="main-content" tabindex="-1">
+            <slot />
+          </main>
+          <Footer />
+        </Flex>
+      </FlexItem>
+    </Flex>
+  </body>
+</html>
diff --git a/src/pages/404.astro b/src/pages/404.astro
new file mode 100644
index 0000000000..3a7e077c19
--- /dev/null
+++ b/src/pages/404.astro
@@ -0,0 +1,27 @@
+---
+import Layout from '@/layouts/Layout.astro';
+import { Icon } from 'astro-icon/components';
+import { Container, H1, H2, Body, Button, Flex } from '@components/primitives';
+---
+
+<Layout title="404 - Page Not Found" description="The page you are looking for could not be found.">
+  <Container>
+    <div>
+      <H1>404</H1>
+      <H2>Page Not Found</H2>
+      <Body color="secondary">
+        The page you are looking for does not exist or has been moved.
+      </Body>
+      <Flex gap="4">
+        <Button as="a" href="/en" variant="primary">Go to Home</Button>
+        <Button
+          as="a"
+          href={'https://github.com/expressjs/expressjs.com/issues/new?template=4documentation.yml'}
+        >
+          <Icon name="fluent:warning-24-regular" size="20" />
+          Raise a issue
+        </Button>
+      </Flex>
+    </div>
+  </Container>
+</Layout>
diff --git a/src/pages/[lang]/[...slug].astro b/src/pages/[lang]/[...slug].astro
new file mode 100644
index 0000000000..eda57c401b
--- /dev/null
+++ b/src/pages/[lang]/[...slug].astro
@@ -0,0 +1,222 @@
+---
+import { getCollection } from 'astro:content';
+import DocLayout from '@layouts/DocLayout.astro';
+import { languages } from '@i18n/locales';
+import { render } from 'astro:content';
+import { getAdjacentPages } from '@utils/content';
+import { docsMenu } from '@/config/menu/docs';
+import { apiMenu } from '@/config/menu/api';
+import { resourcesMenu } from '@/config/menu/resources';
+import type { LanguageCode } from '@i18n/locales';
+
+export async function getStaticPaths() {
+  const DEFAULT_VERSION = '5x';
+  const VERSION_PREFIXES = ['5x', '4x', '3x'];
+  const DEFAULT_LANG = 'en';
+
+  const pages = await getCollection('docs');
+  const api = await getCollection('api');
+  const contentPages = await getCollection('pages');
+
+  type AnyPage = (typeof pages)[0] | (typeof api)[0] | (typeof contentPages)[0];
+
+  const paths: Array<{
+    params: { lang: string; slug: string };
+    props: { page: AnyPage; version?: string };
+  }> = [];
+
+  // Helper to create a map of existing content for fallback logic
+  const existingContent = new Map<string, AnyPage>();
+  pages.forEach((page) => {
+    const [lang, ...slugParts] = page.id.split('/');
+    const fullSlug = slugParts.join('/');
+    existingContent.set(`${lang}/${fullSlug}`, page);
+  });
+
+  api.forEach((page) => {
+    existingContent.set(`en/${page.id}`, page);
+  });
+
+  pages.forEach((page) => {
+    const [lang, ...slugParts] = page.id.split('/');
+    const fullSlug = slugParts.join('/');
+
+    const isVersioned = VERSION_PREFIXES.some((v) => fullSlug.startsWith(`${v}/`));
+
+    paths.push({
+      params: { lang, slug: fullSlug },
+      props: { page, version: isVersioned ? slugParts[0] : DEFAULT_VERSION },
+    });
+  });
+
+  contentPages.forEach((page) => {
+    const [lang, ...slugParts] = page.id.split('/');
+    const fullSlug = slugParts.join('/');
+
+    paths.push({
+      params: { lang, slug: fullSlug },
+      props: { page },
+    });
+  });
+
+  for (const lang of Object.keys(languages)) {
+    api.forEach((page) => {
+      const slugParts = page.id.split('/');
+      const version = slugParts[0];
+      const slug = page.id;
+
+      paths.push({
+        params: { lang, slug },
+        props: { page, version },
+      });
+    });
+  }
+
+  const defaultVersionApiPages = api.filter((page) => page.id.startsWith(`${DEFAULT_VERSION}/`));
+
+  for (const lang of Object.keys(languages)) {
+    defaultVersionApiPages.forEach((page) => {
+      const [, ...restSlugParts] = page.id.split('/');
+      const nonVersionedSlug = restSlugParts.join('/');
+
+      const exists = paths.some(
+        (p) => p.params.lang === lang && p.params.slug === nonVersionedSlug
+      );
+
+      if (!exists && nonVersionedSlug) {
+        paths.push({
+          params: { lang, slug: nonVersionedSlug },
+          props: { page, version: DEFAULT_VERSION },
+        });
+      }
+    });
+  }
+
+  const defaultVersionPages = pages.filter((page) => {
+    const [, ...slugParts] = page.id.split('/');
+    return slugParts[0] === DEFAULT_VERSION;
+  });
+
+  defaultVersionPages.forEach((page) => {
+    const [lang, , ...restSlugParts] = page.id.split('/');
+    const nonVersionedSlug = restSlugParts.join('/');
+
+    const exists = paths.some((p) => p.params.lang === lang && p.params.slug === nonVersionedSlug);
+
+    if (!exists && nonVersionedSlug) {
+      paths.push({
+        params: { lang, slug: nonVersionedSlug },
+        props: { page, version: DEFAULT_VERSION },
+      });
+    }
+  });
+
+  // Fallback for non-versioned default-version slugs: use English content for missing languages
+  const englishDefaultVersionPages = defaultVersionPages.filter((p) =>
+    p.id.startsWith(`${DEFAULT_LANG}/`)
+  );
+
+  for (const lang of Object.keys(languages)) {
+    if (lang === DEFAULT_LANG) continue;
+
+    englishDefaultVersionPages.forEach((page) => {
+      const [, , ...restSlugParts] = page.id.split('/');
+      const nonVersionedSlug = restSlugParts.join('/');
+
+      const exists = paths.some(
+        (p) => p.params.lang === lang && p.params.slug === nonVersionedSlug
+      );
+
+      if (!exists && nonVersionedSlug) {
+        paths.push({
+          params: { lang, slug: nonVersionedSlug },
+          props: { page, version: DEFAULT_VERSION },
+        });
+      }
+    });
+  }
+
+  // Fallback: Create paths for non-English languages using English pages content
+  for (const lang of Object.keys(languages)) {
+    if (lang === DEFAULT_LANG) continue;
+
+    const englishContentPages = contentPages.filter((p) => p.id.startsWith(`${DEFAULT_LANG}/`));
+
+    englishContentPages.forEach((page) => {
+      const [, ...slugParts] = page.id.split('/');
+      const fullSlug = slugParts.join('/');
+
+      const langSpecificExists = paths.some(
+        (p) => p.params.lang === lang && p.params.slug === fullSlug
+      );
+
+      if (!langSpecificExists) {
+        paths.push({
+          params: { lang, slug: fullSlug },
+          props: { page },
+        });
+      }
+    });
+  }
+
+  // Fallback: Create paths for non-English languages using English docs content
+  for (const lang of Object.keys(languages)) {
+    if (lang === DEFAULT_LANG) continue; // Skip English, already added
+
+    const englishPages = pages.filter((p) => p.id.startsWith(`${DEFAULT_LANG}/`));
+
+    englishPages.forEach((page) => {
+      const [, ...slugParts] = page.id.split('/');
+      const fullSlug = slugParts.join('/');
+
+      const langSpecificExists = paths.some(
+        (p) => p.params.lang === lang && p.params.slug === fullSlug
+      );
+
+      // If no language-specific version exists, add fallback to English
+      if (!langSpecificExists) {
+        paths.push({
+          params: { lang, slug: fullSlug },
+          props: {
+            page,
+            version: slugParts[0] === DEFAULT_VERSION ? DEFAULT_VERSION : slugParts[0],
+          },
+        });
+      }
+    });
+  }
+
+  return paths;
+}
+
+const { page, version } = Astro.props;
+const { lang: langParam, slug } = Astro.params;
+const lang = langParam as LanguageCode;
+const { Content, headings } = await render(page);
+const { title, description } = page.data;
+const isTranslation = lang !== 'en';
+const fileExt = page.filePath?.endsWith('.mdx') ? '.mdx' : '.md';
+const { prev, next } = getAdjacentPages(
+  slug,
+  lang,
+  [{ menu: docsMenu }, { menu: apiMenu }, { menu: resourcesMenu, global: true }],
+  version
+);
+
+// TODO: change the url when finish the redesign, this is just a temporary solution to avoid broken links for translated pages
+const editUrl = isTranslation
+  ? `https://github.com/expressjs/expressjs.com/blob/redesign/docs/i18n.md`
+  : `https://github.com/expressjs/expressjs.com/edit/redesign/src/content/${page.collection}/${page.id}${fileExt}`;
+---
+
+<DocLayout
+  title={title}
+  description={description}
+  headings={headings}
+  editUrl={editUrl}
+  isTranslation={isTranslation}
+  prev={prev}
+  next={next}
+>
+  <Content />
+</DocLayout>
diff --git a/src/pages/[lang]/blog/[...page].astro b/src/pages/[lang]/blog/[...page].astro
new file mode 100644
index 0000000000..fa1545f8d9
--- /dev/null
+++ b/src/pages/[lang]/blog/[...page].astro
@@ -0,0 +1,199 @@
+---
+import Layout from '@layouts/Layout.astro';
+import { languages } from '@i18n/locales';
+import { Container, Grid, Col } from '@components/primitives';
+import { Tabs } from '@components/primitives/Tabs';
+import type { TabItem } from '@components/primitives';
+import { PostCard, PageHead, Pagination } from '@components/patterns';
+import { getCollection, type CollectionEntry } from 'astro:content';
+import type { PaginateFunction } from 'astro';
+
+export async function getStaticPaths({ paginate }: { paginate: PaginateFunction }) {
+  const PAGE_SIZE = 6;
+  const allPosts = await getCollection('blog');
+
+  return Object.keys(languages).flatMap((lang) => {
+    const langPosts = allPosts
+      .filter((post) => post.id !== 'write-post')
+      .sort((a, b) => {
+        const aFile = a.id.split('/').pop() ?? '';
+        const bFile = b.id.split('/').pop() ?? '';
+        return bFile.localeCompare(aFile);
+      });
+
+    const allTags = [...new Set(langPosts.flatMap((p) => p.data.tags ?? []))];
+
+    return paginate(langPosts, {
+      params: { lang },
+      pageSize: PAGE_SIZE,
+      props: { allTags, langPosts, pageSize: PAGE_SIZE },
+    });
+  });
+}
+
+const { page, allTags, langPosts, pageSize } = Astro.props;
+const { lang } = Astro.params;
+const pagePosts = page.data as CollectionEntry<'blog'>[];
+
+function getDate(id: string) {
+  const filename = id.split('/').pop() ?? id;
+  return new Date(filename.substring(0, 10)).toLocaleDateString('en-US', {
+    month: 'short',
+    day: 'numeric',
+    year: 'numeric',
+  });
+}
+
+function formatTagLabel(tag: string) {
+  const spaced = tag.replace(/-/g, ' ');
+  return spaced.charAt(0).toUpperCase() + spaced.slice(1);
+}
+
+function getLabels(tags?: string[]) {
+  return (tags ?? []).map(formatTagLabel);
+}
+
+function getPostProps(post: CollectionEntry<'blog'>) {
+  return {
+    href: `/${lang}/blog/${post.id.split('/').pop()}`,
+    labels: getLabels(post.data.tags),
+    title: post.data.title,
+    coverSrc: post.data.cover || `/og/blog-${post.id.split('/').pop()}.png`,
+    authors: (post.data.authors ?? []).map((a) => ({
+      src: a.github ? `https://github.com/${a.github}.png` : '',
+      name: a.name ?? '',
+    })),
+    avatarCaption: getDate(post.id),
+  };
+}
+
+const filterTabs: TabItem[] = [
+  { label: 'All', value: 'all' },
+  ...(allTags as string[]).map((tag) => ({
+    label: formatTagLabel(tag),
+    value: tag,
+  })),
+];
+---
+
+<Layout title="Express Blog">
+  <Container>
+    <PageHead
+      title="Blog"
+      description="Stay tuned for details on new releases, enhancements, and everything you need to know to make the most of your Express applications. Let's dive into what's new!"
+    />
+    <Tabs tabs={filterTabs} defaultValue="all" data-posts-filter />
+    <Grid gap="4" align="stretch" data-posts-grid>
+      {
+        pagePosts.map((post) => (
+          <Col xs={12} md={6} lg={4} data-post-tags={(post.data.tags ?? []).join(' ')}>
+            <PostCard {...getPostProps(post)} />
+          </Col>
+        ))
+      }
+    </Grid>
+    <Pagination
+      data-pagination
+      prevUrl={page.url.prev}
+      nextUrl={page.url.next}
+      currentPage={page.currentPage}
+      lastPage={page.lastPage}
+      style={page.lastPage <= 1 ? 'display:none' : ''}
+    />
+    <template data-posts-pool>
+      {
+        langPosts.map((post) => (
+          <Col xs={12} md={6} lg={4} data-post-tags={(post.data.tags ?? []).join(' ')}>
+            <PostCard {...getPostProps(post)} />
+          </Col>
+        ))
+      }
+    </template>
+  </Container>
+</Layout>
+
+<script
+  define:vars={{
+    pageSize,
+    currentStaticPage: page.currentPage,
+    lastStaticPage: page.lastPage,
+  }}
+  is:inline
+>
+  function initBlogFilter() {
+    const filter = document.querySelector('[data-posts-filter]');
+    const grid = document.querySelector('[data-posts-grid]');
+    const pool = document.querySelector('[data-posts-pool]');
+    const paginationEl = document.querySelector('[data-pagination]');
+    const prevBtn = document.querySelector('[data-pagination-prev]');
+    const nextBtn = document.querySelector('[data-pagination-next]');
+    const pageLabel = document.querySelector('[data-pagination-label]');
+
+    if (!filter || !grid || !pool) return;
+
+    const staticCards = Array.from(grid.children);
+    const allCards = Array.from(pool.content.children);
+    let currentTag = 'all';
+    let filterPage = 1;
+
+    function getFiltered() {
+      if (currentTag === 'all') return allCards;
+      return allCards.filter((el) =>
+        el.dataset.postTags.split(' ').filter(Boolean).includes(currentTag)
+      );
+    }
+
+    function setPaginationState(currentPage, totalPages) {
+      if (paginationEl) {
+        paginationEl.style.display = totalPages > 1 ? '' : 'none';
+      }
+      if (pageLabel) pageLabel.textContent = `Page ${currentPage} of ${totalPages}`;
+      if (prevBtn) prevBtn.setAttribute('aria-disabled', String(currentPage === 1));
+      if (nextBtn) nextBtn.setAttribute('aria-disabled', String(currentPage >= totalPages));
+    }
+
+    function renderFiltered() {
+      const filtered = getFiltered();
+      const totalPages = Math.ceil(filtered.length / pageSize) || 1;
+      const start = (filterPage - 1) * pageSize;
+      grid.innerHTML = '';
+      filtered.slice(start, start + pageSize).forEach((el) => grid.appendChild(el.cloneNode(true)));
+      setPaginationState(filterPage, totalPages);
+    }
+
+    function restoreStatic() {
+      grid.innerHTML = '';
+      staticCards.forEach((card) => grid.appendChild(card));
+      setPaginationState(currentStaticPage, lastStaticPage);
+    }
+
+    filter.addEventListener('tabs-change', (e) => {
+      currentTag = e.detail.value;
+      filterPage = 1;
+      if (currentTag === 'all') {
+        restoreStatic();
+      } else {
+        renderFiltered();
+      }
+    });
+
+    prevBtn?.addEventListener('click', (e) => {
+      if (currentTag === 'all') return;
+      e.preventDefault();
+      if (prevBtn.getAttribute('aria-disabled') === 'true') return;
+      filterPage--;
+      renderFiltered();
+    });
+
+    nextBtn?.addEventListener('click', (e) => {
+      if (currentTag === 'all') return;
+      e.preventDefault();
+      if (nextBtn.getAttribute('aria-disabled') === 'true') return;
+      filterPage++;
+      renderFiltered();
+    });
+  }
+
+  initBlogFilter();
+  document.addEventListener('astro:page-load', initBlogFilter);
+</script>
diff --git a/src/pages/[lang]/blog/[slug].astro b/src/pages/[lang]/blog/[slug].astro
new file mode 100644
index 0000000000..db0a9e75e0
--- /dev/null
+++ b/src/pages/[lang]/blog/[slug].astro
@@ -0,0 +1,134 @@
+---
+import { getCollection, render } from 'astro:content';
+import Layout from '@layouts/Layout.astro';
+import { Container, Button } from '@/components/primitives';
+import { languages } from '@i18n/locales';
+import { getLangFromUrl, useTranslations } from '@i18n/utils';
+import { Icon } from 'astro-icon/components';
+import {
+  PageTopbar,
+  PostHeader,
+  TableOfContents,
+  WriteBanner,
+  RelatedContent,
+} from '@/components/patterns';
+
+export async function getStaticPaths() {
+  const posts = await getCollection('blog');
+
+  return Object.keys(languages).flatMap((lang) =>
+    posts.map((post) => {
+      const filename = post.id.split('/').pop()!;
+      return {
+        params: { lang, slug: filename },
+        props: { post },
+      };
+    })
+  );
+}
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+
+const { post } = Astro.props;
+const { Content, headings } = await render(post);
+
+const { title, description, tags, authors, cover: customCover } = post.data;
+const filename = post.id.split('/').pop() ?? post.id;
+const cover = customCover || `/og/blog-${filename}.png`;
+const authorsList = (authors ?? []).map((a) => ({
+  src: a.github ? `https://github.com/${a.github}.png` : '',
+  name: a.name ?? '',
+}));
+const dateSource = filename.substring(0, 10);
+const parsedDate = new Date(dateSource);
+const date = Number.isNaN(parsedDate.getTime())
+  ? undefined
+  : parsedDate.toLocaleDateString('en-US', {
+      month: 'long',
+      day: 'numeric',
+      year: 'numeric',
+    });
+const labels = tags ?? [];
+
+const allPosts = (await getCollection('blog'))
+  .filter((p) => p.id !== post.id && p.id !== 'write-post')
+  .sort((a, b) => b.id.localeCompare(a.id));
+
+const currentTags = new Set(tags ?? []);
+const tagged = allPosts.filter((p) => p.data.tags?.some((tag) => currentTags.has(tag)));
+const untagged = allPosts.filter((p) => !p.data.tags?.some((tag) => currentTags.has(tag)));
+const relatedPosts = [...tagged, ...untagged].slice(0, 3);
+---
+
+<Layout title={title} description={description} authors={authors} image={customCover}>
+  <Container>
+    <PageTopbar breadcrumbs={[{ label: t('menu.main.blog'), href: `/${Astro.params.lang}/blog` }]}>
+      <Button
+        as="a"
+        variant="secondary"
+        size="sm"
+        href={`https://github.com/expressjs/expressjs.com/edit/main/src/content/blog/${Astro.params.slug}`}
+      >
+        <Icon name="github" aria-hidden="true" />
+        {t('page.editOnGitHub')}
+      </Button>
+    </PageTopbar>
+
+    <article>
+      <PostHeader labels={labels} title={title} authors={authorsList} date={date} cover={cover} />
+
+      <div class="blog-post-body">
+        <div class="blog-post-content">
+          <Content />
+        </div>
+        <TableOfContents headings={headings} class="blog-post-toc" />
+      </div>
+    </article>
+    <RelatedContent posts={relatedPosts} lang={Astro.params.lang} title={t('post.more')} />
+    {
+      filename !== 'write-post' && (
+        <WriteBanner
+          message={t('post.writeBanner')}
+          linkLabel={t('post.writeGuidelines')}
+          href={`/${Astro.params.lang}/blog/write-post`}
+        />
+      )
+    }
+  </Container>
+</Layout>
+
+<style>
+  .blog-post-body {
+    display: flex;
+    flex-direction: column;
+
+    @media (--md-up) {
+      flex-direction: row;
+      align-items: flex-start;
+      gap: var(--space-10);
+    }
+  }
+
+  .blog-post-content {
+    min-width: 0;
+    flex: 1;
+    order: 1;
+  }
+
+  .blog-post-toc {
+    flex-shrink: 0;
+    order: 0;
+    background-color: var(--color-bg-primary);
+    position: sticky;
+    top: var(--space-14);
+    padding: var(--space-6) 0 0;
+
+    @media (--md-up) {
+      order: 1;
+      width: var(--size-56);
+      max-height: calc(100vh - var(--space-24));
+      overflow-y: auto;
+    }
+  }
+</style>
diff --git a/src/pages/[lang]/index.astro b/src/pages/[lang]/index.astro
new file mode 100644
index 0000000000..ba47561e5d
--- /dev/null
+++ b/src/pages/[lang]/index.astro
@@ -0,0 +1,35 @@
+---
+import { Hero, Features, AnnouncementBar } from '@components/patterns';
+import { Card, Col } from '@components/primitives';
+import Layout from '@layouts/Layout.astro';
+import { languages } from '@i18n/locales';
+import { getLangFromUrl, useTranslations } from '@i18n/utils';
+
+export function getStaticPaths() {
+  return Object.keys(languages).map((lang) => ({
+    params: { lang },
+  }));
+}
+
+const lang = getLangFromUrl(Astro.url);
+const t = useTranslations(lang);
+---
+
+<Layout>
+  <AnnouncementBar />
+  <Hero />
+  <Features title={t('features.title')}>
+    <Col xs={12} md={6} lg={6} class="features__card-col">
+      <Card title={t('features.webapplication.title')} body={t('features.webapplication.body')} />
+    </Col>
+    <Col xs={12} md={6} lg={6} class="features__card-col">
+      <Card title={t('features.api.title')} body={t('features.api.body')} />
+    </Col>
+    <Col xs={12} md={6} lg={6} class="features__card-col">
+      <Card title={t('features.performance.title')} body={t('features.performance.body')} />
+    </Col>
+    <Col xs={12} md={6} lg={6} class="features__card-col">
+      <Card title={t('features.middleware.title')} body={t('features.middleware.body')} />
+    </Col>
+  </Features>
+</Layout>
diff --git a/src/pages/feed.xml.ts b/src/pages/feed.xml.ts
new file mode 100644
index 0000000000..0041a0e99a
--- /dev/null
+++ b/src/pages/feed.xml.ts
@@ -0,0 +1,31 @@
+import rss from '@astrojs/rss';
+import { getCollection } from 'astro:content';
+import type { APIRoute } from 'astro';
+import {
+  getLinkedTitleContent,
+  getAuthorsCustomData,
+  getPubDateFromId,
+  shouldIncludeInFeed,
+  sortByIdDateDesc,
+} from '@/utils/rss';
+
+export const GET: APIRoute = async (context) => {
+  const site = context.site as URL;
+  const blog = await getCollection('blog');
+  const sortedBlog = sortByIdDateDesc(blog.filter((post) => shouldIncludeInFeed(post.id)));
+
+  return rss({
+    title: 'The Express.js Blog',
+    description: 'News and updates about express.js',
+    site: site.href,
+    items: sortedBlog.map((post) => ({
+      link: `/blog/${post.id}/`,
+      title: post.data.title,
+      pubDate: getPubDateFromId(post.id),
+      description: post.data.description,
+      content: getLinkedTitleContent(post.data.title, post.id, site),
+      categories: post.data.tags,
+      customData: getAuthorsCustomData(post.data.authors),
+    })),
+  });
+};
diff --git a/src/pages/index.astro b/src/pages/index.astro
new file mode 100644
index 0000000000..655eb6cb65
--- /dev/null
+++ b/src/pages/index.astro
@@ -0,0 +1 @@
+<meta http-equiv="refresh" content="0;url=/en/" />
diff --git a/src/pages/llms.txt.ts b/src/pages/llms.txt.ts
new file mode 100644
index 0000000000..ce5e5df2d8
--- /dev/null
+++ b/src/pages/llms.txt.ts
@@ -0,0 +1,53 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+
+export const GET: APIRoute = async ({ site }) => {
+  const siteUrl = site as URL;
+
+  const api = await getCollection('api');
+
+  // Extract API versions from the collection (e.g. "5x", "4x", "3x")
+  const apiVersions = [...new Set(api.map((d) => d.id.split('/')[0]))].sort().reverse();
+
+  // Extract docs versions (e.g. "5x", "4x")
+  const docs = await getCollection('docs');
+  const docsVersions = [...new Set(docs.map((d) => d.id.replace('en/', '').split('/')[0]))]
+    .sort()
+    .reverse();
+
+  const lines: string[] = [
+    '# Express.js',
+    '',
+    '> Express is a minimal and flexible Node.js web application framework that provides',
+    '> a robust set of features for building web and mobile applications. It is the',
+    '> standard server framework for Node.js and is part of the OpenJS Foundation.',
+    '',
+    '- Website: https://expressjs.com',
+    '- GitHub: https://github.com/expressjs/express',
+    '- npm: https://www.npmjs.com/package/express',
+    '- License: MIT',
+    '',
+    '## Documentation Sets',
+    '',
+    ...docsVersions.map(
+      (v) =>
+        `- [Guides (${`v${v.replace('x', '')}`})](${new URL(`/llms/guides-${v}.txt`, siteUrl).href}): Getting started, routing, middleware, error handling, debugging, and advanced topics for Express ${`v${v.replace('x', '')}`}`
+    ),
+    ...apiVersions.map(
+      (v) =>
+        `- [API Reference (${`v${v.replace('x', '')}`})](${new URL(`/llms/api-${v}.txt`, siteUrl).href}): Complete API documentation for Express ${`v${v.replace('x', '')}`}`
+    ),
+    `- [Official Middleware](${new URL('/llms/middleware.txt', siteUrl).href}): Documentation for middleware modules maintained by the Express.js team`,
+    `- [Resources](${new URL('/llms/resources.txt', siteUrl).href}): Community resources, tools, and utilities for Express.js`,
+    `- [Full Documentation](${new URL('/llms/full.txt', siteUrl).href}): All content in a single file`,
+    '',
+    '## Notes',
+    '',
+    '- All content is sourced from the official Express.js documentation at https://expressjs.com',
+    '- Documentation is maintained by the Express.js team',
+  ];
+
+  return new Response(lines.join('\n'), {
+    headers: { 'Content-Type': 'text/plain; charset=utf-8' },
+  });
+};
diff --git a/src/pages/llms/api-[version].txt.ts b/src/pages/llms/api-[version].txt.ts
new file mode 100644
index 0000000000..1374ad7baa
--- /dev/null
+++ b/src/pages/llms/api-[version].txt.ts
@@ -0,0 +1,31 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+import { getRawMarkdown, buildSection, textResponse } from '@/utils/llms';
+
+export async function getStaticPaths() {
+  const api = await getCollection('api');
+  const versions = [...new Set(api.map((d) => d.id.split('/')[0]))];
+  return versions.map((version) => ({ params: { version } }));
+}
+
+export const GET: APIRoute = async ({ params, site }) => {
+  const siteUrl = site as URL;
+  const version = params.version as string;
+  const label = `v${version.replace('x', '')}`;
+
+  const api = await getCollection('api');
+  const apiDocs = api.filter((d) => d.id.startsWith(`${version}/`));
+
+  const sections: string[] = [`# Express.js — API Reference (${label})\n`];
+  sections.push('> Fast, unopinionated, minimalist web framework for Node.js\n');
+
+  for (const entry of apiDocs) {
+    const url = new URL(`/en/${entry.id}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  return textResponse(sections.join('\n'));
+};
diff --git a/src/pages/llms/full.txt.ts b/src/pages/llms/full.txt.ts
new file mode 100644
index 0000000000..f6cc35bfe0
--- /dev/null
+++ b/src/pages/llms/full.txt.ts
@@ -0,0 +1,50 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+import { getRawMarkdown, buildSection, textResponse } from '@/utils/llms';
+
+export const GET: APIRoute = async ({ site }) => {
+  const siteUrl = site as URL;
+
+  const docs = await getCollection('docs');
+  const api = await getCollection('api');
+  const pages = await getCollection('pages');
+
+  // Filter to English 5x content
+  const enDocs = docs.filter((d) => d.id.startsWith('en/5x/'));
+  const apiDocs = api.filter((d) => d.id.startsWith('5x/'));
+  const enPages = pages.filter((d) => d.id.startsWith('en/'));
+
+  const sections: string[] = ['# Express.js — Full Documentation\n'];
+  sections.push('> Fast, unopinionated, minimalist web framework for Node.js\n');
+
+  // Process docs
+  for (const entry of enDocs) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  // Process API docs
+  for (const entry of apiDocs) {
+    const url = new URL(`/en/${entry.id}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  // Process pages
+  for (const entry of enPages) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  return textResponse(sections.join('\n'));
+};
diff --git a/src/pages/llms/guides-[version].txt.ts b/src/pages/llms/guides-[version].txt.ts
new file mode 100644
index 0000000000..8744c5dcff
--- /dev/null
+++ b/src/pages/llms/guides-[version].txt.ts
@@ -0,0 +1,47 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+import { getRawMarkdown, buildSection, textResponse } from '@/utils/llms';
+
+export async function getStaticPaths() {
+  const docs = await getCollection('docs');
+  const versions = [...new Set(docs.map((d) => d.id.replace('en/', '').split('/')[0]))];
+  return versions.map((version) => ({ params: { version } }));
+}
+
+export const GET: APIRoute = async ({ params, site }) => {
+  const siteUrl = site as URL;
+  const version = params.version as string;
+  const label = `v${version.replace('x', '')}`;
+
+  const docs = await getCollection('docs');
+  const pages = await getCollection('pages');
+
+  const enDocs = docs.filter((d) => d.id.startsWith(`en/${version}/`));
+
+  // Migration and advanced pages from pages collection (not versioned)
+  const migrations = pages.filter((d) => d.id.startsWith('en/guide/migrating'));
+  const advancedPages = pages.filter((d) => d.id.startsWith('en/advanced/'));
+
+  const sections: string[] = [`# Express.js — Guides (${label})\n`];
+  sections.push('> Fast, unopinionated, minimalist web framework for Node.js\n');
+
+  for (const entry of enDocs) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  for (const entry of [...migrations, ...advancedPages]) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  return textResponse(sections.join('\n'));
+};
diff --git a/src/pages/llms/middleware.txt.ts b/src/pages/llms/middleware.txt.ts
new file mode 100644
index 0000000000..cbce3838c4
--- /dev/null
+++ b/src/pages/llms/middleware.txt.ts
@@ -0,0 +1,24 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+import { getRawMarkdown, buildSection, textResponse } from '@/utils/llms';
+
+export const GET: APIRoute = async ({ site }) => {
+  const siteUrl = site as URL;
+
+  const pages = await getCollection('pages');
+  const middleware = pages.filter((d) => d.id.startsWith('en/resources/middleware/'));
+
+  const sections: string[] = ['# Express.js — Official Middleware\n'];
+  sections.push('> Official middleware modules maintained by the Express.js team.\n');
+
+  for (const entry of middleware) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  return textResponse(sections.join('\n'));
+};
diff --git a/src/pages/llms/resources.txt.ts b/src/pages/llms/resources.txt.ts
new file mode 100644
index 0000000000..a231a4675b
--- /dev/null
+++ b/src/pages/llms/resources.txt.ts
@@ -0,0 +1,26 @@
+import type { APIRoute } from 'astro';
+import { getCollection } from 'astro:content';
+import { getRawMarkdown, buildSection, textResponse } from '@/utils/llms';
+
+export const GET: APIRoute = async ({ site }) => {
+  const siteUrl = site as URL;
+
+  const pages = await getCollection('pages');
+  const resources = pages.filter(
+    (d) => d.id.startsWith('en/resources/') && !d.id.includes('/middleware/')
+  );
+
+  const sections: string[] = ['# Express.js — Resources\n'];
+  sections.push('> Community resources, tools, and utilities for Express.js.\n');
+
+  for (const entry of resources) {
+    const slug = entry.id.replace('en/', '');
+    const url = new URL(`/en/${slug}`, siteUrl).href;
+    const content = await getRawMarkdown(entry);
+    if (content) {
+      sections.push(buildSection(entry.data.title, url, content));
+    }
+  }
+
+  return textResponse(sections.join('\n'));
+};
diff --git a/src/pages/og/[...id].ts b/src/pages/og/[...id].ts
new file mode 100644
index 0000000000..85fab5020d
--- /dev/null
+++ b/src/pages/og/[...id].ts
@@ -0,0 +1,175 @@
+import fs from 'fs/promises';
+import { join } from 'path';
+import satori from 'satori';
+import sharp from 'sharp';
+import type { APIRoute, GetStaticPaths } from 'astro';
+import { getCollection } from 'astro:content';
+import { languages } from '@/i18n/locales';
+import { useTranslations } from '@/i18n/utils';
+
+const COLORS = {
+  text: '#fafafa',
+  edge: '#0A0A0A',
+  center: '#1a1a1a',
+  accent: '#525252',
+};
+
+const TAG_COLORS: Record<string, string> = {
+  security: '#261408',
+};
+
+function getCenterColor(tags?: string[]): string {
+  if (!tags?.length) return COLORS.center;
+  for (const tag of tags) {
+    const color = TAG_COLORS[tag.toLowerCase()];
+    if (color) return color;
+  }
+  return COLORS.center;
+}
+
+export const getStaticPaths: GetStaticPaths = async () => {
+  const [blog, docs, api, pages] = await Promise.all([
+    getCollection('blog'),
+    getCollection('docs'),
+    getCollection('api'),
+    getCollection('pages'),
+  ]);
+
+  const blogListingPath = {
+    params: { id: 'blog.png' },
+    props: { title: 'Express Blog' },
+  };
+
+  const blogPaths = blog.map((post) => ({
+    params: { id: `blog-${post.id.split('/').pop()!}.png` },
+    props: { title: post.data.title, tags: post.data.tags },
+  }));
+
+  const docsPagesPaths = [...docs, ...pages].map((entry) => ({
+    params: { id: `${entry.id.replace(/\//g, '-')}.png` },
+    props: { title: entry.data.title },
+  }));
+
+  const apiPaths = api.map((entry) => ({
+    params: { id: `${entry.id.replace(/\//g, '-')}.png` },
+    props: { title: entry.data.title },
+  }));
+
+  const homePaths = Object.keys(languages).map((lang) => {
+    const t = useTranslations(lang as keyof typeof languages);
+    return {
+      params: { id: `home-${lang}.png` },
+      props: { title: t('hero.tagline') },
+    };
+  });
+
+  return [...homePaths, blogListingPath, ...blogPaths, ...docsPagesPaths, ...apiPaths];
+};
+
+export const GET: APIRoute = async ({ props }) => {
+  const { title, tags } = props as { title: string; tags?: string[] };
+  const centerColor = getCenterColor(tags);
+
+  const publicDir = join(process.cwd(), 'public');
+  const interBold = await fs.readFile(join(publicDir, 'fonts', 'inter-bold.woff'));
+
+  const logoSvg = await fs.readFile(
+    join(publicDir, 'images', 'logos', 'logo-express-white.svg'),
+    'utf-8'
+  );
+  const logoBase64 = `data:image/svg+xml;base64,${Buffer.from(logoSvg).toString('base64')}`;
+
+  const displayTitle = title.length > 80 ? title.slice(0, 80) + '...' : title;
+
+  const element = {
+    type: 'div',
+    props: {
+      style: {
+        display: 'flex',
+        width: '100%',
+        height: '100%',
+        background: `linear-gradient(135deg, ${COLORS.edge} 0%, ${centerColor} 50%, ${COLORS.edge} 100%)`,
+        color: COLORS.text,
+        fontFamily: 'Inter',
+        padding: '60px 70px',
+        flexDirection: 'column',
+        justifyContent: 'space-between',
+      },
+      children: [
+        {
+          type: 'img',
+          props: {
+            src: logoBase64,
+            width: 240,
+            height: 64,
+          },
+        },
+        {
+          type: 'div',
+          props: {
+            style: {
+              display: 'flex',
+              flexDirection: 'column',
+              gap: '20px',
+            },
+            children: [
+              {
+                type: 'div',
+                props: {
+                  style: {
+                    display: 'flex',
+                    fontSize: '56px',
+                    fontWeight: 700,
+                    lineHeight: 1.2,
+                    letterSpacing: '-0.03em',
+                    maxWidth: '900px',
+                  },
+                  children: displayTitle,
+                },
+              },
+              {
+                type: 'div',
+                props: {
+                  style: {
+                    width: '80px',
+                    height: '4px',
+                    backgroundColor: COLORS.accent,
+                    borderRadius: '2px',
+                  },
+                  children: '',
+                },
+              },
+            ],
+          },
+        },
+      ],
+    },
+  };
+
+  // eslint-disable-next-line @typescript-eslint/no-explicit-any
+  const svg = await satori(element as any, {
+    width: 1200,
+    height: 630,
+    fonts: [
+      {
+        data: interBold,
+        name: 'Inter',
+        weight: 700,
+        style: 'normal',
+      },
+    ],
+  });
+
+  const pngBuffer = await sharp(Buffer.from(svg))
+    .resize({ width: 1200, height: 630 })
+    .png()
+    .toBuffer();
+
+  return new Response(pngBuffer as BodyInit, {
+    headers: {
+      'Content-Type': 'image/png',
+      'Content-Length': pngBuffer.length.toString(),
+      'Cache-Control': 'public, max-age=2592000, immutable',
+    },
+  });
+};
diff --git a/src/pages/robots.txt.ts b/src/pages/robots.txt.ts
new file mode 100644
index 0000000000..9c3032c062
--- /dev/null
+++ b/src/pages/robots.txt.ts
@@ -0,0 +1,23 @@
+import type { APIRoute } from 'astro';
+
+const getRobotsTxt = (sitemapURL: URL) => `\
+User-agent: *
+Allow: /
+
+Sitemap: ${sitemapURL.href}
+`;
+
+const getBlockedRobotsTxt = () => `\
+User-agent: *
+Disallow: /
+`;
+
+export const GET: APIRoute = ({ site }) => {
+  // Netlify builds should not be indexed.
+  if (import.meta.env.DEPLOY_PRIME_URL) {
+    return new Response(getBlockedRobotsTxt());
+  }
+
+  const sitemapURL = new URL('sitemap-index.xml', site);
+  return new Response(getRobotsTxt(sitemapURL));
+};
diff --git a/src/pages/vulnerabilities.xml.ts b/src/pages/vulnerabilities.xml.ts
new file mode 100644
index 0000000000..4a568c9aa7
--- /dev/null
+++ b/src/pages/vulnerabilities.xml.ts
@@ -0,0 +1,35 @@
+import rss from '@astrojs/rss';
+import { getCollection } from 'astro:content';
+import type { APIRoute } from 'astro';
+import {
+  getLinkedTitleContent,
+  getAuthorsCustomData,
+  getPubDateFromId,
+  shouldIncludeInFeed,
+  sortByIdDateDesc,
+} from '@/utils/rss';
+
+export const GET: APIRoute = async (context) => {
+  const site = context.site as URL;
+  const blog = await getCollection('blog');
+  const securityPosts = sortByIdDateDesc(
+    blog.filter(
+      (post) => shouldIncludeInFeed(post.id) && (post.data.tags ?? []).includes('security')
+    )
+  );
+
+  return rss({
+    title: 'Express.js Security Feed',
+    description: 'Posts tagged as security from the Express.js blog.',
+    site: site.href,
+    items: securityPosts.map((post) => ({
+      link: `/blog/${post.id}/`,
+      title: post.data.title,
+      pubDate: getPubDateFromId(post.id),
+      description: post.data.description,
+      content: getLinkedTitleContent(post.data.title, post.id, site),
+      categories: post.data.tags,
+      customData: getAuthorsCustomData(post.data.authors),
+    })),
+  });
+};
diff --git a/src/plugins/rehype-accessible-tables.mjs b/src/plugins/rehype-accessible-tables.mjs
new file mode 100644
index 0000000000..672679b5dd
--- /dev/null
+++ b/src/plugins/rehype-accessible-tables.mjs
@@ -0,0 +1,72 @@
+import { visit, SKIP } from 'unist-util-visit';
+
+/**
+ * Rehype plugin that makes tables responsive and accessible:
+ * - Wraps each <table> in a <div class="table-scroller"> for horizontal scroll on small viewports
+ * - Adds scope="col" to <th> inside <thead>
+ * - Adds scope="row" to <th> inside <tbody>
+ */
+export function rehypeAccessibleTables() {
+  return (tree) => {
+    // Add scope="col" to th elements inside thead
+    visit(tree, 'element', (node) => {
+      if (node.tagName !== 'thead') return;
+      visit(node, 'element', (th) => {
+        if (th.tagName === 'th' && !th.properties.scope) {
+          th.properties.scope = 'col';
+        }
+      });
+    });
+
+    // Add scope="row" to th elements inside tbody
+    visit(tree, 'element', (node) => {
+      if (node.tagName !== 'tbody') return;
+      visit(node, 'element', (th) => {
+        if (th.tagName === 'th' && !th.properties.scope) {
+          th.properties.scope = 'row';
+        }
+      });
+    });
+
+    // Wrap tables in a scrollable container
+    visit(tree, 'element', (node, index, parent) => {
+      if (node.tagName !== 'table') return;
+      if (!parent || index == null) return;
+
+      // Skip if already wrapped
+      if (parent.tagName === 'div' && parent.properties?.className?.includes('table-scroller'))
+        return;
+
+      const wrapper = {
+        type: 'element',
+        tagName: 'div',
+        properties: { className: ['table-scroller'] },
+        children: [node],
+      };
+
+      parent.children.splice(index, 1, wrapper);
+      // Skip the inserted wrapper so we don't revisit the table inside it
+      return [SKIP, index + 1];
+    });
+  };
+}
+
+/**
+ * Astro integration wrapper — registers rehypeAccessibleTables after
+ * astro-expressive-code has already added its own rehype plugin, so
+ * the two don't interfere with each other in the pipeline.
+ */
+export function accessibleTablesIntegration() {
+  return {
+    name: 'rehype-accessible-tables',
+    hooks: {
+      'astro:config:setup': ({ updateConfig }) => {
+        updateConfig({
+          markdown: {
+            rehypePlugins: [rehypeAccessibleTables],
+          },
+        });
+      },
+    },
+  };
+}
diff --git a/src/styles/base/_expressive-code.css b/src/styles/base/_expressive-code.css
new file mode 100644
index 0000000000..d389dbce52
--- /dev/null
+++ b/src/styles/base/_expressive-code.css
@@ -0,0 +1,31 @@
+/**
+ * Expressive Code Global Styles
+ *
+ * Applied to all expressive-code blocks across the app
+ * Using higher specificity selectors to override expressive-code defaults
+ */
+
+/* Increase specificity by doubling the class selector */
+.expressive-code.expressive-code {
+  margin: var(--space-6) 0;
+
+  .copy {
+    top: var(--space-3);
+    right: var(--space-3);
+    height: var(--size-5);
+
+    button {
+      width: var(--size-6);
+      height: var(--size-6);
+    }
+  }
+
+  figcaption:not(:empty) ~ .copy {
+    top: var(--space-10);
+  }
+}
+
+.expressive-code.expressive-code .feedback {
+  line-height: var(--line-height-snug);
+  font-family: var(--font-family-body);
+}
diff --git a/src/styles/base/_fonts.css b/src/styles/base/_fonts.css
new file mode 100644
index 0000000000..1101ee226c
--- /dev/null
+++ b/src/styles/base/_fonts.css
@@ -0,0 +1,24 @@
+/**
+ * Font Face Declarations
+ *
+ * Self-hosted JetBrains Mono for code blocks.
+ * Currently only Light (300) weight is used across the site.
+ * Using font-display: swap for better performance.
+ */
+
+/* JetBrains Mono - Light */
+@font-face {
+  font-family: 'JetBrains Mono';
+  src: url('/fonts/JetBrainsMono-Light.woff2') format('woff2');
+  font-weight: 300;
+  font-style: normal;
+  font-display: swap;
+}
+
+@font-face {
+  font-family: 'JetBrains Mono';
+  src: url('/fonts/JetBrainsMono-LightItalic.woff2') format('woff2');
+  font-weight: 300;
+  font-style: italic;
+  font-display: swap;
+}
diff --git a/src/styles/base/_global.css b/src/styles/base/_global.css
new file mode 100644
index 0000000000..a4653def88
--- /dev/null
+++ b/src/styles/base/_global.css
@@ -0,0 +1,303 @@
+/**
+ * Global Base Styles (layer: base)
+ *
+ * Applies design tokens to base HTML elements
+ */
+
+html {
+  font-family: var(--font-family-body);
+  font-size: 62.5%;
+  color: var(--color-text-primary);
+  background-color: var(--color-bg-primary);
+  scroll-behavior: smooth;
+  -moz-text-size-adjust: none;
+  -webkit-text-size-adjust: none;
+  text-size-adjust: none;
+  box-sizing: border-box;
+
+  *,
+  *:before,
+  *:after {
+    box-sizing: inherit;
+  }
+}
+
+body {
+  font-family: var(--font-family-body);
+  font-size: var(--font-size-body);
+  line-height: var(--line-height-body);
+  background-color: var(--color-bg-primary);
+  text-rendering: optimizeLegibility;
+}
+
+/* Headings */
+h1,
+.h1,
+h2,
+.h2,
+h3,
+.h3,
+h4,
+.h4,
+h5,
+.h5,
+h6,
+.h6 {
+  font-weight: var(--font-weight-medium);
+  line-height: var(--line-height-tight);
+  letter-spacing: var(--letter-spacing-tight);
+  margin: 0;
+}
+
+h1,
+.h1 {
+  font-size: var(--font-size-h1);
+  margin: 0;
+}
+
+h2 {
+  font-size: var(--font-size-h2-docs);
+  margin: var(--space-h2) 0;
+}
+
+.h2 {
+  font-size: var(--font-size-h2);
+  margin: var(--space-h2) 0;
+}
+
+h3,
+.h3 {
+  font-size: var(--font-size-h3);
+  margin: var(--space-h3) 0;
+}
+
+h4,
+.h4 {
+  font-size: var(--font-size-h4);
+  margin: var(--space-h4) 0;
+}
+
+h5,
+.h5 {
+  font-size: var(--font-size-base);
+  font-weight: var(--font-weight-semibold);
+  line-height: var(--line-height-relaxed);
+  margin: var(--space-body) 0;
+}
+
+h6,
+.h6 {
+  font-size: var(--font-size-sm);
+  font-weight: var(--font-weight-semibold);
+  text-transform: uppercase;
+  letter-spacing: var(--letter-spacing-wide);
+  margin: var(--space-body) 0;
+}
+
+p,
+.body {
+  font-family: var(--font-family-body);
+  font-size: var(--font-size-body);
+  font-weight: var(--font-weight-normal);
+  line-height: var(--line-height-body);
+  letter-spacing: var(--letter-spacing-body);
+  margin: var(--space-body) 0;
+}
+
+span,
+.body-md {
+  font-family: var(--font-family-body);
+  font-weight: var(--font-weight-normal);
+  line-height: var(--line-height-normal);
+}
+
+.body-md {
+  margin: var(--space-body) 0;
+  font-size: var(--font-size-sm);
+}
+
+small,
+.body-sm {
+  font-family: var(--font-family-body);
+  font-weight: var(--font-weight-normal);
+  line-height: var(--line-height-normal);
+  margin: var(--space-body) 0;
+}
+
+.body-sm {
+  font-size: var(--font-size-xs);
+}
+
+.body-xs {
+  font-family: var(--font-family-body);
+  font-size: var(--font-size-xxs);
+  font-weight: var(--font-weight-normal);
+  line-height: var(--line-height-normal);
+  margin: var(--space-body) 0;
+}
+
+/* Heading links (rehype-autolink-headings) */
+h1 > a,
+h2 > a,
+h3 > a,
+h4 > a,
+h5 > a,
+h6 > a {
+  color: inherit;
+  text-decoration: none;
+
+  &:hover {
+    color: inherit;
+    text-decoration: underline;
+  }
+}
+
+/* Links */
+a {
+  color: var(--color-link);
+  text-decoration: underline;
+  text-underline-offset: 0.15em;
+  transition: var(--transition-colors);
+  overflow-wrap: break-word;
+}
+
+a:hover {
+  color: var(--color-link-hover);
+}
+
+a:focus-visible,
+button:focus-visible,
+input:focus-visible,
+select:focus-visible,
+textarea:focus-visible,
+[tabindex]:focus-visible {
+  outline: 1px solid var(--color-focus-ring);
+  outline-offset: -2px;
+}
+
+/* Code */
+code,
+kbd,
+samp,
+pre {
+  font-family: var(--font-family-code);
+  font-size: var(--font-size-code);
+
+  *,
+  *:before,
+  *:after {
+    font-family: inherit;
+  }
+}
+
+code,
+.code {
+  font-family: var(--font-family-code);
+  font-size: var(--font-size-code);
+  font-weight: var(--font-weight-normal);
+  line-height: var(--line-height-snug);
+  background-color: var(--color-bg-tertiary);
+  padding: var(--space-0-5) var(--space-1);
+  border-radius: var(--radius-base);
+  letter-spacing: var(--letter-spacing-normal);
+}
+
+pre {
+  padding: var(--space-4);
+  background-color: var(--color-pre-bg);
+  color: var(--color-pre-fg);
+  border-radius: var(--radius-lg);
+  overflow-x: auto;
+}
+
+pre code {
+  padding: 0;
+  background: none;
+  border-radius: 0;
+}
+
+/* Blockquote */
+blockquote {
+  padding: var(--space-4) var(--space-6);
+  border-left: var(--border-width-4) solid var(--color-border-primary);
+  background-color: var(--color-bg-secondary);
+  font-style: italic;
+  margin: var(--space-4) 0;
+}
+
+/* Horizontal rule */
+hr {
+  border: none;
+  border-top: var(--border-width-1) solid var(--color-border-primary);
+  margin: var(--space-8) 0;
+}
+
+/* Tables */
+.table-scroller {
+  overflow-x: auto;
+  -webkit-overflow-scrolling: touch;
+  margin: var(--space-body) 0;
+}
+
+.table-scroller table {
+  margin: 0;
+}
+
+table {
+  width: 100%;
+  border-collapse: collapse;
+  margin: var(--space-body) 0;
+}
+
+th,
+td {
+  padding: var(--space-3) var(--space-4);
+  text-align: left;
+  border-bottom: var(--border-width-1) solid var(--color-border-primary);
+}
+
+th {
+  font-weight: var(--font-weight-semibold);
+}
+
+/* Lists */
+ul,
+ol {
+  margin: var(--space-body) 0;
+  padding-left: var(--space-6);
+}
+
+:is(ul, ol) :is(ul, ol) {
+  margin: var(--space-1) 0;
+}
+
+ul {
+  list-style-type: disc;
+}
+
+ol {
+  list-style-type: decimal;
+}
+
+main {
+  flex-grow: 1;
+  padding-bottom: var(--space-16);
+
+  @media (--md-up) {
+    padding-top: var(--space-16);
+    padding-bottom: var(--space-32);
+  }
+}
+
+@media (--md-up) {
+  .layout-wrapper {
+    background-color: var(--color-bg-secondary);
+  }
+  .layout-content {
+    background-color: var(--color-bg-primary);
+  }
+}
+
+.layout-content {
+  min-width: 0;
+}
diff --git a/src/styles/base/_reset.css b/src/styles/base/_reset.css
new file mode 100644
index 0000000000..c1aa7864cf
--- /dev/null
+++ b/src/styles/base/_reset.css
@@ -0,0 +1,90 @@
+/**
+ * CSS Reset (layer: reset)
+ *
+ * Modern CSS reset based on Josh Comeau's reset
+ * https://www.joshwcomeau.com/css/custom-css-reset/
+ */
+
+/* Box sizing rules */
+*,
+*::before,
+*::after {
+  box-sizing: border-box;
+}
+
+/* Remove default margin and padding */
+* {
+  margin: 0;
+  padding: 0;
+}
+
+/* Set core body defaults */
+body {
+  min-height: 100vh;
+  -webkit-font-smoothing: antialiased;
+}
+
+/* Remove list styles on ul, ol elements with a list role */
+ul[role='list'],
+ol[role='list'] {
+  list-style: none;
+}
+
+/* Set shorter line heights on interactive elements */
+button,
+input,
+label {
+  line-height: 1.1;
+}
+
+/* Balance text wrapping on headings */
+h1,
+h2,
+h3,
+h4,
+h5,
+h6 {
+  text-wrap: balance;
+}
+
+/* Prevent orphans in long-form text */
+p,
+li,
+blockquote,
+figcaption {
+  text-wrap: pretty;
+}
+
+/* Better text decoration rendering */
+a {
+  text-decoration-skip-ink: auto;
+}
+
+/* Make images easier to work with */
+img,
+picture,
+video,
+canvas,
+svg {
+  display: block;
+  max-width: 100%;
+}
+
+/* Inherit fonts for inputs and buttons */
+input,
+button,
+textarea,
+select {
+  font: inherit;
+  color: inherit;
+}
+
+/* Make sure textareas without a rows attribute are not tiny */
+textarea:not([rows]) {
+  min-height: 10em;
+}
+
+/* Anything that has been anchored to should have extra scroll margin */
+:target {
+  scroll-margin-block: 5ex;
+}
diff --git a/src/styles/main.css b/src/styles/main.css
new file mode 100644
index 0000000000..ad16559b4c
--- /dev/null
+++ b/src/styles/main.css
@@ -0,0 +1,26 @@
+/**
+ * Main Stylesheet
+ *
+ * Entry point for all styles
+ * Import this file in your layout
+ *
+ * CSS Cascade Layers order (lowest to highest priority):
+ * 1. base       - Global styles (reset, fonts, global, utilities)
+ * 2. primitives - Primitive component styles
+ * 3. patterns   - Pattern component styles
+ *
+ * Layer order is defined in Layout.astro <head>
+ * Layers ensure correct specificity order regardless of bundle order
+ */
+
+/* Design Tokens - CSS custom properties (OUTSIDE layers for global access) */
+@import './tokens/index.css';
+
+/* Import base styles into the base layer */
+@import './base/_reset.css' layer(base);
+@import './base/_fonts.css' layer(base);
+@import './base/_global.css' layer(base);
+@import './utilities/_utilities.css' layer(base);
+
+/* Import expressive-code customizations OUTSIDE layers for highest priority */
+@import './base/_expressive-code.css';
diff --git a/src/styles/tokens/_borders.css b/src/styles/tokens/_borders.css
new file mode 100644
index 0000000000..80ea81603e
--- /dev/null
+++ b/src/styles/tokens/_borders.css
@@ -0,0 +1,31 @@
+/**
+ * Border Tokens
+ *
+ * Border widths and radius
+ */
+
+:root {
+  /* Border Widths */
+  --border-width-0: 0px;
+  --border-width-1: 1px;
+  --border-width-2: 2px;
+  --border-width-4: 4px;
+  --border-width-8: 8px;
+
+  /* Border Radius */
+  --radius-none: 0;
+  --radius-sm: 0.2rem; /* 2px */
+  --radius-base: 0.4rem; /* 4px */
+  --radius-md: 0.6rem; /* 6px */
+  --radius-lg: 0.8rem; /* 8px */
+  --radius-xl: 1.2rem; /* 12px */
+  --radius-2xl: 1.6rem; /* 16px */
+  --radius-3xl: 2.4rem; /* 24px */
+  --radius-full: 9999px;
+
+  /* Semantic */
+  --radius-button: var(--radius-md);
+  --radius-input: var(--radius-md);
+  --radius-card: var(--radius-lg);
+  --radius-badge: var(--radius-full);
+}
diff --git a/src/styles/tokens/_breakpoints.css b/src/styles/tokens/_breakpoints.css
new file mode 100644
index 0000000000..21bcc232a8
--- /dev/null
+++ b/src/styles/tokens/_breakpoints.css
@@ -0,0 +1,46 @@
+/**
+ * Breakpoint Tokens
+ *
+ * Design breakpoints:
+ * - Mobile:  < 768px
+ * - Tablet:  768px - 1439px
+ * - Desktop: >= 1440px
+ *
+ * Usage:
+ * @media (--xs-only)  { ... }  - Mobile only
+ * @media (--md-only)  { ... }  - Tablet only
+ * @media (--md-up) { ... } - Above Tablet
+ * @media (--lg-up) { ... } - Above Desktop
+ * @media (--lg-down) { ... } - Below Desktop
+ */
+
+/* ============================================
+   CUSTOM MEDIA QUERIES
+   ============================================ */
+
+/* Device-specific (exclusive) */
+@custom-media --xs-only (width < 768px);
+@custom-media --md-up (width >= 768px);
+@custom-media --md-only (768px <= width < 1440px);
+@custom-media --lg-up (width >= 1440px);
+@custom-media --lg-down (width < 1440px);
+
+/* Range queries (inclusive) */
+
+/* ============================================
+   BREAKPOINT VALUES (for JavaScript)
+
+   Note: CSS custom properties cannot be used in
+   @media or @custom-media queries. These are exposed
+   for documentation (to have a human-readable reference) and
+   for JavaScript access via getComputedStyle().
+
+   Example:
+   const bp = getComputedStyle(document.documentElement)
+     .getPropertyValue('--breakpoint-md');
+   ============================================ */
+
+:root {
+  --breakpoint-md: 768px;
+  --breakpoint-lg: 1440px;
+}
diff --git a/src/styles/tokens/_colors.css b/src/styles/tokens/_colors.css
new file mode 100644
index 0000000000..afd5e30c8f
--- /dev/null
+++ b/src/styles/tokens/_colors.css
@@ -0,0 +1,160 @@
+:root {
+  /**
+   * Theme behavior:
+   * - Default: follows system preference (prefers-color-scheme)
+   * - Override: user can set [data-theme="light|dark"] on <html>
+   */
+  color-scheme: light dark;
+
+  /* ============================================
+     PRIMITIVE TOKENS
+     ============================================ */
+
+  --white: oklch(100% 0 0); /* #FFFFFF */
+  --black: oklch(0% 0 0); /* #000000 */
+
+  --gray-50: oklch(98% 0 0); /* #FAFAFA */
+  --gray-100: oklch(97% 0 0); /* #F6F6F6 */
+  --gray-150: oklch(94% 0 0); /* #EEEEEE */
+  --gray-200: oklch(92% 0 0); /* #E5E5E5 */
+  --gray-300: oklch(87% 0 0); /* #D4D4D4 */
+  --gray-400: oklch(70% 0 0); /* #A3A3A3 */
+  --gray-500: oklch(55% 0 0); /* #737373 */
+  --gray-550: oklch(50% 0 0); /* #626262 */
+  --gray-600: oklch(45% 0 0); /* #525252 */
+  --gray-700: oklch(35% 0 0); /* #404040 */
+  --gray-800: oklch(25% 0 0); /* #262626 */
+  --gray-900: oklch(19% 0 1); /* #141414 */
+  --gray-950: oklch(13% 0 0); /* #0A0A0A */
+
+  /* Green */
+  --green-50: oklch(97% 0.02 155); /* #F0FDF4 */
+  --green-100: oklch(94% 0.04 155); /* #DCFCE7 */
+  --green-200: oklch(89% 0.08 155); /* #BBF7D0 */
+  --green-300: oklch(81% 0.13 155); /* #86EFAC */
+  --green-400: oklch(70% 0.17 155); /* #4ADE80 */
+  --green-500: oklch(62% 0.19 155); /* #22C55E */
+  --green-600: oklch(53% 0.17 155); /* #16A34A */
+  --green-700: oklch(46% 0.14 155); /* #15803D */
+  --green-800: oklch(39% 0.11 155); /* #166534 */
+  --green-900: oklch(34% 0.09 155); /* #14532D */
+  --green-950: oklch(20% 0.06 155); /* #052E16 */
+
+  /* Blue */
+  --blue-50: oklch(97% 0.01 250); /* #EFF6FF */
+  --blue-100: oklch(94% 0.03 250); /* #DBEAFE */
+  --blue-200: oklch(88% 0.06 250); /* #BFDBFE */
+  --blue-300: oklch(79% 0.11 250); /* #93C5FD */
+  --blue-400: oklch(69% 0.15 250); /* #60A5FA */
+  --blue-500: oklch(60% 0.18 250); /* #3B82F6 */
+  --blue-600: oklch(53% 0.2 250); /* #2563EB */
+  --blue-700: oklch(47% 0.19 250); /* #1D4ED8 */
+  --blue-800: oklch(41% 0.16 250); /* #1E40AF */
+  --blue-900: oklch(37% 0.13 250); /* #1E3A8A */
+  --blue-950: oklch(26% 0.1 250); /* #172554 */
+  --blue-975: oklch(18% 0.06 250);
+
+  --sky-500: oklch(71% 0.16 237); /* #0EA5E9 */
+  --sky-700: oklch(48% 0.22 237); /* #0369A1 */
+
+  /* Amber */
+  --amber-50: oklch(98% 0.03 85); /* #FFFBEB */
+  --amber-100: oklch(94% 0.07 85); /* #FEF3C7 */
+  --amber-200: oklch(89% 0.12 85); /* #FDE68A */
+  --amber-300: oklch(83% 0.16 80); /* #FCD34D */
+  --amber-400: oklch(78% 0.17 70); /* #FBBF24 */
+  --amber-500: oklch(73% 0.17 60); /* #F59E0B */
+  --amber-600: oklch(64% 0.17 50); /* #D97706 */
+  --amber-700: oklch(53% 0.15 50); /* #B45309 */
+  --amber-800: oklch(45% 0.12 50); /* #92400E */
+  --amber-900: oklch(39% 0.1 50); /* #78350F */
+  --amber-950: oklch(25% 0.07 50); /* #451A03 */
+
+  /* Red */
+  --red-50: oklch(97% 0.01 25); /* #FEF2F2 */
+  --red-100: oklch(94% 0.03 25); /* #FEE2E2 */
+  --red-200: oklch(89% 0.06 25); /* #FECACA */
+  --red-300: oklch(81% 0.11 25); /* #FCA5A5 */
+  --red-400: oklch(70% 0.17 25); /* #F87171 */
+  --red-500: oklch(62% 0.21 25); /* #EF4444 */
+  --red-600: oklch(54% 0.22 25); /* #DC2626 */
+  --red-700: oklch(47% 0.19 25); /* #B91C1C */
+  --red-800: oklch(40% 0.16 25); /* #991B1B */
+  --red-900: oklch(36% 0.13 25); /* #7F1D1D */
+  --red-950: oklch(22% 0.09 25); /* #450A0A */
+
+  /* ============================================
+     SEMANTIC TOKENS
+     Using light-dark(light-value, dark-value)
+     ============================================ */
+
+  /* Backgrounds */
+  --color-bg-primary: light-dark(var(--white), var(--black));
+  --color-bg-secondary: light-dark(var(--gray-50), var(--gray-900));
+  --color-bg-tertiary: light-dark(var(--gray-150), var(--gray-800));
+  --color-bg-inverse: light-dark(var(--gray-900), var(--gray-100));
+  --color-bg-inverse-secondary: light-dark(var(--gray-800), var(--gray-200));
+  --color-bg-mute: light-dark(var(--gray-200), var(--gray-600));
+  --color-bg-info: light-dark(var(--blue-50), var(--blue-975));
+  --color-bg-success: light-dark(var(--green-50), var(--green-950));
+  --color-bg-warning: light-dark(var(--amber-50), var(--amber-950));
+  --color-bg-error: light-dark(var(--red-50), var(--red-950));
+
+  /* Borders */
+  --color-border-primary: light-dark(var(--gray-300), var(--gray-500));
+  --color-border-secondary: light-dark(var(--gray-200), var(--gray-800));
+  --color-border-tertiary: light-dark(var(--gray-400), var(--gray-400));
+  --color-border-mute: light-dark(var(--gray-300), var(--gray-700));
+  --color-border-inverse: light-dark(var(--gray-700), var(--gray-200));
+  --color-border-info: light-dark(var(--blue-200), var(--blue-950));
+  --color-border-success: light-dark(var(--green-200), var(--green-800));
+  --color-border-warning: light-dark(var(--amber-200), var(--amber-800));
+  --color-border-error: light-dark(var(--red-200), var(--red-800));
+
+  /* Text */
+  --color-text-primary: light-dark(var(--gray-900), var(--gray-100));
+  --color-text-secondary: light-dark(var(--gray-600), var(--gray-150));
+  --color-text-tertiary: var(--gray-500, var(--gray-550));
+  --color-text-inverse: light-dark(var(--gray-100), var(--gray-900));
+  --color-text-mute: var(--gray-500, var(--gray-550));
+  --color-text-info: light-dark(var(--blue-700), var(--blue-400));
+  --color-text-success: light-dark(var(--green-700), var(--green-400));
+  --color-text-warning: light-dark(var(--amber-700), var(--amber-400));
+  --color-text-error: light-dark(var(--red-700), var(--red-400));
+
+  /* Icons */
+  --color-icon-primary: light-dark(var(--gray-900), var(--gray-50));
+  --color-icon-secondary: light-dark(var(--gray-500), var(--gray-400));
+
+  /* ============================================
+     COMPONENT TOKENS
+     ============================================ */
+
+  /* Buttons */
+  --color-button-primary-bg: light-dark(var(--gray-900), var(--white));
+  --color-button-primary-text: light-dark(var(--white), var(--black));
+  --color-button-primary-bg-hover: light-dark(var(--gray-800), var(--gray-200));
+
+  /* Links */
+  --color-link: light-dark(var(--sky-500), var(--sky-500));
+  --color-link-hover: light-dark(var(--sky-500), var(--sky-700));
+  --color-link-visited: light-dark(var(--sky-700), var(--sky-700));
+  /* Focus */
+  --color-focus-ring: light-dark(var(--gray-900), var(--white));
+
+  /* Overlay */
+  --color-overlay: color-mix(in oklch, var(--color-bg-secondary) 90%, transparent);
+}
+
+/* ============================================
+   THEME OVERRIDES
+   Force specific theme via data attribute
+   ============================================ */
+
+[data-theme='light'] {
+  color-scheme: light;
+}
+
+[data-theme='dark'] {
+  color-scheme: dark;
+}
diff --git a/src/styles/tokens/_sizing.css b/src/styles/tokens/_sizing.css
new file mode 100644
index 0000000000..d0eaadb528
--- /dev/null
+++ b/src/styles/tokens/_sizing.css
@@ -0,0 +1,50 @@
+/**
+ * Sizing tokens
+ *
+ * Based on a 4px grid system (0.25rem)
+ * Used for width, height, max-width, max-height, etc.
+ */
+
+:root {
+  --size-0: 0;
+  --size-px: 1px;
+  --size-0-5: 0.2rem; /* 2px */
+  --size-1: 0.4rem; /* 4px */
+  --size-1-5: 0.6rem; /* 6px */
+  --size-2: 0.8rem; /* 8px */
+  --size-2-5: 1rem; /* 10px */
+  --size-3: 1.2rem; /* 12px */
+  --size-3-5: 1.4rem; /* 14px */
+  --size-4: 1.6rem; /* 16px */
+  --size-5: 2rem; /* 20px */
+  --size-6: 2.4rem; /* 24px */
+  --size-7: 2.8rem; /* 28px */
+  --size-8: 3.2rem; /* 32px */
+  --size-9: 3.6rem; /* 36px */
+  --size-10: 4rem; /* 40px */
+  --size-11: 4.4rem; /* 44px */
+  --size-12: 4.8rem; /* 48px */
+  --size-14: 5.6rem; /* 56px */
+  --size-16: 6.4rem; /* 64px */
+  --size-20: 8rem; /* 80px */
+  --size-24: 9.6rem; /* 96px */
+  --size-28: 11.2rem; /* 112px */
+  --size-32: 12.8rem; /* 128px */
+  --size-36: 14.4rem; /* 144px */
+  --size-40: 16rem; /* 160px */
+  --size-44: 17.6rem; /* 176px */
+  --size-48: 19.2rem; /* 192px */
+  --size-52: 20.8rem; /* 208px */
+  --size-56: 22.4rem; /* 224px */
+  --size-60: 24rem; /* 240px */
+  --size-64: 25.6rem; /* 256px */
+  --size-68: 27.2rem; /* 272px */
+  --size-72: 28.8rem; /* 288px */
+  --size-76: 30.4rem; /* 304px */
+  --size-80: 32rem; /* 320px */
+  --size-84: 33.6rem; /* 336px */
+  --size-88: 35.2rem; /* 352px */
+  --size-92: 36.8rem; /* 368px */
+  --size-96: 38.4rem; /* 384px */
+  --size-100: 40rem; /* 400px */
+}
diff --git a/src/styles/tokens/_spacing.css b/src/styles/tokens/_spacing.css
new file mode 100644
index 0000000000..af7f182579
--- /dev/null
+++ b/src/styles/tokens/_spacing.css
@@ -0,0 +1,49 @@
+/**
+ * Spacing Tokens
+ *
+ * Based on a 4px grid system (0.25rem)
+ * Used for margin, padding, gap, etc.
+ */
+
+:root {
+  --space-0: 0;
+  --space-px: 1px;
+  --space-0-5: 0.2rem; /* 2px */
+  --space-1: 0.4rem; /* 4px */
+  --space-1-5: 0.6rem; /* 6px */
+  --space-2: 0.8rem; /* 8px */
+  --space-2-5: 1rem; /* 10px */
+  --space-3: 1.2rem; /* 12px */
+  --space-3-5: 1.4rem; /* 14px */
+  --space-4: 1.6rem; /* 16px */
+  --space-5: 2rem; /* 20px */
+  --space-6: 2.4rem; /* 24px */
+  --space-7: 2.8rem; /* 28px */
+  --space-8: 3.2rem; /* 32px */
+  --space-9: 3.6rem; /* 36px */
+  --space-10: 4rem; /* 40px */
+  --space-11: 4.4rem; /* 44px */
+  --space-12: 4.8rem; /* 48px */
+  --space-14: 5.6rem; /* 56px */
+  --space-16: 6.4rem; /* 64px */
+  --space-18: 7.2rem; /* 72px */
+  --space-20: 8rem; /* 80px */
+  --space-24: 9.6rem; /* 96px */
+  --space-28: 11.2rem; /* 112px */
+  --space-32: 12.8rem; /* 128px */
+  --space-36: 14.4rem; /* 144px */
+  --space-40: 16rem; /* 160px */
+  --space-44: 17.6rem; /* 176px */
+  --space-48: 19.2rem; /* 192px */
+  --space-52: 20.8rem; /* 208px */
+  --space-56: 22.4rem; /* 224px */
+  --space-60: 24rem; /* 240px */
+  --space-64: 25.6rem; /* 256px */
+
+  /* Component specific */
+  --space-h1: var(--space-12);
+  --space-h2: var(--space-10);
+  --space-h3: var(--space-6);
+  --space-h4: var(--space-6);
+  --space-body: var(--space-5);
+}
diff --git a/src/styles/tokens/_transitions.css b/src/styles/tokens/_transitions.css
new file mode 100644
index 0000000000..41c7e739f8
--- /dev/null
+++ b/src/styles/tokens/_transitions.css
@@ -0,0 +1,47 @@
+/**
+ * Transition & Animation Tokens
+ */
+
+:root {
+  /* Durations */
+  --duration-75: 75ms;
+  --duration-100: 100ms;
+  --duration-150: 150ms;
+  --duration-200: 200ms;
+  --duration-300: 300ms;
+  --duration-500: 500ms;
+  --duration-700: 700ms;
+  --duration-1000: 1000ms;
+
+  /* Timing Functions */
+  --ease-linear: linear;
+  --ease-in: cubic-bezier(0.4, 0, 1, 1);
+  --ease-out: cubic-bezier(0, 0, 0.2, 1);
+  --ease-in-out: cubic-bezier(0.4, 0, 0.2, 1);
+
+  /* Semantic transitions */
+  --transition-fast: var(--duration-150) var(--ease-out);
+  --transition-base: var(--duration-200) var(--ease-out);
+  --transition-slow: var(--duration-300) var(--ease-out);
+
+  --transition-colors:
+    color var(--transition-fast), background-color var(--transition-fast),
+    border-color var(--transition-fast);
+  --transition-transform: transform var(--transition-base);
+  --transition-opacity: opacity var(--transition-base);
+  --transition-shadow: box-shadow var(--transition-base);
+}
+
+/* Respect reduced motion preference */
+@media (prefers-reduced-motion: reduce) {
+  :root {
+    --duration-75: 0ms;
+    --duration-100: 0ms;
+    --duration-150: 0ms;
+    --duration-200: 0ms;
+    --duration-300: 0ms;
+    --duration-500: 0ms;
+    --duration-700: 0ms;
+    --duration-1000: 0ms;
+  }
+}
diff --git a/src/styles/tokens/_typography.css b/src/styles/tokens/_typography.css
new file mode 100644
index 0000000000..bec6e99916
--- /dev/null
+++ b/src/styles/tokens/_typography.css
@@ -0,0 +1,85 @@
+/**
+ * Typography Tokens
+ *
+ * Primary font: Helvetica Neue
+ * Code font: JetBrains Mono
+ */
+
+:root {
+  /* Font Families */
+  --font-family-sans:
+    'Helvetica Neue', Helvetica, Arial, system-ui, -apple-system, BlinkMacSystemFont, sans-serif;
+  --font-family-mono:
+    'JetBrains Mono', ui-monospace, 'Cascadia Code', 'Source Code Pro', Menlo, Consolas, monospace;
+
+  /* Font Sizes - Scale using a 1.2 ratio (Minor Third) */
+  --font-size-xxs: 1rem;
+  --font-size-xs: 1.2rem;
+  --font-size-sm: 1.4rem;
+  --font-size-base: 1.6rem;
+  --font-size-lg: 1.8rem;
+  --font-size-xl: 2rem;
+  --font-size-2xl: 2.4rem;
+  --font-size-3xl: 3rem;
+  --font-size-4xl: 3.6rem;
+  --font-size-5xl: 4.5rem;
+  --font-size-6xl: 5.4rem;
+
+  /* Font Weights */
+  --font-weight-light: 300;
+  --font-weight-normal: 400;
+  --font-weight-medium: 500;
+  --font-weight-semibold: 600;
+  --font-weight-bold: 700;
+
+  /* Line Heights */
+  --line-height-none: 1;
+  --line-height-tight: 1.25;
+  --line-height-snug: 1.375;
+  --line-height-normal: 1.5;
+  --line-height-relaxed: 1.625;
+  --line-height-loose: 2;
+
+  /* Letter Spacing */
+  --letter-spacing-tighter: -0.05em;
+  --letter-spacing-tight: -0.025em;
+  --letter-spacing-normal: 0em;
+  --letter-spacing-wide: 0.025em;
+  --letter-spacing-wider: 0.05em;
+  --letter-spacing-widest: 0.1em;
+
+  /* Components tokens */
+  --font-family-body: var(--font-family-sans);
+  --font-size-body: var(--font-size-base);
+  --line-height-body: var(--line-height-normal);
+  --letter-spacing-body: var(--letter-spacing-tight);
+
+  --font-family-heading: var(--font-family-sans);
+  --font-weight-heading: var(--font-weight-bold);
+  --font-line-height-heading: var(--line-height-tight);
+
+  --font-size-h1: var(--font-size-4xl);
+  --font-size-h2: var(--font-size-2xl);
+  --font-size-h2-docs: var(--font-size-2xl);
+  --font-size-h3: var(--font-size-xl);
+  --font-size-h4: var(--font-size-lg);
+
+  --font-family-code: var(--font-family-mono);
+  --font-size-code: 0.9em;
+
+  @media (--md-only) {
+    --font-size-h1: var(--font-size-5xl);
+    --font-size-h2: var(--font-size-5xl);
+    --font-size-h2-docs: var(--font-size-3xl);
+    --font-size-h3: var(--font-size-2xl);
+    --font-size-h4: var(--font-size-lg);
+  }
+
+  @media (--lg-up) {
+    --font-size-h1: var(--font-size-6xl);
+    --font-size-h2: var(--font-size-5xl);
+    --font-size-h2-docs: var(--font-size-3xl);
+    --font-size-h3: var(--font-size-2xl);
+    --font-size-h4: var(--font-size-xl);
+  }
+}
diff --git a/src/styles/tokens/_zindex.css b/src/styles/tokens/_zindex.css
new file mode 100644
index 0000000000..8d543295e5
--- /dev/null
+++ b/src/styles/tokens/_zindex.css
@@ -0,0 +1,12 @@
+/**
+ * Z-Index Scale
+ * Values are ordered from lowest to highest.
+ * Each layer is spaced by 10 to allow for intermediate values if needed.
+ */
+
+:root {
+  --z-index-sidebar-backdrop: 10;
+  --z-index-header: 20;
+  --z-index-sidebar: 30;
+  --z-index-modal-overlay: 40;
+}
diff --git a/src/styles/tokens/index.css b/src/styles/tokens/index.css
new file mode 100644
index 0000000000..ab1b427a2e
--- /dev/null
+++ b/src/styles/tokens/index.css
@@ -0,0 +1,14 @@
+/**
+ * Design Tokens Index
+ *
+ * Import all token files
+ */
+
+@import './_breakpoints.css';
+@import './_colors.css';
+@import './_typography.css';
+@import './_spacing.css';
+@import './_sizing.css';
+@import './_zindex.css';
+@import './_borders.css';
+@import './_transitions.css';
diff --git a/src/styles/utilities/_utilities.css b/src/styles/utilities/_utilities.css
new file mode 100644
index 0000000000..178d00c126
--- /dev/null
+++ b/src/styles/utilities/_utilities.css
@@ -0,0 +1,156 @@
+/**
+ * Utility Classes (layer: utilities)
+ *
+ * High-priority utility classes for one-off overrides.
+ * Use sparingly - prefer component styles.
+ */
+
+/* Visually hidden but accessible to screen readers */
+.sr-only {
+  position: absolute;
+  width: 1px;
+  height: 1px;
+  padding: 0;
+  margin: -1px;
+  overflow: hidden;
+  clip: rect(0, 0, 0, 0);
+  white-space: nowrap;
+  border: 0;
+}
+
+/* Text alignment */
+.text-left {
+  text-align: left;
+}
+.text-center {
+  text-align: center;
+}
+.text-right {
+  text-align: right;
+}
+
+/* Display */
+.hidden {
+  display: none;
+}
+.block {
+  display: block;
+}
+.inline {
+  display: inline;
+}
+.inline-block {
+  display: inline-block;
+}
+.flex {
+  display: flex;
+}
+.grid {
+  display: grid;
+}
+.contents {
+  display: contents;
+}
+
+/* Flex utilities */
+.flex-row {
+  flex-direction: row;
+}
+.flex-col {
+  flex-direction: column;
+}
+.items-center {
+  align-items: center;
+}
+.items-start {
+  align-items: flex-start;
+}
+.items-end {
+  align-items: flex-end;
+}
+.justify-center {
+  justify-content: center;
+}
+.justify-between {
+  justify-content: space-between;
+}
+.justify-end {
+  justify-content: flex-end;
+}
+.gap-1 {
+  gap: var(--space-1);
+}
+.gap-2 {
+  gap: var(--space-2);
+}
+.gap-3 {
+  gap: var(--space-3);
+}
+.gap-4 {
+  gap: var(--space-4);
+}
+.gap-6 {
+  gap: var(--space-6);
+}
+.gap-8 {
+  gap: var(--space-8);
+}
+
+.w-full {
+  width: 100%;
+}
+
+.h-full {
+  height: 100%;
+}
+
+.max-w-prose {
+  max-width: var(--content-width);
+}
+
+.mx-auto {
+  margin-inline: auto;
+}
+.my-auto {
+  margin-block: auto;
+}
+
+/* Padding shortcuts */
+.p-0 {
+  padding: var(--space-0);
+}
+.p-2 {
+  padding: var(--space-2);
+}
+.p-4 {
+  padding: var(--space-4);
+}
+.p-6 {
+  padding: var(--space-6);
+}
+.p-8 {
+  padding: var(--space-8);
+}
+
+/* Margin shortcuts */
+.m-0 {
+  margin: var(--space-0);
+}
+.m-2 {
+  margin: var(--space-2);
+}
+.m-4 {
+  margin: var(--space-4);
+}
+.m-6 {
+  margin: var(--space-6);
+}
+.m-8 {
+  margin: var(--space-8);
+}
+
+.disable-transitions *,
+.disable-transitions *::before,
+.disable-transitions *::after {
+  transition: none !important;
+}
diff --git a/src/utils/content.ts b/src/utils/content.ts
new file mode 100644
index 0000000000..e656027b59
--- /dev/null
+++ b/src/utils/content.ts
@@ -0,0 +1,233 @@
+import type { Menu, MenuItem, MenuSection, VersionPrefix } from '@/config/types';
+import { mainMenu } from '@/config/menu/main';
+import { apiMenu } from '@/config/menu/api';
+
+export type BreadcrumbItem = {
+  href?: string;
+} & (
+  | { label: string; icon?: string; ariaLabel?: string }
+  | { icon: string; ariaLabel: string; label?: never }
+);
+
+function formatLabel(segment: string): string {
+  return segment
+    .split('-')
+    .map((word) =>
+      word.length <= 3 ? word.toUpperCase() : word.charAt(0).toUpperCase() + word.slice(1)
+    )
+    .join(' ');
+}
+
+function buildMenuMaps(menu: Menu) {
+  const labelMap = new Map<string, string>();
+  const sectionMap = new Map<string, string>();
+
+  const walkItems = (items: MenuItem[], section: MenuSection | null, basePath = '') => {
+    for (const item of items) {
+      if ('href' in item && item.href) {
+        if (item.href.startsWith('http')) continue;
+        const fullPath = `${basePath}${item.href}`.replace(/^\/+/, '');
+
+        labelMap.set(fullPath, item.label);
+
+        // Only map section root paths
+        const isSectionRoot = item.href === '/api' || /^\/api\/[^/]+\/?$/.test(item.href);
+
+        if (section?.title && isSectionRoot) {
+          sectionMap.set(fullPath, section.title);
+        }
+      }
+
+      if ('submenu' in item && item.submenu) {
+        const nextBase = item.submenu.basePath || basePath + (item.href || '');
+        walkItems(item.submenu.items || [], section, nextBase);
+      }
+    }
+  };
+
+  if (menu.sections) {
+    for (const section of menu.sections) {
+      walkItems(section.items, section, section.basePath || '');
+    }
+  }
+
+  if (menu.items) {
+    walkItems(menu.items, null, '');
+  }
+
+  return { labelMap, sectionMap };
+}
+
+const { labelMap: mainMenuMap } = buildMenuMaps(mainMenu);
+const { labelMap: apiMenuMap, sectionMap: apiSectionMap } = buildMenuMaps(apiMenu);
+
+/**
+ * Resolve label safely
+ */
+function resolveLabel(t: (key: string) => string, labelKey?: string, segment?: string): string {
+  if (!labelKey) return formatLabel(segment || '');
+
+  return labelKey.startsWith('menu.') ? t(labelKey as string) : labelKey;
+}
+
+/**
+ * Build breadcrumbs
+ */
+export function buildBreadcrumbs(pathname: string, t: (key: string) => string): BreadcrumbItem[] {
+  const segments = pathname.replace(/^\/|\/$/g, '').split('/');
+
+  // Need at least lang + one content segment
+  if (segments.length < 2) return [];
+
+  const [lang, ...rest] = segments;
+
+  const breadcrumbs: BreadcrumbItem[] = [];
+
+  let currentPath = '';
+
+  const isApi = rest.includes('api');
+  const isBlog = rest.includes('blog');
+  const isResources = rest.includes('resources');
+  const isDoc = !isApi && !isBlog && !isResources;
+
+  const menuMap = isApi ? apiMenuMap : mainMenuMap;
+
+  // Matches version prefix segments like '5x', '4x', '3x'
+  const VERSION_SEGMENT = /^\d+x$/;
+
+  rest.forEach((segment, index) => {
+    currentPath += `/${segment}`;
+
+    const isVersion = VERSION_SEGMENT.test(segment);
+    const cleanPath = currentPath.replace(/^\/\d+x\//, '').replace(/^\/+/, '');
+    const isLast = index === rest.length - 1;
+
+    let labelKey = menuMap.get(cleanPath);
+
+    // For API paths, replace intermediate segment labels with their section title
+    // (e.g. show "5.x API" instead of the raw item label for the /api segment).
+    // The last segment always uses its own label so the page title is accurate.
+    if (isApi && !isLast) {
+      const sectionKey = apiSectionMap.get(cleanPath);
+      if (sectionKey) {
+        labelKey = sectionKey;
+      }
+    }
+
+    const label = resolveLabel(t, labelKey, segment);
+
+    // Breadcrumb linking logic:
+    // 1. Last item is never linked (it's the current page).
+    // 2. Version segments are never linked.
+    // 3. Docs pages do not have linked intermediate crumbs (text-only path indicator).
+    // 4. API, Blog, and Resources pages have linked intermediate crumbs for easier navigation.
+    const shouldLink = !isLast && !isVersion && !isDoc;
+
+    breadcrumbs.push({
+      label,
+      href: shouldLink ? `/${lang}${currentPath}` : undefined,
+    });
+  });
+
+  return breadcrumbs;
+}
+
+export type AdjacentPage = {
+  href: string;
+  label: string;
+};
+
+/**
+ * Flattens a menu into an ordered list of link items, respecting version filtering
+ */
+function flattenMenu(
+  menu: Menu,
+  version?: string
+): { href: string; label: string; global?: boolean }[] {
+  const items: { href: string; label: string; global?: boolean }[] = [];
+  const basePath = menu.basePath || '';
+
+  const processItems = (menuItems: MenuItem[]) => {
+    for (const item of menuItems) {
+      if (version && item.omitFrom?.includes(version as VersionPrefix)) continue;
+
+      if ('href' in item && item.href && !item.href.includes('#')) {
+        if (item.href.startsWith('http')) continue;
+        items.push({ href: `${basePath}${item.href}`, label: item.label, global: item.global });
+      }
+      if ('submenu' in item && item.submenu) {
+        items.push(...flattenMenu(item.submenu, version));
+      }
+    }
+  };
+
+  if (menu.sections) {
+    for (const section of menu.sections) {
+      if (version && section.omitFrom?.includes(version as VersionPrefix)) continue;
+      processItems(section.items);
+    }
+  }
+
+  if (menu.items) {
+    processItems(menu.items);
+  }
+
+  return items;
+}
+
+/**
+ * Gets the previous and next pages based on a combined menu order (docs → api → resources)
+ * @param slug - The current page slug (e.g., '5x/starter/installing' or 'starter/installing')
+ * @param lang - The language code
+ * @param menus - Array of menus in navigation order, with global flag for non-versioned menus
+ * @param version - The version prefix (e.g., '5x')
+ */
+export function getAdjacentPages(
+  slug: string,
+  lang: string,
+  menus: { menu: Menu; global?: boolean }[],
+  version?: string
+): { prev: AdjacentPage | null; next: AdjacentPage | null } {
+  const flatItems = menus.flatMap(({ menu, global: isGlobalMenu }) => {
+    const items = flattenMenu(menu, version);
+    return items.map((item) => ({
+      ...item,
+      global: isGlobalMenu || item.global,
+    }));
+  });
+
+  // Remove version prefix from slug to match menu hrefs
+  const slugWithoutVersion =
+    version && slug.startsWith(`${version}/`) ? slug.slice(version.length + 1) : slug;
+
+  // Menu hrefs start with / (e.g., /starter/installing)
+  // Normalize trailing slashes for comparison
+  const normalize = (href: string) => href.replace(/\/+$/, '');
+  const currentHref = normalize(`/${slugWithoutVersion}`);
+
+  const currentIndex = flatItems.findIndex((item) => normalize(item.href) === currentHref);
+
+  if (currentIndex === -1) {
+    return { prev: null, next: null };
+  }
+
+  const versionPath = version ? `/${version}` : '';
+
+  const prev =
+    currentIndex > 0
+      ? {
+          href: `/${lang}${flatItems[currentIndex - 1].global ? '' : versionPath}${flatItems[currentIndex - 1].href}`,
+          label: flatItems[currentIndex - 1].label,
+        }
+      : null;
+
+  const next =
+    currentIndex < flatItems.length - 1
+      ? {
+          href: `/${lang}${flatItems[currentIndex + 1].global ? '' : versionPath}${flatItems[currentIndex + 1].href}`,
+          label: flatItems[currentIndex + 1].label,
+        }
+      : null;
+
+  return { prev, next };
+}
diff --git a/src/utils/llms.ts b/src/utils/llms.ts
new file mode 100644
index 0000000000..28bf0df5ce
--- /dev/null
+++ b/src/utils/llms.ts
@@ -0,0 +1,44 @@
+import fs from 'node:fs/promises';
+import matter from 'gray-matter';
+
+export interface ContentEntry {
+  id: string;
+  data: { title: string; description?: string };
+  filePath?: string;
+}
+
+export function stripMdxSyntax(content: string): string {
+  return (
+    content
+      // Remove import statements
+      .replace(/^import\s+.*$/gm, '')
+      // Remove JSX self-closing tags like <Alert ... />
+      .replace(/<[A-Z]\w*\s*[^>]*\/>/g, '')
+      // Remove JSX opening and closing tags like <Alert> </Alert>
+      .replace(/<\/?[A-Z]\w*[^>]*>/g, '')
+      // Collapse multiple blank lines
+      .replace(/\n{3,}/g, '\n\n')
+      .trim()
+  );
+}
+
+export async function getRawMarkdown(entry: ContentEntry): Promise<string> {
+  if (!entry.filePath) return '';
+  try {
+    const raw = await fs.readFile(entry.filePath, 'utf-8');
+    const { content } = matter(raw);
+    return stripMdxSyntax(content);
+  } catch {
+    return '';
+  }
+}
+
+export function buildSection(title: string, url: string, content: string): string {
+  return `\n---\n\n## ${title}\n\nURL: ${url}\n\n${content}`;
+}
+
+export function textResponse(body: string): Response {
+  return new Response(body, {
+    headers: { 'Content-Type': 'text/plain; charset=utf-8' },
+  });
+}
diff --git a/src/utils/rss.ts b/src/utils/rss.ts
new file mode 100644
index 0000000000..d08510db0b
--- /dev/null
+++ b/src/utils/rss.ts
@@ -0,0 +1,45 @@
+export interface FeedAuthor {
+  name: string;
+  github?: string;
+}
+
+export function getPubDateFromId(id: string): Date | undefined {
+  const filename = id.split('/').pop() ?? id;
+  const match = filename.match(/^(\d{4}-\d{2}-\d{2})/);
+  if (!match) return undefined;
+
+  const date = new Date(`${match[1]}T00:00:00.000Z`);
+  return Number.isNaN(date.getTime()) ? undefined : date;
+}
+
+export function getAuthorsCustomData(authors?: FeedAuthor[]): string | undefined {
+  if (!authors?.length) return undefined;
+
+  return authors
+    .map((author) => {
+      const uri = author.github ? `<uri>https://github.com/${author.github}</uri>` : '';
+      return `<author><name>${author.name}</name>${uri}</author>`;
+    })
+    .join('');
+}
+
+export function sortByIdDateDesc<T extends { id: string }>(items: T[]): T[] {
+  return [...items].sort((a, b) => {
+    const aTime = getPubDateFromId(a.id)?.getTime() ?? 0;
+    const bTime = getPubDateFromId(b.id)?.getTime() ?? 0;
+
+    if (aTime === bTime) return a.id.localeCompare(b.id);
+    return bTime - aTime;
+  });
+}
+
+export function shouldIncludeInFeed(id: string): boolean {
+  const filename = id.split('/').pop() ?? id;
+  return !/^write[-_]posts?$/i.test(filename);
+}
+
+export function getLinkedTitleContent(title: string, id: string, site: URL): string {
+  const link = new URL(`/blog/${id}/`, site).href;
+
+  return `<a href="${link}">${title}</a>`;
+}
diff --git a/src/vite-env.d.ts b/src/vite-env.d.ts
new file mode 100644
index 0000000000..ae43aec7c7
--- /dev/null
+++ b/src/vite-env.d.ts
@@ -0,0 +1,8 @@
+/// <reference types="vite/client" />
+/// <reference types="unplugin-icons/types/react" />
+
+declare module '*.svg?react' {
+  import type { FC, SVGProps } from 'react';
+  const ReactComponent: FC<SVGProps<SVGSVGElement>>;
+  export default ReactComponent;
+}
diff --git a/tests/e2e/homepage.spec.ts b/tests/e2e/homepage.spec.ts
new file mode 100644
index 0000000000..0b31eed779
--- /dev/null
+++ b/tests/e2e/homepage.spec.ts
@@ -0,0 +1,245 @@
+import { test, expect } from '@playwright/test';
+import enStrings from '../../src/i18n/ui/en.json' with { type: 'json' };
+import esStrings from '../../src/i18n/ui/es.json' with { type: 'json' };
+import frStrings from '../../src/i18n/ui/fr.json' with { type: 'json' };
+import deStrings from '../../src/i18n/ui/de.json' with { type: 'json' };
+import itStrings from '../../src/i18n/ui/it.json' with { type: 'json' };
+import jaStrings from '../../src/i18n/ui/ja.json' with { type: 'json' };
+import koStrings from '../../src/i18n/ui/ko.json' with { type: 'json' };
+import ptBrStrings from '../../src/i18n/ui/pt-br.json' with { type: 'json' };
+import zhCnStrings from '../../src/i18n/ui/zh-cn.json' with { type: 'json' };
+import zhTwStrings from '../../src/i18n/ui/zh-tw.json' with { type: 'json' };
+
+// Add property here that will be used to test translations
+const languagesToTest = [
+  {
+    code: 'es',
+    label: 'Español',
+    tagline: esStrings.hero.tagline,
+    themeLabel: esStrings.theme.toggle,
+  },
+  {
+    code: 'fr',
+    label: 'Français',
+    tagline: frStrings.hero.tagline,
+    themeLabel: frStrings.theme.toggle,
+  },
+  {
+    code: 'de',
+    label: 'Deutsch',
+    tagline: deStrings.hero.tagline,
+    themeLabel: deStrings.theme.toggle,
+  },
+  {
+    code: 'it',
+    label: 'Italiano',
+    tagline: itStrings.hero.tagline,
+    themeLabel: itStrings.theme.toggle,
+  },
+  {
+    code: 'ja',
+    label: '日本語',
+    tagline: jaStrings.hero.tagline,
+    themeLabel: jaStrings.theme.toggle,
+  },
+  {
+    code: 'ko',
+    label: '한국어',
+    tagline: koStrings.hero.tagline,
+    themeLabel: koStrings.theme.toggle,
+  },
+  {
+    code: 'pt-br',
+    label: 'Português',
+    tagline: ptBrStrings.hero.tagline,
+    themeLabel: ptBrStrings.theme.toggle,
+  },
+  {
+    code: 'zh-cn',
+    label: '简体中文',
+    tagline: zhCnStrings.hero.tagline,
+    themeLabel: zhCnStrings.theme.toggle,
+  },
+  {
+    code: 'zh-tw',
+    label: '繁體中文',
+    tagline: zhTwStrings.hero.tagline,
+    themeLabel: zhTwStrings.theme.toggle,
+  },
+];
+
+/**
+ * Homepage E2E Tests
+ * Includes: Hero, Features, Theme Toggle, Kawaii Toggle, Footer and Language Selector tests.
+ *
+ * TODO: Add tests for Sidebar and Orama Search component in the future.
+ */
+
+test.describe('Homepage Content', () => {
+  let latestVersion: string;
+
+  test.beforeAll(async () => {
+    const response = await fetch('https://registry.npmjs.org/express/latest');
+    const data = await response.json();
+    latestVersion = data.version;
+  });
+
+  test.beforeEach(async ({ page }) => {
+    await page.goto('/en');
+  });
+
+  // testing hero component
+  test('should display the core brand elements and features', async ({ page }) => {
+    const heroBrand = page.getByTestId('hero-brand');
+
+    // 1. Verify Tagline
+    const tagline = page.getByRole('heading', { level: 1 });
+    await expect(tagline).toBeVisible();
+    await expect(tagline).toHaveText(enStrings.hero.tagline);
+
+    // 2. Verify Logos
+    const standardLogo = heroBrand.getByTestId('logo-standard').first();
+    const kawaiiLogo = heroBrand.getByAltText(enStrings.hero.kawaiiLogoAlt);
+
+    await expect(standardLogo).toBeVisible();
+    await expect(kawaiiLogo).toBeHidden();
+
+    // 3. Verify Version
+    const versionText = heroBrand.getByText(latestVersion);
+    await expect(versionText).toBeVisible();
+
+    // 4. Verify Features Section
+    const featureSection = page.getByTestId('features-section');
+    const featuresTitle = featureSection.getByRole('heading', { level: 2 });
+    await expect(featuresTitle).toHaveText(enStrings.features.title);
+
+    // 5. Verify all four feature cards
+    const features = [
+      enStrings.features.webapplication,
+      enStrings.features.api,
+      enStrings.features.performance,
+      enStrings.features.middleware,
+    ];
+
+    for (const feature of features) {
+      const card = featureSection.getByTestId('card').filter({
+        has: page.getByRole('heading', { name: feature.title, exact: true }),
+      });
+      await expect(card).toBeVisible();
+      await expect(card.locator('p')).toHaveText(feature.body);
+    }
+  });
+
+  test('should display the installation command', async ({ page }) => {
+    const installCode = page.getByTestId('install-command');
+    await expect(installCode).toBeVisible();
+    await expect(installCode).toContainText(/npm install express --save/i);
+  });
+
+  test('should have a working "Get Started" call to action', async ({ page }) => {
+    const getStartedBtn = page.getByRole('link', { name: enStrings.hero.getStarted });
+    await expect(getStartedBtn).toHaveAttribute('href', /\/en\/5x\/starter\/installing/);
+
+    await getStartedBtn.click();
+    await expect(page).toHaveURL(/\/en\/5x\/starter\/installing/);
+  });
+
+  test('should display the example code block', async ({ page }) => {
+    const exampleCode = page.getByTestId('example-code');
+    await expect(exampleCode).toBeVisible();
+  });
+
+  // testing theme toggle component
+  test('should toggle between light and dark themes', async ({ page }) => {
+    const root = page.locator('html');
+    const toggleBtn = page.locator('#theme-toggle-button');
+
+    await expect(toggleBtn).toHaveAttribute('aria-label', enStrings.theme.toggle);
+
+    const initialTheme = (await root.getAttribute('data-theme')) || 'light';
+    const targetTheme = initialTheme === 'light' ? 'dark' : 'light';
+
+    await toggleBtn.click();
+    await expect(root).toHaveAttribute('data-theme', targetTheme);
+
+    const savedTheme = await page.evaluate(() => localStorage.getItem('theme'));
+    expect(savedTheme).toBe(targetTheme);
+
+    await toggleBtn.click();
+    await expect(root).toHaveAttribute('data-theme', initialTheme);
+  });
+
+  // Testing languages selector
+  for (const lang of languagesToTest) {
+    test(`should switch to ${lang.label} successfully`, async ({ page }) => {
+      // 1. Find language switcher button (using translated aria-label)
+      const langSwitcher = page.getByRole('button', { name: enStrings.language.selectLabel });
+      await expect(langSwitcher).toBeVisible();
+
+      // 2. Click to open dropdown
+      await langSwitcher.click();
+
+      // 3. Select the language option
+      const option = page.getByRole('option', { name: lang.label });
+      await expect(option).toBeVisible();
+      await option.click();
+
+      // 4. Verify URL change (handling potential trailing slashes or other path parts)
+      await expect(page).toHaveURL(new RegExp(`/${lang.code}`));
+
+      // 5. Verify tagline is correctly translated
+      const tagline = page.getByRole('heading', { level: 1 });
+      await expect(tagline).toHaveText(lang.tagline);
+
+      // 6. Verify theme toggle aria-label is correctly translated
+      const themeToggle = page.locator('#theme-toggle-button');
+      await expect(themeToggle).toHaveAttribute('aria-label', lang.themeLabel);
+    });
+  }
+
+  // testing footer component
+  test('should display copyright and foundation links', async ({ page }) => {
+    const footer = page.getByTestId('footer');
+    await expect(footer).toBeVisible();
+
+    // Verify copyright text
+    await expect(footer).toContainText(/Copyright/);
+    await expect(footer).toContainText(/OpenJS Foundation/);
+
+    // Verify key legal and foundation links
+    const foundationLinks = [
+      { name: /The OpenJS Foundation/i, href: 'https://openjsf.org' },
+      { name: /Privacy Policy/i, href: /privacy-policy/ },
+      { name: /Code of Conduct/i, href: /code-of-conduct/ },
+      { name: /Security Policy/i, href: /security\/policy/ },
+      { name: /Trademark Policy/i, href: /trademark-policy/ },
+      { name: /Terms of Use/i, href: /terms-of-use/ },
+    ];
+
+    for (const link of foundationLinks) {
+      const locator = footer.getByRole('link', { name: link.name }).first();
+      await expect(locator).toBeVisible();
+      await expect(locator).toHaveAttribute('href', link.href);
+    }
+  });
+
+  test('should display social media links', async ({ page }) => {
+    const footer = page.getByTestId('footer');
+
+    const githubLink = footer.getByRole('link', { name: /GitHub/i });
+    const youtubeLink = footer.getByRole('link', { name: /Youtube/i });
+    const xLink = footer.getByRole('link', { name: /X account/i });
+    const slackLink = footer.getByRole('link', { name: /slack/i });
+    const openCollectiveLink = footer.getByRole('link', { name: /Open Collective/i });
+    const blueskyLink = footer.getByRole('link', { name: /bluesky/i });
+    const rssLink = footer.getByRole('link', { name: /RSS Feed/i });
+
+    await expect(githubLink).toBeVisible();
+    await expect(youtubeLink).toBeVisible();
+    await expect(xLink).toBeVisible();
+    await expect(slackLink).toBeVisible();
+    await expect(openCollectiveLink).toBeVisible();
+    await expect(blueskyLink).toBeVisible();
+    await expect(rssLink).toBeVisible();
+  });
+});
diff --git a/tsconfig.json b/tsconfig.json
new file mode 100644
index 0000000000..b1155e8670
--- /dev/null
+++ b/tsconfig.json
@@ -0,0 +1,18 @@
+{
+  "extends": "astro/tsconfigs/strict",
+  "include": [".astro/types.d.ts", "**/*"],
+  "exclude": ["dist"],
+  "compilerOptions": {
+    "baseUrl": ".",
+    "paths": {
+      "@/*": ["src/*"],
+      "@components/*": ["src/components/*"],
+      "@layouts/*": ["src/layouts/*"],
+      "@assets/*": ["src/assets/*"],
+      "@styles/*": ["src/styles/*"],
+      "@config/*": ["src/config/*"],
+      "@i18n/*": ["src/i18n/*"],
+      "@utils/*": ["src/utils/*"]
+    }
+  }
+}
diff --git a/vulnerabilities.xml b/vulnerabilities.xml
deleted file mode 100644
index d76816832b..0000000000
--- a/vulnerabilities.xml
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: feed
-sitemap: false
-title: Express Vulnerabilities
-html_url: /en/blog/posts.html
----
-{% assign posts = site.posts | sort: "date" | reverse %}
-{% for post in posts %}
-{% if post.tags contains "vulnerabilities" %}{% include feed-entry.xml entry=post %}{% endif %}
-{% endfor %}
diff --git a/zh-cn/3x/api.md b/zh-cn/3x/api.md
deleted file mode 100644
index 022856d69a..0000000000
--- a/zh-cn/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API 参考
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x 不再受到维护**
-
-Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>3.x API</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/zh-cn/4x/api.md b/zh-cn/4x/api.md
deleted file mode 100644
index 96fd9ca571..0000000000
--- a/zh-cn/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API 参考
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>4.x API</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/zh-cn/5x/api.md b/zh-cn/5x/api.md
deleted file mode 100644
index 0cce0d181b..0000000000
--- a/zh-cn/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 参考
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/zh-cn/advanced/best-practice-performance.md b/zh-cn/advanced/best-practice-performance.md
deleted file mode 100644
index 89bb27f924..0000000000
--- a/zh-cn/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: 在生产环境中使用 Express 的性能最佳实践
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# 生产环境最佳实践：性能和可靠性
-
-本文讨论了部署到生产环境的 Express 应用程序的性能和可靠性最佳实践。
-
-This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
-
-- [代码中的注意事项](#code)（开发部分）。
-  - 通过 Gzip 压缩，有助于显著降低响应主体的大小，从而提高 Web 应用程序的速度。可使用[压缩](https://www.npmjs.com/package/compression)中间件进行 Express 应用程序中的 gzip 压缩。例如：
-  - 不使用同步函数
-  - 正确进行日志记录
-  - [Handle exceptions properly](#handle-exceptions-properly)
-- Things to do in your environment / setup (the ops part):
-  - 将 NODE_ENV 设置为“production”
-  - Node 应用程序在遇到未捕获的异常时会崩溃。您需要确保应用程序经过彻底测试，能够处理所有异常，这一点最为重要（请参阅[正确处理异常](#exceptions)以了解详细信息）。但是，作为一种防故障措施，请实施一种机制，确保应用程序崩溃后可以自动重新启动。
-  - 在集群应用程序中，个别工作进程的崩溃并不会影响其余的进程。除了性能优势，故障隔离是运行应用程序进程集群的另一原因。每当工作进程崩溃时，请确保始终使用 cluster.fork() 来记录事件并生成新进程。
-  - 高速缓存请求结果
-  - 使用负载均衡器
-  - 逆向代理位于 Web 应用程序之前，除了将请求转发给应用程序外，还对请求执行支持性操作。它还可以处理错误页、压缩、高速缓存、文件服务和负载均衡等功能。
-
-## Things to do in your code {#in-code}
-
-以下是为改进应用程序性能而在代码中要注意的事项：
-
-- 通过 Gzip 压缩，有助于显著降低响应主体的大小，从而提高 Web 应用程序的速度。可使用[压缩](https://www.npmjs.com/package/compression)中间件进行 Express 应用程序中的 gzip 压缩。例如：
-- 不使用同步函数
-- 正确进行日志记录
-- [Handle exceptions properly](#handle-exceptions-properly)
-
-### 使用 gzip 压缩
-
-Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. 对于生产环境中的大流量网站，实施压缩的最佳位置是在反向代理层级（请参阅[使用反向代理](#proxy)）。在此情况下，不需要使用压缩中间件。有关在 Nginx 中启用 gzip 压缩的详细信息，请参阅 Nginx 文档中的 [ngx_http_gzip_module 模块](http://nginx.org/en/docs/http/ngx_http_gzip_module.html)。
-
-### 不使用同步函数
-
-Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
-
-虽然 Node 和许多模块提供函数的同步和异步版本，但是在生产环境中请始终使用异步版本。只有在初始启动时才适合使用同步函数。 The only time when a synchronous function can be justified is upon initial startup.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
-
-### 正确处理异常
-
-In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### For debugging
-
-如果您出于调试目的进行日志记录，请使用 [debug](https://www.npmjs.com/package/debug) 这样的特殊调试模块，而不要使用 `console.log()`。此模块支持您使用 DEBUG 环境变量来控制将哪些调试消息（如果有）发送到 `console.err()`。为了确保应用程序完全采用异步方式，仍需要将 `console.err()` 通过管道传到另一个程序。但您并不会真的希望在生产环境中进行调试，对吧？ This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
-
-#### 出于应用程序活动目的
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### 正确处理异常
-
-Node 应用程序在遇到未捕获的异常时会崩溃。不处理异常并采取相应的措施会导致 Express 应用程序崩溃并脱机。如果您按照以下[确保应用程序自动重新启动](#restart)中的建议执行，那么应用程序可以从崩溃中恢复。幸运的是，Express 应用程序的启动时间一般很短。然而，应当首先立足于避免崩溃，为此，需要正确处理异常。 Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
-
-要确保处理所有异常，请使用以下方法：
-
-- [使用 try-catch](#try-catch)
-- [使用 promise](#promises)
-
-在深入了解这些主题之前，应该对 Node/Express 错误处理有基本的了解：使用 error-first 回调并在中间件中传播错误。Node 将“error-first 回调”约定用于从异步函数返回错误，回调函数的第一个参数是错误对象，后续参数中包含结果数据。为了表明没有错误，可将 null 值作为第一个参数传递。回调函数必须相应地遵循“error-first”回调约定，以便有意义地处理错误。在 Express 中，最佳做法是使用 next() 函数，通过中间件链来传播错误。 Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
-
-有关错误处理基本知识的更多信息，请参阅：
-
-- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### 使用 try-catch
-
-Try-catch 是一种 JavaScript 语言构造，可用于捕获同步代码中的异常。例如，使用 try-catch 来处理 JSON 解析错误（如下所示）。 Use try-catch, for example, to handle JSON parsing errors as shown below.
-
-Here is an example of using try-catch to handle a potential process-crashing exception.
-This middleware function accepts a query field parameter named "params" that is a JSON object.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-However, try-catch works only for synchronous code. 然而，try-catch 仅适用于同步代码。而由于 Node 平台主要采用异步方式（尤其在生产环境中），因此 try-catch 不会捕获大量异常。
-
-#### 使用 promise
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### What not to do
-
-_请勿_侦听 `uncaughtException` 事件，当异常像气泡一样在事件循环中一路回溯时，就会发出该事件。为 `uncaughtException` 添加事件侦听器将改变进程遇到异常时的缺省行为；进程将继续运行而不理会异常。这貌似是防止应用程序崩溃的好方法，但是在遇到未捕获的异常之后仍继续运行应用程序是一种危险的做法，不建议这么做，因为进程状态可能会变得不可靠和不可预测。 Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
-
-此外，`uncaughtException` 被公认为[比较粗糙](https://nodejs.org/api/process.html#process_event_uncaughtexception)，[建议](https://github.com/nodejs/node-v0.x-archive/issues/2582)从内核中将其移除。所以侦听 `uncaughtException` 并不是个好主意。这就是为何我们推荐诸如多个进程和虚拟机管理器之类的方案：崩溃后重新启动通常是从错误中恢复的最可靠方法。 So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-
-我们也不建议使用[域](https://nodejs.org/api/domain.html)。它一般并不能解决问题，是一种不推荐使用的模块。 It generally doesn't solve the problem and is a deprecated module.
-
-## 环境/设置中的注意事项
-
-以下是为改进应用程序性能而在系统环境中要注意的事项：
-
-- 将 NODE_ENV 设置为“production”
-- Node 应用程序在遇到未捕获的异常时会崩溃。您需要确保应用程序经过彻底测试，能够处理所有异常，这一点最为重要（请参阅[正确处理异常](#exceptions)以了解详细信息）。但是，作为一种防故障措施，请实施一种机制，确保应用程序崩溃后可以自动重新启动。
-- 在集群应用程序中，个别工作进程的崩溃并不会影响其余的进程。除了性能优势，故障隔离是运行应用程序进程集群的另一原因。每当工作进程崩溃时，请确保始终使用 cluster.fork() 来记录事件并生成新进程。
-- 高速缓存请求结果
-- 使用负载均衡器
-- 逆向代理位于 Web 应用程序之前，除了将请求转发给应用程序外，还对请求执行支持性操作。它还可以处理错误页、压缩、高速缓存、文件服务和负载均衡等功能。
-
-### 将 NODE_ENV 设置为“production”
-
-The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-将 NODE_ENV 设置为“production”会使 Express：
-
-- 高速缓存视图模板。
-- 高速缓存从 CSS 扩展生成的 CSS 文件。
-- 生成简短的错误消息。
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-如果您需要编写特定于环境的代码，可以使用 `process.env.NODE_ENV` 来检查 NODE_ENV 的值。请注意，检查任何环境变量的值都会导致性能下降，所以应该三思而行。 Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
-
-在开发中，通常会在交互式 shell 中设置环境变量，例如，使用 `export` 或者 `.bash_profile` 文件。但是一般而言，您不应在生产服务器上执行此操作；而是应当使用操作系统的初始化系统（systemd 或 Upstart）。下一节提供如何使用初始化系统的常规详细信息，但是设置 NODE_ENV 对于性能非常重要（且易于操作），所以会在此重点介绍。 But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
-
-对于 systemd，请使用单元文件中的 `Environment` 伪指令。例如： For example:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### 确保应用程序能够自动重新启动
-
-In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
-
-- 使用进程管理器在应用程序（和 Node）崩溃时将其重新启动。
-- 在操作系统崩溃时，使用操作系统提供的初始化系统重新启动进程管理器。还可以在没有进程管理器的情况下使用初始化系统。 It's also possible to use the init system without a process manager.
-
-Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
-
-#### 使用进程管理器
-
-在开发中，只需在命令行从 `node server.js` 或类似项启动应用程序。但是在生产环境中执行此操作会导致灾难。如果应用程序崩溃，它会脱机，直到其重新启动为止。为了确保应用程序在崩溃后可以重新启动，请使用进程管理器。进程管理器是一种应用程序“容器”，用于促进部署，提供高可用性，并支持用户在运行时管理应用程序。 But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
-
-除了在应用程序崩溃时将其重新启动外，进程管理器还可以执行以下操作：
-
-- 获得对运行时性能和资源消耗的洞察。
-- 动态修改设置以改善性能。
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### 使用初始化系统
-
-下一层的可靠性是确保在服务器重新启动时应用程序可以重新启动。系统仍然可能由于各种原因而宕机。为了确保在服务器崩溃后应用程序可以重新启动，请使用内置于操作系统的初始化系统。目前主要使用两种初始化系统：[systemd](https://wiki.debian.org/systemd) 和 [Upstart](http://upstart.ubuntu.com/)。 Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-有两种方法将初始化系统用于 Express 应用程序：
-
-- 在进程管理器中运行应用程序，使用初始化系统将进程管理器安装为服务。进程管理器将在应用程序崩溃时将其重新启动，初始化系统则在操作系统重新启动时重新启动进程管理器。这是建议使用的方法。 The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
-- Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
-
-##### Systemd
-
-Systemd 是一个 Linux 系统和服务管理器。大多数主要 Linux 分发版采用 systemd 作为其缺省初始化系统。 Most major Linux distributions have adopted systemd as their default init system.
-
-A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-有关 systemd 的更多信息，请参阅 [systemd 参考（联机帮助页）](http://www.freedesktop.org/software/systemd/man/systemd.unit.html)。
-
-### 在集群中运行应用程序
-
-在多核系统中，可以通过启动进程的集群，将 Node 应用程序的性能提升多倍。一个集群运行此应用程序的多个实例，理想情况下一个 CPU 核心上运行一个实例，从而在实例之间分担负载和任务。 A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
-
-In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
-
-#### 使用 Node 的集群模块
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### 高速缓存请求结果
-
-提高生产环境性能的另一种策略是对请求的结果进行高速缓存，以便应用程序不需要为满足同一请求而重复执行操作。
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### 使用负载均衡器
-
-无论应用程序如何优化，单个实例都只能处理有限的负载和流量。扩展应用程序的一种方法是运行此应用程序的多个实例，并通过负载均衡器分配流量。设置负载均衡器可以提高应用程序的性能和速度，并使可扩展性远超单个实例可以达到的水平。 One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
-
-A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-对于负载均衡功能，可能必须确保与特定会话标识关联的请求连接到产生请求的进程。这称为_会话亲缘关系_或者_粘性会话_，可通过以上的建议来做到这一点：将 Redis 之类的数据存储器用于会话数据（取决于您的应用程序）。要了解相关讨论，请参阅 [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/)。 This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### 使用逆向代理
-
-A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
-
-通过将无需了解应用程序状态的任务移交给逆向代理，可以使 Express 腾出资源来执行专门的应用程序任务。因此，建议在生产环境中，在 [Nginx](https://www.nginx.com/) 或 [HAProxy](http://www.haproxy.org/) 之类的逆向代理背后运行 Express。 For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/zh-cn/advanced/best-practice-security.md b/zh-cn/advanced/best-practice-security.md
deleted file mode 100644
index 0a7546919a..0000000000
--- a/zh-cn/advanced/best-practice-security.md
+++ /dev/null
@@ -1,283 +0,0 @@
----
-layout: page
-title: 生产环境中 Express 的安全最佳实践
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# 生产环境最佳实践：安全
-
-## 概述
-
-术语\*“生产”_表示软件生命周期中应用程序或 API 可供最终用户或使用者正常使用的阶段。而在_“开发”_阶段中，您仍然积极编写和测试代码，应用程序并未对外部开发访问。对应的系统环境分别被称为_生产_和_开发\*环境。 In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
-
-Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-本文讨论了部署到生产环境的 Express 应用程序的一些安全最佳实践。
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - [hsts](https://github.com/helmetjs/hsts) 用于设置 `Strict-Transport-Security` 头，实施安全的服务器连接 (HTTP over SSL/TLS)。
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) 用于移除 `X-Powered-By` 头。
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - `domain` - 表示 cookie 的域；用于和请求 URL 的服务器的域进行比较。如果匹配，那么接下来检查路径属性。
-    - 相反，[cookie-session](https://www.npmjs.com/package/cookie-session) 中间件实现 cookie 支持的存储：它将整个会话序列化到 cookie 中，而不只是会话键。仅当会话数据相对较小，且易于编码为原语值（而不是对象）时，才使用此中间件。尽管假设浏览器支持每个 cookie 至少 4096 字节以确保不会超过限制，但是每个域的大小不会超过 4093 字节。另外请注意，客户机可以访问 cookie 数据，所以，如果有任何理由将其保持安全或隐藏状态，那么 express-session 可能是更好的选择。
-    - 使用缺省会话 cookie 名称会使应用程序对攻击敞开大门。`X-Powered-By` 之类的值会造成问题：潜在攻击者可以利用这样的值对服务器采集“指纹”，并相应地确定攻击目标。
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - 最后说明一点，和任何其他 Web 应用程序一样，Express 应用程序也容易受到各种基于 Web 的攻击。请熟悉已知的 [Web 漏洞](https://www.owasp.org/www-project-top-ten/)并采取相应的预防措施。
-  - [Additional considerations](#additional-considerations)
-
-## 请勿使用不推荐或者存在漏洞的 Express 版本
-
-Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html) or consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-Also ensure you are not using any of the vulnerable Express versions listed on the [Security updates page](/{{ page.lang }}/advanced/security-updates.html). If you are, update to one of the stable releases, preferably the latest.
-
-## 使用 TLS
-
-If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-此外，可以使用一种方便的 [Let's Encrypt](https://letsencrypt.org/about/) 工具来获取免费的 TLS 证书，这是由[因特网安全研究组 (ISRG)](https://letsencrypt.org/isrg/) 提供的免费、自动化的开放式认证中心 (CA)。
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## 使用 Helmet
-
-[Helmet](https://www.npmjs.com/package/helmet) 通过适当地设置 HTTP 头，帮助您保护应用程序避免一些众所周知的 Web 漏洞。
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-像安装其他模块一样安装 Helmet：
-
-```bash
-$ npm install helmet
-```
-
-然后将其用于您的代码：
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-By default, Express sends the `X-Powered-By` response header that you can
-disable using the `app.disable()` method:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## 安全地使用 cookie
-
-要确保 cookie 不会打开应用程序使其暴露在风险之中，请勿使用缺省会话 cookie 名称并相应地设置 cookie 安全选项。
-
-有两个主要的中间件 cookie 会话模块：
-
-- [express-session](https://www.npmjs.com/package/express-session)，用于替换 Express 3.x 内置的 `express.session` 中间件。
-- [cookie-session](https://www.npmjs.com/package/cookie-session)，用于替换 Express 3.x 内置的 `express.cookieSession` 中间件。
-
-The main difference between these two modules is how they save cookie session data. 这两个模块之间的主要差异是它们保存 cookie 会话数据的方式。[express-session](https://www.npmjs.com/package/express-session) 中间件将会话数据存储在服务器上；它仅将会话标识（而非会话数据）保存在 cookie 中。缺省情况下，它使用内存中存储，并不旨在用于生产环境。在生产环境中，需要设置可扩展的会话存储；请参阅[兼容的会话存储](https://github.com/expressjs/session#compatible-session-stores)列表。 By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-
-In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
-
-### 请勿使用缺省会话 cookie 名称
-
-Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
-
-为避免此问题，请使用通用 cookie 名称；例如，使用 [express-session](https://www.npmjs.com/package/express-session) 中间件：
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### 设置 cookie 安全性选项
-
-设置以下 cookie 选项来增强安全性：
-
-- `secure` - 确保浏览器只通过 HTTPS 发送 cookie。
-- `httpOnly` - 确保 cookie 只通过 HTTP(S)（而不是客户机 JavaScript）发送，这有助于防御跨站点脚本编制攻击。
-- `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
-- `path` - 表示 cookie 的路径；用于和请求路径进行比较。如果路径和域都匹配，那么在请求中发送 cookie。 If this and domain match, then send the cookie in the request.
-- `expires` - 用于为持久性 cookie 设置到期日期。
-
-以下是使用 [cookie-session](https://www.npmjs.com/package/cookie-session) 中间件的示例：
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### 避免其他已知的漏洞
-
-关注 [Node 安全项目](https://npmjs.com/advisories)公告，这可能会影响 Express 或应用程序使用的其他模块。一般而言，Node 安全项目是有关 Node 安全性的知识和工具的出色资源。 In general, these databases are excellent resources for knowledge and tools about Node security.
-
-Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
-
-## 其他注意事项
-
-以下是来自非常出色的 [Node.js 安全核对表](https://blog.risingstack.com/node-js-security-checklist/)的一些进一步建议。请参阅此博客帖子以了解关于这些建议的所有详细信息： Refer to that blog post for all the details on these recommendations:
-
-- 始终过滤和净化用户输入，防御跨站点脚本编制 (XSS) 和命令注入攻击。
-- 使用参数化查询或预编译的语句来防御 SQL 注入攻击。
-- 使用开源的 [sqlmap](http://sqlmap.org/) 工具来检测应用程序中的 SQL 注入漏洞。
-- 使用 [nmap](https://nmap.org/) 和 [sslyze](https://github.com/nabla-c0d3/sslyze) 工具来测试 SSL 密码、密钥和重新协商的配置以及证书的有效性。
-- 使用 [safe-regex](https://www.npmjs.com/package/safe-regex) 来确保正则表达式不易受到[正则表达式拒绝服务](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS)攻击。
-
-[helmet]: <如果使用 `helmet.js`，它会为您执行此功能。>
\ No newline at end of file
diff --git a/zh-cn/advanced/developing-template-engines.md b/zh-cn/advanced/developing-template-engines.md
deleted file mode 100644
index 46765c119c..0000000000
--- a/zh-cn/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: 为 Express 开发模板引擎
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# 为 Express 开发模板引擎
-
-可以使用 `app.engine(ext, callback)` 方法创建自己的模板引擎。`ext` 表示文件扩展名，而 `callback` 表示模板引擎函数，它接受以下项作为参数：文件位置、选项对象和回调函数。 `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
-
-以下代码示例实现非常简单的模板引擎以呈现 `.ntl` 文件。
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Your app will now be able to render `.ntl` files. 应用程序现在能够呈现 `.ntl` 文件。在 `views` 目录中创建名为 `index.ntl` 且包含以下内容的文件：
-
-```pug
-#title#
-#message#
-```
-
-然后，在应用程序中创建以下路径：
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-您向主页发出请求时，`index.ntl` 将呈现为 HTML。
\ No newline at end of file
diff --git a/zh-cn/advanced/healthcheck-graceful-shutdown.md b/zh-cn/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index c836d6bef9..0000000000
--- a/zh-cn/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### 示例
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/zh-cn/advanced/security-updates.md b/zh-cn/advanced/security-updates.md
deleted file mode 100644
index 977a9a7416..0000000000
--- a/zh-cn/advanced/security-updates.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-layout: page
-title: Express 安全性更新
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# 安全更新
-
-<div class="doc-box doc-notice" markdown="1">
-Node.js vulnerabilities directly affect Express. 
-Node.js 漏洞直接影响 Express。因此，请[监视 Node.js 漏洞](https://nodejs.org
-/en/blog/vulnerability/)并确保使用最新稳定版的 Node.js。
-
-</div>
-
-以下列举了在指定版本更新中修复的 Express 漏洞。
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - 修复了 `express.static`、`res.sendfile` 和 `res.sendFile` 中的根路径披露漏洞
-- 4.10.7
-  - 在 `express.static`（[公告](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)）中修复了开放重定向漏洞。
-- 4.8.8
-  - 在 `express.static`（[公告](http://npmjs.com/advisories/32)、[CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)）中修复了目录遍历漏洞。
-- 4.8.4
-  - Node.js 0.10 在某些情况下可能会泄漏 `fd`，这会影响 `express.static` 和 `res.sendfile`。恶意请求会导致 `fd` 泄漏并最终导致 `EMFILE` 错误和服务器无响应。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 4.8.0
-  - 查询字符串中具有极高数量索引的稀疏数组会导致进程耗尽内存并使服务器崩溃。
-  - 极端嵌套查询字符串对象会导致进程阻塞并使服务器暂时无响应。
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x 不再受到维护**
-
-Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - 修复了 `express.static`、`res.sendfile` 和 `res.sendFile` 中的根路径披露漏洞
-- 3.19.0
-  - 在 `express.static`（[公告](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)）中修复了开放重定向漏洞。
-- 3.16.10
-  - 在 `express.static` 中修复了目录遍历漏洞。
-- 3.16.6
-  - Node.js 0.10 在某些情况下可能会泄漏 `fd`，这会影响 `express.static` 和 `res.sendfile`。恶意请求会导致 `fd` 泄漏并最终导致 `EMFILE` 错误和服务器无响应。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 3.16.0
-  - 查询字符串中具有极高数量索引的稀疏数组会导致进程耗尽内存并使服务器崩溃。
-  - 极端嵌套查询字符串对象会导致进程阻塞并使服务器暂时无响应。
-- 3.3.0
-  - 不受支持的方法覆盖尝试的 404 响应易于受到跨站点脚本编制攻击。
\ No newline at end of file
diff --git a/zh-cn/api.md b/zh-cn/api.md
deleted file mode 100644
index 7eac63a8f4..0000000000
--- a/zh-cn/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 参考
-description: 访问 Express.js API 参考文档，获取当前版本所有模块、方法及属性的详细说明，助您构建 Web 应用。
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/zh-cn/changelog/index.md b/zh-cn/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/zh-cn/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/zh-cn/guide/behind-proxies.md b/zh-cn/guide/behind-proxies.md
deleted file mode 100644
index dbf842e68b..0000000000
--- a/zh-cn/guide/behind-proxies.md
+++ /dev/null
@@ -1,98 +0,0 @@
----
-layout: page
-title: 代理背后的 Express
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# 代理背后的 Express
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-在代理背后运行 Express 应用程序时，可使用 [app.set()](/{{ page.lang }}/4x/api.html#app.set) 将应用程序变量 `trust proxy` 设置为下表中所列的某个值。
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>类型</th><th>值</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>布尔</td>
-<td markdown="1">
-如果为 `true`，那么客户机的 IP 地址将用作 `X-Forwarded-*` 头中最左侧的条目。
-如果为 `false`，那么该应用程序将被视为直接面对因特网，而客户机的 IP 地址则派生自 `req.connection.remoteAddress`。这是缺省设置。
-
-
-If `false`, the app is understood as directly facing the client and the client's IP address is derived from `req.socket.remoteAddress`. This is the default setting.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`, `::1/128`
-- linklocal - `169.254.0.0/16`, `fe80::/10`
-- uniquelocal - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`, `fc00::/7`
-
-您可以按以下某种方法设置 IP 地址：
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-如果指定 IP 地址或子网，那么会在地址确定过程中排除这些项，而将最接近应用程序服务器的不受信任的 IP 地址确定为客户机的 IP 地址。 This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>数字</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">[req.hostname](/{{ page.lang }}/api.html#req.hostname) 的值派生自 `X-Forwarded-Host` 头中设置的值（可以由客户机或代理设置此值）。
-  </li>
-  <li markdown="1">`X-Forwarded-Proto` 可以由逆向代理设置，以告知应用程序：它是 `https` 还是 `http`，或者甚至是无效名称。该值由 [req.protocol](/{{ page.lang }}/api.html#req.protocol) 反映。
-   This value is reflected by [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">[req.ip](/{{ page.lang }}/api.html#req.ip) 和 [req.ips](/{{ page.lang }}/api.html#req.ips) 值由 `X-Forwarded-For` 的地址列表填充。
-  </li>
-</ul>
-
-`trust proxy` 设置由使用 [proxy-addr](https://www.npmjs.com/package/proxy-addr) 包实现。有关更多信息，请参阅其文档。 For more information, see its documentation.
diff --git a/zh-cn/guide/database-integration.md b/zh-cn/guide/database-integration.md
deleted file mode 100644
index 4fbe3c08bc..0000000000
--- a/zh-cn/guide/database-integration.md
+++ /dev/null
@@ -1,499 +0,0 @@
----
-layout: page
-title: Express 数据库集成
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# 数据库集成
-
-要将数据库连接到 Express 应用程序，只需在该应用程序中为数据库装入相应的 Node.js 驱动程序。本文档简要说明如何在 Express 应用程序中为数据库系统添加和使用某些最流行的 Node.js 模块： This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongodb)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgresql)
-- [Redis](#redis)
-- [SQL Server](#sql-server)
-- [SQLite](#sqlite)
-- [Elasticsearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-
-这些数据库驱动程序是众多可用数据库驱动程序的一部分。要了解其他选项，请在 [npm](https://www.npmjs.com/) 站点上搜索。
- For other options,
-search on the [npm](https://www.npmjs.com/) site.
-</div>
-
-## Cassandra
-
-**模块**：[cassandra-driver](https://github.com/datastax/nodejs-driver)
-
-### 安装
-
-```bash
-$ npm install cassandra-driver
-```
-
-### 示例
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**模块**: [couchnode](https://github.com/couchbase/couchnode)
-
-### 安装
-
-```bash
-$ npm install couchbase
-```
-
-### 示例
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**模块**：[nano](https://github.com/dscape/nano)
-
-### 安装
-
-```bash
-$ npm install nano
-```
-
-### 示例
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**模块**：[levelup](https://github.com/rvagg/node-levelup)
-
-### 安装
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### 示例
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**模块**：[mysql](https://github.com/felixge/node-mysql/)
-
-### 安装
-
-```bash
-$ npm install mysql
-```
-
-### 示例
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**模块**：[mongodb](https://github.com/mongodb/node-mongodb-native)
-
-### 安装
-
-```bash
-$ npm install mongodb
-```
-
-### 示例（v2.\*）
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### 示例（v3.\*）
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-如果您需要 MongoDB 的对象模型驱动程序，请查看 [Mongoose](https://github.com/LearnBoost/mongoose)。
-
-## Neo4j
-
-**Module**: [neo4j-driver](https://github.com/neo4j/neo4j-javascript-driver)
-
-### 安装
-
-```bash
-$ npm install neo4j-driver
-```
-
-### 示例
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**模块**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### 安装
-
-注意: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### 示例
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**Module**: [pg-promise](https://github.com/vitaly-t/pg-promise)
-
-### 安装
-
-```bash
-$ npm install pg-promise
-```
-
-### 示例
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**模块**：[redis](https://github.com/mranney/node_redis)
-
-### 安装
-
-```bash
-$ npm install redis
-```
-
-### 示例
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**模块**: [tedious](https://github.com/tediousjs/tedious)
-
-### 安装
-
-```bash
-$ npm install tedious
-```
-
-### 示例
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**模块**：[sqlite3](https://github.com/mapbox/node-sqlite3)
-
-### 安装
-
-```bash
-$ npm install sqlite3
-```
-
-### 示例
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**模块**：[elasticsearch](https://github.com/elastic/elasticsearch-js)
-
-### 安装
-
-```bash
-$ npm install elasticsearch
-```
-
-### 示例
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/zh-cn/guide/debugging.md b/zh-cn/guide/debugging.md
deleted file mode 100644
index 0a66829379..0000000000
--- a/zh-cn/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: 调试 Express
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# 调试 Express
-
-要查看 Express 中使用的所有内部日志，在启动应用程序时，请将 `DEBUG` 环境变量设置为 `express:*`。
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-在 Windows 上，使用对应的命令。
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-在 [Express 生成器](/{{ page.lang }}/starter/generator.html)所生成的缺省应用程序上运行此命令将显示以下输出：
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-向应用程序发出请求时，可以看到 Express 代码中指定的日志：
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-要仅查看来自路由器实现的日志，请将 `DEBUG` 的值设置为 `express:router`。与此类似，要仅查看来自应用程序实现的日志，请将 `DEBUG` 的值设置为 `express:application`，以此类推。 Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
-
-## `express` 生成的应用程序
-
-`express` 命令生成的应用程序还使用 `debug` 模块，其调试名称空间范围限定为应用程序的名称。
-
-例如，如果您以 `$ express sample-app` 生成应用程序，那么可以使用以下命令来启用调试语句：
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-可以通过分配逗号分隔的名称列表来指定多个调试名称空间：
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/zh-cn/guide/error-handling.md b/zh-cn/guide/error-handling.md
deleted file mode 100644
index b4d04d0d54..0000000000
--- a/zh-cn/guide/error-handling.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
-layout: page
-title: Express 错误处理
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# 错误处理
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## 如果将错误传递到 `next()` 且未在错误处理程序中进行处理，那么该错误将由内置的错误处理程序处理；错误将写入客户机的堆栈跟踪内。堆栈跟踪不包含在生产环境中。
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. For example:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-For errors returned from asynchronous functions invoked by route handlers
-and middleware, you must pass them to the `next()` function, where Express will
-catch and process them.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Starting with Express 5, route handlers and middleware that return a Promise
-will call `next(value)` automatically when they reject or throw an error.
-For example:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-如果将任何项传递到 `next()` 函数（除了字符串 `'route'`），那么 Express 会将当前请求视为处于错误状态，并跳过所有剩余的非错误处理路由和中间件函数。如果您希望以某种方式处理此错误，必须如下一节中所述创建一个错误处理路由。
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. For example:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. For example:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## 缺省错误处理程序
-
-Express 随附一个内置的错误处理程序，负责处理应用程序中可能遇到的任何错误。这个缺省的错误处理中间件函数添加在中间件函数集的末尾。 This default error-handling middleware function is added at the end of the middleware function stack.
-
-If you pass an error to `next()` and you do not handle it in a custom error
-handler, it will be handled by the built-in error handler; the error will be
-written to the client with the stack trace. The stack trace is not included
-in the production environment.
-
-<div class="doc-box doc-info" markdown="1">
-将环境变量 `NODE_ENV` 设置为 `production`，以生产方式运行此应用程序。
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-如果在开始写响应之后调用 `next()` 时出错（例如，如果在以流式方式将响应传输到客户机时遇到错误），Express 缺省错误处理程序会关闭连接并使请求失败。
-
-因此，在添加定制错误处理程序时，如果头已发送到客户机，您可能希望委托给 Express 中的缺省错误处理机制处理：
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-错误处理中间件函数的定义方式与其他中间件函数基本相同，差别在于错误处理函数有四个自变量而不是三个：`(err, req, res, next)`：例如： For example:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-请在其他 `app.use()` 和路由调用之后，最后定义错误处理中间件，例如：
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-中间件函数中的响应可以采用您首选的任何格式，例如，HTML 错误页、简单消息或 JSON 字符串。
-
-For organizational (and higher-level framework) purposes, you can define
-several error-handling middleware functions, much as you would with
-regular middleware functions. For example, to define an error-handler
-for requests made by using `XHR` and those without:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-在此示例中，通用 `logErrors` 可能将请求和错误信息写入 `stderr`，例如：
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-也是在此示例中，`clientErrorHandler` 定义如下，错误会显式传递到下一项：
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-“catch-all”`errorHandler` 函数可以如下实现：
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-如果一个路由处理程序具有多个回调函数，那么可以使用 `route` 参数跳至下一个路由处理程序。例如： For example:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-在此示例中，将跳过 `getPaidContent` 处理程序，而将继续执行 `/a_route_behind_paywall` 的 `app` 中所有剩余的处理程序。
-
-<div class="doc-box doc-info" markdown="1">
-
-对 `next()` 和 `next(err)` 的调用会表明当前处理程序是否完整以及处于何种状态。`next(err)` 将跳过链中所有剩余的处理程序（设置为按上述方式处理错误的处理程序除外）。
-  `next(err)` will skip all remaining handlers in the chain except for those that are set up to handle errors as described above.
-</div>
diff --git a/zh-cn/guide/migrating-4.md b/zh-cn/guide/migrating-4.md
deleted file mode 100644
index ade2581235..0000000000
--- a/zh-cn/guide/migrating-4.md
+++ /dev/null
@@ -1,578 +0,0 @@
----
-layout: page
-title: 迁移到 Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# 迁移到 Express 4
-
-<h2 id="overview">概述</h2>
-
-Express 4 is a breaking change from Express 3. Express 4 对 Express 3 进行了重大更改，这意味着，如果您在现有 Express 3 应用程序的依赖项中更新了 Express 版本，那么该应用程序将无法工作。
-
-本文讲述：
-
-<ul class="doclist">
-  <li><a href="#changes">Express 4 中的更改。</a></li>
-  <li>将 Express 3 应用程序迁移到 Express 4 的<a href="#example-migration">示例</a>。</li>
-  <li><a href="#app-gen">升级到 Express 4 应用程序生成器。</a></li>
-</ul>
-
-<h2 id="changes">Express 4 中的更改</h2>
-
-Express 4 中进行了若干重大更改：
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">对路由系统进行了更改。</a></li>
-  <li><a href="#other-changes">其他各种更改。</a></li>
-</ul>
-
-另请参阅：
-
-- [New features in 4.x](https://github.com/expressjs/express/wiki/New-features-in-4.x)。
-- [Migrating from 3.x to 4.x](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)。
-
-<h3 id="core-changes">
-对 Express 核心和中间件系统的更改。
-</h3>
-
-Express 4 不再依赖于 Connect，从其核心移除了所有内置的中间件（除了 `express.static` 函数）。这意味着 Express 现在是独立的路由和中间件 Web 框架，Express 的版本控制和发行不受中间件更新的影响。 This means that
-Express is now an independent routing and middleware web framework, and
-Express versioning and releases are not affected by middleware updates.
-
-由于没有内置中间件，因此您必须显式添加所需的所有中间件才能运行应用程序。只需执行以下步骤： Simply follow these steps:
-
-1. 安装模块：`npm install --save <module-name>`
-2. 在应用程序中需要此模块：`require('module-name')`
-3. 根据文档使用模块：`app.use( ... )`
-
-下表列出了 Express 3 中间件及其在 Express 4 中的对应组件。
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-可参考 Express 4 中间件的[完整列表](https://github.com/senchalabs/connect#middleware)。
-
-在大多数情况下，可以将旧的 V3 中间件替换为 Express 4 的对应组件。有关详细信息，请参阅 GitHub 中的模块文档。 For details, see the module documentation in
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> 可以使用参数</h4>
-
-在 V4 中，您可以使用变量参数来定义装入中间件函数的路径，然后从路由处理程序读取参数的值。
-例如：
-For example:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-路由系统
-</h3>
-
-应用程序现在隐式装入路由中间件，所以您不再需要担心其他中间件相对于`路由`中间件的装入顺序。
-
-定义路由的方式并未改变，但是路由系统新增了两个功能，用于帮助组织路由：
-
-{: .doclist }
-
-- 一个新方法 `app.route()`，用于为路由路径创建可链接的路由处理程序。
-- 一个新类 `express.Router`，用于创建可安装的模块化路由处理程序。
-
-<h4 id="app-route"><code>app.route()</code> 方法</h4>
-
-新的 `app.route()` 方法使您可以为路由路径创建可链接的路由处理程序。创建模块化路由很有帮助，因为在单一位置指定路径，所以可以减少冗余和输入错误。有关路由的更多信息，请参阅 [`Router()` 文档](/{{ page.lang }}/4x/api.html#router)。 Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
-information about routes, see [`Router()` documentation](/{{ page.lang }}/4x/api.html#router).
-
-以下是使用 `app.route()` 函数定义的链式路由处理程序的示例。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> 类</h4>
-
-The other feature that helps to organize routes is a new class,
-`express.Router`, that you can use to create modular mountable
-route handlers. 有助于组织路由的另一个功能是新类 `express.Router`，可用于创建可安装的模块化路由处理程序。`Router` 实例是完整的中间件和路由系统；因此，常常将其称为“微型应用程序”。
-
-以下示例将路由器创建为模块，在其中装入中间件，定义一些路由，然后安装在主应用程序的路径中。
-
-例如，在应用程序目录中创建名为 `birds.js` 的路由器文件，其中包含以下内容：
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-接着，在应用程序中装入路由器模块：
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-此应用程序现在可处理针对 `/birds` 和 `/birds/about` 路径的请求，调用特定于此路由的 `timeLog` 中间件。
-
-<h3 id="other-changes">
-其他更改
-</h3>
-
-下表列出 Express 4 中虽小但重要的其他更改：
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>对象</th>
-<th>描述</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 需要 Node.js 0.10.x 或更高版本，已取消对 Node.js 0.8.x 的支持。</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-
-不再需要 `http` 模块，除非您要直接使用它 (socket.io/SPDY/HTTPS)。可以使用 `app.listen()` 函数来启动此应用程序。
- The app can be started by using the
-`app.listen()` function.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-The `app.configure()` function has been removed.  
-已移除 `app.configure()` 函数。使用 `process.env.NODE_ENV` 或 `app.get('env')` 功能来检测环境并相应配置该应用程序。
-
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-在 Express 4 中，缺省情况下，已禁用 `json spaces` 应用程序属性。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-使用 `req.accepts()`、`req.acceptsEncodings()`、`req.acceptsCharsets()` 和 `req.acceptsLanguages()`。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-不再解析相对 URL。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-原来是数组；现在是对象。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-原来是函数；现在是对象。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-更改为 `res.headersSent`。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-现在可作为 `app.mountpath` 使用。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-已移除。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-已移除。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Functionality is now limited to setting the basic cookie value. 
-功能现在已限制为设置基本 cookie 值。将 `res.cookie()` 用于增添的功能。
-
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">应用程序迁移示例</h2>
-
-以下是将 Express 3 应用程序迁移到 Express 4 的示例。
-涉及的文件包括 `app.js` 和 `package.json`。
-下一步，将 `package.json` 文件中的 `"start": "node ./bin/www"` 更改为 `"start": "node app.js"`。
-
-<h3 id="">
-V3 应用程序
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-考虑具有以下 `app.js` 文件的 Express V3 应用程序：
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-随附的 V3 `package.json` 文件可能具有类似于以下的内容：
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-进程
-</h3>
-
-使用以下命令安装 Express 4 应用程序的必需中间件并将 Express 和 Pug 分别更新到其最新版本，从而开始迁移过程：
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-对 `app.js` 进行以下更改：
-
-1. Express 内置中间件函数 `express.favicon`、`express.logger`、`express.methodOverride`、`express.session`、`express.bodyParser` 和 `express.errorHandler` 不再可用于 `express` 对象。您必须手动安装其替代项，然后在应用程序中装入。 You must install their alternatives
-   manually and load them in the app.
-
-2. You no longer need to load the `app.router` function.
-   不再需要装入 `app.router` 函数。它不是有效的 Express 4 应用程序对象，所以移除了 `app.use(app.router);` 代码。
-
-3. 确保以正确顺序装入中间件函数 - 在装入应用程序路由之后装入 `errorHandler`。
-
-<h3 id="">V4 应用程序</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-运行以上 `npm` 命令会更新 `package.json`，如下所示：
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-随后，移除无效代码，装入所需中间件，并根据需要进行其他更改。`app.js` 文件如下： The `app.js` file will look like this:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-除非您需要直接使用 `http` 模块 (socket.io/SPDY/HTTPS)，否则不需要将其装入，可按以下方式启动此应用程序：
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">运行应用程序</h3>
-
-迁移过程完成，此应用程序现在是 Express 4 版本。要进行确认，可使用以下命令启动此应用程序： To confirm, start the app by using the following command:
-
-```bash
-$ node .
-```
-
-装入 [http://localhost:3000](http://localhost:3000)，然后查看 Express 4 呈现的主页。
-
-<h2 id="app-gen">升级到 Express 4 应用程序生成器</h2>
-
-用于生成 Express 应用程序的命令行工具仍然是 `express`，但是要升级到新版本，您必须卸载 Express 3 应用程序生成器，然后安装新的 `express-generator`。
-
-<h3 id="">安装</h3>
-
-如果您已经在系统上安装了 Express 3 应用程序生成器，必须将其卸载：
-
-```bash
-$ npm uninstall -g express
-```
-
-根据您的文件和目录特权的配置方式，可能需要使用 `sudo` 来运行此命令。
-立即安装新的生成器：
-
-Now install the new generator:
-
-```bash
-$ npm install -g express-generator
-```
-
-根据您的文件和目录特权的配置方式，可能需要使用 `sudo` 来运行此命令。
-立即安装新的生成器：
-
-现在，系统上的 `express` 命令已更新到 Express 4 生成器。
-
-<h3 id="">对应用程序生成器的更改</h3>
-
-命令选项和用法大体保持相同，但也存在以下例外：
-
-{: .doclist }
-
-- 已移除 `--sessions` 选项。
-- 已移除 `--jshtml` 选项。
-- 已添加 `--hogan` 选项来支持 [Hogan.js](http://twitter.github.io/hogan.js/)。
-
-<h3 id="">示例</h3>
-
-执行以下命令来创建 Express 4 应用程序：
-
-```bash
-$ express app4
-```
-
-如果查看 `app4/app.js` 文件的内容，那么会注意到应用程序所需的所有中间件函数（除了 `express.static`）都作为独立模块装入，而在应用程序中不再显式装入 `router` 中间件。
-
-还可以注意到，与旧生成器生成的独立应用程序相反，`app.js` 文件现在是 Node.js 模块。
-
-在安装依赖项之后，可使用以下命令来启动此应用程序：
-
-```bash
-$ npm start
-```
-
-如果查看 `package.json` 文件中的 npm 启动脚本，可以注意到启动应用程序的实际命令是 `node ./bin/www`，而过去在 Express 3 中，该命令是 `node app.js`。
-
-因为 Express 4 生成器生成的 `app.js` 文件现在是 Node.js 模块，所以不再能够将其作为应用程序独立启动（除非修改代码）。必须在 Node.js 文件中加载此模块，并通过 Node.js 文件启动。在此情况下，Node.js 文件是 `./bin/www`。 The module must be loaded in a Node.js file
-and started via the Node.js file. The Node.js file is `./bin/www`
-in this case.
-
-对于创建 Express 应用程序或启动此应用程序，`bin` 目录或无扩展名的 `www` 文件都不是必需的。它们只是生成器提出的建议，可随意根据自己的需求进行修改。 They are
-just suggestions made by the generator, so feel free to modify them to suit your
-needs.
-
-如果不想使用 `www` 目录，而是保持“Express 3 风格”，请删除 `app.js` 文件末尾的 `module.exports = app;` 行，然后将以下代码粘贴在到该位置：
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-确保使用以下代码在 `app.js` 文件之上装入 `debug` 模块：
-
-```js
-var debug = require('debug')('app4')
-```
-
-现在，您已将 `./bin/www` 的功能恢复为 `app.js`。不建议进行此更改，但是此练习可以帮助您理解 `./bin/www` 文件的工作方式，以及为何 `app.js` 文件不再自行启动。
-
-You have now moved the functionality of `./bin/www` back to
-`app.js`. This change is not recommended, but the exercise helps you
-to understand how the `./bin/www` file works, and why the `app.js` file
-no longer starts on its own.
diff --git a/zh-cn/guide/migrating-5.md b/zh-cn/guide/migrating-5.md
deleted file mode 100644
index cf86a53709..0000000000
--- a/zh-cn/guide/migrating-5.md
+++ /dev/null
@@ -1,618 +0,0 @@
----
-layout: page
-title: 迁移到 Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# 迁移到 Express 5
-
-<h2 id="overview">概述</h2>
-
-Express 5 与 Express 4 的差异不是很大：对 API 的更改不像 3.0 到 4.0 升级那样大刀阔斧。虽然基本 API 保持相同，但仍有一些重大更改；换言之，如果将现有 Express 4 程序更新为使用 Express 5，那么该程序可能无法工作。 Therefore, an application built with Express 4 might not work if you update it to use Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-随后，可以运行自动化测试以查看哪些地方发生故障，然后根据以下列出的更新修复问题。在解决测试故障问题之后，运行应用程序以查看发生哪些错误。如果应用程序使用任何不受支持的方法或属性，您马上就可以发现。 After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Express 5 中的更改</h2>
-
-**已移除的方法和属性**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">复数的方法名称</a></li>
-  <li><a href="#leading">app.param(name, fn) 的 name 自变量中的前置冒号</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**改进**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#app.listen">app.listen</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**已更改**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## 已移除的方法和属性
-
-If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 不再支持 `app.del()` 函数。如果使用此函数，将抛出错误。要注册 HTTP DELETE 路由，请使用 `app.delete()` 函数。 If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
-
-最初之所以使用 `del` 而不是 `delete`，是因为 `delete` 是 JavaScript 中的保留关键字。但在 ECMAScript 6 时，`delete` 和其他保留关键字可以合法地用作属性名称。您可以在此阅读该讨论，这导致我们在此不推荐使用 `app.del` 函数。 However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-`app.param(fn)` 特征符用于修改 `app.param(name, fn)` 函数的行为。自 V4.11.0 起不推荐使用该特征符，而 Express 5 完全不再提供支持。 It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="plural">复数的方法名称</h3>
-
-The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
-
-`req.acceptsLanguage()` 由 `req.acceptsLanguages()` 取代。
-
-`req.acceptsCharset()` 由 `req.acceptsCharsets()` 取代。
-
-`req.acceptsEncoding()` 由 `req.acceptsEncodings()` 取代。
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">app.param(name, fn) 的名称中的前置冒号 (:)</h3>
-
-`app.param(name, fn)` 函数名称中的前置冒号字符 (:) 是 Express 3 的遗留问题，为了向后兼容性，Express 4 提供支持但会显示不推荐使用的提醒。而 Express 5 则静默忽略它，使用不带前置冒号的名称参数。 Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
-
-如果您遵循 [app.param](/{{ page.lang }}/4x/api.html#app.param) 的 Express 4 文档进行开发，那么不会影响代码，因为文档中没有提及前置冒号。
-
-<h3 id="req.param">req.param(name)</h3>
-
-This potentially confusing and dangerous method of retrieving form data has been removed. 已移除用于检索表单数据的方法，因为这可能引起混淆，而且很危险。现在，您需要在 `req.params`、`req.body` 或 `req.query` 对象中专门寻找提交的参数名称。
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 不再支持特征符 `res.json(obj, status)`。而是设置状态，然后将其链接到 `res.json()` 方法，如下所示：`res.status(status).json(obj)`。 Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 不再支持特征符 `res.jsonp(obj, status)`。而是设置状态，然后将其链接到 `res.jsonp()` 方法，如下所示：`res.status(status).jsonp(obj)`。 Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 不再支持特征符 `res.send(obj, status)`。而是设置状态，然后将其链接到 `res.send()` 方法，如下所示：`res.status(status).send(obj)`。 Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 no longer supports the signature `res.send(status)`, where `status` is a number. Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
-If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-在 Express 5 中，`res.sendfile()` 函数已由驼峰式大小写版本 `res.sendFile()` 替换。
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## 已更改
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. For example:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-For example:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-在 Express 4 中已移除的 `app.router` 对象在 Express 5 中已恢复。在新版本中，此对象只是对 Express 基本路由器的引用，不像在 Express 3 中应用程序必须显式将该路由器装入。 In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-在 Express 4 中，如果存在端口号，`req.host` 函数会错误地将其剥离。在 Express 5 中，则会保留端口号。 In Express 5, the port number is maintained.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## 改进
-
-<h3 id="res.render">res.render()</h3>
-
-现在，此方法为所有查看引擎强制执行异步行为，避免具有同步实现以及违反建议接口的查看引擎所导致的错误。
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/zh-cn/guide/overriding-express-api.md b/zh-cn/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/zh-cn/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/zh-cn/guide/routing.md b/zh-cn/guide/routing.md
deleted file mode 100644
index 381320769b..0000000000
--- a/zh-cn/guide/routing.md
+++ /dev/null
@@ -1,412 +0,0 @@
----
-layout: page
-title: Express 路由
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# 路由
-
-_路由_表示应用程序端点 (URI) 的定义以及端点响应客户机请求的方式。
-有关路由的简介，请参阅[基本路由](/{{ page.lang }}/starter/basic-routing.html)。
-For an introduction to routing, see [Basic routing](/{{ page.lang }}/starter/basic-routing.html).
-
-我们所使用的 app 与 HTTP 方法相对应的 Express 对象方法来定义路由，如 `app.get()` 用于处理 GET 请求，而 `app.post` 则用于处理 POST 请求。 For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-这些路由方法都指定了回调函数（或者：“处理程序函数”），当程序接收到指定的路由（端点）的时候（也就是说 HTTP 方法请求时被调用），来调用回调函数，换句话说就是应用程序监听与指定路由和方法匹配的请求，当检测到匹配时，他会调用对应的回调函数。 In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-以下代码是非常基本的路由示例。
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">路由方法</h2>
-
-路由方法派生自 HTTP 方法之一，附加到 `express` 类的实例。
-
-以下代码是为访问应用程序根目录的 GET 和 POST 方法定义的路由示例。
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-有一种特殊路由方法：`app.all()`，它并非派生自 HTTP 方法。该方法用于在所有请求方法的路径中装入中间件函数。 在以下示例中，无论您使用 GET、POST、PUT、DELETE 还是在 [http 模块](https://nodejs.org/api/http.html#http_http_methods)中支持的其他任何 HTTP 请求方法，都将为针对“/secret”的请求执行处理程序。
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">路由路径</h2>
-
-路由路径与请求方法相结合，用于定义可以在其中提出请求的端点。路由路径可以是字符串、字符串模式或正则表达式。 Route paths can be strings, string patterns, or regular expressions.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### 以下是基于字符串的路由路径的一些示例。
-
-此路由路径将请求与 `/random.text` 匹配。
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-此路由路径将请求与 `/about` 匹配。
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-此路由路径将请求与根路由 `/` 匹配。
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### 以下是基于字符串模式的路由路径的一些示例。
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-此路由路径将匹配 `/abe` 和 `/abcde`。
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-此路由路径将匹配 `abcd`、`abbcd`、`abbbcd` 等。
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-此路由路径将匹配 `abcd`、`abxcd`、`abRABDOMcd`、`ab123cd` 等。
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-此路由路径将匹配 `acd` 和 `abcd`。
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### 基于正则表达式的路由路径的示例：
-
-此路由路径将匹配名称中具有“a”的所有路由。
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-此路由路径将匹配 `butterfly` 和 `dragonfly`，但是不匹配 `butterflyman`、`dragonfly man` 等。
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">路由处理程序</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Route handlers</h2>
-
-您可以提供多个回调函数，以类似于[中间件](/{{ page.lang }}/guide/using-middleware.html)的行为方式来处理请求。唯一例外是这些回调函数可能调用 `next('route')` 来绕过剩余的路由回调。您可以使用此机制对路由施加先决条件，在没有理由继续执行当前路由的情况下，可将控制权传递给后续路由。 The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
-
-单个回调函数可以处理一个路由。例如： For example:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-多个回调函数可以处理一个路由（确保您指定 `next` 对象）。例如： For example:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-一组回调函数可以处理一个路由。例如： For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-独立函数与一组函数的组合可以处理一个路由。例如： For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">响应方法</h2>
-
-下表中响应对象 (`res`) 的方法可以向客户机发送响应，并终止请求/响应循环。如果没有从路由处理程序调用其中任何方法，客户机请求将保持挂起状态。 If none of these methods are called from a route handler, the client request will be left hanging.
-
-| 方法                                                                                                                                                                                                                        | 描述                       |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | 提示将要下载文件。                |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | 结束响应进程。                  |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | 发送 JSON 响应。              |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | 在 JSONP 的支持下发送 JSON 响应。  |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | 重定向请求。                   |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | 呈现视图模板。                  |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | 发送各种类型的响应。               |
-| [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile)     | 以八位元流形式发送文件。             |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | 设置响应状态码并以响应主体形式发送其字符串表示。 |
-
-<h2 id="app-route">app.route()</h2>
-
-您可以使用 `app.route()` 为路由路径创建可链接的路由处理程序。
-因为在单一位置指定路径，所以可以减少冗余和输入错误。有关路由的更多信息，请参阅 [Router() 文档](/{{ page.lang }}/4x/api.html#router)。
-Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/{{ page.lang }}/5x/api.html#router).
-
-以下是使用 `app.route()` 定义的链式路由处理程序的示例。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-使用 `express.Router` 类来创建可安装的模块化路由处理程序。`Router` 实例是完整的中间件和路由系统；因此，常常将其称为“微型应用程序”。 A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
-
-以下示例将路由器创建为模块，在其中装入中间件，定义一些路由，然后安装在主应用程序的路径中。
-
-在应用程序目录中创建名为 `birds.js` 的路由器文件，其中包含以下内容：
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-接着，在应用程序中装入路由器模块：
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-此应用程序现在可处理针对 `/birds` 和 `/birds/about` 的请求，调用特定于此路由的 `timeLog` 中间件函数。
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/zh-cn/guide/using-middleware.md b/zh-cn/guide/using-middleware.md
deleted file mode 100644
index 367eb6cc38..0000000000
--- a/zh-cn/guide/using-middleware.md
+++ /dev/null
@@ -1,281 +0,0 @@
----
-layout: page
-title: 使用 Express 中间件
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# 使用中间件
-
-Express 是一个路由和中间件 Web 框架，其自身只具有最低程度的功能：Express 应用程序基本上是一系列中间件函数调用。
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
-
-中间件函数可以执行以下任务：
-
-- 执行任何代码。
-- 对请求和响应对象进行更改。
-- 结束请求/响应循环。
-- 调用堆栈中的下一个中间件函数。
-
-如果当前中间件函数没有结束请求/响应循环，那么它必须调用 `next()`，以将控制权传递给下一个中间件函数。否则，请求将保持挂起状态。 Otherwise, the request will be left hanging.
-
-Express 应用程序可以使用以下类型的中间件：
-
-- [应用层中间件](#middleware.application)
-- [路由器层中间件](#middleware.router)
-- [错误处理中间件](#middleware.error-handling)
-- [内置中间件](#middleware.built-in)
-- [第三方中间件](#middleware.third-party)
-
-You can load application-level and router-level middleware with an optional mount path.
-You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
-
-<h2 id='middleware.application'>应用层中间件</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
-HTTP request on the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Here is an example of loading a series of middleware functions at a mount point, with a mount path.
-It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Route handlers enable you to define multiple routes for a path. 路由处理程序使您可以为一个路径定义多个路由。以下示例为针对 `/user/:id` 路径的 GET 请求定义两个路由。第二个路由不会导致任何问题，但是永远都不会被调用，因为第一个路由结束了请求/响应循环。 The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
-
-此示例显示一个中间件子堆栈，用于处理针对 `/user/:id` 路径的 GET 请求。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-要跳过路由器中间件堆栈中剩余的中间件函数，请调用 `next('route')` 将控制权传递给下一个路由。
-**注**：`next('route')` 仅在使用 `app.METHOD()` 或 `router.METHOD()` 函数装入的中间件函数中有效。
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-此示例显示一个中间件子堆栈，用于处理针对 `/user/:id` 路径的 GET 请求。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-此示例显示安装在 `/user/:id` 路径中的中间件函数。在 `/user/:id` 路径中为任何类型的 HTTP 请求执行此函数。
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>路由器层中间件</h2>
-
-路由器层中间件的工作方式与应用层中间件基本相同，差异之处在于它绑定到 `express.Router()` 的实例。
-
-```js
-const router = express.Router()
-```
-
-以下是在安装点使用安装路径装入一系列中间件函数的示例。
-它演示一个中间件子堆栈，用于显示针对 `/user/:id` 路径的任何类型 HTTP 请求的信息。
-
-使用 `router.use()` 和 `router.METHOD()` 函数装入路由器层中间件。
-以下示例代码使用路由器层中间件复制以上为应用层中间件显示的中间件系统：
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-To skip the rest of the router's middleware functions, call `next('router')`
-to pass control back out of the router instance.
-
-此示例显示一个中间件子堆栈，用于处理针对 `/user/:id` 路径的 GET 请求。
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>错误处理中间件</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors.
-</div>
-
-错误处理中间件函数的定义方式与其他中间件函数基本相同，差别在于错误处理函数有四个自变量而不是三个，专门具有特征符 `(err, req, res, next)`：
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-有关错误处理中间件的详细信息，请参阅：[错误处理](/{{ page.lang }}/guide/error-handling.html)。
-
-<h2 id='middleware.built-in'>内置中间件</h2>
-
-Starting with version 4.x, Express no longer depends on [Connect](https://github.com/senchalabs/connect). 自 V4.x 起，Express 不再依赖于 [Connect](https://github.com/senchalabs/connect)。除 `express.static` 外，先前 Express 随附的所有中间件函数现在以单独模块的形式提供。请查看[中间件函数的列表](https://github.com/senchalabs/connect#middleware)。
-
-Express has the following built-in middleware functions:
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>第三方中间件</h2>
-
-使用第三方中间件向 Express 应用程序添加功能。
-
-安装具有所需功能的 Node.js 模块，然后在应用层或路由器层的应用程序中将其加装入。
-
-以下示例演示如何安装和装入 cookie 解析中间件函数 `cookie-parser`。
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-有关 Express 常用的第三方中间件函数的部分列表，请参阅：[第三方中间件](../resources/middleware.html)。
diff --git a/zh-cn/guide/using-template-engines.md b/zh-cn/guide/using-template-engines.md
deleted file mode 100644
index 38b4d9671b..0000000000
--- a/zh-cn/guide/using-template-engines.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-layout: page
-title: 将模板引擎用于 Express
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# 将模板引擎用于 Express
-
-A _template engine_ enables you to use static template files in your application. At runtime, the template engine replaces
-variables in a template file with actual values, and transforms the template into an HTML file sent to the client.
-This approach makes it easier to design an HTML page.
-
-The [Express application generator](/{{ page.lang }}/starter/generator.html) uses [Pug](https://pugjs.org/api/getting-started.html) as its default, but it also supports [Handlebars](https://www.npmjs.com/package/handlebars), and [EJS](https://www.npmjs.com/package/ejs), among others.
-
-To render template files, set the following [application setting properties](/{{ page.lang }}/4x/api.html#app.set), in the default `app.js` created by the generator:
-
-- `views`, the directory where the template files are located. `views`：模板文件所在目录。例如：`app.set('views', './views')`
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, the template engine to use. `view engine`：要使用的模板引擎。例如：`app.set('view engine', 'pug')`
-
-然后安装对应的模板引擎 npm 包：
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-与 Express 兼容的模板引擎（例如 Pug）导出名为 `__express(filePath, options, callback)` 的函数，该函数由 `res.render()` 函数调用以呈现模板代码。
-某些模板引擎并不遵循此约定。[Consolidate.js](https://www.npmjs.org/package/consolidate) 库通过映射所有流行的 Node.js 模板引擎来遵循此约定，因此可以在 Express 内无缝工作。
-
-
-Some template engines do not follow this convention. The [@ladjs/consolidate](https://www.npmjs.com/package/@ladjs/consolidate)
-library follows this convention by mapping all of the popular Node.js template engines, and therefore works seamlessly within Express.
-
-</div>
-
-在设置视图引擎之后，不必指定该引擎或者在应用程序中装入模板引擎模块；Express 在内部装入此模块，如下所示（针对以上示例）。
-
-```js
-app.set('view engine', 'pug')
-```
-
-在 `views` 目录中创建名为 `index.pug` 的 Pug 模板文件，其中包含以下内容：
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Create a route to render the `index.pug` file. If the `view engine` property is not set,
-you must specify the extension of the `view` file. Otherwise, you can omit it.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-向主页发出请求时，`index.pug` 文件将呈现为 HTML。
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/zh-cn/guide/writing-middleware.md b/zh-cn/guide/writing-middleware.md
deleted file mode 100644
index 1b99b798e0..0000000000
--- a/zh-cn/guide/writing-middleware.md
+++ /dev/null
@@ -1,224 +0,0 @@
----
-layout: page
-title: 编写中间件以用于 Express 应用程序
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# 编写中间件以用于 Express 应用程序
-
-<h2>概述</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
-
-中间件函数可以执行以下任务：
-
-- 执行任何代码。
-- 对请求和响应对象进行更改。
-- 结束请求/响应循环。
-- 调用堆栈中的下一个中间件。
-
-如果当前中间件函数没有结束请求/响应循环，那么它必须调用 `next()`，以将控制权传递给下一个中间件函数。否则，请求将保持挂起状态。 Otherwise, the request will be left hanging.
-
-以下示例显示中间件函数调用的元素：
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">中间件函数适用的 HTTP 方法。</div></tbody>
-
-<div class="callout" id="callout2">中间件函数适用的路径（路由）。</div>
-
-<div class="callout" id="callout3">中间件函数。</div>
-
-<div class="callout" id="callout4">中间件函数的回调自变量，按约定称为“next”。</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>示例</h2>
-
-以下是“Hello World”Express 应用程序的简单示例，将为其定义两个中间件函数：
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Here is a simple example of a middleware function called "myLogger". This function just prints "LOGGED" when a request to the app passes through it. 以下是称为“myLogger”的中间件函数的简单示例。此函数仅在应用程序的请求通过它时显示“LOGGED”。中间件函数会分配给名为 `myLogger` 的变量。
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Notice the call above to `next()`. Calling this function invokes the next middleware function in the app.
-
-请注意以上对 `next()` 的调用。调用此函数时，将调用应用程序中的下一个中间件函数。
-`next()` 函数不是 Node.js 或 Express API 的一部分，而是传递给中间件函数的第三自变量。`next()` 函数可以命名为任何名称，但是按约定，始终命名为“next”。为了避免混淆，请始终使用此约定。
- The `next()` function could be named anything, but by convention it is always named "next".
-To avoid confusion, always use this convention.
-</div>
-
-To load the middleware function, call `app.use()`, specifying the middleware function.
-For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-应用程序每次收到请求时，会在终端上显示消息“LOGGED”。
-
-中间件装入顺序很重要：首先装入的中间件函数也首先被执行。
-
-如果在根路径的路由之后装入 `myLogger`，那么请求永远都不会到达该函数，应用程序也不会显示“LOGGED”，因为根路径的路由处理程序终止了请求/响应循环。
-
-中间件函数 `myLogger` 只是显示消息，然后通过调用 `next()` 函数将请求传递到堆栈中的下一个中间件函数。
-
-<h3>Middleware function requestTime</h3>
-
-下一个示例将名为 `requestTime` 的属性添加到请求对象。我们将此中间件函数命名为“requestTime”。
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-The app now uses the `requestTime` middleware function. 现在，该应用程序使用 `requestTime` 中间件函数。此外，根路径路由的回调函数使用由中间件函数添加到 `req`（请求对象）的属性。
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-您向应用程序根发出请求时，此应用程序当前在浏览器中显示请求的时间戳记。
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-因为您拥有请求对象、响应对象、堆栈中的下一个中间件函数以及整个 Node.js API 的访问权，所以中间件函数的可能性是无穷的。
-
-有关 Express 中间件的更多信息，请参阅：[使用 Express 中间件](/{{ page.lang }}/guide/using-middleware.html)。
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/zh-cn/index.md b/zh-cn/index.md
deleted file mode 100644
index 00c9cab584..0000000000
--- a/zh-cn/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web 应用框架
-description: "Express 是 Node.js 的一个快速、灵活、极简的Web框架，为网页和移动应用提供了一套强大的功能特性。"
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">快速、灵活、极简的 <a href='https://nodejs.org/en/'>Node.js</a> Web 框架</h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web 应用开发</h2> Express 是一个简洁灵活的 Node.js Web 应用框架，为网页和移动应用提供了一套强大的功能特性。
-    </div>
-    <div id="apis">
-      <h2>API 开发</h2> 借助丰富的 HTTP 工具方法和中间件支持，快速构建健壮的 API 接口易如反掌。
-    </div>
-    <div id="performance">
-      <h2>性能表现</h2> Express 提供基础的 Web 应用功能薄层封装，绝不遮蔽您熟悉且喜爱的原生 Node.js 特性。
-    </div>
-    <div id="middleware">
-      <h2>中间件</h2> 
-      Express是一个轻量和灵活的路由框架，核心功能最小， 
-      将通过使用Express <a href="{{ page.lang }}/resources/middleware.html">中间件</a> 模块来增加。
-    </div>
-  </div>
-</section>
diff --git a/zh-cn/resources/community.md b/zh-cn/resources/community.md
deleted file mode 100644
index 0765369179..0000000000
--- a/zh-cn/resources/community.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-layout: page
-title: Express 社区
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# 社区
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-我们充满活力的社区已创建了大量各种各样的扩展、[中间件模块](/{{ page.lang }}/resources/middleware.html)和更高层次的框架。请在 [wiki](https://github.com/expressjs/express/wiki) 中了解详细信息。
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## 问题
-
-如果您发现程序中存在错误，或者只是希望提出功能请求，请在[问题队列](https://github.com/expressjs/express/issues)中开具凭证。
-
-## 示例
-
-查看存储库中数十个 Express 应用程序[示例](https://github.com/expressjs/express/tree/master/examples)，这些示例涵盖从 API 设计和认证到模板引擎集成的一切内容。
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/zh-cn/resources/contributing.md b/zh-cn/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/zh-cn/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/zh-cn/resources/glossary.md b/zh-cn/resources/glossary.md
deleted file mode 100644
index 366849ca4a..0000000000
--- a/zh-cn/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express 词汇表
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# 词汇表
-
-### 应用程序 (application)
-
-In general, one or more programs that are designed to carry out operations for a specific purpose.  一般而言，表示设计为针对特定目的执行操作的一个或多个程序。在 Express 的上下文中，表示使用 Node.js 平台上运行的 Express API 的一个程序。可能还指[应用程序对象](/{{ page.lang }}/api.html#express)。  Might also refer to an [app object](/{{ page.lang }}/api.html#express).
-
-### API
-
-应用程序编程接口。在首次使用时包含此缩写。 Spell out the abbreviation when it is first used.
-
-### Express
-
-Node.js 应用程序的一种高度包容、快速而极简的 Web 框架。一般而言，“Express”优先于“Express.js”，但是后者也可接受。 In general, "Express" is preferred to "Express.js," though the latter is acceptable.
-
-### libuv
-
-一种多平台支持库，关注异步 I/O，主要供 Node.js 使用。
-
-### middleware
-
-在最终请求处理程序之前由 Express 路由层调用的函数，因此位于原始请求与最终期望的路由之间的中间位置。有关中间件的术语有几点说明： A few fine points of terminology around middleware:
-
-- 调用 `var foo = require('middleware')`：_需要_或_使用_ Node.js 模块。随后 `var mw = foo()` 语句通常返回中间件。 Then the statement `var mw = foo()` typically returns the middleware.
-- 调用 `app.use(mw)`：_将中间件添加到全局处理堆栈_。
-- 调用 `app.get('/foo', mw, function (req, res) { ... })`：_将中间件添加到“GET /foo”处理堆栈_。
-
-### Node.js
-
-A software platform that is used to build scalable network applications. 用于构建可扩展网络应用程序的一种软件平台。Node.js 将 JavaScript 用作其脚本编制语言，并通过非阻塞 I/O 和单线程事件循环实现大吞吐量。请参阅 [nodejs.org](http://nodejs.org/)。**使用说明**：最初为“Node.js”，后来成为“Node”。 See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
-
-### 开放源码 (open-source, open source)
-
-英文中用作形容词时，以连字符连接；例如：“This is open-source software”。请参阅 [Wikipedia 上的开源软件](http://en.wikipedia.org/wiki/Open-source_software)。注：虽然不对此术语添加连字符也很常见，但是我们使用标准英语规则对复合形容词添加连字符。 See [Open-source software on Wikipedia](http://en.wikipedia.org/wiki/Open-source_software).
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### 请求 (request)
-
-An HTTP request. HTTP 响应。服务器将 HTTP 响应消息返回给客户机。此响应包含关于请求的完整状态信息，可能还在消息体中包含请求的内容。  HTTP 请求。客户机向服务器提交 HTTP 请求消息，然后服务器返回响应。该请求必须使用若干[请求方法](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods)之一，例如 GET、POST 等。
-
-### 响应 (response)
-
-An HTTP response. A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
-
-### 路由 (route)
-
-Part of a URL that identifies a resource. 标识资源的部分 URL。例如，在 `http://foo.com/products/id` 中，“/products/id”是路由。
-
-### 路由器 (router)
-
-请参阅“API 参考”中的[路由器](/{{ page.lang }}/4x/api.html#router)。
diff --git a/zh-cn/resources/middleware.md b/zh-cn/resources/middleware.md
deleted file mode 100644
index 4a0be47806..0000000000
--- a/zh-cn/resources/middleware.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-layout: middleware
-title: Express 中间件
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Express 中间件
-
-The Express middleware modules listed here are maintained by the
-[Expressjs team](https://github.com/orgs/expressjs/people).
-
-| Middleware module                                                           | 描述                                                                                                                                  |
-| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                                             |
-
-## Additional middleware modules
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Middleware module                                                           | 描述                                                                                                                                                                                            |
-| --------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet)：一个模块，用于通过设置各种 HTTP 头来帮助保护应用程序。 | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport)：用于认证的 Express 中间件模块。    | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/zh-cn/resources/middleware/body-parser.md b/zh-cn/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/zh-cn/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/zh-cn/resources/middleware/compression.md b/zh-cn/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/zh-cn/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/zh-cn/resources/middleware/connect-rid.md b/zh-cn/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/zh-cn/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/zh-cn/resources/middleware/cookie-parser.md b/zh-cn/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/zh-cn/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/zh-cn/resources/middleware/cookie-session.md b/zh-cn/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/zh-cn/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/zh-cn/resources/middleware/cors.md b/zh-cn/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/zh-cn/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/zh-cn/resources/middleware/errorhandler.md b/zh-cn/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/zh-cn/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/zh-cn/resources/middleware/method-override.md b/zh-cn/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/zh-cn/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/zh-cn/resources/middleware/morgan.md b/zh-cn/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/zh-cn/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/zh-cn/resources/middleware/multer.md b/zh-cn/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/zh-cn/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/zh-cn/resources/middleware/response-time.md b/zh-cn/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/zh-cn/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/zh-cn/resources/middleware/serve-favicon.md b/zh-cn/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/zh-cn/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/zh-cn/resources/middleware/serve-index.md b/zh-cn/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/zh-cn/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/zh-cn/resources/middleware/serve-static.md b/zh-cn/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/zh-cn/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/zh-cn/resources/middleware/session.md b/zh-cn/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/zh-cn/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/zh-cn/resources/middleware/timeout.md b/zh-cn/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/zh-cn/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/zh-cn/resources/middleware/vhost.md b/zh-cn/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/zh-cn/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/zh-cn/resources/utils.md b/zh-cn/resources/utils.md
deleted file mode 100644
index ccbe9c5e8e..0000000000
--- a/zh-cn/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | 描述                                                                                                                                                                                                                         |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/zh-cn/starter/basic-routing.md b/zh-cn/starter/basic-routing.md
deleted file mode 100644
index 5743654783..0000000000
--- a/zh-cn/starter/basic-routing.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-layout: page
-title: Express 基本路由
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# 基本路由
-
-_路由_用于确定应用程序如何响应对特定端点的客户机请求，包含一个 URI（或路径）和一个特定的 HTTP 请求方法（GET、POST 等）。
-
-每个路由可以具有一个或多个处理程序函数，这些函数在路由匹配时执行。
-
-路由定义采用以下结构：
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Where:
-
-- `app` 是 `express` 的实例。
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` 是服务器上的路径。
-- `HANDLER` 是在路由匹配时执行的函数。
-
-<div class="doc-box doc-notice" markdown="1">
-This tutorial assumes that an instance of `express` named `app` is created and the server is running. 
-本教程假定创建了名为 `app` 的 `express` 实例且服务器正在运行。如果您对创建和启动应用程序并不熟悉，请参阅 [Hello world 示例](/{{ page.lang }}/starter/hello-world.html)。
-
-</div>
-
-以下示例演示了如何定义简单路由。
-
-以主页上的 `Hello World!` 进行响应：
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-对 `/user` 路由的 PUT 请求进行响应：
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-对 `/user` 路由的 DELETE 请求进行响应：
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-有关路由的更多详细信息，请参阅[路由指南](/{{ page.lang }}/guide/routing.html)。
-
diff --git a/zh-cn/starter/examples.md b/zh-cn/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/zh-cn/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/zh-cn/starter/faq.md b/zh-cn/starter/faq.md
deleted file mode 100644
index 3d1e803ca9..0000000000
--- a/zh-cn/starter/faq.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-layout: page
-title: Express 常见问题及解答
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# 常见问题及解答
-
-## 如何构造自己的应用程序？
-
-There is no definitive answer to this question. 这个问题没有固定答案。具体取决于您的应用程序以及参与团队的规模。为了实现尽可能的灵活性，Express 在结构方面不作任何假设。 To be as
-flexible as possible, Express makes no assumptions in terms of structure.
-
-路由和其他特定于应用程序的逻辑可以存在于您首选的任何目录结构的任意数量的文件中。请查看以下示例以获取灵感： View the following
-examples for inspiration:
-
-- [路由列表](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [路由图](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [MVC 样式控制器](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-另外还有针对 Express 的第三方扩展，这有助于简化某些模式：
-
-- [资源丰富的路由](https://github.com/expressjs/express-resource)
-
-## 如何定义模型？
-
-Express 没有数据库概念。此概念留给第三方 Node 模块实现，因此可以接入几乎任何数据库。 This concept is
-left up to third-party Node modules, allowing you to
-interface with nearly any database.
-
-请参阅 [LoopBack](http://loopback.io) 以了解处于模型中心的基于 Express 的框架。
-
-## 如何对用户进行认证？
-
-Authentication is another opinionated area that Express does not
-venture into. You may use any authentication scheme you wish.
-认证是 Express 没有涉足的另一严格领域。您可使用所希望的任何认证方案。
-要了解简单的“用户名/密码”方案，请参阅[此示例](https://github.com/expressjs/express/tree/master/examples/auth)。
-
-## Express 支持哪些模板引擎？
-
-Express 支持符合 `(path, locals, callback)` 特征符的任何模板引擎。
-为了使模板引擎接口和高速缓存实现标准化，请参阅 [consolidate.js](https://github.com/visionmedia/consolidate.js) 项目以获得支持。未列出的模板引擎可能也支持 Express 特征符。
-To normalize template engine interfaces and caching, see the
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-project for support. Unlisted template engines might still support the Express signature.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## 如何处理 404 响应？
-
-在 Express 中，404 响应不是错误的结果，所以错误处理程序中间件不会将其捕获。此行为是因为 404 响应只是表明缺少要执行的其他工作；换言之，Express 执行了所有中间件函数和路由，且发现它们都没有响应。您需要做的只是在堆栈的最底部（在其他所有函数之下）添加一个中间件函数来处理 404 响应： This behavior is
-because a 404 response simply indicates the absence of additional work to do;
-in other words, Express has executed all middleware functions and routes,
-and found that none of them responded. All you need to
-do is add a middleware function at the very bottom of the stack (below all other functions)
-to handle a 404 response:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## 如何设置错误处理程序？
-
-错误处理中间件的定义方式与其他中间件基本相同，差别在于错误处理中间件有四个自变量而不是三个，专门具有特征符 `(err, req, res, next)`：
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-有关更多信息，请参阅[错误处理](/{{ page.lang }}/guide/error-handling.html)。
-
-## 如何呈现纯 HTML？
-
-You don't! 您不必这么做！无需使用 `res.render()` 函数来“呈现”HTML。
-如果您具有特定文件，请使用 `res.sendFile()` 函数。
-如果您希望从目录提供许多资产，请使用 `express.static()` 中间件函数。
-If you have a specific file, use the `res.sendFile()` function.
-If you are serving many assets from a directory, use the `express.static()`
-middleware function.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/zh-cn/starter/generator.md b/zh-cn/starter/generator.md
deleted file mode 100644
index e4e096f123..0000000000
--- a/zh-cn/starter/generator.md
+++ /dev/null
@@ -1,128 +0,0 @@
----
-layout: page
-title: Express 应用程序生成器
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Express 应用程序生成器
-
-可使用应用程序生成器工具 (`express-generator`) 快速创建应用程序框架。
-
-您可以使用 `npx` 命令（在 Node.js 8.2.0 中可用）运行应用程序生成器。
-
-```bash
-$ npx express-generator
-```
-
-对于早期的 Node 版本，可将应用程序生成器作为全局 npm 软件包安装，然后启动它。
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-使用 `-h` 选项显示命令选项：
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-For example, the following creates an Express app named _myapp_. 例如，以下语句在当前工作目录中创建名为 _myapp_ 的 Express 应用程序并将视图引擎将设置为 [Pug](https://pugjs.org/) ：
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-然后安装依赖项：
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-在 MacOS 或 Linux 上，采用以下命令运行此应用程序：
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-在 Windows 命令提示符上，使用以下命令：
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-在 Windows PowerShell 上，使用以下命令：
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-然后在浏览器中输入 `http://localhost:3000/` 以访问此应用程序。
-
-生成的应用程序具有以下目录结构：
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-
-生成器创建的应用程序结构只是构造 Express 应用程序的众多方法之一。请随意使用此结构或者对其进行修改以最大程度满足自己的需求。
- Feel free to use this structure or modify it to best suit your needs.
-</div>
\ No newline at end of file
diff --git a/zh-cn/starter/hello-world.md b/zh-cn/starter/hello-world.md
deleted file mode 100644
index 6f5cb604e8..0000000000
--- a/zh-cn/starter/hello-world.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-layout: page
-title: Express“Hello World”示例
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Hello world 示例
-
-<div class="doc-box doc-info" markdown="1">
-Embedded below is essentially the simplest Express app you can create. It is a single file app &mdash; _not_ what you'd get if you use the [Express generator](/{{ page.lang }}/starter/generator.html), which creates the scaffolding for a full app with numerous JavaScript files, Jade templates, and sub-directories for various purposes.
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-This app starts a server and listens on port 3000 for connections. 应用程序会启动服务器，并在端口 3000 上侦听连接。此应用程序以“Hello World!”响应针对根 URL (`/`) 或_路由_的请求。对于其他所有路径，它将以 **404 Not Found** 进行响应。 For every other path, it will respond with a **404 Not Found**.
-
-### Running Locally
-
-首先创建名为 `myapp` 的目录，切换到此目录，然后运行 `npm init`。根据[安装指南](/{{ page.lang }}/starter/installing.html)将 `express` 安装为依赖项。 Then, install `express` as a dependency, as per the [installation guide](/{{ page.lang }}/starter/installing.html).
-
-在 `myapp` 目录中，创建名为 `app.js` 的文件，然后添加以下代码：
-
-<div class="doc-box doc-notice" markdown="1">
-`req`（请求）和 `res`（响应）与 Node 提供的对象完全相同，所以您可以在不涉及 Express 的情况下调用 `req.pipe()`、`req.on('data', callback)` 和要执行的其他任何函数。
-</div>
-
-使用以下命令运行应用程序：
-
-```bash
-$ node app.js
-```
-
-然后，在浏览器中输入 [http://localhost:3000/](http://localhost:3000/) 以查看输出。
\ No newline at end of file
diff --git a/zh-cn/starter/installing.md b/zh-cn/starter/installing.md
deleted file mode 100644
index c03dda67cd..0000000000
--- a/zh-cn/starter/installing.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-layout: page
-title: 安装 Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# 安装
-
-假设您已经安装了 [Node.js](https://nodejs.org/)，创建目录以保存应用程序，并将其设置为工作目录。
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-使用 `npm init` 命令为应用程序创建 `package.json` 文件。
-有关 `package.json` 工作方式的更多信息，请参阅 [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json)。
-For more information on how `package.json` works, see [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json).
-
-```bash
-$ npm init
-```
-
-This command prompts you for a number of things, such as the name and version of your application.
-For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-```
-entry point: (index.js)
-```
-
-输入 `app.js`，或者您希望使用的任何主文件名称。如果希望文件名为 `index.js`，请按回车键以接受建议的缺省文件名。 If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
-
-在 `myapp` 目录中安装 Express，然后将其保存在依赖项列表中。例如： For example:
-
-```bash
-$ npm install express
-```
-
-要暂时安装 Express 而不将其添加到依赖项列表中：
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-
-默认情况下，版本为 npm 5.0+ 的 npm install 将模块添加到 `package.json` 文件中的 `dependencies` 列表；对于较早版本的 npm，必须显式指定 `--save` 选项。
-今后运行 `app` 目录中的 `npm install` 将自动安装依赖项列表中的模块。
- Then, afterwards, running `npm install` in the app directory will automatically install modules in the dependencies list.
-</div>
\ No newline at end of file
diff --git a/zh-cn/starter/static-files.md b/zh-cn/starter/static-files.md
deleted file mode 100644
index c28f8a82f7..0000000000
--- a/zh-cn/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: 在 Express 中提供静态文件
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# 在 Express 中提供静态文件
-
-为了提供诸如图像、CSS 文件和 JavaScript 文件之类的静态文件，请使用 Express 中的 `express.static` 内置中间件函数。
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-现在，可以访问位于 `public` 目录中的文件：
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express 相对于静态目录查找文件，因此静态目录的名称不是此 URL 的一部分。
-</div>
-
-要使用多个静态资源目录，请多次调用 `express.static` 中间件函数：
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express 以您使用 `express.static` 中间件函数设置静态目录的顺序来查找文件。
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-现在，可以访问具有 `/static` 路径前缀的 `public` 目录中的文件。
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-然而，向 `express.static` 函数提供的路径相对于您在其中启动 `node` 进程的目录。如果从另一个目录运行 Express 应用程序，那么对于提供资源的目录使用绝对路径会更安全： If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/zh-cn/support/index.md b/zh-cn/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/zh-cn/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)
diff --git a/zh-tw/3x/api.md b/zh-tw/3x/api.md
deleted file mode 100644
index f0334bab23..0000000000
--- a/zh-tw/3x/api.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: api
-version: 3x
-title: Express 3.x - API 參照
-description: Access the API reference for Express.js version 3.x, noting that this version is end-of-life and no longer maintained - includes details on modules and methods.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x 已不再維護**
-
-Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-  <h1>3.x API</h1>
-
-<a id='application' class='h2'></a>
-{% include api/en/3x/app.md %}
-
-</div>
diff --git a/zh-tw/4x/api.md b/zh-tw/4x/api.md
deleted file mode 100644
index 336e95a7c5..0000000000
--- a/zh-tw/4x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 4x
-title: Express 4.x - API 參照
-description: Access the API reference for Express.js 4.x, detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>4.x API</h1>
-
-{% capture node-version %}
-
-Express 4.0 requires Node.js 0.10 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/4x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/4x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/4x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/4x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/4x/router.md %}
-
-</div>
diff --git a/zh-tw/5x/api.md b/zh-tw/5x/api.md
deleted file mode 100644
index a24a00d31e..0000000000
--- a/zh-tw/5x/api.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 參照
-description: Access the API reference for Express.js 5.x, detailing all modules, methods, and properties for building web applications with this latest version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-
-  <h1>5.x API</h1>
-
-{% capture node-version %}
-
-Express 5.0 requires Node.js 18 or higher.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=node-version %}
-
-<a id='express' class='h2'></a>
-{% include api/en/5x/express.md %} <a id='app' class='h2'></a>
-{% include api/en/5x/app.md %} <a id='req' class='h2'></a>
-{% include api/en/5x/req.md %} <a id='res' class='h2'></a>
-{% include api/en/5x/res.md %} <a id='router' class='h2'></a>
-{% include api/en/5x/router.md %}
-
-</div>
diff --git a/zh-tw/advanced/best-practice-performance.md b/zh-tw/advanced/best-practice-performance.md
deleted file mode 100644
index e841c665db..0000000000
--- a/zh-tw/advanced/best-practice-performance.md
+++ /dev/null
@@ -1,311 +0,0 @@
----
-layout: page
-title: 在正式作業中使用 Express 的效能最佳作法
-description: Discover performance and reliability best practices for Express apps in production, covering code optimizations and environment setups for optimal performance.
-menu: advanced
-order: 4
-redirect_from: "  "
----
-
-# 正式作業最佳作法：效能和可靠性
-
-本文討論部署至正式作業之 Express 應用程式的效能與可靠性最佳作法。
-
-This topic clearly falls into the "devops" world, spanning both traditional development and operations. Accordingly, the information is divided into two parts:
-
-- Things to do in your code (the dev part):
-  - 採用 gzip 壓縮
-  - [Don't use synchronous functions](#dont-use-synchronous-functions)
-  - [Do logging correctly](#do-logging-correctly)
-  - [Handle exceptions properly](#handle-exceptions-properly)
-- Things to do in your environment / setup (the ops part):
-  - 將 NODE_ENV 設為 "production"
-  - 確定您的應用程式自動重新啟動
-  - [Run your app in a cluster](#run-your-app-in-a-cluster)
-  - [Cache request results](#cache-request-results)
-  - 負載平衡器通常是一個反向 Proxy，負責協調與多個應用程式實例和伺服器之間的資料流量。利用 [Nginx](http://nginx.org/en/docs/http/load_balancing.html) 或 [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts)，就能輕鬆設定您應用程式的負載平衡器。
-  - 反向 Proxy 位於 Web 應用程式前面，除了將要求引導至應用程式，也會對要求執行支援的作業。除此之外，它還可以處理錯誤頁面、壓縮、快取、提供的檔案，以及負載平衡。
-
-## Things to do in your code {#in-code}
-
-以下是您可以在程式碼中執行的一些作法，藉以改良您應用程式的效能：
-
-- 採用 gzip 壓縮
-- [Don't use synchronous functions](#dont-use-synchronous-functions)
-- [Do logging correctly](#do-logging-correctly)
-- [Handle exceptions properly](#handle-exceptions-properly)
-
-### 採用 gzip 壓縮
-
-Gzip compressing can greatly decrease the size of the response body and hence increase the speed of a web app. Use the [compression](https://www.npmjs.com/package/compression) middleware for gzip compression in your Express app. For example:
-
-```js
-const compression = require('compression')
-const express = require('express')
-const app = express()
-
-app.use(compression())
-```
-
-For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see [Use a reverse proxy](#use-a-reverse-proxy)). In that case, you do not need to use compression middleware. 在正式作業中，如果網站的資料流量極高，落實執行壓縮最好的作法是在反向 Proxy 層次實作它（請參閱[使用反向 Proxy](#proxy)）。在該情況下，就不需使用壓縮中介軟體。如需在 Nginx 中啟用 gzip 壓縮的詳細資料，請參閱 Nginx 說明文件中的 [ngx_http_gzip_module 模組](http://nginx.org/en/docs/http/ngx_http_gzip_module.html)。
-
-### 不使用同步函數
-
-Synchronous functions and methods tie up the executing process until they return. A single call to a synchronous function might return in a few microseconds or milliseconds, however in high-traffic websites, these calls add up and reduce the performance of the app. Avoid their use in production.
-
-雖然 Node 和許多模組會提供其函數的同步與非同步版本，在正式作業中，請一律使用非同步版本。唯一有理由使用同步函數的時機是在最初啟動之時。 The only time when a synchronous function can be justified is upon initial startup.
-
-You can use the `--trace-sync-io` command-line flag to print a warning and a stack trace whenever your application uses a synchronous API. Of course, you wouldn't want to use this in production, but rather to ensure that your code is ready for production. See the [node command-line options documentation](https://nodejs.org/api/cli.html#cli_trace_sync_io) for more information.
-
-### Do logging correctly
-
-In general, there are two reasons for logging from your app: For debugging and for logging app activity (essentially, everything else). Using `console.log()` or `console.error()` to print log messages to the terminal is common practice in development. But [these functions are synchronous](https://nodejs.org/api/console.html#console) when the destination is a terminal or a file, so they are not suitable for production, unless you pipe the output to another program.
-
-#### For debugging
-
-如果您為了除錯而記載，則不要使用 `console.log()`，請改用 [debug](https://www.npmjs.com/package/debug) 之類的特殊除錯模組。這個模組可讓您使用 DEBUG 環境變數，來控制哪些除錯訊息（若有的話）要送往 `console.err()`。為了讓應用程式完全維持非同步，您仍得將 `console.err()` 引導至另一個程式。但之後在正式作業中，實際上您並不會進行除錯，不是嗎？ This module enables you to use the DEBUG environment variable to control what debug messages are sent to `console.error()`, if any. To keep your app purely asynchronous, you'd still want to pipe `console.error()` to another program. But then, you're not really going to debug in production, are you?
-
-#### 為了應用程式活動
-
-If you're logging app activity (for example, tracking traffic or API calls), instead of using `console.log()`, use a logging library like [Pino](https://www.npmjs.com/package/pino), which is the fastest and most efficient option available.
-
-### Handle exceptions properly
-
-Node apps crash when they encounter an uncaught exception. Not handling exceptions and taking appropriate actions will make your Express app crash and go offline. If you follow the advice in [Ensure your app automatically restarts](#ensure-your-app-automatically-restarts) below, then your app will recover from a crash. Fortunately, Express apps typically have a short startup time. Nevertheless, you want to avoid crashing in the first place, and to do that, you need to handle exceptions properly.
-
-為了確保您能處理所有的異常狀況，請使用下列技術：
-
-- [使用 try-catch](#try-catch)
-- [使用 promise](#promises)
-
-Before diving into these topics, you should have a basic understanding of Node/Express error handling: using error-first callbacks, and propagating errors in middleware. Node uses an "error-first callback" convention for returning errors from asynchronous functions, where the first parameter to the callback function is the error object, followed by result data in succeeding parameters. To indicate no error, pass null as the first parameter. The callback function must correspondingly follow the error-first callback convention to meaningfully handle the error. And in Express, the best practice is to use the next() function to propagate errors through the middleware chain.
-
-如需進一步瞭解錯誤處理的基本概念，請參閱：
-
-- [Error Handling in Node.js](https://www.tritondatacenter.com/node-js/production/design/errors)
-
-#### 使用 try-catch
-
-try-catch 是一種 JavaScript 語言建構，可用來捕捉同步程式碼中的異常狀況。例如，如以下所示，利用 try-catch 來處理 JSON 剖析錯誤。 Use try-catch, for example, to handle JSON parsing errors as shown below.
-
-Here is an example of using try-catch to handle a potential process-crashing exception.
-This middleware function accepts a query field parameter named "params" that is a JSON object.
-
-```js
-app.get('/search', (req, res) => {
-  // Simulating async operation
-  setImmediate(() => {
-    const jsonStr = req.query.params
-    try {
-      const jsonObj = JSON.parse(jsonStr)
-      res.send('Success')
-    } catch (e) {
-      res.status(400).send('Invalid JSON string')
-    }
-  })
-})
-```
-
-However, try-catch works only for synchronous code. 不過，try-catch 只適用於同步程式碼。由於 Node 平台主要是非同步（尤其是在正式作業環境），try-catch 不會捕捉大量的異常狀況。
-
-#### 使用 promise
-
-When an error is thrown in an `async` function or a rejected promise is awaited inside an `async` function, those errors will be passed to the error handler as if calling `next(err)`
-
-```js
-app.get('/', async (req, res, next) => {
-  const data = await userData() // If this promise fails, it will automatically call `next(err)` to handle the error.
-
-  res.send(data)
-})
-
-app.use((err, req, res, next) => {
-  res.status(err.status ?? 500).send({ error: err.message })
-})
-```
-
-Also, you can use asynchronous functions for your middleware, and the router will handle errors if the promise fails, for example:
-
-```js
-app.use(async (req, res, next) => {
-  req.locals.user = await getUser(req)
-
-  next() // This will be called if the promise does not throw an error.
-})
-```
-
-Best practice is to handle errors as close to the site as possible. So while this is now handled in the router, it’s best to catch the error in the middleware and handle it without relying on separate error-handling middleware.
-
-#### What not to do
-
-One thing you should _not_ do is to listen for the `uncaughtException` event, emitted when an exception bubbles all the way back to the event loop. Adding an event listener for `uncaughtException` will change the default behavior of the process that is encountering an exception; the process will continue to run despite the exception. This might sound like a good way of preventing your app from crashing, but continuing to run the app after an uncaught exception is a dangerous practice and is not recommended, because the state of the process becomes unreliable and unpredictable.
-
-此外，使用 `uncaughtException` 被公認為[拙劣作法](https://nodejs.org/api/process.html#process_event_uncaughtexception)，這裡有一份[提案](https://github.com/nodejs/node-v0.x-archive/issues/2582)，指出如何將它從核心移除。因此，接聽 `uncaughtException` 並不可取。這是我們建議採取多重程序和監督程式等事項的原因：當機再重新啟動，通常是從錯誤回復最可靠的作法。 So listening for `uncaughtException` is just a bad idea. This is why we recommend things like multiple processes and supervisors: crashing and restarting is often the most reliable way to recover from an error.
-
-我們也不建議使用 [domains](https://nodejs.org/api/domain.html)。它通常不能解決問題，並且是個已淘汰的模組。 It generally doesn't solve the problem and is a deprecated module.
-
-## 在環境 / 設定中的作法
-
-以下是您可以在系統環境中執行的一些作法，藉以改良您應用程式的效能：
-
-- 將 NODE_ENV 設為 "production"
-- 確定您的應用程式自動重新啟動
-- [Run your app in a cluster](#run-your-app-in-a-cluster)
-- [Cache request results](#cache-request-results)
-- 負載平衡器通常是一個反向 Proxy，負責協調與多個應用程式實例和伺服器之間的資料流量。利用 [Nginx](http://nginx.org/en/docs/http/load_balancing.html) 或 [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts)，就能輕鬆設定您應用程式的負載平衡器。
-- 反向 Proxy 位於 Web 應用程式前面，除了將要求引導至應用程式，也會對要求執行支援的作業。除此之外，它還可以處理錯誤頁面、壓縮、快取、提供的檔案，以及負載平衡。
-
-### 將 NODE_ENV 設為 "production"
-
-The NODE_ENV environment variable specifies the environment in which an application is running (usually, development or production). One of the simplest things you can do to improve performance is to set NODE_ENV to `production`.
-
-將 NODE_ENV 設為 "production"，可讓 Express：
-
-- Cache view templates.
-- 快取從 CSS 延伸項目產生的 CSS 檔案。
-- Generate less verbose error messages.
-
-[Tests indicate](https://www.dynatrace.com/news/blog/the-drastic-effects-of-omitting-node-env-in-your-express-js-applications/) that just doing this can improve app performance by a factor of three!
-
-如果您需要撰寫環境特定的程式碼，您可以使用 `process.env.NODE_ENV` 來檢查 NODE_ENV 的值。請注意，檢查任何環境變數的值都會影響效能，因此請慎行。 Be aware that checking the value of any environment variable incurs a performance penalty, and so should be done sparingly.
-
-In development, you typically set environment variables in your interactive shell, for example by using `export` or your `.bash_profile` file. But in general, you shouldn't do that on a production server; instead, use your OS's init system (systemd). The next section provides more details about using your init system in general, but setting `NODE_ENV` is so important for performance (and easy to do), that it's highlighted here.
-
-採用 systemd 時，請在單位檔案中使用 `Environment` 指引。例如： For example:
-
-```sh
-# /etc/systemd/system/myservice.service
-Environment=NODE_ENV=production
-```
-
-For more information, see [Using Environment Variables In systemd Units](https://www.flatcar.org/docs/latest/setup/systemd/environment-variables/).
-
-### 確定您的應用程式自動重新啟動
-
-In production, you don't want your application to be offline, ever. This means you need to make sure it restarts both if the app crashes and if the server itself crashes. Although you hope that neither of those events occurs, realistically you must account for both eventualities by:
-
-- 當應用程式（和 Node）當機時，使用程序管理程式重新啟動它。
-- Using the init system provided by your OS to restart the process manager when the OS crashes. It's also possible to use the init system without a process manager.
-
-Node applications crash if they encounter an uncaught exception. The foremost thing you need to do is to ensure your app is well-tested and handles all exceptions (see [handle exceptions properly](#handle-exceptions-properly) for details). But as a fail-safe, put a mechanism in place to ensure that if and when your app crashes, it will automatically restart.
-
-#### 使用程序管理程式
-
-在開發中，只需從指令行使用 `node server.js` 或類似指令，就會啟動應用程式。但在正式作業中這樣做，卻會成為禍因。如果應用程式當機，就會離線直到您重新啟動它為止。為了確保應用程式會在當機時重新啟動，請使用程序管理程式。程序管理程式是一個應用程式的「儲存器」，有助於部署、提供高可用性，並可讓您在執行時期管理應用程式。 But doing this in production is a recipe for disaster. If the app crashes, it will be offline until you restart it. To ensure your app restarts if it crashes, use a process manager. A process manager is a "container" for applications that facilitates deployment, provides high availability, and enables you to manage the application at runtime.
-
-除了在應用程式當機時重新啟動它，程序管理程式還可讓您：
-
-- 洞察執行時期效能和資源的耗用情況。
-- 動態修改設定，以改良效能。
-- Control clustering (pm2).
-
-Historically, it was popular to use a Node.js process manager like [PM2](https://github.com/Unitech/pm2). See their documentation if you wish to do this. However, we recommend using your init system for process management.
-
-#### 使用 init 系統
-
-The next layer of reliability is to ensure that your app restarts when the server restarts. Systems can still go down for a variety of reasons. To ensure that your app restarts if the server crashes, use the init system built into your OS. The main init system in use today is [systemd](https://wiki.debian.org/systemd).
-
-init 系統若要與 Express 應用程式搭配使用，其作法有二：
-
-- Run your app in a process manager, and install the process manager as a service with the init system. The process manager will restart your app when the app crashes, and the init system will restart the process manager when the OS restarts. This is the recommended approach.
-- Run your app (and Node) directly with the init system. This is somewhat simpler, but you don't get the additional advantages of using a process manager.
-
-##### Systemd
-
-Systemd 是一個 Linux 系統和服務管理程式。大部分主要的 Linux 發行套件已採用 systemd 作為其預設 init 系統。 Most major Linux distributions have adopted systemd as their default init system.
-
-A systemd service configuration file is called a _unit file_, with a filename ending in `.service`. Here's an example unit file to manage a Node app directly. Replace the values enclosed in `<angle brackets>` for your system and app:
-
-```sh
-[Unit]
-Description=<Awesome Express App>
-
-[Service]
-Type=simple
-ExecStart=/usr/local/bin/node </projects/myapp/index.js>
-WorkingDirectory=</projects/myapp>
-
-User=nobody
-Group=nogroup
-
-# Environment variables:
-Environment=NODE_ENV=production
-
-# Allow many incoming connections
-LimitNOFILE=infinity
-
-# Allow core dumps for debugging
-LimitCORE=infinity
-
-StandardInput=null
-StandardOutput=syslog
-StandardError=syslog
-Restart=always
-
-[Install]
-WantedBy=multi-user.target
-```
-
-如需 systemd 的相關資訊，請參閱 [systemd 參照（線上指令說明）](http://www.freedesktop.org/software/systemd/man/systemd.unit.html)。
-
-### Run your app in a cluster
-
-In a multi-core system, you can increase the performance of a Node app by many times by launching a cluster of processes. A cluster runs multiple instances of the app, ideally one instance on each CPU core, thereby distributing the load and tasks among the instances.
-
-![Balancing between application instances using the cluster API](/images/clustering.png)
-
-IMPORTANT: Since the app instances run as separate processes, they do not share the same memory space. That is, objects are local to each instance of the app. Therefore, you cannot maintain state in the application code. However, you can use an in-memory datastore like [Redis](http://redis.io/) to store session-related data and state. This caveat applies to essentially all forms of horizontal scaling, whether clustering with multiple processes or multiple physical servers.
-
-In clustered apps, worker processes can crash individually without affecting the rest of the processes. Apart from performance advantages, failure isolation is another reason to run a cluster of app processes. Whenever a worker process crashes, always make sure to log the event and spawn a new process using cluster.fork().
-
-#### 使用 Node 的叢集模組
-
-Clustering is made possible with Node's [cluster module](https://nodejs.org/api/cluster.html). This enables a master process to spawn worker processes and distribute incoming connections among the workers.
-
-#### Using PM2
-
-If you deploy your application with PM2, then you can take advantage of clustering _without_ modifying your application code. You should ensure your [application is stateless](https://pm2.keymetrics.io/docs/usage/specifics/#stateless-apps) first, meaning no local data is stored in the process (such as sessions, websocket connections and the like).
-
-When running an application with PM2, you can enable **cluster mode** to run it in a cluster with a number of instances of your choosing, such as the matching the number of available CPUs on the machine. You can manually change the number of processes in the cluster using the `pm2` command line tool without stopping the app.
-
-To enable cluster mode, start your application like so:
-
-```bash
-# Start 4 worker processes
-$ pm2 start npm --name my-app -i 4 -- start
-# Auto-detect number of available CPUs and start that many worker processes
-$ pm2 start npm --name my-app -i max -- start
-```
-
-This can also be configured within a PM2 process file (`ecosystem.config.js` or similar) by setting `exec_mode` to `cluster` and `instances` to the number of workers to start.
-
-Once running, the application can be scaled like so:
-
-```bash
-# Add 3 more workers
-$ pm2 scale my-app +3
-# Scale to a specific number of workers
-$ pm2 scale my-app 2
-```
-
-For more information on clustering with PM2, see [Cluster Mode](https://pm2.keymetrics.io/docs/usage/cluster-mode/) in the PM2 documentation.
-
-### 快取要求結果
-
-在正式作業中改良效能的另一項策略是快取要求的結果，這樣您的應用程式就不會重複執行作業而反覆處理相同的要求。
-
-Use a caching server like [Varnish](https://www.varnish-cache.org/) or [Nginx](https://blog.nginx.org/blog/nginx-caching-guide) (see also [Nginx Caching](https://serversforhackers.com/nginx-caching/)) to greatly improve the speed and performance of your app.
-
-### 使用負載平衡器
-
-No matter how optimized an app is, a single instance can handle only a limited amount of load and traffic. One way to scale an app is to run multiple instances of it and distribute the traffic via a load balancer. Setting up a load balancer can improve your app's performance and speed, and enable it to scale more than is possible with a single instance.
-
-A load balancer is usually a reverse proxy that orchestrates traffic to and from multiple application instances and servers. You can easily set up a load balancer for your app by using [Nginx](https://nginx.org/en/docs/http/load_balancing.html) or [HAProxy](https://www.digitalocean.com/community/tutorials/an-introduction-to-haproxy-and-load-balancing-concepts).
-
-With load balancing, you might have to ensure that requests that are associated with a particular session ID connect to the process that originated them. This is known as _session affinity_, or _sticky sessions_, and may be addressed by the suggestion above to use a data store such as Redis for session data (depending on your application). For a discussion, see [Using multiple nodes](https://socket.io/docs/v4/using-multiple-nodes/).
-
-### 使用反向 Proxy
-
-A reverse proxy sits in front of a web app and performs supporting operations on the requests, apart from directing requests to the app. It can handle error pages, compression, caching, serving files, and load balancing among other things.
-
-Handing over tasks that do not require knowledge of application state to a reverse proxy frees up Express to perform specialized application tasks. For this reason, it is recommended to run Express behind a reverse proxy like [Nginx](https://www.nginx.org/) or [HAProxy](https://www.haproxy.org/) in production.
diff --git a/zh-tw/advanced/best-practice-security.md b/zh-tw/advanced/best-practice-security.md
deleted file mode 100644
index e813dcac35..0000000000
--- a/zh-tw/advanced/best-practice-security.md
+++ /dev/null
@@ -1,287 +0,0 @@
----
-layout: page
-title: 正式作業中的 Express 安全最佳作法
-description: Discover crucial security best practices for Express apps in production, including using TLS, input validation, secure cookies, and preventing vulnerabilities.
-menu: advanced
-order: 3
-redirect_from: "  "
----
-
-# 正式作業最佳作法：安全
-
-## 概觀
-
-The term _"production"_ refers to the stage in the software lifecycle when an application or API is generally available to its end-users or consumers. In contrast, in the _"development"_ stage, you're still actively writing and testing code, and the application is not open to external access. The corresponding system environments are known as _production_ and _development_ environments, respectively.
-
-Development and production environments are usually set up differently and have vastly different requirements. What's fine in development may not be acceptable in production. For example, in a development environment you may want verbose logging of errors for debugging, while the same behavior can become a security concern in a production environment. And in development, you don't need to worry about scalability, reliability, and performance, while those concerns become critical in production.
-
-{% capture security-note %}
-
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/en/resources/contributing.html#security-policies-and-procedures).
-
-{% endcapture %}
-
-{% include admonitions/note.html content=security-note %}
-
-Security best practices for Express applications in production include:
-
-- [Production Best Practices: Security](#production-best-practices-security)
-  - [Overview](#overview)
-  - [Don't use deprecated or vulnerable versions of Express](#dont-use-deprecated-or-vulnerable-versions-of-express)
-  - 您可能熟悉 Secure Socket Layer (SSL) 加密。[TLS 就是 SSL 後繼的演進](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx)。換句話說，如果您之前使用 SSL，請考量升級至 TLS。一般而言，我們建議由 Nginx 來處理 TLS。如需有關在 Nginx（和其他伺服器）上配置 TLS 的適當參考資料，請參閱 [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations)。
-  - [Do not trust user input](#do-not-trust-user-input)
-    - [Prevent open redirects](#prevent-open-redirects)
-  - [hidePoweredBy](https://github.com/helmetjs/hide-powered-by) 會移除 `X-Powered-By` 標頭。
-  - [Reduce fingerprinting](#reduce-fingerprinting)
-  - `domain` - 指出 Cookie 的網域；用來與發出 URL 要求之伺服器的網域相互比較。如果相符，接著會檢查路徑屬性。
-    - 相對地，[cookie-session](https://www.npmjs.com/package/cookie-session) 中介軟體會實作以 Cookie 為基礎的儲存體：它會將整個階段作業序列化為 Cookie，而非只是一個階段作業金鑰。只有在階段作業資料相對較小，且易於編碼成基本值（而非物件）時，才使用此項。雖然瀏覽器對於每個 Cookie 理應可以支援至少
-      4096 個位元組，為了確保您不會超出限制，對於每一個網域，請勿超過 4093 個位元組大小。此外要留意的是，用戶端可以看見 Cookie 資料，因此，若有任何原因需要保護該資料的安全或加以遮蔽，最好選擇 express-session。
-    - 使用預設階段作業 Cookie 名稱可能開放您的應用程式遭受攻擊。引發的安全問題類似於 `X-Powered-By`：潛在的攻擊者可能用它來對伺服器進行指紋辨識，從而發動目標攻擊。
-  - [Prevent brute-force attacks against authorization](#prevent-brute-force-attacks-against-authorization)
-  - [Ensure your dependencies are secure](#ensure-your-dependencies-are-secure)
-    - 最後，如同其他任何的 Web 應用程式，Express 應用程式仍可能遭到各種 Web 型攻擊。請多加熟悉已知的 [Web 漏洞](https://www.owasp.org/www-project-top-ten/)，並採取預防措施，來避免這些攻擊。
-  - [Additional considerations](#additional-considerations)
-
-## 請勿使用已淘汰或有漏洞的 Express 版本
-
-Express 2.x and 3.x are no longer maintained. Security and performance issues in these versions won't be fixed. Do not use them! If you haven't moved to version 4, follow the [migration guide](/{{ page.lang }}/guide/migrating-4.html) or consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-另請確定您沒有使用[「安全更新」頁面](/{{ page.lang }}/advanced/security-updates.html)中列出的任何有漏洞的 Express 版本。若有使用，請更新為其中一個穩定版本，最好是最新版本。 If you are, update to one of the stable releases, preferably the latest.
-
-## 使用 TLS
-
-If your app deals with or transmits sensitive data, use [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) (TLS) to secure the connection and the data. This technology encrypts data before it is sent from the client to the server, thus preventing some common (and easy) hacks. Although Ajax and POST requests might not be visibly obvious and seem "hidden" in browsers, their network traffic is vulnerable to [packet sniffing](https://en.wikipedia.org/wiki/Packet_analyzer) and [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack).
-
-You may be familiar with Secure Socket Layer (SSL) encryption. [TLS is simply the next progression of SSL](https://msdn.microsoft.com/en-us/library/windows/desktop/aa380515\(v=vs.85\).aspx). In other words, if you were using SSL before, consider upgrading to TLS. In general, we recommend Nginx to handle TLS. For a good reference to configure TLS on Nginx (and other servers), see [Recommended Server Configurations (Mozilla Wiki)](https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Server_Configurations).
-
-此外，可方便您取得免費 TLS 憑證的工具是 [Let's Encrypt](https://letsencrypt.org/about/)，這是一個免費的自動化開放憑證管理中心 (CA)，由 [Internet Security Research Group (ISRG)](https://letsencrypt.org/isrg/) 提供。
-
-## Do not trust user input
-
-For web applications, one of the most critical security requirements is proper user input validation and handling. This comes in many forms and we will not cover all of them here.
-Ultimately, the responsibility for validating and correctly handling the types of user input your application accepts is yours.
-
-### Prevent open redirects
-
-An example of potentially dangerous user input is an _open redirect_, where an application accepts a URL as user input (often in the URL query, for example `?url=https://example.com`) and uses `res.redirect` to set the `location` header and
-return a 3xx status.
-
-An application must validate that it supports redirecting to the incoming URL to avoid sending users to malicious links such as phishing websites, among other risks.
-
-Here is an example of checking URLs before using `res.redirect` or `res.location`:
-
-```js
-app.use((req, res) => {
-  try {
-    if (new Url(req.query.url).host !== 'example.com') {
-      return res.status(400).end(`Unsupported redirect to host: ${req.query.url}`)
-    }
-  } catch (e) {
-    return res.status(400).end(`Invalid url: ${req.query.url}`)
-  }
-  res.redirect(req.query.url)
-})
-```
-
-## 使用 Helmet
-
-[Helmet](https://www.npmjs.com/package/helmet) 會適當設定 HTTP 標頭，有助於防範您的應用程式出現已知的 Web 漏洞。
-
-Helmet is a middleware function that sets security-related HTTP response headers. Helmet sets the following headers by default:
-
-- `Content-Security-Policy`: A powerful allow-list of what can happen on your page which mitigates many attacks
-- `Cross-Origin-Opener-Policy`: Helps process-isolate your page
-- `Cross-Origin-Resource-Policy`: Blocks others from loading your resources cross-origin
-- `Origin-Agent-Cluster`: Changes process isolation to be origin-based
-- `Referrer-Policy`: Controls the [`Referer`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referer) header
-- `Strict-Transport-Security`: Tells browsers to prefer HTTPS
-- `X-Content-Type-Options`: Avoids [MIME sniffing](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#mime_sniffing)
-- `X-DNS-Prefetch-Control`: Controls DNS prefetching
-- `X-Download-Options`: Forces downloads to be saved (Internet Explorer only)
-- `X-Frame-Options`: Legacy header that mitigates [Clickjacking](https://en.wikipedia.org/wiki/Clickjacking) attacks
-- `X-Permitted-Cross-Domain-Policies`: Controls cross-domain behavior for Adobe products, like Acrobat
-- `X-Powered-By`: Info about the web server. Removed because it could be used in simple attacks
-- `X-XSS-Protection`: Legacy header that tries to mitigate [XSS attacks](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting), but makes things worse, so Helmet disables it
-
-Each header can be configured or disabled. To read more about it please go to [its documentation website][helmet].
-
-安裝 Helmet 等之類的其他任何模組：
-
-```bash
-$ npm install helmet
-```
-
-然後在您的程式碼中使用它：
-
-```js
-// ...
-
-const helmet = require('helmet')
-app.use(helmet())
-
-// ...
-```
-
-## Reduce fingerprinting
-
-It can help to provide an extra layer of security to reduce the ability of attackers to determine
-the software that a server uses, known as "fingerprinting." Though not a security issue itself,
-reducing the ability to fingerprint an application improves its overall security posture.
-Server software can be fingerprinted by quirks in how it responds to specific requests, for example in
-the HTTP response headers.
-
-By default, Express sends the `X-Powered-By` response header that you can
-disable using the `app.disable()` method:
-
-```js
-app.disable('x-powered-by')
-```
-
-{% capture powered-advisory %}
-
-Disabling the `X-Powered-By header` does not prevent
-a sophisticated attacker from determining that an app is running Express. It may
-discourage a casual exploit, but there are other ways to determine an app is running
-Express.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=powered-advisory %}
-
-Express also sends its own formatted "404 Not Found" messages and formatter error
-response messages. These can be changed by
-[adding your own not found handler](/en/starter/faq.html#how-do-i-handle-404-responses)
-and
-[writing your own error handler](/en/guide/error-handling.html#writing-error-handlers):
-
-```js
-// last app.use calls right before app.listen():
-
-// custom 404
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-
-// custom error handler
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-## 安全地使用 Cookie
-
-為了確保 Cookie 不會開啟您的應用程式進行惡意探索，請勿使用預設階段作業 Cookie 名稱，並適當設定 Cookie 安全選項。
-
-以下是兩個主要的中介軟體 Cookie 階段作業模組：
-
-- [express-session](https://www.npmjs.com/package/express-session)，取代了 Express 3.x 內建的 `express.session` 中介軟體。
-- [cookie-session](https://www.npmjs.com/package/cookie-session)，取代了 Express 3.x 內建的 `express.cookieSession` 中介軟體。
-
-這兩個模組之間的主要差異是它們儲存 Cookie 階段作業資料的方式。[express-session](https://www.npmjs.com/package/express-session) 中介軟體會將階段作業資料儲存在伺服器上；
-它只將階段作業 ID（而非階段作業資料）儲存在 Cookie 本身中。依預設，它使用記憶體內儲存體，且並非設計成用於正式作業環境。在正式作業中，您需要設定可調式階段作業儲存庫；
-請參閱[相容的階段作業儲存庫](https://github.com/expressjs/session#compatible-session-stores)清單。 The [express-session](https://www.npmjs.com/package/express-session) middleware stores session data on the server; it only saves the session ID in the cookie itself, not session data. By default, it uses in-memory storage and is not designed for a production environment. In production, you'll need to set up a scalable session-store; see the list of [compatible session stores](https://github.com/expressjs/session#compatible-session-stores).
-
-In contrast, [cookie-session](https://www.npmjs.com/package/cookie-session) middleware implements cookie-backed storage: it serializes the entire session to the cookie, rather than just a session key. Only use it when session data is relatively small and easily encoded as primitive values (rather than objects). Although browsers are supposed to support at least 4096 bytes per cookie, to ensure you don't exceed the limit, don't exceed a size of 4093 bytes per domain. Also, be aware that the cookie data will be visible to the client, so if there is any reason to keep it secure or obscure, then `express-session` may be a better choice.
-
-### 請勿使用預設階段作業 Cookie 名稱
-
-Using the default session cookie name can open your app to attacks. The security issue posed is similar to `X-Powered-By`: a potential attacker can use it to fingerprint the server and target attacks accordingly.
-
-為了避免發生此問題，請使用通用 Cookie 名稱；
-例如，使用 [express-session](https://www.npmjs.com/package/express-session) 中介軟體：
-
-```js
-const session = require('express-session')
-app.set('trust proxy', 1) // trust first proxy
-app.use(session({
-  secret: 's3Cur3',
-  name: 'sessionId'
-}))
-```
-
-### 設定 Cookie 安全選項
-
-設定下列 Cookie 選項來加強安全：
-
-- `secure` - 確保瀏覽器只透過 HTTPS 傳送 Cookie。
-- `httpOnly` - 確保只透過 HTTP(S) 傳送 Cookie，而不透過用戶端 JavaScript 傳送，如此有助於防範跨網站 Scripting 攻擊。
-- `domain` - indicates the domain of the cookie; use it to compare against the domain of the server in which the URL is being requested. If they match, then check the path attribute next.
-- `path` - 指出 Cookie 的路徑；用來與要求路徑相互比較。如果此項與網域相符，則會傳送要求中的 Cookie。 If this and domain match, then send the cookie in the request.
-- `expires` - 用來設定持續性 Cookie 的到期日。
-
-下列範例使用 [cookie-session](https://www.npmjs.com/package/cookie-session) 中介軟體：
-
-```js
-const session = require('cookie-session')
-const express = require('express')
-const app = express()
-
-const expiryDate = new Date(Date.now() + 60 * 60 * 1000) // 1 hour
-app.use(session({
-  name: 'session',
-  keys: ['key1', 'key2'],
-  cookie: {
-    secure: true,
-    httpOnly: true,
-    domain: 'example.com',
-    path: 'foo/bar',
-    expires: expiryDate
-  }
-}))
-```
-
-## Prevent brute-force attacks against authorization
-
-Make sure login endpoints are protected to make private data more secure.
-
-A simple and powerful technique is to block authorization attempts using two metrics:
-
-1. The number of consecutive failed attempts by the same user name and IP address.
-2. The number of failed attempts from an IP address over some long period of time. For example, block an IP address if it makes 100 failed attempts in one day.
-
-[rate-limiter-flexible](https://github.com/animir/node-rate-limiter-flexible) package provides tools to make this technique easy and fast. You can find [an example of brute-force protection in the documentation](https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#login-endpoint-protection)
-
-## Ensure your dependencies are secure
-
-Using npm to manage your application's dependencies is powerful and convenient. But the packages that you use may contain critical security vulnerabilities that could also affect your application. The security of your app is only as strong as the "weakest link" in your dependencies.
-
-Since npm@6, npm automatically reviews every install request. Also, you can use `npm audit` to analyze your dependency tree.
-
-```bash
-$ npm audit
-```
-
-If you want to stay more secure, consider [Snyk](https://snyk.io/).
-
-Snyk offers both a [command-line tool](https://www.npmjs.com/package/snyk) and a [Github integration](https://snyk.io/docs/github) that checks your application against [Snyk's open source vulnerability database](https://snyk.io/vuln/) for any known vulnerabilities in your dependencies. Install the CLI as follows:
-
-```bash
-$ npm install -g snyk
-$ cd your-app
-```
-
-Use this command to test your application for vulnerabilities:
-
-```bash
-$ snyk test
-```
-
-### 避免其他已知的漏洞
-
-Keep an eye out for [Node Security Project](https://npmjs.com/advisories) or [Snyk](https://snyk.io/vuln/) advisories that may affect Express or other modules that your app uses. In general, these databases are excellent resources for knowledge and tools about Node security.
-
-Finally, Express apps&mdash;like any other web apps&mdash;can be vulnerable to a variety of web-based attacks. Familiarize yourself with known [web vulnerabilities](https://www.owasp.org/www-project-top-ten/) and take precautions to avoid them.
-
-## 其他注意事項
-
-以下是優異的 [Node.js Security Checklist](https://blog.risingstack.com/node-js-security-checklist/) 所提供的進一步建議。如需這些建議的所有詳細資料，請參閱該部落格文章： Refer to that blog post for all the details on these recommendations:
-
-- 一律對使用者輸入進行過濾和消毒，來防範跨網站 Scripting (XSS) 和指令注入攻擊。
-- 使用參數化查詢或備妥陳述式，來防禦 SQL 注入攻擊。
-- 使用開放程式碼 [sqlmap](http://sqlmap.org/) 工具，來偵測您應用程式中的 SQL 注入漏洞。
-- 使用 [nmap](https://nmap.org/) 和 [sslyze](https://github.com/nabla-c0d3/sslyze) 工具，來測試您 SSL 密碼、金鑰和重新協議的配置，以及測試您憑證的有效性。
-- 使用 [safe-regex](https://www.npmjs.com/package/safe-regex)，確定您的正規表示式不易受到[正規表示式阻斷服務](https://www.owasp.org/index.php/Regular_expression_Denial_of_Service_-_ReDoS)攻擊。
-
-[helmet]: <如果您使用 `helmet.js`，自會為您處理此事。>
\ No newline at end of file
diff --git a/zh-tw/advanced/developing-template-engines.md b/zh-tw/advanced/developing-template-engines.md
deleted file mode 100644
index 989b444ca6..0000000000
--- a/zh-tw/advanced/developing-template-engines.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-layout: page
-title: 開發 Express 範本引擎
-description: Learn how to develop custom template engines for Express.js using app.engine(), with examples on creating and integrating your own template rendering logic.
-menu: advanced
-order: 1
-redirect_from: "  "
----
-
-# 開發 Express 範本引擎
-
-利用 `app.engine(ext, callback)` 方法，來建立您自己的範本引擎。`ext` 是指副檔名，`callback` 是範本引擎函數，它可接受下列項目作為參數：檔案的位置、options 物件，以及回呼函數。 `ext` refers to the file extension, and `callback` is the template engine function, which accepts the following items as parameters: the location of the file, the options object, and the callback function.
-
-下列程式碼範例說明如何實作一個相當簡單的範本引擎，以呈現 `.ntl` 檔。
-
-```js
-const fs = require('fs') // this engine requires the fs module
-app.engine('ntl', (filePath, options, callback) => { // define the template engine
-  fs.readFile(filePath, (err, content) => {
-    if (err) return callback(err)
-    // this is an extremely simple template engine
-    const rendered = content.toString()
-      .replace('#title#', `<title>${options.title}</title>`)
-      .replace('#message#', `<h1>${options.message}</h1>`)
-    return callback(null, rendered)
-  })
-})
-app.set('views', './views') // specify the views directory
-app.set('view engine', 'ntl') // register the template engine
-```
-
-Your app will now be able to render `.ntl` files. 現在，您的應用程式能夠呈現 `.ntl` 檔。請在 `views` 目錄中建立一個名稱是 `index.ntl` 的檔案，內含下列內容。
-
-```pug
-#title#
-#message#
-```
-
-Then, create the following route in your app.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-當您向首頁提出要求時，`index.ntl` 會呈現成 HTML。
\ No newline at end of file
diff --git a/zh-tw/advanced/healthcheck-graceful-shutdown.md b/zh-tw/advanced/healthcheck-graceful-shutdown.md
deleted file mode 100644
index 8207887225..0000000000
--- a/zh-tw/advanced/healthcheck-graceful-shutdown.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-layout: page
-title: Health Checks and Graceful Shutdown
-description: Learn how to implement health checks and graceful shutdown in Express apps to enhance reliability, manage deployments, and integrate with load balancers like Kubernetes.
-menu: advanced
-order: 5
-redirect_from: "  "
----
-
-# Health Checks and Graceful Shutdown
-
-## Graceful shutdown
-
-When you deploy a new version of your application, you must replace the previous version. The process manager you're using will first send a SIGTERM signal to the application to notify it that it will be killed. Once the application gets this signal, it should stop accepting new requests, finish all the ongoing requests, clean up the resources it used,  including database connections and file locks then exit.
-
-### 範例
-
-```js
-const server = app.listen(port)
-
-process.on('SIGTERM', () => {
-  debug('SIGTERM signal received: closing HTTP server')
-  server.close(() => {
-    debug('HTTP server closed')
-  })
-})
-```
-
-## Health checks
-
-A load balancer uses health checks to determine if an application instance is healthy and can accept requests. For example, [Kubernetes has two health checks](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/):
-
-- `liveness`, that determines when to restart a container.
-- `readiness`, that determines when a container is ready to start accepting traffic. When a pod is not ready, it is removed from the service load balancers.
\ No newline at end of file
diff --git a/zh-tw/advanced/security-updates.md b/zh-tw/advanced/security-updates.md
deleted file mode 100644
index c3b10b6c91..0000000000
--- a/zh-tw/advanced/security-updates.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-layout: page
-title: Express 安全更新
-description: Review the latest security updates and patches for Express.js, including detailed vulnerability lists for different versions to help maintain a secure application.
-menu: advanced
-order: 2
-redirect_from: "  "
----
-
-# 安全更新
-
-<div class="doc-box doc-notice" markdown="1">
-
-Node.js 的漏洞會直接影響 Express。因此，請[隨時監看 Node.js 漏洞](https://nodejs.org
-/en/blog/vulnerability/)，並確保您所用的是最新的 Node.js 穩定版本。
- Therefore, [keep a watch on Node.js vulnerabilities](https://nodejs.org/en/blog/vulnerability/) and make sure you are using the latest stable version of Node.js.
-</div>
-
-以下列舉已在指定的版本更新中修正的 Express 漏洞。
-
-{% capture security-policy %}
-If you believe you have discovered a security vulnerability in Express, please see
-[Security Policies and Procedures](/{{page.lang}}/resources/contributing.html#security-policies-and-procedures).
-{% endcapture %}
-
-{% include admonitions/note.html content=security-policy %}
-
-## 4.x
-
-- 4.21.2
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-rhx6-c78j-4q9w).
-- 4.21.1
-  - The dependency `cookie` has been updated to address a [vulnerability](https://github.com/jshttp/cookie/security/advisories/GHSA-pxg6-pf52-xh8x), This may affect your application if you use `res.cookie`.
-- 4.20.0
-  - Fixed XSS vulnerability in `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-qw6h-vgh9-j6wx), [CVE-2024-43796](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43796)).
-  - The dependency `serve-static` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-cm22-4g7w-348p).
-  - The dependency `send` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-m6fv-jmcg-4jfg).
-  - The dependency `path-to-regexp` has been updated to address a [vulnerability](https://github.com/pillarjs/path-to-regexp/security/advisories/GHSA-9wv6-86v2-598j).
-  - The dependency `body-parser` has been updated to addres a [vulnerability](https://github.com/advisories/GHSA-qwcr-r2fm-qrc7), This may affect your application if you had url enconding activated.
-- 4.19.0, 4.19.1
-  - Fixed open redirect vulnerability in `res.location` and `res.redirect` ([advisory](https://github.com/expressjs/express/security/advisories/GHSA-rv95-896h-c2vc), [CVE-2024-29041](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-29041)).
-- 4.17.3
-  - The dependency `qs` has been updated to address a [vulnerability](https://github.com/advisories/GHSA-hrpp-h998-j3pp). This may affect your application if the following APIs are used: `req.query`, `req.body`, `req.param`.
-- 4.16.0
-  - The dependency `forwarded` has been updated to address a [vulnerability](https://npmjs.com/advisories/527). This may affect your application if the following APIs are used: `req.host`, `req.hostname`, `req.ip`, `req.ips`, `req.protocol`.
-  - The dependency `mime` has been updated to address a [vulnerability](https://npmjs.com/advisories/535), but this issue does not impact Express.
-  - The dependency `send` has been updated to provide a protection against a [Node.js 8.5.0 vulnerability](https://nodejs.org/en/blog/vulnerability/september-2017-path-validation/). This only impacts running Express on the specific Node.js version 8.5.0.
-- 4.15.5
-  - The dependency `debug` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:debug:20170905), but this issue does not impact Express.
-  - The dependency `fresh` has been updated to address a [vulnerability](https://npmjs.com/advisories/526). This will affect your application if the following APIs are used: `express.static`, `req.fresh`, `res.json`, `res.jsonp`, `res.send`, `res.sendfile` `res.sendFile`, `res.sendStatus`.
-- 4.15.3
-  - The dependency `ms` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:ms:20170412). This may affect your application if untrusted string input is passed to the `maxAge` option in the following APIs: `express.static`, `res.sendfile`, and `res.sendFile`.
-- 4.15.2
-  - The dependency `qs` has been updated to address a [vulnerability](https://snyk.io/vuln/npm:qs:20170213), but this issue does not impact Express. Updating to 4.15.2 is a good practice, but not required to address the vulnerability.
-- 4.11.1
-  - 已修正 `express.static`、`res.sendfile` 和 `res.sendFile` 中的根路徑揭露漏洞
-- 4.10.7
-  - 已修正 `express.static`（[諮詢](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)）中的開放重新導向漏洞。
-- 4.8.8
-  - 已修正 `express.static`（[諮詢](http://npmjs.com/advisories/32)、[CVE-2014-6394](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6394)）中的目錄遍訪漏洞。
-- 4.8.4
-  - 在某些情況下，Node.js 0.10 可能洩漏 `fd`，而影響 `express.static` 和 `res.sendfile`。惡意的要求可能造成 `fd` 洩漏，最後導致 `EMFILE` 錯誤和伺服器無回應。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 4.8.0
-  - 如果稀疏陣列在查詢字串中的索引過多，可能導致程序耗盡記憶體，而使伺服器當機。
-  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
-
-## 3.x
-
-  <div class="doc-box doc-warn" markdown="1">
-  **Express 3.x 已不再維護**
-
-Known and unknown security and performance issues in 3.x have not been addressed since the last update (1 August, 2015). It is highly recommended to use the latest version of Express.
-
-If you are unable to upgrade past 3.x, please consider [Commercial Support Options](/{{ page.lang }}/support#commercial-support-options).
-
-  </div>
-
-- 3.19.1
-  - 已修正 `express.static`、`res.sendfile` 和 `res.sendFile` 中的根路徑揭露漏洞
-- 3.19.0
-  - 已修正 `express.static`（[諮詢](https://npmjs.com/advisories/35)、[CVE-2015-1164](http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1164)）中的開放重新導向漏洞。
-- 3.16.10
-  - 已修正 `express.static` 中的目錄遍訪漏洞。
-- 3.16.6
-  - 在某些情況下，Node.js 0.10 可能洩漏 `fd`，而影響 `express.static` 和 `res.sendfile`。惡意的要求可能造成 `fd` 洩漏，最後導致 `EMFILE` 錯誤和伺服器無回應。 Malicious requests could cause `fd`s to leak and eventually lead to `EMFILE` errors and server unresponsiveness.
-- 3.16.0
-  - 如果稀疏陣列在查詢字串中的索引過多，可能導致程序耗盡記憶體，而使伺服器當機。
-  - Extremely nested query string objects could cause the process to block and make the server unresponsive temporarily.
-- 3.3.0
-  - 404 回應（試圖進行不支援的方法置換）容易受到跨網站 Scripting 攻擊。
\ No newline at end of file
diff --git a/zh-tw/api.md b/zh-tw/api.md
deleted file mode 100644
index 4075da84b0..0000000000
--- a/zh-tw/api.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-layout: api
-version: 5x
-title: Express 5.x - API 參照
-description: Access the API reference for Express.js detailing all modules, methods, and properties for building web applications with this version.
-menu: api
-redirect_from: "  "
----
-
-<div id="api-doc" markdown="1">
-  <h1>5.x API</h1><a id='express' class='h2'></a>
-  {% include api/en/5x/express.md %}
-  <a id='app' class='h2'></a>
-  {% include api/en/5x/app.md %}
-  <a id='req' class='h2'></a>
-  {% include api/en/5x/req.md %}
-  <a id='res' class='h2'></a>
-  {% include api/en/5x/res.md %}
-  <a id='router' class='h2'></a>
-  {% include api/en/5x/router.md %}
-</div>
diff --git a/zh-tw/changelog/index.md b/zh-tw/changelog/index.md
deleted file mode 100644
index c03940c3e7..0000000000
--- a/zh-tw/changelog/index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-layout: page
-title: Express changelog
-description: Stay updated with the release changelog for Express.js, detailing new features, bug fixes, and important changes across versions.
-sitemap: false
-redirect_from:
-  - "  "
-  - "  "
-redirect_to: https://github.com/expressjs/express/releases
----
diff --git a/zh-tw/guide/behind-proxies.md b/zh-tw/guide/behind-proxies.md
deleted file mode 100644
index 01acc0757d..0000000000
--- a/zh-tw/guide/behind-proxies.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-layout: page
-title: 位於 Proxy 背後的 Express
-description: Learn how to configure Express.js applications to work correctly behind reverse proxies, including using the trust proxy setting to handle client IP addresses.
-menu: guide
-order: 8
-redirect_from: "  "
----
-
-# 位於 Proxy 背後的 Express
-
-When running an Express app behind a reverse proxy, some of the Express APIs may return different values than expected. In order to adjust for this, the `trust proxy` application setting may be used to expose information provided by the reverse proxy in the Express APIs. The most common issue is express APIs that expose the client's IP address may instead show an internal IP address of the reverse proxy.
-
-<div class="doc-box doc-info" markdown="1">
-When configuring the `trust proxy` setting, it is important to understand the exact setup of the reverse proxy. Since this setting will trust values provided in the request, it is important that the combination of the setting in Express matches how the reverse proxy operates.
-</div>
-
-The application setting `trust proxy` may be set to one of the values listed in the following table.
-
-<table class="doctable" border="1" markdown="1">
-  <thead><tr><th>類型</th><th>值</th></tr></thead>
-  <tbody>
-    <tr>
-      <td>布林</td>
-<td markdown="1">
-若為 `true`，會將用戶端的 IP 位址視為 `X-Forwarded-*` 標頭中的最左側項目。
-
-若為 `false`，會將應用程式視為直接面對網際網路，且用戶端的 IP 位址衍生自 `req.connection.remoteAddress`。這是預設值。 This is the default setting.
-
-<div class="doc-box doc-warn" markdown="1">
-When setting to `true`, it is important to ensure that the last reverse proxy trusted is removing/overwriting all of the following HTTP headers: `X-Forwarded-For`, `X-Forwarded-Host`, and `X-Forwarded-Proto`, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>IP addresses</td>
-<td markdown="1">
-An IP address, subnet, or an array of IP addresses and subnets to trust as being a reverse proxy. The following list shows the pre-configured subnet names:
-
-- loopback - `127.0.0.1/8`、`::1/128`
-- linklocal - `169.254.0.0/16`、`fe80::/10`
-- uniquelocal - `10.0.0.0/8`、`172.16.0.0/12`、`192.168.0.0/16`、`fc00::/7`
-
-您可以採下列任何方式來設定 IP 位址：
-
-```js
-app.set('trust proxy', 'loopback') // specify a single subnet
-app.set('trust proxy', 'loopback, 123.123.123.123') // specify a subnet and an address
-app.set('trust proxy', 'loopback, linklocal, uniquelocal') // specify multiple subnets as CSV
-app.set('trust proxy', ['loopback', 'linklocal', 'uniquelocal']) // specify multiple subnets as an array
-```
-
-When specified, the IP addresses or the subnets are excluded from the address determination process, and the untrusted IP address nearest to the application server is determined as the client's IP address. This works by checking if `req.socket.remoteAddress` is trusted. If so, then each address in `X-Forwarded-For` is checked from right to left until the first non-trusted address.
-
-</td>
-    </tr>
-    <tr>
-      <td>號碼</td>
-<td markdown="1">
-Use the address that is at most `n` number of hops away from the Express application. `req.socket.remoteAddress` is the first hop, and the rest are looked for in the `X-Forwarded-For` header from right to left. A value of `0` means that the first untrusted address would be `req.socket.remoteAddress`, i.e. there is no reverse proxy.
-
-<div class="doc-box doc-warn" markdown="1">
-When using this setting, it is important to ensure there are not multiple, different-length paths to the Express application such that the client can be less than the configured number of hops away, otherwise it may be possible for the client to provide any value.
-</div>
-</td>
-    </tr>
-    <tr>
-      <td>Function</td>
-<td markdown="1">
-Custom trust implementation.
-
-```js
-app.set('trust proxy', (ip) => {
-  if (ip === '127.0.0.1' || ip === '123.123.123.123') return true // trusted IPs
-  else return false
-})
-```
-
-</td>
-    </tr>
-  </tbody>
-</table>
-
-Enabling `trust proxy` will have the following impact:
-
-<ul>
-  <li markdown="1">[req.hostname](/{{ page.lang }}/api.html#req.hostname) 值會衍生自 `X-Forwarded-Host` 標頭中所設定的值，且該值可能由用戶端或 Proxy 所設定。
-  </li>
-  <li markdown="1">反向 Proxy 可能設定 `X-Forwarded-Proto`，以告知應用程式它是 `https` 或 `http` 或甚至是無效的名稱。[req.protocol](/{{ page.lang }}/api.html#req.protocol) 會反映此值。
-   This value is reflected by [req.protocol](/{{ page.lang }}/api.html#req.protocol).
-  </li>
-  <li markdown="1">[req.ip](/{{ page.lang }}/api.html#req.ip) 和 [req.ips](/{{ page.lang }}/api.html#req.ips) 值中會移入 `X-Forwarded-For` 中的位址清單。
-  </li>
-</ul>
-
-會使用 [proxy-addr](https://www.npmjs.com/package/proxy-addr) 套件來實作 `trust proxy` 設定。如需相關資訊，請參閱其說明文件。 For more information, see its documentation.
diff --git a/zh-tw/guide/database-integration.md b/zh-tw/guide/database-integration.md
deleted file mode 100644
index ea1a215693..0000000000
--- a/zh-tw/guide/database-integration.md
+++ /dev/null
@@ -1,506 +0,0 @@
----
-layout: page
-title: Express 資料庫整合
-description: Discover how to integrate various databases with Express.js applications, including setup examples for MongoDB, MySQL, PostgreSQL, and more.
-menu: guide
-order: 11
-redirect_from: "  "
----
-
-# 資料庫整合
-
-Adding the capability to connect databases to Express apps is just a matter of loading an appropriate Node.js driver for the database in your app. This document briefly explains how to add and use some of the most popular Node.js modules for database systems in your Express app:
-
-- [Cassandra](#cassandra)
-- [Couchbase](#couchbase)
-- [CouchDB](#couchdb)
-- [LevelDB](#leveldb)
-- [MySQL](#mysql)
-- [MongoDB](#mongo)
-- [Neo4j](#neo4j)
-- [Oracle](#oracle)
-- [PostgreSQL](#postgres)
-- [Redis](#redis)
-- <a name="mysql"></a>
-- [SQLite](#sqlite)
-- [ElasticSearch](#elasticsearch)
-
-<div class="doc-box doc-notice" markdown="1">
-These database drivers are among many that are available. For other options,
-search on the [npm](https://www.npmjs.com/) site.
-</div>
-
-## Cassandra
-
-**模組**：[cassandra-driver](https://github.com/datastax/nodejs-driver)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install cassandra-driver
-```
-
-### 範例
-
-```js
-const cassandra = require('cassandra-driver')
-const client = new cassandra.Client({ contactPoints: ['localhost'] })
-
-client.execute('select key from system.local', (err, result) => {
-  if (err) throw err
-  console.log(result.rows[0])
-})
-```
-
-## Couchbase
-
-**Module**: [couchnode](https://github.com/couchbase/couchnode)
-
-### Installation
-
-```bash
-$ npm install couchbase
-```
-
-### 範例
-
-```js
-const couchbase = require('couchbase')
-const bucket = (new couchbase.Cluster('http://localhost:8091')).openBucket('bucketName')
-
-// add a document to a bucket
-bucket.insert('document-key', { name: 'Matt', shoeSize: 13 }, (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-
-// get all documents with shoe size 13
-const n1ql = 'SELECT d.* FROM `bucketName` d WHERE shoeSize = $1'
-const query = N1qlQuery.fromString(n1ql)
-bucket.query(query, [13], (err, result) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(result)
-  }
-})
-```
-
-## CouchDB
-
-**模組**：[nano](https://github.com/dscape/nano)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install nano
-```
-
-### 範例
-
-```js
-const nano = require('nano')('http://localhost:5984')
-nano.db.create('books')
-const books = nano.db.use('books')
-
-// Insert a book document in the books database
-books.insert({ name: 'The Art of war' }, null, (err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body)
-  }
-})
-
-// Get a list of all books
-books.list((err, body) => {
-  if (err) {
-    console.log(err)
-  } else {
-    console.log(body.rows)
-  }
-})
-```
-
-## LevelDB
-
-**模組**：[levelup](https://github.com/rvagg/node-levelup)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install level levelup leveldown
-```
-
-### 範例
-
-```js
-const levelup = require('levelup')
-const db = levelup('./mydb')
-
-db.put('name', 'LevelUP', (err) => {
-  if (err) return console.log('Ooops!', err)
-
-  db.get('name', (err, value) => {
-    if (err) return console.log('Ooops!', err)
-
-    console.log(`name=${value}`)
-  })
-})
-```
-
-## MySQL
-
-**模組**：[mysql](https://github.com/felixge/node-mysql/)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install mysql
-```
-
-### 範例
-
-```js
-const mysql = require('mysql')
-const connection = mysql.createConnection({
-  host: 'localhost',
-  user: 'dbuser',
-  password: 's3kreee7',
-  database: 'my_db'
-})
-
-connection.connect()
-
-connection.query('SELECT 1 + 1 AS solution', (err, rows, fields) => {
-  if (err) throw err
-
-  console.log('The solution is: ', rows[0].solution)
-})
-
-connection.end()
-```
-
-## MongoDB
-
-**模組**：[mongodb](https://github.com/mongodb/node-mongodb-native)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install mongodb
-```
-
-### Example (v2.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, db) => {
-  if (err) throw err
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-### Example (v3.\*)
-
-```js
-const MongoClient = require('mongodb').MongoClient
-
-MongoClient.connect('mongodb://localhost:27017/animals', (err, client) => {
-  if (err) throw err
-
-  const db = client.db('animals')
-
-  db.collection('mammals').find().toArray((err, result) => {
-    if (err) throw err
-
-    console.log(result)
-  })
-})
-```
-
-如果您需要 MongoDB 物件模型驅動程式，請查看 [Mongoose](https://github.com/LearnBoost/mongoose)。
-
-## Neo4j
-
-這些資料庫驅動程式只是眾多可用驅動程式中的一部分。如需其他選項，請在 [npm](https://www.npmjs.com/) 網站中搜尋。
-
-### Installation
-
-```bash
-$ npm install neo4j-driver
-```
-
-### 範例
-
-```js
-const neo4j = require('neo4j-driver')
-const driver = neo4j.driver('neo4j://localhost:7687', neo4j.auth.basic('neo4j', 'letmein'))
-
-const session = driver.session()
-
-session.readTransaction((tx) => {
-  return tx.run('MATCH (n) RETURN count(n) AS count')
-    .then((res) => {
-      console.log(res.records[0].get('count'))
-    })
-    .catch((error) => {
-      console.log(error)
-    })
-})
-```
-
-## Oracle
-
-**Module**: [oracledb](https://github.com/oracle/node-oracledb)
-
-### Installation
-
-NOTE: [See installation prerequisites](https://github.com/oracle/node-oracledb#-installation).
-
-```bash
-$ npm install oracledb
-```
-
-### 範例
-
-```js
-const oracledb = require('oracledb')
-const config = {
-  user: '<your db user>',
-  password: '<your db password>',
-  connectString: 'localhost:1521/orcl'
-}
-
-async function getEmployee (empId) {
-  let conn
-
-  try {
-    conn = await oracledb.getConnection(config)
-
-    const result = await conn.execute(
-      'select * from employees where employee_id = :id',
-      [empId]
-    )
-
-    console.log(result.rows[0])
-  } catch (err) {
-    console.log('Ouch!', err)
-  } finally {
-    if (conn) { // conn assignment worked, need to close
-      await conn.close()
-    }
-  }
-}
-
-getEmployee(101)
-```
-
-## PostgreSQL
-
-**模組**：[pg-promise](https://github.com/vitaly-t/pg-promise)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install pg-promise
-```
-
-### 範例
-
-```js
-const pgp = require('pg-promise')(/* options */)
-const db = pgp('postgres://username:password@host:port/database')
-
-db.one('SELECT $1 AS value', 123)
-  .then((data) => {
-    console.log('DATA:', data.value)
-  })
-  .catch((error) => {
-    console.log('ERROR:', error)
-  })
-```
-
-## Redis
-
-**模組**：[redis](https://github.com/mranney/node_redis)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install redis
-```
-
-### 範例
-
-```js
-const redis = require('redis')
-const client = redis.createClient()
-
-client.on('error', (err) => {
-  console.log(`Error ${err}`)
-})
-
-client.set('string key', 'string val', redis.print)
-client.hset('hash key', 'hashtest 1', 'some value', redis.print)
-client.hset(['hash key', 'hashtest 2', 'some other value'], redis.print)
-
-client.hkeys('hash key', (err, replies) => {
-  console.log(`${replies.length} replies:`)
-
-  replies.forEach((reply, i) => {
-    console.log(`    ${i}: ${reply}`)
-  })
-
-  client.quit()
-})
-```
-
-## SQL Server
-
-**Module**: [tedious](https://github.com/tediousjs/tedious)
-
-### Installation
-
-```bash
-$ npm install tedious
-```
-
-### 範例
-
-```js
-const Connection = require('tedious').Connection
-const Request = require('tedious').Request
-
-const config = {
-  server: 'localhost',
-  authentication: {
-    type: 'default',
-    options: {
-      userName: 'your_username', // update me
-      password: 'your_password' // update me
-    }
-  }
-}
-
-const connection = new Connection(config)
-
-connection.on('connect', (err) => {
-  if (err) {
-    console.log(err)
-  } else {
-    executeStatement()
-  }
-})
-
-function executeStatement () {
-  request = new Request("select 123, 'hello world'", (err, rowCount) => {
-    if (err) {
-      console.log(err)
-    } else {
-      console.log(`${rowCount} rows`)
-    }
-    connection.close()
-  })
-
-  request.on('row', (columns) => {
-    columns.forEach((column) => {
-      if (column.value === null) {
-        console.log('NULL')
-      } else {
-        console.log(column.value)
-      }
-    })
-  })
-
-  connection.execSql(request)
-}
-```
-
-## SQLite
-
-**模組**：[sqlite3](https://github.com/mapbox/node-sqlite3)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install sqlite3
-```
-
-### 範例
-
-```js
-const sqlite3 = require('sqlite3').verbose()
-const db = new sqlite3.Database(':memory:')
-
-db.serialize(() => {
-  db.run('CREATE TABLE lorem (info TEXT)')
-  const stmt = db.prepare('INSERT INTO lorem VALUES (?)')
-
-  for (let i = 0; i < 10; i++) {
-    stmt.run(`Ipsum ${i}`)
-  }
-
-  stmt.finalize()
-
-  db.each('SELECT rowid AS id, info FROM lorem', (err, row) => {
-    console.log(`${row.id}: ${row.info}`)
-  })
-})
-
-db.close()
-```
-
-## ElasticSearch
-
-**模組**：[elasticsearch](https://github.com/elastic/elasticsearch-js)
-**安裝**
-
-### Installation
-
-```bash
-$ npm install elasticsearch
-```
-
-### 範例
-
-```js
-const elasticsearch = require('elasticsearch')
-const client = elasticsearch.Client({
-  host: 'localhost:9200'
-})
-
-client.search({
-  index: 'books',
-  type: 'book',
-  body: {
-    query: {
-      multi_match: {
-        query: 'express js',
-        fields: ['title', 'description']
-      }
-    }
-  }
-}).then((response) => {
-  const hits = response.hits.hits
-}, (error) => {
-  console.trace(error.message)
-})
-```
diff --git a/zh-tw/guide/debugging.md b/zh-tw/guide/debugging.md
deleted file mode 100644
index bb888fcdb0..0000000000
--- a/zh-tw/guide/debugging.md
+++ /dev/null
@@ -1,130 +0,0 @@
----
-layout: page
-title: 對 Express 除錯
-description: Learn how to enable and use debugging logs in Express.js applications by setting the DEBUG environment variable for enhanced troubleshooting.
-menu: guide
-order: 7
-redirect_from: "  "
----
-
-# 對 Express 除錯
-
-如果要查看 Express 中使用的所有內部日誌，在您啟動應用程式時，請將 `DEBUG` 環境變數設為 `express:*`。
-
-```bash
-$ DEBUG=express:* node index.js
-```
-
-在 Windows 中，使用對應指令。
-
-```bash
-> $env:DEBUG = "express:*"; node index.js
-```
-
-對 [express generator](/{{ page.lang }}/starter/generator.html) 產生的預設應用程式執行這個指令，會列印下列輸出：
-
-```bash
-$ DEBUG=express:* node ./bin/www
-  express:router:route new / +0ms
-  express:router:layer new / +1ms
-  express:router:route get / +1ms
-  express:router:layer new / +0ms
-  express:router:route new / +1ms
-  express:router:layer new / +0ms
-  express:router:route get / +0ms
-  express:router:layer new / +0ms
-  express:application compile etag weak +1ms
-  express:application compile query parser extended +0ms
-  express:application compile trust proxy false +0ms
-  express:application booting in development mode +1ms
-  express:router use / query +0ms
-  express:router:layer new / +0ms
-  express:router use / expressInit +0ms
-  express:router:layer new / +0ms
-  express:router use / favicon +1ms
-  express:router:layer new / +0ms
-  express:router use / logger +0ms
-  express:router:layer new / +0ms
-  express:router use / jsonParser +0ms
-  express:router:layer new / +1ms
-  express:router use / urlencodedParser +0ms
-  express:router:layer new / +0ms
-  express:router use / cookieParser +0ms
-  express:router:layer new / +0ms
-  express:router use / stylus +90ms
-  express:router:layer new / +0ms
-  express:router use / serveStatic +0ms
-  express:router:layer new / +0ms
-  express:router use / router +0ms
-  express:router:layer new / +1ms
-  express:router use /users router +0ms
-  express:router:layer new /users +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-  express:router use / &amp;lt;anonymous&amp;gt; +0ms
-  express:router:layer new / +0ms
-```
-
-當對應用程式發出要求時，您會看到 Express 程式碼中指定的日誌：
-
-```bash
-  express:router dispatching GET / +4h
-  express:router query  : / +2ms
-  express:router expressInit  : / +0ms
-  express:router favicon  : / +0ms
-  express:router logger  : / +1ms
-  express:router jsonParser  : / +0ms
-  express:router urlencodedParser  : / +1ms
-  express:router cookieParser  : / +0ms
-  express:router stylus  : / +0ms
-  express:router serveStatic  : / +2ms
-  express:router router  : / +2ms
-  express:router dispatching GET / +1ms
-  express:view lookup "index.pug" +338ms
-  express:view stat "/projects/example/views/index.pug" +0ms
-  express:view render "/projects/example/views/index.pug" +1ms
-```
-
-如果只想查看來自路由器實作的日誌，請將 `DEBUG` 的值設為 `express:router`。同樣地，如果只想查看來自應用程式實作的日誌，請將 `DEBUG` 的值設為 `express:application`，以此類推。 Likewise, to see logs only from the application implementation, set the value of `DEBUG` to `express:application`, and so on.
-
-## `express` 產生的應用程式
-
-`express` 指令產生的應用程式也會使用 `debug` 模組，且其除錯名稱空間的範圍限於應用程式的名稱。
-
-舉例來說，如果您使用 `$ express sample-app` 來產生應用程式，您可以利用下列指令來啟用除錯陳述式：
-
-```bash
-$ DEBUG=sample-app:* node ./bin/www
-```
-
-您可以指派以逗點區隔的名稱清單，來指定多個除錯名稱空間：
-
-```bash
-$ DEBUG=http,mail,express:* node index.js
-```
-
-## Advanced options
-
-When running through Node.js, you can set a few environment variables that will change the behavior of the debug logging:
-
-| Name                | Purpose                                                           |
-| ------------------- | ----------------------------------------------------------------- |
-| `DEBUG`             | Enables/disables specific debugging namespaces.   |
-| `DEBUG_COLORS`      | Whether or not to use colors in the debug output. |
-| `DEBUG_DEPTH`       | Object inspection depth.                          |
-| `DEBUG_FD`          | File descriptor to write debug output to.         |
-| `DEBUG_SHOW_HIDDEN` | Shows hidden properties on inspected objects.     |
-
-{% capture debug-text %}
-
-The environment variables beginning with `DEBUG_` end up being
-converted into an Options object that gets used with `%o`/`%O` formatters.
-See the Node.js documentation for
-[`util.inspect()`](https://nodejs.org/api/util.html#util_util_inspect_object_options)
-for the complete list.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=debug-text %}
diff --git a/zh-tw/guide/error-handling.md b/zh-tw/guide/error-handling.md
deleted file mode 100644
index 8c4145b55d..0000000000
--- a/zh-tw/guide/error-handling.md
+++ /dev/null
@@ -1,293 +0,0 @@
----
-layout: page
-title: Express 錯誤處理
-description: Understand how Express.js handles errors in synchronous and asynchronous code, and learn to implement custom error handling middleware for your applications.
-menu: guide
-order: 6
-redirect_from: "  "
----
-
-# 錯誤處理
-
-_Error Handling_ refers to how Express catches and processes errors that
-occur both synchronously and asynchronously. Express comes with a default error
-handler so you don't need to write your own to get started.
-
-## Catching Errors
-
-It's important to ensure that Express catches all errors that occur while
-running route handlers and middleware.
-
-Errors that occur in synchronous code inside route handlers and middleware
-require no extra work. If synchronous code throws an error, then Express will
-catch and process it. For example:
-
-```js
-app.get('/', (req, res) => {
-  throw new Error('BROKEN') // Express will catch this on its own.
-})
-```
-
-For errors returned from asynchronous functions invoked by route handlers
-and middleware, you must pass them to the `next()` function, where Express will
-catch and process them.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  fs.readFile('/file-does-not-exist', (err, data) => {
-    if (err) {
-      next(err) // Pass errors to Express.
-    } else {
-      res.send(data)
-    }
-  })
-})
-```
-
-Starting with Express 5, route handlers and middleware that return a Promise
-will call `next(value)` automatically when they reject or throw an error.
-For example:
-
-```js
-app.get('/user/:id', async (req, res, next) => {
-  const user = await getUserById(req.params.id)
-  res.send(user)
-})
-```
-
-If `getUserById` throws an error or rejects, `next` will be called with either
-the thrown error or the rejected value. If no rejected value is provided, `next`
-will be called with a default Error object provided by the Express router.
-
-If you pass anything to the `next()` function (except the string `'route'`),
-Express regards the current request as being an error and will skip any
-remaining non-error handling routing and middleware functions.
-
-If the callback in a sequence provides no data, only errors, you can simplify
-this code as follows:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.writeFile('/inaccessible-path', 'data', next)
-  },
-  function (req, res) {
-    res.send('OK')
-  }
-])
-```
-
-In the above example, `next` is provided as the callback for `fs.writeFile`,
-which is called with or without errors. If there is no error, the second
-handler is executed, otherwise Express catches and processes the error.
-
-You must catch errors that occur in asynchronous code invoked by route handlers or
-middleware and pass them to Express for processing. For example:
-
-```js
-app.get('/', (req, res, next) => {
-  setTimeout(() => {
-    try {
-      throw new Error('BROKEN')
-    } catch (err) {
-      next(err)
-    }
-  }, 100)
-})
-```
-
-The above example uses a `try...catch` block to catch errors in the
-asynchronous code and pass them to Express. If the `try...catch`
-block were omitted, Express would not catch the error since it is not part of the synchronous
-handler code.
-
-Use promises to avoid the overhead of the `try...catch` block or when using functions
-that return promises.  For example:
-
-```js
-app.get('/', (req, res, next) => {
-  Promise.resolve().then(() => {
-    throw new Error('BROKEN')
-  }).catch(next) // Errors will be passed to Express.
-})
-```
-
-Since promises automatically catch both synchronous errors and rejected promises,
-you can simply provide `next` as the final catch handler and Express will catch errors,
-because the catch handler is given the error as the first argument.
-
-You could also use a chain of handlers to rely on synchronous error
-catching, by reducing the asynchronous code to something trivial. For example:
-
-```js
-app.get('/', [
-  function (req, res, next) {
-    fs.readFile('/maybe-valid-file', 'utf-8', (err, data) => {
-      res.locals.data = data
-      next(err)
-    })
-  },
-  function (req, res) {
-    res.locals.data = res.locals.data.split(',')[1]
-    res.send(res.locals.data)
-  }
-])
-```
-
-The above example has a couple of trivial statements from the `readFile`
-call. If `readFile` causes an error, then it passes the error to Express, otherwise you
-quickly return to the world of synchronous error handling in the next handler
-in the chain. Then, the example above tries to process the data. If this fails, then the
-synchronous error handler will catch it. If you had done this processing inside
-the `readFile` callback, then the application might exit and the Express error
-handlers would not run.
-
-Whichever method you use, if you want Express error handlers to be called in and the
-application to survive, you must ensure that Express receives the error.
-
-## The default error handler
-
-Express comes with a built-in error handler that takes care of any errors that might be encountered in the app. This default error-handling middleware function is added at the end of the middleware function stack.
-
-如果您傳遞錯誤至 `next()`，且您沒有在錯誤處理常式中處理它，將會交由內建錯誤處理常式處理；該錯誤會連同堆疊追蹤寫入至用戶端。在正式作業環境中，則不包含堆疊追蹤。 The stack trace is not included
-in the production environment.
-
-<div class="doc-box doc-info" markdown="1">
-將 `NODE_ENV` 環境變數設為 `production`，以便在正式作業模式下執行應用程式。
-</div>
-
-When an error is written, the following information is added to the
-response:
-
-- The `res.statusCode` is set from `err.status` (or `err.statusCode`). If
-  this value is outside the 4xx or 5xx range, it will be set to 500.
-- The `res.statusMessage` is set according to the status code.
-- The body will be the HTML of the status code message when in production
-  environment, otherwise will be `err.stack`.
-- Any headers specified in an `err.headers` object.
-
-在您開始撰寫回應之後，一旦在呼叫 `next()` 時才發生錯誤（例如，當您將回應串流輸出至用戶端時遇到錯誤），Express 的預設錯誤處理程式會關閉連線，並使要求失敗。
-
-So when you add a custom error handler, you must delegate to
-the default Express error handler, when the headers
-have already been sent to the client:
-
-```js
-function errorHandler (err, req, res, next) {
-  if (res.headersSent) {
-    return next(err)
-  }
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-Note that the default error handler can get triggered if you call `next()` with an error
-in your code more than once, even if custom error handling middleware is in place.
-
-Other error handling middleware can be found at [Express middleware](/{{ page.lang }}/resources/middleware.html).
-
-## Writing error handlers
-
-錯誤處理中介軟體函數的定義方式，與其他中介軟體函數相同，差別在於錯誤處理函數的引數是四個而非三個：`(err, req, res, next)`。例如： For example:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-您是在定義其他 `app.use()` 和路由呼叫之後，最後才定義錯誤處理中介軟體；例如：
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use((err, req, res, next) => {
-  // logic
-})
-```
-
-Responses from within a middleware function can be in any format, such as an HTML error page, a simple message, or a JSON string.
-
-For organizational (and higher-level framework) purposes, you can define
-several error-handling middleware functions, much as you would with
-regular middleware functions. For example, to define an error-handler
-for requests made by using `XHR` and those without:
-
-```js
-const bodyParser = require('body-parser')
-const methodOverride = require('method-override')
-
-app.use(bodyParser.urlencoded({
-  extended: true
-}))
-app.use(bodyParser.json())
-app.use(methodOverride())
-app.use(logErrors)
-app.use(clientErrorHandler)
-app.use(errorHandler)
-```
-
-在本例中，通用的 `logErrors` 可能將要求和錯誤資訊寫入至 `stderr`，例如：
-
-```js
-function logErrors (err, req, res, next) {
-  console.error(err.stack)
-  next(err)
-}
-```
-
-此外在本例中，`clientErrorHandler` 定義成如下；在此情況下，會將錯誤明確傳遞給下一個：
-
-Notice that when _not_ calling "next" in an error-handling function, you are responsible for writing (and ending) the response. Otherwise, those requests will "hang" and will not be eligible for garbage collection.
-
-```js
-function clientErrorHandler (err, req, res, next) {
-  if (req.xhr) {
-    res.status(500).send({ error: 'Something failed!' })
-  } else {
-    next(err)
-  }
-}
-```
-
-"catch-all" `errorHandler` 函數的實作方式如下：
-
-```js
-function errorHandler (err, req, res, next) {
-  res.status(500)
-  res.render('error', { error: err })
-}
-```
-
-If you have a route handler with multiple callback functions, you can use the `route` parameter to skip to the next route handler. For example:
-
-```js
-app.get('/a_route_behind_paywall',
-  (req, res, next) => {
-    if (!req.user.hasPaid) {
-      // continue handling this request
-      next('route')
-    } else {
-      next()
-    }
-  }, (req, res, next) => {
-    PaidContent.find((err, doc) => {
-      if (err) return next(err)
-      res.json(doc)
-    })
-  })
-```
-
-在本例中，會跳過 `getPaidContent` 處理程式，但是會繼續執行 `app` 中 `/a_route_behind_paywall` 的其餘處理程式。
-
-<div class="doc-box doc-info" markdown="1">
-Calls to `next()` and `next(err)` indicate that the current handler is complete and in what state.  `next(err)` will skip all remaining handlers in the chain except for those that are set up to handle errors as described above.
-</div>
diff --git a/zh-tw/guide/migrating-4.md b/zh-tw/guide/migrating-4.md
deleted file mode 100644
index 40f5fd61f3..0000000000
--- a/zh-tw/guide/migrating-4.md
+++ /dev/null
@@ -1,580 +0,0 @@
----
-layout: page
-title: 移轉至 Express 4
-description: A guide to migrating your Express.js applications from version 3 to 4, covering changes in middleware, routing, and how to update your codebase effectively.
-menu: guide
-order: 9
-redirect_from: "  "
----
-
-# 移至 Express 4
-
-<h2 id="overview">概觀</h2>
-
-Express 4 是對 Express 3 的突破性變更。也就是說，如果您在其相依關係中更新 Express 版本，現有的 Express 3 應用程式將無法運作。 That means an existing Express 3 app will _not_ work if you update the Express version in its dependencies.
-
-本文涵蓋：
-
-<ul class="doclist">
-  <li><a href="#changes">Express 4 中的變更。</a></li>
-  <li>將 Express 3 應用程式移轉至 Express 4 的<a href="#example-migration">範例</a>。</li>
-  <li><a href="#app-gen">升級至 Express 4 應用程式產生器。</a></li>
-</ul>
-
-<h2 id="changes">Express 4 中的變更</h2>
-
-Express 4 有數項明顯的變更：
-
-<ul class="doclist">
-  <li><a href="#core-changes">Changes to Express core and middleware system.</a> The dependencies on Connect and built-in middleware were removed, so you must add middleware yourself.
-  </li>
-  <li><a href="#routing">路由系統的變更。</a></li>
-  <li><a href="#other-changes">其他各項變更。</a></li>
-</ul>
-
-另請參閱：
-
-- [New features in 4.x](https://github.com/expressjs/express/wiki/New-features-in-4.x)
-- [Migrating from 3.x to 4.x](https://github.com/expressjs/express/wiki/Migrating-from-3.x-to-4.x)
-
-<h3 id="core-changes">
-Express 核心和中介軟體系統的變更
-</h3>
-
-Express 4 不再相依於 Connect，除了 `express.static` 函數，其他所有的內建中介軟體皆已從其核心移除。也就是說，Express 現在是一個獨立的路由與中介軟體 Web 架構，Express 的版本化與版次不受中介軟體更新的影響。 This means that
-Express is now an independent routing and middleware web framework, and
-Express versioning and releases are not affected by middleware updates.
-
-由於沒有內建中介軟體，您必須明確新增執行您應用程式所需的所有中介軟體。只需遵循下列步驟： Simply follow these steps:
-
-1. 安裝模組：`npm install --save <module-name>`
-2. 在您的應用程式中，需要模組：`require('module-name')`
-3. 遵循模組的說明文件來使用該模組：`app.use( ... )`
-
-下表列出 Express 3 中介軟體和其在 Express 4 中的對應項目。
-
-<table class="doctable" border="1">
-<tbody><tr><th>Express 3</th><th>Express 4</th></tr>
-<tr><td><code>express.bodyParser</code></td>
-<td><a href="https://github.com/expressjs/body-parser">body-parser</a> +
-<a href="https://github.com/expressjs/multer">multer</a></td></tr>
-<tr><td><code>express.compress</code></td>
-<td><a href="https://github.com/expressjs/compression">compression</a></td></tr>
-<tr><td><code>express.cookieSession</code></td>
-<td><a href="https://github.com/expressjs/cookie-session">cookie-session</a></td></tr>
-<tr><td><code>express.cookieParser</code></td>
-<td><a href="https://github.com/expressjs/cookie-parser">cookie-parser</a></td></tr>
-<tr><td><code>express.logger</code></td>
-<td><a href="https://github.com/expressjs/morgan">morgan</a></td></tr>
-<tr><td><code>express.session</code></td>
-<td><a href="https://github.com/expressjs/session">express-session</a></td></tr>
-<tr><td><code>express.favicon</code></td>
-<td><a href="https://github.com/expressjs/serve-favicon">serve-favicon</a></td></tr>
-<tr><td><code>express.responseTime</code></td>
-<td><a href="https://github.com/expressjs/response-time">response-time</a></td></tr>
-<tr><td><code>express.errorHandler</code></td>
-<td><a href="https://github.com/expressjs/errorhandler">errorhandler</a></td></tr>
-<tr><td><code>express.methodOverride</code></td>
-<td><a href="https://github.com/expressjs/method-override">method-override</a></td></tr>
-<tr><td><code>express.timeout</code></td>
-<td><a href="https://github.com/expressjs/timeout">connect-timeout</a></td></tr>
-<tr><td><code>express.vhost</code></td>
-<td><a href="https://github.com/expressjs/vhost">vhost</a></td></tr>
-<tr><td><code>express.csrf</code></td>
-<td><a href="https://github.com/expressjs/csurf">csurf</a></td></tr>
-<tr><td><code>express.directory</code></td>
-<td><a href="https://github.com/expressjs/serve-index">serve-index</a></td></tr>
-<tr><td><code>express.static</code></td>
-<td><a href="https://github.com/expressjs/serve-static">serve-static</a></td></tr>
-</tbody></table>
-
-以下是 Express 4 中介軟體的[完整清單](https://github.com/senchalabs/connect#middleware)。
-
-In most cases, you can simply replace the old version 3 middleware with
-its Express 4 counterpart. For details, see the module documentation in
-GitHub.
-
-<h4 id="app-use"><code>app.use</code> 接受參數</h4>
-
-In version 4 you can use a variable parameter to define the path where middleware functions are loaded, then read the value of the parameter from the route handler.
-For example:
-
-```js
-app.use('/book/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-})
-```
-
-<h3 id="routing">
-路由系統
-</h3>
-
-Apps 現在隱含地載入了路由中介軟體，因此您不用再擔心該中介軟體相對於 `router` 中介軟體的載入順序。
-
-路由的定義方式不變，但是路由系統多了兩個新特性，可協助您組織路由：
-
-{: .doclist }
-
-- 新方法 `app.route()`，用來為路由路徑建立可鏈接的路由處理程式。
-- 新類別 `express.Router`，用來建立可裝載的模組路由處理程式。
-
-<h4 id="app-route"><code>app.route()</code> 方法</h4>
-
-新的 `app.route()` 方法可讓您為路由路徑建立可鏈接的路由處理程式。由於是在單一位置指定路徑，建立模組路由很有用，因為它可減少冗餘和打錯字的情況。如需路由的相關資訊，請參閱 [`Router()` 說明文件](/{{ page.lang }}/4x/api.html#router)。 Because the path is specified in a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more
-information about routes, see [`Router()` documentation](/{{ page.lang }}/4x/api.html#router).
-
-下列範例顯示利用 `app.route()` 函數所定義的路由處理程式鏈。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h4 id="express-router"><code>express.Router</code> 類別</h4>
-
-The other feature that helps to organize routes is a new class,
-`express.Router`, that you can use to create modular mountable
-route handlers. A `Router` instance is a complete middleware and
-routing system; for this reason it is often referred to as a "mini-app".
-
-下列範例是將路由器建立成模組、
-在其中載入中介軟體、定義一些路由，並將它裝載在主要應用程式中的路徑。
-
-例如，在應用程式目錄中建立一個名為 `birds.js` 的路由器檔案，內含下列內容：
-
-```js
-var express = require('express')
-var router = express.Router()
-
-// middleware specific to this router
-router.use((req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-})
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-然後將路由器模組載入應用程式中：
-
-```js
-var birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-現在，應用程式就能夠處理發給 `/birds` 和 `/birds/about` 路徑的要求，並且會呼叫該路由特定的 `timeLog` 中介軟體。
-
-<h3 id="other-changes">
-其他變更
-</h3>
-
-下表列出 Express 4 其他小幅卻很重要的變更：
-
-<table class="doctable" border="1">
-<tbody><tr>
-<th>Object</th>
-<th>Description</th>
-</tr>
-<tr>
-<td>Node.js</td>
-<td>Express 4 需要 Node.js 0.10.x 或更新版本，且不再支援 Node.js 0.8.x。</td>
-</tr>
-<tr>
-<td markdown="1">
-`http.createServer()`
-</td>
-<td markdown="1">
-
-不再需要 `http` 模組，除非您需要直接使用它 (socket.io/SPDY/HTTPS)。應用程式可藉由使用 `app.listen()` 函數來啟動。
- The app can be started by using the
-`app.listen()` function.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.configure()`
-</td>
-<td markdown="1">
-The `app.configure()` function has been removed.  
-`app.configure()` 函數已移除。請使用 `process.env.NODE_ENV` 或 `app.get('env')` 函數來偵測環境，並據以配置應用程式。
-
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`json spaces`
-</td>
-<td markdown="1">
-Express 4 中依預設會停用 `json spaces` 應用程式內容。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.accepted()`
-</td>
-<td markdown="1">
-使用 `req.accepts()`、`req.acceptsEncodings()`、`req.acceptsCharsets()` 和 `req.acceptsLanguages()`。</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.location()`
-</td>
-<td markdown="1">
-不再解析相對 URL。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`req.params`
-</td>
-<td markdown="1">
-Was an array; now an object.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.locals`
-</td>
-<td markdown="1">
-Was a function; now an object.
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.headerSent`
-</td>
-<td markdown="1">
-已變更為 `res.headersSent`。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`app.route`
-</td>
-<td markdown="1">
-現在以 `app.mountpath` 形式提供。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.on('header')`
-</td>
-<td markdown="1">
-已移除。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.charset`
-</td>
-<td markdown="1">
-已移除。
-</td>
-</tr>
-<tr>
-<td markdown="1">
-`res.setHeader('Set-Cookie', val)`
-</td>
-<td markdown="1">
-Functionality is now limited to setting the basic cookie value. 
-現在功能僅限於設定基本 Cookie 值。請使用
-`res.cookie()` 來取得新增的功能。
-
-</td>
-</tr>
-</tbody></table>
-
-<h2 id="example-migration">應用程式移轉範例</h2>
-
-下列範例顯示如何將 Express 3 應用程式移轉至 Express 4。值得一提的檔案是 `app.js` 和 `package.json`。
-The files of interest are `app.js` and `package.json`.
-
-<h3 id="">
-第 3 版應用程式
-</h3>
-
-<h4 id=""><code>app.js</code></h4>
-
-假設 Express 第 3 版應用程式具有下列的 `app.js` 檔：
-
-```js
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var http = require('http')
-var path = require('path')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(express.favicon())
-app.use(express.logger('dev'))
-app.use(express.methodOverride())
-app.use(express.session({ secret: 'your secret here' }))
-app.use(express.bodyParser())
-app.use(app.router)
-app.use(express.static(path.join(__dirname, 'public')))
-
-// development only
-if (app.get('env') === 'development') {
-  app.use(express.errorHandler())
-}
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-http.createServer(app).listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<h4 id=""><code>package.json</code></h4>
-
-附帶的第 3 版 `package.json` 檔可能類似如下：
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "express": "3.12.0",
-    "pug": "*"
-  }
-}
-```
-
-<h3 id="">
-程序
-</h3>
-
-開始移轉程序，作法是使用下列指令，為 Express 4 應用程式安裝必要的中介軟體，並將 Express 和 Pug 更新為其個別的最新版本：
-
-```bash
-$ npm install serve-favicon morgan method-override express-session body-parser multer errorhandler express@latest pug@latest --save
-```
-
-對 `app.js` 進行下列變更：
-
-1. `express` 物件中不再提供內建 Express 中介軟體函數
-   `express.favicon`、`express.logger`, `express.methodOverride`、`express.session`、`express.bodyParser` 和 `express.errorHandler`。您必須手動安裝其替代項目，並將它們載入到應用程式。 You must install their alternatives
-   manually and load them in the app.
-
-2. You no longer need to load the `app.router` function.
-   不再需要載入 `app.router` 函數。它不是有效的 Express 4 應用程式物件，因此請移除 `app.use(app.router);` 程式碼。
-
-3. Make sure that the middleware functions are loaded in the correct order - load `errorHandler` after loading the app routes.
-
-<h3 id="">第 4 版應用程式</h3>
-
-<h4 id=""><code>package.json</code></h4>
-
-執行上述 `npm` 指令，將會更新 `package.json`，如下所示：
-
-```json
-{
-  "name": "application-name",
-  "version": "0.0.1",
-  "private": true,
-  "scripts": {
-    "start": "node app.js"
-  },
-  "dependencies": {
-    "body-parser": "^1.5.2",
-    "errorhandler": "^1.1.1",
-    "express": "^4.8.0",
-    "express-session": "^1.7.2",
-    "pug": "^2.0.0",
-    "method-override": "^2.1.2",
-    "morgan": "^1.2.2",
-    "multer": "^0.1.3",
-    "serve-favicon": "^2.0.1"
-  }
-}
-```
-
-<h4 id=""><code>app.js</code></h4>
-
-Then, remove invalid code, load the required middleware, and make other
-changes as necessary. The `app.js` file will look like this:
-
-```js
-var http = require('http')
-var express = require('express')
-var routes = require('./routes')
-var user = require('./routes/user')
-var path = require('path')
-
-var favicon = require('serve-favicon')
-var logger = require('morgan')
-var methodOverride = require('method-override')
-var session = require('express-session')
-var bodyParser = require('body-parser')
-var multer = require('multer')
-var errorHandler = require('errorhandler')
-
-var app = express()
-
-// all environments
-app.set('port', process.env.PORT || 3000)
-app.set('views', path.join(__dirname, 'views'))
-app.set('view engine', 'pug')
-app.use(favicon(path.join(__dirname, '/public/favicon.ico')))
-app.use(logger('dev'))
-app.use(methodOverride())
-app.use(session({
-  resave: true,
-  saveUninitialized: true,
-  secret: 'uwotm8'
-}))
-app.use(bodyParser.json())
-app.use(bodyParser.urlencoded({ extended: true }))
-app.use(multer())
-app.use(express.static(path.join(__dirname, 'public')))
-
-app.get('/', routes.index)
-app.get('/users', user.list)
-
-// error handling middleware should be loaded after the loading the routes
-if (app.get('env') === 'development') {
-  app.use(errorHandler())
-}
-
-var server = http.createServer(app)
-server.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-<div class="doc-box doc-info" markdown="1">
-除非您需要直接使用 `http` 模組 (socket.io/SPDY/HTTPS)，並不需要載入它，只需採下列方式就能啟動應用程式：
-
-```js
-app.listen(app.get('port'), () => {
-  console.log('Express server listening on port ' + app.get('port'))
-})
-```
-
-</div>
-
-<h3 id="">Run the app</h3>
-
-The migration process is complete, and the app is now an
-Express 4 app. To confirm, start the app by using the following command:
-
-```bash
-$ node .
-```
-
-載入 [http://localhost:3000](http://localhost:3000)，並查看 Express 4 所呈現的首頁。
-
-<h2 id="app-gen">升級至 Express 4 應用程式產生器</h2>
-
-用來產生 Express 應用程式的指令行工具仍然是 `express`，但為了升級至新版本，您必須解除安裝 Express 3 應用程式產生器，再安裝新的 `express-generator`。
-
-<h3 id="">安裝</h3>
-
-如果您的系統已安裝 Express 3 應用程式產生器，必須解除安裝它：
-
-```bash
-$ npm uninstall -g express
-```
-
-視您如何配置檔案與目錄專用權而定，您可能需要使用 `sudo` 來執行這個指令。
-
-現在安裝新的產生器：
-
-```bash
-$ npm install -g express-generator
-```
-
-視您如何配置檔案與目錄專用權而定，您可能需要使用 `sudo` 來執行這個指令。
-
-現在，您系統上的 `express` 指令已更新為 Express 4 產生器。
-
-<h3 id="">Changes to the app generator </h3>
-
-除了以下，指令的選項與用法大致不變：
-
-{: .doclist }
-
-- 已移除 `--sessions` 選項。
-- 已移除 `--jshtml` 選項。
-- 新增了 `--hogan` 選項，以支援 [Hogan.js](http://twitter.github.io/hogan.js/)。
-
-<h3 id="">範例</h3>
-
-執行下列指令，以建立 Express 4 應用程式：
-
-```bash
-$ express app4
-```
-
-如果您查看 `app4/app.js` 檔的內容，您會發現應用程式所需要的所有中介軟體函數（但不包括 `express.static`）都載入成獨立模組，且 `router` 中介軟體不再明確載入到應用程式中。
-
-您也會發現，相對於舊產生器產生的獨立式應用程式，`app.js` 檔現在是一個 Node.js 模組。
-
-安裝相依關係之後，請使用下列指令來啟動應用程式：
-
-```bash
-$ npm start
-```
-
-如果您查看 `package.json` 檔中的 npm 啟動 Script，您會發現，啟動應用程式的實際指令是 `node ./bin/www`，這在 Express 3 中是 `node app.js`。
-
-由於 Express 4 產生器產生的 `app.js` 檔現在是一個 Node.js 模組，因此無法再以應用程式形式單獨啟動它（除非您修改程式碼）。模組必須載入到 Node.js 檔，並透過 Node.js 檔啟動。在本例中，Node.js 檔是 `./bin/www`。 The module must be loaded in a Node.js file
-and started via the Node.js file. The Node.js file is `./bin/www`
-in this case.
-
-Neither the `bin` directory nor the extensionless `www`
-file is mandatory for creating an Express app or starting the app. They are
-just suggestions made by the generator, so feel free to modify them to suit your
-needs.
-
-若要除去 `www` 目錄，並採用「Express 3 形式」，請刪除 `app.js` 檔尾端的 `module.exports = app;` 字行，然後在該處貼上下列程式碼：
-
-```js
-app.set('port', process.env.PORT || 3000)
-
-var server = app.listen(app.get('port'), () => {
-  debug('Express server listening on port ' + server.address().port)
-})
-```
-
-請使用下列程式碼，確定 `debug` 模組是載入於 `app.js` 檔頂端：
-
-```js
-var debug = require('debug')('app4')
-```
-
-然後將 `package.json` 檔中的 `"start": "node ./bin/www"` 變更為 `"start": "node app.js"`。
-
-現在您已將 `./bin/www` 的功能移回至 `app.js`。不建議進行這項變更，但這項練習有助您瞭解 `./bin/www` 檔的運作方式，以及 `app.js` 檔不再自行啟動的原因。 This change is not recommended, but the exercise helps you
-to understand how the `./bin/www` file works, and why the `app.js` file
-no longer starts on its own.
diff --git a/zh-tw/guide/migrating-5.md b/zh-tw/guide/migrating-5.md
deleted file mode 100644
index 809ebdb9b0..0000000000
--- a/zh-tw/guide/migrating-5.md
+++ /dev/null
@@ -1,620 +0,0 @@
----
-layout: page
-title: 移轉至 Express 5
-description: A comprehensive guide to migrating your Express.js applications from version 4 to 5, detailing breaking changes, deprecated methods, and new improvements.
-menu: guide
-order: 10
-redirect_from: "  "
----
-
-# 移至 Express 5
-
-<h2 id="overview">概觀</h2>
-
-Express 5 與 Express 4 之間差異不大：API 的變更不會像從 3.0 至 4.0 那樣顯著。雖然基本 API 維持相同，仍有一些突破性變更；換句話說，如果您更新成使用 Express 5，現有 Express 4 程式可能無法運作。 Therefore, an application built with Express 4 might not work if you update it to use Express 5.
-
-To install this version, you need to have a Node.js version 18 or higher. Then, execute the following command in your application directory:
-
-```sh
-npm install "express@5"
-```
-
-然後您可以執行自動化測試，查看失敗之處，並根據下方列出的更新項目來修正問題。解決測試失敗之後，請執行您的應用程式，查看發生哪些錯誤。只要應用程式使用任何不支援的方法或內容，您會馬上發現。 After addressing test failures, run your app to see what errors occur. You'll find out right away if the app uses any methods or properties that are not supported.
-
-## Express 5 Codemods
-
-To help you migrate your express server, we have created a set of codemods that will help you automatically update your code to the latest version of Express.
-
-Run the following command for run all the codemods available:
-
-```sh
-npx codemod@latest @expressjs/v5-migration-recipe
-```
-
-If you want to run a specific codemod, you can run the following command:
-
-```sh
-npx codemod@latest @expressjs/name-of-the-codemod
-```
-
-You can find the list of available codemods [here](https://codemod.link/express).
-
-<h2 id="changes">Express 5 中的變更</h2>
-
-**已移除的方法和內容**
-
-<ul class="doclist">
-  <li><a href="#app.del">app.del()</a></li>
-  <li><a href="#app.param">app.param(fn)</a></li>
-  <li><a href="#plural">複數化的方法名稱</a></li>
-  <li><a href="#leading">Leading colon in name argument to app.param(name, fn)</a></li>
-  <li><a href="#req.param">req.param(name)</a></li>
-  <li><a href="#res.json">res.json(obj, status)</a></li>
-  <li><a href="#res.jsonp">res.jsonp(obj, status)</a></li>
-  <li><a href="#magic-redirect">res.redirect('back') and res.location('back')</a></li>
-  <li><a href="#res.redirect">res.redirect(url, status)</a></li>
-  <li><a href="#res.send.body">res.send(body, status)</a></li>
-  <li><a href="#res.send.status">res.send(status)</a></li>
-  <li><a href="#res.sendfile">res.sendfile()</a></li>
-  <li><a href="#router.param">router.param(fn)</a></li>
-  <li><a href="#express.static.mime">express.static.mime</a></li>
-  <li><a href="#express:router-debug-logs">express:router debug logs</a></li>
-</ul>
-
-**改良**
-
-<ul class="doclist">
-  <li><a href="#path-syntax">Path route matching syntax</a></li>
-  <li><a href="#rejected-promises">Rejected promises handled from middleware and handlers</a></li>
-  <li><a href="#express.urlencoded">express.urlencoded</a></li>
-  <li><a href="#express.static.dotfiles">express.static dotfiles</a></li>
-  <li><a href="#leading">app.param(name, fn) 名稱引數中的前導冒號</a></li>
-  <li><a href="#app.router">app.router</a></li>
-  <li><a href="#req.body">req.body</a></li>
-  <li><a href="#req.host">req.host</a></li>
-  <li><a href="#req.params">req.params</a></li>
-  <li><a href="#req.query">req.query</a></li>
-  <li><a href="#res.clearCookie">res.clearCookie</a></li>
-  <li><a href="#res.status">res.status</a></li>
-  <li><a href="#res.vary">res.vary</a></li>
-</ul>
-
-**已變更**
-
-<ul class="doclist">
-  <li><a href="#res.render">res.render()</a></li>
-  <li><a href="#brotli-support">Brotli encoding support</a></li>
-</ul>
-
-## 已移除的方法和內容
-
-If you use any of these methods or properties in your app, it will crash. So, you'll need to change your app after you update to version 5.
-
-<h3 id="app.del">app.del()</h3>
-
-Express 5 no longer supports the `app.del()` function. If you use this function, an error is thrown. For registering HTTP DELETE routes, use the `app.delete()` function instead.
-
-最初是使用 `del` 而非 `delete`，因為 `delete` 是 JavaScript 中的保留關鍵字。不過，從 ECMAScript 6 起，`delete` 和其他保留關鍵字可以合法作為內容名稱。您可以在這裡閱讀導致淘汰 `app.del` 函數的相關討論。 However, as of ECMAScript 6, `delete` and other reserved keywords can legally be used as property names.
-
-{% capture codemod-route-del-to-delete %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/route-del-to-delete
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-route-del-to-delete %}
-
-```js
-// v4
-app.del('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-
-// v5
-app.delete('/user/:id', (req, res) => {
-  res.send(`DELETE /user/${req.params.id}`)
-})
-```
-
-<h3 id="app.param">app.param(fn)</h3>
-
-The `app.param(fn)` signature was used for modifying the behavior of the `app.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="plural">Pluralized method names</h3>
-
-The following method names have been pluralized. In Express 4, using the old methods resulted in a deprecation warning. Express 5 no longer supports them at all:
-
-`req.acceptsLanguage()` 以 `req.acceptsLanguages()` 取代。
-
-`req.acceptsCharset()` 以 `req.acceptsCharsets()` 取代。
-
-`req.acceptsEncoding()` 以 `req.acceptsEncodings()` 取代。
-
-{% capture codemod-pluralized-methods %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/pluralize-method-names
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-pluralized-methods %}
-
-```js
-// v4
-app.all('/', (req, res) => {
-  req.acceptsCharset('utf-8')
-  req.acceptsEncoding('br')
-  req.acceptsLanguage('en')
-
-  // ...
-})
-
-// v5
-app.all('/', (req, res) => {
-  req.acceptsCharsets('utf-8')
-  req.acceptsEncodings('br')
-  req.acceptsLanguages('en')
-
-  // ...
-})
-```
-
-<h3 id="leading">app.param(name, fn) 名稱中的前導冒號 (:)</h3>
-
-`app.param(name, fn)` 函數名稱中的前導冒號字元 (:) 遺留自 Express 3，基於舊版相容性，Express 4 仍支援它，只是會發出淘汰警示。Express 5 會無聲自動忽略它，並使用少了冒號字首的名稱參數。 Express 5 will silently ignore it and use the name parameter without prefixing it with a colon.
-
-如果您遵循 Express 4 [app.param](/{{ page.lang }}/4x/api.html#app.param) 說明文件，應該不會影響您的程式碼，因為該說明文件不會提及前導冒號。
-
-<h3 id="req.param">req.param(name)</h3>
-
-This potentially confusing and dangerous method of retrieving form data has been removed. You will now need to specifically look for the submitted parameter name in the `req.params`, `req.body`, or `req.query` object.
-
-{% capture codemod-req-param %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/explicit-request-params
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-req-param %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  const id = req.param('id')
-  const body = req.param('body')
-  const query = req.param('query')
-
-  // ...
-})
-
-// v5
-app.post('/user', (req, res) => {
-  const id = req.params.id
-  const body = req.body
-  const query = req.query
-
-  // ...
-})
-```
-
-<h3 id="res.json">res.json(obj, status)</h3>
-
-Express 5 不再支援 `res.json(obj, status)` 簽章。請改以設定狀態，然後與 `res.json()` 方法鏈接，如下所示：`res.status(status).json(obj)`。 Instead, set the status and then chain it to the `res.json()` method like this: `res.status(status).json(obj)`.
-
-{% capture codemod-status-send-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/status-send-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.json({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).json({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.jsonp">res.jsonp(obj, status)</h3>
-
-Express 5 不再支援 `res.jsonp(obj, status)` 簽章。請改以設定狀態，然後與 `res.jsonp()` 方法鏈接，如下所示：`res.status(status).jsonp(obj)`。 Instead, set the status and then chain it to the `res.jsonp()` method like this: `res.status(status).jsonp(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.post('/user', (req, res) => {
-  res.jsonp({ name: 'Ruben' }, 201)
-})
-
-// v5
-app.post('/user', (req, res) => {
-  res.status(201).jsonp({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.redirect">res.redirect(url, status)</h3>
-
-Express 5 no longer supports the signature `res.redirect(url, status)`. Instead, use the following signature: `res.redirect(status, url)`.
-
-{% capture codemod-redirect-arg-order %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/redirect-arg-order
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-redirect-arg-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('/users', 301)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(301, '/users')
-})
-```
-
-<h3 id="magic-redirect">res.redirect('back') and res.location('back')</h3>
-
-Express 5 no longer supports the magic string `back` in the `res.redirect()` and `res.location()` methods. Instead, use the `req.get('Referrer') || '/'` value to redirect back to the previous page. In Express 4, the `res.redirect('back')` and `res.location('back')` methods were deprecated.
-
-{% capture codemod-back-redirect-deprecated %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/back-redirect-deprecated
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-back-redirect-deprecated %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.redirect('back')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.redirect(req.get('Referrer') || '/')
-})
-```
-
-<h3 id="res.send.body">res.send(body, status)</h3>
-
-Express 5 不再支援 `res.send(obj, status)` 簽章。請改以設定狀態，然後與 `res.send()` 方法鏈接，如下所示：`res.status(status).send(obj)`。 Instead, set the status and then chain it to the `res.send()` method like this: `res.status(status).send(obj)`.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send({ name: 'Ruben' }, 200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.status(200).send({ name: 'Ruben' })
-})
-```
-
-<h3 id="res.send.status">res.send(status)</h3>
-
-Express 5 不再支援 <code>res.send(<em>status</em>)</code> 簽章，其中 _`status`_ 是數字。請改用 `res.sendStatus(statusCode)` 函數，此函數是設定 HTTP 回應標頭狀態碼，並傳送文字版的程式碼：「找不到」、「內部伺服器錯誤」等。
-如果您需要使用 `res.send()` 函數來傳送數字，請將數字括上引號來轉換成字串，這樣 Express 就不會解譯它以試圖使用不支援的舊簽章。 Instead, use the `res.sendStatus(statusCode)` function, which sets the HTTP response header status code and sends the text version of the code: "Not Found", "Internal Server Error", and so on.
-If you need to send a number by using the `res.send()` function, quote the number to convert it to a string, so that Express does not interpret it as an attempt to use the unsupported old signature.
-
-{% include admonitions/note.html content=codemod-status-send-order %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.send(200)
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendStatus(200)
-})
-```
-
-<h3 id="res.sendfile">res.sendfile()</h3>
-
-`res.sendfile()` 函數已被 Express 5 中的駝峰式大小寫版本 `res.sendFile()` 取代。
-
-**Note:** In Express 5, `res.sendFile()` uses the `mime-types` package for MIME type detection, which returns different Content-Type values than Express 4 for several common file types:
-
-- JavaScript files (.js): now "text/javascript" instead of "application/javascript"
-- JSON files (.json): now "application/json" instead of "text/json"
-- CSS files (.css): now "text/css" instead of "text/plain"
-- XML files (.xml): now "application/xml" instead of "text/xml"
-- Font files (.woff): now "font/woff" instead of "application/font-woff"
-- SVG files (.svg): now "image/svg+xml" instead of "application/svg+xml"
-
-{% capture codemod-camelcase-sendfile %}
-You can replace the deprecated signatures with the following command:
-
-```plain-text
-npx codemod@latest @expressjs/camelcase-sendfile
-```
-
-{% endcapture %}
-
-{% include admonitions/note.html content=codemod-camelcase-sendfile %}
-
-```js
-// v4
-app.get('/user', (req, res) => {
-  res.sendfile('/path/to/file')
-})
-
-// v5
-app.get('/user', (req, res) => {
-  res.sendFile('/path/to/file')
-})
-```
-
-<h3 id="router.param">router.param(fn)</h3>
-
-The `router.param(fn)` signature was used for modifying the behavior of the `router.param(name, fn)` function. It has been deprecated since v4.11.0, and Express 5 no longer supports it at all.
-
-<h3 id="express.static.mime">express.static.mime</h3>
-
-In Express 5, `mime` is no longer an exported property of the `static` field.
-Use the [`mime-types` package](https://github.com/jshttp/mime-types) to work with MIME type values.
-
-**Important:** This change affects not only direct usage of `express.static.mime` but also other Express methods that rely on MIME type detection, such as `res.sendFile()`. The following MIME types have changed from Express 4:
-
-- JavaScript files (.js): now served as "text/javascript" instead of "application/javascript"
-- JSON files (.json): now served as "application/json" instead of "text/json"
-- CSS files (.css): now served as "text/css" instead of "text/plain"
-- HTML files (.html): now served as "text/html; charset=utf-8" instead of just "text/html"
-- XML files (.xml): now served as "application/xml" instead of "text/xml"
-- Font files (.woff): now served as "font/woff" instead of "application/font-woff"
-
-```js
-// v4
-express.static.mime.lookup('json')
-
-// v5
-const mime = require('mime-types')
-mime.lookup('json')
-```
-
-<h3 id="express:router-debug-logs">express:router debug logs</h3>
-
-In Express 5, router handling logic is performed by a dependency. Therefore, the
-debug logs for the router are no longer available under the `express:` namespace.
-In v4, the logs were available under the namespaces `express:router`, `express:router:layer`,
-and `express:router:route`. All of these were included under the namespace `express:*`.
-In v5.1+, the logs are available under the namespaces `router`, `router:layer`, and `router:route`.
-The logs from `router:layer` and `router:route` are included in the namespace `router:*`.
-To achieve the same detail of debug logging when using `express:*` in v4, use a conjunction of
-`express:*`, `router`, and `router:*`.
-
-```sh
-# v4
-DEBUG=express:* node index.js
-
-# v5
-DEBUG=express:*,router,router:* node index.js
-```
-
-## 已變更
-
-<h3 id="path-syntax">Path route matching syntax</h3>
-
-Path route matching syntax is when a string is supplied as the first parameter to the `app.all()`, `app.use()`, `app.METHOD()`, `router.all()`, `router.METHOD()`, and `router.use()` APIs. The following changes have been made to how the path string is matched to an incoming request:
-
-- The wildcard `*` must have a name, matching the behavior of parameters `:`, use `/*splat` instead of `/*`
-
-```js
-// v4
-app.get('/*', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/*splat', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% capture note_wildcard %}
-`*splat` matches any path without the root path. If you need to match the root path as well `/`, you can use `/{*splat}`, wrapping the wildcard in braces.
-
-```js
-// v5
-app.get('/{*splat}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-{% endcapture %}
-{% include admonitions/note.html content=note_wildcard %}
-
-- The optional character `?` is no longer supported, use braces instead.
-
-```js
-// v4
-app.get('/:file.:ext?', async (req, res) => {
-  res.send('ok')
-})
-
-// v5
-app.get('/:file{.:ext}', async (req, res) => {
-  res.send('ok')
-})
-```
-
-- Regexp characters are not supported. For example:
-
-```js
-app.get('/[discussion|page]/:slug', async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-should be changed to:
-
-```js
-app.get(['/discussion/:slug', '/page/:slug'], async (req, res) => {
-  res.status(200).send('ok')
-})
-```
-
-- Some characters have been reserved to avoid confusion during upgrade (`()[]?+!`), use `\` to escape them.
-- Parameter names now support valid JavaScript identifiers, or quoted like `:"this"`.
-
-<h3 id="rejected-promises">Rejected promises handled from middleware and handlers</h3>
-
-Request middleware and handlers that return rejected promises are now handled by forwarding the rejected value as an `Error` to the error handling middleware. This means that using `async` functions as middleware and handlers are easier than ever. When an error is thrown in an `async` function or a rejected promise is `await`ed inside an async function, those errors will be passed to the error handler as if calling `next(err)`.
-
-Details of how Express handles errors is covered in the [error handling documentation](/en/guide/error-handling.html).
-
-<h3 id="express.urlencoded">express.urlencoded</h3>
-
-The `express.urlencoded` method makes the `extended` option `false` by default.
-
-<h3 id="express.static.dotfiles">express.static dotfiles</h3>
-
-In Express 5, the `express.static` middleware's `dotfiles` option now defaults to `"ignore"`. This is a change from Express 4, where dotfiles were served by default. As a result, files inside a directory that starts with a dot (`.`), such as `.well-known`, will no longer be accessible and will return a **404 Not Found** error. This can break functionality that depends on serving dot-directories, such as Android App Links, and Apple Universal Links.
-
-Example of breaking code:
-
-```js
-// v4
-app.use(express.static('public'))
-```
-
-After migrating to Express 5, a request to `/.well-known/assetlinks.json` will result in a **404 Not Found**.
-
-To fix this, serve specific dot-directories explicitly using the `dotfiles: "allow"` option:
-
-```js
-// v5
-app.use('/.well-known', express.static('public/.well-known', { dotfiles: 'allow' }))
-app.use(express.static('public'))
-```
-
-This approach allows you to safely serve only the intended dot-directories while keeping the default secure behavior for other dotfiles, which remain inaccessible.
-
-<h3 id="app.listen">app.listen</h3>
-
-In Express 5, the `app.listen` method will invoke the user-provided callback function (if provided) when the server receives an error event. In Express 4, such errors would be thrown. This change shifts error-handling responsibility to the callback function in Express 5. If there is an error, it will be passed to the callback as an argument.
-For example:
-
-```js
-const server = app.listen(8080, '0.0.0.0', (error) => {
-  if (error) {
-    throw error // e.g. EADDRINUSE
-  }
-  console.log(`Listening on ${JSON.stringify(server.address())}`)
-})
-```
-
-<h3 id="app.router">app.router</h3>
-
-`app.router` 物件已在 Express 4 中移除，在 Express 5 中又重新納入。
-在新版本中，這個物件只用來參照至基本 Express 路由器，不像在 Express 3 中，應用程式還得明確載入它。 In the new version, this object is a just a reference to the base Express router, unlike in Express 3, where an app had to explicitly load it.
-
-<h3 id="req.body">req.body</h3>
-
-The `req.body` property returns `undefined` when the body has not been parsed. In Express 4, it returns `{}` by default.
-
-<h3 id="req.host">req.host</h3>
-
-In Express 4, the `req.host` function incorrectly stripped off the port number if it was present. In Express 5, the port number is maintained.
-
-<h3 id="req.params">req.params</h3>
-
-The `req.params` object now has a **null prototype** when using string paths. However, if the path is defined with a regular expression, `req.params` remains a standard object with a normal prototype. Additionally, there are two important behavioral changes:
-
-**Wildcard parameters are now arrays:**
-
-Wildcards (e.g., `/*splat`) capture path segments as an array instead of a single string.
-
-```js
-app.get('/*splat', (req, res) => {
-  // GET /foo/bar
-  console.dir(req.params)
-  // => [Object: null prototype] { splat: [ 'foo', 'bar' ] }
-})
-```
-
-**Unmatched parameters are omitted:**
-
-In Express 4, unmatched wildcards were empty strings (`''`) and optional `:` parameters (using `?`) had a key with value `undefined`. In Express 5, unmatched parameters are completely omitted from `req.params`.
-
-```js
-// v4: unmatched wildcard is empty string
-app.get('/*', (req, res) => {
-  // GET /
-  console.dir(req.params)
-  // => { '0': '' }
-})
-
-// v4: unmatched optional param is undefined
-app.get('/:file.:ext?', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => { file: 'image', ext: undefined }
-})
-
-// v5: unmatched optional param is omitted
-app.get('/:file{.:ext}', (req, res) => {
-  // GET /image
-  console.dir(req.params)
-  // => [Object: null prototype] { file: 'image' }
-})
-```
-
-<h3 id="req.query">req.query</h3>
-
-The `req.query` property is no longer a writable property and is instead a getter. The default query parser has been changed from "extended" to "simple".
-
-<h3 id="res.clearCookie">res.clearCookie</h3>
-
-The `res.clearCookie` method ignores the `maxAge` and `expires` options provided by the user.
-
-<h3 id="res.status">res.status</h3>
-
-The `res.status` method only accepts integers in the range of `100` to `999`, following the behavior defined by Node.js, and it returns an error when the status code is not an integer.
-
-<h3 id="res.query">res.vary</h3>
-
-The `res.vary` throws an error when the `field` argument is missing. In Express 4, if the argument was omitted, it gave a warning in the console
-
-## 改良
-
-<h3 id="res.render">res.render()</h3>
-
-此方法現在會針對所有視圖引擎施行非同步行為，可避免採行同步實作及違反建議介面的視圖引擎所造成的錯誤。
-
-<h3 id="brotli-support">Brotli encoding support</h3>
-
-Express 5 supports Brotli encoding for requests received from clients that support it.
diff --git a/zh-tw/guide/overriding-express-api.md b/zh-tw/guide/overriding-express-api.md
deleted file mode 100644
index 5210622ff2..0000000000
--- a/zh-tw/guide/overriding-express-api.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-layout: page
-title: Overriding the Express API
-description: Discover how to customize and extend the Express.js API by overriding methods and properties on the request and response objects using prototypes.
-menu: guide
-order: 4
----
-
-# Overriding the Express API
-
-The Express API consists of various methods and properties on the request and response objects. These are inherited by prototype. There are two extension points for the Express API:
-
-1. The global prototypes at `express.request` and `express.response`.
-2. App-specific prototypes at `app.request` and `app.response`.
-
-Altering the global prototypes will affect all loaded Express apps in the same process. If desired, alterations can be made app-specific by only altering the app-specific prototypes after creating a new app.
-
-## Methods
-
-You can override the signature and behavior of existing methods with your own, by assigning a custom function.
-
-Following is an example of overriding the behavior of [res.sendStatus](/4x/api.html#res.sendStatus).
-
-```js
-app.response.sendStatus = function (statusCode, type, message) {
-  // code is intentionally kept simple for demonstration purpose
-  return this.contentType(type)
-    .status(statusCode)
-    .send(message)
-}
-```
-
-The above implementation completely changes the original signature of `res.sendStatus`. It now accepts a status code, encoding type, and the message to be sent to the client.
-
-The overridden method may now be used this way:
-
-```js
-res.sendStatus(404, 'application/json', '{"error":"resource not found"}')
-```
-
-## Properties
-
-Properties in the Express API are either:
-
-1. Assigned properties (ex: `req.baseUrl`, `req.originalUrl`)
-2. Defined as getters (ex: `req.secure`, `req.ip`)
-
-Since properties under category 1 are dynamically assigned on the `request` and `response` objects in the context of the current request-response cycle, their behavior cannot be overridden.
-
-Properties under category 2 can be overwritten using the Express API extensions API.
-
-The following code rewrites how the value of `req.ip` is to be derived. Now, it simply returns the value of the `Client-IP` request header.
-
-```js
-Object.defineProperty(app.request, 'ip', {
-  configurable: true,
-  enumerable: true,
-  get () { return this.get('Client-IP') }
-})
-```
-
-## Prototype
-
-In order to provide the Express API, the request/response objects passed to Express (via `app(req, res)`, for example) need to inherit from the same prototype chain. By default, this is `http.IncomingRequest.prototype` for the request and `http.ServerResponse.prototype` for the response.
-
-Unless necessary, it is recommended that this be done only at the application level, rather than globally. Also, take care that the prototype that is being used matches the functionality as closely as possible to the default prototypes.
-
-```js
-// Use FakeRequest and FakeResponse in place of http.IncomingRequest and http.ServerResponse
-// for the given app reference
-Object.setPrototypeOf(Object.getPrototypeOf(app.request), FakeRequest.prototype)
-Object.setPrototypeOf(Object.getPrototypeOf(app.response), FakeResponse.prototype)
-```
diff --git a/zh-tw/guide/routing.md b/zh-tw/guide/routing.md
deleted file mode 100644
index 3635821263..0000000000
--- a/zh-tw/guide/routing.md
+++ /dev/null
@@ -1,412 +0,0 @@
----
-layout: page
-title: Express 路由
-description: Learn how to define and use routes in Express.js applications, including route methods, route paths, parameters, and using Router for modular routing.
-menu: guide
-order: 1
-redirect_from: "  "
----
-
-# 路由
-
-_Routing_ refers to how an application's endpoints (URIs) respond to client requests.
-For an introduction to routing, see [Basic routing](/{{ page.lang }}/starter/basic-routing.html).
-
-You define routing using methods of the Express `app` object that correspond to HTTP methods;
-for example, `app.get()` to handle GET requests and `app.post` to handle POST requests. For a full list,
-see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD). You can also use [app.all()](/{{ page.lang }}/5x/api.html#app.all) to handle all HTTP methods and [app.use()](/{{ page.lang }}/5x/api.html#app.use) to
-specify middleware as the callback function (See [Using middleware](/{{ page.lang }}/guide/using-middleware.html) for details).
-
-These routing methods specify a callback function (sometimes called "handler functions") called when the application receives a request to the specified route (endpoint) and HTTP method. In other words, the application "listens" for requests that match the specified route(s) and method(s), and when it detects a match, it calls the specified callback function.
-
-In fact, the routing methods can have more than one callback function as arguments.
-With multiple callback functions, it is important to provide `next` as an argument to the callback function and then call `next()` within the body of the function to hand off control
-to the next callback.
-
-以下是以字串為基礎的部分路由路徑範例。
-
-```js
-const express = require('express')
-const app = express()
-
-// respond with "hello world" when a GET request is made to the homepage
-app.get('/', (req, res) => {
-  res.send('hello world')
-})
-```
-
-<h2 id="route-methods">路由方法</h2>
-
-路由方法衍生自其中一個 HTTP 方法，並且會附加到 `express` 類別的實例中。
-
-下列程式碼範例說明對應用程式根目錄提出 GET 和 POST 方法時所定義的路由。
-
-```js
-// GET method route
-app.get('/', (req, res) => {
-  res.send('GET request to the homepage')
-})
-
-// POST method route
-app.post('/', (req, res) => {
-  res.send('POST request to the homepage')
-})
-```
-
-Express supports methods that correspond to all HTTP request methods: `get`, `post`, and so on.
-For a full list, see [app.METHOD](/{{ page.lang }}/5x/api.html#app.METHOD).
-
-`app.all()` 是一個特殊的路由方法，它不是衍生自任何 HTTP 方法。此方法用來在所有要求方法的路徑中載入中介軟體函數。 在下列範例中，不論您使用的是 GET、POST、PUT、DELETE 或 [http 模組](https://nodejs.org/api/http.html#http_http_methods)中支援的其他任何 HTTP 要求方法，都會針對傳給 "/secret" 的要求執行處理程式。
-
-```js
-app.all('/secret', (req, res, next) => {
-  console.log('Accessing the secret section ...')
-  next() // pass control to the next handler
-})
-```
-
-<h2 id="route-paths">路由路徑</h2>
-
-Route paths, in combination with a request method, define the endpoints at which requests can be made. Route paths can be strings, string patterns, or regular expressions.
-
-{% capture caution-character %} In express 5, the characters `?`, `+`, `*`, `[]`, and `()` are handled differently than in version 4, please review the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-character %}
-
-{% capture note-dollar-character %}In express 4, regular expression characters such as `$` need to be escaped with a `\`.
-{% endcapture %}
-
-{% include admonitions/caution.html content=note-dollar-character %}
-
-{% capture note-path-to-regexp %}
-
-Express uses [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) for matching the route paths; see the path-to-regexp documentation for all the possibilities in defining route paths. [Express Playground Router](https://bjohansebas.github.io/playground-router/) is a handy tool for testing basic Express routes, although it does not support pattern matching.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=note-path-to-regexp %}
-
-{% capture query-string-note %}
-
-Query strings are not part of the route path.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=query-string-note %}
-
-### Route paths based on strings
-
-This route path will match requests to the root route, `/`.
-
-```js
-app.get('/', (req, res) => {
-  res.send('root')
-})
-```
-
-This route path will match requests to `/about`.
-
-```js
-app.get('/about', (req, res) => {
-  res.send('about')
-})
-```
-
-此路由路徑將符合傳送給 `/random.text` 的要求。
-
-```js
-app.get('/random.text', (req, res) => {
-  res.send('random.text')
-})
-```
-
-### Route paths based on string patterns
-
-{% capture caution-string-patterns %} The string patterns in Express 5 no longer work. Please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax) for more information.{% endcapture %}
-
-{% include admonitions/caution.html content=caution-string-patterns %}
-
-此路由路徑將符合 `acd` 和 `abcd`。
-
-```js
-app.get('/ab?cd', (req, res) => {
-  res.send('ab?cd')
-})
-```
-
-此路由路徑將符合 `abcd`、`abbcd`、`abbbcd` 等。
-
-```js
-app.get('/ab+cd', (req, res) => {
-  res.send('ab+cd')
-})
-```
-
-此路由路徑將符合 `abcd`、`abxcd`、`abRABDOMcd`、`ab123cd` 等。
-
-```js
-app.get('/ab*cd', (req, res) => {
-  res.send('ab*cd')
-})
-```
-
-此路由路徑將符合 `/abe` 和 `/abcde`。
-
-```js
-app.get('/ab(cd)?e', (req, res) => {
-  res.send('ab(cd)?e')
-})
-```
-
-### 以正規表示式為基礎的路由路徑範例：
-
-This route path will match anything with an "a" in it.
-
-```js
-app.get(/a/, (req, res) => {
-  res.send('/a/')
-})
-```
-
-此路由路徑將符合 `butterfly` 和 `dragonfly`，但不符合 `butterflyman`、`dragonfly man` 等。
-
-```js
-app.get(/.*fly$/, (req, res) => {
-  res.send('/.*fly$/')
-})
-```
-
-<h2 id="route-parameters">當路由路徑配上要求方法時，即定義了發出要求時的目標端點。路由路徑可以是字串、字串型樣或正規表示式。</h2>
-
-Route parameters are named URL segments that are used to capture the values specified at their position in the URL. The captured values are populated in the `req.params` object, with the name of the route parameter specified in the path as their respective keys.
-
-```
-Route path: /users/:userId/books/:bookId
-Request URL: http://localhost:3000/users/34/books/8989
-req.params: { "userId": "34", "bookId": "8989" }
-```
-
-To define routes with route parameters, simply specify the route parameters in the path of the route as shown below.
-
-```js
-app.get('/users/:userId/books/:bookId', (req, res) => {
-  res.send(req.params)
-})
-```
-
-<div class="doc-box doc-notice" markdown="1">
-The name of route parameters must be made up of "word characters" ([A-Za-z0-9_]).
-</div>
-
-Since the hyphen (`-`) and the dot (`.`) are interpreted literally, they can be used along with route parameters for useful purposes.
-
-```
-Route path: /flights/:from-:to
-Request URL: http://localhost:3000/flights/LAX-SFO
-req.params: { "from": "LAX", "to": "SFO" }
-```
-
-```
-Route path: /plantae/:genus.:species
-Request URL: http://localhost:3000/plantae/Prunus.persica
-req.params: { "genus": "Prunus", "species": "persica" }
-```
-
-{% capture warning-regexp %}
-In express 5, Regexp characters are not supported in route paths, for more information please refer to the [migration guide](/{{ page.lang }}/guide/migrating-5.html#path-syntax).{% endcapture %}
-
-{% include admonitions/caution.html content=warning-regexp %}
-
-To have more control over the exact string that can be matched by a route parameter, you can append a regular expression in parentheses (`()`):
-
-```
-Route path: /user/:userId(\d+)
-Request URL: http://localhost:3000/user/42
-req.params: {"userId": "42"}
-```
-
-{% capture escape-advisory %}
-
-Because the regular expression is usually part of a literal string, be sure to escape any `\` characters with an additional backslash, for example `\\d+`.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=escape-advisory %}
-
-{% capture warning-version %}
-
-In Express 4.x, <a href="https://github.com/expressjs/express/issues/2495">the `*` character in regular expressions is not interpreted in the usual way</a>. As a workaround, use `{0,}` instead of `*`. This will likely be fixed in Express 5.
-
-{% endcapture %}
-
-{% include admonitions/warning.html content=warning-version %}
-
-<h2 id="route-handlers">Route handlers</h2>
-
-You can provide multiple callback functions that behave like [middleware](/{{ page.lang }}/guide/using-middleware.html) to handle a request. The only exception is that these callbacks might invoke `next('route')` to bypass the remaining route callbacks. You can use this mechanism to impose pre-conditions on a route, then pass control to subsequent routes if there's no reason to proceed with the current route.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  if (req.params.id === '0') {
-    return next('route')
-  }
-  res.send(`User ${req.params.id}`)
-})
-
-app.get('/user/:id', (req, res) => {
-  res.send('Special handler for user ID 0')
-})
-```
-
-In this example:
-
-- `GET /user/5` → handled by first route → sends "User 5"
-- `GET /user/0` → first route calls `next('route')`, skipping to the next matching `/user/:id` route
-
-Route handlers can be in the form of a function, an array of functions, or combinations of both, as shown in the following examples.
-
-A single callback function can handle a route. For example:
-
-```js
-app.get('/example/a', (req, res) => {
-  res.send('Hello from A!')
-})
-```
-
-More than one callback function can handle a route (make sure you specify the `next` object). For example:
-
-```js
-app.get('/example/b', (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from B!')
-})
-```
-
-An array of callback functions can handle a route. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-const cb2 = function (req, res) {
-  res.send('Hello from C!')
-}
-
-app.get('/example/c', [cb0, cb1, cb2])
-```
-
-A combination of independent functions and arrays of functions can handle a route. For example:
-
-```js
-const cb0 = function (req, res, next) {
-  console.log('CB0')
-  next()
-}
-
-const cb1 = function (req, res, next) {
-  console.log('CB1')
-  next()
-}
-
-app.get('/example/d', [cb0, cb1], (req, res, next) => {
-  console.log('the response will be sent by the next function ...')
-  next()
-}, (req, res) => {
-  res.send('Hello from D!')
-})
-```
-
-<h2 id="response-methods">回應方法</h2>
-
-The methods on the response object (`res`) in the following table can send a response to the client, and terminate the request-response cycle. If none of these methods are called from a route handler, the client request will be left hanging.
-
-| 方法                                                                                                                                                                                                                        | Description                                                                                           |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
-| [res.download()](/{{ page.lang }}/4x/api.html#res.download)     | 提示您提供要下載的檔案。                                                                                          |
-| [res.end()](/{{ page.lang }}/4x/api.html#res.end)               | End the response process.                                                             |
-| [res.json()](/{{ page.lang }}/4x/api.html#res.json)             | 傳送 JSON 回應。                                                                                           |
-| [res.jsonp()](/{{ page.lang }}/4x/api.html#res.jsonp)           | 傳送 JSON 回應，並支援 JSONP。                                                                                 |
-| [res.redirect()](/{{ page.lang }}/4x/api.html#res.redirect)     | 將要求重新導向。                                                                                              |
-| [res.render()](/{{ page.lang }}/4x/api.html#res.render)         | Render a view template.                                                               |
-| [res.send()](/{{ page.lang }}/4x/api.html#res.send)             | 傳送各種類型的回應。                                                                                            |
-| [res.sendFile()](/{{ page.lang }}/4x/api.html#res.sendFile)     | 以八位元組串流形式傳送檔案。                                                                                        |
-| [res.sendStatus()](/{{ page.lang }}/4x/api.html#res.sendStatus) | Set the response status code and send its string representation as the response body. |
-
-<h2 id="app-route">app.route()</h2>
-
-您可以使用 `app.route()`，來為路由路徑建立可鏈接的路由處理程式。
-由於是在單一位置指定路徑，建立模組路由很有用，因為它可減少冗餘和打錯字的情況。如需路由的相關資訊，請參閱 [Router() 說明文件](/{{ page.lang }}/4x/api.html#router)。
-Because the path is specified at a single location, creating modular routes is helpful, as is reducing redundancy and typos. For more information about routes, see: [Router() documentation](/{{ page.lang }}/5x/api.html#router).
-
-下列範例顯示利用 `app.route()` 所定義的路由處理程式鏈。
-
-```js
-app.route('/book')
-  .get((req, res) => {
-    res.send('Get a random book')
-  })
-  .post((req, res) => {
-    res.send('Add a book')
-  })
-  .put((req, res) => {
-    res.send('Update the book')
-  })
-```
-
-<h2 id="express-router">express.Router</h2>
-
-Use the `express.Router` class to create modular, mountable route handlers. A `Router` instance is a complete middleware and routing system; for this reason, it is often referred to as a "mini-app".
-
-The following example creates a router as a module, loads a middleware function in it, defines some routes, and mounts the router module on a path in the main app.
-
-在應用程式目錄中建立一個名為 `birds.js` 的路由器檔案，內含下列內容：
-
-```js
-const express = require('express')
-const router = express.Router()
-
-// middleware that is specific to this router
-const timeLog = (req, res, next) => {
-  console.log('Time: ', Date.now())
-  next()
-}
-router.use(timeLog)
-
-// define the home page route
-router.get('/', (req, res) => {
-  res.send('Birds home page')
-})
-// define the about route
-router.get('/about', (req, res) => {
-  res.send('About birds')
-})
-
-module.exports = router
-```
-
-然後將路由器模組載入應用程式中：
-
-```js
-const birds = require('./birds')
-
-// ...
-
-app.use('/birds', birds)
-```
-
-現在，應用程式就能夠處理發給 `/birds` 和 `/birds/about` 的要求，並且呼叫該路由特定的 `timeLog` 中介軟體函數。
-
-But if the parent route `/birds` has path parameters, it will not be accessible by default from the sub-routes. To make it accessible, you will need to pass the `mergeParams` option to the Router constructor [reference](/{{ page.lang }}/5x/api.html#app.use).
-
-```js
-const router = express.Router({ mergeParams: true })
-```
diff --git a/zh-tw/guide/using-middleware.md b/zh-tw/guide/using-middleware.md
deleted file mode 100644
index 82e08bcbe7..0000000000
--- a/zh-tw/guide/using-middleware.md
+++ /dev/null
@@ -1,279 +0,0 @@
----
-layout: page
-title: 使用 Express 中介軟體
-description: Learn how to use middleware in Express.js applications, including application-level and router-level middleware, error handling, and integrating third-party middleware.
-menu: guide
-order: 3
-redirect_from: "  "
----
-
-# 使用中介軟體
-
-Express 是一個本身功能極簡的路由與中介軟體 Web 架構：本質上，Express 應用程式是一系列的中介軟體函數呼叫。
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req)  (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the next middleware function in the application's request-response cycle. The next middleware function is commonly denoted by a variable named `next`.
-
-Middleware functions can perform the following tasks:
-
-- 執行任何程式碼。
-- Make changes to the request and the response objects.
-- End the request-response cycle.
-- Call the next middleware function in the stack.
-
-If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
-
-Express 應用程式可以使用下列類型的中介軟體：
-
-- [應用程式層次的中介軟體](#middleware.application)
-- [路由器層次的中介軟體](#middleware.router)
-- [錯誤處理中介軟體](#middleware.error-handling)
-- [內建中介軟體](#middleware.built-in)
-- [協力廠商中介軟體](#middleware.third-party)
-
-You can load application-level and router-level middleware with an optional mount path.
-You can also load a series of middleware functions together, which creates a sub-stack of the middleware system at a mount point.
-
-<h2 id='middleware.application'>應用程式層次的中介軟體</h2>
-
-Bind application-level middleware to an instance of the [app object](/{{ page.lang }}/5x/api.html#app) by using the `app.use()` and `app.METHOD()` functions, where `METHOD` is the HTTP method of the request that the middleware function handles (such as GET, PUT, or POST) in lowercase.
-
-This example shows a middleware function with no mount path. The function is executed every time the app receives a request.
-
-```js
-const express = require('express')
-const app = express()
-
-app.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-```
-
-This example shows a middleware function mounted on the `/user/:id` path. The function is executed for any type of
-HTTP request on the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-This example shows a route and its handler function (middleware system). The function handles GET requests to the `/user/:id` path.
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  res.send('USER')
-})
-```
-
-Here is an example of loading a series of middleware functions at a mount point, with a mount path.
-It illustrates a middleware sub-stack that prints request info for any type of HTTP request to the `/user/:id` path.
-
-```js
-app.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-```
-
-Route handlers enable you to define multiple routes for a path. The example below defines two routes for GET requests to the `/user/:id` path. The second route will not cause any problems, but it will never get called because the first route ends the request-response cycle.
-
-本例顯示中介軟體子堆疊，它處理了指向 `/user/:id` 路徑的 GET 要求。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  console.log('ID:', req.params.id)
-  next()
-}, (req, res, next) => {
-  res.send('User Info')
-})
-
-// handler for the /user/:id path, which prints the user ID
-app.get('/user/:id', (req, res, next) => {
-  res.send(req.params.id)
-})
-```
-
-To skip the rest of the middleware functions from a router middleware stack, call `next('route')` to pass control to the next route.
-
-{% capture next-function %}
-
-`next('route')` will work only in middleware functions that were loaded by using the `app.METHOD()` or `router.METHOD()` functions.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=next-function %}
-
-本例顯示中介軟體子堆疊，它處理了指向 `/user/:id` 路徑的 GET 要求。
-
-```js
-app.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next route
-  if (req.params.id === '0') next('route')
-  // otherwise pass the control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // send a regular response
-  res.send('regular')
-})
-
-// handler for the /user/:id path, which sends a special response
-app.get('/user/:id', (req, res, next) => {
-  res.send('special')
-})
-```
-
-Middleware can also be declared in an array for reusability.
-
-本例顯示裝載在 `/user/:id` 路徑的中介軟體函數。會對 `/user/:id` 路徑上任何類型的 HTTP 要求，執行此函數。
-
-```js
-function logOriginalUrl (req, res, next) {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}
-
-function logMethod (req, res, next) {
-  console.log('Request Type:', req.method)
-  next()
-}
-
-const logStuff = [logOriginalUrl, logMethod]
-app.get('/user/:id', logStuff, (req, res, next) => {
-  res.send('User Info')
-})
-```
-
-<h2 id='middleware.router'>路由器層次的中介軟體</h2>
-
-路由器層次的中介軟體的運作方式如同應用程式層次的中介軟體，不同之處在於它會連結至 `express.Router()` 實例。
-
-```js
-const router = express.Router()
-```
-
-請利用 `router.use()` 和 `router.METHOD()` 函數來載入路由器層次的中介軟體。
-
-下列的程式碼範例是使用路由器層次的中介軟體，抄寫上述針對應用程式層次的中介軟體顯示的中介軟體系統：
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// a middleware function with no mount path. This code is executed for every request to the router
-router.use((req, res, next) => {
-  console.log('Time:', Date.now())
-  next()
-})
-
-// a middleware sub-stack shows request info for any type of HTTP request to the /user/:id path
-router.use('/user/:id', (req, res, next) => {
-  console.log('Request URL:', req.originalUrl)
-  next()
-}, (req, res, next) => {
-  console.log('Request Type:', req.method)
-  next()
-})
-
-// a middleware sub-stack that handles GET requests to the /user/:id path
-router.get('/user/:id', (req, res, next) => {
-  // if the user ID is 0, skip to the next router
-  if (req.params.id === '0') next('route')
-  // otherwise pass control to the next middleware function in this stack
-  else next()
-}, (req, res, next) => {
-  // render a regular page
-  res.render('regular')
-})
-
-// handler for the /user/:id path, which renders a special page
-router.get('/user/:id', (req, res, next) => {
-  console.log(req.params.id)
-  res.render('special')
-})
-
-// mount the router on the app
-app.use('/', router)
-```
-
-To skip the rest of the router's middleware functions, call `next('router')`
-to pass control back out of the router instance.
-
-本例顯示中介軟體子堆疊，它處理了指向 `/user/:id` 路徑的 GET 要求。
-
-```js
-const express = require('express')
-const app = express()
-const router = express.Router()
-
-// predicate the router with a check and bail out when needed
-router.use((req, res, next) => {
-  if (!req.headers['x-auth']) return next('router')
-  next()
-})
-
-router.get('/user/:id', (req, res) => {
-  res.send('hello, user!')
-})
-
-// use the router and 401 anything falling through
-app.use('/admin', router, (req, res) => {
-  res.sendStatus(401)
-})
-```
-
-<h2 id='middleware.error-handling'>Error-handling middleware</h2>
-
-<div class="doc-box doc-notice" markdown="1">
-Error-handling middleware always takes _four_ arguments. You must provide four arguments to identify it as an error-handling middleware function. Even if you don't need to use the `next` object, you must specify it to maintain the signature. Otherwise, the `next` object will be interpreted as regular middleware and will fail to handle errors.
-</div>
-
-Define error-handling middleware functions in the same way as other middleware functions, except with four arguments instead of three, specifically with the signature `(err, req, res, next)`:
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-For details about error-handling middleware, see: [Error handling](/{{ page.lang }}/guide/error-handling.html).
-
-<h2 id='middleware.built-in'>Built-in middleware</h2>
-
-從 4.x 版起，Express 不再相依於 [Connect](https://github.com/senchalabs/connect)。除了 `express.static`，Express 先前隨附的所有中介軟體函數現在位於個別的模組中。請檢視[中介軟體函數清單](https://github.com/senchalabs/connect#middleware)。 The middleware
-functions that were previously included with Express are now in separate modules; see [the list of middleware functions](https://github.com/senchalabs/connect#middleware).
-
-Express has the following built-in middleware functions:
-
-- [express.static](/en/5x/api.html#express.static) serves static assets such as HTML files, images, and so on.
-- [express.json](/en/5x/api.html#express.json) parses incoming requests with JSON payloads. **NOTE: Available with Express 4.16.0+**
-- [express.urlencoded](/en/5x/api.html#express.urlencoded) parses incoming requests with URL-encoded payloads.  **NOTE: Available with Express 4.16.0+**
-
-<h2 id='middleware.third-party'>Third-party middleware</h2>
-
-Use third-party middleware to add functionality to Express apps.
-
-針對必要的功能安裝 Node.js 模組，然後在應用程式層次或路由器層次將它載入到您的應用程式中。
-
-下列範例說明如何安裝和載入用來剖析 Cookie 的中介軟體函數 `cookie-parser`。
-
-```bash
-$ npm install cookie-parser
-```
-
-```js
-const express = require('express')
-const app = express()
-const cookieParser = require('cookie-parser')
-
-// load the cookie-parsing middleware
-app.use(cookieParser())
-```
-
-For a partial list of third-party middleware functions that are commonly used with Express, see: [Third-party middleware](../resources/middleware.html).
diff --git a/zh-tw/guide/using-template-engines.md b/zh-tw/guide/using-template-engines.md
deleted file mode 100644
index fd1a615e69..0000000000
--- a/zh-tw/guide/using-template-engines.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-layout: page
-title: 在 Express 中使用模板引擎
-description: Discover how to integrate and use template engines like Pug, Handlebars, and EJS with Express.js to render dynamic HTML pages efficiently.
-menu: guide
-order: 5
-redirect_from: "  "
----
-
-# 在 Express 中使用模板引擎
-
-A _template engine_ enables you to use static template files in your application. 模板引擎讓您能在應用程式中使用靜態模板檔案。在執行時，模板引擎會將靜態模板檔案中的變數取代為真實的值，並將模板轉換為 HTML 檔案發送至客戶端，這種方法使得設計一個 HTML 頁面變得更加容易。
-This approach makes it easier to design an HTML page.
-
-部分主流的模板引擎 [Pug](https://pugjs.org/api/getting-started.html)、[Mustache](https://www.npmjs.com/package/mustache) 和 [EJS](https://www.npmjs.com/package/ejs) 均可被使用於 Express 中。[Express 應用程式產生器](http://expressjs.com/en/starter/generator.html)預設採用 [Jade](https://www.npmjs.com/package/jade)，但也支援包含上述的多種模板引擎。
-
-若要渲染模板檔案，您必須在應用程式產生器產生的 `app.js` 設定以下[應用程式屬性](http://expressjs.com/en/4x/api.html#app.set)：
-
-- `views`, the directory where the template files are located. `views`：範本檔所在的目錄。例如：`app.set('views', './views')`，其預設為應用程式根目錄的 `views` 資料夾。
-  This defaults to the `views` directory in the application root directory.
-- `view engine`, the template engine to use. `view engine`：要使用的範本引擎，例如若要使用 Pug 模板引擎：`app.set('view engine', 'pug')`
-
-並安裝對應的模板引擎 npm 套件，例如安裝 Pug：
-
-```bash
-$ npm install pug --save
-```
-
-<div class="doc-box doc-notice" markdown="1">
-與 Express 相容的範本引擎（例如 Pug）會匯出一個名稱是 `__express(filePath, options, callback)` 的函數，以供 `res.render()` 函數呼叫，來呈現範本程式碼。
-
-Some template engines do not follow this convention. 有些範本引擎不遵循這項慣例。[Consolidate.js](https://www.npmjs.org/package/consolidate) 程式庫遵循這項慣例，它會對映所有常見的 Node.js 範本引擎，因此能在 Express 內平順無礙地運作。
-
-</div>
-
-在設定模板引擎之後，您不必指定引擎或將範本引擎模組載入到應用程式中；Express 會在內部載入模組，如以下所示（針對上述範例）。
-
-```js
-app.set('view engine', 'pug')
-```
-
-在 `views` 目錄中，建立一個名稱是 `index.pug` 並內含下列內容的 Pug 範本檔：
-
-```pug
-html
-  head
-    title= title
-  body
-    h1= message
-```
-
-Create a route to render the `index.pug` file. If the `view engine` property is not set,
-you must specify the extension of the `view` file. Otherwise, you can omit it.
-
-```js
-app.get('/', (req, res) => {
-  res.render('index', { title: 'Hey', message: 'Hello there!' })
-})
-```
-
-當您向首頁發出請求時，`index.pug` 檔會以 HTML 被渲染出來。
-
-The view engine cache does not cache the contents of the template's output, only the underlying template itself. The view is still re-rendered with every request even when the cache is on.
diff --git a/zh-tw/guide/writing-middleware.md b/zh-tw/guide/writing-middleware.md
deleted file mode 100644
index 797e2f0553..0000000000
--- a/zh-tw/guide/writing-middleware.md
+++ /dev/null
@@ -1,222 +0,0 @@
----
-layout: page
-title: 撰寫中介軟體以用於 Express 應用程式中
-description: Learn how to write custom middleware functions for Express.js applications, including examples and best practices for enhancing request and response handling.
-menu: guide
-order: 2
-redirect_from: "  "
----
-
-# 撰寫中介軟體以用於 Express 應用程式中
-
-<h2>概觀</h2>
-
-_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
-
-Middleware functions can perform the following tasks:
-
-- 執行任何程式碼。
-- Make changes to the request and the response objects.
-- End the request-response cycle.
-- Call the next middleware in the stack.
-
-If the current middleware function does not end the request-response cycle, it must call `next()` to pass control to the next middleware function. Otherwise, the request will be left hanging.
-
-The following figure shows the elements of a middleware function call:
-
-<div class="table-scroller">
-<table id="mw-fig">
-<tbody><tr><td id="mw-fig-imgcell">
-<img src="/images/express-mw.png" alt="Elements of a middleware function call" id="mw-fig-img" />
-</td>
-<td class="mw-fig-callouts">
-<div class="callout" id="callout1">HTTP method for which the middleware function applies.</div></tbody>
-
-<div class="callout" id="callout2">Path (route) for which the middleware function applies.</div>
-
-<div class="callout" id="callout3">The middleware function.</div>
-
-<div class="callout" id="callout4">中介軟體函數的回呼引數，依慣例，稱為 "next"。</div>
-
-<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
-
-<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
-</td></tr>
-</table>
-</div>
-
-Starting with Express 5, middleware functions that return a Promise will call `next(value)` when they reject or throw an error. `next` will be called with either the rejected value or the thrown Error.
-
-<h2>範例</h2>
-
-下列範例顯示簡單的 "Hello World" Express 應用程式，您將為這個應用程式定義兩個中介軟體函數：
-The remainder of this article will define and add three middleware functions to the application:
-one called `myLogger` that prints a simple log message, one called `requestTime` that
-displays the timestamp of the HTTP request, and one called `validateCookies` that validates incoming cookies.
-
-```js
-const express = require('express')
-const app = express()
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-<h3>Middleware function myLogger</h3>
-Here is a simple example of a middleware function called "myLogger". This function just prints "LOGGED" when a request to the app passes through it. The middleware function is assigned to a variable named `myLogger`.
-
-```js
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Notice the call above to `next()`. Calling this function invokes the next middleware function in the app.
-The `next()` function is not a part of the Node.js or Express API, but is the third argument that is passed to the middleware function. The `next()` function could be named anything, but by convention it is always named "next".
-To avoid confusion, always use this convention.
-</div>
-
-To load the middleware function, call `app.use()`, specifying the middleware function.
-For example, the following code loads the `myLogger` middleware function before the route to the root path (/).
-
-```js
-const express = require('express')
-const app = express()
-
-const myLogger = function (req, res, next) {
-  console.log('LOGGED')
-  next()
-}
-
-app.use(myLogger)
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(3000)
-```
-
-每當應用程式收到要求時，它會將 "LOGGED" 訊息列印至終端機。
-
-The order of middleware loading is important: middleware functions that are loaded first are also executed first.
-
-如果 `myLogger` 是在根路徑路由之後才載入，要求永不會抵達該函數，應用程式也不會列印 "LOGGED"，因為根路徑的路由處理程式會終止要求/回應循環。
-
-The middleware function `myLogger` simply prints a message, then passes on the request to the next middleware function in the stack by calling the `next()` function.
-
-<h3>Middleware function requestTime</h3>
-
-Next, we'll create a middleware function called "requestTime" and add a property called `requestTime`
-to the request object.
-
-```js
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-```
-
-The app now uses the `requestTime` middleware function. Also, the callback function of the root path route uses the property that the middleware function adds to `req` (the request object).
-
-```js
-const express = require('express')
-const app = express()
-
-const requestTime = function (req, res, next) {
-  req.requestTime = Date.now()
-  next()
-}
-
-app.use(requestTime)
-
-app.get('/', (req, res) => {
-  let responseText = 'Hello World!<br>'
-  responseText += `<small>Requested at: ${req.requestTime}</small>`
-  res.send(responseText)
-})
-
-app.listen(3000)
-```
-
-When you make a request to the root of the app, the app now displays the timestamp of your request in the browser.
-
-<h3>Middleware function validateCookies</h3>
-
-Finally, we'll create a middleware function that validates incoming cookies and sends a 400 response if cookies are invalid.
-
-Here's an example function that validates cookies with an external async service.
-
-```js
-async function cookieValidator (cookies) {
-  try {
-    await externallyValidateCookie(cookies.testCookie)
-  } catch {
-    throw new Error('Invalid cookies')
-  }
-}
-```
-
-Here, we use the [`cookie-parser`](/resources/middleware/cookie-parser.html) middleware to parse incoming cookies off the `req` object and pass them to our `cookieValidator` function. The `validateCookies` middleware returns a Promise that upon rejection will automatically trigger our error handler.
-
-```js
-const express = require('express')
-const cookieParser = require('cookie-parser')
-const cookieValidator = require('./cookieValidator')
-
-const app = express()
-
-async function validateCookies (req, res, next) {
-  await cookieValidator(req.cookies)
-  next()
-}
-
-app.use(cookieParser())
-
-app.use(validateCookies)
-
-// error handler
-app.use((err, req, res, next) => {
-  res.status(400).send(err.message)
-})
-
-app.listen(3000)
-```
-
-<div class="doc-box doc-notice" markdown="1">
-Note how `next()` is called after `await cookieValidator(req.cookies)`. This ensures that if `cookieValidator` resolves, the next middleware in the stack will get called. If you pass anything to the `next()` function (except the string `'route'` or `'router'`), Express regards the current request as being an error and will skip any remaining non-error handling routing and middleware functions.
-</div>
-
-Because you have access to the request object, the response object, the next middleware function in the stack, and the whole Node.js API, the possibilities with middleware functions are endless.
-
-For more information about Express middleware, see: [Using Express middleware](/{{ page.lang }}/guide/using-middleware.html).
-
-<h2>Configurable middleware</h2>
-
-If you need your middleware to be configurable, export a function which accepts an options object or other parameters, which, then returns the middleware implementation based on the input parameters.
-
-File: `my-middleware.js`
-
-```js
-module.exports = function (options) {
-  return function (req, res, next) {
-    // Implement the middleware function based on the options object
-    next()
-  }
-}
-```
-
-The middleware can now be used as shown below.
-
-```js
-const mw = require('./my-middleware.js')
-
-app.use(mw({ option1: '1', option2: '2' }))
-```
-
-Refer to [cookie-session](https://github.com/expressjs/cookie-session) and [compression](https://github.com/expressjs/compression) for examples of configurable middleware.
diff --git a/zh-tw/index.md b/zh-tw/index.md
deleted file mode 100644
index 1d461bc316..0000000000
--- a/zh-tw/index.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-layout: home
-title: Express - Node.js web application framework
-description: "Express is a fast, unopinionated, minimalist web framework for Node.js, providing a robust set of features for web and mobile applications."
-menu: home
-redirect_from: "  "
----
-
-<section id="home-content">
-  <div id="homepage-leftpane" class="pane">
-    <section id="description">
-        <div class="express"><span>Express</span><a href="https://github.com/expressjs/express/releases" id="express-version">{{ site.data.express.current_version }}</a></div>
-        <h1 class="description">Fast, unopinionated, minimalist web framework for <a href='https://nodejs.org/en/'>Node.js</a></h1>
-    </section>
-    <pre class="install-command"><code>$ npm install express --save</code></pre>
-  </div>
-
-  <div id="homepage-rightpane" class="pane" markdown="1">
-
-```javascript
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-  </div>
-</section>
-
-{% if site.announcement %}
-
-<section id="announcements">
-  {% include announcement.html %}
-</section>
-{% endif %}
-
-<section id="intro">
-  <div id="boxes" class="clearfix">
-    <div id="web-applications">
-      <h2>Web Applications</h2> Express is a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
-    </div>
-    <div id="apis">
-      <h2>APIs</h2> With a myriad of HTTP utility methods and middleware at your disposal, creating a robust API is quick and easy.
-    </div>
-    <div id="performance">
-      <h2>Performance</h2> Express provides a thin layer of fundamental web application features, without obscuring Node.js features that you know and love.
-    </div>
-    <div id="middleware">
-      <h2>中介軟體</h2> 
-      Express is a lightweight and flexible routing framework with minimal core features 
-      meant to be augmented through the use of Express <a href="{{ page.lang }}/resources/middleware.html">middleware</a> modules.
-    </div>
-  </div>
-</section>
diff --git a/zh-tw/resources/community.md b/zh-tw/resources/community.md
deleted file mode 100644
index 97fb27e3c9..0000000000
--- a/zh-tw/resources/community.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-layout: page
-title: Express 社群
-description: Connect with the Express.js community, learn about the technical committee, find resources, explore community-contributed modules, and get involved in discussions.
-menu: resources
-order: 1
-redirect_from: "  "
----
-
-# 社群
-
-## Technical committee
-
-The Express technical committee meets online every two weeks (as needed) to discuss development and maintenance of Express,
-and other issues relevant to the Express project. Each meeting is typically announced in an
-[expressjs/discussions issue](https://github.com/expressjs/discussions/issues) with a link to join or view the meeting, which is
-open to all observers.
-
-The meetings are recorded; for a list of the recordings, see the [Express.js YouTube channel](https://www.youtube.com/channel/UCYjxjAeH6TRik9Iwy5nXw7g).
-
-Members of the Express technical committee are:
-
-**Active:**
-
-- [@blakeembrey](https://github.com/blakeembrey) - Blake Embrey
-- [@crandmck](https://github.com/crandmck) - Rand McKinney
-- [@LinusU](https://github.com/LinusU) - Linus Unnebäck
-- [@ulisesgascon](https://github.com/ulisesGascon) - Ulises Gascón
-- [@sheplu](https://github.com/sheplu) - Jean Burellier
-- [@wesleytodd](https://github.com/wesleytodd) - Wes Todd
-- [@jonchurch](https://github.com/jonchurch) - Jon Church
-- [@ctcpip](https://github.com/ctcpip/) - Chris de Almeida
-
-**Inactive:**
-
-- [@dougwilson](https://github.com/dougwilson) - Douglas Wilson
-- [@hacksparrow](https://github.com/hacksparrow) - Hage Yaapa
-- [@jonathanong](https://github.com/jonathanong) - jongleberry
-- [@niftylettuce](https://github.com/niftylettuce) - niftylettuce
-- [@troygoode](https://github.com/troygoode) - Troy Goode
-
-## Express is made of many modules
-
-我們的熱情活躍的社群已建立各式各樣的延伸項目、[中介軟體模組](/{{ page.lang }}/resources/middleware.html)，以及更高層次的架構。相關資訊請參閱 [Wiki](https://github.com/expressjs/express/wiki)。
-
-Additionally, the Express community maintains modules in these two GitHub orgs:
-
-- [jshttp](https://github.com/jshttp) modules providing useful utility functions; see [Utility modules](/{{ page.lang }}/resources/utils.html).
-- [pillarjs](https://github.com/pillarjs): low-level modules that Express uses internally.
-
-To keep up with what is going on in the whole community, check out the [ExpressJS StatusBoard](https://expressjs.github.io/statusboard/).
-
-## 議題
-
-如果您恰巧碰到您認為是錯誤之處，或者只是想提出一項特性要求，請在[議題列表](https://github.com/expressjs/express/issues)中開立問題單。
-
-## 範例
-
-檢視儲存庫中數十個 Express 應用程式[範例](https://github.com/expressjs/express/tree/master/examples)，從 API 設計與鑑別，到範本引擎的整合，樣樣涵蓋在內。
-
-## Github Discussions
-
-The [GitHub Discussions](https://github.com/expressjs/discussions) section is an excellent space to engage in conversations about the development and maintenance of Express, as well as to share ideas and discuss topics related to its usage.
-
-# Branding of Express.js
-
-## Express.js Logo
-
-Express is a project of the OpenJS Foundation. Please review the [trademark policy](https://trademark-policy.openjsf.org/) for information about permissible use of Express.js logos and marks.
-
-<div class="logo-table">
-    <div>
-        <h3>Logotype</h3><a href="/images/brand/logotype-light.svg" class="hidden-dark">
-            <img src="/images/brand/logotype-light.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-        <a href="/images/brand/logotype-dark.svg" class="hidden-light">
-            <img src="/images/brand/logotype-dark.svg" alt="Express.js logo" width="250" height="56"/>
-        </a>
-    </div>
-    <div>
-        <h3>Logomark</h3><a href="/images/brand/logo-light.svg" class="hidden-dark">
-            <img src="/images/brand/logo-light.svg" alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-        <a href="/images/brand/logo-dark.svg" class="hidden-light">
-            <img src="/images/brand/logo-dark.svg"  alt="Express.js mark" width="96.5" height="56"/>
-        </a>
-    </div>
-<div>
-</div>
diff --git a/zh-tw/resources/contributing.md b/zh-tw/resources/contributing.md
deleted file mode 100644
index 24bdb8dd2a..0000000000
--- a/zh-tw/resources/contributing.md
+++ /dev/null
@@ -1,516 +0,0 @@
----
-layout: page
-title: Contributing to Express
-description: Find out how to contribute to Express.js, including guidelines for reporting issues, submitting pull requests, becoming a collaborator, and understanding security policies.
-menu: resources
-order: 5
-redirect_from: "  "
----
-
-# Contributing to Express
-
-### Looking to contribute to Expressjs.com? Click [here](#expressjs-website-contributing).
-
-Express and the other projects in the [expressjs organization on GitHub](https://github.com/expressjs) are projects of the [OpenJs Foundation](https://openjsf.org/).
-These projects are governed under the general policies and guidelines of the Node.js Foundation along with the additional guidelines below.
-
-- [Technical committee](#technical-committee)
-- [Community contributing guide](#community-contributing-guide)
-- [Collaborator's guide](#collaborators-guide)
-- [Security policies and procedures](#security-policies-and-procedures)
-
-## Technical committee
-
-The Express technical committee consists of active project members, and guides development and maintenance of the Express project. For more information, see [Express Community - Technical committee](community.html#technical-committee).
-
-## Community contributing guide
-
-<!-- SRC: expressjs/discussions docs/GOVERNANCE.md -->
-
-The goal of this document is to create a contribution process that:
-
-- Encourages new contributions.
-- Encourages contributors to remain involved.
-- Avoids unnecessary processes and bureaucracy whenever possible.
-- Creates a transparent decision making process that makes it clear how
-  contributors can be involved in decision making.
-
-### Vocabulary
-
-- A **Contributor** is any individual creating or commenting on an issue or pull request.
-- A **Committer** is a subset of contributors who have been given write access to the repository.
-- A **Project Captain** is the lead maintainer of a repository.
-- A **TC (Technical Committee)** is a group of committers representing the required technical
-  expertise to resolve rare disputes.
-- A **Triager** is a subset of contributors who have been given triage access to the repository.
-
-### Logging Issues
-
-Log an issue for any question or problem you might have. When in doubt, log an issue, and
-any additional policies about what to include will be provided in the responses. The only
-exception is security disclosures which should be sent privately.
-
-Committers may direct you to another repository, ask for additional clarifications, and
-add appropriate metadata before the issue is addressed.
-
-Please be courteous and respectful. Every participant is expected to follow the
-project's Code of Conduct.
-
-### Contributions
-
-Any change to resources in this repository must be through pull requests. This applies to all changes
-to documentation, code, binary files, etc. Even long term committers and TC members must use
-pull requests.
-
-No pull request can be merged without being reviewed.
-
-For non-trivial contributions, pull requests should sit for at least 36 hours to ensure that
-contributors in other timezones have time to review. Consideration should also be given to
-weekends and other holiday periods to ensure active committers all have reasonable time to
-become involved in the discussion and review process if they wish.
-
-The default for each contribution is that it is accepted once no committer has an objection.
-During a review, committers may also request that a specific contributor who is most versed in a
-particular area gives a "LGTM" before the PR can be merged. There is no additional "sign off"
-process for contributions to land. Once all issues brought by committers are addressed it can
-be landed by any committer.
-
-In the case of an objection being raised in a pull request by another committer, all involved
-committers should seek to arrive at a consensus by way of addressing concerns being expressed
-by discussion, compromise on the proposed change, or withdrawal of the proposed change.
-
-If a contribution is controversial and committers cannot agree about how to get it to land
-or if it should land then it should be escalated to the TC. TC members should regularly
-discuss pending contributions in order to find a resolution. It is expected that only a
-small minority of issues be brought to the TC for resolution and that discussion and
-compromise among committers be the default resolution mechanism.
-
-### Becoming a Triager
-
-Anyone can become a triager! Read more about the process of being a triager in
-[the triage process document](https://github.com/expressjs/discussions/blob/master/Triager-Guide.md).
-
-Currently, any existing [organization member](https://github.com/orgs/expressjs/people) can nominate
-a new triager. If you are interested in becoming a triager, our best advice is to actively participate
-in the community by helping triaging issues and pull requests. As well we recommend
-to engage in other community activities like attending the TC meetings, and participating in the Slack
-discussions. If you feel ready and have been helping triage some issues, reach out to an active member of the organization to ask if they'd
-be willing to support you. If they agree, they can create a pull request to formalize your nomination. In the case of an objection to the nomination, the triage team is responsible for working with the individuals involved and finding a resolution.
-
-You can also reach out to any of the [organization members](https://github.com/orgs/expressjs/people)
-if you have questions or need guidance.
-
-### Becoming a Committer
-
-All contributors who have landed significant and valuable contributions should be onboarded in a timely manner,
-and added as a committer, and be given write access to the repository.
-
-Committers are expected to follow this policy and continue to send pull requests, go through
-proper review, and have other committers merge their pull requests.
-
-### TC Process
-
-The TC uses a "consensus seeking" process for issues that are escalated to the TC.
-The group tries to find a resolution that has no open objections among TC members.
-If a consensus cannot be reached that has no objections then a majority wins vote
-is called. It is also expected that the majority of decisions made by the TC are via
-a consensus seeking process and that voting is only used as a last-resort.
-
-Resolution may involve returning the issue to project captains with suggestions on
-how to move forward towards a consensus. It is not expected that a meeting of the TC
-will resolve all issues on its agenda during that meeting and may prefer to continue
-the discussion happening among the project captains.
-
-Members can be added to the TC at any time. Any TC member can nominate another committer
-to the TC and the TC uses its standard consensus seeking process to evaluate whether or
-not to add this new member. The TC will consist of a minimum of 3 active members and a
-maximum of 10. If the TC should drop below 5 members the active TC members should nominate
-someone new. If a TC member is stepping down, they are encouraged (but not required) to
-nominate someone to take their place.
-
-TC members will be added as admin's on the Github orgs, npm orgs, and other resources as
-necessary to be effective in the role.
-
-To remain "active" a TC member should have participation within the last 12 months and miss
-no more than six consecutive TC meetings. Our goal is to increase participation, not punish
-people for any lack of participation, this guideline should be only be used as such
-(replace an inactive member with a new active one, for example). Members who do not meet this
-are expected to step down. If A TC member does not step down, an issue can be opened in the
-discussions repo to move them to inactive status. TC members who step down or are removed due
-to inactivity will be moved into inactive status.
-
-Inactive status members can become active members by self nomination if the TC is not already
-larger than the maximum of 10. They will also be given preference if, while at max size, an
-active member steps down.
-
-### Project Captains
-
-The Express TC can designate captains for individual projects/repos in the
-organizations. These captains are responsible for being the primary
-day-to-day maintainers of the repo on a technical and community front.
-Repo captains are empowered with repo ownership and package publication rights.
-When there are conflicts, especially on topics that effect the Express project
-at large, captains are responsible to raise it up to the TC and drive
-those conflicts to resolution. Captains are also responsible for making sure
-community members follow the community guidelines, maintaining the repo
-and the published package, as well as in providing user support.
-
-Like TC members, Repo captains are a subset of committers.
-
-To become a captain for a project the candidate is expected to participate in that
-project for at least 6 months as a committer prior to the request. They should have
-helped with code contributions as well as triaging issues. They are also required to
-have 2FA enabled on both their GitHub and npm accounts.
-
-Any TC member or an existing captain on the **same** repo can nominate another committer
-to the captain role. To do so, they should submit a PR to this document, updating the
-**Active Project Captains** section (while maintaining the sort order) with the project
-name, the nominee's GitHub handle, and their npm username (if different).
-
-- Repos can have as many captains as make sense for the scope of work.
-- A TC member or an existing repo captain **on the same project** can nominate a new captain.
-  Repo captains from other projects should not nominate captains for a different project.
-
-The PR will require at least 2 approvals from TC members and 2 weeks hold time to allow
-for comment and/or dissent.  When the PR is merged, a TC member will add them to the
-proper GitHub/npm groups.
-
-#### Active Projects and Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#active-projects-and-members)
-
-#### Current Initiative Captains
-
-The list can be found at [https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains](https://github.com/expressjs/discussions/blob/HEAD/docs/contributing/captains_and_committers.md#current-initiative-captains)
-
-### Inactivity and Emeritus Policy for Any Role
-
-To support the health and continuity of the project, all individuals holding a role within the community (such as Triager, Committer, WG member, Project Captain, or TC member) are encouraged to maintain active participation.
-
-Inactivity is defined as the absence of meaningful involvement in the project—such as contributions, code reviews, triage, meeting attendance, or discussion participation—for a continuous period of 6 months.
-
-#### Exceptions
-
-Anyone may request a temporary leave from active participation due to personal or professional reasons. In such cases, the individual should inform the relevant team or the Technical Committee (TC). During this time, the inactivity policy is paused, and the individual will not be flagged as inactive.
-
-#### Inactivity Process
-
-- If someone is deemed inactive, the individual may be transitioned to an emeritus role that reflects their past contributions. A best effort will be made to inform them that this has occurred. They may request to be reinstated when they are ready to be active again.
-- The emeritus status helps preserve a clear record of contributors who have meaningfully shaped the project over time.
-
-#### Accountability
-
-- The Technical Committee (TC) and the respective captains of each package/team are responsible for assessing activity levels and enacting this policy fairly and transparently, in coordination with other relevant teams.
-- In case of disagreement, the situation can be discussed and resolved by consensus within the TC or appropriate team.
-
-### Developer's Certificate of Origin 1.1
-
-```text
-By making a contribution to this project, I certify that:
-
- (a) The contribution was created in whole or in part by me and I
-     have the right to submit it under the open source license
-     indicated in the file; or
-
- (b) The contribution is based upon previous work that, to the best
-     of my knowledge, is covered under an appropriate open source
-     license and I have the right under that license to submit that
-     work with modifications, whether created in whole or in part
-     by me, under the same open source license (unless I am
-     permitted to submit under a different license), as indicated
-     in the file; or
-
- (c) The contribution was provided directly to me by some other
-     person who certified (a), (b) or (c) and I have not modified
-     it.
-
- (d) I understand and agree that this project and the contribution
-     are public and that a record of the contribution (including all
-     personal information I submit with it, including my sign-off) is
-     maintained indefinitely and may be redistributed consistent with
-     this project or the open source license(s) involved.
-```
-
-## Collaborator's guide
-
-<!-- SRC: expressjs/.github CONTRIBUTING.md -->
-
-### Website Issues
-
-Open issues for the expressjs.com website in https://github.com/expressjs/expressjs.com.
-
-For issues in other Express managed repos (everything in `expressjs`, `pillarjs` or `jshttp` other than `expressjs/express`), be sure to check their contributing guide and open issues and PRs in the appropriate repository.
-
-### PRs and Code contributions
-
-- Tests must pass.
-- Follow the [JavaScript Standard Style](https://standardjs.com/) and `npm run lint`.
-- If you fix a bug, add a test.
-
-### Branches
-
-Use the `master` branch for bug fixes or minor work that is intended for the
-current release stream.
-
-Use the correspondingly named branch, e.g. `6.x`, for anything intended for
-a future release of Express.
-
-### Steps for contributing
-
-1. Create an issue for the
-   bug you want to fix or the feature that you want to add.
-2. Create your own fork on GitHub, then
-   checkout your fork.
-3. Write your code in your local copy. It's good practice to create a branch for
-   each new issue you work on, although not compulsory.
-4. To run the test suite, first install the dependencies by running `npm install`,
-   then run `npm test`.
-5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-   see listed.
-6. If the tests pass, you can commit your changes to your fork and then create
-   a pull request from there. Make sure to reference your issue from the pull
-   request comments by including the issue number e.g. `#123`.
-
-### Issues which are questions
-
-We will typically close any vague issues or questions that are specific to some
-app you are writing. Please double check the docs and other references before
-being trigger happy with posting a question issue.
-
-Things that will help get your question issue looked at:
-
-- Full and runnable JS code.
-- Clear description of the problem or unexpected behavior.
-- Clear description of the expected result.
-- Steps you have taken to debug it yourself.
-
-If you post a question and do not outline the above items or make it easy for
-us to understand and reproduce your issue, it will be closed.
-
-If your question meets all of the above requirements but you do not believe it needs to be looked at
-by the maintainers
-(for example, if you are just looking for community input) please open it as a discussion topic instead
-of an issue. If you
-are unsure and open an issue, we may move it to discussions if we triage them and decide they do
-not need high
-visibility or maintainer input.
-
-## Security Policies and Procedures
-
-<!-- SRC: expressjs/.github SECURITY.md -->
-
-This document outlines security procedures and general policies for the Express
-project.
-
-- [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
-- [Disclosure Policy](#disclosure-policy)
-- [Comments on this Policy](#comments-on-this-policy)
-- [The Express Threat Model](#the-express-threat-model)
-
-### Reporting a Bug or Security Vulnerability
-
-> [!IMPORTANT]
-> Before reporting a vulnerability, please review the [Express Threat Model](#the-express-threat-model) to check if the issue falls within Express's security scope.
-
-The Express team and community take all security vulnerabilities seriously.
-Thank you for improving the security of Express and related projects.
-We appreciate your efforts in responsible disclosure and will make every effort
-to acknowledge your contributions.
-
-A [Security triage team member](https://github.com/expressjs/security-wg#security-triage-team-expressjssecurity-triage)
-or [the repo captain](https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md)
-will acknowledge your report as soon as possible.
-These timelines may extend when our triage
-volunteers are away on holiday, particularly at the end of the year.
-
-After the initial reply to your report, the security team will
-endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-> [!NOTE]  
-> You can find more information about our process in [this guide](https://github.com/expressjs/security-wg/blob/main/docs/incident_response_plan.md)
-
-#### Reporting Security Bugs via GitHub Security Advisory (Preferred)
-
-The preferred way to report security vulnerabilities is through
-[GitHub Security Advisories](https://github.com/advisories).
-This allows us to collaborate on a fix while maintaining the
-confidentiality of the report.
-
-To report a vulnerability
-([docs](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)):
-
-1. Visit the **Security** tab of the affected repository on GitHub.
-2. Click **Report a vulnerability** and follow the provided steps.
-
-This process applies to any repositories within the Express ecosystem.
-If you are unsure whether a repository falls under this policy,
-feel free to reach out via email.
-
-#### Reporting via Email
-
-If you prefer, you can also report security issues by emailing `express-security@lists.openjsf.org`.
-
-To ensure a timely response, please include all relevant details directly in the email body rather than linking to external sources or attaching files.
-
-The lead maintainer will acknowledge your email within 48 hours and provide an initial response outlining the next steps. The security team will keep you updated on the progress and may request additional details.
-
-#### Third-Party Modules
-
-If the security issue pertains to a third-party module that is not directly maintained within the Express ecosystem, please report it to the maintainers of that module.
-
-### Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-- Confirm the problem and determine the affected versions.
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance. These fixes will be
-  released as fast as possible to npm.
-
-### Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
-
-### The Express Threat Model
-
-The Express threat model defines the boundaries of what the framework considers its security responsibility. It establishes which elements are trusted (such as the developer, the runtime environment, and application code) versus untrusted (such as data from network connections). Issues arising from trusted elements are considered out of scope, while Express is responsible for safely handling untrusted data.
-
-Many commonly reported concerns fall outside Express's security scope and are the responsibility of the application developer. Such as prototype pollution from unsanitized user input, misconfigured static file serving, or issues in third-party dependencies.
-
-For complete details, see the [Express Threat Model](https://github.com/expressjs/security-wg/blob/main/docs/ThreatModel.md).
-
-----
-
-# Contributing to Expressjs.com {#expressjs-website-contributing}
-
-<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
-
-### The Official Documentation of the Express.js Framework
-
-This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
-
-#### Need some ideas? These are some typical issues.
-
-1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-   - Display or screen sizing problems
-   - Mobile responsiveness issues
-   - Missing or broken accessibility features
-   - Website outages
-   - Broken links
-   - Page structure or user interface enhancements
-
-2. **Content Issues**: Fix anything related to site content or typos.
-   - Spelling errors
-   - Incorrect/outdated Express.js documentation
-   - Missing content
-
-3. **Translation Issues**: Fix any translation errors or contribute new content.
-   - Fix spelling errors
-   - Fix incorrect/poorly translated words
-   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
-
-#### Want to work on a backlog issue?
-
-We often have bugs or enhancements that need work. You can find these under our repo's [Issues tab](https://github.com/expressjs/expressjs.com/issues). Check out the tags to find something that's a good match for you.
-
-#### Have an idea? Found a bug?
-
-If you've found a bug or a typo, or if you have an idea for an enhancement, you can:
-
-- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
-
-- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
-
-## Getting Started
-
-The steps below will guide you through the Expressjs.com contribution process.
-
-#### Step 1: (OPTIONAL) Open a New Issue
-
-So you've found a problem that you want to fix, or have a site enhancement you want to make.
-
-1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-   - For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
-   - When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
-
-2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
-   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
-
-#### Step 2: Get the Application Code Base
-
-Clone the repo and get the code:
-
-```sh
-git clone https://github.com/expressjs/expressjs.com.git
-```
-
-After you've got the code you're ready to start making your changes!
-
-But just in case you need a little extra explanation, this section below outlines the main sections of the code base, where most changes are likely to be made.
-
-**Markdown Page Files**:
-
-- These files render to html and make up the individual pages of the site. Most of the site's documentation text content is written in `md` files.
-- Change these to make changes to individual pages' content/text or markup.
-- Each language has its own complete set of pages, located under their respective language directories - all the Spanish markdown content is found in the `es` directory, for example.
-
-**Includes Partials and Layout Templates**
-
-- `_includes` are partials that are imported and reused across multiple pages.
-  - These are used to import text content for reuse across pages, such as the API documentation, e.g., `_includes > api > en > 5x`, which is included in every language.
-  - These are used to include the page components that make up site-wide user interface and periphery structure, e.g., Header, Footer, etc.
-- `_layouts` are the templates used to wrap the site's individual pages.
-  - These are used to display the structure of the site's periphery, such as the header and footer, and for injecting and displaying individual markdown pages inside the `content` tag.
-
-**Blog Markdown Files**
-
-- These files make up the individual blog posts. If you want to contribute a blog post please
-  follow the specific instructions for [How to write a blog post.](https://expressjs.com/en/blog/write-post.html)
-- Located under the `_posts` directory.
-
-**CSS or Javascript**
-
-- All css and js files are kept in `css` and `js` folders on the project root.
-
-The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
-
-#### Step 3: Running the Application
-
-Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
-
-1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
-   - This is the recommended option for moderate to complex work.
-
-2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
-   1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
-   2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
-   3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
-
-## Contributing translations
-
-We use Crowdin to manage our translations in multiple languages and achieve automatic translation with artificial intelligence. Since these translations can be inefficient in some cases, we need help from the community to provide accurate and helpful translations.
-
-The documentation is translated into these languages:
-
-- Chinese Simplified (`zh-cn`)
-- Chinese Traditional (`zh-tw`)
-- English (`en`)
-- French (`fr`)
-- German (`de`)
-- Italian (`it`)
-- Japanese (`ja`)
-- Korean (`ko`)
-- Brazilian Portuguese (`pt-br`)
-- Spanish (`es`)
-
-### How to translate
-
-1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
-2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
-3. [Start translating](https://support.crowdin.com/online-editor/)
-
diff --git a/zh-tw/resources/glossary.md b/zh-tw/resources/glossary.md
deleted file mode 100644
index e602fa0f2d..0000000000
--- a/zh-tw/resources/glossary.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-layout: page
-title: Express 名詞解釋
-description: A comprehensive glossary of terms related to Express.js, Node.js, middleware, routing, and other key concepts to help you understand and use Express effectively.
-menu: resources
-order: 2
-redirect_from: "  "
----
-
-# 名詞解釋
-
-### 應用程式 (application)
-
-In general, one or more programs that are designed to carry out operations for a specific purpose.  通常是指設計成實行作業以達特定目的的一或多個程式。就 Express 環境定義來說，是指使用 Express API（在 Node.js 平台上執行）的程式。亦可稱為[應用程式物件 (app object)](/{{ page.lang }}/api.html#express)。  Might also refer to an [app object](/{{ page.lang }}/api.html#express).
-
-### API
-
-Application programming interface. Spell out the abbreviation when it is first used.
-
-### Express
-
-A fast, un-opinionated, minimalist web framework for Node.js applications. 快速、集思廣益、極簡的 Node.js 應用程式 Web 架構。一般而言，"Express" 比 "Express.js" 合適，不過，也能接受後者。
-
-### libuv
-
-多平台支援的程式庫，著重在非同步 I/O，主要開發供 Node.js 使用。
-
-### middleware
-
-A function that is invoked by the Express routing layer before the final request handler, and thus sits in the middle between a raw request and the final intended route. A few fine points of terminology around middleware:
-
-- `var foo = require('middleware')` 可稱為_需要_或_使用_ Node.js 模組。接著，`var mw = foo()` 陳述式通常會傳回中介軟體。 Then the statement `var mw = foo()` typically returns the middleware.
-- `app.use(mw)` 可稱為_將中介軟體新增至廣域處理程序堆疊_。
-- `app.get('/foo', mw, function (req, res) { ... })` 可稱為_將中介軟體新增至 "GET /foo" 處理程序堆疊_。
-
-### Node.js
-
-A software platform that is used to build scalable network applications. Node.js uses JavaScript as its scripting language, and achieves high throughput via non-blocking I/O and a single-threaded event loop. See [nodejs.org](https://nodejs.org/en/). **Usage note**: Initially, "Node.js," thereafter "Node".
-
-### 開放程式碼 (open-source, open source)
-
-當作為形容詞時，會加連號；例如："This is open-source software." 請參閱[維基百科上的開放程式碼軟體](http://en.wikipedia.org/wiki/Open-source_software)。附註：雖然此術語通常不會加連號，我們仍採用標準的英文規則，加上連號來代表複合形容詞。
-
-{% capture english-rules %}
-
-Although it is common not to hyphenate this term, we are using the standard English rules for hyphenating a compound adjective.
-
-{% endcapture %}
-
-{% include admonitions/note.html content=english-rules %}
-
-### 要求 (request)
-
-An HTTP request. A client submits an HTTP request message to a server, which returns a response.  一種 HTTP 要求。用戶端提交 HTTP 要求訊息給伺服器，再由伺服器傳回回應。要求必須使用其中一種[要求方法](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol#Request_methods)，例如 GET、POST 等。
-
-### 回應 (response)
-
-一種 HTTP 回應。伺服器傳回 HTTP 回應訊息給用戶端。回應包含要求的相關完成狀態資訊，也可能將要求內容包含在其訊息內文中。 A server returns an HTTP response message to the client. The response contains completion status information about the request and might also contain requested content in its message body.
-
-### 路由 (route)
-
-Part of a URL that identifies a resource. URL 的一部分，用來識別資源。例如，在 `http://foo.com/products/id` 中，"/products/id" 就是路由。
-
-### 路由器 (router)
-
-請參閱 API 參照中的[路由器](/{{ page.lang }}/4x/api.html#router)。
diff --git a/zh-tw/resources/middleware.md b/zh-tw/resources/middleware.md
deleted file mode 100644
index 6410b55171..0000000000
--- a/zh-tw/resources/middleware.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-layout: middleware
-title: Express 中介軟體
-description: Explore a list of Express.js middleware modules maintained by the Express team and the community, including built-in middleware and popular third-party modules.
-menu: resources
-order: 3
-redirect_from: "  "
-module: mw-home
----
-
-## Express 中介軟體
-
-The Express middleware modules listed here are maintained by the
-[Expressjs team](https://github.com/orgs/expressjs/people).
-
-| Middleware module                                                           | Description                                                                                                                         |
-| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [body-parser](/{{page.lang}}/resources/middleware/body-parser.html)         | Parse HTTP request body.                                                                                            |
-| [compression](/{{page.lang}}/resources/middleware/compression.html)         | Compress HTTP responses.                                                                                            |
-| [connect-rid](/{{page.lang}}/resources/middleware/connect-rid.html)         | Generate unique request ID.                                                                                         |
-| [cookie-parser](/{{page.lang}}/resources/middleware/cookie-parser.html)     | Parse cookie header and populate `req.cookies`. See also [cookies](https://github.com/jed/cookies). |
-| [cookie-session](/{{page.lang}}/resources/middleware/cookie-session.html)   | Establish cookie-based sessions.                                                                                    |
-| [cors](/{{page.lang}}/resources/middleware/cors.html)                       | Enable cross-origin resource sharing (CORS) with various options.                                |
-| [errorhandler](/{{page.lang}}/resources/middleware/errorhandler.html)       | Development error-handling/debugging.                                                                               |
-| [method-override](/{{page.lang}}/resources/middleware/method-override.html) | Override HTTP methods using header.                                                                                 |
-| [morgan](/{{page.lang}}/resources/middleware/morgan.html)                   | HTTP request logger.                                                                                                |
-| [multer](/{{page.lang}}/resources/middleware/multer.html)                   | Handle multi-part form data.                                                                                        |
-| [response-time](/{{page.lang}}/resources/middleware/response-time.html)     | Record HTTP response time.                                                                                          |
-| [serve-favicon](/{{page.lang}}/resources/middleware/serve-favicon.html)     | Serve a favicon.                                                                                                    |
-| [serve-index](/{{page.lang}}/resources/middleware/serve-index.html)         | Serve directory listing for a given path.                                                                           |
-| [serve-static](/{{page.lang}}/resources/middleware/serve-static.html)       | Serve static files.                                                                                                 |
-| [session](/{{page.lang}}/resources/middleware/session.html)                 | Establish server-based sessions (development only).                                              |
-| [timeout](/{{page.lang}}/resources/middleware/timeout.html)                 | Set a timeout perioHTTP request processing.                                                                         |
-| [vhost](/{{page.lang}}/resources/middleware/vhost.html)                     | Create virtual domains.                                                                                             |
-
-## Additional middleware modules
-
-These are some additional popular middleware modules.
-
-{% include community-caveat.html %}
-
-| Middleware module                                                            | Description                                                                                                                                                                                   |
-| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [helmet](https://github.com/helmetjs/helmet)：此模組會設定各種 HTTP 標頭，有助於保護您應用程式的安全。 | Helps secure your apps by setting various HTTP headers.                                                                                                                       |
-| [passport](https://github.com/jaredhanson/passport)：鑑別用的 Express 中介軟體模組。     | Authentication using "strategies" such as OAuth, OpenID and many others.  See [passportjs.org](https://passportjs.org/) for more information. |
diff --git a/zh-tw/resources/middleware/body-parser.md b/zh-tw/resources/middleware/body-parser.md
deleted file mode 100644
index 9c3e7e0276..0000000000
--- a/zh-tw/resources/middleware/body-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express body-parser middleware
-menu: resources
-redirect_from: '  '
-module: body-parser
----
diff --git a/zh-tw/resources/middleware/compression.md b/zh-tw/resources/middleware/compression.md
deleted file mode 100644
index d288542a65..0000000000
--- a/zh-tw/resources/middleware/compression.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express compression middleware
-menu: resources
-redirect_from: '  '
-module: compression
----
diff --git a/zh-tw/resources/middleware/connect-rid.md b/zh-tw/resources/middleware/connect-rid.md
deleted file mode 100644
index 95b2689265..0000000000
--- a/zh-tw/resources/middleware/connect-rid.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express connect-rid middleware
-menu: resources
-redirect_from: '  '
-module: connect-rid
----
diff --git a/zh-tw/resources/middleware/cookie-parser.md b/zh-tw/resources/middleware/cookie-parser.md
deleted file mode 100644
index 55100372e3..0000000000
--- a/zh-tw/resources/middleware/cookie-parser.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-parser middleware
-menu: resources
-redirect_from: '  '
-module: cookie-parser
----
diff --git a/zh-tw/resources/middleware/cookie-session.md b/zh-tw/resources/middleware/cookie-session.md
deleted file mode 100644
index c6308fa81c..0000000000
--- a/zh-tw/resources/middleware/cookie-session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cookie-session middleware
-menu: resources
-redirect_from: '  '
-module: cookie-session
----
diff --git a/zh-tw/resources/middleware/cors.md b/zh-tw/resources/middleware/cors.md
deleted file mode 100644
index 4692141929..0000000000
--- a/zh-tw/resources/middleware/cors.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express cors middleware
-menu: resources
-redirect_from: '  '
-module: cors
----
diff --git a/zh-tw/resources/middleware/errorhandler.md b/zh-tw/resources/middleware/errorhandler.md
deleted file mode 100644
index 3b11a1208e..0000000000
--- a/zh-tw/resources/middleware/errorhandler.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express errorhandler middleware
-menu: resources
-redirect_from: '  '
-module: errorhandler
----
diff --git a/zh-tw/resources/middleware/method-override.md b/zh-tw/resources/middleware/method-override.md
deleted file mode 100644
index 8dff029cd4..0000000000
--- a/zh-tw/resources/middleware/method-override.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express method-override middleware
-menu: resources
-redirect_from: '  '
-module: method-override
----
diff --git a/zh-tw/resources/middleware/morgan.md b/zh-tw/resources/middleware/morgan.md
deleted file mode 100644
index 99c4c80fa9..0000000000
--- a/zh-tw/resources/middleware/morgan.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express morgan middleware
-menu: resources
-redirect_from: '  '
-module: morgan
----
diff --git a/zh-tw/resources/middleware/multer.md b/zh-tw/resources/middleware/multer.md
deleted file mode 100644
index 2fffab3b73..0000000000
--- a/zh-tw/resources/middleware/multer.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express multer middleware
-menu: resources
-redirect_from: '  '
-module: multer
----
diff --git a/zh-tw/resources/middleware/response-time.md b/zh-tw/resources/middleware/response-time.md
deleted file mode 100644
index 78ee67cd32..0000000000
--- a/zh-tw/resources/middleware/response-time.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express response-time middleware
-menu: resources
-redirect_from: '  '
-module: response-time
----
diff --git a/zh-tw/resources/middleware/serve-favicon.md b/zh-tw/resources/middleware/serve-favicon.md
deleted file mode 100644
index 7a1c8e6f5c..0000000000
--- a/zh-tw/resources/middleware/serve-favicon.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-favicon middleware
-menu: resources
-redirect_from: '  '
-module: serve-favicon
----
diff --git a/zh-tw/resources/middleware/serve-index.md b/zh-tw/resources/middleware/serve-index.md
deleted file mode 100644
index deeb963c8f..0000000000
--- a/zh-tw/resources/middleware/serve-index.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-index middleware
-menu: resources
-redirect_from: '  '
-module: serve-index
----
diff --git a/zh-tw/resources/middleware/serve-static.md b/zh-tw/resources/middleware/serve-static.md
deleted file mode 100644
index ff9bcc313e..0000000000
--- a/zh-tw/resources/middleware/serve-static.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express serve-static middleware
-menu: resources
-redirect_from: '  '
-module: serve-static
----
diff --git a/zh-tw/resources/middleware/session.md b/zh-tw/resources/middleware/session.md
deleted file mode 100644
index 22cf354ae7..0000000000
--- a/zh-tw/resources/middleware/session.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express session middleware
-menu: resources
-redirect_from: '  '
-module: session
----
diff --git a/zh-tw/resources/middleware/timeout.md b/zh-tw/resources/middleware/timeout.md
deleted file mode 100644
index 1afa2c5dd3..0000000000
--- a/zh-tw/resources/middleware/timeout.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express timeout middleware
-menu: resources
-redirect_from: '  '
-module: timeout
----
diff --git a/zh-tw/resources/middleware/vhost.md b/zh-tw/resources/middleware/vhost.md
deleted file mode 100644
index 2bad4c964f..0000000000
--- a/zh-tw/resources/middleware/vhost.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-layout: middleware
-title: Express vhost middleware
-menu: resources
-redirect_from: '  '
-module: vhost
----
diff --git a/zh-tw/resources/utils.md b/zh-tw/resources/utils.md
deleted file mode 100644
index 4c1a17b886..0000000000
--- a/zh-tw/resources/utils.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-layout: page
-title: Express utilities
-description: Discover utility modules related to Express.js and Node.js, including tools for cookies, CSRF protection, URL parsing, routing, and more to enhance your applications.
-menu: resources
-order: 4
-redirect_from: "  "
----
-
-## Express utility functions
-
-The [pillarjs](https://github.com/pillarjs) GitHub organization contains a number of modules
-for utility functions that may be generally useful.
-
-| Utility modules                                                | Description                                                                                                                                                                                                                |
-| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [cookies](https://www.npmjs.com/package/cookies)               | Get and set HTTP(S) cookies that can be signed to prevent tampering, using Keygrip. Can be used with the Node.js HTTP library or as Express middleware. |
-| [csrf](https://www.npmjs.com/package/csrf)                     | Contains the logic behind CSRF token creation and verification.  Use this module to create custom CSRF middleware.                                                                         |
-| [finalhandler](https://www.npmjs.com/package/finalhandler)     | Function to invoke as the final step to respond to HTTP request.                                                                                                                                           |
-| [parseurl](https://www.npmjs.com/package/parseurl)             | Parse a URL with caching.                                                                                                                                                                                  |
-| [path-to-regexp](https://www.npmjs.com/package/path-to-regexp) | Turn an Express-style path string such as \`\`/user/:name\` into a regular expression.                                                                                                     |
-| [resolve-path](https://www.npmjs.com/package/resolve-path)     | Resolves a relative path against a root path with validation.                                                                                                                                              |
-| [router](https://www.npmjs.com/package/router)                 | Simple middleware-style router.                                                                                                                                                                            |
-| [send](https://www.npmjs.com/package/send)                     | Library for streaming files as a HTTP response, with support for partial responses (ranges), conditional-GET negotiation, and granular events.                                          |
-
-For additional low-level HTTP-related modules, see [jshttp](http://jshttp.github.io/).
diff --git a/zh-tw/starter/basic-routing.md b/zh-tw/starter/basic-routing.md
deleted file mode 100644
index 2266d3a1f1..0000000000
--- a/zh-tw/starter/basic-routing.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-layout: page
-title: Express 基本路由
-description: Learn the fundamentals of routing in Express.js applications, including how to define routes, handle HTTP methods, and create route handlers for your web server.
-menu: starter
-order: 4
-redirect_from: "  "
----
-
-# 基本路由
-
-_Routing_ refers to determining how an application responds to a client request to a particular endpoint, which is a URI (or path) and a specific HTTP request method (GET, POST, and so on).
-
-Each route can have one or more handler functions, which are executed when the route is matched.
-
-路由定義的結構如下：
-
-```js
-app.METHOD(PATH, HANDLER)
-```
-
-Where:
-
-- `app` 是 `express` 的實例。
-- `METHOD` is an [HTTP request method](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Methods), in lowercase.
-- `PATH` 是伺服器上的路徑。
-- `HANDLER` 是當路由相符時要執行的函數。
-
-<div class="doc-box doc-notice" markdown="1">
-This tutorial assumes that an instance of `express` named `app` is created and the server is running. 
-這項指導教學假設已建立名稱為 `app` 的 `express` 實例，且伺服器正在執行。如果您不熟悉如何建立和啟動應用程式，請參閱 [Hello world 範例](/{{ page.lang }}/starter/hello-world.html)。
-
-</div>
-
-下列範例說明如何定義簡單的路由。
-
-首頁中以 `Hello World!` 回應。
-
-```js
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-```
-
-Respond to a POST request on the root route (`/`), the application's home page:
-
-```js
-app.post('/', (req, res) => {
-  res.send('Got a POST request')
-})
-```
-
-對 `/user` 路由發出 PUT 要求時的回應：
-
-```js
-app.put('/user', (req, res) => {
-  res.send('Got a PUT request at /user')
-})
-```
-
-對 `/user` 路由發出 DELETE 要求時的回應：
-
-```js
-app.delete('/user', (req, res) => {
-  res.send('Got a DELETE request at /user')
-})
-```
-
-如需路由的詳細資料，請參閱[路由手冊](/{{ page.lang }}/guide/routing.html)。
-
diff --git a/zh-tw/starter/examples.md b/zh-tw/starter/examples.md
deleted file mode 100644
index 86700f94c3..0000000000
--- a/zh-tw/starter/examples.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: page
-title: Express examples
-description: Explore a collection of Express.js application examples covering various use cases, integrations, and advanced configurations to help you learn and build your projects.
-menu: starter
-order: 6
-redirect_from: "  "
----
-
-{% capture examples %}{% include readmes/express-master/examples.md %}{% endcapture %}
-{{ examples | replace: "](.", "](https://github.com/expressjs/express/tree/master/examples" }}
-
-## Additional examples
-
-These are some additional examples with more extensive integrations.
-
-{% include community-caveat.html %}
-
-- [prisma-fullstack](https://github.com/prisma/prisma-examples/tree/latest/pulse/fullstack-simple-chat) - Fullstack app with Express and Next.js using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
-- [prisma-rest-api-ts](https://github.com/prisma/prisma-examples/tree/latest/orm/express) - REST API with Express in TypeScript using [Prisma](https://www.npmjs.com/package/prisma) as an ORM
\ No newline at end of file
diff --git a/zh-tw/starter/faq.md b/zh-tw/starter/faq.md
deleted file mode 100644
index 53348b12ad..0000000000
--- a/zh-tw/starter/faq.md
+++ /dev/null
@@ -1,95 +0,0 @@
----
-layout: page
-title: Express 常見問題 (FAQ)
-description: Find answers to frequently asked questions about Express.js, including topics on application structure, models, authentication, template engines, error handling, and more.
-menu: starter
-order: 7
-redirect_from: "  "
----
-
-# 常見問題 (FAQ)
-
-## 我該如何建立我的應用程式結構？
-
-There is no definitive answer to this question. The answer depends
-on the scale of your application and the team that is involved. To be as
-flexible as possible, Express makes no assumptions in terms of structure.
-
-Routes and other application-specific logic can live in as many files
-as you wish, in any directory structure you prefer. View the following
-examples for inspiration:
-
-- [路由清單](https://github.com/expressjs/express/blob/4.13.1/examples/route-separation/index.js#L32-47)
-- [路由對映](https://github.com/expressjs/express/blob/4.13.1/examples/route-map/index.js#L52-L66)
-- [MVC 樣式控制器](https://github.com/expressjs/express/tree/master/examples/mvc)
-
-此外，Express 有一些協力廠商延伸，可簡化部分這些型樣：
-
-- [express-resource 路由](https://github.com/expressjs/express-resource)
-
-## 如何定義模型？
-
-Express has no notion of a database. This concept is
-left up to third-party Node modules, allowing you to
-interface with nearly any database.
-
-請參閱 [LoopBack](http://loopback.io)，取得以模組為中心的 Express 型架構。
-
-## 如何鑑別使用者？
-
-Authentication is another opinionated area that Express does not
-venture into. You may use any authentication scheme you wish.
-For a simple username / password scheme, see [this example](https://github.com/expressjs/express/tree/master/examples/auth).
-
-## Express 支援哪些範本引擎？
-
-Express 支援符合 `(path, locals, callback)` 簽章的任何範本引擎。若要使範本引擎介面和快取正規化，請參閱 [consolidate.js](https://github.com/visionmedia/consolidate.js) 專案，以取得支援。未列出的範本引擎可能仍支援 Express 簽章。
-To normalize template engine interfaces and caching, see the
-[consolidate.js](https://github.com/visionmedia/consolidate.js)
-project for support. Unlisted template engines might still support the Express signature.
-
-For more information, see [Using template engines with Express](/{{page.lang}}/guide/using-template-engines.html).
-
-## 如何處理 404 回應？
-
-In Express, 404 responses are not the result of an error, so
-the error-handler middleware will not capture them. This behavior is
-because a 404 response simply indicates the absence of additional work to do;
-in other words, Express has executed all middleware functions and routes,
-and found that none of them responded. All you need to
-do is add a middleware function at the very bottom of the stack (below all other functions)
-to handle a 404 response:
-
-```js
-app.use((req, res, next) => {
-  res.status(404).send("Sorry can't find that!")
-})
-```
-
-Add routes dynamically at runtime on an instance of `express.Router()`
-so the routes are not superseded by a middleware function.
-
-## 如何設定錯誤處理程式？
-
-錯誤處理中介軟體的定義方式，與其他中介軟體相同，差別在於引數是四個而非三個，具體來說，就是使用 `(err, req, res, next)` 簽章：
-
-```js
-app.use((err, req, res, next) => {
-  console.error(err.stack)
-  res.status(500).send('Something broke!')
-})
-```
-
-如需相關資訊，請參閱[錯誤處理](/{{ page.lang }}/guide/error-handling.html)。
-
-## 如何呈現一般 HTML？
-
-You don't! 不需要！不需要用 `res.render()` 函數來「呈現」HTML。如果您有特定的檔案，請使用 `res.sendFile()` 函數。如果您會從目錄提供許多資產，請使用 `express.static()` 中介軟體函數。
-If you have a specific file, use the `res.sendFile()` function.
-If you are serving many assets from a directory, use the `express.static()`
-middleware function.
-
-## What version of Node.js does Express require?
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
\ No newline at end of file
diff --git a/zh-tw/starter/generator.md b/zh-tw/starter/generator.md
deleted file mode 100644
index 1c86d3d763..0000000000
--- a/zh-tw/starter/generator.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-layout: page
-title: Express 應用程式產生器
-description: Learn how to use the Express application generator tool to quickly create a skeleton for your Express.js applications, streamlining setup and configuration.
-menu: starter
-order: 3
-redirect_from: "  "
----
-
-# Express 應用程式產生器
-
-Use the application generator tool, `express-generator`, to quickly create an application skeleton.
-
-You can run the application generator with the `npx` command (available in Node.js 8.2.0).
-
-```bash
-$ npx express-generator
-```
-
-For earlier Node versions, install the application generator as a global npm package and then launch it:
-
-```bash
-$ npm install -g express-generator
-$ express
-```
-
-使用 `-h` 選項來顯示指令選項：
-
-```bash
-$ express -h
-
-  Usage: express [options] [dir]
-
-  Options:
-
-    -h, --help          output usage information
-        --version       output the version number
-    -e, --ejs           add ejs engine support
-        --hbs           add handlebars engine support
-        --pug           add pug engine support
-    -H, --hogan         add hogan.js engine support
-        --no-view       generate without view engine
-    -v, --view <engine> add view <engine> support (ejs|hbs|hjs|jade|pug|twig|vash) (defaults to jade)
-    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
-        --git           add .gitignore
-    -f, --force         force on non-empty directory
-```
-
-舉例來說，以下是在現行工作目錄中建立一個名為 _myapp_ 的 Express 應用程式： The app will be created in a folder named _myapp_ in the current working directory and the view engine will be set to <a href="https://pugjs.org/" target="_blank" title="Pug documentation">Pug</a>:
-
-```bash
-$ express --view=pug myapp
-
-   create : myapp
-   create : myapp/package.json
-   create : myapp/app.js
-   create : myapp/public
-   create : myapp/public/javascripts
-   create : myapp/public/images
-   create : myapp/routes
-   create : myapp/routes/index.js
-   create : myapp/routes/users.js
-   create : myapp/public/stylesheets
-   create : myapp/public/stylesheets/style.css
-   create : myapp/views
-   create : myapp/views/index.pug
-   create : myapp/views/layout.pug
-   create : myapp/views/error.pug
-   create : myapp/bin
-   create : myapp/bin/www
-```
-
-然後安裝相依項目：
-
-```bash
-$ cd myapp
-$ npm install
-```
-
-在 MacOS 或 Linux 中，使用下列指令來執行應用程式：
-
-```bash
-$ DEBUG=myapp:* npm start
-```
-
-在 Windows 中，使用下列指令：
-
-```bash
-> set DEBUG=myapp:* & npm start
-```
-
-On Windows PowerShell, use this command:
-
-```bash
-PS> $env:DEBUG='myapp:*'; npm start
-```
-
-Then, load `http://localhost:3000/` in your browser to access the app.
-
-The generated app has the following directory structure:
-
-```bash
-.
-├── app.js
-├── bin
-│   └── www
-├── package.json
-├── public
-│   ├── images
-│   ├── javascripts
-│   └── stylesheets
-│       └── style.css
-├── routes
-│   ├── index.js
-│   └── users.js
-└── views
-    ├── error.pug
-    ├── index.pug
-    └── layout.pug
-
-7 directories, 9 files
-```
-
-<div class="doc-box doc-info" markdown="1">
-The app structure created by the generator is just one of many ways to structure Express apps. Feel free to use this structure or modify it to best suit your needs.
-</div>
\ No newline at end of file
diff --git a/zh-tw/starter/hello-world.md b/zh-tw/starter/hello-world.md
deleted file mode 100644
index b054358462..0000000000
--- a/zh-tw/starter/hello-world.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-layout: page
-title: Express "Hello World" 範例
-description: Get started with Express.js by building a simple 'Hello World' application, demonstrating the basic setup and server creation for beginners.
-menu: starter
-order: 2
-redirect_from: "  "
----
-
-# Hello world 範例
-
-<div class="doc-box doc-info" markdown="1">
-Embedded below is essentially the simplest Express app you can create. 
-本質上，這是您所能建立的最簡易 Express 應用程式。它是單一檔案應用程式 &mdash; 與您使用 [Express 產生器](/{{ page.lang }}/starter/generator.html)所產生的結果*不同*，Express 產生器會建立完整應用程式框架，其中含有眾多 JavaScript 檔案、Jade 範本，以及各種用途的子目錄。
-
-</div>
-
-```js
-const express = require('express')
-const app = express()
-const port = 3000
-
-app.get('/', (req, res) => {
-  res.send('Hello World!')
-})
-
-app.listen(port, () => {
-  console.log(`Example app listening on port ${port}`)
-})
-```
-
-This app starts a server and listens on port 3000 for connections. 應用程式會啟動伺服器，並在埠 3000 接聽連線。應用程式對指向根 URL (`/`) 或_路由_的要求，以 "Hello World!" 回應。對於其他每一個路徑，它的回應是 **404 找不到**。
-
-### Running Locally
-
-首先請建立一個名為 `myapp` 的目錄，切換至該目錄，並執行 `npm init`。然後按照[安裝手冊](/{{ page.lang }}/starter/installing.html)，將 `express` 安裝成一個相依關係。 Then, install `express` as a dependency, as per the [installation guide](/{{ page.lang }}/starter/installing.html).
-
-在 `myapp` 目錄中，建立名為 `app.js` 的檔案，並新增下列程式碼：
-
-<div class="doc-box doc-notice" markdown="1">
-`req`（要求）和 `res`（回應）與 Node 提供的物件完全相同，因此您可以呼叫 `req.pipe()`、`req.on('data', callback)`，以及任何您要執行的項目，而不需要 Express 涉及。
-</div>
-
-使用下列指令來執行應用程式：
-
-```bash
-$ node app.js
-```
-
-然後在瀏覽器中載入 [http://localhost:3000/](http://localhost:3000/)，以查看輸出。
\ No newline at end of file
diff --git a/zh-tw/starter/installing.md b/zh-tw/starter/installing.md
deleted file mode 100644
index adbc0f0f26..0000000000
--- a/zh-tw/starter/installing.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-layout: page
-title: 安裝 Express
-description: Learn how to install Express.js in your Node.js environment, including setting up your project directory and managing dependencies with npm.
-menu: starter
-order: 1
-redirect_from: "  "
----
-
-# 安裝
-
-假設您已安裝 [Node.js](https://nodejs.org/)，請建立目錄來保留您的應用程式，並使它成為您的工作目錄。
-
-- [Express 4.x](/{{ page.lang }}/4x/api.html) requires Node.js 0.10 or higher.
-- [Express 5.x](/{{ page.lang }}/5x/api.html) requires Node.js 18 or higher.
-
-```bash
-$ mkdir myapp
-$ cd myapp
-```
-
-Use the `npm init` command to create a `package.json` file for your application.
-使用 `npm init` 指令，為您的應用程式建立 `package.json` 檔。如需 `package.json` 如何運作的相關資訊，請參閱 [Specifics of npm's package.json handling](https://docs.npmjs.com/files/package.json)。
-
-```bash
-$ npm init
-```
-
-This command prompts you for a number of things, such as the name and version of your application.
-For now, you can simply hit RETURN to accept the defaults for most of them, with the following exception:
-
-```
-entry point: (index.js)
-```
-
-輸入 `app.js`，或您所要的主要檔名稱。如果您希望其名稱是 `index.js`，請按 RETURN 鍵，接受建議的預設檔名。 If you want it to be `index.js`, hit RETURN to accept the suggested default file name.
-
-現在，將 Express 安裝在 `myapp` 目錄中，並儲存在相依關係清單中。例如： For example:
-
-```bash
-$ npm install express
-```
-
-如果只想暫時安裝 Express，而不新增至相依關係清單，請省略 `--save` 選項：
-
-```bash
-$ npm install express --no-save
-```
-
-<div class="doc-box doc-info" markdown="1">
-
-安裝 Node 模組時，如果指定了 `--save` 選項，則會將這些模組新增至 `package.json` 檔中的 `dependencies` 清單。之後，當您在 `app` 目錄中執行 `npm install` 時，就會自動安裝相依關係清單中的模組。
- Then, afterwards, running `npm install` in the app directory will automatically install modules in the dependencies list.
-</div>
\ No newline at end of file
diff --git a/zh-tw/starter/static-files.md b/zh-tw/starter/static-files.md
deleted file mode 100644
index d3aba1964c..0000000000
--- a/zh-tw/starter/static-files.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-layout: page
-title: 在 Express 中提供靜態檔案
-description: Understand how to serve static files like images, CSS, and JavaScript in Express.js applications using the built-in 'static' middleware.
-menu: starter
-order: 5
-redirect_from: "  "
----
-
-# 在 Express 中提供靜態檔案
-
-To serve static files such as images, CSS files, and JavaScript files, use the `express.static` built-in middleware function in Express.
-
-The function signature is:
-
-```js
-express.static(root, [options])
-```
-
-The `root` argument specifies the root directory from which to serve static assets.
-For more information on the `options` argument, see [express.static](/{{page.lang}}/5x/api.html#express.static).
-
-For example, use the following code to serve images, CSS files, and JavaScript files in a directory named `public`:
-
-```js
-app.use(express.static('public'))
-```
-
-現在，您可以載入位於 `public` 目錄中的檔案：
-
-```text
-http://localhost:3000/images/kitten.jpg
-http://localhost:3000/css/style.css
-http://localhost:3000/js/app.js
-http://localhost:3000/images/bg.png
-http://localhost:3000/hello.html
-```
-
-<div class="doc-box doc-info">
-Express 會查閱靜態目錄的相對檔案，因此靜態目錄的名稱不是 URL 的一部分。
-</div>
-
-To use multiple static assets directories, call the `express.static` middleware function multiple times:
-
-```js
-app.use(express.static('public'))
-app.use(express.static('files'))
-```
-
-Express looks up the files in the order in which you set the static directories with the `express.static` middleware function.
-
-{% capture alert_content %}
-For best results, [use a reverse proxy](/{{page.lang}}/advanced/best-practice-performance.html#use-a-reverse-proxy) cache to improve performance of serving static assets.
-{% endcapture %}
-{% include admonitions/note.html content=alert_content %}
-
-To create a virtual path prefix (where the path does not actually exist in the file system) for files that are served by the `express.static` function, [specify a mount path](/{{ page.lang }}/5x/api.html#app.use) for the static directory, as shown below:
-
-```js
-app.use('/static', express.static('public'))
-```
-
-現在，您可以透過 `/static` 路徑字首，來載入 `public` 目錄中的檔案。
-
-```text
-http://localhost:3000/static/images/kitten.jpg
-http://localhost:3000/static/css/style.css
-http://localhost:3000/static/js/app.js
-http://localhost:3000/static/images/bg.png
-http://localhost:3000/static/hello.html
-```
-
-不過，您提供給 `express.static` 函數的路徑，是相對於您從中啟動 `node` 程序的目錄。如果您是從另一個目錄執行 Express 應用程式，保險作法是使用您想提供之目錄的絕對路徑： If you run the express app from another directory, it's safer to use the absolute path of the directory that you want to serve:
-
-```js
-const path = require('path')
-app.use('/static', express.static(path.join(__dirname, 'public')))
-```
-
-For more details about the `serve-static` function and its options, see  [serve-static](/resources/middleware/serve-static.html).
\ No newline at end of file
diff --git a/zh-tw/support/index.md b/zh-tw/support/index.md
deleted file mode 100644
index 2b70a1fb48..0000000000
--- a/zh-tw/support/index.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-layout: page
-title: Version Support
-description: Find information about the support schedule for different Express.js versions, including which versions are currently maintained and end-of-life policies.
-menu: support
----
-
-# Version Support
-
-Only the latest version of any given major release line is supported.
-
-Versions that are EOL (end-of-life) _may_ receive updates for critical security vulnerabilities, but the Express team offers no guarantee and does not plan to address or release fixes for any issues found.
-
-| Major Version                                                                                                                                              | Minimum Node.js Version | Support Start Date | Support End Date                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | ------------------ | ---------------------------------------------------------- |
-| [**v5.x**{: .supported }](/{{page.lang}}/5x/api.html){: .ignore-underline} | 18                                      | September 2024     | **ongoing**{: .supported } |
-| [**v4.x**{: .supported }](/{{page.lang}}/4x/api.html){: .ignore-underline} | 0.10.0  | April 2014         | **ongoing**{: .supported } |
-| [**v3.x**{: .eol }](/{{page.lang}}/3x/api.html){: .ignore-underline}       | 0.8.0   | October 2012       | July 2015                                                  |
-| [**v2.x**{: .eol }](/2x/){: .ignore-underline}                             | 0.4.1   | March 2011         | July 2012                                                  |
-| **v1.x**{: .eol }                                                                                          | 0.2.0   | December 2010      | March 2011                                                 |
-| **v0.14.x**{: .eol }                                                                       | 0.1.98  | December 2010      | December 2010                                              |
-
-## Commercial Support Options
-
-If you are unable to update to a supported version of Express, please contact one of our partners to receive security updates:
-
-- [HeroDevs Never-Ending Support](http://www.herodevs.com/support/express-nes?utm_source=expressjs&utm_medium=link&utm_campaign=express_eol_page)